3com MSR 20-20 참조 매뉴얼
1381
<Sysname> system-view
[Sysname] msdp
[Sysname-msdp] shutdown 125.10.7.6
static-rpf-peer
Syntax
static-rpf-peer peer-address [ rp-policy ip-prefix-name ]
undo static-rpf-peer peer-address
View
Public instance MSDP view, VPN instance MSDP view
Parameter
peer-address: MSDP peer address.
rp-policy ip-prefix-name: Specifies a filtering policy based on the RP address in SA
messages, where ip-prefix-name is the filtering policy name, a string of 1 to 19
characters (case sensitive).
messages, where ip-prefix-name is the filtering policy name, a string of 1 to 19
characters (case sensitive).
Description
Use the static-rpf-peer command to configure a static RPF peer.
Use the undo static-rpf-peer command to remove a static RPF peer.
No static RPF peer is configured by default.
When you configure multiple static RPF peers, observe the follow rules:
1 If you use the rp-policy keyword for all the static RPF peers, all the static RPF peers
take effect concurrently. SA messages will be filtered as per the configured prefix
list and only those SA messages whose RP addresses pass the filtering will be
accepted. If multiple static RPF peers use the same filtering policy at the same
time, when a peer receives an SA message, it will forward the SA message to the
other peers.
list and only those SA messages whose RP addresses pass the filtering will be
accepted. If multiple static RPF peers use the same filtering policy at the same
time, when a peer receives an SA message, it will forward the SA message to the
other peers.
2 If you use the rp-policy keyword for none of the static RPF peers, according to the
configuration sequence, only the first static RPF peer whose connection is in the
UP state will be activated, and all SA messages from this peer will be accepted
while the SA messages from other static RPF peers will be discarded. When this
active static RPF peer fails (for example, when the configuration is removed or
when the connection is torn down), still the first RPF peer whose connection is in
UP state will be selected as the activated RPF peer according to the configuration
sequence.
UP state will be activated, and all SA messages from this peer will be accepted
while the SA messages from other static RPF peers will be discarded. When this
active static RPF peer fails (for example, when the configuration is removed or
when the connection is torn down), still the first RPF peer whose connection is in
UP state will be selected as the activated RPF peer according to the configuration
sequence.
Related command:
display msdp peer-status and ip prefix-list.
Example
# Configure static RPF peers in the public instance.
<Sysname> system-view
[Sysname] ip ip-prefix list1 permit 130.10.0.0 16 great-equal 16 les
s-equal 32
[Sysname] msdp
[Sysname-msdp] peer 130.10.7.6 connect-interface ethernet 1/0
[Sysname-msdp] static-rpf-peer 130.10.7.6 rp-policy list1