OmniSwitch

Overview

CAUTION Service Disruption

OmniSwitch devices do not support automatic synchronization with the NFM-P database when you use the CLI to make configuration changes.

To ensure that you are viewing accurate OmniSwitch information in the NFM-P, you must resynchronize the NE by clicking on the appropriate Resync button.

OmniSwitch NEs do not send trap notifications for all MIB changes on the NE. To ensure that you are viewing the current configuration information in the NFM-P, you must resynchronize the NE by clicking on the appropriate Resync button.

The OmniSwitch family of devices is a group of Enterprise and Metro Ethernet LAN switches. The NFM-P supports the OmniSwitch chassis types listed in the NSP NFM-P Network Element Compatibility Guide.

OmniSwitch LAG objects

OmniSwitch NEs support static and dynamic LAGs. When you create a static LAG, you can add ports as LAG members. The ports that you select as members of a dynamic LAG are first placed into an Unassigned Dynamic LAG Members group. The OmniSwitch uses LACP to dynamically assign ports from an Unassigned Dynamic LAG Members group to the appropriate LAG. When a port is assigned to a dynamic LAG, the port is removed from the Unassigned Dynamic LAG Members group.

You can create VLANs, use 802.1Q framing, configure QoS conditions, and enable other networking functions on a LAG, which is treated the same as a physical link.

OmniSwitch LAG support includes:

• up to 32 LAGs on an OS 6250, OS 6400, OS 6450, OS 6465, OS 6850, OS 6850E, OS 6855, or on a stack of OmniSwitch devices

• up to 128 LAGs on an:

  • OS 9600, OS 9700, and OS 9800

  • OS 9700E, or OS 9800E

  • OS 10K

  • OS 6860, OS 6860E, OS 6860N, OS 6865, or OS 6900

• two, four, or eight Ethernet links in a LAG

• access or network LAGs

Using WebView to manage an OmniSwitch

You can configure and manage an OmniSwitch using the WebView application, a web-based EM tool that runs on an OmniSwitch. See theNSP Planning Guide for information about browser compatibility.

Note: You must enable cookies and Java in the web browser that you use to open WebView.

See the appropriate OmniSwitch Switch Management Guide for information about configuring and using WebView. See Chapter 12, Device object configuration for information about opening WebView using the GUI.

OmniSwitch port modes

The ports of OmniSwitch NEs can operate in either access mode or network mode. Access ports can be added to stacked VLANs as UNI ports, or to standard VLANs as tagged or untagged ports. Network ports can automatically bind to stacked VLANs as NNI ports when the service is created. OmniSwitch NEs using AOS Release 6.4.6 or later, or AOS Release 6.6.5 or later, can operate in hybrid mode. Hybrid ports can be added to standard VLANs as tagged or untagged ports, and also bind to all stacked VLANs on an NE as NNI ports.

Note: When a port is changed to hybrid mode, any previous UNI associations will be deleted.

OmniSwitch splitter ports

The NFM-P supports splitter ports and sub-ports where equipped on OmniSwitch devices (typically, QSFP+ ports). Sub-ports are identified by the CLI Name parameter on the port properties form.