enable msdp process-sa-request

enable msdp [{peer} remoteaddr | peer all] process-sa-request {sa-request-filter filter-name } {vr vr_name}

Description

This command configures MSDP to receive and process SA request messages from a specified peer or all peers. If an SA request filter is specified, only SA request messages from those groups permitted are accepted. All others are ignored.

Syntax Description

peer all Specifies all MSDP peers.
filter-name Specifies the name of the policy filter associated with SA request processing.
remoteaddr Specifies the IP address of the MSDP peer.
vr_name 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.

Default

By default, all SA request messages are accepted from peers.

Usage Guidelines

Use this command to configure the router to accept all or just some SA request messages from peers. If no policy is specified, all SA request messages are accepted. If a policy is specified, only SA request messages from those groups permitted are accepted, and all others are ignored.

You cannot change an SA request filter while SA request processing is enabled for an MSDP peer. You must first disable SA request processing for a peer and then re-enable it with an SA request filter.

You can use the following policy attributes in an SA request policy. All other attributes are ignored.
  • Match:
    • multicast-group
    • multicast-source
    • pim-rp
  • Set:
    • permit
    • deny

Example

The following example enables processing of SA request messages received from a peer with the IP address 192.168.45.43:

enable msdp peer 192.168.45.43 process-sa-request sa-request-filter intra_domain

History

This command was first available in ExtremeXOS 12.0.

Platform Availability

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 Feature License Requirements document.