Switchport going to Error-disable frequently which is connected to Hub

Answered Question
Apr 24th, 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.

I have this problem too.
0 votes
Correct Answer by Leo Laohoo about 1 year 11 months ago

Hmmm ... Do you see the result?

Shut/no shut the interface again and run the same commands. Make sure you wait for approximately 5 to 7 seconds.

If this is the same output then you MAY have a faulty cable.

Sent from Cisco Technical Support iPad App

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (4 ratings)
sivaalthi85 Tue, 04/24/2012 - 05:30

I Have issued no shoutdown command and the port came up but afte sometime its again going to errordisable.

Please help.

dancicioiu Tue, 04/24/2012 - 05:53

Hi Siva,

You might have errdisable-recovery configured on the equipment, that's why the port got up without any manual action. Also you might have configure "storm-control action shutdown" which is one of the reasons that this is happening.

Dan

sivaalthi85 Tue, 04/24/2012 - 06:46

Hi Palani,

Below is the output of show logging on switch

pr 24 14:43:25.971:  DHCPD: address 10.127.43.104 mask 255.255.255.0

Apr 24 14:43:25.971:  DHCPD: reason flags: timeout 3.108

Apr 24 14:43:25.971:   DHCPD: htype 1 chaddr 000f.fe1c.bcc2

Apr 24 14:43:25.971:   DHCPD: out_vlan_id 0

Apr 24 14:43:25.971: DHCPD: returned 10.127.43.104 to address pool Teviot_Comm_Vlan.

Apr 24 14:43:25.971: DHCPD: the lease for address 10.127.43.107 has expired.

Apr 24 14:43:25.971: DHCPD: Sending notification of TERMINATION:

Apr 24 14:43:25.971:  DHCPD: address 10.127.43.107 mask 255.255.255.0

Apr 24 14:43:25.979:  DHCPD: reason flags: timeout e.5906.79

Apr 24 14:43:25.979:   DHCPD: htype 1 chaddr 000f.fe1c.bd42

Apr 24 14:43:25.979:   DHCPD: out_vlan_id 0

Apr 24 14:43:25.979: DHCPD: returned 10.127.43.107 to address pool Teviot_Comm_Vlan.

Apr 24 14:43:25.979: DHCPD: the lease for address 10.127.43.101 has expired.

Apr 24 14:43:25.979: DHCPD: Sending notification of TERMINATION:

Apr 24 14:43:25.979:  DHCPD: address 10.127.43.101 mask 255.255.255.0

Apr 24 14:43:25.979:  DHCPD: reason flags: timeout 3.110

Apr 24 14:43:25.979:   DHCPD: htype 1 chaddr 000f.fe1c.c10a

Apr 24 14:43:25.979:   DHCPD: out_vlan_id 0

Apr 24 14:43:25.979: DHCPD: returned 10.127.43.101 to address pool Teviot_Comm_Vlan.

Apr 24 14:43:25.979: DHCPD: the lease for address 10.127.43.109 has expired.

Apr 24 14:43:25.979: DHCPD: Sending notification of TERMINATION:

Apr 24 14:43:25.979:  DHCPD: address 10.127.43.109 mask 255.255.255.0

Apr 24 14:43:25.979:  DHCPD: reason flags: timeout 3.108

Apr 24 14:43:25.979:   DHCPD: htype 1 chaddr 000f.fe1c.c91e

Apr 24 14:43:25.979:   DHCPD: out_vlan_id 0

Apr 24 14:43:25.979: DHCPD: returned 10.127.43.109 to address pool Teviot_Comm_Vlan.

Apr 24 14:43:26.390: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:43:29.410: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:43:31.423: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:43:32.967: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:43:33.973: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to down

Apr 24 14:43:38.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:43:40.676: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:43:46.296: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:43:48.402: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:43:50.709: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to up

Apr 24 14:43:50.709: DHCPD: interface GigabitEthernet0/13 coming up

Apr 24 14:43:51.715: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:43:55.515: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

sivaalthi85 Tue, 04/24/2012 - 06:34

Hi Dan,

No its not coming up automatically. All the time I'm logging into switch and issuing Shutdown and No shutdown command.

then  it coming up for sometime and again its going to error-disable.

There is no Strom control coomand given to the switch.

Before it was configured with portfast and BPDU gaurd but I have deleted it because

Spantree port fast start should only be enabled on ports connected

to a single host. Connecting hubs, concentrators, switches, bridges, etc. to

