Vpc Consistency Check For Layer 3 Parameters; Multicast Interaction In A Vpc Topology; Unsupported Multicast Topology - 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

vPC Consistency Check for Layer 3 Parameters

In a vPC topology, vPC peer switches run routing protocols independently and they maintain the routing
table independently. Consistency checks are not performed to verify that Layer 3 configurations in the
vPC domain are configured symmetrically.
For example, if you configure a router ACL (RACL) on one SVI and you do not configure the router on
the corresponding SVI on the vPC peer, a syslog message is not displayed. You must configure the RACL
on both devices. This is consistent with the operation of independent routing devices.
Similarly, if you configure peer gateway on one vPC peer and you want the same peer gateway
configuration on the other vPC peer, you must configure the peer gateway on the vPC peer.
To confirm that a vPC domain is correctly configured for Layer 3 operations, the following
configurations must be consistent:
•
•
•

Multicast Interaction in a vPC Topology

This section includes the following topics:
•
•

Unsupported Multicast Topology

Figure 2-8
Figure 2-8 Unsupported Multicast Topology with a vPC
N5k-1
When a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join
messages are received only by one switch. The multicast data might be received by the other switch.
SVI configurations
RACLs
Routing protocol configurations
Unsupported Multicast Topology, page 2-9
Multicast Routing Table Size, page 2-10
shows an unsupported multicast topology in a vPC configuration.
N5k-2
Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
vPC Consistency Check for Layer 3 Parameters
N5k-1
PIM peer
N5k-2
2-9