other. This is a pretty powerful feature that adds another layer of virtualization to the Nexus platform. VRFs are a distinctly Layer-3 idea, SO you cannot assign a VLAN to a VRF, but you can assign a VLAN interface to one. VRFs can be frustrating if you're not used to them. In our example, the command sho ip route won't show any of our configured interfaces. This is because the default VRF is named default. Since there are multiple routing tables now, if you want to see the routing table within a specific VRF, you must specify the VRF within your show command: NX-7K-1-Daisy# sho ip route vrf Earth IP Route Table for VRF "Earth" '*' denotes best ucast next-hop '** denotes best mcast next-hop "[x/y]' denotes [preference/metric] 10.0.0.0/24, ubest/mbest: 1/0, attached *via 10.0.0.1, Eth3/25, [o/o], 02:49:03, direct 10.0.0.1/32, ubest/mbest: 1/0, attached *via 10.0.0.1, Eth3/25, [o/o], 02:49:03, local Most Layer-3 relayed commands support the VRF keyword in the Nexus, as shown here: NX-7K-1-Daisy# sho ip eigrp neighbors vrf Earth IP-EIGRP neighbors for process 0 VRF Earth IP-EIGRP neighbors for process 100 VRF Earth Address Interface Uptime RTO Q Seq (sec) Cnt Num 10.0.0.2 Eth3/25 00:00:50 Even the ping command supports the VRF keyword: NX-7K-1-Daisy# ping 10.0.0.2 vrf Earth PING 10.0.0.2 (10.0.0.2): 56 data bytes Request 0 timed out 64 bytes from 10.0.0.2: icmp_seq=1 ttl=254 time=0.884 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=254 time=0.538 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=254 time=0.597 ms 64 bytes from 10.0.0.2: icmp_seq=4 ttl=254 time=0.6 ms Chapter 9: Routing and Routers To make things easier, you can change the current VRF SO that all subsequent com- mands apply to that VRF. You do this with the routing-context command, which is not a configuration command: NX-7K-1-Daisy# routing-context vrf Earth NX-7K-1-Daisy%Earth# This changes our prompt by appending the name of the VRF after a percent sign to remind us where we are. Now when we run the show ip route (or any other) command, it is applied to the c