Sumit, did you see the attachment that I have sent. Can you explain what does actually mean by "conditionally"
On Wed, May 12, 2010 at 12:49 PM, Sumit Mahla <[email protected]>wrote: > Yes kings........... > > Untill the recovery cause is mentioned it will not recover... it you only > mention the recovery cause... then it default time is 120 seconds.... > > you can change the recovery time but it will only come in effect when you > configure the cause... > > > > > ------------------------------ > Date: Wed, 12 May 2010 11:14:39 +0530 > From: [email protected] > To: [email protected] > Subject: [OSL | CCIE_Security] errdisable recovery > > > Hi all > > With this O/P, will bpduguard recover in 120 seconds automatically. Do we > need "errdisable recovery cause bpduguard"? > I have attached the task from Yusuf's practice lab. > > I am posting this query regarding the task. > > > SW#sh errdisable recovery > ErrDisable Reason Timer Status > ----------------- -------------- > arp-inspection Disabled > bpduguard Disabled > channel-misconfig Disabled > dhcp-rate-limit Disabled > dtp-flap Disabled > gbic-invalid Disabled > l2ptguard Disabled > link-flap Disabled > mac-limit Disabled > link-monitor-failure Disabled > loopback Disabled > oam-remote-failure Disabled > pagp-flap Disabled > port-mode-failure Disabled > psecure-violation Disabled > security-violation Disabled > sfp-config-mismatch Disabled > storm-control Disabled > udld Disabled > unicast-flood Disabled > vmps Disabled > > Timer interval: 120 seconds > Interfaces that will be enabled at the next timeout: > > > > > > With regards > Kings > > ------------------------------ > The latest auto launches and test drives Drag n' > drop<http://autos.in.msn.com/> > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
