Netgear XCM8806 - 8800 SERIES 6-SLOT CHASSIS SWITCH 사용자 설명서
766
|
Chapter 29. MSDP
NETGEAR 8800 User Manual
To configure the router to reject SA request messages from a specified MSDP peer or all
peers, use the following command:
peers, use the following command:
disable msdp [{peer} <remoteaddr> | peer all] process-sa-request {vr <vrname>}
To display configuration and run-time parameters about MSDP peers, use the following
command:
command:
show msdp [peer {detail} | {peer} <remoteaddr>] {vr <vrname>}
MSDP Mesh-Groups
MSDP can operate in a mesh-group topology. A mesh-group limits the flooding of SA
messages to neighboring peers. In a mesh-group, every MSDP peer must be connected to
every other peer in the group. In this fully-meshed topology, when an SA message is received
from a member of the mesh-group, the SA message is always accepted, but not flooded to
other members of the same group. Because MSDP peers are connected to every other peer
in the mesh-group, an MSDP peer is not required to forward SA messages to other members
of the same mesh-group. However, SA messages are flooded to members of other
mesh-groups. An MSDP mesh-group is an easy way to implement inter-domain multicast, as
it relaxes the requirement to validate looping of MSDP control traffic (that is, peer-RPF
checking is not required). Consequently, SA messages do not loop in the network.
messages to neighboring peers. In a mesh-group, every MSDP peer must be connected to
every other peer in the group. In this fully-meshed topology, when an SA message is received
from a member of the mesh-group, the SA message is always accepted, but not flooded to
other members of the same group. Because MSDP peers are connected to every other peer
in the mesh-group, an MSDP peer is not required to forward SA messages to other members
of the same mesh-group. However, SA messages are flooded to members of other
mesh-groups. An MSDP mesh-group is an easy way to implement inter-domain multicast, as
it relaxes the requirement to validate looping of MSDP control traffic (that is, peer-RPF
checking is not required). Consequently, SA messages do not loop in the network.
Note:
NETGEAR recommends that you configure anycast RP peers in a
mesh topology.
To configure an MSDP mesh-group, use the following command:
create msdp mesh-group <mesh-group-name> {vr <vrname>}
To remove an MSDP mesh-group, use the following command:
delete msdp mesh-group <mesh-group-name> {vr <vrname>}
To display information about an MSDP mesh-group, use the following command:
show msdp [mesh-group {detail} | {mesh-group} <mesh-group-name>] {vr <vrname>}
To configure a peer to be a member of an MSDP mesh-group, use the following command:
configure msdp peer [<remoteaddr> | all] mesh-group [<mesh-group-name> | none]
{vr <vrname>}
To remove a peer from an MSDP mesh-group, use the following command:
configure msdp [{peer} <remoteaddr> | peer all] mesh-group none {vr <vrname>}