Lag Port Membership Constraints; Vpls Feature Support And Restrictions - Alcatel-Lucent 7210 SAS M Service Manual

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.):
•
•
•
•
•
•
•
•
•
•
•
•
7210 SAS M Services Guide
SDPs used in spoke or mesh SDP bindings cannot be configured.
The VPLS service type cannot be a M-VPLS.
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.
VPLS service can use either access SAP or Access-Uplink SAPs.
VPLS service can use the following 'svc-sap-type' values: any, dot1q-preserve and null-
star. Only specific SAP combinations are allowed for a given svc-sap-type, except that
default QinQ SAPs cannot be used in a R-VPLS service. The allowed SAP combinations
are similar to that available in a plain VPLS service and is as given in the table above in
the services Chapter (with the exception noted before).
G8032 or mVPLS/STP based protection mechanism can be used with R-VPLS service. A
separate G8032 control instance or a separate mVPLS/STP instance needs to be used and
the R-VPLS SAPs needs to be associated with these control instances such that the R-
VPLS SAP's forwarding state is driven by the control instance protocols.
IGMP snooping is not supported in a VPLS service.
Virtual Private LAN Services
Page 299