Routed VPLS
Page 282 7210 SAS-X, R6 OS Services Guide
Routed VPLS SAPs only Supported on Standard Ethernet Ports
The allow-ip-int-binding flag is set (routing support enabled) on a VPLS service. SAPs within the
service can be created on standard Ethernet ports.
LAG Port Membership Constraints
If a LAG has a non-supported port type as a member, a SAP for the routing-enabled VPLS service
cannot be created on the LAG. Once one or more routing enabled VPLS SAPs are associated with
a LAG, a non-supported Ethernet port type cannot be added to the LAG membership.
VPLS Feature Support and Restrictions
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). The following restrictions apply to both network mode and access-uplink moed unless
called out separately:
• SDPs used in spoke or mesh SDP bindings cannot be configured.
• In access-uplink mode, the VPLS service type cannot be M-VPLS.
• In network mode, the VPLS Service type must be 'r-vpls' and any other VPLS service is
not allowed.
• MVR from Routed VPLS and to another SAP is not supported.
• Default QinQ SAPs is not supported in R-VPLS service.
• The “allow-ip-int-binding” command cannot be used in a VPLS service which is acting as
the G8032 control instance.
• IPv4 filters (ingress and egress) can be used with the R-VPLS SAPs. Additionally IP
ingress override filters are supported which affects the behavior of the IP filters attached to
the R-VPLS SAPs. Please see below for more information about use of ingress override
filters.
• MAC filters (ingress and egress) are not supported for use with R-VPLS SAPs.
• VPLS IP interface is not allowed in a R-VPLS service. The converse also holds.
• In network mode, VPLS service can use the following 'svc-sap-type' values: any.
• In Access-uplink mode, the VPLS service can use either access SAP or Access-Uplink
SAPs. In network mode, the VPLS service can use only access SAPs.