Dedicated Vrf For A Keepalive Interface - Cisco Nexus 5000 Series Operation Manual

Chapter 2 Cisco Nexus 5500 Platform Layer 3 and vPC Operations
S e n d d o c u m e n t a t i o n c o m m e n t s t o n 5 k d o c f e e d b a c k @ c i s c o . c o m
Figure 2-6
VLAN 10:1.1.1.1
This topology is supported for unicast traffic but not for multicast traffic. In this topology, we
recommend that you use Layer 3 interfaces instead of vPC interfaces to connect routers to Cisco Nexus
5500 Platform switches whenever possible.
Figure
connects with Layer 3 interfaces 1.1.1.2 and 2.2.2.2 to the two vPC peers and these interfaces are not
part of a vPC port channel.
Figure 2-7
L3 intf: 1.1.1.1

Dedicated VRF For a Keepalive Interface

Beginning in Cisco NX-OS Release 5.0(3)N1(1b), the Cisco Nexus 5500 Platform switch supports VRF
lite with a Layer 3 module and Enterprise license and you can create a VRF and assign the interface to
a VRF. Prior to this release, two VRFs were created by default: the VRF management and VRF default.
The management interface(mgmt0) and all SVI interfaces resided in the VRF management and VRF
default respectively.
Control Traffic Forwarding in a vPC Topology
N5k-1
Po1:1.1.1.3
Routing protocol peer
2-7, shows the recommended topology for connectivity of routers to a vPC domain. The router
Connecting a Router to a vPC Domain Using Layer 3 Interfaces
N5k-1
1.1.1.2
Routing protocol peer
Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
2. Packets are
redirected to CPU.
Software forwards
packet to "N5k-1."
N5k-2
VLAN 10:1.1.1.2
1. Protocol packets
destined to: 1.1.1.1
and TTL-1
N5k-2
L3 intf: 2.2.2.1
2.2.2.2
Dedicated VRF For a Keepalive Interface
2-7