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
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
?
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
peteli...@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
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
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.
Hi Pete,
On Fri, May 22, 2009 at 1:07 AM, Pete Templin peteli...@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?
Our L3VPN service provider uses this format on PE-CE
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@puck.nether.net
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@puck.nether.net
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
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 peteli...@templin.org wrote:
List,
What do you put into your interface
11 matches
Mail list logo
