From: Sam Wilson on
In article <slrngion68.6qq.joliver(a)ns.sdsitehosting.net>,
John Oliver <joliver(a)john-oliver.net> wrote:

> On Tue, 25 Nov 2008 19:46:22 +0000, Sam Wilson wrote:
> > In article <slrngiogof.4jg.joliver(a)ns.sdsitehosting.net>,
> > John Oliver <joliver(a)john-oliver.net> wrote:
> >
> >> In the past week or two, I've hada three or four Gigabit Ethernet
> >> interfaces on about as many 2960s go down and say "err-diabled".
> >> :
> >> :
> >> However, no errors are counted. How can I start to figure out what is
> >> happening and why?
> >
> > Start with "sh errdis ?" and look at the options. I don't have a 2960
> > to hand but the 3550 I just checked offers detect, flap-values and
> > recovery. We have recovery enabled and "sh errdis rec" shows (would
> > show) a list of interfaces that would be reenabled at the next timeout.
> > I don't know what you'll see.
>
> SES-Distribution#sh errdisable recovery
> SES-Distribution#sh errdisable detect
> SES-Distribution#sh errdisable flap-values
> [nothing helpful]

OK, try 'sh int status err-disabled' if your IOS supports that.

Sam
From: Stephen on
On Tue, 25 Nov 2008 19:25:19 +0100 (CET), John Oliver
<joliver(a)john-oliver.net> wrote:

>In the past week or two, I've hada three or four Gigabit Ethernet
>interfaces on about as many 2960s go down and say "err-diabled". One
>doesn't even have anything attached to it!

try the various "sh err-dis" subcommands and it should be able to tell
you what is going on.

you can also set the ports (or entire switch) to auto recover after a
time, and AFAIR for specific types of error.

>
>SES-Distribution#sh int Gi0/4
>GigabitEthernet0/4 is down, line protocol is down (err-disabled)
> Hardware is Gigabit Ethernet, address is 0022.be29.eb04 (bia
>0022.be29.eb04)
> 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)
> 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 1w5d, output 1w5d, output hang never
> Last clearing of "show interface" counters never
> Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops:
>15298
> 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
> 18322903 packets input, 20805679728 bytes, 0 no buffer
> Received 18297621 broadcasts (0 multicasts)
> 0 runts, 0 giants, 0 throttles
> 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
> 0 watchdog, 15121276 multicast, 0 pause input
> 0 input packets with dribble condition detected
> 166633 packets output, 226858846 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
>
>
>However, no errors are counted. How can I start to figure out what is
>happening and why?
--
Regards

stephen_hope(a)xyzworld.com - replace xyz with ntl
From: John Oliver on
On Tue, 25 Nov 2008 20:52:09 +0000, Sam Wilson wrote:
> OK, try 'sh int status err-disabled' if your IOS supports that.

SES-Distribution#sh int status err-disabled

Port Name Status Reason
Err-disabled Vlans
Gi0/4 err-disabled loopback


And, of course, that interface is down again. I'm shutting it and then
no-shutting it. But, apparently, it's just going to go down again.

--
* John Oliver http://www.john-oliver.net/ *
From: News Reader on
John Oliver wrote:
> On Tue, 25 Nov 2008 20:52:09 +0000, Sam Wilson wrote:
>> OK, try 'sh int status err-disabled' if your IOS supports that.
>
> SES-Distribution#sh int status err-disabled
>
> Port Name Status Reason
> Err-disabled Vlans
> Gi0/4 err-disabled loopback
>
>
> And, of course, that interface is down again. I'm shutting it and then
> no-shutting it. But, apparently, it's just going to go down again.
>

Your command output is conveying a reason - "loopback".

A simple Google search (err-disabled loopback) returned the following
link (among others):

http://ciscosystems.com/application/pdf/paws/69980/errdisable_recovery.pdf

Do a simple search within the document for the term "Loopback error" to
find the information desired.

Best Regards,
News Reader
From: Sam Wilson on
In article <4a1Xk.94$Yg.73(a)read2.cgocable.net>,
News Reader <user(a)domain.null> wrote:

> John Oliver wrote:
> > On Tue, 25 Nov 2008 20:52:09 +0000, Sam Wilson wrote:
> >> OK, try 'sh int status err-disabled' if your IOS supports that.
> >
> > SES-Distribution#sh int status err-disabled
> >
> > Port Name Status Reason
> > Err-disabled Vlans
> > Gi0/4 err-disabled loopback
> >
> >
> > And, of course, that interface is down again. I'm shutting it and then
> > no-shutting it. But, apparently, it's just going to go down again.

So check up on the errdisable recovery command(s). BUT...

> Your command output is conveying a reason - "loopback".
>
> A simple Google search (err-disabled loopback) returned the following
> link (among others):
>
> http://ciscosystems.com/application/pdf/paws/69980/errdisable_recovery.pdf
>
> Do a simple search within the document for the term "Loopback error" to
> find the information desired.

.... what he said! Find out what the problem is (you have a loop in your
network somewhere) and fix it and then the port will stop going down.

Sam