HP 7102dl - ProCurve Secure Router Configuration Manual page 697

2.
3.
ProCurve# show ip mroute
IP Multicast Routing Table
Flags:
bit Set,
F - Register, R - RP-bit Set
Timers: Uptime/Expires
(*, G) entry for the
(*, 239.255.1.1), 00:00:48/00:03:08, RP 10.1.1.2, Flags: SC
RP tree
Group address
Figure 13-22. Multicast Routing Table Entry
4.
If you see the group that you are troubleshooting in the list of group
memberships, move to step 3.
If the list of group memberships does not include necessary groups, then
you must troubleshoot IGMP. Remember that you should enable PIM on
LAN interfaces in order for those interfaces to run IGMP. It is also possible
that the problem lies with the host. See Chapter 12: Configuring Multi-
cast Support for a Stub Network for more information on troubleshooting
IGMP.
View the multicast routing table by entering this command:
ProCurve# show ip mroute
The table should include an entry for each multicast group listed in the
router's IGMP group memberships. The entry may be a (*, G) entry, or, if
the router has already received multicast traffic for this group, the entry
may be an (S, G) entry.
Figure 13-22 displays an example of a multicast routing table entry.
S - Sparse, C - Connected, P - Pruned, J - Join SPT, T - SPT-
Incoming interface: fr 1.1, RPF nbr 10.2.2.1
Outgoing interface list:
eth 0/1, Forward, 00:00:48/00:03:08
Downstream interface
If the multicast routing table does not include any entries, then the router
may not be implementing PIM-SM. Enter the following command to verify
that all the local interfaces that should be running PIM-SM are actually
doing so:
ProCurve# show ip pim-sparse interfaces
View the DR for the network that is experiencing the problems. If the local
router is not the DR, it will not forward multicasts for network. You should
troubleshoot the DR. If an interface is down, then you must, of course,
bring it up before it can rejoin the PIM domain.
Configuring Multicast Support with PIM-SM
Troubleshooting PIM-SM
Upstream
neighbor
13-57