U2020

V300R019C10

Northbound Command Line

Interface Developer Guide

Issue 01
Date 2019-08-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.

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 a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: https://www.huawei.com
Email: [email protected]

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. i

U2020
Northbound Command Line Interface Developer
Guide About This Document

About This Document

Overview
This document provides guidance on the northbound command line interface
(MML command interface) of U2020. It describes the meaning and
interconnection parameters, and interconnection and function of the northbound
MML command interface.
This document covers how to use and configure common functions of the product
rather than customized functions. For details about the customized functions,
contact Huawei to apply for and obtain relevant documents.

Product Version
The following table lists the product version related to this document.

Product Name Product Version

U2020 V300R019C10

Intended Audience
This document is intended for:
Network management engineers

Change History
02 (2019-06-25)
Added the section How Do I Enable the SSL Connection Mode?
01 (2019-06-12)
Migrated the following functions to U2020: Setting an IP Address Whitelist for
the MML Command Interface, and (Optional) Hiding or Unhiding Security
Information in MML Command Output. Modified the operation procedure.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. ii

U2020
Northbound Command Line Interface Developer
Guide About This Document

Organization
1 Introduction to Northbound MML Command Interface

2 Function of the Northbound MML Command Interface

3 Interconnection Commissioning of the Northbound MML Command

Interface

4 Troubleshooting for the Northbound MML Command Interface

Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk which, if

not avoided, will result in death or serious injury.

Indicates a hazard with a medium level of risk

which, if not avoided, could result in death or
serious injury.

Indicates a hazard with a low level of risk which, if

not avoided, could result in minor or moderate
injury.

Indicates a potentially hazardous situation which, if

not avoided, could result in equipment damage,
data loss, performance deterioration, or
unanticipated results.
NOTICE is used to address practices not related to
personal injury.

Supplements the important information in the main

text.
NOTE is used to address information not related to
personal injury, equipment damage, and
environment deterioration.

General Conventions
The general conventions that may be found in this document are defined as
follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. iii

U2020
Northbound Command Line Interface Developer
Guide About This Document

Convention Description

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen

are in Courier New.

Command Conventions

The command conventions that may be found in this document are defined as
follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are

optional.

{ x | y | ... } Optional items are grouped in braces and separated

by vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and

separated by vertical bars. One item is selected or
no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated

by vertical bars. A minimum of one item or a
maximum of all items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and

separated by vertical bars. Several items or no item
can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and

dialog titles are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by

the ">" signs. For example, choose File > Create >
Folder.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. iv

U2020
Northbound Command Line Interface Developer
Guide About This Document

Keyboard Operations

The keyboard operations that may be found in this document are defined as
follows.

Format Description

Key Press the key. For example, press Enter and press
Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing

Ctrl+Alt+A means the three keys should be pressed
concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A
means the two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button

without moving the pointer.

Double-click Press the primary mouse button twice continuously

and quickly without moving the pointer.

Drag Press and hold the primary mouse button and move
the pointer to a certain position.

Conventions
Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. v

U2020
Northbound Command Line Interface Developer
Guide About This Document

Symbol Description

Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.

Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.

General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New. The messages

entered on terminals by users are displayed in
boldface.

Command Conventions

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are

optional.

{ x | y | ... } Optional items are grouped in braces and separated

by vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated

by vertical bars. One item is selected or no item is
selected.

{ x | y | ... } * Optional items are grouped in braces and separated

by vertical bars. A minimum of one item or a
maximum of all items can be selected.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. vi

U2020
Northbound Command Line Interface Developer
Guide About This Document

Convention Description

[ x | y | ... ] * Optional items are grouped in brackets and separated

by vertical bars. Several items or no item can be
selected.

GUI Conventions

Convention Description

Boldface Buttons, menus, parameters, tabs, windows, and

dialog titles are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by

the ">" signs. For example, choose File > Create >
Folder.

Keyboard Operation

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl
+Alt+A means the three keys should be pressed
concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing "Alt, F"
means the two keys should be pressed in turn.

Mouse Operation

Action Description

Click Select and release the primary mouse button without

moving the pointer.

Double-click Press the primary mouse button twice continuously

and quickly without moving the pointer.

Drag Press and hold the primary mouse button and move
the pointer to a certain position.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. vii

U2020
Northbound Command Line Interface Developer
Guide Contents

Contents

About This Document................................................................................................................ ii

1 Introduction to Northbound MML Command Interface................................................ 1
1.1 Definition of Northbound Interface.................................................................................................................................. 1
1.2 Implementation of the Northbound MML Command Interface.............................................................................2
1.3 Application of the Northbound MML Command Interface...................................................................................... 4
1.4 Technical Specifications of Northbound MML Command Interface......................................................................4

2 Function of the Northbound MML Command Interface................................................ 5

2.1 Connecting the Northbound MML Command Interface........................................................................................... 5
2.1.1 Login......................................................................................................................................................................................... 5
2.1.2 Listing Operable NEs.......................................................................................................................................................... 7
2.1.3 Registering an NE................................................................................................................................................................ 8
2.1.4 Listing Operable VNFCs under a CloudEdge NE....................................................................................................... 9
2.1.5 Registering a VNFC under a CloudEdge NE............................................................................................................. 10
2.2 Maintaining the Northbound MML Command Interface....................................................................................... 11
2.2.1 Transmitting MML Commands..................................................................................................................................... 12
2.2.2 Issuing MML Commands in Batches........................................................................................................................... 12
2.2.3 Sending Handshake Messages......................................................................................................................................15
2.2.4 Sending Disconnection Messages when Disconnecting.......................................................................................16
2.3 Disconnecting the Northbound MML Command Interface................................................................................... 16
2.3.1 Deregistering a VNFC under a CloudEdge NE......................................................................................................... 16
2.3.2 Deregistering an NE......................................................................................................................................................... 17
2.3.3 Logout................................................................................................................................................................................... 19

3 Interconnection Commissioning of the Northbound MML Command Interface... 20

3.1 Checking License (MML Command Interface)........................................................................................................... 20
3.2 Negotiating Interconnection Parameters of the Northbound MML Command Interface...........................21
3.3 Preparations for the Commissioning of the Northbound MML Command Interface................................... 22
3.3.1 Creating a User and Assigning Rights........................................................................................................................ 22
3.3.2 Assigning MML Command Rights to the Specified User or Role......................................................................25
3.3.3 Querying an Authorized MML Command................................................................................................................ 25
3.4 Commissioning the Interconnection of the Northbound MML Command Interface.................................... 25
3.4.1 Connection Configuration File of the MML Command Interface..................................................................... 26
3.4.2 Modifying the Connection Configuration File of the MML Command Interface........................................28

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. viii

U2020
Northbound Command Line Interface Developer
Guide Contents

3.4.3 Simulating the Interconnection with the NMS in Unencrypted Connection Mode (MML Command
Interface).........................................................................................................................................................................................29
3.4.4 Simulating the Interconnection with the NMS in SSL Connection Mode (MML Command Interface)
............................................................................................................................................................................................................ 29
3.4.5 Checking the CloudEdge NE Interconnection Effect............................................................................................. 30
3.4.6 Setting an IP Address Whitelist for the MML Command Interface..................................................................32
3.5 (Optional) Hiding or Unhiding Security Information in MML Command Outputs....................................... 32

4 Troubleshooting for the Northbound MML Command Interface.............................. 34

4.1 Common Troubleshooting and Information Collection (MML Command Interface)................................... 34
4.2 Troubleshooting Failure to Issue MML Commands.................................................................................................. 35
4.3 How Do I Handle a Closed SSL Connection?.............................................................................................................. 36
4.4 What Do I Do If the ping Command Cannot Be Stopped in the Current NMS Client?................................37
4.5 How Do I Change the Public Key Length of the Diffie-Hellman Algorithm?.................................................. 37
4.6 How Do I Enable the SSL Connection Mode?............................................................................................................. 38

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. ix

U2020
Northbound Command Line Interface Developer 1 Introduction to Northbound MML Command
Guide Interface

