Configuring PIM Anycast RP
Context
Anycast RP allows several RPs with the same address to be configured in a PIM-SM domain and establish peer relationships, so that a multicast source can register with the closest RP and receivers can join the closest RP. This releases burdens on a single RP, implements RP backup, and optimizes multicast forwarding paths. Currently, there are two anycast implementations: Multicast Source Discovery Protocol (MSDP) for anycast RP and PIM for anycast RP. In IPv4 network deployment, choose either of the two modes. It is recommended that the two modes be not used together.
Configuring Global Anycast RP
Configuring Local Addresses for Anycast RPs
Context
The devices functioning as Anycast RPs are identified by the same logical address so that the RP in the PIM-SM domain is unique. However, the devices need to distinguish one another during communication, so the Anycast RP addresses cannot be used. In this situation, you need to configure the Anycast RP local address and Anycast RP peers.
After the local address is configured, the RP uses the local addresses as the source addresses of the packets when sending Register packets to Anycast RP peers.
Procedure
- Run system-view
The system view is displayed.
- Run pim [ vpn-instance vpn-instance-name ]
The PIM view is displayed.
- Run anycast-rp rp-address
The Anycast RP view is displayed.
- Run local-address local-address
Local addresses are configured for Anycast RP.
You are advised to use the address of the Loopback interface as the local address of the Anycast RP.
The local address of the Anycast RP must be different from the address of the Anycast RP.
Configuring Anycast RP Peers
Context
The devices functioning as Anycast RPs are identified by the same logical address so that the RP in the PIM-SM domain is unique. However, the devices need to distinguish one another during communication, so the Anycast RP addresses cannot be used. In this situation, you need to configure the Anycast RP local address and Anycast RP peers.
After Anycast RP peers are configured, the RP uses the peer addresses as the destination addresses of the packets when sending Register packets to Anycast RP peers.
Procedure
- Run system-view
The system view is displayed.
- Run pim [ vpn-instance vpn-instance-name ]
The PIM view is displayed.
- Run anycast-rp rp-address
The Anycast RP view is displayed.
- Run peer peer-address [ fwd-msdp-sa [ acl-number | acl-name acl-name ] ]
Anycast RP peers are configured.
In a PIM-SM domain, devices functioning as Anycast RP must be fully connected. Anycast RP peer relationships need to be configured between every two Anycast RPs.
Verifying the PIM Anycast RP Configuration
Context
Procedure
- Run the display pim [ vpn-instance vpn-instance-name | all-instance ] rp-info command to check the RP.
- Run the following commands to check the PIM routing table.
display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]
display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table brief [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | incoming-interface { interface-type interface-number | register } ] *