a fast start port can cause temporary spanning tree loops.

Regrads,

Siva

Ivan Krimmel Tue, 04/24/2012 - 06:38

Hey Siva,

it looks like time to time storm-control thresholds are being crossed over. Anyway, if you'd like the port to come up automatically, you can go for the global config command:

errdisable recovery cause

HTH,

Ivan.

sivaalthi85 Tue, 04/24/2012 - 06:49

Hi Ivan,

I have enable but still the port is flatuating.

24 14:46:03.643: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:46:08.097: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:46:10.874: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:46:12.879: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:46:19.682: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:46:21.695: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:46:23.490: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:46:28.465: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:46:35.763: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:46:43.480: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:46:50.787: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:46:55.736: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:46:57.045: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:46:59.058: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:02.179: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:04.192: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:06.440: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:08.453: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:11.557: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:13.570: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:17.144: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:23.343: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:24.929: %SYS-5-CONFIG_I: Configured from console by vty0 (192.168.18.27)

Apr 24 14:47:25.994: DHCPD: checking for expired leases.

Apr 24 14:47:26.992: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:26.992: DHCPD: interface GigabitEthernet0/13 coming up

Apr 24 14:47:27.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:33.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:37.268: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:46.328: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:48.333: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:50.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:51.260: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:53.265: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:53.265: DHCPD: interface GigabitEthernet0/13 coming up

Apr 24 14:47:54.280: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:47:56.134: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:47:59.884: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to down

Apr 24 14:48:06.570: %LINK-3-UPDOWN: Interface GigabitEthernet0/13, changed state to up

Apr 24 14:48:06.570: DHCPD: interface GigabitEthernet0/13 coming up

Ivan Krimmel Tue, 04/24/2012 - 06:57

Thanks Siva,

it is good that we have logs now, it is clear that storm-control is not a culprit here, otherwise it would have shown that is has kicked in. It could be a hardware issue on that specific port, but let's check what is connected to this port on the other end and what do we have in the logs there. To avoid hardware issue you could use a spare port on this switch instead of port gige0/13.

Awaiting your update!

sivaalthi85 Tue, 04/24/2012 - 07:15

Hi Ivan,

An hub is connected to this port and to that Hub two Pcs corrected.

If I connect the cable to other port on the switch same thing is going on.

basically two pcs connected to hub and from hub their a cable connected to Switchport 13

Ivan Krimmel Tue, 04/24/2012 - 07:27

That's interesting Siva, thanks. I'd try these things(the order does not matter):

1) try to unplug one pc and see whether it will rectify the situation;

2) while the port is up, collect 'sh interface' output

3) run wireshark on one of the pc's - this will give you an idea what is going on in the wires;

4) try to play with duplex, for a hub it should be set to half;

5) remove storm-control knobs off the switch - I still suspect kind of storm due to a hub being connected;

Let me know how is it going.

sivaalthi85 Tue, 04/24/2012 - 07:40

HI Ivan,

Thank you so much for your time, I really appreciate.

I have couple of doubts on the steps you have suggested above. can you please breifly explain to me.

4) try to play with duplex, for a hub it should be set to half;

how to set half duplex on hub, its a 100mb hub and the port on switch is auto negogiate and the pcs connected to the hubs were auto nego but this morning i changed to full duplex but still problem is not solved.

5) remove storm-control knobs off the switch - I still suspect kind of storm due to a hub being connected;

I have no idea about the storm-control knobs . could you please explain. how to remove what is it actually used for

Thanks,

siva

Ivan Krimmel Tue, 04/24/2012 - 07:43

Siva,

my pleasure!

4) I meant to hardcode it on the switch. Though autoneg is a good thing, it maybe wise to manually code it, at least to try;

5) you have those in the config :

storm-control broadcast level 20.00

storm-control multicast level 20.00

gotcha?

Regards,

Ivan.

sivaalthi85 Tue, 04/24/2012 - 08:04

Hi Ivan,

I'm pasting configuration for couple of ports below.

interface GigabitEthernet0/12

switchport access vlan 43

storm-control broadcast level 20.00

storm-control multicast level 20.00

spanning-tree portfast

spanning-tree bpduguard enable

!

interface GigabitEthernet0/13

switchport access vlan 43

storm-control broadcast level 20.00

storm-control multicast level 20.00

!

interface GigabitEthernet0/14

switchport access vlan 43

storm-control broadcast level 20.00

storm-control multicast level 20.00

