Contents

Configuring the OAP module· 1

Internal interfaces for OAP modules· 2

Logging in to an OAP module· 2

Logging in through the console port on the OAP module· 2

Logging in through the management Ethernet port on the OAP module by using SSH· 3

Logging in through the internal Ethernet interface on the OAP module by using SSH· 3

Redirecting to the OAP module from the CLI of the device· 3

Resetting OAP modules· 4

 

Configuring the OAP module

H3C Open Application Architecture provides an open interface for third-party vendors to develop and integrate value-added applications into H3C products. These applications can apply to one of the following forms:

·     A standalone network device.

·     A card that can be installed in a network device (Open Application Platform module, or OAP module).

OAP modules have their own operating systems. You can log in to the operating system of an OAP module to install features. For example, you can install security features and voice features on the OAP module operating system to provide security and voice services for users.

OAP modules exchange data, status information, and control information with hosting devices through internal interfaces.

Table 1 Module type

OAP module	Module type	Number of internal interfaces
LSU1FWCEA0	Firewall card	Four 10G Ethernet interfaces
LSU3FWCEA0		Four 10G Ethernet interfaces
LSQ1FWBSC0		Two 10G Ethernet interfaces. Only the first one is available.
LSQ2FWBSC0		Two 10G Ethernet interfaces. Only the first one is available.
LSUM1FWCEAB0		Four 10G Ethernet interfaces
LSU1IPSBEA0	IPS card	Four 10G Ethernet interfaces
LSQ1IPSSC0		One 10G Ethernet interface
LSQ1SSLSC0	SSL VPN card	One 10G Ethernet interface
LSQ1ACGASC0	ACG card	One 10G Ethernet interface
LSQ1NSMSC0	NetStream card	Two 10G Ethernet interfaces. Only the first one is available.
LSU1NSCEA0		Four 10G Ethernet interfaces
LSU3WCMD0	High performance access controller module	Two 10G Ethernet interfaces
LSU1WCME0		Four 10G Ethernet interfaces
LSQ1WCMD0		Two 10G Ethernet interfaces
LSU1ADECEA0	Application delivery engine module	Four 10G Ethernet interfaces
LSQ1LBSC0	LB card	Two 10G Ethernet interfaces

 

 

IMPORTANT: An LSQ OAP module can only be installed on an S7506E-X.

 

IMPORTANT: ·     For the traffic received from the interface module to be redirected to the OAP module correctly, do not install any of the following interface modules on an S7502E that has an LSQ OAP module installed: ¡     LSQM1TGS12EC0. ¡     LSQM2GP44TSSC0. ¡     LSQM2GP24TSSC0. ¡     LSQM2GT24PTSSC0. ¡     LSQM2GT24TSSC0. ¡     LSQM2GT48SC0. ¡     LSQM4GV48SC0. ¡     SA interface modules. ·     An LSU1WCME0 cannot be installed on an S7502E.

 

Internal interfaces for OAP modules

An OAP module integrates a front card and a rear card. The front card provides value-added security services, such as firewall, intrusion prevention, and application control. The rear card is responsible for data exchange between the front card and the switch. The rear card communicates with the front card through the internal interface, as shown in the following figure.

Figure 1 Diagram for the internal interface

 

IMPORTANT: ·     On an LSQ OAP module, an internal interface cannot be set to operate in Layer 3 mode. For more information about Ethernet interface operating modes, see Interface Configuration Guide. ·     BFD is not available on internal interfaces of an LSQ OAP module. For more information about BFD, see High Availability Configuration Guide.

 

Logging in to an OAP module

Logging in through the console port on the OAP module

1.     Connect one end of the console cable to the serial port of the configuration terminal (for example, a PC).

2.     Connect the other end of the console cable to the console port of the OAP module.

3.     Start the PC and run a terminal emulation program, such as HyperTerminal.

4.     Select the COM connection mode and set the terminal parameters as follows:

¡     Bits per second—9600.

¡     Data bits—8.

¡     Parity check mode—None.

¡     Stop bits—1.

¡     Flow control—None.

5.     Follow the OAP module user guide to log in to the operating system of the OAP module through the terminal emulation program.

Logging in through the management Ethernet port on the OAP module by using SSH

1.     Connect the management Ethernet port of the OAP module to the network by using a network cable.

2.     Log in to the OAP module through the console port and enable the SSH server function on the OAP module.

3.     Assign an IP address to the management Ethernet port of the OAP module. Make sure the management Ethernet port and the SSH client (an H3C device or a PC with SSH client software) can reach each other.

4.     From the SSH client, establish an SSH connection to the IP address of the management Ethernet port on the OAP module.

After the SSH connection is successfully established, you are logged in to the operating system of the OAP module.

Logging in through the internal Ethernet interface on the OAP module by using SSH

When installed in the expansion slot of a device, an OAP module exchanges information with the device through two internal interfaces: one console port and one fast Ethernet interface. The fast Ethernet interface is used for this login method.

To log in to the operating system of an OAP module through the internal Ethernet interface:

1.     Connect the SSH client (for example, a PC) to the Ethernet port of the device by using a network cable.

2.     Log in to the OAP module through the console port and enable the SSH server function on the OAP module.

3.     Assign an IP address to the internal Ethernet interface on the OAP module. Make sure the PC and the fast Ethernet interface on the OAP module can reach each other.

4.     From the SSH client, establish an SSH connection to the IP address of the fast Ethernet interface.

After the SSH connection is successfully established, you are logged in to the operating system of the OAP module.

Redirecting to the OAP module from the CLI of the device

From the CLI of the device, you can redirect to the CLI of the OAP module. To return to the CLI of the device, press Ctrl+K.

Perform the following task in user view:

 

Task	Command	Remarks
Redirect to the CLI of the OAP module from the device.	·     In standalone mode: oap connect slot slot-number ·     In IRF mode: oap connect chassis chassis-number slot slot-number	The oap connect command is available only on the default MDC. The oap connect command is not available on the following OAP modules: ·     LSQ OAP modules. ·     LSU1IPSBEA0.

 

Resetting OAP modules

CAUTION: Resetting an OAP module might cause a service outage.

 

IMPORTANT: To avoid service data loss, close the operating system of an OAP module before resetting the module.

 

You can reset an OAP module to restore it to normal operation in the following situations:

·     The OAP module fails.

·     The OAP module is not operating correctly. For example, the OAP module does not respond to your operation.

Pressing the reset button of the OAP module has the same effect. The device can still identify and control the OAP module after the module starts up again.

Perform the following task in user view:

 

Task	Command	Remarks
Reset the OAP module.	·     In standalone mode: oap reboot slot slot-number [ system system-name ] ·     In IRF mode: oap reboot chassis chassis-number slot slot-number	The oap reboot command is not available on the following OAP modules: ·     LSQ OAP modules. ·     LSU1IPSBEA0. ·     LSU1WCME0.