Configuring VLAN Stacking Configuring VLAN Stacking Services
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 35-13
sap-profile : default-sap-profile
-> show ethernet-service svlan 300
Service Name : VideoOne
SVLAN : 300
NNI(s) : 2/1, 3/2
SAP Id : 20
UNIs : 1/1, 1/2
CVLAN(s) : 10, 20
sap-profile : sap-video1
SAP Id : 30
UNIs : 1/3
CVLAN(s) : 30, 40
sap-profile : sap-video2
To delete a service from the switch configuration, use the no form of the ethernet-service service-name
command. For example, the following command deletes the “Video-Service” service:
-> no ethernet-service service-name Video-Service
Note that when a VLAN Stacking service is deleted, the SVLAN ID association with the service is
automatically deleted. However, if one or more VLAN Stacking service access point (SAP) are associated
with the service, remove the SAPs first before attempting to delete the service.
Configuring VLAN Stacking Network Ports
The ethernet-service nni command is used to configure a switch port or link aggregate of ports as a
VLAN Stacking Network Network Interface (NNI). For example, the following command configures port
2/1 as an NNI port:
-> ethernet-service nni port 2/1
When a port is converted to a NNI port, the default VLAN for the port is changed to a VLAN that is
reserved for the VLAN Stacking application. At this point, the port is no longer configurable using
standard VLAN port commands.
The ethernet-service nni command is also used to optionally specify the following parameter values that
are applied to traffic proessed by the NNI port:
• tpid—Configures the vendor TPID value for the SVLAN tag. This value is set to the default and is
applied to traffic egressing on the NNI port and is compared to the SVLAN tag of packets ingressing
on the NNI port. If the configured NNI TPID value and the ingress packet value match, then the packet
is considered an SVLAN tagged packet. If these values do not match, then the packet is classified as a
non-SVLAN tagged packet.
• stp legacy-bpdu—Specifies whether or not legacy Spanning Tree BPDU are tunneled on the NNI port.
The following command example configures the vendor TPID for NNI port 2/1 to 0x88a8 and enables
support for Spanning Tree legacy BPDU:
-> ethernet-service nni port 2/1 tpid 88a8 stp legacy-bpdu enable
Consider the following when configuring NNI port parameter values:
• A mismatch of TPID values on NNI ports that are connected together is not supported; VLAN
Stacking will not work between switches using different NNI TPID values.
To Next Page
Loading...
