From: ccie2be (ccie2be@nyc.rr.com)
Date: Thu Jul 08 2004 - 18:40:13 GMT-3
Hey Ken et al,
The errdisable recovery command lets you specify how long the interface
stays in the errdisable state. The idea is that sometimes the problem is
transitory eg. someone tries to access a secure port where their mac address
isn't allowed. Depending on how you've configured the port, the port may
transition into the err-disable state but you may want it to transition out
of err-disable state all by itself without requiring any intervention on
your part.
That said, for most causes of errdisable, if the port transitioned out of
the errdisable state after a bit, it wouldn't do any good unless the root
cause of the problem had been fixed. If the root cause hasn't been fixed,
then shortly after leaving the errdisable state, the root problem would
cause the port to re-transition back into errdisable state. So, no net gain
would be achieved.
If you look in the CR for the 3550 under errdisable recovery, you'll see the
last parameter is interval. This is very easy to miss given the massive
amount of other info there, but that's the key to understanding this
command.
<snip>
Specify the time to recover from the specified error-disable state. The
range is 30 to 86400 seconds. The same interval is applied to all causes.
The default interval is 300 seconds.
<snip>
I think it's possible to specify the interval on a per cause basis, but my
brain can't retain that much detail info for that long. So, I don't remeber
if the above statement is always true or just true when a specific cause
isn't specified.
HTH
PS: Have you been following the thread re: tunnels & recursive routing? If
so, maybe you could give me an example of this recursive problem so I can
recongize it and know what to look out for. I understand it conceptually,
but can't figure out how the tunnel & ip addressing would be configured to
cause this problem, so an example would be really helpful.
----- Original Message -----
From: "Kenneth Wygand" <KWygand@customonline.com>
To: "ccie2be" <ccie2be@nyc.rr.com>; "Scott Morris" <swm@emanon.com>;
<tycampbell@comcast.net>; <ccielab@groupstudy.com>
Sent: Thursday, July 08, 2004 4:27 PM
Subject: RE: udld on 3550
Tim,
This is what I was able to find, which confuses me a bit - what is the
difference between "errdisable detect cause" (which is enabled by
default) and "errdisable recovery" (which is disabled by default)?
<SNIP>
"ERRDISABLE DETECT CAUSE" command
---------------------------------
errdisable detect cause
Use the errdisable detect cause global configuration command to enable
error disable detection for a specific cause or all causes. Use the no
form of this command to disable the error disable detection feature.
Defaults
Detection is enabled for all causes.
"ERRDISABLE RECOVERY" command
---------------------------------
errdisable recovery
Use the errdisable recovery global configuration command to configure
the recover mechanism variables. Use the no form of this command to
return to the default setting.
Defaults
Recovery is disabled for all causes.
The default recovery interval is 300 seconds.
</SNIP>
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"The only unattainable goal is the one not attempted."
-Anonymous
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Thursday, July 08, 2004 4:09 PM
To: Scott Morris; tycampbell@comcast.net; ccielab@groupstudy.com
Subject: Re: udld on 3550
Unless I'm mistaken ( which happens often), all causes (there are about
a
dozen or so) of err-disabled are enabled by default.
Isn't that right?
----- Original Message -----
From: "Scott Morris" <swm@emanon.com>
To: <tycampbell@comcast.net>; <ccielab@groupstudy.com>
Sent: Thursday, July 08, 2004 2:05 PM
Subject: RE: udld on 3550
> You may also want to add "errdisable recovery cause udld" to actually
enact
> it. The interval is simply the timer.
>
>
> Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP,
> JNCIP, et al.
> IPExpert CCIE Program Manager
> IPExpert Sr. Technical Instructor
> swm@emanon.com/smorris@ipexpert.net
> http://www.ipexpert.net
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> tycampbell@comcast.net
> Sent: Thursday, July 08, 2004 8:47 AM
> To: ccielab@groupstudy.com
> Subject: udld on 3550
>
> I have a task that specifies that both switches should be able to
determine
> whether a physical link defect prohibits bidirectional
communication...
>
> ok..this is udld
>
> but after that, it says that they should be able to automatically
recover
> after an hour....
>
> would this be "errdisable recovery interval 3600" ?
>
> just want to make sure....
>
>
> Thanks!
>
>
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:50 GMT-3