Pim Neighbors - HP 7102dl - ProCurve Secure Router Configuration Manual

Debug messages
when the router
receives an
IGMP join for a
new group.
Periodic join/
prunes are sent
for each
multicast route
entry, by
default, every
30 seconds.
N o t e
You can also enter show ip pim-sparse traffic to verify that the router
is sending join/prune messages. If you want to see the actual messages
being sent then you must use the debug ip pim-sparse joinprune
command as shown in Figure 13-27.
ProCurve# debug ip pim-sparse joinprune
PIMSM: Upstream JoinPrune state for (*, 239.255.1.1) [
NotJoined --> Join]; Event=JoinDesired
09:30:54: PIMSM: Sent JOIN (*, 239.255.1.1) to 10.2.2.1
09:30:54: PIMSM: Downstream JoinPrune state for (*, 239.255.1.1, eth
0/1) [NoInfo --> Join]; Event=ReceivedJoin
09:44:21: PIMSM: Sent JOIN (*, 224.0.1.22) to 10.1.1.2
09:44:23: PIMSM: Sent JOIN (*, 239.255.1.1) to 10.1.1.2
Figure 13-27. Viewing Real-Time Join/Prune Messages
If the router does not seem to be sending messages, try returning the join/
prune interval to its default setting. Move to the PIM sparse configuration
mode context and enter this command:
ProCurve(config-pim-sparse)# no join-prune-msg-interval
If you complete these steps and cannot find the problem, you must trouble-
shoot your router in conjunction with other routers in the domain.
Troubleshooting A Router in Conjunction with Its PIM
Neighbors
These instructions assume that you have access to all routers in the PIM
domain. If you do not, then you may need to request information from a
network administrator at a remote site.
You should first determine whether the local router and its neighbors have
selected the same RP for the multicast group.
Configuring Multicast Support with PIM-SM
Troubleshooting PIM-SM
The router sends a join to its
upstream RP neighbor.
13-61