Alcatel-Lucent 7210 SAS-X - VPLS SAP Ingress IP Filter Override

Virtual Private LAN Services
7210 SAS-X, R6 OS Services Guide Page 283
• In Access-uplink mode, 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. IP multicast is not supported in the R-
VPLS service.
• DHCP snooping is not supported for the SAPs configured in the routed VPLS service.
Instead, DHCP relay can be enabled on the IES service associated with the routed VPLS
service.
VPLS SAP Ingress IP Filter Override
When an IP Interface is attached to a VPLS service context, the VPLS SAP provisioned IP filter
for ingress routed packets may be optionally overridden in order to provide special ingress
filtering for routed packets. This allows different filtering for routed packets and non-routed
packets. The filter override is defined on the IP interface bound to the VPLS service name. A
separate override filter may be specified for IPv4 packet types.
If a filter for a given packet type (IPv4) is not overridden, the SAP specified filter is applied to the
packet (if defined).