Alcatel-Lucent 6850-48 Guida Di Rete
Configuring VLAN Stacking Services
Configuring VLAN Stacking
page 9-18
OmniSwitch AOS Release 6 Network Configuration Guide
September 2009
For example, the following command specifies that all untagged frames and frames tagged with CVLAN
ID 500 is accepted on UNI ports associated with SAP 20:
ID 500 is accepted on UNI ports associated with SAP 20:
-> ethernet-service sap 20 cvlan 500 untagged
Use the no form of the ethernet-service sap cvlan command to delete an association between customer
traffic and a VLAN Stacking SAP. For example, the following command deletes the association between
CVLAN 500 and SAP 20:
traffic and a VLAN Stacking SAP. For example, the following command deletes the association between
CVLAN 500 and SAP 20:
-> ethernet-service sap 20 no cvlan 500
Note that when the last customer traffic association is deleted from a SAP, the SAP itself is not automati-
cally deleted. No traffic is accepted or processed by a SAP in this state, but the SAP ID is still known to
the switch.
cally deleted. No traffic is accepted or processed by a SAP in this state, but the SAP ID is still known to
the switch.
Consider the following when configuring the type of customer traffic to tunnel:
• If no customer traffic is associated with a VLAN Stacking SAP, then the SAP does not process any
traffic for the service.
• Only one all or untagged designation is allowed for any given SAP; specifying both for the same SAP
is not allowed.
• Only one untagged designation is allowed per UNI port, even if the UNI port is associated with multi-
ple SAPs.
• Only one all designation is allowed per UNI port, even if the UNI port is associated with multiple
SAPs.
• Associating customer traffic with a service using an IP Multicast VLAN (IPMVLAN) is not allowed.
Use the
command to display the type of customer traffic associated with each SAP
configured for the switch
Configuring a Service Access Point Profile
command is used to create a VLAN Stacking service access point (SAP)
profile. The SAP profile defines the following traffic engineering attributes that are applied to customer
traffic that is accepted on the SAP UNI ports.
traffic that is accepted on the SAP UNI ports.
• Ingress bandwidth sharing. Specifies if bandwidth is shared across UNI ports and CVLANs. Band-
width is shared by default.
• Ingress rate limiting. Specifies in bits per second the rate at which customer frames ingress on UNI
ports. The ingress bandwidth limit is set to 10 mbps by default.
• Double-tag or translate. Determines if a customer frame is tagged with the SVLAN ID (double-tag)
or the CVLAN ID is changed to the SVLAN ID (translate) when the frame is encapsulated for tunnel-
ing. Double-tag is used by default.
ing. Double-tag is used by default.
• Priority mapping. Determines if the CVLAN (inner tag) 802.1p or DSCP value is mapped to the
SVLAN (outer tag) 802.1p value or if a fixed priority value is used for the SVLAN 802.1p value. Prior-
ity mapping is set to a fixed rate of zero by default.
ity mapping is set to a fixed rate of zero by default.
A default profile, named “default-sap-profile”, is automatically assigned to the SAP at the time the SAP is
created (see
created (see
). It is only necessary to
create a new profile to specify different attribute values if the default profile values (see above) are not
sufficient.
sufficient.