SJ-20101227165724-011-NetNumen M31 (RAN) (V12.10.032) MML Terminal Operation Guide PDF

NetNumen M31(RAN)
Mobile Network Element Management System

MML Terminal Operation Guide
Version: 12.10.032
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2011-02-28 First Edition
R1.1 2011-04-25 This revision provides an introduction to man-machine language

in an additional appendix.
Serial Number: SJ-20101227165724-011
Publishing Date: 2011-04-25(R1.1)

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 MML Terminal Overview ..................................................................................... 1-1
1.2 GUI of the MML Terminal .................................................................................... 1-2
1.3 Setting Preferences ............................................................................................ 1-3
1.4 Implicit Prerequisites .......................................................................................... 1-5
Chapter 2 Using the MML Terminal........................................................... 2-1

2.1 Running a Command on the MML Tree ............................................................... 2-1
2.2 Running a Command by Manual Input ................................................................. 2-3
2.3 Searching for an MML Command ........................................................................ 2-4
2.4 Getting the Help of an MML Command ................................................................ 2-5
2.5 Querying History Commands .............................................................................. 2-6
2.6 Viewing Uploaded Messages .............................................................................. 2-7
2.7 Operations on Command Results ........................................................................ 2-8
2.7.1 Clearing the Command Results................................................................. 2-8
2.7.2 Saving the Command Results ................................................................... 2-9
2.8 Operations on History Commands ..................................................................... 2-10
2.8.1 Saving History Commands...................................................................... 2-10
2.8.2 Deleting History Commands.................................................................... 2-10
Chapter 3 Batch File Operations............................................................... 3-1

3.1 Importing a Batch File......................................................................................... 3-1
3.2 Running the Commands of a Batch File ............................................................... 3-2
3.3 Saving a Batch File ............................................................................................ 3-3
3.4 Clearing the Running Result of a Batch File ......................................................... 3-3
3.5 Clearing the Imported Batch File Contents ........................................................... 3-4
Chapter 4 Using MML Commands via Telnet........................................... 4-1

4.1 Logging in to the Server via Telnet....................................................................... 4-1
4.2 Running MML Commands via Telnet ................................................................... 4-2
Appendix A Introduction to Man-Machine Language ............................ A-1

Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
I
II
About This Manual
The NetNumen M31 Mobile Network Element Management System (hereinafter called
NetNumen M31 or EMS for short) is a network management system for managing mobile
network elements. It is an intermediate system between the upper-layer operation support
system and lower-layer network element management systems. By using NetNumen M31,
you may perform the integrated and centralised management operations on the network
elements, including:
l Configuration management
l Fault management
l Performance management
l Security management
l Log management
l Report management
NetNumen M31 uses object-oriented technologies. It is designed on the advanced J2EE
platform, providing unified standard interfaces to external devices.
Purpose
This operation guide provides the instructions on using the MML terminal provided by
NetNumen M31.
Intended Audience
l Operation and Maintenance Engineers
l Network Monitoring Engineers
What Is in This Manual
Chapter Summary
Chapter 1, Overview Introduces the function of the MML terminal and MML commands,
describes the graphic user interface of the MML terminal on the
NetNumen M31 client, and provides the instruction on how to set the
preferences for the MML terminal.
Chapter 2, Using the MML Provides the instructions on using single commands on the MML
Terminal terminal interface, and describes the operations on the command
results, history commands.
Chapter 3, Batch File Provides the instructions on the batch file operations in the MML
Operations terminal view, such as import, modify, save and delete a batch file.
I
Chapter Summary
Chapter 4, Using MML Describes how to log in to the NetNumen M31 server from a PC
Commands via Telnet terminal via Telnet and how to use MML commands via Telnet.
Appendix A Introduction to Gives an introduction to MML, including common MML terms and the
Man-Machine Language implementation of MML functions in the NetNumen M31 system.
Conventions
ZTE documents employ the following typographical conventions.
Typeface Meaning
Italics References to other manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input fields, option button names, check
boxes, drop-down lists, dialogue box names, window names.
CAPS Keys on the keyboard and buttons on screens and company name.
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be checked before

proceeding further.
Tip: Indicates a suggestion or hint to make things easier or more productive

for the reader.
II
Chapter 1
Overview
Table of Contents
MML Terminal Overview .............................................................................................1-1
GUI of the MML Terminal............................................................................................1-2
Setting Preferences....................................................................................................1-3
Implicit Prerequisites ..................................................................................................1-5
1.1 MML Terminal Overview

MML Terminal
NetNumen M31 provides the Man-Machine Language (MML) terminal as a command
line tool. The MML terminal supports various commands for fault management, security
management, and configuration management operations. You can manage the objects
involved in the network Element Management System (EMS) by running single commands
or batch commands in the MML terminal.
The NetNumen M31 client provides a Graphic User Interface (GUI) for the MML terminal,
on which you can use MML commands in an intuitive way. You can also telnet to the MML
terminal via a remote computer and use MML commands directly to perform operations
on managed objects.
MML Command Introduction

An MML command always starts with a command code and ends with “;”. The command
code determines the function of the command. When a command code is not enough to
involve the complete operation information, the parameter part is generally added to the
command code for explication.
The parameter part, using “:” as the start symbol, contains one parameter, or multiple
parameters separated by “,”. The value of each parameter is bracketed by double
quotation marks.
The following gives an example of MML command:
ADD USER: NAME= "study", FULLNAME= "student", DESCRIPTION= "1", PHONENUMB

ER= "5555555", EMAILADDRESS= "jiandan@111.com", DEPARTMENT= "Maintenance",
USERVALIDDAYS= 50, PASSWORDVALIDDAYS= 50, DISABLE= TRUE;
The previous command is used to add a new user with the user name “study” and full
name “student”. The telephone number of the user is “5555555” and the Email address is
1-1
SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

NetNumen M31(RAN) MML Terminal Operation Guide
“jiandan@111.com”. This user belongs to the maintenance department. And the user 's
validity period is 50 days. The password validity period is also 50 days.
Note:
MML commands vary with the actual equipment managed by the EMS. Therefore,
this operation guide only gives the instruction of using the MML terminal. For more
explanations of MML commands, please refer to MML command reference manual of
related equipment.
1.2 GUI of the MML Terminal

To open the MML terminal interface on the NetNumen M31 client, log in to the client first,
and then do one of the following:
l Click Configuration > MML Terminal on the menu bar.
l Click on the toolbar.
Figure 1-1 shows the MML terminal interface on the client.
Figure 1-1 MML Terminal Interface
1. NE tree 3. Command parameter pane 5. MML tree

2. Command processing pane 4. Command input pane
The following explains some components on the MML terminal interface.

l NE tree: lists all network elements managed by the EMS.
1-2

Chapter 1 Overview
l MML-Tree: lists all available MML commands of the selected NE.

l Command Processing: This pane consists of the following four tabs:
à Command Result tab: shows the running result of MML commands.
à History Command tab: lists all the history commands that you have run on the
MML terminal interface, including the running time, result and command name.
à Upload Message tab: shows the running result of some commands that need
long time for completion, which may not be displayed on the Command Result
tab.
à Help tab: shows the help information of an MML command, such as command
format, input parameters, output parameters, enumerable parameters, and
command examples.
l Batch Processing: In this pane, you can import a batch file, run the batch commands
in the imported file, view the running result of the commands, save the running result,
and delete the imported batch file.
l Code drop-down box: shows the current command selected on the MML-Tree and
lists all previous commands that you have run.
l : click to show the previous command listed in the Code drop-down box.
l : Click to show the next command listed in the Code drop-down box.
l : click to run the current command.
l : This button is available only when you run a batch command on the
command processing pane. Generally, a batch command needs a long time for
completion because it concerns a mass of data. It may occupy the Command Result
tab for a long time to show the command result and you can not do other operations
on the interface during the running of the batch command. In this case, you can click
this button to suspend the batch command after getting the information you want
before the completion of this command.
1.3 Setting Preferences

Prerequisites
l You have successfully logged in to the NetNumen M31 client.
l The MML Terminal interface is open.
Context
The purpose of preferences setting is to determine the processing mode of history
commands, command results, messages and batch command results when their counts
exceed a certain limit, for example, deleting them directly, or saving and then deleting
them. After the setting of preferences, the related records will be automatically deleted,
or saved and deleted, when the records are more than the preset number.
To set the preferences, perform the following steps:
1-3

Steps
1. On the menu bar of the client window, click Configuration > Preferences to open the
Preferences dialogue box, as shown in Figure 1-2.
Figure 1-2 Preferences dialogue box
2. Set the preferences according to Table 1-1.
Table 1-1 Value Range for Preference Setting
Record Type Value Range Default Saving Path
/ums-client/works/full/runtime/ppus/
History Command 1 to 100
uca.ppu/uca-mml.pmu/log/History
/ums-client/works/full/runtime/ppus
Command Result 1 to 100 /uca.ppu/uca-mml.pmu/log/ExecuteRe
sult
/ums-client/works/full/runtime/ppus
Message Report 1 to 100 /uca.ppu/uca-mml.pmu/log/MessageRe
port
/ums-client/works/full/runtime/ppus/
Batch Command Result 1 to 100
uca.ppu/uca-mml.pmu/log/BatchResult
• All the default folders, where the records are saved, are under the installation directory of the
client software, which corresponds to the setting during the installation process.
a. Type the upper limit of record number in the box after “beyond”.
1-4

Chapter 1 Overview
b. If you want to save the records of command results before deleting them, select
the Automatic Save check box.
c. If you want to save the records of command results under another path instead of
the default one, click Browse to select a new path in the pop-up Save dialogue
box.
d. If you want to save the records of command results by NE, select Automatic Save
By NE. Or else, select Automatic Save Not By NE.
3. Click OK to complete the setting of preferences and close the Preferences dialogue
box.
– End of Steps –
1.4 Implicit Prerequisites

For all the operations described subsequent to this section, the following prerequisites are
presumed to have been met.
l You have successfully logged in to the NetNumen M31 client.
l The MML Terminal view is open.
l The connection between the managed NE and the NetNumen M31 server is normal.
1-5

This page intentionally left blank.
1-6

Chapter 2
Using the MML Terminal
Table of Contents
Running a Command on the MML Tree ......................................................................2-1
Running a Command by Manual Input........................................................................2-3
Searching for an MML Command ...............................................................................2-4
Getting the Help of an MML Command.......................................................................2-5
Querying History Commands......................................................................................2-6
Viewing Uploaded Messages .....................................................................................2-7
Operations on Command Results...............................................................................2-8
Operations on History Commands............................................................................2-10
2.1 Running a Command on the MML Tree

Context
The MML-Tree pane on the MML Terminal view provides all available MML commands for
each managed object in the system. You can select a command on MML-Tree and issue
the command to the corresponding NE. The NE will then carry out the operation required
by the command and return the result.
To select and run a command on the MML tree, perform the following steps:
Steps
1. Click an NE node on the NE tree. The MML-Tree refreshes itself automatically and
shows all available MML commands corresponding to the type of the selected NE, as
shown in Figure 2-1.
2-1

Figure 2-1 Selecting an NE
Tip:
If you want to issue a command to multiple NEs of the same type, press and hold
CTRL, and then click these NEs one by one on the NE tree.
2. Expand MML-Tree and then click the MML command you want to run.
The selected MML command appears in the Code drop-down box, and the parameter
display area shows the input parameters of the command that you need to set, as
Figure 2-2 Selecting an MML Command
3. Set the input parameter(s).
2-2

Chapter 2 Using the MML Terminal
4. Click the Execute button.

Result
The Command Result tab on the Command Process pane shows the command result,
as shown in Figure 2-3.
Figure 2-3 Showing the Command Result
2.2 Running a Command by Manual Input

Prerequisites
l You have selected the managed NE to which the command will be issued.
To select a managed NE, you can click the corresponding NE node on the NE tree
directly, or use the SET AMO command.
Context
NetNumen M31 also supports the manual input of MML commands. You can enter an
MML command on the command input pane in the MML Terminal view to issue the input
command to the corresponding NE.
2-3

Note:
MML commands vary with the NE types managed by the EMS. The previous section
“MML Terminal Overview” gives a brief explanation of MML commands. For more
explanation of MML commands, please refer to the MML command reference manual of
related equipment.
To run an MML command by manual input, perform the following steps:
Steps
1. Type an MML command in the command input pane, as shown in Figure 2-4.
Figure 2-4 Typing an MML Command
2. Click Execute to run the command.

Result
The Command Result tab on the Command Processing pane shows the command
result.
2.3 Searching for an MML Command

Context
To search for an MML command of an NE, “CLEAR ALARM”, for example, perform the
following steps:
2-4

Steps
1. Click an NE node on the NE tree. The MML-Tree refreshes itself automatically to show
all available MML commands corresponding to the type of the selected NE.
2. Type a keyword (“ALARM”, for example) of the command to be found in the Input
search text box, and then click .
Result
The MML-Tree changes accordingly and shows all the commands containing the keyword
“ALARM”. The command “CLEAR ALARM” is the first command in the search result, as
Figure 2-5 Search Result
2.4 Getting the Help of an MML Command

Context
The Help tab on the command processing pane of the MML Terminal view provides the
help information of some MML commands, such as command function, input parameters,
output parameters, and command examples.
To view the help information of an MML command, perform the following steps:
Steps
1. Click an NE node on the NE tree. The MML-Tree refreshes itself automatically to show
all available MML commands corresponding to the type of the selected NE.
2. Expand MML-Tree and then click the MML command you want to view.
3. Click the Help tab on the Command Processing pane.

2-5

Result
The help information of the selected command appears in the Help tab, as shown in Figure
2-6.
Figure 2-6 Getting the Command Help
2.5 Querying History Commands

Context
To query the history commands that you have run in the MML Terminal view, do the
following:
Steps
l Click the History Command tab on the Command Processing pane.
Result
The History Command tab on the Command Processing pane lists the records of all
history commands that you have run in the MML Terminal view, as shown in Figure 2-7.
2-6

Figure 2-7 History Command
2.6 Viewing Uploaded Messages

Context
If an MML command takes a long time for completion and its result can not be displayed in
real-time on the Command Result tab, you can view the command result on the Upload
Message tab because the command result can be uploaded in the format of message via
broadcast interface at request.
Take the SHOW DB RATIO command for example. The following describes how to view
the command result on the Upload Message tab.
Steps
1. Click the EMS server node on the NE tree.
2. Type the SHOW DB RATIO command in the command input area and then click
, as shown in Figure 2-8.
The Command Result tab prompts you to view the command result on the Upload
Message tab.
2-7

Figure 2-8 Command Result
3. Click the Upload Message tab and you can view the command result, as shown in
Figure 2-9.
Figure 2-9 Upload Message Tab
2.7 Operations on Command Results

2.7.1 Clearing the Command Results
Context
To clear the command results displayed on the Command Result tab on the command
processing pane, do the following:
2-8

Steps
l Right-click any place on the Command Result tab, and then click Clear on the shortcut
menu.
Result
The command results displayed on the Command Result tab are cleared.
2.7.2 Saving the Command Results

Context
The command results displayed on the Command Result tab on the command processing
pane can be saved as local text file(s).
NetNumen M31 supports the following two saving modes:
l Save all the command results in one text file
l Save the results of commands running in the same NE in a text file, that is, the
command results of different NEs are saved separately in multiple text files.
To save the command results in a text file, perform the following steps:
Steps
1. Right-click any place on the Command Result tab, and then click Save on the shortcut
menu to open the Save dialogue box.
Tip:
To save the command results by NE, click Save by NE Type instead on the shortcut
menu.
2. In the pop-up Save dialogue box, select the saving path, type the file name, and then
click Save.
3. Click OK in the pop-up Confirm dialogue box that prompts successful saving.
2-9

2.8 Operations on History Commands

2.8.1 Saving History Commands
Context
You can save the record of one history command or all history commands displayed on
the History Command tab on the command processing pane.
To save one history command record, perform the following steps:
Steps
1. Click the History Command tab on the Command Processing pane.
2. Right—click the history command record to be saved on the History Command tab,
and then click Save on the shortcut menu.
Tip:
To save all the records of the history commands, click Save All instead on the shortcut
menu.
3. In the Save dialogue box, select the saving path, type the file name, and then click
Save.
2.8.2 Deleting History Commands

Context
You can delete one history command record or all history commands displayed on the
History Command tab on the Command Processing pane.
To delete a history command record, perform the following steps:
Steps
1. Click the History Command tab on the Command Processing pane to show all the
records of history commands.
2. Right-click the history command record to be deleted on the History Command tab,
and then click Delete on the shortcut menu.
2-10

Tip:
To delete all history command records, click Clear instead on the shortcut menu.
Result
The selected history command record disappears from the History Command tab.
2-11

2-12

Chapter 3
Batch File Operations
Table of Contents
Importing a Batch File ................................................................................................3-1
Running the Commands of a Batch File .....................................................................3-2
Saving a Batch File ....................................................................................................3-3
Clearing the Running Result of a Batch File ...............................................................3-3
Clearing the Imported Batch File Contents .................................................................3-4
3.1 Importing a Batch File

Prerequisites
l You have prepared the batch file to be imported.
Context
A batch file is a text file containing a series of commands. The system can run the batch
file to execute all commands in the file.
To import a batch file into the system, perform the following steps:
Steps
1. Click the Batch Processing tab on the MML Terminal interface, as shown in Figure
3-1.
Figure 3-1 Batch Processing Tab
3-1

2. Click on the toolbar to open the Select File dialogue box.

3. In the Select File dialogue box, select the batch file, and then click Open.
Result
The content in the selected batch file is displayed on the Batch Processing tab, as shown
in Figure 3-2.
Figure 3-2 Imported Batch File
Tip:
You can modify the contents of the imported file directly on the Batch Processing tab.
3.2 Running the Commands of a Batch File

Prerequisites
l The batch file has been imported into the MML terminal.
3-2

Chapter 3 Batch File Operations
Context
A single command only defines one operation. To make an NE complete multiple
maintenance operations continuously, you can edit a batch file and import it to the MML
terminal. When the batch file is run, the MML terminal reads the batch file and executes
the imported commands line by line.
Steps
l Click on the batch toolbar to run the imported batch file.
Result
The running result appears in the Result area. The error messages are also listed if there
are any.
3.3 Saving a Batch File

Prerequisites
Context
After importing a batch file, you can modify the content of the file as needed on the Batch
Processing pane and then save the modification.
To edit and save an imported batch file, perform the following steps:
Steps
1. Modify the contents in the batch file as needed in the Batch Processing pane.
2. Click on the toolbar.
3.4 Clearing the Running Result of a Batch File

Prerequisites
l You have run a batch file.
Context
To clear the running result of a batch file displayed in the Result area, do the following:
3-3

Steps
2. In the pop-up Confirm dialogue box, click OK.
Result
The running result disappears from the Result area on the MML terminal interface.
Tip:
Before clearing the running result of a batch file, you can save them first by using the
corresponding buttons. is used to save all running result, while is used to save the
result by NE type.
3.5 Clearing the Imported Batch File Contents

Prerequisites
Context
To clear the imported contents of a batch file displayed on the Batch Processing pane
and remove the batch file from the MML terminal, do the following:
Steps
2. In the pop-up Confirm dialogue box, click OK.
Result
The Batch Processing pane is cleared and the corresponding batch file is deleted from
the MML terminal.
3-4

Chapter 4
Using MML Commands via
Telnet
Table of Contents
Logging in to the Server via Telnet..............................................................................4-1
Running MML Commands via Telnet ..........................................................................4-2
4.1 Logging in to the Server via Telnet

Prerequisites
l The NetNumen M31 server has been started.
l The local PC terminal runs properly, on which a Windows operating system is installed.
Context
To log in to the NetNumen M31 server via Telnet on the local PC terminal, perform the
following steps:
Steps
1. On the local PC, click Start > Run to open the Run dialogue box.
2. Type cmd in the Run dialogue box, and click OK.
3. In the pop-up DOS command window, type telnet IP address of the server 21123, and
press ENTER.
“21123” is the Telnet port number of the NetNumen M31 server. Suppose the
IP address of the server is 10.63.138.35. To telnet to the server, type telnet
10.63.138.35 21123.
4. Type the user name, press ENTER, and then type the password, press ENTER again
to log in to the NetNumen M31 server.
Result
The prompt $> appears in the DOS command window after successful login.
4-1

*****************************************************
NetNumen(TM) Unified Management System Terminal
ums [NetNumen M31 V12.10.032e]
*****************************************************
LOGIN
username:admin
password:
$>
4.2 Running MML Commands via Telnet

Prerequisites
l The NetNumen M31 server runs properly.
l The connection between the local PC terminal and the server is normal.
l You have logged in to the server via Telnet.
Context
After successful login to the NetNumen M31 server via Telnet, you can issue MML
commands to an NE managed by NetNumen M31 to carry out necessary operations.
Note:
MML commands vary with the type of NEs managed by NetNumen M31. The previous
section “MML Terminal Overview” gives a brief explanation of MML commands. For more
explanations of MML commands, please refer to the MML command reference manual of
related equipment.
The following gives an example of how to connect to an NE and issue commands to the
NE via Telnet.
Steps
1. After the prompt $> in the command window, type the SET AMO: NE NAME= ;
command and press ENTER to connect to the corresponding NE.
Note:
“NE NAME” is the name of an NE displayed on the NetNumen M31 client, which is
defined during the creation of the corresponding NE agent.
4-2

Chapter 4 Using MML Commands via Telnet
For example, suppose the “NE NAME” is “10.61.90.159”, enter the command as
follows:
*****************************************************
NetNumen(TM) Unified Management System Terminal
ums [1.10.30]
*****************************************************
LOGIN
username:admin
password:
$>SET AMO:10.61.90.159
$10.61.90.159>
Where, $10.61.90.159> indicates that the local PC is successfully connected to the

NE (10.61.90.159) via Telnet.
2. Type an MML command and press ENTER to issue this command to the NE, which
executes the received command and returns the command result to the local terminal.
For example, to show all users of the NE, type the SHOW ALLUSER command in the
command window. The NE returns the command result as follows.
$10.61.90.159>SHOW ALLUSER
No. |Name |Description |Disable
---------------------------------------------------------------------
1 admin Administrator has all rights of this system. FALSE
---------------------------------------------------------------------
Rows: 1
$10.61.90.159>
Note:
You are recommended to use the NetNumen M31 client for the commissioning and
maintenance of the NetNumen M31 system. If you want to use the MML terminal
for the commissioning, configuration, and maintenance of NEs via Telnet, refer to
related MML command manuals of the corresponding equipment types for detailed
instructions on MML commands.
4-3

4-4

Appendix A
Introduction to Man-Machine
Language
The NetNumen M31 system supports the use of a Man-Machine Language (MML) that
is defined to standardize the interfaces for managing telecommunications devices from a
console. You can get access to a device in the managed network via a super terminal or
TELNET utility, and then use MML commands to manage the device. The use of MML
facilitates the commissioning and maintenance of telecommunications devices due to its
convenience, flexibility and easy-use features.
MML Terminology
The following table explains common terms related to MML.
Term Explanation
MML command MML command is a data format specified by ITU-T for data transfer between
a terminal and a network management system. It is the complete specification
of a function that the system is required to perform.
The common attributes of an MML command include: command code,
mnemonic symbol, command name, and one or more parameters.
Mnemonic symbol A mnemonic symbol is a character string used for the memory of an MML
command, for example, “ADD_SHELF”. It usually indicates the meaning of
the MML command.
Character set The character set is a definite set of different characters specified in CCITT
Z.314, that is, a sub-set of the CCITT International Alphabet No. 5. The
character set contains three types of characters: letter, digit, and special
character.
Downlink MML Downlink MML commands are command data issued by a user from a
command terminal to the network management system.
Uplink MML Uplink MML commands are data responded or reported by the network
command management system.
A-1

Term Explanation
Command code A command must provide a complete specification of a function that the
system is required to perform. It comprises a command code followed
generally by one or more parameter blocks. A command code in the EMS is
an identifier containing four letters.
l The first letter defines the functional area (or sub-area) which this
command belongs to. It is regarded as level-1 code.
l The second and third letters define the object class that the command
will effect or influence. They are regarded as level-2 codes.
l The fourth letter defines the action that the system shall perform. It is
regarded as level-3 code.
Parameter A parameter is data that identifies and contains pieces of information

necessary to execute a command. It consists of one or multiple parameter
blocks separated with a delimiter (:). A parameter contains two parts:
parameter name and parameter value.
l Parameter Name: An identifier which indicates unambiguously the
meaning and structure of the subsequent parameter value.
l Parameter Value: The part of a parameter that contains the information
required to specify any appropriate object(s) or value(s).
Parameter block A parameter block is a set of parameters containing information necessary

for the system to perform the function specified in the command. Multiple
parameters in a parameter block are separated by a comma (,).
Simple parameter A simple parameter refers to a parameter whose value contains only one
information unit.
Compound A compound parameter refers to a parameter whose value contains more than
parameter one information unit. It is used to specify a multidimensional object or value.
Different information units are separated by a hyphen (-) in a logical order.
The positions of these information units cannot be changed. The information
units of digit type are generally placed at the end.
An example of compound parameter is: add user: userinfo = testuser-xxx;
Multiple instances A parameter may contain more than one parameter value, that is, a set of
parameter values separated with &. There is no logical relation among these
parameter values. The parameter values must be of the same type, that is,
simple, or compound. In other words, a parameter value may have multiple
instances.
For example, add user: userinfo= testuser1-xxx&testuser2-xxx;
Parameter type Parameter type determines the conversion method and storage mode of
parameter values. Common parameter types include: Boolean, integer, float,
enumeration, date&time, duration, address, and character string.
A-2

Appendix A Introduction to Man-Machine Language
Term Explanation
Reserved identifier Some identifiers are reserved because they are used by system commands,
system parameters, or common parameters in the system. These reserved
identifiers cannot be used in the definition of command codes and parameter
names. For example, commit, Rollback, begin, end, and ack are all reserved
identifiers.
Implementation of MML Functions in the EMS

The client and server of the NetNumen M31 system cooperate with each other to
implement the MML functions, as illustrated in Figure A-1.
Figure A-1 Implementation of MML Functions
l WSF: WorkStation Function

l MML: Man-Machine Language
l GUI: Graphic User Interface
l EMS: Element Management System
l CLIS: Command Line Interface Server
l NE: Network Element
The following describes how the MML functions are implements on the client and the server
of the NetNumen M31 system.
l MML functions supported by the client
The client supports the access to the server via a command line terminal, which is
an embedded operation interface similar to DOS. The operation requests are input as
command lines in the terminal and then sent to the server in the format of command
messages.
l MML functions supported by the server
A-3

The server allows the access of different clients, implements the logic processing
of received requests, manages the database, and interacts with managed network
elements.
As shown in Figure A-1, the F interface module and the CLIS module work together
to support the access of clients.
à The F interface module forwards received operation requests to corresponding
modules according to the command codes of these requests. The command code
of an operation request varies with the actual module that shall do this operation.
à The CLIS module receives the commands sent by the MML terminal or the GUI,
verifies the validity of these commands, and then processes these commands
according to their types. The received commands can be classified into the
following three types:
t Data configuration commands: The CLIS module encapsulates such
commands in a unified format and then sends them to the internal logic
processing module for further processing.
t Alarm and performance commands: The CLIS module encapsulates such
commands into F interface messages and then sends them to the F interface
module for further processing.
t System commands: The CLIS module forwards such commands to the NE
system directly.
à The internal logic processing module implements the following processes:
t Security processing: This module authenticates the received operation
requests, and records these operations in logs.
t Data processing: This module can modify the topology information of the
system according to the received commands, and store the requested data
in the database of the system.
t Communicating with NEs: This module directly forwards the real-time
commands (for example, a command for querying alarms, or an online
configuration command) to the NE system, and sends non-real-time
commands (for example, an offline configuration command) to the NE
system after processing them.
t Responding on requests: This module can respond to some requests directly

(for example, a single offline configuration command without synchronization
requirement), or forward the response of the NE system to the EMS.
A-4

Figures
Figure 1-1 MML Terminal Interface ........................................................................... 1-2
Figure 1-2 Preferences dialogue box ........................................................................ 1-4
Figure 2-1 Selecting an NE ....................................................................................... 2-2
Figure 2-2 Selecting an MML Command ................................................................... 2-2
Figure 2-3 Showing the Command Result................................................................. 2-3
Figure 2-4 Typing an MML Command ....................................................................... 2-4
Figure 2-5 Search Result .......................................................................................... 2-5
Figure 2-6 Getting the Command Help...................................................................... 2-6
Figure 2-7 History Command .................................................................................... 2-7
Figure 2-8 Command Result ..................................................................................... 2-8
Figure 2-9 Upload Message Tab ............................................................................... 2-8
Figure 3-1 Batch Processing Tab .............................................................................. 3-1
Figure 3-2 Imported Batch File.................................................................................. 3-2
Figure A-1 Implementation of MML Functions ...........................................................A-3
I
Figures

Tables
Table 1-1 Value Range for Preference Setting........................................................... 1-4
III
Tables

Glossary
CLIS
- Command Line Interface Server
DOS
- Disk Operating System
EMS
- Network Element Management System
GUI
- Graphical User Interface
J2EE
- JAVA 2 platform Enterprise Edition
MML
- Man Machine Language
NE
- Network Element

SJ-20101227165724-011-NetNumen M31 (RAN) (V12.10.032) MML Terminal Operation Guide PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SJ-20101227165724-011-NetNumen M31 (RAN) (V12.10.032) MML Terminal Operation Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

NetNumen M31(RAN)

Mobile Network Element Management System

Revision No. Revision Date Revision Reason

R1.0 2011-02-28 First Edition

R1.1 2011-04-25 This revision provides an introduction to man-machine language

Serial Number: SJ-20101227165724-011

Publishing Date: 2011-04-25(R1.1)

Chapter 2 Using the MML Terminal........................................................... 2-1

Chapter 3 Batch File Operations............................................................... 3-1

Chapter 4 Using MML Commands via Telnet........................................... 4-1

Appendix A Introduction to Man-Machine Language ............................ A-1

What Is in This Manual

Italics References to other manuals and documents.

“Quotes” Links on screens.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before

Tip: Indicates a suggestion or hint to make things easier or more productive

1.1 MML Terminal Overview

MML Command Introduction

The following gives an example of MML command:

ADD USER: NAME= "study", FULLNAME= "student", DESCRIPTION= "1", PHONENUMB

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

1.2 GUI of the MML Terminal

Figure 1-1 MML Terminal Interface

1. NE tree 3. Command parameter pane 5. MML tree

The following explains some components on the MML terminal interface.

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

l MML-Tree: lists all available MML commands of the selected NE.

1.3 Setting Preferences

To set the preferences, perform the following steps:

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

Figure 1-2 Preferences dialogue box

2. Set the preferences according to Table 1-1.

Table 1-1 Value Range for Preference Setting

Record Type Value Range Default Saving Path

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

1.4 Implicit Prerequisites

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

2.1 Running a Command on the MML Tree

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

Figure 2-1 Selecting an NE

Figure 2-2 Selecting an MML Command

3. Set the input parameter(s).

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

4. Click the Execute button.

Figure 2-3 Showing the Command Result

2.2 Running a Command by Manual Input

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

To run an MML command by manual input, perform the following steps:

Figure 2-4 Typing an MML Command

2. Click Execute to run the command.

2.3 Searching for an MML Command

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

Figure 2-5 Search Result

2.4 Getting the Help of an MML Command

3. Click the Help tab on the Command Processing pane.

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

Figure 2-6 Getting the Command Help

2.5 Querying History Commands

SJ-20101227165724-011|2011-04-25(R1.1) ZTE Proprietary and Confidential

Figure 2-7 History Command