Alcatel-Lucent 1643 AMS User's Operation Manual page 430

Traffic provisioning
In the IEEE 802.1Q STP virtual switch mode and in the provider bridge mode, the port
role of each LAN and WAN port can be flexibly assigned. Each LAN or WAN port
can be configured to be either a customer-role or network-role port.
These are the characteristics of customer-role and network-role ports:
In the IEEE 802.1Q STP virtual switch
mode:
In the ingress direction, untagged Ethernet
frames are tagged with a default identifier,
the port VLAN identifier (PVID). The
PVID is removed from each frame at each
network egress port. See also:
802.1Q VLAN tagging" (p. 8-69)
In the provider bridge mode:
A provider bridge tag carrying a customer
identifier (CID) is inserted into each
Ethernet frame in the ingress direction,
and removed from the frame in the
reverse direction. Frames that are already
tagged become double tagged. See also:
"IEEE 802.1ad VLAN tagging" (p. 8-69)
The spanning tree protocol (STP) is not
supported.
GVRP is not supported.
VLAN IDs or CIDs need to be configured
manually.
Ingress rate control exists at "UNI" and
"E-NNI" ports only (see
Service (QoS) overview" (p.
Fix port-role assignment in the VPN tagging modes
In all the operational modes relying on the VPN tagging mode (see
tagging" (p.
• LAN ports are always customer role ports.
• WAN ports are always network role ports.
....................................................................................................................................................................................................................................
8-78
Customer-role port
"IEEE
"Quality of
8-81)).
8-68)) the port role is fixed:
Alcatel-Lucent - Proprietary
See notice on first page
Network-role port
No tagging or untagging operations are
performed.
The spanning tree protocol (STP) can be
enabled (default setting) or disabled.
GVRP can be enabled (default setting) or
disabled.
Dynamic VLAN IDs or CIDs of
intermediate and access nodes are
automatically configured if GVRP is
enabled.
There is no rate control on "I-NNI" ports.
The traffic class encoded in the p1 and p2
bits of the incoming frames is evaluated
and transparently passed through.
Port provisioning
"Transparent
365-312-807R7.2
Issue 4, May 2007