Mailing List Archive: Cisco: NSP

Interface descriptions - what do you put in?

Index | Next | Previous | View Threaded

petelists at templin

May 21, 2009, 8:07 AM

Post #1 of 12 (1119 views)
Permalink

Interface descriptions - what do you put in?

List,

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?

Pete
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

synack at live

May 21, 2009, 9:23 AM

Post #2 of 12 (1082 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

I always try to put "customer name - Circuit ID". I've found ip addressing and bandwidth are too dynamic and become inaccurate over time

Darin Herteen

> Date: Thu, 21 May 2009 10:07:09 -0500
> From: petelists [at] templin
> To: cisco-nsp [at] puck
Send
> Subject: [c-nsp] Interface descriptions - what do you put in?
>
> List,
>
> 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?
>
> Pete
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

_________________________________________________________________
Insert movie times and more without leaving Hotmail®.
http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd1_052009
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

peter at rathlev

May 21, 2009, 11:34 AM

Post #3 of 12 (1083 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

On Thu, 2009-05-21 at 10:07 -0500, Pete Templin 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?

We typically use something like "TGE-trunk-HER.CORE-Te6/1" or
"FE-access-AAR-SNA-KMD-Fa0/0", mentioning local end link hardware and
type, and remote end name and interface.

On interface down/up we extract the description and sends it along with
the alert.

We're an enterprise network though, not service provider. :-)

Regards,
Peter

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

engel.labiro at gmail

May 21, 2009, 9:22 PM

Post #4 of 12 (1071 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

Pete,
for WAN connection we put the Provider name and circuit number,
for LAN connection we put the hostname of the other end and its
interface number.

HTH,
Engel

On Fri, May 22, 2009 at 12:07 AM, Pete Templin <petelists [at] templin> wrote:
> List,
>
> 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?
>
> Pete
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

gregariouspearl at gmail

May 21, 2009, 9:56 PM

Post #5 of 12 (1071 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

Try the following as well.

*** [Client Name] [Media] [Data/Internet] [BW] ***
You can easily judge all the general relvants in "sh int desc" command.

In your core you can use the following:

*** Connected to [BOX] [Port] ***

MSZ

On Fri, May 22, 2009 at 10:22 AM, Engelhard Labiro
<engel.labiro [at] gmail>wrote:

> Pete,
> for WAN connection we put the Provider name and circuit number,
> for LAN connection we put the hostname of the other end and its
> interface number.
>
> HTH,
> Engel
>
> On Fri, May 22, 2009 at 12:07 AM, Pete Templin <petelists [at] templin>
> wrote:
> > List,
> >
> > 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?
> >
> > Pete
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp [at] puck
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

--
"Death is no the greatest loss in life ....
The greatest loss is what dies inside
you while U live...!"
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

oliver.gorwits at oucs

May 21, 2009, 11:00 PM

Post #6 of 12 (1073 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> <petelists [at] templin> 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
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

blahu77 at gmail

May 22, 2009, 1:23 AM

Post #7 of 12 (1071 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

> 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?

I like to have short description that fits 'show int status' so
something like <hostname> and use cdp if I need more info.

Best Regards,

-mat
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

p.mayers at imperial

May 22, 2009, 8:41 AM

Post #8 of 12 (1068 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

On Thu, May 21, 2009 at 04:07:09PM +0100, Pete Templin wrote:
>List,
>
>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?

Far end equipment, though I might reconsider that as LLDP takes hold.

>
>Pete
>_______________________________________________
>cisco-nsp mailing list cisco-nsp [at] puck
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

dale.shaw+cisco-nsp at gmail

May 22, 2009, 5:43 PM

Post #9 of 12 (1067 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

Hi Pete,

On Fri, May 22, 2009 at 1:07 AM, Pete Templin <petelists [at] templin> 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?

Our L3VPN service provider uses this format on PE-CE interfaces:

user1 [at] T3NVB66AW11-RE> show configuration interfaces ge-0/2/4.246
description "By ProJEN SRID#92658 : SLID#74826 : IPVPN (: QOS : #27740
: U4NN T3NV B66AW11 PRX005 : JOEBLOGGSCORP : JBC : WA :
PERTH_33SMITH_63 : PR ): : : XX : : ";

Obviously ":" is used as a delimiter and some fields can be empty.
Most fields map back to billing and provisioning system IDs. Some
fields are customer specific and others link specific. "U4NN" and
"L3NV" are building codes. "B66AW11" is the PE router's hostname
suffix. "PR" is the business unit with the SP that owns the customer.

This only references the L3VPN circuit ID -- the underlying PE-CE
transmission gets a different ID.

I guess this is the other end of the spectrum to "description To
ROUTER4 Fa0/0" :-)

cheers,
Dale
(field values changed to protect the innocent)
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

zivl at gilat

May 24, 2009, 12:47 AM

Post #10 of 12 (1046 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

I think all the others already gave a lot of examples, I can only add one little suggestion.
Omit the "connected to" prefix for a description and save yourself some characters for more important info.
What else can an interface be other than "connected to" something else???? Isn't it obvious?

-----Original Message-----
From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Pete Templin
Sent: Thursday, May 21, 2009 6:07 PM
To: Cisco Nsp
Subject: [c-nsp] Interface descriptions - what do you put in?

List,

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?

Pete
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

asturluismi at gmail

May 25, 2009, 10:47 AM

Post #11 of 12 (1021 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

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> 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
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

asturluismi at gmail

Nov 5, 2009, 4:02 PM

Post #12 of 12 (736 views)
Permalink

Re: Interface descriptions - what do you put in? [In reply to]

Area code - critical value - description - remote port [port-cX]

Area code: [ip|sys|rf] are responsible of the end device
critical value:
00 total service disruption for the customers
01 partial service disruption for the customers - some customers are
working others not or the service is degraded
02 no impact in the customers (ex, pcs or internal desktops)

description: as you prefer
remote port: Gi0/1/12 or G1/12 RFEC1 (RFEC = remote port-channel)

example:

A - 00 - Trunk to stack01 - G1/0/24 RFEC1

it works ok for us

El jue, 21-05-2009 a las 10:07 -0500, Pete Templin escribió:
> List,
>
> 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?
>
> Pete
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads