167
Configuring a description for an MSDP peer
This feature helps administrators easily distinguish an MSDP peer from other MSDP peers.
To configure a description for an MSDP peer:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MSDP view.
msdp
[
vpn-instance
vpn-instance-name
]
N/A
3.
Configure a description for
an MSDP peer.
peer peer-address description
text
By default, no description for an
MSDP peer exists.
Configuring an MSDP mesh group
This feature avoids SA message flooding among MSDP peers within an AS. It also simplifies the
RPF check mechanism because you do not need to run BGP or MBGP between these MSDP peers.
When receiving an SA message from outside the mesh group, a member MSDP peer performs the
RPF check on the SA message. If the SA message passes the RPF check, the member MSDP peer
floods the message to the other members in the mesh group. When receiving an SA message from
another member, the MSDP peer neither performs an RPF check on the message nor forwards the
message to the other members.
To organize multiple MSDP peers in a mesh group, assign the same mesh group name to these
MSDP peers. Before doing this, make sure the routers are interconnected with one another.
To configure an MSDP mesh group:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter MSDP view.
msdp
[
vpn-instance
vpn-instance-name
]
N/A
3.
Configure an MSDP mesh
group.
peer peer-address mesh-group
name
By default, an MSDP peer does
not belong to any mesh group.
If you assign an MSDP peer to
multiple mesh groups, the most
recent configuration takes effect.
Controlling MSDP peering connections
MSDP peers are interconnected over TCP (port number 639). You can tear down or re-establish
MSDP peering connections to control SA message exchange between the MSDP peers. When the
connection between two MSDP peers is torn down, SA messages are no longer delivered between
them. No attempt is made to re-establish the connection. The configuration information for the peer
remains unchanged.
MSDP peers periodically send keepalive messages to each other to keep a session alive. When a
session is established, an MSDP peer sends a keepalive message to its peer and starts a keepalive
timer and a peer hold timer. When the keepalive timer expires, the MSDP peer sends a new
keepalive message. If the MSDP peer receives an MSDP message from its peer before the peer hold
timer expires, it resets the peer hold timer. Otherwise, the MSDP peer tears down the session.
A TCP connection is required when one of the following conditions exists:
