29-16
Cisco ASA 5500 Series Configuration Guide using ASDM
Chapter29 Configuring Multicast Routing
Customizing Multicast Routing
Step2 Double-click an entry in the PIM Bidirectional Neighbor Filter table to open the Edit Bidirectional
Neighbor Filter Entry dialog box for that entry.
Step3 Choose the PIM neighbor that you want to configure from the table by clicking Add/Edit/Insert.
The Add/Edit/Insert Bidirectional Neighbor Filter Entry dialog box appears, which lets you create ACL
entries for the PIM bidirectional neighbor filter ACL
Step4 Choose the interface name from the Interface Name drop-down list. Select the interface for which you
are configuring the PIM bidirectional neighbor filter ACL entry.
Step5 From the Action drop-down list, choose Permit or Deny for the neighbor filter ACL entry.
Choose Permit to allow the specified devices to participate in the DF election process. Choose Deny to
prevent the specified devices from participating in the DF election process.
Step6 In the IP Address text field, enter the IP address of the multicast PIM group being permitted or denied.
Valid group addresses range from 224.0.0.0 to 239.255.255.255.255.
Step7 From the Netmask drop-down list, choose the netmask for the multicast group address.
Step8 Click OK.
Configuring a Multicast Boundary
Address scoping defines domain boundaries so that domains with RPs that have the same IP address do
not leak into each other. Scoping is performed on the subnet boundaries within large domains and on the
boundaries between the domain and the Internet.
You can set up an administratively scoped boundary on an interface for multicast group addresses by
choosing Configuration > Routing > Multicast > MBoundary in ASDM. IANA has designated the
multicast address range from 239.0.0.0 to 239.255.255.255 as the administratively scoped addresses.
This range of addresses can be reused in domains administered by different organizations. The addresses
would be considered local, not globally unique.
A standard ACL defines the range of affected addresses. When a boundary is set up, no multicast data
packets are allowed to flow across the boundary from either direction. The boundary allows the same
multicast group address to be reused in different administrative domains.
You can configure, examine, and filter Auto-RP discovery and announcement messages at the
administratively scoped boundary . Any Auto-RP group range announcements from the Auto-RP packets
that are denied by the boundary ACL are removed. 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.
To configure a multicast boundary, perform the following steps:
Step1 In the main ASDM window, choose Configuration> Routing > Multicast > MBoundary.
The MBoundary pane lets you configure a multicast boundary for administratively scoped multicast
addresses. A multicast boundary restricts multicast data packet flows and enables reuse of the same
multicast group address in different administrative domains. When a multicast boundary is defined on
an interface, only the multicast traffic permitted by the filter ACL passes through the interface.
Step2 Click Edit.