[127472] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Advice regarding Cisco/Juniper/HP

daemon@ATHENA.MIT.EDU (Greg Whynott)
Wed Jun 30 12:18:39 2010

From: Greg Whynott <Greg.Whynott@oicr.on.ca>
To: George Bonser <gbonser@seven.com>
Date: Wed, 30 Jun 2010 12:18:24 -0400
In-Reply-To: <5A6D953473350C4B9995546AFE9939EE09EA4EFC@RWC-EX1.corp.seven.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Jun 30, 2010, at 12:07 PM, George Bonser wrote:
>  if I want to
> know which vlans a port is in, you look at the port config and there it
> is.  Other gear you need to look through each vlan configuration and
> note which vlans the port appears in and hope you don't overlook one.

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..=20

I like cisco,  but i think the HP way is more logical and less prone to err=
or.  A previous poster gave an excelent example,  i burnt myself not adding=
 the "add" to a trunk config on our cisco switches.   i went over the magic=
al number (and I've no idea why you need to use another argument when you p=
ass some threshold,  it seems redundant and silly) of vlans and took out ab=
out 7 departments till I realized what I had done.   thankfully you only ne=
ed to do this once to learn.=20

the trunking is more logical on HP config wise too,   there is a line in th=
e config which shows all the members and trunk type,  on one line.  =20

not being able to issue commands while in config mode (without the 'do') is=
 annoying as hell too..  its like not being able to do anything on a unix b=
ox while you are root without being asked "are you sure" every time you hit=
 carriage return.
=20
the biggest think I don't like about the HP CLI is the lack of regx or the =
ablitly to string a few together on one line.  some models have it,  others=
 don''t.   that woudl be the second issue,  the lack of consistency between=
 devices.  cisco owns that one.




-g






home help back first fref pref prev next nref lref last post