H3C MSR Series User manual

H3C MSR Router Series
Comware 7 OAA Configuration Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: MSR-CMW710-R0615
Document version: 6W202-20200321

Copyright © 2018-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 Open Application Architecture (OAA) supported protocols
(such as ACFP and ACSEI), their configurations, and the configuration of the H3C open application
platform (OAP) card.
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 >

Convention
Description
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.
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.
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
Overview····························································································································································1
Compatibility information····································································································································1
Feature and hardware compatibility···········································································································1
Command and hardware compatibility·······································································································1
Logging in to the OAP module···························································································································2
Configuring network parameters for the OAP module ·······················································································2
Configuring network parameters for an OAP module that runs the CVK operating system·······················2
Configuring network parameters for an OAP module that runs the Linux operating system ·····················3
Rebooting the OAP module ·······························································································································4
Index··············································································································5

1
Configuring the OAP module
Overview
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.
This feature is supported only on the HMIM-OAP module.
Compatibility information
Feature and hardware compatibility
Hardware
OAP module compatibility
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/
810-LM-HK/810-W-LM-HK/810-LMS/810-LUS No
MSR2600-6-X1/2600-10-X1 No
MSR 2630 No
MSR3600-28/3600-51 No
MSR3600-28-SI/3600-51-SI No
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC No
MSR 3610/3620/3620-DP/3640/3660 Yes
MSR5620/5660/5680 Yes
Command and hardware compatibility
Commands and descriptions for centralized devices apply to the following routers:
•
MSR810/810-W/810-W-DB/810-LM/810-W-LM/810-10-PoE/810-LM-HK/810-W-LM-HK/810-L
MS/810-LUS.
•
MSR2600-6-X1/2600-10-X1.
•
MSR 2630.
•
MSR3600-28/3600-51.
•
MSR3600-28-SI/3600-51-SI.
•
MSR3610-X1/3610-X1-DP/3610-X1-DC/3610-X1-DP-DC.

2
•
MSR 3610/3620/3620-DP/3640/3660.
Commands and descriptions for distributed devices apply to the following routers:
•
MSR5620.
•
MSR 5660.
•
MSR 5680.
Logging in to the OAP module
From the CLI of the router, you can log in to the operating system of the OAP module. To return to the
CLI of the router, press Ctrl+K.
Perform the following task in user view:
Task
Command
Log in to the OAP module from the device.
•Distributed devices in standalone mode/centralized
devices in standalone or IRF mode:
oap connect slot slot-number system system-name
•Distributed devices in IRF mode:
oap connect chassis chassis-number slot
slot-number system system-name
Configuring network parameters for the OAP
module
After logging in to the operating system of an OAP module, you can configure network parameters
for the module as prompted.
Configuring network parameters for an OAP module that runs
the CVK operating system
In the following example, the OAP module is installed in slot 4 on the router.
1. Log in to the operating system of the OAP module as user root.
<System> oap connect slot 0 system 4
Connected to OAP
CentOS release 5.4 (Final)
Kernel 2.6.18-164.el5 on an x86_64
cvknode login: root
Password:
Last login: Tue Mar 12 04:10:46 CST 2013 on ttyS0
0 packages can be updated.
0 updates are security updates.
Your network has not been configured, do you want to configure it now?[y/n]
2. Enter y. To enter the operating system without configuring network parameters, enter n.
Your network has not been configured, do you want to configure it now?[y/n]y
Current configuration is:

3
hostname: cvknode
ipaddress: 192.168.0.162
netmask: 255.255.255.0
gateway: 192.168.0.1
network: 192.168.0.0
broadcast: 192.168.0.255
nameserver: 192.168.0.1
Please input hostname:
3. Configure network parameters as prompted.
Please input hostname: host1
Please input ipaddress: 192.168.0.167
Please input netmask: 255.255.255.0
Please input gateway: 192.168.0.1 (This setting is optional.)
Please input nameserver: 192.168.0.1 (This setting is optional.)
The hostname is cvknode by default. After you complete the configuration, the following
prompt appears:
Current input is corret?[y/n]y
4. Press yto confirm the settings. To change the settings, press nand repeat step 3.
The following prompt appears:
Would you want to save?[y/n]y
5. Press yto save the settings or press nto discard the settings.
You are logged in to the operating system of the OAP module. The operating system prompt
appears:
root@ cvknode:
To modify the network settings, use the /usr/bin/init_net/init_net.sh command and repeat step 2
through step 5.
6. To change the login password, execute the following command:
root@ cvknode:~# passwd root
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
The password is case sensitive and can contain letters, digits, and special characters.
Configuring network parameters for an OAP module that runs
the Linux operating system
In the following example, the OAP module is installed in slot 4 on the router.
# Log in to the operating system of the OAP module as user root.
<System> oap connect slot 0 system 4
Connected to OAP
CentOS release 5.4 (Final)
Kernel 2.6.18-164.el5 on an x86_64
localhost login: root
Password: root
Last login: Wed Feb 8 16:58:27 on ttyS0

4
[root@localhost ~]#
Rebooting the OAP module
CAUTION:
Rebooting the OAP module might cause a service outage.
IMPORTANT:
To avoid service data loss, close the operating system of the
OAP module before rebooting the
module.
You can reboot the OAP module if it fails or is not operating correctly. Pressing the reboot button of
the OAP module has the same effect. The router can still identify and control the OAP module after
the reboot.
Perform the following task in user view:
Task
Command
Reboot the OAP module.
•Distributed devices in standalone mode/centralized
devices in standalone or IRF mode:
oap reboot slot slot-number system system-name
•Distributed devices in IRF mode:
oap reboot chassis chassis-number slot slot-number
system system-name

5
Index
C L O R
C
Compatibility information,1
Configuring network parameters for the OAP
module,2
L
Logging in to the OAP module,2
O
Overview,1
R
Rebooting the OAP module,4