Configuring sa messages related parameters, Configuration prerequisites, Configuring sa message content – H3C Technologies H3C S10500 Series Switches User Manual
Page 229: Configuring sa messages, Related parameters

214
To do...
Use the command...
Remarks
Deactivate an MSDP peer
shutdown peer-address
Optional
Active by default
Configure the interval between
MSDP peer connection retries
timer retry interval
Optional
30 seconds by default
Configure an MD5 authentication
key for the TCP connection to be
established with an MSDP peer
peer peer-address password
{ cipher | simple } password
Optional
By default, MD5 authentication is
not performed before an TCP
connection is established.
CAUTION:
The MSDP peers involved in the MD5 authentication must have the same authentication method and key.
Otherwise, the authentication fails and the TCP connection cannot be established.
Configuring SA messages related parameters
Configuration prerequisites
Before you configure SA message delivery, complete the following tasks:
•
Configure any unicast routing protocol so that all devices in the domain are interoperable at the
network layer
•
Configure basic functions of MSDP
•
Determine the ACL rules for filtering SA request messages
•
Determine the ACL rules as SA message creation rules
•
Determine the ACL rules for filtering SA messages to be received and forwarded
•
Determine the TTL threshold for multicast packet encapsulation in SA messages
•
Determine the maximum number of (S, G) entries learned from the specified MSDP peer that the
router can cache
Configuring SA message content
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 joins 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.
After the source-side RP is enabled to encapsulate multicast data in SA messages, if the RP wants to sends
a multicast packet, it encapsulates the multicast packet in an SA message and sends it. After receiving the
SA message, the remote RP de-encapsulates the SA message and delivers the multicast packet 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
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. In the Anycast RP application, however, you must configure RPs with
the same IP address on two or more routers in the same PIM-SM domain and configure these routers as