13-OAA Configuration Guide

HomeSupportResource CenterRoutersH3C SR8800 Router SeriesH3C SR8800 Router SeriesTechnical DocumentsConfigure & DeployConfiguration GuidesH3C SR8800 Configuration Guide-Release3347-6W10313-OAA Configuration Guide
01-OAP Module Configuration
Title Size Download
01-OAP Module Configuration 79.51 KB

Configuring OAP modules

OAP module overview

As an open software and hardware system, the Open Application Architecture (OAA) of Hangzhou H3C Technologies Co., Ltd. (referred to as H3C herein after) provides a set of complete standard software and hardware interfaces based on H3C devices. The third party vendors can develop products with special functions. These products can be compatible with H3C devices as long as they conform to the OAA interface standards. Therefore the functions of single network products can be expanded and the users can get more benefits.

The Open Application Platform (OAP) is developed based on the OAA. It can be an independent network device, or a card used as an extended part of a device or integrated into a network device. This kind of OAP is called an OAP module. An OAP module runs an independent operating system. You can load software such as security and voice in the operating system as needed. Meanwhile, after an OAP module is inserted into the expansion module slot of the router, it interacts with the router on data, status information and control information through its internal service interfaces.

 

 

NOTE:

For the installation, startup and configuration, and software upgrading of the SecBlade firewall card (IM-FW), you can obtain the information by following these steps:

·       Go to the homepage of the website at http://www.h3c.com.

·       Select Technical Support & Document > Technical Documents from the homepage.

·       Select SecBlade II Firewall Cards in the Security Products area, and you can view the related manuals.

 

Logging in to the operating system of an OAP module

 

 

NOTE:

This document only covers the OAP module related operations on a router. For the operations on an OAP module, see the documentation of the OAP module.

 

Logging in through the console port of an OAP module

You can log in to the operating system on an OAP module directly through the console port on the OAP module. In this example, a PC acts as a terminal.

1.      Connect one end of the configuration cable to the serial port of the PC, and the other end to the console port of the OAP module.

2.      Start the PC and run the terminal emulation program such as the HyperTerminal. Select the connection mode COM and set the terminal parameters as follows: set the bits per seconds to 9600, data bits to 8, parity to none, stop bits to 1, and flow control to none.

After the configuration, you can log in to the operating system of the OAP module through the terminal emulation program on the PC.

Telnetting to an OAP module through the network management port

You can telnet to the operating system on an OAP module directly through the network management port of the OAP module.

Telnetting to an OAP module from a router

1.      Assign an IP address to the network management port of the OAP module.

2.      Enable the Telnet server on the OAP v with the telnet server enable command.

3.      Connect one end of the cable to the Ethernet port of the router, and the other end to the network management port of the OAP module.

4.      Make sure that the network management port of the router and that of the OAP module can reach each other.

5.      Execute the telnet command on the router, with the IP address of the network management port of the OAP module as the destination address. You can log in to the operating system of the OAP module after a connection is established.

Telnetting to an OAP module from a PC

1.      Assign an IP address to the network management port of the OAP module.

2.      Enable the Telnet server on the OAP module with the telnet server enable command.

3.      Connect one end of the cable to the Ethernet port of the PC, and the other end to the network management port of the OAP module.

4.      Make sure that the network management port of the PC and that of the OAP module can reach each other.

5.      Execute the telnet command on the PC, with the IP address of the network management port of the OAP module as the destination address. You can log in to the operating system of the OAP module after a connection is established.

Logging in through the network management port of an OAP module with SSH

You can use the SSH client to log in to the operating system of an OAP module through its network management port.

Using a router as the SSH client

1.      Assign an IP address to the network management port of the OAP module.

2.      Enable the SSH server on the OAP module with the ssh server enable command.

3.      Connect one end of the cable to the Ethernet port of the router, and the other end to the network management port of the OAP module.

4.      Make sure that the network management port of the router and that of the OAP module can reach each other.

5.      Execute the ssh command on the router, with the IP address of the network management port of the OAP module as the SSH server address. You can log in to the operating system of the OAP module after the connection is established.

Using a PC as the SSH client

1.      Assign an IP address to the network management port of the OAP module.

2.      Enable the SSH server on the OAP module with the ssh server enable command.

3.      Connect one end of the cable to the Ethernet port of the PC, and the other end to the network management port of the OAP module.

4.      Make sure that the network management port of the PC and that of the OAP module can reach each other.

5.      Execute the ssh command on the PC, with the IP address of the network management port of the OAP module as the SSH server address. You can log in to the operating system of the OAP module after the connection is established.

Redirecting to an OAP module from the router

You can redirect to the operating system of an OAP module from the router through the following operation. In this way, the terminal display interface is switched from the command line interface (CLI) on the router to the operating interface of the operating system of the OAP module, and you can manage the system and application software on the OAP module. You can press Ctrl+k to return to the router CLI.

To redirect from the router to the OAP module:

 

Task

Command

Remarks

Redirect from the router to the OAP module.

oap connect slot slot-number

Available in user view

 

 

NOTE:

·       Before redirecting from the router to the OAP module, perform basic configurations to the AUX port of the router from the console port of the OAP module to allow the login from the router.

·       The IM-SSL card does not support the redirection from the router to the OAP module through the oap connect command.

 

Resetting the system of an OAP module

If the operating system of an OAP module works abnormally or is under other anomalies (for example, the system does not respond), you can reset the system of an OAP module with the following operation to power on the OAP module again. This operation is equal to resetting the OAP module by pressing the reset button on the OAP module.

OAP modules have independent CPU systems. The router can still recognize and control the OAP module after you reset the OAP system.

To reset the system of an OAP module:

 

Task

Command

Remarks

Reset the system of an OAP module.

oap reboot slot slot-number

Available in user view

 

CAUTION

CAUTION:

Reset of the OAP module may cause data loss and service interruption. Therefore, before resetting the OAP module, you need to save the configurations of the OAP module operating system and shut down the OAP module operating system to avoid service interruption and hardware data loss.