Configuring Static RPF Peers

You can configure a static Reverse Path Forwarding (RPF) peer relationship between Rendezvous Points (RPs) in different ASs so that Source Active (SA) messages which sent by RPF peer do not need do RPF check.

Prerequisites

Before configuring static RPF peers, complete the following tasks:

Configuring a unicast routing protocol to enable interworking at the network layer
Enabling IP multicast
Configuring a PIM-SM domain to implement intra-domain multicast

Procedure

Access the system view.
system-view
Enable MSDP in the public network instance or VPN instance and access the MSDP view.
msdp [ vpn-instance vpn-instance-name ]
Configure an MSDP peer connection.
peer peer-address connect-interface interface-type interface-number

The parameters of the command are explained as follows:
- peer-address: specifies the address of a remote MSDP peer.
- interface-type interface-number: specifies the local interface connected to the remote MSDP peer.
(Optional) Add description of a remote MSDP peer.
peer peer-address description text

The configuration helps to distinguish remote MSDP peers and manage the connections with the remote MSDP peers.

The parameters of the command are explained as follows:
- peer-address: specifies the address of a remote MSDP peer.
- text: specifies the description text. The text is a string of up to 80 characters.
Specify a remote MSDP peer statically as an RPF peer.
static-rpf-peer peer-address [ rp-policy ip-prefix-name ]

peer-address specifies the address of a remote MSDP peer.