[112469] in North American Network Operators' Group
Re: Documentation of switch maps
daemon@ATHENA.MIT.EDU (Gergely Antal)
Fri Feb 27 02:44:50 2009
Date: Fri, 27 Feb 2009 08:44:27 +0100
From: Gergely Antal <skoal@skoal.name>
To: Blake Pfankuch <bpfankuch@cpgreeley.com>
In-Reply-To: <01759D50DC387C45A018FE1817CE27D7540E0F4395@CPExchange1.cpgreeley.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Reply-To: skoal@skoal.name
Errors-To: nanog-bounces@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7742D425F7DEC8BE9F67E9AD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi
try netdot (https://netdot.uoregon.edu/trac/)
It's a pretty good stuff ,but not easy to setup
Blake Pfankuch wrote:
> Howdy.
>=20
> 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?
>=20
> Thanks, Blake Pfankuch
--------------enig7742D425F7DEC8BE9F67E9AD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkmnmeEACgkQWNIUppUpb3KoywCdG109FLy1mIhisSJOKOwiBybg
CF4AoI1GcrsdZKFme46fSw0IFWutXTdz
=xe8C
-----END PGP SIGNATURE-----
--------------enig7742D425F7DEC8BE9F67E9AD--
