Configuring Sa Message-Related Parameters; Configuration Prerequisites; Configuring Sa Message Contents - HPE FlexFabric 5930 Series Ip Multicast Configuration Manual

IMPORTANT:
The MSDP peers involved in MD5 authentication must be configured with the same authentication
method and password. Otherwise, the authentication fails and the TCP connection cannot be
established.
To control MSDP peering connections:
Step
Enter system view.
1.
Enter MSDP view.
2.
Tear down an MSDP peering
3.
connection.
Configure the interval
4.
between MSDP peering
connection attempts.
Configure MD5
5.
authentication for both
MSDP peers to establish a
TCP connection.

Configuring SA message-related parameters

This section describes how to configure SA message-related parameters.

Configuration prerequisites

Before you configure SA message delivery, complete the following tasks:
•
Configure a unicast routing protocol so that all devices in the domain can interoperate at the
network layer.
•
Configure basic MSDP functions.

Configuring SA message contents

Some multicast sources send multicast data at an interval longer than the aging time of (S, G) entries.
In this case, the source-side DR must encapsulate multicast data packet-by-packet in register
messages and send them to the source-side RP. The source-side RP transmits the (S, G)
information to the remote RP through SA messages. Then, the remote RP sends join messages to
the source-side DR and builds an SPT. Because the (S, G) entries have timed out, remote receivers
can never receive the multicast data from the multicast source.
To avoid this problem, you can configure the source-side RP to encapsulate multicast data in SA
messages. As a result, the source-side RP can forward the multicast data in SA messages to its
remote MSDP peers. After receiving the SA messages, the remote RP decapsulates the SA
messages and forwards the multicast data to the receivers in the local domain along the RPT.
The MSDP peers deliver SA messages to one another. After receiving an SA message, a router
performs an RPF check on the message. If the router finds that the remote RP address is the same
as the local RP address, it discards the SA message.
However, in the Anycast RP application, you must configure the same IP address for the RPs in the
same PIM-SM domain and configure these RPs as MSDP peers. To make sure SA messages can
pass the RPF check, you must assign SA messages a logical RP address that is different than the
Command
system-view
msdp [ vpn-instance
vpn-instance-name ]
shutdown peer-address
timer retry interval
peer peer-address password
{ cipher | simple } password
153
Remarks
N/A
N/A
By default, an MSDP peering
connection is active.
The default setting is 30 seconds.
By default, MD5 authentication is
not performed before a TCP
connection is established.