Discussion:
[rancid] rancid reporting ports in err-disable state
Jon Peatfield
2011-03-29 12:43:27 UTC
Permalink
Yesterday while trying to disagnose a problem with a user not being able
to use one port on a switch I noticed that the port in question had
managed to get into the err-disabled state.

As I'd rather not have to wait for users to complain I've written a
trivial patch to get rancid to run (for Cisco only):

show interfaces status err-disabled

which only generates output if ports are in the err-disabled state, and
lists the reason for each port.

The lines (if any) are added as comments with the prefix SISED as it made
sense at the time.

Anyway I thought that this might possibly be of use to others.

This patch probably won't cleanly apply for others since the diff was
generated after applying a patch to add 'show cdp neighbors detail' to the
list of commands, so if anyone needs a patch against the clean 2.3.6 let
me know...
--
/--------------------------------------------------------------------\
| "Computers are different from telephones. Computers do not ring." |
| -- A. Tanenbaum, "Computer Networks", p. 32 |
---------------------------------------------------------------------|
| Jon Peatfield, _Computer_ Officer, DAMTP, University of Cambridge |
| Mail: ***@damtp.cam.ac.uk Web: http://www.damtp.cam.ac.uk/ |
\--------------------------------------------------------------------/
Loading...