The following items apply to IGMP snooping in R-VPLS and should be included with the regular VPLS multicast configuration guidelines (see Configuration guidelines for IGMP snooping in VPLS service and Routed VPLS supported functionality and restrictions):
R-VPLS without an IP interface association can be used to emulate VPLS service with support for IGMPv3 snooping.
R-VPLS with or without IP interface association can be used for IGMPv3 snooping. If enabling MVR on the service then the service should not have an IP interface association.
IGMPv3 snooping can be enabled in the context of the R-VPLS (both with and without MVR). It cannot be enabled in regular VPLS service. Regular VPLS service supports IGMP v1 and v2 only.
MVR can be configured in an R-VPLS without an IP interface association. It can be used to leak multicast traffic to a user R-VPLS service with an IP interface configuration. Therefore, a user R-VPLS can be used to forward both unicast and multicast services.
In addition, the following list of guidelines and restrictions pertain to IGMP snooping in an R-VPLS service:
R-VPLS service can only have a single SAP per port configured in a service. That is, two SAPs on the same port cannot be configured in the same service.
Spoke SDPs and mesh SDPs cannot be configured in an R-VPLS service.
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 with IGMP v1 or v2 snooping) or l3-multicast (either multicast in an Layer 3 service or IGMP snooping in an R-VPLS), but not both. That is, it is not possible to configure SAPs on the port such that one SAP is a receiver for multicast traffic to be processed by IGMP snooping, and another SAP is a receiver for multicast traffic to be processed by IP multicast in the context of Layer 3 service or R-VPLS. An option per port is available using the configure>port>ethernet>multicast-ingress {l2-mc | ip-mc} command to enable one or the other. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about this command. By default, IGMP snooping is enabled to be backward compatible. Users need to explicitly change the IGMP snooping configuration to allow processing of received multicast traffic as IP multicast in the context of Layer 3 service or R-VPLS.
If a VPLS SAP is configured on the same port as the port on which IP multicast is 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.
With R-VPLS multicast, a port on which receivers are present can be configured to perform either Layer 2 multicast replication (that is, no IP TTL decrement and no source MAC replacement) or Layer 3 multicast replication (that is, IP TTL is decremented and source MAC is replaced with 7210 SAS chassis MAC or IP interface MAC). An option to use either Layer 2 or Layer 3 multicast replication is available using the configure>port>ethernet>multicast-egress {l2-switch | l3-forward} command. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about this command. All SAPs on the port have the same behavior.
An MVR R-VPLS must be configured without an IP interface and supports Layer 2 forwarding of both unicast and multicast traffic (that is, no IP forwarding).
A user R-VPLS can be configured with an IP interface and supports Layer 2 forwarding of both unicast and multicast (with (S,G) IP multicast replications) and supports Layer 3 forwarding of unicast traffic.
On 7210 SAS-R6, when using SAP-based egress queues and scheduler, R-VPLS BUM traffic uses per port egress queues—not per SAP egress queues.
In an MVR configuration, the svc-sap-type of the R-VPLS service that is the source (also known as MVR R-VPLS service) and the svc-sap-type of the R-VPLS service that is the sink (also known as user R-VPLS service) should match.
On 7210 SAS-R6 and 7210 SAS-R12, the MVR R-VPLS service configured with IGMPv3 snooping shares resources with TWAMP. An increase in one decreases the amount of resources available for the other. Contact your Nokia representative for more information about scaling of these features.