ent iterations prefer to have the management IP address in the management VRF. This will likely burn you more than once because the manage- ment VRF is not the default VRF. Here's a great example. Everyone loves the show ip interface brief command, SO let's try it on a configured Nexus 5000: NX-5K-1# sho ip int brie IP Interface Status for VRF "default" Interface IP Address Interface Status Huh. That's odd. I know I configured the management interface, SO why doesn't it show up? Because the default VRF is named "default" (clever huh?), but the manage- ment interface resides in the management VRF. To see it, we have to add vrf manage ment to the show ip interface brief command: NX-5K-1# sho ip int brie vrf management IP Interface Status for VRF "management" Interface IP Address Interface Status mgmto 10.10.10.1 protocol-up/link-up/admin-up If you're thinking "That's dumb," you're not alone. Remember, though, the manage- ment VRF is designed to be out of band with the switch, and that's why it resides there. It makes sense, especially if you use a 7000 instead of a 5000, but it's different, SO it can be frustrating. If you find that your command isn't working, think about your VRF and see if that helps. Even ping needs to have the VRF specified: NX-5K-1# ping 10.10.10.2 vrf management PING 10.10.10.2 (10.10.10.2) 56 data bytes 64 bytes from 10.10.10.2: icmp_seq=0 ttl=254 time=4.762 ms 64 bytes from 10.10.10.2: icmp_seq=1 ttl=254 time=8.052 ms 64 bytes from 10.10.10.2: icmp_seq=2 ttl=254 time=8.078 ms 64 bytes from 10.10.10.2: icmp_seq=3 ttl=254 time=8.168 ms 64 bytes from 10.10.10.2: icmp_seq=4 ttl=254 time=8.178 ms Luckily, you can change the routing context used with the routing-context vrf vrf- name command: NX-5K-1# routing-context vrf management NX-5K-1%management# Now, every command we issue will apply to the management VRF: NX-5K-1%management # ping 10.10.10.2 PING 10.10.10.2 (10.10.10.2): 56 data bytes 64 bytes from 10.10.10.2: icmp_seq=0 ttl=254 time=4.762 ms 64 bytes from 10.10.10.2: icmp_seq=1 ttl=254 ti