H3C MSR810 User manual

H3C MSR 810 & 2600 & 3600 Routers
Comware 7 OAA Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: MSR-CMW710-R0809
Document version: 6W400-20200823

Copyright © 2020, 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
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this
document are the property of their respective owners.
Notice
The information in this document is subject to change without notice. All contents in this document, including
statements, information, and recommendations, are believed to be accurate, but they are presented without
warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions
contained herein.

Preface
This configuration guide describes the OAP module feature.
This preface includes the following topics about the documentation:
•
Audience.
•
Conventions.
•
Documentation feedback.
Audience
This documentation is intended for:
•
Network planners.
•
Field technical support and servicing engineers.
•
Network administrators.
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 syntaxchoices 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
example, the New User window opens; click OK.
> 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.
Represents a wireless terminator unit.
Represents a 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.
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.
T
T
T
T

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
Restrictions: Hardware compatibility with OAP modules ···················································································1
Logging in to an OAP module····························································································································1
Logging in through the console port on the OAP module ··········································································1
Logging in from the CLI of the device ········································································································1
Resetting OAP modules·····································································································································2

1
Configuring the OAP module
About OAP modules
OAP is a hardware platform based on 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.
Restrictions: Hardware compatibility with OAP
modules
The device supports this feature only when it has HMIM-OAP interface modules.
Only MSR 3610, MSR 3620, MSR 3620-DP, MSR 3620-XS, MSR 3640, and MSR 3660 support
HMIM-OAP interface modules.
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 from the CLI of the device
About this task
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.

2
Procedure
To log in to an OAP module from the CLI of the device, execute one of the following commands in
user view:
In standalone mode:
oap connect system system-name
In IRF mode:
oap connect slot slot-number [system system-name ]
Resetting OAP modules
About this task
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. To avoid service data loss, close the
operating system of an OAP module before resetting the module.
Procedure
To reset an OAP module, execute one of the following commands in user view:
In standalone mode:
oap reboot system system-name
In IRF mode:
oap reboot slot slot-number [system system-name ]