HP 7102dl - ProCurve Secure Router Configuration Manual page 705

Note the difference in Router B's ACL for the RP at 10.1.1.2. On Router B, this
RP only supports the half of all possible multicast groups (224.0.0.0 through
231.255.255.255) rather than all of the groups. Figure 13-32 shows which RPs
Router A and B have actually selected for each active group.
RouterA# show ip pim-sparse rp-map
Number of group-to-RP mappings: 5
Group address
------------------------------------------
224.0.1.22
224.1.1.1
239.255.255.1
239.255.255.10
239.255.255.200
RouterB# show ip pim-sparse rp-map
Number of group-to-RP mappings: 5
Group address
------------------------------------------
224.0.1.22
224.1.1.1
239.255.255.1
239.255.255.10
239.255.255.200
Figure 13-32. Viewing Active RPs in an RP Map
Because Router A allows RP 10.1.1.2 to support all groups, Router A has
selected this RP for multicast group 239.255.255.200. Router B, which has an
RP set that prohibits RP 10.1.1.2 from supporting this group, selected RP
10.3.3.2. You can view the access lists configured on Router A once again to
find the error. (See Figure 13-33.)
In this example, the administrator who configured the ACL for RP 10.1.1.2
accidently made the RP support all groups. The administrator then attempted
to correct the error, but forgot to remove the faulty permit statement. (See
Figure 13-33.)
Configuring Multicast Support with PIM-SM
RP address
10.1.1.2
10.1.1.2
10.1.1.1
10.3.3.2
10.1.1.2
The RP for this group is different
on Router A and Router B.
RP address
10.1.1.2
10.1.1.2
10.1.1.1
10.3.3.2
10.3.3.2
Troubleshooting PIM-SM
13-65