Configuring Multicast Support with PIM-SM
Troubleshooting PIM-SM
11-66
RouterA# show ip pim-sparse rp-set
Group address
Static-RP-address
-----------------------------------
rp1
rp2
rp3
RouterA# show access-lists
Standard IP access list rp1
permit host 239.255.255.1 (1 matches)
Standard IP access list rp2
deny
host 239.255.255.1 (1 matches)
permit 224.0.0.0 15.255.255.255 (3 matches)
permit 224.0.0.0 7.255.255.255 (0 matches)
Standard IP access list rp3
deny
host 239.255.255.1 (0 matches)
permit 232.0.0.0 7.255.255.255 (1 matches)
Figure 11-33. Fixing a Misconfigured ACL
To fix the ACL so that Router A selects the correct RP for multicast group
239.255.255.200, you would enter these commands:
ProCurve(config)# ip access-list standard rp2
ProCurve(config-std-nacl)# no permit 224.0.0.0 15.255.255.255
Figure 11-34 shows another misconfigured RP set. The PIM domain in this
example uses the RP at 10.1.1.2 to support half of the multicast groups and
the RP at 10.3.3.2 to support the others. The administrator for Router A used
extended ACLs instead of standard ACLs and entered the group address as a
destination rather than a source. However, routers use the source address in
an RP's ACL to determine which groups the RP supports.
10.1.1.1
10.1.1.2
10.3.3.2
Remove this
statement.
Need help?
Do you have a question about the ProCurve Secure Router 7203 dl and is the answer not in the manual?
Questions and answers