From: Swan, Jay (jswan@sugf.com)
Date: Thu Dec 13 2007 - 20:16:42 ART
Or you could do "sh int status err" and it'll even tell you why it's
disabled, which is useful if you forgot to look at (or set up) your log.
3560A#sh int status err
Port Name Status Reason
Fa0/3 err-disabled psecure-violation
Jay
#17783
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: Thursday, December 13, 2007 5:38 AM
To: 'nhatphuc'; 'Cisco certification'
Subject: RE: Interface shutdown automatically
Either gremlins or err-disabled. i'll vote for #2.
Your logging messages should be telling you WHY it does that. (use "sh
int
| in errd" to take a look around first!)
Typically I see this when people are setting up their trunks or
etherchannels. And if you aren't doing it fast enough (per the switch's
opinion) you'll start to see things shutdown due to port
inconsistencies.
Cut 'n' paste from notepad makes things go faster!
Or just treat it as expected behavior.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
JNCIE-M
#153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:30 ARST