Device Online Help

sVLAN UNI and NNI ports

The ports in the switch can be configured as sVLAN user-to-network interface (UNI), sVLAN network-to-network interface (NNI), or normal.

Note: You must change the switch level to 1 or above before you configure sVLAN UNI or NNI ports.

You must configure the ports to which you want to provide VLAN transparency as UNI ports. UNI ports can only belong to one sVLAN. When you configure a UNI port in the CLI, the tagged-frames-discard parameter is automatically enabled.

NNI ports interconnect the switches in the core network, drop untagged frames on ingress, and insert the sVLAN tag at the egress. NNI ports can belong to multiple sVLANs. An NNI port sends sVLAN tagged frames. When you configure an NNI port in the CLI, the untagged-frames-discard parameter is automatically enabled.

• If a Spanning Tree Group (STG) contains both UNI and NNI ports, you should change the standardized MAC addresses used for BPDUs to a non-standardized BPDU MAC address to avoid interference with regular customer BPDUs.
• The UNI and NNI ports are kept in sVLAN type STG.
• All of the ports in the MLT should have the same port type (normal/UNI/NNI).
• Large frame support is automatically enabled on UNI/NNI ports.

When you change the sVLAN port type from normal to UNI/NNI, all the affected ports are removed from the configured STGs and VLANs. Similarly, when you change the sVLAN port type from UNI/NNI to normal, all the affected ports are removed from the configured STGs and VLANs and added to the default STG and default VLAN.  

Note: The affected ports are all the ports in the Octapid.

Note: An NNI port belonging to default VLAN and default STG is not saved across reboots. To avoid this, do not configure an NNI port under default VLAN/STG.

• sVLAN Levels
• sVLAN rules
• Configuring sVLAN
• About stacked VLANs
• About VLANs