Solved: Switchport going to Error-disable frequently which is connected to Hub - Page 2

sivaalthi85 · ‎04-24-2012

Hi Friends,

One of our swtich is frequently going to error-disable.

That switch port is connected to a hub and to that two PCs are connected.

Can you please suggest what is the problem and how to solve it.

Switch#sh interfaces gigabitEthernet 0/13

GigabitEthernet0/13 is down, line protocol is down (err-disabled)

Hardware is Gigabit Ethernet, address is 503d.e508.4b0d (bia 503d.e508.4b0d)

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Auto-duplex, Auto-speed, 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 20:09:59, 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

1244435 packets input, 198757270 bytes, 0 no buffer

Received 4177 broadcasts (252 multicasts)

0 runts, 0 giants, 0 throttles

5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 252 multicast, 0 pause input

0 input packets with dribble condition detected

2293998 packets output, 2192224484 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

Configuration for that particular port

interface GigabitEthernet0/13

switchport access vlan 43

storm-control broadcast level 20.00

storm-control multicast level 20.00

please Help.

fb_webuser · ‎04-24-2012

Check if err-disable for storm-control is enabled by doing the following:

NJ-SW#sh errdisable recovery | i storm-control

storm-control Enabled

-

If the output is ENABLED as shown above, please run the following command in config mode:

NJ-SW(config)#no errdisable recovery cause storm-control

and hit enter!!!!!!

---

Posted by WebUser Neeraj Jagga from Cisco Support Community App

fb_webuser · ‎04-24-2012

please run this command in config mode in addtion to my earlier post:

NJ-SW(config)#no errdisable detect cause all

---

Posted by WebUser Neeraj Jagga from Cisco Support Community App

sivaalthi85 · ‎04-24-2012

Hi Web,

Switch#show errdisable recovery | i storm-control
storm-control Enabled
Switch(config)#no errdisable recovery cause storm-control
Switch(config)#no errdisable detect cause all
Switch(config)#exit

Just given commands as you suggested

fb_webuser · ‎04-24-2012

After running the commands, please update if the err disable problem is solved....

---

Posted by WebUser Neeraj Jagga from Cisco Support Community App

burleyman · ‎04-24-2012

I see you said you set the PC's to full duplex, that is incorrect, they need to be hard set to half duplex, hubs only work in half duplex. Also on the port that the hub connects to on the switch you need to also hard code that to half duplex NOT auto. This causes duplex mismatching and will cause the port to erro-disable.

Mike

sivaalthi85 · ‎04-25-2012

Hi Burleyman,

I will try what you have suggested and I ll reply soon.

Thank you so much for ur time..!!!!

sivaalthi85 · ‎04-25-2012

Hi Web Still the problem is not solved.

Please help

spanning-tree mode pvst

spanning-tree etherchannel guard misconfig

spanning-tree extend system-id

!

no errdisable detect cause small-frame

no errdisable detect cause loopback

no errdisable detect cause gbic-invalid

no errdisable detect cause sfp-config-mismatch

no errdisable detect cause pagp-flap

no errdisable detect cause dtp-flap

no errdisable detect cause link-flap

no errdisable detect cause l2ptguard

no errdisable detect cause pppoe-ia-rate-limit

no errdisable detect cause dhcp-rate-limit

no errdisable detect cause arp-inspection

errdisable recovery cause udld

errdisable recovery cause bpduguard

errdisable recovery cause security-violation

errdisable recovery cause channel-misconfig (STP)

errdisable recovery cause pagp-flap

errdisable recovery cause dtp-flap

errdisable recovery cause link-flap

errdisable recovery cause sfp-config-mismatch

errdisable recovery cause gbic-invalid

errdisable recovery cause l2ptguard

errdisable recovery cause psecure-violation

errdisable recovery cause port-mode-failure

errdisable recovery cause dhcp-rate-limit

errdisable recovery cause pppoe-ia-rate-limit

errdisable recovery cause mac-limit

errdisable recovery cause vmps

errdisable recovery cause inline-power

errdisable recovery cause arp-inspection

errdisable recovery cause loopback

errdisable recovery cause small-frame

Leo Laohoo · ‎04-24-2012

Something is not right here.

If the interface goes into error-disable then the first question I'd be asking is WHY. To know WHY the port(s) went into error-disable then use the command "sh interface status error".

Next, if the reason is "link flap" (or something in that vicinity) then I'd consider running a TDR.

Palaniswamy P · ‎04-24-2012

Hi Siva,

try to do this things:

1) clear the counter of interface gi0/13.

2) set the speed and duplex w.r.t hub

3)observe the ouputs of " show interface" (multiple time) .

4) After that if port not stabilizes then try to remove the pc one by one.

Regards,

Palani

sivaalthi85 · ‎04-25-2012

Hi This morning output,

Apr 25 08:21:33.546: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:21:35.560: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:21:39.427: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:21:43.495: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:21:46.733: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:21:48.746: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:22:00.675: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:22:02.688: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:22:26.403: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:22:28.416: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:23:29.787: DHCPD: checking for expired leases.

Apr 25 08:24:07.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:24:09.096: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:25:29.795: DHCPD: checking for expired leases.

Apr 25 08:26:52.037: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:26:54.050: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:27:29.802: DHCPD: checking for expired leases.

Apr 25 08:27:50.514: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:27:52.527: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:28:05.890: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:28:06.896: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to down

Apr 25 08:28:11.267: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to up

Apr 25 08:28:11.267: DHCPD: interface GigabitEthernet0/13 coming up

Apr 25 08:28:12.274: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:29:29.809: DHCPD: checking for expired leases.

Apr 25 08:29:35.254: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:29:37.267: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:29:44.137: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:29:46.150: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:31:28.651: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:31:29.817: DHCPD: checking for expired leases.

Apr 25 08:31:30.673: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:31:33.072: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:31:35.077: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:31:39.942: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:31:41.955: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:31:52.189: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:31:54.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 25 08:33:09.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 25 08:33:11.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Harca_Teviot_Core#

mohseen patel · ‎04-25-2012

Hi sivaalthi,

Can please tell the model number of switch and hub.

Br.

Mohseen

sivaalthi85 · ‎04-25-2012

HI Mohseen,

Its a layer 3 cisco switch and full duplex hub.

Leo Laohoo · ‎04-25-2012

Its a layer 3 cisco switch and full duplex hub.

C'mon here. Mohseen asked a very legitimate question. Please answer appropriately.

I have the strange feeling this is a layer 1 issue. One way of checking is TDR.

sivaalthi85 · ‎04-25-2012

Hi,

Sorry Its 3560

* 1 30 WS-C3560X-24P 12.2(53)SE2 C3560E-UNIVERSALK9-M

Leo Laohoo · ‎04-25-2012

Ok. That's good. 3560X supports TDR.

1. Command: test cabl TDR int gig 0/13;

2. Wait between 5 to 7 seconds;

3. Command: sh cable TDR int gig 0/13;

4. Please post the output.

Sent from Cisco Technical Support iPad App