Last updated on December 25, 2018
In my topology, spirent is connected to MRV switch ( L1 switch). MRV switch interface gi 0/13 is connected to the CISCO switch interface gi 0/14. I don't see any errors on the gi 0/14 of the cisco switch. However, I see the errors on the gi 0/13 ,which is the interface coming from MRV. Does it mean that CISCO switch is telling that there is some problem in the MRV switch?
In my topology, I have connected spirent - traffic generator to MRV switch ( L1 switch) and then connected to CISCO switch. I am seeing some input errors on this interface. What does it mean? Does it mean that some packets are bad from spirent MRV switch. here is the show command of the interface gi 0/13.
My quesion is what the above error indicates to me.
1557336 input errors, 1557204 CRC, 0 frame, 0 overrun, 0 ignored
c3560g_1>sh interfaces gi 0/13 GigabitEthernet0/13 is up, line protocol is up (connected) Hardware is Gigabit Ethernet, address is 0013.c4d0.570d (bia 0013.c4d0.570d) Description: -- MRV, 1.1.19 -- MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX input flow-control is off, output flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input never, output 00:00:01, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 1000 bits/sec, 2 packets/sec 80971440 packets input, 125278495288 bytes, 0 no buffer Received 0 broadcasts (0 multicasts) 132 runts, 0 giants, 0 throttles 1557336 input errors, 1557204 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 0 input packets with dribble condition detected 24289474 packets output, 36669631614 bytes, 0 underruns 0 output errors, 0 collisions, 5 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 0 output buffer failures, 0 output buffers swapped out