Effects of a multicast boundary on link local multicast?

Unanswered Question
Mar 23rd, 2007

Hello community,

Does the use of a multicast boundary that does not explicitly allow 224/8 also stop link local mcast packets for say EIGRP, OSPF, PIM RP announce, etc ,etc.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

use IP multicase boundary command and match require trafic using access-list.

IP multicase boundary command to configure an administratively scoped boundary on an interface to filter multicast group addresses in the range defined by the access-list argument.

A standard access list defines the range of addresses affected. When this command is configured, no multicast data packets are allowed to flow across the boundary from either direction. Restricting multicast data packet flow enables reuse of the same multicast group address in different administrative domains.

If you configure the filter-autorp keyword, the administratively scoped boundary also examines Auto-RP discovery and announcement messages and removes any Auto-RP group range announcements from the Auto-RP packets that are denied by the boundary ACL. An Auto-RP group range announcement is permitted and passed by the boundary only if all addresses in the Auto-RP group range are permitted by the boundary ACL. If any address is not permitted, the entire group range is filtered and removed from the Auto-RP message before the Auto-RP message is forwarded.

Actions

This Discussion