I've seen several implementations of "interface vlan <id>" on many Catalyst switches for interVLAN routing but on a single instance of a core switch only.
Recently, I've seen 2 core switches connected with each other via HSRP and with interface vlan <id> configured on each switches -- same vlan id created for both switches. The interface vlan <id> was configured to have a virtual ip and a priority id for HSRP.
My question is, in these kind of scenario, what would be the reason, chances or cause that a virtual interface (layer 3 - switch virtual interface) would go into a down state ? I am just looking for a clear answer/picture since it's the physical interface that often encounter these type of problems most of the time.
Very well explained by Steven and very less likely you will see any vlan interface in particular going down. If the core switch 1 vlan interface does not find any physical port configured for itself it will go down.
Generally on core switches there are no end users and generally we find trunk connections so lets say the trunk connection or that particular physical port goes down then the vlan interface will also go down. Also sometimes bymistake if you delete some vlan from vlan database then also its layer 3 interface goes down.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...