Man.. I'd love to have this for Netgear switches! :)
> -----Original Message-----
> From: Bielawa, Daniel W. (NS) [mailto:dwbiel...@liberty.edu]
> Sent: Thursday, February 26, 2009 2:07 PM
> To: nanog@nanog.org
> Subject: RE: Documentation of switch maps
>
> 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:bpfank...@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
>
>
> --
> This message has been scanned for viruses and
> dangerous content by N2Net Mailshield, and is
> believed to be clean.