1 Introduction to Northbound MML

Command Interface

About This Chapter

This describes the definition of the northbound interface, and the implementation
and interconnecting parameters of the northbound MML command interface.
1.1 Definition of Northbound Interface
1.2 Implementation of the Northbound MML Command Interface
1.3 Application of the Northbound MML Command Interface
1.4 Technical Specifications of Northbound MML Command Interface

1.1 Definition of Northbound Interface

The northbound interface links the element management system (EMS) and the
NMS.
The NMS obtains information about the network elements (NEs) managed by the
EMS and delivers operation commands through the northbound interface. The NE
information includes the alarm, configuration, performance, and inventory data.
Figure 1-1 shows the position of the northbound interface in the network.

Figure 1-1 Position of the northbound interface

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 1

U2020
Northbound Command Line Interface Developer 1 Introduction to Northbound MML Command
Guide Interface

In the communication network, the U2020 provides the alarm, configuration,

performance, and inventory data of NEs to the NMS through the northbound
interface.

1.2 Implementation of the Northbound MML

Command Interface
The U2020 provides the northbound MML command interface for the NMS. On
this interface, the NMS connects to and manages NEs that are managed by the
U2020 server. The MML command interface supports connection in SSL and non-
SSL modes. The SSL mode is more secure than the non-SSL mode. Therefore, the
SSL mode is recommended.

Implementation
Table 1-1 describes the process for implementation.

Table 1-1 Process for implementation

Brief Description

Log in to the U2020 server as user Currently, the northbound MML command
U2020. Establish the remote interface supports a maximum of 64
connection between the NMS and remote connections. If the number of
the U2020. connections is greater than 64, the system
denies the connection.

The U2020 authenticates the ● If the authentication is successful, the

received information about the login success message is displayed.
user account. ● If the authentication fails, the NMS
disconnects the NE.

Users can query the list of all the For the direct running of scripts, the default
authorized NEs and select an NE operation object is the U2020.
to operate.
NOTE
For an CloudEdge NE, select a certain
VNFC to operate under it.

The U2020 transparently The packet of the NE is displayed to the

transmits an MML command sent NMS.
by users to the NE.

● Using a command, the NMS can switch to operate another NE at any time. The NMS,
however, can operate one NE at a time.
● For CloudEdge NEs, the NMS can operate only a certain VNFC under a single NE at a
time.

For details of the process, see Figure 1-2.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 2

U2020
Northbound Command Line Interface Developer 1 Introduction to Northbound MML Command
Guide Interface

MML Commands Transmission Process

Figure 1-2 Transmission process of an MML command sent by NMS

No. Operation

1 The NMS establishes connection with the U2020.

2 The NMS sends the name and password of the user who logs in to
the system to the U2020 for authentication.

3 The authentication result is displayed.

4 If the authentication is successful, the NMS sends an NE list

command.

5 The operable NE list information is displayed.

6 The NMS registers an NE to be operated.

7 The U2020 queries whether the NE is connected.

8 The connection result is displayed.

9 If the connection fails, the U2020 replies the northbound with the
connection failure message.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 3

U2020
Northbound Command Line Interface Developer 1 Introduction to Northbound MML Command
Guide Interface

No. Operation

10 If the connection is successful, the NMS sends an MML command.

NOTE
For CloudEdge NEs, the following operations are required:
1. The NMS sends an MML command to list VNFCs of the registered
CloudEdge NE.
2. The operable VNFC list information about the registered CloudEdge NE is
displayed.
3. The NMS registers a VNFC to be operated.

11 The MML command is transparently transmitted to the NE.

12 The result of the operation is displayed.

13 The operation result is displayed to the NMS.

1.3 Application of the Northbound MML Command

Interface
This section describes how to use the northbound MML command interface when
the U2020 system adopts different networking modes.
For details about how to use the northbound MML command interface in different
U2020 networking modes, see Table 1-2.

Table 1-2 Application of the northbound MML command interface

U2020 System Type NMS and U2020 Interconnection Solution

Virtual Cluster System Perform interconnection on the U2020 master

(Distributed networking) service VM.

1.4 Technical Specifications of Northbound MML

Command Interface
This section describes the technical specifications related to the northbound MML
command interface.

Specification Item Value

Maximum number of northbound MML command interface 64

connections

Time for responding to the northbound MML command 5

interface (unit: second)

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 4

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

2 Function of the Northbound MML

Command Interface

About This Chapter

This section describes the function of the northbound MML command interface,
which consists of connecting the northbound MML command interface,
maintaining the northbound MML command interface, and disconnecting the
northbound MML command interface.

Context
Strictly conform to the format of MML commands when using the MML
commands. The colon (:) and semicolon (;) are mandatory for the MML
commands. End each MML command with the newline character.
2.1 Connecting the Northbound MML Command Interface
2.2 Maintaining the Northbound MML Command Interface
2.3 Disconnecting the Northbound MML Command Interface

2.1 Connecting the Northbound MML Command

Interface
This section describes the procedure for connecting the northbound MML
command interface, which consists of login, listing operable NEs, and registering
an NE. If a CloudEdge NE is registered, you need to list operable VNFCs and
register VNFCs.

2.1.1 Login
The NMS remotely logs in to the U2020 server through the MML service port to
connect to the U2020 server.

Prerequisites
The U2020 user is created on the U2020 client. For details, see 3.3.1 Creating a
User and Assigning Rights.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 5

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Procedure
Step 1 Remotely log in to port 31114 of the U2020 server.

NOTICE

Using SSL mode is recommended because of its higher security than Non-SSL
mode.

● SSL mode
For example, enter the following command in the system where the openssl
software is installed to simulate the client:
openssl s_client -CAfile CA trust certificate -cert device certificate on the
client -key private key of the device certificate on the client -port 31114 -
host floating IP address of the server -tls1_2 -quiet -crlf

The openssl parameter -tls1_2 corresponds to the TLSv1.2 version. During the
interconnection, use the openssl parameter based on the version value set in
SSLOption.xml. The SSLv3 protocol corresponds to the -ssl3 parameter.
If the TLSv1.2 protocol is used, the OpenSSL tool later than the 1.0.1p version must be used.
If you need to use a third-party certificate for the interconnection with the NMS, replace
the existing certificate with a third-party certificate by following the instructions provided in
Updating Certificates in U2020 Product Documentation. You must stop all U2020 services
before the replacement. After the replacement, start all U2020 services again.
The SSLv3 and TLSv1.0 protocols have security risks. If you do not need to use them, disable
them according to Disabling the SSLv3 Protocol Used on the U2020 and Disabling the
TLSv1.0 Protocol Used on the U2020 in U2020 Administrator Guide.
Since V200R018C10, SSLv3 and TLSv1.0 are disabled by default for security purposes in
new installation scenarios. You are advised not to enable SSLv3 and TLSv1.0. If you need to
enable them, see Enabling the SSLv3 Protocol Used on the U2020 and Enabling the
TLSv1.0 Protocol Used on the U2020 in U2020 Administrator Guide.
By default, the public key of the Diffie-Hellman algorithm contains 2048 bits. If the NMS
does not support the Diffie-Hellman algorithm with the 2048-bit public key, change the
default public key length of the Diffie-Hellman algorithm to 1024 bits, resulting in security
risks. For details, see 4.5 How Do I Change the Public Key Length of the Diffie-Hellman
Algorithm?
● Non-SSL mode
For example, enter telnet floating IP address of the U2020 server 31114 for
the remote login.

Step 2 Run the following command to log in to the U2020 server:

The command syntax is as follows, with all letters being in uppercase:

LGI:OP="MML user", PWD="password of MML user";

For example, LGI:OP="MMLUser",PWD="OSSnbi_123";

● If "RETCODE = 0 Success" is displayed, login to the U2020 server succeeds.

● If "RETCODE = 1 Error Message" is displayed, login to the U2020 server failed.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 6

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

The possible reasons for the failure are as follows: The U2020 user is not
created, the U2020 user and password are incorrect, the U2020 user is locked,
and the password expires.

