s about the two VLANs: MSFC-6509#sho ip int brief Interface IP-Address OK? Method Status Protocol There are no SVIs active on the MSFC-not even VLAN 1. Let's add an SVI for VLAN 20 and see what happens: MSFC-6509#conf t Enter configuration commands, one per line. End with CNTL/Z. MSFC-6509(config)# int vlan 20 MSFC-6509(config-if)# ip address 10.20.20.1 255.255.255.0 MSFC-6509(config-if)# no shut MSFC-6509(config-if)# ^Z MSFC-6509# 17w2d: %LINK-3-UPDOWN: Interface Vlan20, changed state to down 17w2d: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan20, changed state to down MSFC-6509# MSFC-6509# sho ip int brief Interface IP-Address OK? Method Status Protocol Vlan20 10.20.20.1 YES manual down The SVI is now there, but it won't come up. The SVI will not come up unless there is an active port in the VLAN in Layer 2. I often forget this fact and, after adding the SVIs, go off to create my VLANs, only to find that none of them will come up. To illustrate the point, I'll assign an IP address to the CatOS management interface SCO and place it in VLAN 20. This will put an active device in the VLAN: Catos-6509: (enable) set int sco 20 10.20.20.20 255.255.255.0 Interface SCO vlan set, IP address and netmask set. Now, with something active in VLAN 20, the VLAN 20 SVI comes up in the MSFC: MSFC-6509#sho ip int brief Interface IP-Address OK? Method Status Protocol Vlan20 10.20.20.1 YES manual up NX-OS (Nexus 7000, 5000) Configuring a Nexus for SVIs is very similar to doing SO in IOS. The main difference that gets me every time I'm configuring one for the first time is that, by default, SVIs are not allowed: NX-7K-1(config)# int vlan 10 Invalid command (interface name) at '^' marker. Configuring SVIs As with many technologies on the Nexus platform, SVIs must be enabled. The specific feature that needs to be enabled is called interface-vlan: X-1(config)# feature interface-vlan Once this feature is enabled, we're free to configure the SVI as we would in IOS: NX-7K-1(config)# int vlan 10 NX-7K-1(config-if)# ip address 10.10.1