[c-nsp] Interface descriptions - what do you put in?

luismi asturluismi at gmail.com
Mon May 25 13:47:29 EDT 2009


What we do here....

Area Code - Severity - Description

Example:

A - 00 - Gi0/1 FEC12 SW8  BT_Internet

Where...
 A is IP team
 00 is total service disruption if interface is down
 Gi0/1 FEC12 SW8  BT_Internet, remote end of the cable as type of
traffic inside






El vie, 22-05-2009 a las 07:00 +0100, Oliver Gorwits escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> > <petelists at templin.org> wrote:
> >> What do you put into your interface descriptions?  Do you
> >> document circuit ID, far-end equipment/port, near-end
> >> equipment/port, and/or anything else?
> 
> On occasion we add a coded message to tell our monitoring system to
> do something different with that port.
> 
> A simple example - "[DNA]" in the description for "Do Not Alert".
> 
> HTH,
> 
> - --
> Oliver Gorwits, Network and Telecommunications Group,
> Oxford University Computing Services
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFKFj+D2NPq7pwWBt4RAuIyAJoD8TSodxQEG8G+gSZD5YzMmDvqFACgzOSd
> viAYXP1Y2V2YmbLRlcdP9lg=
> =Fex1
> -----END PGP SIGNATURE-----
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list