Configuring PIM and PIM6
Verification for N7K-1:
show ip pim group 224.1.1.0
PIM Group-Range Configuration for VRF "default"
Group-range
224.0.0.0/4
Verification for N7K-2:
show ip pim group 224.1.1.0
PIM Group-Range Configuration for VRF "default"
Group-range
224.0.0.0/4
• Because you cannot configure a static RP and its default value is 0, the RP priority has no impact. You
can configure the BSR RP-candidate with a value between 0 and 255. The system elects the device with
the most specific group list. If both devices have the same group list, the system elects the device with
the highest RP IP address (see configuration example 3).
Configuration for N7K-1:
interface loopback0
ip address 192.168.1.1/32
ip pim sparse-mode
ip pim bsr bsr-candidate loopback0
ip pim rp-address 192.168.2.1 group-list 224.0.0.0/4
ip pim bsr rp-candidate loopback0 group-list 224.0.0.0/4 priority 0
ip pim bsr forward listen
Configuration for N7K-2:
interface loopback0
ip address 192.168.2.1/32
ip pim sparse-mode
ip pim rp-address 192.168.2.1 group-list 224.0.0.0/4
ip pim bsr forward listen
Mode
RP-address
ASM
192.168.2.1
Mode
RP-address
ASM
192.168.2.1
• Configuration example 3—Identical group list and identical RP priorities: In this example, the
system elects the device labeled N7K-2 as the RP for all multicast addresses specified in the
224.0.0.0/4 group list because it has the highest RP IP address. The system does not compare RP
priorities between BSR RPs and static RPs.
Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide
PIM BSR RP-Candidate Versus Static RP Election Process
Shared-tree-only range
Shared-tree-only range
-
67