3Com WX3000 Logging In Through OAP, OAP Overview, Logging In to the Switching Engine Through OAP

2 Logging In Through OAP

OAP Overview

As an open software and hardware system, Open Application Architecture (OAA) provides a set of complete standard software and hardware interfaces. The third party vendors can develop products with special functions. These products can be compatible with each other as long as they conform to the OAA interface standards. Therefore the functions of single network product can be expanded and the users can get more benefits.

Open Application Platform (OAP) is a physical platform developed based on OAA. It can be an independent network device, or a board or program used as an extended part of a device. An OAP runs an independent operating system. You can load software such as security and voice in the operating system as needed.

Logging In to the Switching Engine Through OAP

You can log in to the access control engine through the console port on the device and perform the following configurations on the access control engine. Then, you can log in to the switching engine.

1)Execute the oap connect slot 0 command in user view of the access control engine to log in to the

switching engine.

<device> oap connect slot 0

Connected to OAP!

2)Press Enter to enter user view of the switching engine.

<device_LSW>

zTo distinguish between the access control engine and the switching engine, the name of the switching engine is changed to device_LSW here. In fact, the default name of the switching engine is device.

zYou can press Ctrl+K to return to the command line interface of the access control engine.

Configuring the Management IP Address of the OAP Software System

In the OAA system of the device, the access control engine and the switching engine integrate together and function as one device. For the snmp UDP Domain-based network management station (NMS), however, the access control engine and the switching engine are independent SNMP agents. Physically, two agents are on the same managed object; while logically, they belong to two different systems, and they manage their own MIB objects on the access control engine and the switching engine separately.

2-1