By default, the U2020 client locks on three incorrect password attempts. It is unlocked 30
minutes later. For details about client locking and unlocking, see the sections Parameters
for Setting an Account Policy and Unlocking an OM User under User Management in the
U2020 Online Help or the U2020 product documentation.
If the user password expires, you can log in to the server again after changing the
password. You can set the expiration duration of the password to 0 so that the password
will not expire. Consider of the security of system, it is not recommended to set the
expiration duration of the password to 0. For detailed operations, see U2020 Online Help.

----End

2.1.2 Listing Operable NEs

This describes the procedure for listing operable NEs.

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.

Step 2 Query NE information.

If the NMS queries the NE list from the U2020, it executes the LST NEBYOMC:;
(recommended) or LST NE:; (not recommended) command, with all letters being
in uppercase.

NOTICE

● If the NMS is using the LST NE:; command and no error occurs, it can still use
the LST NE:; command. If the LST NE:; command is in conflict with the LST
NE:; of some NEs, the NMS uses the LST NEBYOMC:; command.

● If the NMS knows the IP address of the NE to be maintained, it can directly

send a registration command, and this step is not required.

The packet returned to the NMS lists all NEs that can be operated by the current
user. The user can select an NE to maintain.

● If the LST NEBYOMC:; runs successfully, the following packet is displayed:

LST NEBYOMC:;
+++ NMS SERVER 2015-01-08 14:53:05
O&M #2304
%%LST NEBYOMC:;%%
RETCODE = 0 Success

LST NE Info
-----------

NE Type NE Name IP address

BSC6900GSMNE 10.144.242.36 10.144.242.36

BSC6900GSMNE 10.145.16.108 10.145.16.108

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 7

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

● If the LST NEBYOMC:; runs unsuccessfully, the following packet is displayed:

+++ NMS SERVER 2006-03-02 12:09:25
O&M #2304
%%LST NEBYOMC:;%%
RETCODE = 1 Error Message
Error Message
--- END

● If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is

displayed.
● Error Message indicates the detailed error message.
● Set Info based on the input parameter during the registration of the NMS.
● If the NMS queries the basic information from NEs, it runs the following command (the
following operations apply to NEs that support the LST NE:; command):
LST NEBYOMC:;
LST NE:;
The LST NEBYOMC:; command is used to query the NE list from U2020, and then the
LST NE:; command is issued to NEs to query basic NE information. The two commands
are executed in sequence.

----End

2.1.3 Registering an NE
When the user selects an NE from an NE list to maintain, the NMS sends a
registration command to the U2020.

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.
Step 2 Registering an NE.

When you register an NE managed by the CGPOMU, use the name rather than the IP
address of the NE because the IP addresses of the NE and the CGPOMU are the same.
● Registering an NE Through IP Address
The format of the command is as follows, with all letters being in uppercase:
REG NE:IP="10.161.198.243";
Based on the parameters in the REG NE command, the U2020 analyzes the IP
address of an NE and establishes the connection to the NE.
– If the connection is successful, a success message is sent to the NMS.
– If the connection fails, an error message is sent to the NMS.
If the connection is successful, the following packet is displayed by the
U2020:
+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%% REG NE:IP="10.161.198.243";%%
RETCODE = 0 Success

Success

--- END

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 8

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

If the connection fails, the following packet is displayed by the U2020:

+++ NMS SERVER 2006-03-02 12:09:25
O&M #2304
%% REG NE:IP="10.161.198.243";%%
RETCODE = 1 Error Message
Error Message
--- END

● If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is

displayed.
● Error Message indicates the detailed error message.
● Registering an NE Through NE Name
The format of the command is as follows, with all letters being in uppercase:
REG NE:NAME="NodeB_czh";
Based on the parameters in the REG NE command, the U2020 obtains an NE
name and establishes the connection to the NE.
– If the connection is successful, the success message is sent to the NMS.
– If the connection fails, the error message is sent to the NMS.
If the connection is successful, the following packet is displayed by the
U2020:
+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%% REG NE: NAME ="NodeB_czh";%%
RETCODE = 0 Success

Success

--- END

If the connection fails, the following packet is displayed by the U2020:

+++ NMS SERVER 2006-03-02 12:09:25
O&M #2304
%% REG NE: NAME ="NodeB_czh";%%
RETCODE = 1 Error Message
Error Message
--- END

● If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is

displayed.
● Error Message indicates the detailed error message.
● If the user knows the IP address of the NE or the name of the NE, the LST NE command
need not be used. You can register the NE based on the IP address or the NE name.
● The NMS can maintain only one NE at a time. The NMS, however, can send the REG
command to switch to a different NE. After the NMS sends the REG command, the
U2020 automatically disconnects the previous NE that is maintained.

----End

2.1.4 Listing Operable VNFCs under a CloudEdge NE

MML commands can be transparently transmitted over the MML command
interface to list operable VNFCs under a registered CloudEdge NE.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 9

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Prerequisites
You have registered a CloudEdge NE. For details, see 2.1.3 Registering an NE.

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.

Step 2 Run the following command to query operable VNFCs under a registered
CloudEdge NE.

The command syntax is as follows, with all letters being in uppercase:

LST VNFCBYNE:;

● If the LST VNFCBYNE:; command is executed successfully, the following

following packet is returned:
LST VNFCBYNE:;
+++ NMS SERVER 2017-02-21 16:33:25
O&M #2304
%%LST VNFCBYNE:;%%
RETCODE = 0 Success

LST CloudEdge NE Info

-----------

NE Type NE Name IP address VNFC Name

vUGWNE GSC 10.107.72.20 VNFP

vUGWNE GSC 10.107.72.20 cslb
vUGWNE GSC 10.107.72.20 gsc
vUGWNE GSC 10.107.72.20 ip
vUGWNE GSC 10.107.72.20 ugw

--- END

● If the LST VNFCBYNE:; command is not executed successfully, the following

packet is returned:
LST VNFCBYNE:;
+++ NMS SERVER 2017-02-21 16:09:37
O&M #2304
%%LST VNFCBYNE:;%%
RETCODE = 1 Error Message

Error Message
--- END

The packet returned to the NMS lists all VNFCs that can be operated by the
current user under the registered CloudEdge NE. The user can select a VNFC to
maintain.

----End

2.1.5 Registering a VNFC under a CloudEdge NE

When users select a VNFC for maintenance from the VNFC list, the NMS sends a
VNFC registration command to the U2020.

Prerequisites
● You have registered a CloudEdge NE.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 10

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.
Step 2 Query the VNFCs of the registered CloudEdge NE. For details, see 2.1.4 Listing
Operable VNFCs under a CloudEdge NE.
Step 3 Register a VNFC.
The command syntax is as follows, with all letters being in uppercase:
REG VNFC:NAME="VNFC name";
The U2020 analyzes parameters in the REG VNFC command to obtain the VNFC
name and sets up a connection with the VNFC.
If the registration is successful, the U2020 returns a success response to the NMS.
Otherwise, the U2020 returns an error response.
● If the registration is successful, the U2020 returns the following packet:
REG VNFC:NAME="gsc";
+++ NMS SERVER 2017-02-21 16:49:48
O&M #2304
%%REG VNFC:NAME="gsc";%%
RETCODE = 0 Success

Success

--- END

● If the registration fails, the U2020 returns the following packet:

REG VNFC:NAME="gsc";
+++ NMS SERVER 2017-02-21 16:46:01
O&M #2304
%%REG VNFC:NAME="gsc";%%
RETCODE = 1 Error Message

Error Message
--- END

● If the registration is successful, the returned value of RETCODE is 0. If the registration

fails, an error code is returned.
● Error Message indicates the detailed error message.
● If users know the operable VNFC name, users can skip the LST VNFCBYNE command
and register the VNFC using the name.
● The NMS can maintain one VNFC at a time, but can issue the REG VNFC command to
switch to maintain another NE as required. When the NMS sends the REG VNFC
command again, the U2020 automatically disconnects from the previously maintained
VNFC.

----End

2.2 Maintaining the Northbound MML Command

