[112450] in North American Network Operators' Group
RE: Documentation of switch maps
daemon@ATHENA.MIT.EDU (Bielawa, Daniel W. (NS))
Thu Feb 26 14:07:12 2009
From: "Bielawa, Daniel W. (NS)" <dwbielawa@liberty.edu>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Thu, 26 Feb 2009 14:06:58 -0500
In-Reply-To: <01759D50DC387C45A018FE1817CE27D7540E0F4395@CPExchange1.cpgreeley.com>
Errors-To: nanog-bounces@nanog.org
Hello,
We use switchmap here for tracking port utilization, days inactive,=
and devices connected. It uses SNMP to determine the information.
http://switchmap.sourceforge.net/
Thank You
Daniel Bielawa
Network Engineer
Liberty University Information Services
-----Original Message-----
From: Blake Pfankuch [mailto:bpfankuch@cpgreeley.com]
Sent: Thursday, February 26, 2009 2:01 PM
To: nanog@nanog.org
Subject: Documentation of switch maps
Howdy.
Had a customer come to me this morning who wanted to create a document for =
their switching infrastructure and thought I would bounce it off the rest o=
f the world on how you usually do this. Typically I use a spreadsheet with=
outlines to define the "switch" and then outlines for the ports and color =
coding for vlan's as well as a description of the port. Curious what other=
people are doing, as this would be a huge undertaking for a customer who i=
s using an entire /19 of rfc 1918 ip addresses and has well over 150 switch=
es and 40 active vlans. The want to be able to look at this document and p=
ull up any switch and look at the port and be able to see what vlan the por=
t is on, as well as what device it is connected to as well as port channel =
membership, trunks and other fun things like that. Needless to say their d=
ocumentation is lacking on the physical connectivity however their cisco in=
frastructure does have labels on every port that goes to a named device out=
side of the DHCP pools. Thoughts?
Thanks,
Blake Pfankuch
