Netgear XCM8810 - 8800 SERIES 10-SLOT CHASSIS SWITCH ユーザーズマニュアル
Chapter 29. MSDP
|
763
NETGEAR 8800 User Manual
For example, as businesses expand and networks grow in size, it might become necessary
to connect PIM domains to allow multicast applications to reach other offices across the
network. MSDP simplifies this process by providing a mechanism to connect those multicast
routing domains without reconfiguring existing domains. Each PIM domain remains separate
and has its own RP. The RP in each domain establishes an MSDP peering relationship over
a TCP connection either with RPs in other domains or with border routers leading to other
domains. When an RP learns about a new multicast source in its own domain (using the
normal PIM registration process), it then sends a SA message to all of its MSDP peers,
letting them know about the new stream. In this way, the network can receive multicast traffic
from all over the network without having to reconfigure each existing PIM domain.
to connect PIM domains to allow multicast applications to reach other offices across the
network. MSDP simplifies this process by providing a mechanism to connect those multicast
routing domains without reconfiguring existing domains. Each PIM domain remains separate
and has its own RP. The RP in each domain establishes an MSDP peering relationship over
a TCP connection either with RPs in other domains or with border routers leading to other
domains. When an RP learns about a new multicast source in its own domain (using the
normal PIM registration process), it then sends a SA message to all of its MSDP peers,
letting them know about the new stream. In this way, the network can receive multicast traffic
from all over the network without having to reconfigure each existing PIM domain.
Supported Platforms
MSDP is supported on NETGEAR 8800 running a firmware with the Core license.
Our implementation of MSDP is compliant with RFC 3618 and RFC 3446, and compatible
with other devices that are compliant with these standards.
with other devices that are compliant with these standards.
Limitations
The limitations of MSDP are as follows:
•
There is no support for MSDP operating with SA cache disabled (transit node). MSDP will
always cache/store received SA messages.
•
There is no support for logical RP.
•
There is no support for MSDP on user-created virtual routers (VRs).
•
RIP routes are not used for peer-RPF checking. So, our implementation of MSDP does
not exactly conform to rule (iii) in section 10.1.3 of RFC 3618. However, our
implementation of MSDP uses BGP/OSPF for peer-RPF checking as per rule (iii) in
section 10.1.3.
implementation of MSDP uses BGP/OSPF for peer-RPF checking as per rule (iii) in
section 10.1.3.
•
Read-write/read-create access is not supported on MSDP MIB objects.
PIM Border Configuration
To create a PIM-SM domain for MSDP, you must restrict the reach of Bootstrap Router (BSR)
advertisements by defining a VLAN border. BSR advertisements are not sent out of a PIM
interface configured as a VLAN border, thereby defining a PIM domain for MSDP.
advertisements by defining a VLAN border. BSR advertisements are not sent out of a PIM
interface configured as a VLAN border, thereby defining a PIM domain for MSDP.
To configure a PIM VLAN border, use the following command:
configure pim <vlan_name> border