Interface
This describes the procedure for maintaining the northbound MML command
interface, which consists of MML commands transmission, sending handshake
messages, and sending disconnection messages when disconnecting.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 11

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

2.2.1 Transmitting MML Commands

This describes the procedure for MML command transmission.

Prerequisites
● NEs must be registered before the execution of MML command transmission.
For details, see 2.1.3 Registering an NE.
● The MML command to be transmitted must be authorized in advance.

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.
Step 2 The NMS sends a command to an NE.
After receiving a command, the U2020 immediately forwards it to a specific NE,
The format of the command is as follows, with all letters being in uppercase:

GET OFI:;
+++ HW-MSOFTX 2008-09-12 10:40:25+08:00
O&M #969842
%%/*2881@CMM_SID=1@*/GET OFI:;%%
RETCODE = 0 Operation succeeded
--- End

● If the MML command is authorized, the Success can be displayed.

● If the MML command is not authorized, the authentication fails.

----End

2.2.2 Issuing MML Commands in Batches

The NMS can activate a script to issue multiple MML commands to NEs in
batches. Therefore, the NMS can operate and maintain the NEs.

Prerequisites
● The script contains only the authorized MML commands for the
corresponding NEs.
● The script is uploaded to the /export/home/sysm/ftproot/itf_n/
nms_mml_server/script directory on the U2020 server by user ftpuser.

Context
● The script must be in the .txt format. The NMS needs to maintain the script
that is uploaded in ASCII mode and saved in the /export/home/sysm/
ftproot/itf_n/nms_mml_server/script directory.
● The name of the script file can contain only letters and digits. The character-
encoding scheme of the script file must be GBK.
● The file containing the script execution results is saved in the /export/home/
sysm/ftproot/itf_n/nms_mml_server/result directory. The U2020
automatically deletes the result files generated three days ago.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 12

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

● The U2020 automatically names the result files. The naming convention is as
follows: name of the script to be activated_time when the script is
activated_name of the user that remotely logs in to the U2020 server for
using the MML service_random number.rst. The format of time when the
script is activated is YYYYMMDDHHMMSS. YYYY indicates year, MM indicates
month, DD indicates date, HH indicates hour (24-hour format), MM indicates
minute, and SS indicates second. For example, 20090511171950 indicates that
the script is activated at 17:19:50 on May 11, 2009. Multiple results files are
generated when multiple users remotely and simultaneously log in to the
U2020 server to active a certain script by using the same user account. In this
case, the random number parameter can be used to distinguish between
these results files.
● Only one script can be activated at a time. That is, if the current user is
activating a script, the user cannot activate another script at the same time.
● You can specify the NE on which the MML command is to be used in either
the activation command or the script. After you specify an NE in the
activation command, the MML command is to be used on this NE no matter
whether you specify the NE in the script or not. If you do not specify an NE in
the activation command, the MML command is to be used on the NE that is
specified in the script.
● In the script, different MML commands are located in different lines. {} is
added to each MML command to specify the NEs to which the command is to
be issued. If you do not need to specify any NE, {} is not required. For
example, if you need to issue the LST CELL:; command to the NEs named
rnc_l and rnc_2 and the LST PRACH:; command to the NE named rnc_l, but
need not specify any NE to which the LST BRD:; command is issued, the script
is as follows, with all letters being in uppercase:
LST CELL:; {rnc_l,rnc_2}
LST PRACH:; {rnc_l}
LST BRD:;

● Description of the command parameters

The format of the command is: S_ACTIVATE: FILE="filename"[,
NELIST="{nename1[,nename2]}"][, SERIAL="{true|false}"];

Table 2-1 Parameter description

Parameter Parameter description

FILE Mandatory.
The script file whose extension name is .txt.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 13

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Parameter Parameter description

NELIST Optional.
The list of NEs to which MML commands are to be issued.
● If this parameter is contained in the command, MML
commands are to be issued to the NEs in the list rather than
the NEs specified in the MML script.
● Otherwise, MML commands are to be issued to the NEs
specified in the script.
● For CloudEdge NEs, you need to specify this parameter and
enter the name of the corresponding VNFC. In addition, the
MML script to be issued should not contain the names of
CloudEdge NEs.

SERIAL Optional. The default value is false.

This parameter determines whether the MML commands are
issued according to the serial numbers in the script.
● If the value of this parameter is true, MML commands are
issued according to the serial numbers in the script. The
issuing order is consistent with the order in the script.
● If the value of this parameter is false, MML commands are
issued according to the simultaneous operation of NEs. The
issuing order is decided by the simultaneous operation of NEs.
If the script has multiple NEs, the issuing efficiency is high by
setting this parameter to false.

STOPWHEN This parameter is optional. The default value is false.

ERROR Indicates whether to stop a task when an error occurs.
● If this parameter is set to true and an MML command in the
script file fails to be executed, the task is stopped immediately
and the remaining MML commands are not executed.
● If this parameter is set to false and an MML command in the
script file fails to be executed, all the remaining MML
commands are executed.

STARTNO This parameter is optional. The default value is 1.

Indicates the start number of command execution.

● Do not register NEs for issuing MML command in batches.

● When STOPWHENERROR is set to true, SERIAL must be set to true. (When the break on
failure mode is used, MML commands can be issued only in serial mode.) NELIST allows
only CGP NEs, and USE ME:MEID=XXXX; must be used to switch to the corresponding
subnet for the batch-processing MML script file. The supported sub-NEs are ATS9900,
iCG9815, MSOFTX3000, CSC3300, MRP6600, SPG2800, and SE2900.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 14

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.

Step 2 Specify the NEs in the activation command or script. Run the following command
to activate the script, with all letters being in uppercase:
● Specify the NEs to which the MML commands are to be issued in the
activation command.
Run the following command to deliver the script named testMML2.txt to the
NEs rnc_1 and rnc_2. Save the execution results to the file Name of the script
to be activated_Time when the script is activated_Name of the user that
remotely logs in to the U2020 server for using the MML service_random
number.rst. For example, a file named
testMML2_20090511171950_UserName_102.rst.
S_ACTIVATE: FILE="testMML2.txt", NELIST="{rnc_1,rnc_2}";
If the system displays the following information, you can infer that the script
is executed successfully.

S_ACTIVATE OK; RESULFILE=testMML2_20090511171950_UserName_102.rst

10% ACCOMPLISHED
50% ACCOMPLISHED
100% ACCOMPLISHED
S_ACTIVATE SUCCESS;

If the system displays the following information, you can infer that executing
the script failed. You can rectify the fault according to the error message.
S_ACTIVATE FAILED; REASON=insufficient privilege

● Specify the NEs to which the MML commands are to be issued in the script.
Run the following command to deliver the script test1.txt to the specified
NEs and save the execution results to the file named Name of the script to
be activated_Time when the script is activated_Name of the user that
remotely logs in to the U2020 server for using the MML service_Random
number.rst. For example, a file named
test1_20090511171950_UserName_102.rst.
S_ACTIVATE: FILE="test1.txt";
If the system displays the following information, you can infer that the script
is executed successfully.
S_ACTIVATE OK; RESULFILE=test1_20090511171950_UserName_102.rst
10% ACCOMPLISHED
50% ACCOMPLISHED
100% ACCOMPLISHED
S_ACTIVATE SUCCESS;

If the system displays the following information, you can infer that executing
the script failed. You can rectify the fault according to the error message.
S_ACTIVATE FAILED; REASON=insufficient privilege

----End

2.2.3 Sending Handshake Messages

To ensure smooth connection, the NMS sends a handshake message to MML
command interface every 300 seconds.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 15

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.

Step 2 Run the following command, with all letters being in uppercase.

SHK HAND:;

The packet displayed by the NE is as follows:

+++ NMS SERVER 2006-03-02 15:18:59 DST
O&M #0
%%SHK HAND:;%%
RETCODE = 0 Success

Success

--- END

----End

2.2.4 Sending Disconnection Messages when Disconnecting

When an NE disconnects the U2020, the U2020 sends an NE disconnection
message to the NMS.

