When the allow-ip-int-binding flag is set on a VPLS service, the following features cannot be enabled (the flag also cannot be enabled while any of these features are applied to the VPLS service):
In network mode, SDPs used in spoke or mesh SDP bindings cannot be configured.
In network mode, the VPLS service type must be R-VPLS; no other VPLS service is allowed.
MVR from an R-VPLS SAP to another SAP is not supported.
Default QinQ SAPs are not supported in an R-VPLS service.
The allow-ip-int-binding command cannot be used in a VPLS service that is acting as the G.8032 control instance.
IPv4 filters (ingress and egress) can be used with R-VPLS SAPs. Additionally IP ingress override filters are supported, which affects the behavior of the IP filters attached to the R-VPLS SAPs.
MAC filters (ingress and egress) are not supported for use with R-VPLS SAPs.
A VPLS IP interface is not allowed in an R-VPLS service, and an R-VPLS service/SAP cannot be configured with a VPLS IP interface.
In network mode, the R-VPLS service can be configured only with access SAPs or with SAPs on hybrid ports (applies only to the 7210 SAS-R6 and 7210 SAS-R12).
In network mode, the VPLS service can use the following svc-sap-type values: any, null-star, and dot1q-preserve.
G.8032 or MVPLS/STP based protection mechanisms can be used with an R-VPLS service. A separate G.8032 control instance or a separate MVPLS/STP instance must be used and the R-VPLS SAPs must be associated with these control instances such that the R-VPLS SAP forwarding state is driven by the control instance protocols
IP multicast is not supported in an R-VPLS service.
IGMP snooping is supported in an R-VPLS service for 7210 SAS-R6 and 7210 SAS-R12.
DHCP snooping is not supported for the SAPs configured in an R-VPLS service. Instead, DHCP relay can be enabled on the IES service associated with the R-VPLS service.
In network mode, an R-VPLS SAP drops packets received with extra tags. That is, if a packet is received on a R-VPLS SAP, with number of tags greater than the SAP tags to which it is mapped, then it is dropped. This is true for all supported encapsulations (that is, null, dot1q, and QinQ encapsulations) of the port. For example, double-tagged packets received on a dot1q SAP configured in a R-VPLS service is dropped on ingress.