Source
GjCAtR•

Wait til you see Arista

30
fit4130•

And extreme is the dumb classmate not paying attention while eating paste.

20
Castform5•

Dealing with those daily, kinda have to agree.

3
TedFartass•

Or Huawei

11
tecberth•

Or netgear

4
LuisTechnology•

Or Dell or HP or Most OEM network syntax 😂

3
bobdawonderweasel•

Need a few other vendors copying command sets.

Then again how many ways are there to define an access port VLAN??

16
nolxus•

I always found the HP procurve interesting in that aspect, defining the ports in the vlan, not the vlan in the ports

17
duffil•

Brocade does the same. Frustrating to have to drop out of interface config to configure interface properties.

3
Roger_Amchip•

Procurves are so weird

2
mengelesparrot•

Smoking something weird up in Roseville.

1
macbalance•

I feel like many companies want to (avoiding legal concerns) say their syntax is 'Cisco-like' to make migration easier... Sometimes they're arguably better if they're more consistent which is not a Cisco strength.

3
networkjack•

set vlans v5 vlan-id 5

set interface ge-0/0/0 unit 0 family ethernet-switching vlan members v5

commit

5
techi23•

The thing about Juniper is that, although excessive on the text, almost everything is configurable. Almost.

3
SnoopyTRB•

Man, the Arista guys got so mad when I told them I was glad they implemented ciscos cli structure because HP's was garbage. They very tersely told me it was an "industry standard" cli.

4
darkthought•

I mean, he's not wrong.

3
BWMerlin•

I honestly have no idea why Aruba would want to change their CLI syntax as I find the procurve CLI syntax super easy and intuitive vs Cisco.

3
ex-accrdwgnguy•

I actually like HP's syntax. I have a couple Hp switches i use at home

2