168
•
A new MSDP peer is created.
•
A previously deactivated MSDP peering connection is reactivated.
•
A previously failed MSDP peer attempts to resume operation.
You can change the MSDP connection retry interval to adjust the interval between MSDP peering
connection attempts.
To enhance MSDP security, enable MD5 authentication for both MSDP peers to establish a TCP
connection. If the MD5 authentication fails, the TCP connection cannot be established.
IMPORTANT:
The MSDP peers involved in MD5 authentication must be configured with the same authentication
method and key. Otherwise, the authentication fails and the TCP connection cannot be established.
To control MSDP peering connections:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MSDP view.
msdp
[
vpn-instance
vpn-instance-name
]
N/A
3.
Tear down an MSDP peering
connection.
shutdown
peer-address
By default, an MSDP peering
connection is active.
4.
Set the keepalive timer and
peer hold timer for MSDP
sessions.
timer
keepalive
keepalive
holdtime
By default, the keepalive timer
and peer hold timer are 60
seconds and 75 seconds,
respectively.
This command immediately takes
effect on an established session.
5.
Configure
the
MSDP
connection retry interval.
timer retry interval
The default setting is 30 seconds.
6.
Configure the device to
perform MD5 authentication
when establishing a TCP
connection with an MSDP
peer.
peer peer-address
password
{
cipher
|
simple
}
password
By default, the device does not
perform MD5 authentication when
establishing a TCP connection
with an MSDP peer.
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 features.
Enabling multicast data encapsulation in SA messages
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
