This command configures a default or static RPF peer from which all MSDP SA messages are accepted. To remove the default peer, enter the configure msdp peer no-default-peer command.
|filter-name||Specifies the name of the policy filter associated with the default peer. The peer will be the default peer for all SA entries that are permitted by the policy filter. If an SA message is allowed by the policy filter, it will be accepted. Otherwise, the SA message has to go through the regular RPF-check. The static peer RPF check is the last step in peer RPF algorithm. So, if an SA message is denied by the default peer policy, ultimately the SA message will be rejected by MSDP.|
|peer all||Specifies all MSDP peers.|
|remoteaddr||Specifies the IP address of the MSDP peer.|
|vrname||Specifies the name of the virtual router to which this command applies. If a name is not specified, it is extracted from the current CLI context.|
By default, no static RPF peer is configured.
The default-peer-policy keyword specifies the name of the policy filter associated with the default peer. You can configure multiple default peers with different policies. If no policy is specified, then the current peer is the default RPF peer for all SA messages.
Configuring a default peer simplifies peer-RPF checking of SA messages. If the peer-RPF check fails, the default peer rule is applied to see if the SA messages should be accepted or rejected.
If a default peer policy is specified, the peer is the default peer only for the (Source, Group), or (S, G), that satisfies the policy. If the policy is not specified, then the default peer is used for all (S, G, RP).
You can configure multiple default peers on an MSDP router; however, all default peers must either have a default policy or not. A mix of default peers, with a policy and without a policy, is not allowed.
The following example configures an MSDP peer with the IP address 192.168.45.43 as the default peer policy for "sales":
configure msdp peer 192.168.45.43 default-peer default-peer-policy sales
This command was first available in ExtremeXOS 12.0.
This command is available on platforms that support the appropriate license. For complete information about software licensing, including how to obtain and upgrade your license and which licenses support the MSDP feature, see the Switch Engine 32.3 Feature License Requirements document.