The static-rpf-peer command specifies the static Reverse Path Forwarding (RPF) peer for the FW. Source Active (SA) messages sent by the peer are free from the RPF check.
The undo static-rpf-peer command restores the default configuration.
| Parameter | Description | Value |
|---|---|---|
| peer-address | Specifies the address of a static RPF peer. | The address is in dotted decimal notation. |
| rp-policy ip-prefix-name | Indicates the filtering policy based on RP addresses. The filtering policy is used to filter SA messages based on source RP addresses. ip-prefix-name specifies the name of the filtering policy. | The name is a string of 1 to 169 characters. |
By default, the static RPF peer is not configured.
You can repeat the static-rpf-peer peer-address command to specify multiple remote static RPF peers for the FW.
Configure multiple static RPF peers for the FW using the following methods:
rp-policy is configured on all peers: When SA messages sent by a static RPF peer in the active state reach the local router, the local router filters the SA messages according to rp-policy specified on the peers, and receives only the SA messages passing the filtering.
None of the peers is configured with rp-policy: The local router receives all SA messages from static RPF peers in the active state.
<sysname> system-view
[sysname] ip ip-prefix list-df permit 192.168.0.0 16 greater-equal 16 less-equal 32
[sysname] msdp
[sysname-msdp] peer 192.168.3.2 connect-interface GigabitEthernet 0/0/0
[sysname-msdp] static-rpf-peer 192.168.3.2 rp-policy list-df