H3C LS-3100-52P-OVS-H3 Operation Manual - page 1018
1-11
Configuring MSDP Peer Connection Control
MSDP peers are interconnected over TCP (port number 639). You can flexibly control sessions
between MSDP peers by manually deactivating and reactivating the MSDP peering connections. When
the connection between two MSDP peers is deactivated, SA messages will no longer be delivered
between them, and the TCP connection is closed without any connection setup retry, but the
configuration information will remain unchanged.
When a new MSDP peer is created, or when a previously deactivated MSDP peer connection is
reactivated, or when a previously failed MSDP peer attempts to resume operation, a TCP connection is
required. You can flexibly adjust the interval between MSDP peering connection retries.
Follow these steps to configure MSDP peer connection control:
To do...
Use the command...
Remarks
Enter system view
system-view
—
Enter MSDP view
msdp
—
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
Configuring SA Messages Related Parameters
Configuration Prerequisites
Before configuring SA message delivery, complete the following tasks:
z
Configure any unicast routing protocol so that all devices in the domain are interoperable at the
network layer.
z
Configuring basic functions of MSDP
Before configuring SA message delivery, prepare the following data:
z
ACL rules for filtering SA request messages
z
ACL rules as SA message creation rules
z
ACL rules for filtering SA messages to be received and forwarded
z
TTL threshold for multicast packet encapsulation in SA messages
z
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 has to 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.
Since the (S, G) entries have timed out, remote receivers can never receive the multicast data from the
multicast source.
If the source-side RP is enabled to encapsulate register messages in SA messages, when there is a
multicast packet to deliver, the source-side RP encapsulates a register message containing the
multicast packet in an SA message and sends it out. After receiving the SA message, the remote RP