Why?

Maybe I missed it but...

SVI = vlan interface

BVI - bridged group interface

But oh no, an etherchannel's port interface is called.....port interface!!

Why not PVI?

Right right?

Find more posts tagged with

Save $250 on 2025 certification boot camps from Infosec!

Book now with code EOY2025

Button

Comments

Cyanic

It's all semantics, don't sweat it.

notgoing2fail

Cyanic wrote: »

It's all semantics, don't sweat it.

lol yes I know, but my OCD kinda kicks in. Why wouldn't they want to refer it to as PVI? I don't think there's a PVI at all is there?

Cyanic

Man, there are so many inconsistencies with Cisco, and others as well. I think it is done to keep us tech types on our feet and non-tech types away.

I love commands like

sh mac address-table
sh mac-address-table
sh cam

Why do they have to change it? I don't know but you might as well get use to it, lol.

notgoing2fail

Cyanic wrote: »

Man, there are so many inconsistencies with Cisco, and others as well. I think it is done to keep us tech types on our feet and non-tech types away.

I love commands like

sh mac address-table
sh mac-address-table
sh cam

Why do they have to change it? I don't know but you might as well get use to it, lol.

Is that right? I'll have to check those commands out, that would be horrible.

There's also a typo in the IP DHCP Snooping command in earlier versions of IOS. I think they fixed it now though...

With everything I'm studying for, they really don't need to add fuel to the fire!!

4E6564

show cam: Cat
show mac add or mac-add are all over the place....

Very annoying bouncing around the network looking for a MAC, and for each layer 2 hop having to check if it is "mac add" or "mac-add"

ColbyG

Cyanic wrote: »

Man, there are so many inconsistencies with Cisco, and others as well. I think it is done to keep us tech types on our feet and non-tech types away.

I love commands like

sh mac address-table
sh mac-address-table
sh cam

Why do they have to change it? I don't know but you might as well get use to it, lol.

Wait until you get on a Nexus and try "wr" or "logo".

Edit: "sh mac-add" seems to work pretty consistently for me (other than on CATOS, obviously).

notgoing2fail

I don't know what happened but on my latest IOS 15.0 my "do" command only does "do show run".

If I try: "do wr" or "do wr mem" it doesn't work.

tiersten

notgoing2fail wrote: »

I don't know what happened but on my latest IOS 15.0 my "do" command only does "do show run".

If I try: "do wr" or "do wr mem" it doesn't work.

write memory is deprecated and you should use copy running-config startup-config. Whilst wr mem doesn't work, copy run sta does along with other commands. The privileged mode parser works differently when you're using it via do.

notgoing2fail

tiersten wrote: »

write memory is deprecated and you should use copy running-config startup-config. Whilst wr mem doesn't work, copy run sta does along with other commands. The privileged mode parser works differently when you're using it via do.

lol it is!!?? hold the music folks...

Wait a second...I thought "wr mem" or just "wr" was kinda the "new" shortcut instead of typing out copy run start? Apparently not...wow!

So wasn't "copy run start" always in the IOS? Why was "wr mem" introduced in the first place then?

My old IOS's from what I remember don't support "wr mem" so I always thought that "wr mem" or "wr" was the newer method...

ColbyG

write mem is way old school

DevilWAH

funny aint it well all use wr, as its so easy and quick. but yep its old school. however as far as switches go it works identical to copy run start. As i unerstood it write memory did exactly that. wrote the running memory to a perstance storage. copy run start copies a actual file out of memory to perstance storage. write memory was like saving a snap shot of the running state. while copy run is a file that needs to be read and parsed back in to the running memory at boot. now of course wr and copy run do the same thing. i supose so many people like the ease of "wr" that cisco saw fit to keep the syntax.

tiersten

DevilWAH wrote: »

As i unerstood it write memory did exactly that. wrote the running memory to a perstance storage. copy run start copies a actual file out of memory to perstance storage. write memory was like saving a snap shot of the running state. while copy run is a file that needs to be read and parsed back in to the running memory at boot.

"copy nvram:running-config nvram:startup-config" and "write memory" do exactly the same thing. The configuration generated is the same and they're interchangeable.

DevilWAH wrote: »

now of course wr and copy run do the same thing. i supose so many people like the ease of "wr" that cisco saw fit to keep the syntax.

At one point in 12.3, Cisco decided that "write memory" would be deprecated and removed at some unspecified point in the future. However, due to the complaints it appears that they reversed this decision in 12.4 onwards and "write memory" is no longer marked as deprecated.

As Cisco may change their mind in the future, I'd still say use "copy run sta" if you can.

notgoing2fail

Thanks guys, well, I suppose I better get used to "copy run start" if that's the way of the future. But jeez, couldn't they throw us a bone?

"wr" was sooooo and isssss so much easier....

what next? they are going to take away "u all"?

tiersten

notgoing2fail wrote: »

Thanks guys, well, I suppose I better get used to "copy run start" if that's the way of the future. But jeez, couldn't they throw us a bone?

"wr" was sooooo and isssss so much easier....

You can always set an alias. Up to you anyway if you want to use it. The latest IOS command reference on cisco.com doesn't list it as deprecated.

notgoing2fail wrote: »

what next? they are going to take away "u all"?

Thats a built in alias.

Router#show aliases
Exec mode aliases:
  h                     help
  lo                    logout
  p                     ping
  r                     resume
  s                     show
  u                     undebug
  un                    undebug
  w                     where

ATM virtual circuit configuration mode aliases:
  vbr                   vbr-nrt

notgoing2fail

tiersten wrote: »
You can always set an alias. Up to you anyway if you want to use it. The latest IOS command reference on cisco.com doesn't list it as deprecated.

Thats a built in alias.
Router#show aliases
Exec mode aliases:
  h                     help
  lo                    logout
  p                     ping
  r                     resume
  s                     show
  u                     undebug
  un                    undebug
  w                     where

ATM virtual circuit configuration mode aliases:
  vbr                   vbr-nrt

Dude. Are you like walking IOS savant?

tiersten

notgoing2fail wrote: »

Dude. Are you like walking IOS savant?

No :P I looked at the list of public commands and saw that there are multiple u* commands and therefore something must be forcing u to be undebug. Looking at the list of built in aliases answered that question.

dynamik

notgoing2fail wrote: »

Dude. Are you like walking IOS savant?

Not only IOS...