spanning-tree portfast

spanning-tree bpduguard enable

!

interface GigabitEthernet0/15

switchport access vlan 43

storm-control broadcast level 20.00

storm-control multicast level 20.00

spanning-tree portfast

spanning-tree bpduguard enable

!

interface GigabitEthernet0/16

switchport access vlan 43

storm-control broadcast level 20.00

storm-control multicast level 20.00

spanning-tree portfast

spanning-tree bpduguard enable

sivaalthi85 Tue, 04/24/2012 - 07:17

Apr 24 14:50:39.234: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:50:42.531: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:50:51.490: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:50:53.000: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:50:55.013: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:50:57.362: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:01.682: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:06.220: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:08.233: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:11.178: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:20.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:23.626: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:25.640: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:26.009: DHCPD: checking for expired leases.

Apr 24 14:51:28.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:30.136: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:32.250: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:36.805: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:40.664: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:44.875: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:46.259: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:48.272: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:51:51.082: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 14:51:55.151: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 14:53:26.016: DHCPD: checking for expired leases.

Apr 24 14:55:26.024: DHCPD: checking for expired leases.

Apr 24 14:57:26.031: DHCPD: checking for expired leases.

Apr 24 14:59:26.038: DHCPD: checking for expired leases.

Apr 24 15:01:26.046: DHCPD: checking for expired leases.

Apr 24 15:01:33.252: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/8, changed state to down

Apr 24 15:01:34.250: %LINK-3-UPDOWN: Interface GigabitEthernet0/8, changed state to down

Apr 24 15:01:36.624: %LINK-3-UPDOWN: Interface GigabitEthernet0/8, changed state to up

Apr 24 15:01:36.624: DHCPD: interface GigabitEthernet0/8 coming up

Apr 24 15:01:37.630: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/8, changed state to up

Apr 24 15:03:26.053: DHCPD: checking for expired leases.

Apr 24 15:05:26.061: DHCPD: checking for expired leases.

Apr 24 15:07:21.882: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to down

Apr 24 15:07:23.895: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/13, changed state to up

Apr 24 15:07:26.068: DHCPD: checking for expired leases.

Apr 24 15:09:26.076: DHCPD: checking for expired leases.

Apr 24 15:11:26.083: DHCPD: checking for expired leases.

Apr 24 15:13:26.090: DHCPD: checking for expired leases.

Apr 24 15:15:26.098: DHCPD: checking for expired leases.

Switch# show clock

15:16:08.829 UTC Tue Apr 24 2012

fb_webuser Tue, 04/24/2012 - 08:09

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

sivaalthi85 Tue, 04/24/2012 - 08:22

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

burleyman Tue, 04/24/2012 - 13:30

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 Wed, 04/25/2012 - 00:36

Hi Burleyman,

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

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

sivaalthi85 Wed, 04/25/2012 - 00:33

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 Tue, 04/24/2012 - 18:18

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

palani.swamy Tue, 04/24/2012 - 22:51

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 Wed, 04/25/2012 - 00:35

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 Wed, 04/25/2012 - 01:54

Hi sivaalthi,

Can  please tell the model number of switch and hub.

Br.

Mohseen


Leo Laohoo Wed, 04/25/2012 - 03:12
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 Wed, 04/25/2012 - 03:24

Hi,

Sorry Its 3560

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

Leo Laohoo Wed, 04/25/2012 - 03:42

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

sivaalthi85 Wed, 04/25/2012 - 03:48

HI Leolaohoo,

Interface Speed Local pair Pair length        Remote pair Pair status

--------- ----- ---------- ------------------ ----------- --------------------

Gi0/13    100M  Pair A     N/A                N/A         Not Completed

                Pair B     N/A                N/A         Not Completed

                Pair C     N/A                N/A         Not Completed

                Pair D     N/A                N/A         Not Completed

Above is the output

Thanks

Correct Answer
Leo Laohoo Wed, 04/25/2012 - 03:56

Hmmm ... Do you see the result?

Shut/no shut the interface again and run the same commands. Make sure you wait for approximately 5 to 7 seconds.

If this is the same output then you MAY have a faulty cable.

Sent from Cisco Technical Support iPad App

Actions

Login or Register to take actions

This Discussion

Posted April 24, 2012 at 5:27 AM
Stats:
Replies:31 Avg. Rating:5
Views:3797 Votes:0
Shares:0
Tags: switch, error
+

Related Content

Discussions Leaderboard