H3C CR16000-F User manual

H3C CR16000-F Routers
Comware 7 OAA Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com.hk
Software version: CR16000-CMW710-R7655P05 or later
Document version: 6W100-20170825

Copyright © 2017, New H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior written
consent of New H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE,Aolynk, , H3Care, , IRF, NetPilot, Netflow, SecEngine,
SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of New H3C Technologies
Co., Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Preface
This configuration guide describes OAA fundamentals and configuration. It describes how to
configure the H3C open application platform (OAP) module connected to your device to exchange
information between your device and the OAP module.
This preface includes the following topics about the documentation:
•Audience.
•Conventions
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners.
•Field technical support and servicing engineers.
•Network administrators working with the routers.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention Description
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select a minimum of one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Description
Boldface Window names, button names, field names, and menu items are in Boldface. For

Convention Description
example, the New Use
r
window opens; click O
K
.
> Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.
Symbols
Convention Description
WARNING! An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION: An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT: An alert that calls attention to essential information.
NOTE: An alert that contains additional or supplementary information.
TIP: An alert that provides helpful information.
Network topology icons
Convention Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that
supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access
controller engine on a unified wired-WLAN switch.
Represents an access point.
Wireless terminator unit.
Wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
Represents a security module, such as a firewall, load balancing, NetStream, SSL
VPN, IPS, or ACG module.
T
T
T
T





Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model,
configuration, or software version. It is normal that the port numbers, sample output, screenshots,
and other information in the examples differ from what you have on your device.
Obtaining documentation
To access the most up-to-date H3C product documentation, go to the H3C website at
http://www.h3c.com.hk
To obtain information about installation, configuration, and maintenance, click
http://www.h3c.com.hk/Technical_Documents
To obtain software version information such as release notes, click
http://www.h3c.com.hk/Software_Download
Technical support
[e-mail]
http://www.h3c.com.hk
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
Configuring the OAP module ······························································1
About OAP modules···················································································································1
Logging in to an OAP module·······································································································1
Logging in through the console port on the OAP module······························································1
Logging in through the management Ethernet port on the OAP module by using SSH························1
Logging in through the internal Ethernet interface on the OAP module by using SSH·························2
Logging in from the CLI of the device·······················································································2
Resetting OAP modules ··············································································································2
About resetting OAP modules ································································································2
Restrictions and guidelines····································································································2
Procedure··························································································································3
Configuring the OAP manager ····························································4
About OAP manager···················································································································4
OAP manager/client model····································································································4
OAP functions ····················································································································4
OAP manager timers············································································································5
Configuring the OAP manager······································································································5
Enabling OAP·····················································································································5
Setting the clock synchronization timer·····················································································5
Setting the client monitoring timer ···························································································5
Managing OAP clients·················································································································5
Restarting an OAP client·······································································································5
Shutting down an OAP client ·································································································6
Display and maintenance commands for OAP manager·····································································6
Index·····························································································7

1
Configuring the OAP module
About OAP modules
The Open Application Platform (OAP) is a hardware platform based on the OpenApplication
Architecture (OAA). OAP uses a manager/client model. The OAP client can be a network device or
an OAP module. An OAP module can be an expansion card installed in a network device or an
integrated part of a network device.
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.
OAP provides an open interface for third-party vendors to develop and integrate value-added
applications into H3C products.
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.
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 SSHclient 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.

2
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 can exchange information with the
device through internal interfaces, including a fast Ethernet interface.
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.
Logging in from the CLI of the device
From the CLI of the device, you can log in 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
Log in 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
Resetting OAP modules
About resetting OAP modules
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.
Restrictions and guidelines
Resetting an OAP module might cause a service outage.

3
To avoid service data loss, close the operating system of an OAP module before resetting the
module.
Procedure
Perform the following task in user view:
Task Command
Reset the OAP module.
In standalone mode:
oap reboot slot slot-number
In IRF mode:
oap reboot chassis chassis-number slot slot-number

4
Configuring the OAP manager
About OAP manager
The Open Application Platform (OAP) is a hardware platform based on the Open Application
Architecture (OAA). OAAallows products from different vendors to operate together to meet service
requirements.
OAP manager/client model
OAP uses a manager/client model.
•OAP manager—A feature integrated in the Comware system software.
•OAP client—Afeature that is integrated in the Comware system software of the device or in the
operating system of the OAP module.
Figure 1 OAA diagram
As shown in Figure 1, OAA includes the following components:
•Routing/switching component—Provides routing and switching services. This component is
the control center of the entire architecture and acts as the OAP manager.
•Standalone service component—Provides services to meet specific requirements.
•Interfacing component—Connects the standalone service component to the
routing/switching component and acts as the OAP client.
OAP is used for communication and cooperation between the routing/switching component and the
standalone service component.
You can install an OAP module in the device. For example, you can install an IDS/IPS OAP module
in the device to provide intrusion detection and protection services.
OAP functions
OAP provides the following functions:
•OAP clients register with and deregister from the OAP manager.
•The OAP manager assigns IDs to OAP clients to uniquely identify the clients.
•The OAP manager and an OAPclient exchange information to, for example, monitor each other
and synchronize the clock.
From the OAP manager, you can perform the following tasks:
•Restart OAP clients.
•Shut down OAP clients.
•Display OAP client information.
An OAP manager can manage up to 255 OAP clients.