Guidelines And Limitations For Pim And Pim6 - Cisco Nexus 7000 Series Configuration Manual

Guidelines and Limitations for PIM and PIM6

• For global commands, you are in the correct virtual routing and forwarding (VRF) mode. The default
Guidelines and Limitations for PIM and PIM6
PIM and PIM6 have the following configuration guidelines and limitations:
• Tunnel interfaces do not support PIM until Cisco NX-OS Release 5.2(1). Beginning with Release 5.2(1),
• The Cisco NX-OS software does not support multicast on a GRE tunnel interface that is in a different
• Cisco NX-OS PIM and PIM6 do not interoperate with any version of PIM dense mode or PIM sparse
• Do not configure both Auto-RP and BSR protocols in the same network.
• Configure candidate RP intervals to a minimum of 15 seconds.
• If a device is configured with a BSR policy that should prevent it from being elected as the BSR, the
• F2-Series modules do not support any form of IPv4 or IPv6 tunnels.
• Beginning with Release 5.x, using BFD for PIM to support fast failure detection is recommended.
• Default values for the PIM hello interval are recommended and should not be modified.
• Cisco NX-OS PIM and PIM6 do not support Bidir PIM or SSM on vPCs.
• PIM adjacency with a vPC leg or with a router behind a vPC is not supported.
• Beginning with Release 7.1, PIM Bidir mode is not supported for VDCs that have the F2 Module. Bidir
• Use the ip igmp static-oif command on a Layer 3 interface of Cisco Nexus device to force the interface
Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide
76
configuration mode shown in the examples in this chapter applies to the default VRF.
you can configure multicast on generic routing encapsulation (GRE) tunnel interfaces.
virtual routing and forwarding (VRF) instance than the VRF of the transport interface.
mode version 1.
device ignores the policy. This behavior results in the following undesirable conditions:
• If a device receives a BSM that is permitted by the policy, the device, which incorrectly elected
itself as the BSR, drops that BSM so that routers downstream fail to receive it. Downstream devices
correctly filter the BSM from the incorrect BSR so that these devices do not receive RP information.
• A BSM received by a BSR from a different device sends a new BSM but ensures that downstream
devices do not receive the correct BSM.
Note Aggressive PIM timers have been tested and can be supported in deployments
where PIM timers must be modified. However this testing was limited and
SSO/ISSU cannot be guaranteed in such a deployment. For more information,
see the Cisco Nexus 7000 Series NX-OS Verified Scalability Guide.
mode is supported on F2E or F2E with F3 modules on the same VDC.
getting populated as an Outgoing Interface List (OIL). Do not use the ip igmp join-group command for
this purpose.
Configuring PIM and PIM6