From: Tarun Pahuja (pahujat@gmail.com)
Date: Mon Nov 05 2007 - 13:34:46 ART
Slevin,
There are various reasons for the interface to go into
errdisable.
Duplex mismatch
Port channel misconfiguration
BPDU guard violation
UniDirectional Link Detection (UDLD) condition
Late-collision detection
Link-flap detection
Security violation
Port Aggregation Protocol (PAgP) flap
Layer 2 Tunneling Protocol (L2TP) guard
DHCP snooping rate-limit
Incorrect GBIC / Small Form-Factor Pluggable (SFP) module or cable
Address Resolution Protocol (ARP) inspection
Inline power
Error-disable detection is enabled for all of these reasons by default. In
order to disable error-disable detection, use the no errdisable detect cause
command.
HTH,
Tarun
On 10/29/07, slevin kremera <slevin.kremera@gmail.com> wrote:
>
> Hi Experts
>
> Lets say in a switch there are few ports (port fa0/5 and port 0/6) part of
> some vlan 20 and to these ports i add the switchport host
> command.Inaddition to these there is another port (fa0/16) to which is
> connected some
> router and that is made an access port using the usual cli..switchport
> mode
> access and sw access vlan 10.Now if i have to prevent the host ports from
> getting into err-disable mode... so wud it be correct if i get into fa0/5
> and fa0/6 and config span-tree bpduguard enable or do i have to do it on
> fa0/16 too?
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:28 ART