The protocols that use IP multicast, for example, Universal Plug and Play (uPnP), cause performance issues in the network as they generate many changes in the Intermediate-System-to-Intermediate-System (IS-IS) Link State Database (LSDB). To address the network issues, the IP SPB Multicast Policy feature aggregates multiple multicast groups (senders or receivers) in a static data I-SID that you configure in GRT/VRF, by associating the IP SPB Multicast Policy with a route-map. You can also configure filtering on the multicast groups based on the traffic flow (senders only or receivers only) using the IP SPB Multicast Policy feature.
When IP SPB Multicast Policy matches the sender‘s multicast group IP address, the following list identifies potential IP multicast stream behavior:
Dropped.
Forwarded as one dynamic data I-SID per stream (pre-existing design).
Forwarded as multiple IPMC streams mapped to the same static data-ISID.
The following list identifies restrictions of an IP SPB Multicast Policy :
This feature is not supported on:
IGMP snooping
Distributed Virtual Routing (DvR) leaf
Multi-area SPB boundary nodes with remote IS-IS enabled do not support IP SPB Multicast Policy .
Multi-area SPB boundary nodes do not support static data I-SID configuration. However, it can redistribute the static data I-SID with MAC learning disabled.
The system ignores the include and exclude lists for IGMPv3 membership reports and forwards all traffic that is received in the static data I-SID to the receiver.
This feature is not compatible with multicast traffic processed on a PIM GW interface and will not influence its behavior.