Procedure
Step 1 The U2020 sends an NE disconnection message to the NMS.

The packet sent by the U2020 is as follows:

+++ NMS SERVER 2006-03-02 11:57:11
SYNC #2304
NE Disconnect Information
--------------------
IP="10.161.198.243";
--- END

----End

2.3 Disconnecting the Northbound MML Command

Interface
This describes the procedure for disconnecting the northbound MML command
interface, which consists of deregistering an NE and logout.

2.3.1 Deregistering a VNFC under a CloudEdge NE

After a VNFC is registered, some system resources are required. When the NMS
does not need to maintain the VNFC, you can deregister the VNFC to release
related resources.

Prerequisites
You have register a CloudEdge NE and a certain VNFC.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 16

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Context
● You can deregister a registered VNFC using its name.
● You can run the UNREG NE command to deregister a registered CloudEdge
NE. The VNFC under the CloudEdge NE is also deregistered.
● The NMS can maintain only a VNFC at a time. You can run the REG VNFC
command to register another VNFC for maintenance, and the previously
registered VNFC is automatically deregistered.

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.

Step 2 Send an MML command to deregister a VNFC.

The command syntax is as follows, with all letters being in uppercase:

UNREG VNFC:NAME="Name of the registered VNFC";

● If the deregistration is successful, the U2020 returns the following packet:

UNREG VNFC:NAME="gsc";
+++ NMS SERVER 2017-02-21 20:47:02
O&M #2304
%%UNREG VNFC:NAME="gsc";%%
RETCODE = 0 Success

Success

--- END

● If the deregistration fails, the U2020 returns the following packet:

UNREG VNFC:NAME="gsc";
+++ NMS SERVER 2017-02-21 20:40:11
O&M #2304
%%UNREG VNFC:NAME="gsc";%%
RETCODE = 1 Error Message

Error Message

--- END

● If the deregistration is successful, the returned value of RETCODE is 0. If the

deregistration fails, an error code is returned.
● Error Message indicates the detailed error message. You can resolve the problem based
on the error message. If the problem persists, contact Huawei technical support.

----End

2.3.2 Deregistering an NE
Registering an NE requires the system resource. Therefore, if the NMS does not
maintain an NE, you need to deregister the NE to release the resource.

Prerequisites
You have registered an NE and obtained the IP address or name of the NE.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 17

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

Context
You can use the IP address or the name of an NE to deregister the NE.

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.

Step 2 Deregistering an NE.

● Deregistering an NE Through IP Address
The format of the command is as follows, with all letters being in uppercase:
UNREG NE:IP="10.161.198.243";
If the logout command is run successfully, the packet displayed by the U2020
is as follows:
+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%% UNREG NE:IP="10.161.198.243";%%
RETCODE = 0 Success

Success

--- END

If the logout command is run unsuccessfully, the packet displayed by the

U2020 is as follows:
+++ NMS SERVER 2006-03-02 12:09:25
O&M #2304
%% UNREG NE:IP="10.161.198.243";%%
RETCODE = 1 Error Message
Error Message
--- END

● If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is

displayed.
● Error Message indicates the detailed error message.
● Deregistering an NE Through NE Name
The format of the command is as follows, with all letters being in uppercase:
UNREG NE:NAME ="NodeB_czh";
If the logout command is run successfully, the packet displayed by the U2020
is as follows:
+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%% UNREG NE:NAME ="NodeB_czh";%%
RETCODE = 0 Success
Success
--- END

If the logout command is run unsuccessfully, the packet displayed by the

U2020 is as follows:
+++ NMS SERVER 2006-03-02 12:09:25
O&M #2304
%% UNREG NE:NAME ="NodeB_czh";%%
RETCODE = 1 Error Message
Error Message
--- END

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 18

U2020
Northbound Command Line Interface Developer 2 Function of the Northbound MML Command
Guide Interface

● If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is

displayed.
● Error Message indicates the detailed error message. You can handle related problems
based on the error message. If it is not possible to solve a problem, contact Huawei for
technical support.

----End

2.3.3 Logout
When you log out of the U2020 and disconnect the U2020, you need send the
LGO:OP="MMLUser"; command.

Prerequisites
You have logged in to port 31114 of the U2020 server.

Procedure
Step 1 Log in to the MML port of the U2020. For details, see 2.1.1 Login.

Step 2 In the login window, run the following command, with all letters being in
uppercase.

LGO:OP="MMLUser";

If the logout is successful, the packet displayed by the U2020 is as follows:

+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%%LGO:OP="MMLUser";%%
RETCODE = 0 Success
Success
--- END

If the logout fails, the packet displayed by the U2020 is as follows:

+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%%LGO:OP="MMLUser";%%
RETCODE = 1 Error Message
Error Message
--- END

● If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is

displayed.
● Error Message indicates the detailed error message. You can handle related problems
according to the error message. If it is not possible to handle a problem, contact Huawei
for technical support.

----End

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 19

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

3 Interconnection Commissioning of the

Northbound MML Command Interface

About This Chapter

Before interconnecting the NMS with the U2020, you must conduct an
interconnection commissioning. Based on the commissioning result, determine
whether the northbound MML command interface meets the conditions for
interconnecting with the NMS.

NOTICE

If the EOX date of a third-party software release (such as the browser) you have
deployed on your PC is earlier than that of the product, upgrade the software to a
version that spans the product lifecycle to ensure network security.

3.1 Checking License (MML Command Interface)

3.2 Negotiating Interconnection Parameters of the Northbound MML Command
Interface
3.3 Preparations for the Commissioning of the Northbound MML Command
Interface
3.4 Commissioning the Interconnection of the Northbound MML Command
Interface
3.5 (Optional) Hiding or Unhiding Security Information in MML Command
Outputs

3.1 Checking License (MML Command Interface)

Before interconnecting the U2020 to the NMS, make sure that U2020 is licensed
to use the northbound MML command interface.

Perform the following operations to check whether U2020 has the required
license:

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 20

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

1. Log in to the U2020 client.

2. Choose License > License Management.
3. In the navigation pane, choose License Information.
4. In the License Information page, click the Function Control tab.
a. For RAN NEs, if Function contains Northbound Additional Interface
(such as Northbound Additional Interface-L), U2020 is authorized to
use the MML command interface.
b. For CN NEs, if Function contains Command Line Interface (such as
Command Line Interface-CN), U2020 is authorized to use the MML
command interface.

3.2 Negotiating Interconnection Parameters of the

Northbound MML Command Interface
Before the interconnection, U2020 needs to provide interconnection information to
the NMS.
For details about the information to be provided, see Table 3-1.

Table 3-1 Information to be provided by U2020

Parameter Parameter Value Description

Floating IP address of 10.121.77.248 Change the parameter

the U2020 server value as required.
NOTE
If a NAT device is deployed
between U2020 and the
NMS, the translated host
name and IP address are
configured on U2020 and
need to be provided to the
NMS during northbound
interconnection.
Log in to https://OSMU IP
address:31945, choose
System > System
Configuration >
Configure NAT, and view
the translated host name
and IP address.

U2020 port number 31114 Use the default

parameter value.

User name MMLUser Change the parameter

value as required, which
can be any user on the
client.

Password OSSnbi_123 Change the parameter

value as required.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 21

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

3.3 Preparations for the Commissioning of the

Northbound MML Command Interface
Before simulating the interconnection, you need to create a user that is authorized
to use the MML commands for NEs on the U2020 client.

3.3.1 Creating a User and Assigning Rights

Step 1 Log in to the U2020 client as the admin user, choose Security Management >
User Management. In the displayed page, choose Roles in the left pane and click
Create in the right pane.
Step 2 Enter a role name and click Next to create a role.

Step 3 Click Devices, select All Objects, and select the device to be managed. Click Next.

Step 4 Select the MML operation rights and click Finish.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 22

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

Step 5 Choose Security Management > User Management. In the displayed page,
choose Users in the left pane. Click Create in the right page to create a user.
Select Local, and enter a user name and password. In the Advanced Settings
area, deselect Force password change at the first login and click Next.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 23

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

