Extreme Networks ExtremeWare 7.2e, Installation And User Manual

Page: 253 / 344

Multicast Tools
ExtremeWare 7.2e Installation and User Guide 253
should IP address type entries, and the IP address of each entry must be in the class-D multicast
address space, but should not be in the multicast control subnet range (224.0.0.x/24). After you have
created an access profile, use the following command to associate the access profile and filter with a set
of ports:
configure igmp snooping vlan <vlan name> ports <portlist> filter [<access profile> |
none]
To remove the filter, use the
none
option as shown in the following example:
configure igmp snooping vlan <vlan name> ports <portlist> filter none
To display the IGMP snooping filters, use the following command:
show igmp snooping {vlan <vlan name>} filter
Multicast Tools
ExtremeWare provides two commonly available tools to monitor and troubleshoot IP multicast,
mrinfo
and
mtrace
.
Mrinfo
The multicast router information tool, (mrinfo), requests information from a router that could be used
for tracing and troubleshooting. A request is sent to a multicast router, and the router responds with the
following information:
• code version
• system multicast information
• interface information
— interface IP address
— interface multicast capabilities
—
metric configured on the interface
— threshold configured on the interface
— count and IP address of the neighbors discovered on the interface
Use the following command to send an
mrinfo
request:
mrinfo <ip address> {from <ip address>} {timeout <seconds>}
Mtrace
Multicast trace (mtrace) relies on a feature of multicast routers that is accessed using the IGMP protocol.
Since multicast uses reverse path forwarding, a multicast trace is run from the destination to the source.
A query packet is sent to the last-hop multicast router. This router builds a trace response packet, fills in
a report for its hop, and forwards the packet to the next upstream router. As the request is forwarded,
each router in turn adds its own report to the trace response. When the request reaches the first-hop
router, the filled in request is sent back to the system requesting the trace. The request will also be
returned if the maximum hop limit is reached.