Configuring Vlan Stacking Network Ports; Configuring Nni Port Parameters - Alcatel-Lucent OmniSwitch 6850-48 Network Configuration Manual

Configuring VLAN Stacking Services
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 servic-name Video-Service
Note that when a VLAN Stacking service is deleted, the SVLAN or IMPVLAN 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 svlan nni
VLAN Stacking Network Network Interface (NNI) and associate the NNI with an SVLAN. Note that NNI
ports are not associated with IP Multicast VLANs. For example, the following command configures port
2/1 as an NNI port and associates 2/1 with SVLAN 300:
-> ethernet-service svlan 300 nni 2/1
When a port is associated with an SVLAN using this command, the port is automatically defined as an
NNI to carry traffic for the specified SVLAN. In addition, 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 config-
urable using standard VLAN port commands.
To delete an NNI port association with an SVLAN, use the no form of the ethernet-service svlan nni
command. For example, the following command deletes the NNI 2/1 and SVLAN 300 association:
-> no ethernet-service svlan 300 nni 2/1
Note that when the last SVLAN association for the port is deleted, the port automatically reverts back to a
conventional switch port and is no longer VLAN Stacking capable.
Use the show ethernet-service port

Configuring NNI Port Parameters

The ethernet-service nni
processed by NNI ports:
•
tpid—Configures the vendor TPID value for the SVLAN tag. This value is set to 0x8100 by 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 clas-
sified as a non-SVLAN tagged packet.
•
gvrp legacy-bpdu—Specifies whether or not legacy GVRP BPDU are tunneled on the NNI port.
GVRP BPDU are dropped by default.
•
stp legacy-bpdu—Specifies whether or not legacy Spanning Tree BPDU are tunneled on the NNI port.
Spanning Tree BPDU are dropped by default.
•
transparent-bridging—Configures the transparent bridging status for the NNI port. When transparent
bridging is enabled, the NNI forwards SVLAN traffic without processing packet contents. As a result,
the NNI port can also forward traffic for SVLANs that are not configured on the local switch, thus
allowing for a greater number of NNI port associations with SVLANs. Enabling transparent bridging is
recommended only on NNI ports that are known to and controlled by the network administrator.
page 9-14
command is used to configure a switch port or link aggregate of ports as a
command to verify the NNI port configuration for the switch.
command is used to configure the following parameters that apply to traffic
OmniSwitch AOS Release 6 Network Configuration Guide
Configuring VLAN Stacking
September 2009