Step 6 Select the created role and click Finish.

----End

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 24

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

3.3.2 Assigning MML Command Rights to the Specified User

or Role
This section describes the procedure for binding a new NE to a user on the U2020
client.

Procedure
Step 1 On the U2020 client, choose Security > NE User Management.
Step 2 In the navigation tree, choose MML Rights Manager.
Step 3 Select the role created in 3.3.1 Creating a User and Assigning Rights.
Select a device in the Managed Objects area, select an NE type under Command
Group, and select Command Group to select all MML commands.
Click Apply.

----End

3.3.3 Querying an Authorized MML Command

This section describes the procedure for querying an authorized MML command
on the U2020 client.

Procedure
Step 1 Choose Security > NE User Management, the NE User Management window is
displayed.
Step 2 In the navigation tree, choose MML Rights Manager.
Step 3 In the right pane, query an authorized MML command.

----End

3.4 Commissioning the Interconnection of the

Northbound MML Command Interface
In the commissioning of the northbound MML command interface
interconnection, you need to simulate the interconnection, check the
interconnection result, and determine whether the northbound MML command

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 25

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

interface meets the conditions for interconnecting with the NMS based on the
interconnection result.

3.4.1 Connection Configuration File of the MML Command

Interface
U2020 provides the configuration file /export/home/ossshare/U2020/
IRPService/etc/IRPService/NMSMMLServer/SSLOption.xml (U2020 is an
example product alias. You can run the ls /opt/cloud/ |grep (U2020 command to
obtain the actual product alias.) for you to set SSL and non-SSL connection
parameters. You can modify this configuration file to connect to the MML
command interface in SSL or non-SSL connection mode.

Overview
The configuration file SSLOption.xml is used to configure whether to use SSL
connection and, when SSL connection is used, configure SSL connection policies.

Connection Parameters
The configuration items in SSLOption.xml are used to configure connection
parameters related to northbound interface operations. Table 3-2 describes these
configuration items.

Table 3-2 Configuration items in SSLOption.xml

Par Descriptio Reference
am n
ete
r

ena Whether ● true: SSL connection is used.

ble to use SSL ● false: Non-SSL connection is used.
SSL connection
The default value is true.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 26

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

Par Descriptio Reference

am n
ete
r

ver SSL The default value is TLSv1.2.

sio protocol NOTE
n version ● The SSLv3 and TLSv1.0 protocols have security risks. If you do not
need to use them, disable them according to Disabling the
SSLv3 Protocol Used on the U2020 and Disabling the TLSv1.0
Protocol Used on the U2020 in U2020 Administrator Guide.
● Since V200R018C10, SSLv3 and TLSv1.0 are disabled by default
for security purposes in new installation scenarios. You are
advised not to enable SSLv3 and TLSv1.0. If you need to enable
them, see Enabling the SSLv3 Protocol Used on the U2020 and
Enabling the TLSv1.0 Protocol Used on the U2020 in U2020
Administrator Guide.
● In V300R019C10SPC520 and later versions, SSLv3, TLSv1.0, and
TLSv1.1 are disabled by default for security purposes in new
installation scenarios. You are not advised to enable them. If they
are required, perform the following operations after setting the
version parameters:
Log in to the master service node of the target OSS as the
ossuser user and run the following commands:
~>mkdir -p /export/home/ossshare/U2020/IRPService/conf/ssl
~> cp -rf /opt/oss/apps/IRPService/conf/ssl/
cipherSuiteConfig.xml /export/home/ossshare/U2020/IRPService/
conf/ssl
Restart the northbound services.
~>. /opt/oss/apps/IRPService/tools/env_profile.sh
~>nbi_adm -cmd restart CORBA
In the preceding commands, U2020 is only an example. Change
it based on the site requirements, for example, to U2020-1.

enc Encryption This parameter can be set to high or all. The default value is
ryp level high.
tLe The encryption levels are defined in the algorithm list
vel file /opt/oss/apps/IRPService/rtsp/iMAP_Common/
conf/ssl/cipherSuiteConfig.xml. You can select different
algorithm lists from this file to implement security and
performance control. The mapping relationships between
encryption levels and algorithm lists vary with SSL protocol
versions. The algorithm names in this file are consistent with
those defined by the SSL protocol.

ena Whether ● true: The server authenticates the client and an identity
ble to certificate must be deployed on the client. The server
Aut authentica determines whether the client identity certificate is valid
hP te the based on the trust certificate deployed on the server.
eer client. ● false: The server does not authenticate the client and no
identity certificate needs to be deployed on the client.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 27

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

Par Descriptio Reference

am n
ete
r

ena Whether ● true: The session is reused.

ble to reuse a ● false: The session is not reused.
Ses session.
sio The default value is true.
nR
eus
e

ses Timeout Valid interval between reusing a session. The parameter

sio period for value must be an integer in the unit of second.
nTi reusing a The default value is 300.
me session.
out

ena Whether ● true: SSL and non-SSL ports are automatically adapted.
ble to ● false: SSL and non-SSL ports are not automatically
SSL automatic adapted.
Por ally adapt
tAu to SSL and This parameter cannot be modified.
toA non-SSL
da ports.
pt

3.4.2 Modifying the Connection Configuration File of the MML

Command Interface
This section describes how to modify the connection configuration file
SSLOption.xml to change the connection mode from the default SSL connection
to non-SSL connection.

Prerequisites
You have logged in to the U2020 (active or master) server as user ossuser.

Context
After you modify SSLOption.xml, restart the IRPService service for the
modifications to take effect.
Perform the following operations on the U2020 master service node.

Procedure
Step 1 Edit the configuration file.
vi /export/home/ossshare/U2020/IRPService/etc/IRPService/NMSMMLServer/
SSLOption.xml>

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 28

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

(U2020 is an example product alias. You can run the ls /opt/cloud/ |grep (U2020
command to obtain the actual product alias.)

----End

3.4.3 Simulating the Interconnection with the NMS in

Unencrypted Connection Mode (MML Command Interface)
When the NMS successfully logs in to the specified port of the U2020 by using the
provided user information, the interconnection is complete.

Prerequisites
● The NMS has been licensed to use the MML command interface.
● The enableSSL is set to false in /export/home/ossshare/U2020/
IRPService/etc/IRPService/NMSMMLServer/SSLOption.xml.
(U2020 is an example product alias. You can run the ls /opt/cloud/ |grep
(U2020 command to obtain the actual product alias.)

Context
Perform the following operations on the U2020 master service node.

Procedure
Step 1 Remotely log in to port 31114 of the U2020 server.

For example, enter telnet floating IP address of the U2020 server 31114 for the
remote login.

Step 2 Log in to the port by using the information about the user that is already created.

For example, enter LGI:OP="MMLUser",PWD="OSSnbi_123"; for the login.

----End

3.4.4 Simulating the Interconnection with the NMS in SSL

Connection Mode (MML Command Interface)
When the NMS successfully logs in to the specified port of the U2020 by using the
provided user information, the interconnection is complete.

Prerequisites
● You have modified the configuration file /export/home/ossshare/U2020/
IRPService/etc/IRPService/NMSMMLServer/SSLOption.xml.
(U2020 is an example product alias. You can run the ls /opt/cloud/ |grep
(U2020 command to obtain the actual product alias.)
● The NMS has been licensed to use the MML command interface.
● When enableAuthPeer is set to true in SSLOption.xml, you have obtained
the certificates from the NMS, including the trust certificate, device certificate
on the client, and the private key of the device certificate on the client.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 29

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

Context
Perform the following operations on the U2020 master service node.

Procedure
Step 1 The NMS remotely logs in to the specified port of the U2020 server to simulate
the interconnection with the U2020.
For example, run the following commands on the PC where OpenSSL is installed
to simulate the client:
● When enableAuthPeer is set to true, run the following commands:
openssl s_client -CAfile CA trust certificate -cert device certificate on the
client -key private key of the device certificate on the client -port 31114 -
host floating IP address of the server -tls1_2 -quiet -crlf
● When enableAuthPeer is set to false, run the following commands:
openssl s_client -port 31114 -host floating IP address of the server -tls1_2
-quiet -crlf

The OpenSSL parameter -tls1_2 corresponds to the TLSv1.2 version. During the
interconnection, use the OpenSSL parameter based on the version value set in
SSLOption.xml.
If the TLSv1.2 protocol is used, the OpenSSL tool later than the 1.0.1p version must be used.
If you need to use a third-party certificate for the interconnection with the NMS, replace
the existing certificate with a third-party certificate by following the instructions provided in
section "Certificate Management" in the product documentation. You must stop all U2020
services before the replacement. After the replacement, start all U2020 services again.
The SSLv3 and TLSv1.0 protocols have security risks. If you do not need to use them, disable
them according to Disabling the SSLv3 Protocol Used on the U2020 and Disabling the
TLSv1.0 Protocol Used on the U2020 in U2020 Administrator Guide.
Since V200R018C10, SSLv3 and TLSv1.0 are disabled by default for security purposes in
new installation scenarios. You are advised not to enable SSLv3 and TLSv1.0. If you need to
enable them, see Enabling the SSLv3 Protocol Used on the U2020 and Enabling the
TLSv1.0 Protocol Used on the U2020 in U2020 Administrator Guide.
By default, the public key of the Diffie-Hellman algorithm contains 2048 bits. If the NMS
does not support the Diffie-Hellman algorithm with the 2048-bit public key, change the
default public key length of the Diffie-Hellman algorithm to 1024 bits, resulting in security
risks. For details, see 4.5 How Do I Change the Public Key Length of the Diffie-Hellman
Algorithm?

Step 2 Log in to the port by using the information about the user that is already created.
For example, enter LGI:OP="MMLUser",PWD="OSSnbi_123"; for the login.

----End

3.4.5 Checking the CloudEdge NE Interconnection Effect

This section describes how to check the CloudEdge NE interconnection effect.

Prerequisites
You have registered a VNFC.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 30

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

Procedure
Step 1 Simulate the interconnection with the NMS in non-encryption mode. Remotely log
in to the U2020 server through port 31114.

For example, telnet Floating IP address of the U2020 server 31114

Step 2 Use an existing user account to log in to the U2020 server.

For example, LGI:OP="User name",PWD="User password";

Step 3 Run the following command to query NE information:

LST NEBYOMC:; (All letters in the command are in uppercase.)

Step 4 Send an MML command to register an NE.

● Register an NE using the IP address.
The command syntax is as follows, with all letters being in uppercase:
REG NE:IP="IP address";
● Register an NE using the NE name.
The command syntax is as follows, with all letters being in uppercase:
REG NE:NAME="NE name";

Step 5 Query the VNFCs of the registered CloudEdge NE.

Run the LST VNFCBYNE:; command with all letters being in uppercase:

Step 6 Send an MML command to register a VNFC.

The command syntax is as follows, with all letters being in uppercase:

REG VNFC:NAME="VNFC name";

Step 7 Simulate the NMS to send a command to the registered VNFC and view the
command output.

After receiving a command, the U2020 immediately forwards it to a specific NE.

The command syntax is as follows, with all letters being in uppercase:

DSP DATETIME:;

The following information is displayed:

+++ gsc 2017-02-21 16:48:01
O&M #1879048211
%%/*1879048211*/DSP DATETIME:;%%
RETCODE = 0 Operation Success.

The result is as follows

------------------------
Current Time = 2017-02-21 16:48:01
Week Day Information = Tuesday
(Number of results = 1)
--- END

----End

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 31

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

3.4.6 Setting an IP Address Whitelist for the MML Command

Interface
This section describes how to set an IP address whitelist for the MML command
interface. After an IP address whitelist is configured for the MML command
interface, only IP addresses in the whitelist are allowed to connect to the MML
command interface of the U2020 in socket mode.

Procedure
Step 1 Start a browser and visit https://U2020 server IP address:31943.

Step 2 On the U2020 client, choose Maintenance > OSS Maintenance Tool > NBI
Management.

Step 3 In the navigation tree, choose Parameters Settings.

Step 4 Select Northbound Command Line Interface from the Northbound Interface
Name drop-down list.

Step 5 Select NmsMmlParam.xml from the Configuration file name drop-down list.

Step 6 Enter IP addresses in the allowed ip list text box.

Separate multiple IP addresses with vertical bars (|). A maximum of 100 IP addresses can be
configured in a whitelist.
By default, the allowed ip list text box is empty, indicating no IP address restriction during
interconnection.

Step 7 Click Save&Restart.

----End

3.5 (Optional) Hiding or Unhiding Security Information

in MML Command Outputs
Northbound MML command outputs may contain plaintext security information.
This section describes how to hide or unhide plaintext security information in
MML command outputs.

Context
Northbound MML command outputs may contain plaintext security information,
for example, plaintext passwords. Plaintext security information can be hidden
(replaced by *) over the northbound MML command line interface.

By default, plaintext security information is not hidden. You can use either of the
following methods to hide plaintext security information:

● Hiding plaintext security information by running commands

● Hiding plaintext security information on the U2020 client

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 32

U2020
Northbound Command Line Interface Developer 3 Interconnection Commissioning of the Northbound
Guide MML Command Interface

Procedure
● Hiding plaintext security information by running commands
a. Log in to the U2020 server as user ossuser.
b. Run the following commands:
> . /opt/oss/apps/SystemService/svc_profile.sh
> SettingTool -cmd setparam -path /imap/nbi/nmsmml/
mmlSecInfoHide -value "true"
To unhide security information, run the following commands:
> . /opt/oss/apps/SystemService/svc_profile.sh
> SettingTool -cmd setparam -path /imap/nbi/nmsmml/
mmlSecInfoHide -value "false"
● Hiding plaintext security information on the U2020 client
a. Start a browser and visit https://U2020 server IP address:31943.
b. On the U2020 client, choose Maintenance > OSS Maintenance Tool > NBI
Management.
c. In the navigation tree, choose Parameters Settings.
d. Select Northbound Command Line Interface from the Northbound
Interface Name drop-down list.
e. Select Command Line Parameter Setting from the Configuration file
name drop-down list.
f. In the Command Line Parameter Setting area, set mmlSecInfoHide to
true.
To unhide security information, set it to false.
g. Click Save after the modification is complete.
You can view the operation result in Service Restarted Log. When the
operation is successful, the parameter setting takes effect.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 33

U2020
Northbound Command Line Interface Developer 4 Troubleshooting for the Northbound MML
Guide Command Interface

4 Troubleshooting for the Northbound

MML Command Interface

About This Chapter

This describes how to troubleshoot the northbound MML command interface. If a
fault occurs when the NMS is interconnected to the U2020 through the
northbound MML command interface, refer to this chapter for handling the fault.
4.1 Common Troubleshooting and Information Collection (MML Command
Interface)
4.2 Troubleshooting Failure to Issue MML Commands
4.3 How Do I Handle a Closed SSL Connection?
4.4 What Do I Do If the ping Command Cannot Be Stopped in the Current NMS
Client?
4.5 How Do I Change the Public Key Length of the Diffie-Hellman Algorithm?
4.6 How Do I Enable the SSL Connection Mode?

4.1 Common Troubleshooting and Information

Collection (MML Command Interface)
If a fault occurs when the NMS interconnects to the U2020 through the
northbound MML command interface, rectify the fault according to common
troubleshooting methods. If it is not possible to rectify the fault by using the
common troubleshooting methods, collect the fault information and contact
Huawei engineers for assistance.

Troubleshooting
For the common troubleshooting methods, see Table 4-1.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 34

U2020
Northbound Command Line Interface Developer 4 Troubleshooting for the Northbound MML
Guide Command Interface

Table 4-1 Troubleshooting

Common Fault Troubleshooting Method

Issuing MML commands See 4.2 Troubleshooting Failure to Issue MML

fails. Commands.

How to Handle the Closed See 4.3 How Do I Handle a Closed SSL
SSL Connection Problem Connection?.

Information Collection
If a fault not included in Table 4-1 occurs when the NMS is obtaining the data,
you need to collect relevant information for fault localization. Table 4-2 lists the
information to be collected and the collection methods.

Table 4-2 Information to be collected

Related Information Description

Operation information The operation information records the

operations performed before a fault occurs and
the troubleshooting measures taken later.

Version information You need to obtain the information about the

U2020 version, NE mediation version, and NE
version.

IP address information You need to obtain the floating IP address

information about the U2020 server.

Log information NOTE

Perform the following operations on the U2020
master service node.
You can obtain logs from the /export/home/
ossshare/U2020/IRPService/log/ directory.
(The directory is only an example. Replace it
with the actual name.). The trace file of the
MML interface is iMAP.irp_agent.trace.

4.2 Troubleshooting Failure to Issue MML Commands

This section describes how to troubleshoot the failure to issue MML commands
caused by NE disruption.

Problem Description
The NMS fails to issue an MML command.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 35

U2020
Northbound Command Line Interface Developer 4 Troubleshooting for the Northbound MML
Guide Command Interface

Troubleshooting
The NMS fails to issue the MML command possibly due to NE disruption.

Handling NE Disconnection Faults

1. On the U2020 client, choose Topology > Main Topology. In the Main
Topology window, right-click the disconnected NE and then choose
Reconnect NE.
2. Verify the network and rectify the network fault.
3. Rectify the fault on the NE mediation. To reinstall the NE mediation, see the
Commissioning Guide of the corresponding U2020 networking mode.

Solution
Contact Huawei technical support.

4.3 How Do I Handle a Closed SSL Connection?

This section describes how to locate the cause when the SSL connection between
the NMS and the U2020 server is closed.

Question
The SSL connection between the NMS and the U2020 server is closed.

Solution

SSL connection transmits data based on records and TCP/IP connection transmits data
based on streams. In SSL connection, a sending error occurs when the client end receives
data too slowly or even cannot receive data, or the data transmission times out.

Perform the following steps to determine whether the closed SSL connection
problem is caused by a sending error. When a sending error occurs, the U2020
server (server end of SSL connection) automatically closes the SSL connection.

1. Log in to the U2020 client.

2. Choose Security > Log Management > Query System Logs.

3. In the Filter Criteria dialog box, click . In the displayed Source dialog box,
select a northbound interface. For example, select FMNotify for the alarm
streaming interface and NMSMMLServer for the MML command interface.
4. In the Basic Information area, select SSL connection is closed.
– There is a record: This problem is caused by a sending error. As a result,
the U2020 server automatically closes the SSL connection. In this
situation, the NMS needs to re-initiate the SSL connection to the U2020
server.
– There is no record: This problem is not caused by a sending error. In this
situation, contact Huawei technical support.

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 36

U2020
Northbound Command Line Interface Developer 4 Troubleshooting for the Northbound MML
Guide Command Interface

4.4 What Do I Do If the ping Command Cannot Be

Stopped in the Current NMS Client?
This section describes how to resolve the problem that the ping command cannot
be stopped in the current NMS client.

Question
The ping command cannot be stopped in the current NMS client.

Solution
The command line interface forwards MML commands to NEs without processing
and can forward MML commands to NEs in the same connection only after the
execution result is returned. If the command line interface forwards the ping
command and the number of times for performing ping operations has been
specified, the current NMS client keeps receiving the execution result of the ping
command and cannot be used to forward the command for stopping the ping
command. To stop the ping command, perform the following operations:

1. Restart a new NMS client and remotely log in to the U2020 through port
31114. For details, see 2.1.1 Login.
2. Register NEs. The registered NEs should be consistent with those registered
when the ping command is issued. For details, see 2.1.3 Registering an NE.
3. Forward the MML command (__STP:;) for stopping the ping command to NEs.
For details, see 2.2.1 Transmitting MML Commands.
4. Deregister NEs. For details, see 2.3.2 Deregistering an NE.
5. Disconnect the U2020. For details, see 2.3.3 Logout.

4.5 How Do I Change the Public Key Length of the

Diffie-Hellman Algorithm?
By default, the public key of the Diffie-Hellman algorithm contains 2048 bits. This
section describes how to change the public key length of the Diffie-Hellman
algorithm to 1024 bits. The 1024-bit public key has security risks.

Prerequisites
You have logged in to the U2020 server as user ossuser.

Procedure
Step 1 Run the following command to open the configuration file SSLOption.xml and
modify the public key length of the Diffie-Hellman algorithm:

vi /export/home/ossshare/U2020/IRPService/etc/IRPService/NMSMMLServer/
SSLOption.xml>

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 37

U2020
Northbound Command Line Interface Developer 4 Troubleshooting for the Northbound MML
Guide Command Interface

(U2020 is an example product alias. You can run the ls /opt/cloud/ |grep (U2020
command to obtain the actual product alias.)

Add the public key length of the Diffie-Hellman algorithm between PARAS nodes.
The contents after the modification are as follows:
<?xml version="1.0" encoding="utf-8"?>
<COMMINIDATA>
<AREADESC areaname="ssl">
<DESC descname="options">
<PARAS>
..................................
<PARA name="secureDHLen" value="1024"/>
</PARAS>
</DESC>
</AREADESC>
</COMMINIDATA>

Step 2 Press Esc, input:wq and press Enter, save the file and quit.

Step 3 Run the following commands to restart the IRPService service for the
configuration to take effect: > . /opt/oss/apps/IRPService/tools/env_profile.sh>
nbi_adm -cmd restart IRPService

----End

4.6 How Do I Enable the SSL Connection Mode?

Context
The SSL connection mode improves system security. You are advised to enable this
mode.

Procedure
Step 1 Log in to the U2020 client and choose Maintenance > OSS Maintenance Tool >
NBI Management.

Step 2 In the navigation tree, choose Northbound Configuration Parameters Settings.

Step 3 In the right pane, set Northbound Interface Name to the Northbound
Command Line Interface, and Configuration file Name to SSLOption.xml.

Step 4 Set enableSSL to true, set version, and click Save&Restart.

For details about enableSSL and version, see the following table.

Paramete Descripti Description

r on

enableSSL Whether ● true: SSL connection is used.

to use ● false: Non-SSL connection is used.
SSL
connectio The default value is true.
n

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 38

U2020
Northbound Command Line Interface Developer 4 Troubleshooting for the Northbound MML
Guide Command Interface

Paramete Descripti Description

r on

version SSL The default value is TLSv1.2.

protocol NOTE
version ● The SSLv3 and TLSv1.0 protocols have security risks. If you
do not need to use them, disable them according to
Disabling the SSLv3 Protocol Used on U2020 and
Disabling the TLSv1.0 Protocol Used on U2020 in U2020
Administrator Guide.
● Since V200R018C10, SSLv3 and TLSv1.0 are disabled by
default for security purposes in new installation scenarios.
You are advised to disable SSLv3 and TLSv1.0. If you need
to enable them, see Enabling the SSLv3 Protocol Used on
U2020 and Enabling the TLSv1.0 Protocol Used on
U2020 in U2020 Administrator Guide.
● In V300R019C10SPC520 and later versions, SSLv3, TLSv1.0,
and TLSv1.1 are disabled by default for security purposes
in new installation scenarios. You are advised to disable
them. If they are required, perform the following
operations after setting the version parameters:
Log in to the master service node of the target OSS as the
ossuser user and run the following commands:
~>mkdir -p /export/home/ossshare/U2020/IRPService/
conf/ssl
~> cp -rf /opt/oss/apps/IRPService/conf/ssl/
cipherSuiteConfig.xml /export/home/ossshare/U2020/
IRPService/conf/ssl
Restart the northbound services.
~>. /opt/oss/apps/IRPService/tools/env_profile.sh
~>nbi_adm -cmd restart CORBA
In the preceding commands, U2020 is only an example.
Change it based on the site requirements, for example, to
U2020-1.

----End

Issue 01 (2019-08-30) Copyright © Huawei Technologies Co., Ltd. 39