Unrestricted Mac Move - Nokia 7302 Manual

FD 100/320Gbps NT and FX NT IHub Services Guide
5.8.2.6
The VPLS behavior distinguishes between the user side and network side, to secure
control over MAC learning capabilities. MAC learning on regular access ports or on
SDP bindings has by default priority over MACs learned on residential SAPs. That
is, a MAC address learned on a regular port shall not move to a residential port when
learned on that port, while a MAC learned on a residential port shall move to a regular
port when learned/configured on that regular port. This default MAC move behavior
can however be modified.
The following CLI command syntax can be used to enable or unrestricted-mac-move
for a VPLS instance:
configure service vpls <service-id> [no] unrestrict-mac-move
5.8.2.7
In v-VPLS/VPLS/Epipe, each service can be configured to use a dot1q-etype value
other than the port default ether-type by setting a VLAN level ether-type parameter
vlan-dot1q-etype in the context of that service.
This value will be applicable for all the SAPs on that service, where
use-vlan-dot1q-etype is enabled on the underlying ports.
This means, when vlan-dot1q-etype is configured in a service, only the packets
matching this TPID are allowed on all those SAPs where use-vlan-dot1q-etype is
enabled on the underlying ports.
Similarly, all packets that egress out of the service will be tagged with the
dot1q-etype value configured at the VLAN level, for those SAPs on that service,
where use-vlan-dot1q-etype is enabled on the underlying ports.
The following scenarios can occur for ingress traffic on a SAP in true VPLS/Epipe,
when use-vlan-dot1q is disabled on the port:
•
•
•
The following example displays vlan-dot1q-etype configuration:
>configure>service>vpls # info
---------------------------------------------------------------
vlan-dot1q-etype <etype>
Issue: 13

Unrestricted MAC move

Service Dot1q Etype
If traffic egresses out of SDP: ingress traffic TPID does not match with the service
TPID, but matches with the port TPID: FORWARD with extra VLAN tag using
VLAN ID = 0 when egressing out of SDP.
If traffic egresses out of SAP: ingress traffic TPID does not match with the service
TPID, but matches with the port TPID: FORWARD with extra VLAN tag, user tag
preserved and outer tag added with VLAN of egress SAP and service TPID.
In case the ingress control plane traffic TPID does not match with the service
TPID, then it will be dropped.
3HH-11985-AAAA-TQZZA
Virtual Private LAN Service
195