[127479] in North American Network Operators' Group
RE: Advice regarding Cisco/Juniper/HP
daemon@ATHENA.MIT.EDU (George Bonser)
Wed Jun 30 18:33:21 2010
Date: Wed, 30 Jun 2010 15:32:43 -0700
In-Reply-To: <0C63EADB-39D9-474B-914F-0FC2C7EC4C4E@oicr.on.ca>
From: "George Bonser" <gbonser@seven.com>
To: "Greg Whynott" <Greg.Whynott@oicr.on.ca>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> -----Original Message-----
> From: Greg Whynott
> Sent: Wednesday, June 30, 2010 9:18 AM
> To: George Bonser
> Cc: Colin Alston; nanog@nanog.org
> Subject: Re: Advice regarding Cisco/Juniper/HP
>=20
> or become familiar with some basic commands, which is after all, our
> job... on hp: show port vlan e1, which will show you all the vlans
> port E1 is a member of..
True if you happen to be logged on to the device. What I had in mind
was reading config files which is an exercise I happen to have been
doing recently. I can look at the config file for a Cisco unit and
determine easily which ports are in which vlans by looking at the port
config. Some other vendors I must parse the vlan config for port
numbers.
So yeah, on a Brocade unit one can do sho vlan <interface> if you are
logged on to it and other vendors have their way. It isn't that big of
an issue but if I could have a perfect world, I would rather specify
vlans per interface than interfaces per vlan.
G
