 [1/0] via 10.0.0.1 [1/0] via 10.0.0.2 When in doubt, look at the 0.0.0.0/0 entry in the routing table, as it will always have the most accurate information. Virtual Routing and Forwarding Nexus switches and newer versions of IOS support something called Virtual Routing and Forwarding (VRF) instances. Each VRF is a self-contained routing table within the same router. Within a Nexus 7000, you can have multiple VRFs within a single Virtual Device Context (VDC). On the Nexus 5000, which as of this writing does not support VDCs or routing, you can still have multiple VRFs. In fact, by default, the management network resides in a management VRF, while other traffic is in the default VRF. In IOS 15.x, you may also configure VRFs. On the Nexus platform, two VRFs exist by default-management and default: NX-7K-1-Daisy# sho vrf VRF-Name VRF-ID State Reason default management Creating a new VRF is as simple as specifying one with the vrf context vrf-name com- mand. Here, I'll create two new VRFs, named Earth and Mars: NX-7K-1-Daisy(config)# vrf context Earth NX-7K-1-Daisy(config)# vrf context Mars Now we can see the additional VRFs with the show vrf command: NX-7K-1-Daisy(config)# sho vrf VRF-Name VRF-ID State Reason Earth default management Interfaces can be assigned to VRFs. Remember that in Nexus 7000 switches, interfaces default to routed mode, SO we don't need to configure them as such. You apply inter- faces to VRFs with the vrf member vrf-name interface command: NX-7K-1-Daisy(config)# int e3/25 NX-7K-1-Daisy(config-if)# vrf member Earth NX-7K-1-Daisy(config-if)# ip address 10.0.0.1/24 Virtual Routing and Forwarding Now I'll assign a different interface to another VRF: NX-7K-1-Daisy(config-if)# int e3/26 NX-7K-1-Daisy(config-if)# vrf member Mars NX-7K-1-Daisy(config-if)# ip address 10.0.0.1/24 Notice that I have two interfaces in the same router configured with the same IP address. This is possible because they each belong to a different VRF. The routing tables in VRFs Earth and Mars are completely separate from each 