•
If the helper address is "enabled," the interface is running IGMP proxy.
Verify that the helper address is correct in the running config. Also
check connectivity using the ping command. The router must, of
course, be able to reach the multicast device at the central site. If
necessary, troubleshoot a connection. (See the Basic Management
and Configuration Guide, Chapter 6: Configuring the Data Link
Layer Protocol for E1, T1, and Serial Interfaces, Chapter 7: ADSL
WAN Connections, and Chapter 8: Configuring Demand Routing for
Primary ISDN Modules.)
•
In an inactive network, you can add the router stack to the multicast
group (ip igmp join <A.B.C.D>) and use the ping, debug, and
traceroute commands to determine whether the multicast source is
receiving joins from the router.
6.
If the router is receiving messages but is not forwarding them, try viewing
the multicast routing table. Enter:
ProCurve# show ip mroute
It should include the interface that directly connects to the network in
question as an outgoing interface and the upstream interface as the
incoming interface.
If the table does not exist, multicast routing may not be enabled. You must
enable multicast routing in order for downstream interfaces to forward
multicast messages. Enter:
ProCurve(config)# ip multicast-routing
Make sure that you have configured an upstream interface. View the
portion of the running config for the upstream interface (for example,
enter show run int ppp 1) and look for ip mcast-stub upstream.
Configuring Multicast Support for a Stub Network
Troubleshooting Multicast Stub Routing and IGMP
12-25