07-31-2020 07:26 AM
Is there an easy way to only show Vlan Interfaces that have an IP addresses applied to them aka SVI? Currently I am doing a 'sh run'; however, I feel as if there might be a better way.
My hardware is a mixture of NX-OS and Cat.
Thank you
07-31-2020 07:36 AM - edited 07-31-2020 07:38 AM
show ip interface brief | in up - is this work for you ?
show ip interface brief | in Vlan - nexus works
08-03-2020 07:44 AM
07-31-2020 07:36 AM - edited 07-31-2020 07:37 AM
On Nexus platforms, you can use for example:
sh int vlan 10
or
if you want to see multiple vlans
sh int vlan 10-15
On catalyst
sh run int vlan10
HTH
07-31-2020 07:18 PM
I should have put - "If you do not know what vlans have svi interfaces".
I will try all of your suggestions on Monday.
Thank you
08-01-2020 02:29 PM
Hello,
what about:
show ip int brief | exclude unassigned
08-03-2020 07:47 AM
08-02-2020 01:33 AM
Hi!
On Cisco Catalyst (IOS and IOS-XE) I am not aware that you can really limit the output to just SVIs with IP addresses.. by default ;)
You can only limit the output to see ANY interfaces with an IP address configured:
# show ip interface brief | exclude unassigned
However on the Nexus we are better off :)
NX-OS let's you use grep (Unix command) by default.
On the Catalyst you have to enable shell processing to be able to do the same!
Enabling shell processing is completely harmless - you can do it anytime.
It just enables you to use a few extra commands which you can not use per default:
# conf t
(conf)# shell processing full
(conf)# end
# show ip interface brief | grep -v unassigned | grep Vlan
Hope that helps :)
Let me know what you think.
Best regards
Juls
08-03-2020 07:43 AM
Hi Julian.bendix
I just read about 'enable shell processing', and noticed it was introduced in 15.x. Is there any security issues I would have to worry about turning this on? Do you know why Cisco did not enable this by default with the new track?
Thank you.
08-03-2020 08:24 AM - edited 08-03-2020 09:28 AM
Hey @romanroma ,
no it just enables you to use a couple extra commands, like some commands that you are used to from Unix :)
There is also another possibilty, which enables shell processing just for one session, and not globally:
#terminal shell
This command in privileged mode does the same as enabling "shell processing full" in global config mode.
But it is only active for the current login session, as soon as you log out, it is deactivated again :)
No concern there in my point of view.
Hope this was helpful, let me know what you think!
Julian
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide