Northbound MML Command Interface Developer Guide
Northbound MML Command Interface Developer Guide
V200R009
Issue 01
Date 2009-08-29
Website: http://www.huawei.com
Email: [email protected]
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Contents
Figures
Tables
Purpose
This document provides the guide to the M2000 Northbound MML command transparent
transmission interface. It consists of the following contents: meaning and interconnection
parameters of the Northbound MML command transparent transmission interface,
interconnection of the Northbound MML command transparent transmission interface, and
Northbound MML command transparent transmission.
Related Versions
The following table lists the product versions related to this document.
M2000 V200R009
Intended Audience
The intended audiences of this document are:
l Network administrator
Update History
01 (2009-06-30)
Initial release. Also, the first formal release.
Organization
This describes the definition of the Northbound interface, and the implementation and
interconnecting parameters of the Northbound MML command transparent transmission
interface.
This describes the transparent transmission of the Northbound MML command, which consists
of connecting the MML command transparent transmission, maintaining the MML command
transparent transmission, and disconnecting the MML command transparent transmission.
Before interconnecting the NMS with the M2000, you must conduct an interconnection
commissioning. Based on the commissioning result, determine whether the northbound MML
interface meets the conditions for interconnecting with the NMS.
This describes how to troubleshoot the northbound MML interface. If a fault occurs when the
NMS is interconnected to the M2000 through the northbound MML interface, refer to this
chapter for handling the fault.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
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
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
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.
Format Description
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.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
This describes the definition of the Northbound interface, and the implementation and
interconnecting parameters of the Northbound MML command transparent transmission
interface.
In the mobile communication network, the M2000 is an EMS. The M2000 reports the alarm,
configuration, performance and inventory data to the NMS through the northbound interface.
Implementation
Table 1-1 describes the process for implementation.
Log in to the M2000 server as user Currently, the MML command interface supports
M2000. Establish the remote a maximum of 64 remote connections. If the
connection between the NMS and the number of connections is greater than 64, the
M2000. For example, through telnet. system denies the connection.
The M2000 authenticates the received l If the authentication is successful, the login
information about the user account. success message is displayed.
l 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 to operation object is the M2000.
operate.
The M2000 transparently transmits an The packet of the NE is displayed to the NMS.
MML command sent by users to the NE.
NOTE
Using a command, the NMS can switch to operate another NE at any time. The NMS, however, can operate
one NE at a time.
No. Operation
2 The NMS sends the name and password of the user who logs in to the system to
the M2000 for authentication.
9 If the connection fails, the M2000 replies the northbound with the connection
failure message.
No. Operation
This describes the transparent transmission of the Northbound MML command, which consists
of connecting the MML command transparent transmission, maintaining the MML command
transparent transmission, and disconnecting the MML command transparent transmission.
Context
Strictly conform to the format of MML commands when using the MML commands. The
symbols : and ; are mandatory for the MML commands. Type all the MML commands and press
Enter to end.
2.1 Connecting the MML Command Transparent Transmission
This describes the connecting the MML command transparent transmission, which consists of
login, listing operable NEs, and registering an NE.
2.2 Maintaining the MML Command Transparent Transmission
This describes the procedure for maintaining the MML command transparent transmission,
which consists of MML command transparent transmission, sending handshake messages, and
sending disconnection messages when disconnecting.
2.3 Disconnecting the MML Command Transparent Transmission
This describes the procedure for disconnecting the MML command transparent transmission,
which consists of deregistering an NE and logout.
2.1.1 Login
The NMS remotely logs in to the M2000 server through the MML service port to connect to the
M2000 server.
2.1.2 Listing Operable NEs
This describes the procedure for listing operable NEs.
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 M2000.
2.1.1 Login
The NMS remotely logs in to the M2000 server through the MML service port to connect to the
M2000 server.
Prerequisite
The M2000 user is created on the M2000 M2000 client. For details, see 3.2.1 Creating a
User.
Procedure
Step 1 Remotely connect to port 31114 of the M2000 server.
For example, telnet 10.121.77.248 31114
Step 2 Run the following command to log in to the M2000 server:
The command syntax is as follows:
LGI:OP="MML user", PWD="password of MML user";
For example, LGI:OP="MMLUser",PWD="M2000nbi";
l If the M2000 returns RETCODE = 0 Success, you can infer that logging in to the
M2000 server is successful.
l If the M2000 returns RETCODE = 1 Error Message, you can infer that logging in to
the M2000 server fails.
The possible reasons for the failure are as follows: The M2000 user is not created, the
M2000 user and password are incorrect, and the M2000 user is locked.
----End
Procedure
Step 1 Use the telnet command to connect to the port 31114 of the M2000 server.
Step 2 The NMS sends the command for logging in to the M2000.
For details about how to log in to the M2000, see 2.1.1 Login.
Step 3 The NMS sends the LST NE command to list all the NEs that can be operated by the current
user.
LST NE:;
If the LST NE command runs successfully, the following packet is displayed by the M2000:
+++ NMS SERVER 2006-03-02 12:09:25
O&M #2304
%%LST NE:;%%
RETCODE = 0 Success
LST NE Info
-----------------------------
--- END
If the LST NE command runs unsuccessfully, the following packet is displayed by the M2000:
+++ NMS SERVER 2006-03-02 12:09:25
O&M #2304
%%LST NE:;%%
RETCODE = 1 Error Message
Error Message
--- END
NOTE
l If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is displayed.
l To type the parameter for Info, refer to the parameter that is different during the registration of the
NMS.
TIP
The LST NE command is optional. If the NMS needs to maintain the IP of an NE, the NMS can directly
send the registration command.
----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 M2000.
Procedure
Step 1 Use the telnet command to connect to the port 31114 of the M2000 server.
Step 2 The NMS sends the login command to log in to the M2000.
For details, refer to 2.1.1 Login.
Success
--- END
NOTE
l If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is displayed.
l Error Message indicates the detailed error message.
l Registering an NE Through NE Name
The format of the command is as follows:
REG NE:NAME="NodeB_czh";
Based on the parameters in the REG NE command, the M2000 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 M2000:
+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%% REG NE: NAME ="NodeB_czh";%%
RETCODE = 0 Success
Success
--- END
NOTE
l If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is displayed.
l Error Message indicates the detailed error message.
TIP
l 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.
l 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 M2000 automatically
disconnects the previous NE that is maintained.
----End
Prerequisite
Only when an MML command transparently transmitted is authorized.
Procedure
Step 1 Use the telnet command to connect to the port 31114 of the M2000 server.
After the connection is successful, the transparent transmission can be performed.
After receiving a command, the M2000 immediately forwards it to a specific NE, The format
of the command is as follows:
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
NOTE
----End
Prerequisite
l The script contains only the MML commands that are authorized to be used on the
corresponding NE.
l The script is uploaded to the /export/home/sysm/ftproot/itf_n/nms_mml_server/script
directory on the M2000 server.
Context
l The script must be in .txt format. The M2000 needs to maintain the script that is uploaded
in ASC mode and saved in the /export/home/sysm/ftproot/itf_n/nms_mml_server/
script directory.
l The file containing the script execution results is saved in the /export/home/sysm/ftproot/
itf_n/nms_mml_server/result directory. The M2000 automatically deletes the result files
generated three days ago.
l The M2000 automatically names the result files. The name convention is as follows: name
of the script to be activated_time when the script is activated_the name of the user that
remotely logs in to the M2000 server for using the MML service_random number.rst.
The format of the 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 2009-5-11.Multiple results files are
generated when multiple users remotely and simultaneously log in to the M2000 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.
l If the current user is activating a script, he or she cannot activate another script at the same
time.
l 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.
l In the script, different MML commands are located in different lines. {} is added to each
MML command to specify the NE to which the command is to be issued. If you need not
specify any NE, no {} is 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 you need not specify any NE to which the LST BRD:; command is issued,
the script is as follows:
LST CELL:; {rnc_l,rnc_2}
LST PRACH:; {rnc_l}
LST BRD:;
Procedure
Step 1 Remotely log in to the port numbered 31114 on the M2000 server. For example, log in to the
port through telnet.
Step 2 Specify the NEs in the activation command or script. Run the following command to activate
the script:
l 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 named
rnc_1 and rnc_2 and save the execution results to the file named name of the script to be
activated_time when the script is activated_the name of the user that remotely logs in to
the M2000 server for using the MML service_random number.rst. For example, a file is
named testMML2_20090511171950_UserName_102.rst.
S_ACTIVATE: FILE="testMML2.txt", NELIST="{rnc_1,rnc_2}";
If the system output is as follows, 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 output is as follows, you can infer that the script is failed. Rectify the fault
according to the error message.
S_ACTIVATE FAILED; REASON=insufficient privilege
l Specify the NEs to which the MML commands are to be issued in the script.
Run the following command to deliver the script named 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_the name of the user that remotely logs in to the M2000 server for
using the MML service_random number.rst. For example, a file is named
test1_20090511171950_UserName_102.rst.
S_ACTIVATE: FILE="test1.txt";
If the system output is as follows, 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 output is as follows, you can infer that the script is failed. Rectify the fault
according to the error message.
S_ACTIVATE FAILED; REASON=insufficient privilege
----End
Procedure
Step 1 Use the telnet command to connect to the port 31114 of the M2000 server.
Step 2 Run the following command.
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
--- END
----End
Procedure
Step 1 The M2000 sends an NE disconnection message to the NMS.
The packet sent by the M2000 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.1 Deregistering an NE
Registering an NE requires the system resource. Thus, if the NMS does not maintain an NE, you
need to deregister the NE to release the resource.
2.3.2 Logout
When you log out of the M2000 and disconnect the M2000, you need send the
LGO:OP="MMLUser"; command.
2.3.1 Deregistering an NE
Registering an NE requires the system resource. Thus, if the NMS does not maintain an NE, you
need to deregister the NE to release the resource.
Prerequisite
You have registered an NE and obtained the IP address or name of the NE.
Context
You can use the IP address or the name of an NE to degegister the NE.
Procedure
Step 1 Use the telnet command to connect to the port 31114 of the M2000 server.
Step 2 The NMS sends the login command to log in to the M2000.
For details, refer to 2.1.1 Login.
Step 3 Deregistering an NE.
l Deregistering an NE Through IP Address
The format of the command is as follows:
UNREG NE:IP="10.161.198.243";
If the logout is successful, the packet displayed by the M2000 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
NOTE
l If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is displayed.
l Error Message indicates the detailed error message.
l Deregistering an NE Through NE Name
The format of the command is as follows:
UNREG NE:NAME ="NodeB_czh";
If the logout command runs successfully, the packet displayed by the M2000 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 M2000 is as follows:
NOTE
l If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is displayed.
l 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
2.3.2 Logout
When you log out of the M2000 and disconnect the M2000, you need send the
LGO:OP="MMLUser"; command.
Prerequisite
You have logged in to port 31114 of the M2000 server.
Procedure
Step 1 In the login window, run the following command.
LGO:OP="MMLUser";
If the logout is successful, the packet displayed by the M2000 is as follows:
+++ NMS SERVER 2006-03-02 11:57:11
O&M #2304
%%LGO:OP="MMLUser";%%
RETCODE = 0 Success
Success
--- END
NOTE
l If RETCODE is successful, the displayed value is 0; if RETCODE fails, an error code is displayed.
l 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
Before interconnecting the NMS with the M2000, you must conduct an interconnection
commissioning. Based on the commissioning result, determine whether the northbound MML
interface meets the conditions for interconnecting with the NMS.
Checking License
Before interconnecting the M2000 and the NMS, check whether the NMS is licensed to use the
MML interface.
1. Log in to the M2000 client.
2. Choose Help > License Information. The License Information window is displayed.
3. Click the Function control item tab. If License name contains Command Line
Interface, you can infer that the NMS is authorized to use the MML interface.
Port number of the M2000 31114 Indicates the number of the port
that is used to receive NMS
connection requests and MML
commands.
Use the default parameter value.
Procedure
Step 1 Choose Security > Security Management.
The Security Management window is displayed, as shown in Figure 3-1.
Step 2 Select the User node from the navigation tree, as shown in Figure 3-2.
Step 4 Type the user name MMLUser and the password M2000nbi.
For other information, use the default system settings.
----End
Procedure
Step 1 Choose Security > Security Management.
The Security Management window is displayed, as shown in Figure 3-4.
Step 2 Select the User node from the navigation tree, as shown in Figure 3-5.
----End
Procedure
Step 1 Choose Security > Security Management.
The Security Management window is displayed, as shown in Figure 3-8.
Step 2 Select MMLUser under the User node to view the detailed user information, as shown in Figure
3-9.
Step 3 Select the Binded NE tab to view the bound NE list, as shown in Figure 3-10.
----End
Procedure
Step 1 Choose Security > NE User Management.
The NE User Management window is displayed, as shown in Figure 3-12.
The command group that can be operated by the user is displayed on the top right of the GUI.
Select a command group and the MML command assigned to the rights is displayed.
NOTE
For details of the operation method, refer to the Managing NE Users in M2000 Operator Guide.
----End
Procedure
Step 1 Remotely log in to port 31114 of the M2000 server.
For example, enter telnet IP address of the M2000 server 31114 for the remote login.
Step 2 Log in to the port by using the information about the user that is already created.
----End
Prerequisite
The simulation of the NMS interconnection is complete. The NMS have successfully logged in
to the specified port of the M2000 server.
Procedure
Step 1 Issue an MML command and check the returned information.
For example, issue the LST NE:; command and check whether the returned information includes
the types, names, and IP addresses of the NEs that you are authorized to query. If the returned
information includes the types, names, and IP addresses of the relevant NEs, you can infer that
the interconnection is successful. Otherwise, you can infer that the interconnection fails. For
details about how to handle the interconnection failure, see 4 Troubleshooting for the
Northbound MML Interface.
Step 2 To exit the interconnection, see 2.3 Disconnecting the MML Command Transparent
Transmission.
----End
The M2000 system can adopt the following networking modes: single-server system, HA
system, remote HA system, and SLS system. For details about how to use the northbound MML
interface in different networking modes, see Table 3-2.
This describes how to troubleshoot the northbound MML interface. If a fault occurs when the
NMS is interconnected to the M2000 through the northbound MML interface, refer to this
chapter for handling the fault.
Troubleshooting
For the common troubleshooting methods, see Table 4-1.
Issuing MML commands fails. See 4.2 Handling the Failure of Issuing MML
Commands.
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 that needs to
be collected and the collection methods.
Version information You need to obtain the information about the M2000
version, NE mediation version, and NE version.
Problem Description
The NMS fails to issue an MML command.
Troubleshooting
The NMS fails to issue the MML command possibly due to NE disruption.
Solution
Contact Huawei engineers for assistance.