Enabling Trace Messages For Igmp Layer 2 Querier Troubleshooting; Troubleshooting Static Mroute - Avaya 8800 Troubleshooting Manual

IGMP snoop and IGMP Layer 2 querier must be enabled for the feature to function.

Enabling trace messages for IGMP Layer 2 querier troubleshooting

If the preceding information does not address your issue, you can also use the following trace
command to view additional information related to Layer 2 querier:
trace level 23 <1-4>

Troubleshooting static mroute

Multicast routing protocols like PIM-SM, PIM-SSM, and MSDP rely on unicast routing protocols
to perform Reverse Path Forwarding (RPF) checks to avoid loops in forwarding multicast data.
As a result, multicast streams are forced to share network paths with the unicast traffic streams.
You generally cannot separate the paths for multicast and unicast data streams.
The static mroute feature allows you to configure separate paths for unicast and multicast
streams. To do so, the feature provides a configurable static IP route table. This table is used
only by the multicast routing protocols and is not visible to any other protocols. Any routes
added to the static IP route table do not affect the switching and routing of IP unicast
packets.
An entry in this static IP route table has the following attributes:
• IP prefix/mask denotes the destination network for which the route is being added.
• RPF address is the equivalent in multicast to the next-hop in the unicast static IP route
table. Here it denotes the RPF neighbor towards the RP or source.
• Preference is the administrative distance for the given route. When the unicast routing
table and the multicast static IP route table have different routes for the same destination
network, this administrative distance is compared with that of the protocol that contributed
the route in the unicast routing table. By configuring the administrative distance for
different routes, the administrator can choose different distances for different networks.
• Status indicates the status of the route in this table, and can be enabled and disabled
using CLI or ACLI commands.
The logic used for static mroute selection is as follows:
• Direct and local routes for a given destination take precedence over any route for the
same destination in the multicast static IP route table.
• If a route is present in the multicast static IP table, and no route exists in the unicast routing
table for the given destination, the route in the multicast static IP table is used.
• If no route exists in the multicast static IP route table for the given destination, then the
route from the unicast routing table is used, if available.
Troubleshooting
Troubleshooting static mroute
July 2013 371