Setting Parameters of the SA Request Message
Context
By default, when a receiver joins in, the device does not initiatively send an SA Request message to the MSDP peer. The device waits for the Source-Active (SA) message sent by the MSDP peer during the next period, which delays the time for the receiver to obtain information about multicast sources. To enable the new receiver to learn information about active multicast sources immediately, the device needs to initiatively send an SA Request message to the MSDP peer.
After receiving the SA Request message, the remote MSDP peer responds to the SA message with a message containing the (S, G) information that meets the requirements. If the rule for filtering SA Request messages is configured on the remote MSDP peer, the remote MSDP peer responds only to the SA Request messages that match the rule.
Before configuring a local RP to send SA Request messages, you must disable the SA caching function on the local RP and enable the SA caching function on its remote MSDP peer.
Procedure
- Run system-view
The system view is displayed.
- Run msdp [ vpn-instance vpn-instance-name ]
The MSDP view is displayed.
- Configure a local rendezvous point (RP) to send SA Request messages initiatively.
Run peer peer-address request-sa-enable
The local RP is configured to send SA Request messages initiatively.
- (Optional) Configure the rule for filtering received SA Request messages on the remote MSDP peer.
Run peer peer-address sa-request-policy [ acl { basic-acl-number | acl-name } ]
A rule for filtering received SA Request messages is configured.