Configuring Inter-AS Static RPF Peers

To enable PIM-SM domains in different ASs to share multicast source information, configure a static Reverse Path Forwarding (RPF) peer relationship between Rendezvous Points (RPs) in different ASs.

Context

If inter-AS MSDP peers have been configured for BGP peers, skip this configuration.

Procedure

Run system-view
The system view is displayed.
Run msdp [ vpn-instance vpn-instance-name ]
The MSDP view is displayed.
Run peer peer-address connect-interface interface-type interface-number
An MSDP peer connection is set up.
- peer-address: specifies the IP address of a remote MSDP peer.
- interface-type interface-number: specifies the local interface connected with the remote MSDP peer.
(Optional) Run peer peer-address description text
A description is added for the remote MSDP peer.

This configuration helps you differentiate remote MSDP peers and manage the connections with the remote MSDP peers.
- peer-address: specifies the IP address of a remote MSDP peer.
- text: specifies the description text. The text is a string of a maximum of 80 characters.
Run static-rpf-peer peer-address [ rp-policy ip-prefix-name ]
The remote MSDP peer is specified as a static RPF peer.
- peer-address: specifies the IP address of a remote MSDP peer.
- rp-policy ip-prefix-name: specifies the policy of filtering the addresses of source's RPs in the Source Active (SA) messages.
  
  If several static RPF peers are configured for one router, obey the following configuration rules:
  - Specify rp-policy for all static RPF peers.
    
    After receiving SA messages from active static RPF peers, the local router filters the SA messages based on the rp-policy configured for each static RPF peer. The local router accepts only the SA messages that pass the filtration rule.
  - Do not specify rp-policy for any static RPF peers.
    
    The router accepts all SA messages received from active static RPF peers.
Run commit
The configuration is committed.