Configuring Sending SA Request Messages

When FW receives a new Join message and no corresponding (S, G) entry exists locally or in the Source Active (SA) cache, the FW immediately sends an SA Request message to the specified MSDP peer rather than waits for the SA message in the next period.

Prerequisites

Before Configuring Sending SA Request Messages, complete the following tasks:

Configuring a unicast routing protocol to implement interconnection at the network layer
Enabling IP multicast
Configuring a PIM-SM domain to implement intra-domain multicast
Configuring PIM-SM Inter-domain Multicast or Configuring PIM-SM Inter-domain Multicast

Context

The capacity of SA Cache on certain FWs is small. When these FWs need to receive multicast data, they cannot immediately obtain the valid (S, G) information and need to wait for the SA message sent by their MSDP peers in the next period.

If SA Cache is enabled on the remote MSDP peer and the capacity of the SA Cache is large, configuring sending SA Request message on the local router can shorten the period during which receivers obtain multicast source information.

Procedure

Access the system view.
system-view
Access the MSDP view.
msdp [ vpn-instance vpn-instance-name ]
Enable the function of sending SA Request messages.
peer peer-address request-sa-enable

peer-address specifies the address of a remote MSDP peer. When the local FW receives a new Join message from a group, it sends an SA Request message only to peer-address.