Static Mroute - Avaya 8800 Planning And Engineering, Network Design

Multicast network design
You can configure the RP to filter which sources it describes in SA messages. You can use
Message Digest (MD) 5 authentication to secure control messages.
Avaya Ethernet Routing Switch 8800/8600 supports the MSDP management information base (MIB)
as described in RFC 4624.

Static mroute

The Avaya Ethernet Routing Switch 8800/8600 supports a static IP route table to separate the paths
for unicast and multicast streams. Only multicast protocols use this table. Adding a route to this
table does not affect the switching or routing of unicast packets.
The entries in this table use the following attributes:
• IP prefix or IP mask—the destination network for the added route
• Reverse Path Forwarding (RPF) address—the IP address of the RPF neighbor towards the
rendezvous point (RP) or source
• route preference—the administrative distance for the route
If the unicast routing table and the multicast-static IP route table use different routes for the
same destination network, the system compares the administrative distance with that of the
protocol that contributed the route in the unicast routing table.
• route status—the status, either enabled or disabled, of the route in the table
The following figure shows an example of static mroute configured in a network.
Figure 103: Static mroute
June 2016 Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
216