The following are the configuration guidelines for 7210 SAS:
On 7210 SAS devices, on ingress of a port, multicast traffic can be processed in the context of either igmp-snooping (Layer 2 Ethernet multicast) or l3-multicast (Layer 3 multicast), but not both. It is not possible to configure SAPs on the port such that one SAP is a receiver for multicast traffic that is processed by IGMP snooping, and the other is the receiver for multicast traffic that is processed by IP multicast in the context of Layer 3 service or RVPLS. An option per port (using the configure>port>ethernet>multicast-ingress {l2-mc | ip-mc} command) is available to enable one or the other. By default, backward compatibility is enabled for IGMP snooping. To allow processing of received multicast traffic as IP multicast in the context of Layer 3 service or RVPLS, the user must explicitly change the default by using the configure>port>ethernet>multicast-ingress command. For more information about the command, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.
On 7210 SAS devices in network mode, on egress of a port, users have an option to configure Layer 2 or Layer 3 multicast replication. That is, with RVPLS IGMPv3 snooping-based multicast, a port on which receivers are present can be configured to do either Layer 2 multicast replication—where IP TTL is not decremented and the source MAC address is not replaced with the 7210 SAS chassis MAC or IP interface MAC address—or Layer 3 multicast replication—where IP TTL is decremented and the source MAC address is replaced. Users have an option to modify this with the configure>port>ethernet>multicast-egress command. For more information about the command, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.
If a VPLS SAP is configured on the port that has IP multicast enabled, then multicast traffic received on the SAP is dropped. Unicast, Broadcast and unknown-unicast packets received on the SAP are forwarded appropriately. This behavior is true only for VPLS SAPs and does not apply to VPLS SDPs, Epipe SAPs, and Epipe SDPs.
7210 SAS platforms can be used as RPs.
Static RP configuration and automatic RP discovery using PIM BSR messages is supported. 7210 SAS-R6 or 7210 SAS-R12 platforms can be configured as candidate RP (or candidate BSR).
It is possible to configure the 7210 SAS as a First Hop Multicast router (FHR) from the source in a PIM-SM network.
7210 SAS devices provide an option to either switch over to the SPT or continue to use the share tree. However, the traffic rate threshold cannot be configured to trigger the switch over.
There is no hardware support for LAG hashing of replicated multicast traffic on 7210 SAS-R6 and 7210 SAS-R12 for IES access interfaces configured on a LAG. On these platforms, to egress on IES access interfaces, software assigns multicast traffic to the member ports of the LAG based on system-defined hash logic. LAG hashing is supported by hardware for multicast traffic on 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and on network port interfaces for 7210 SAS-R6 and 7210 SAS-R12.
RFP check are performed using the unicast routing table. Multicast BGP and multicast routing table are not supported.