02-19-2014 03:28 PM - edited 03-04-2019 10:23 PM
one off our switch showing in logs
000895: Feb 20 12:02:26 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to up
000896: Feb 20 12:02:28 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
000897: Feb 20 12:02:46 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to down
000898: Feb 20 12:02:47 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to down
000899: Feb 20 12:02:50 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to up
000900: Feb 20 12:02:52 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
000901: Feb 20 12:03:09 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to down
000902: Feb 20 12:03:10 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to down
000903: Feb 20 12:03:13 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to up
000904: Feb 20 12:03:15 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
000905: Feb 20 12:03:32 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to down
000906: Feb 20 12:03:33 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to down
000907: Feb 20 12:03:36 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to up
000908: Feb 20 12:03:38 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
000909: Feb 20 12:03:55 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to down
000910: Feb 20 12:03:56 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to down
000911: Feb 20 12:03:59 NZDT: %LINK-3-UPDOWN: Interface FastEthernet0/16, changed state to up
000912: Feb 20 12:04:01 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to up
000913: Feb 20 12:04:18 NZDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/16, changed state to down
its just keep going after some time switch reboot it self and reboot status showes
Last reset from address error
is this a bug ?
thanks
02-19-2014 04:25 PM
Post the following output:
1. sh interface F0/16; and
2. sh controll e F0/16
02-19-2014 04:39 PM
please see below
#sh int f0/16
FastEthernet0/16 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is 0018.184e.0392 (bia 0018.184e.0392)
Description: USER VOICE/DATA PORT
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, 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 3000 bits/sec, 4 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
24810 packets output, 3226551 bytes, 0 underruns
0 output errors, 0 collisions, 1 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
#sh controllers ethernet-controller f0/16
Transmit FastEthernet0/16 Receive
3234001 Bytes 0 Bytes
1968 Unicast frames 0 Unicast frames
12173 Multicast frames 0 Multicast frames
10755 Broadcast frames 0 Broadcast frames
0 Too old frames 0 Unicast bytes
0 Deferred frames 0 Multicast bytes
0 MTU exceeded frames 0 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 0 Minimum size frames
0 8 collision frames 0 65 to 127 byte frames
0 9 collision frames 0 128 to 255 byte frames
0 10 collision frames 0 256 to 511 byte frames
0 11 collision frames 0 512 to 1023 byte frames
0 12 collision frames 0 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 0 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
7011 64 byte frames 0 Valid frames, too small
14024 127 byte frames
1056 255 byte frames 0 Too old frames
2474 511 byte frames 0 Valid oversize frames
259 1023 byte frames 0 System FCS error frames
72 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames
02-19-2014 04:53 PM
Possibly your NIC is faulty.
I can see ONE-WAY traffic. Switch port is sending data downstream but downstream client is not responding.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: