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 of 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 is using an entire /19 of rfc 1918 ip addresses and has well over 150 switches and 40 active vlans. The want to be able to look at this document and pull up any switch and look at the port and be able to see what vlan the port 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 documentation is lacking on the physical connectivity however their cisco infrastructure does have labels on every port that goes to a named device outside of the DHCP pools. Thoughts? Thanks, Blake Pfankuch

Dear Blake,

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 of 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 is using an entire /19 of rfc 1918 ip addresses and has well over 150 switches and 40 active vlans. The want to be able to look at this document and pull up any switch and look at the port and be able to see what vlan the port 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 documentation is lacking on the physical connectivity however their cisco infrastructure does have labels on every port that goes to a named device outside of the DHCP pools. Thoughts?

I use wiki. 1 page switch: switchname...........10.0.0.20 ----------------- 1 uplink 2 server2 . 24 donwlink 1 page vlans: 102........MYVLAN ------------------------- ip: 10.0.1.0/24 ports: sw1: 1+, 2, 3, 24+ sw2: 1+, 4, 5 + means tagged kind regards, Ingo Flaschberger

Hi try netdot (https://netdot.uoregon.edu/trac/) It's a pretty good stuff ,but not easy to setup Blake Pfankuch wrote:

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 of 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 is using an entire /19 of rfc 1918 ip addresses and has well over 150 switches and 40 active vlans. The want to be able to look at this document and pull up any switch and look at the port and be able to see what vlan the port 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 documentation is lacking on the physical connectivity however their cisco infrastructure does have labels on every port that goes to a named device outside of the DHCP pools. Thoughts?

Thanks, Blake Pfankuch