A few days ago, a switch cascade using a Cisco 2950 switch and a 100MB port of Tp-link 24 ports. Causes the Cascade ports on the Cisco 2950 device to be in use one day later, the next morning when the port shows err-disabled. The network is not working. How to deal with?
To view the interface status:
GX-SW-2950-01#SH Interfaces F0/2
FASTETHERNET0/2 is off, line protocol was down (err-disabled)
Hardware is Fast Ethernet, address is 0011.bb48.d4c2 (BIA 0011.bb48.d4c2)
MTU bytes, BW 100000 Kbit, DLY usec,
Reliability 254/255, Txload 1/255, Rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive Set (SEC)
Auto-duplex, Auto-speed, media type is 100BaseTX
Input Flow-control is unsupported output Flow-control is unsupported
ARP Type:arpa, ARP Timeout 04:00:00
Last input 12:08:35, output 12:08:35, 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 0 bits/sec, 0 packets/sec
7828496 packets Input, 3836732423 bytes, 0 no buffer
Received 153627 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
2 input errors, 1 CRC, 1 frame, 0 overrun, 0 ignored
0 watchdog, 89124 multicast, 0 pause input
0 input packets with dribble condition detected
7809493 packets output, 2721732114 bytes, 0 underruns
0 output errors, 0 collisions, 2 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
Only 2 input errors, 1 CRC, 1 frame,2 interface resets. The reason is not enough to cause the interface to enter the err-disabled state.
There is no way to configure err-disabled only. Enable the recovery feature. The command is as follows:
gx-sw-2950-01 (config) #errdisable recovery interval 30
gx-sw-2950-01 (config) #errdisable recovery cause all
After a few days of testing, can be used normally. The unfortunate thing, did not figure out why into the err-disabled state. There are a number of possible reasons. But I don't know which one. The following are some possible causes that Cisco provides by default:
Gx-sw-2950-01#show errdisable Detect
ErrDisable Reason Detection Status
----------------- ----------------
UDLD Enabled
Bpduguard Enabled
Security-violatio Enabled
Channel-misconfig Enabled
Psecure-violation Enabled
Dhcp-rate-limit Enabled
Unicast-flood Enabled
Vmps Enabled
Pagp-flap Enabled
Dtp-flap Enabled
Link-flap Enabled
Gbic-invalid Enabled
Loopback Enabled
Dhcp-rate-limit Enabled
Unicast-flood Enabled
You can actually test each one individually. To find out the real reason, but there are 15 possibilities. Think about it or forget it.
Cisco 2,950 Cascade Tp-link, ports are always err-disabled. Causes the network to be not through, how to deal with?