SJ-20140527134054-017-ZXUR 9000 UMTS (V4.13.10.15) MML Command Reference_594423.pdf

ZXUR 9000 UMTS
Radio Network Controller
MML Command Reference
Version: V4.13.10.15
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn

LEGAL INFORMATION
Copyright © 2014 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revison No. Revision Date Revision Reason
R1.0 2014–07–31 First edition
Serial Number: SJ-20140527134054-017
Publishing Date: 2014-07-31 (R1.0)
SJ-20140527134054-017|2014-07-31 (R1.0) ZTE Proprietary and Confidential

Content
About This Manual ......................................................................................... I
Chapter 1 Overview....................................................................................1-1
1.1 Command Format .............................................................................................. 1-1
1.2 Command Compilation ....................................................................................... 1-3
Chapter 2 Command ..................................................................................2-1
2.1 A....................................................................................................................... 2-1
2.1.1 ACTIVE VERSION ................................................................................... 2-1
2.1.2 ADD ALMWOBBLE .................................................................................. 2-3
2.1.3 ADD RUNBATCH PERIODIC POLICY....................................................... 2-4
2.1.4 ADD RUNBATCH TIMING POLICY ........................................................... 2-7
2.1.5 ADD VERSION ...................................................................................... 2-12
2.1.6 APPLY MUTEXRIGHT............................................................................ 2-14
2.1.7 APTDACTIVE VERSION ........................................................................ 2-15
2.1.8 APTDCONFIRM VERSION..................................................................... 2-17
2.1.9 APTDDEACTIVE VERSION.................................................................... 2-19
2.1.10 APTDQUERY ALLPKG......................................................................... 2-21
2.1.11 APTDVALIDATE VERSION ................................................................... 2-22
2.2 B..................................................................................................................... 2-24
2.2.1 BACKUP ............................................................................................... 2-24
2.2.2 BACKUPLOG ........................................................................................ 2-26
2.3 C..................................................................................................................... 2-27
2.3.1 CONFIRM VERSION.............................................................................. 2-27
2.3.2 CREATE................................................................................................ 2-29
2.3.3 CREATE VERSION................................................................................ 2-30
2.4 D..................................................................................................................... 2-32
2.4.1 DEACTIVE VERSION............................................................................. 2-32
2.4.2 DEL ALMWOBBLE................................................................................. 2-34
2.4.3 DELETE ................................................................................................ 2-35
2.4.4 DELETE VERSION ................................................................................ 2-36
2.4.5 DEL POLICY ......................................................................................... 2-38
2.5 E..................................................................................................................... 2-40
2.5.1 EXECUTE POLICY INSTANTLY ............................................................. 2-40
2.6 G..................................................................................................................... 2-41
I

2.6.1 GET BOOT............................................................................................ 2-41
2.6.2 GET CELLSTATUS ................................................................................ 2-43
2.6.3 GETCMDLOG........................................................................................ 2-45
2.6.4 GETCPURATIO ..................................................................................... 2-49
2.6.5 GETDBRATIO........................................................................................ 2-50
2.6.6 GETHDUSAGE...................................................................................... 2-51
2.6.7 GETHDUSAGEBYNAME........................................................................ 2-52
2.6.8 GET INDEPDTBOARD........................................................................... 2-54
2.6.9 GET INDEPDTBOARDLINKSTATE ......................................................... 2-61
2.6.10 GETRAMUSAGE ................................................................................. 2-62
2.6.11 GETSECLOG....................................................................................... 2-64
2.6.12 GET SITEMS ....................................................................................... 2-67
2.6.13 GETSYSLOG....................................................................................... 2-69
2.7 K..................................................................................................................... 2-72
2.7.1 KILL MUTEXRIGHT ............................................................................... 2-72
2.8 M .................................................................................................................... 2-73
2.8.1 MODIFY TRXLICENSE .......................................................................... 2-73
2.8.2 MULTIREQUEST ................................................................................... 2-74
2.9 O..................................................................................................................... 2-75
2.9.1 OMMBACKUP ....................................................................................... 2-75
2.10 Q................................................................................................................... 2-77
2.10.1 QRY ACL4 ALL TABLE......................................................................... 2-77
2.10.2 QRY ACL4 GROUP.............................................................................. 2-79
2.10.3 QRY ACL4 SPECIFIC TABLE ............................................................... 2-81
2.10.4 QRY AH IF EPU................................................................................... 2-83
2.10.5 QRY AH IF RPU................................................................................... 2-85
2.10.6 QRY ALL BLOCK RUP UNIT ................................................................ 2-88
2.10.7 QRY ALL BLOCK SLAVE SUNIT........................................................... 2-89
2.10.8 QRY ALLLINK STATUS ........................................................................ 2-90
2.10.9 QRY ARP PORT .................................................................................. 2-92
2.10.10 QRY ARP PORT CHANNEL ............................................................... 2-95
2.10.11 QRY ARP STATIC .............................................................................. 2-96
2.10.12 QRY ARP SUPERVLAN ..................................................................... 2-98
2.10.13 QRY ASPSTATUS.............................................................................2-100
2.10.14 QRY ASSTATUS ...............................................................................2-102
2.10.15 QRY BATCHASPSTATUS..................................................................2-103
2.10.16 QRY BATCHASSTATUS ....................................................................2-105
II

2.10.17 QRY BFD BRIEF EPU .......................................................................2-106
2.10.18 QRY BFD CHANGOVER PORT EPU .................................................2-109
2.10.19 QRY BFD DAMP RPU ....................................................................... 2-111
2.10.20 QRY BFD DETAIL EPU......................................................................2-112
2.10.21 QRY CEID STATUS...........................................................................2-116
2.10.22 QRY CEID STATUS ALL....................................................................2-118
2.10.23 QRY CEID STATUS BY PATH ............................................................2-125
2.10.24 QRY CPUUSERATE..........................................................................2-126
2.10.25 QRY DISK.........................................................................................2-128
2.10.26 QRY DPISTATUS ..............................................................................2-130
2.10.27 QRY EPU INTERFACE......................................................................2-131
2.10.28 QRY EPU IPD DETAIL.......................................................................2-135
2.10.29 QRY EPU ROUTE.............................................................................2-137
2.10.30 QRY ETHCFM MA.............................................................................2-143
2.10.31 QRY ETHCFM MD ............................................................................2-145
2.10.32 QRY ETHOAM ALLCFG ....................................................................2-147
2.10.33 QRY ETHOAM DISC .........................................................................2-149
2.10.34 QRY ETHOAM LINKMONI .................................................................2-153
2.10.35 QRY ETHOAM STATICS....................................................................2-156
2.10.36 QRY GPSSTATUS.............................................................................2-159
2.10.37 QRY HARDVERINFO ........................................................................2-162
2.10.38 QRY IMAGRP STATUS......................................................................2-165
2.10.39 QRY IMALINK STATE........................................................................2-166
2.10.40 QRY IPPATHSTATUS UMTS..............................................................2-169
2.10.41 QRY LACP COUNTERS....................................................................2-171
2.10.42 QRY LACP INTERNAL ......................................................................2-173
2.10.43 QRY LACP NEIGHBOURS ................................................................2-175
2.10.44 QRY LACP PORTCHNL ....................................................................2-177
2.10.45 QRY MEMORYUSERATE..................................................................2-179
2.10.46 QRY MODULESTATUS .....................................................................2-184
2.10.47 QRY MTP2LINK STATUS ..................................................................2-185
2.10.48 QRY MTP3LINK ERLANG .................................................................2-186
2.10.49 QRY MTP3LINKSETSTATUS.............................................................2-188
2.10.50 QRY NTPTIME..................................................................................2-190
2.10.51 QRY OFFICE ALL STATUS................................................................2-191
2.10.52 QRY OFFICE STATUS.......................................................................2-192
2.10.53 QRY OMCBPATHSTATUS UMTS.......................................................2-194
III

2.10.54 QRY OMPMTP3LINKSTATUS............................................................2-196
2.10.55 QRY PATHBAND...............................................................................2-198
2.10.56 QRY PATHGPBAND..........................................................................2-200
2.10.57 QRY PATH STATUS ..........................................................................2-204
2.10.58 QRY PATH STATUS ALL ...................................................................2-205
2.10.59 QRY POLICYMAP EPU .....................................................................2-207
2.10.60 QRY POLICYMAP RPU.....................................................................2-209
2.10.61 QRY PROCPURATE .........................................................................2-211
2.10.62 QRY PTP ALL INTF CFG...................................................................2-215
2.10.63 QRY PTP ALL PORT STATE..............................................................2-219
2.10.64 QRY PTP GLOBA CFG .....................................................................2-221
2.10.65 QRY PTP ONE INTF CFG .................................................................2-223
2.10.66 QRY PTP ONE PORT STATE ............................................................2-226
2.10.67 QRY PTP ONE UNICAST NEGOTIATION ..........................................2-228
2.10.68 QRY PTP UNICAST NEGO NORMAL PORT ......................................2-232
2.10.69 QRY PTP UNICAST NEGOTIATION...................................................2-234
2.10.70 QRY PVCSTATUS.............................................................................2-237
2.10.71 QRY RPU INTERFACE......................................................................2-239
2.10.72 QRY RPU ROUTE.............................................................................2-245
2.10.73 QRY SAAL LMLINK CFG...................................................................2-252
2.10.74 QRY SAAL LMLINK STATUS .............................................................2-254
2.10.75 QRY SBCXSTATUS...........................................................................2-256
2.10.76 QRY SCTP ALL.................................................................................2-257
2.10.77 QRY SCTP BY ASSOCIATION...........................................................2-258
2.10.78 QRY SCTP BY PORT........................................................................2-262
2.10.79 QRY SLAVESTATUS .........................................................................2-266
2.10.80 QRY SMPMTP3LINKSTATUS ............................................................2-268
2.10.81 QRY SSCOPLINK CFG .....................................................................2-269
2.10.82 QRY SSCOPLINK STATUS................................................................2-272
2.10.83 QRY SSN STATUS............................................................................2-273
2.10.84 QRY SUNITSTATUS..........................................................................2-275
2.10.85 QRY SUPERVLAN IPPORT...............................................................2-277
2.10.86 QRY SUPERVLAN MEMBER.............................................................2-278
2.10.87 QRY TC STATE.................................................................................2-280
2.10.88 QRY TIME ........................................................................................2-282
2.10.89 QRY UNITSTATUS............................................................................2-283
2.10.90 QUERY2...........................................................................................2-285
IV

2.10.91 QUERY.............................................................................................2-286
2.10.92 QUERY ALLPKG...............................................................................2-288
2.10.93 QUERY CELLCHANNEL ...................................................................2-292
2.10.94 QUERY CREATED VERSION ............................................................2-294
2.10.95 QUERY IUBLINK...............................................................................2-298
2.10.96 QUERY RUNNING ............................................................................2-299
2.10.97 QUERY SNAPSHOT .........................................................................2-313
2.10.98 QUERY TRXLICENSE.......................................................................2-315
2.10.99 QUERY UTRANCELLFDD .................................................................2-316
2.10.100 QUERY VERFILE............................................................................2-318
2.11 R ..................................................................................................................2-322
2.11.1 RELEASE MUTEXRIGHT ....................................................................2-322
2.11.2 RESET IUBLINK .................................................................................2-323
2.11.3 RESET UTRANCELLFDD....................................................................2-324
2.11.4 RESTORE ..........................................................................................2-326
2.12 S ..................................................................................................................2-327
2.12.1 SET APS CHANGE.............................................................................2-327
2.12.2 SET ASPACTIVE ................................................................................2-329
2.12.3 SET ASPDEACTIVE............................................................................2-331
2.12.4 SET ASPDOWN..................................................................................2-333
2.12.5 SET ASPUP........................................................................................2-335
2.12.6 SET BLOCKSUNIT..............................................................................2-337
2.12.7 SET BLOCKUNIT................................................................................2-339
2.12.8 SET BOOT .........................................................................................2-340
2.12.9 SET CEIDOPR RESET........................................................................2-342
2.12.10 SET CEID STOP RESET ...................................................................2-344
2.12.11 SET CELLSTATUS ............................................................................2-346
2.12.12 SET CLOCKBASE.............................................................................2-347
2.12.13 SET DISLOOP ALLUNIT....................................................................2-349
2.12.14 SET DYNAASSOC REL IPANDPORT.................................................2-351
2.12.15 SET DYNAASSOC REL MODANDASSOCID......................................2-353
2.12.16 SET FORCECHANGE .......................................................................2-355
2.12.17 SET FORCERESET ..........................................................................2-357
2.12.18 SET INDBP NTPSYN ........................................................................2-359
2.12.19 SET INDEPDTBOARD.......................................................................2-360
2.12.20 SET INHIBIT IMAGROUP ..................................................................2-385
2.12.21 SET INHIBITIMALINK........................................................................2-387
V

2.12.22 SETLOG...........................................................................................2-389
2.12.23 SET LOOP SUNITTS.........................................................................2-391
2.12.24 SET MANUAL BLOCK MODULE........................................................2-393
2.12.25 SET MANUAL UNBLOCK MODULE...................................................2-395
2.12.26 SET MTP3ALLLINK ACTIVATE ..........................................................2-396
2.12.27 SET MTP3ALLLINK DEACTIVATE .....................................................2-398
2.12.28 SET MTP3LINK ACTIVE....................................................................2-399
2.12.29 SET MTP3LINK DEACTIVE ...............................................................2-400
2.12.30 SET MTP3LINK INHIBIT....................................................................2-402
2.12.31 SET MTP3LINK UNINHIBIT ...............................................................2-403
2.12.32 SET NORMALCHANGE ....................................................................2-405
2.12.33 SET NORMALRESET........................................................................2-407
2.12.34 SET NTPSYN ...................................................................................2-408
2.12.35 SET PATHOPR BLOCK .....................................................................2-410
2.12.36 SET PATHOPR UNBLOCK ................................................................2-412
2.12.37 SET POOLIUBLINK...........................................................................2-413
2.12.38 SET PP2S BASE EXCHANGE ...........................................................2-414
2.12.39 SET RUNBATCH PERIODIC POLICY.................................................2-416
2.12.40 SET RUNBATCH TIMING POLICY.....................................................2-419
2.12.41 SET SBCXCHANGE..........................................................................2-424
2.12.42 SET SBCXDATACHECK....................................................................2-424
2.12.43 SET SBCXSYN .................................................................................2-425
2.12.44 SET SCTP ABORT............................................................................2-426
2.12.45 SET SCTP ABORT ALL.....................................................................2-428
2.12.46 SET SCTP ESTABLISH .....................................................................2-429
2.12.47 SET SCTP ESTABLISH ALL ..............................................................2-431
2.12.48 SET SCTP SHUTDOWN....................................................................2-433
2.12.49 SET SCTP SHUTDOWN ALL.............................................................2-434
2.12.50 SET SITEMS.....................................................................................2-436
2.12.51 SET SLAVEOPR ...............................................................................2-438
2.12.52 SET SSNBLOCKOPR........................................................................2-439
2.12.53 SET SSNUNBLOCKOPR...................................................................2-440
2.12.54 SET TIME .........................................................................................2-441
2.12.55 SET UNBLOCKSUNIT.......................................................................2-443
2.12.56 SET UNBLOCKUNIT .........................................................................2-445
2.12.57 SET UNINHIBIT IMAGROUP .............................................................2-446
2.12.58 SET UNINHIBITIMALINK...................................................................2-448
VI

2.12.59 SHOW ALLROLE ..............................................................................2-450
2.12.60 SHOW ALLROLESET........................................................................2-451
2.12.61 SHOW ALLSESSION ........................................................................2-452
2.12.62 SHOW ALLUSER..............................................................................2-454
2.12.63 SHOW ALMWOBBLE........................................................................2-455
2.12.64 SHOW DEPARTMENT ......................................................................2-456
2.12.65 SHOW MO........................................................................................2-457
2.12.66 SHOW MOINFO................................................................................2-459
2.12.67 SHOW NEVERSION .........................................................................2-461
2.12.68 SHOW POLICY.................................................................................2-461
2.12.69 SHOW ROLE ....................................................................................2-464
2.12.70 SHOW ROLESET..............................................................................2-466
2.12.71 SHOW USER....................................................................................2-467
2.12.72 SHW UTRANCELL............................................................................2-469
2.12.73 SYNC ALMWOBBLE .........................................................................2-476
2.13 U..................................................................................................................2-477
2.13.1 UPDATE.............................................................................................2-477
2.14 V ..................................................................................................................2-479
2.14.1 VALIDATE VERSION...........................................................................2-479
2.14.2 VERSION IDECHECK .........................................................................2-481
2.14.3 VERSION MSSYNC ............................................................................2-482
Tables .............................................................................................................. I
Glossary ...................................................................................................... XV
VII

This page intentionally left blank.
VIII

About This Manual
Purpose
This manual explains each MML command with its function, syntax, input and output
parameters of the ZXUR 9000 UMTS.
Intended Audience
l Maintenance engineer
l Debugging engineer
What Is in This Manual
This manual contains the following chapters.
Chapter Description
Chapter 1 Overview Introduces command format and command compilation.
Chapter 2 Command Introduces details of commands.
I

This page intentionally left blank.
II

Chapter 1
Overview
This chapter introduces command format, command parameter type, command compiling
key points, and Network Management MML terminal.
Table of Contents
Command Format ......................................................................................................1-1
Command Compilation...............................................................................................1-3
1.1 Command Format
Command composition format is as follows:
Command prompt: Input Parameter
Command Example:
SET PASSWORD: NAME =<NAME>,[OLDPASSWORD =<OLDPASSWORD>],[PASSWO
RD =<PASSWORD>];
Input parameter include mandatory parameter and optional parameter, where optional
parameters are marked by square brackets. Where, positions of mandatory parameter
and optional parameter can be interchanged.
Command prompt
Command prompt, also named mnemonic, is composed of words with command function
such as SHOW USER, which can be used to inquire the basic information of user.
l Mandatory parameter
Mandatory parameter is the mandatory part of a command, separated from command
prompt by a colon. Mandatory parameter is marked with red asterisk on graphic
interface. Under TELNET mode, the system prompts it in sequence. If a command
has mandatory parameter, user must input the mandatory parameter, to run the
command normally.
l Optional parameter
Optional parameter is an optional input for user. After user inputs command prompt
and mandatory parameter, system automatically fills in default value, and run the
command.
End of command
By default, a command ends with semicolon. Under TELNET mode, if user directly runs
the command without a semicolon, after inputting command prompt and all parameters,
system automatically adds “;” to the command and execute it. For the command under
1-1

ZXUR 9000 UMTS MML Command Reference
Network Management login mode, when the user clicks Execute button or press F5 key,
system automatically adds “;” at the end of the command, and execute it.
Command parameters types:
l Numeric
Numeric parameter can be divided into INTEGER and FLOAT.
There are two types of INTEGER:
à INTEGER number
à Parameter Argument INTEGER.
INTEGER number doesn’t include any separator, but Parameter Argument
INTEGER includes separators &, &&, -, &&- between INTEGER numbers.
There are two types of FLOAT:
à FLOAT number
à Parameter Argument FLOAT.
FLOAT number doesn’t include any separator, but Parameter Argument FLOAT
includes separator ‘&’ between FLOAT numbers.
l BOOLEAN
BOOLEAN value can be T (TRUE) or F (FALSE).
l IDENTIFIER
There are two types of identifier:
à Basic identifier
It includes normal identifier, alphabet and number. Basic identifier starts with an
alphabet. For example: abc123.
à Parameter argument identifier
It includes a separator ‘&’ between two basic identifiers. For example:
abc123&abc123.
l Enumeration
There are two types of Enumerations:
à Normal enumeration
à Parameter argument enumeration
à Normal enumerative items are separated by “,”. Parameter Argument
enumeration includes a separator ‘&’ between normal enumerative items.
l Date
Representation of date: YYYY-MM-DD.
l Time
1-2

Chapter 1 Overview
It includes second level time type (representation of second level time type:
HH-MI-SS) and minute level time type (representation of minute level time type:
HH-MI).
l Temperature
Decimal float number + postfix 'C'.
l Percent
Decimal float number + postfix '%'.
l String
There are two types of strings:
à Normal string
à Parameter argument string
Normal string type is enclosed by double quotation marks. Parameter argument
string includes ‘&’ between normal strings.
l Complex
It is a special parameter type combined by multiple parameter types
1.2 Command Compilation
Table 1-1 describes command compilation.
Table 1-1 - Command Compilation
Item Description Example
Prompt Title of each command DEL CHAN
Command
format
Command input format, where
optional parameters are included in
square brackets.
DEL CHAN:[SUBNETID=<SUBNETID>][,C
ONFSETID=<CONFSETID>][,BSCID=<BSC
ID>][,SITEID=<SITEID>][,BTSID=<BTSID
>][,TRXID=<TRXID>][,TSID=<TSID>];
Input parameter Describes the meaning, value range,
and filling of all parameters, including
mandatory parameters and optional
parameters.
When the Parameter Type of an
input parameter is Enumeration,
the format of its range is A:B, where
A is the field value of the parameter
in the command and B is the value
description.
-
Output
parameter
Describes the normal output
parameters.
-
1-3

Item Description Example
Example Shows examples for the execution of
a command in network administration
system, divided into inputs and
outputs.
DEL CHAN:SUBNETID=1, CONFSETID
=0,BSCID=1,SITEID=1,BTSID=1,TRXID
=1,TSID=0;
Remarks Other information related with a
command.
-
1-4

Chapter 2
Command
Table of Contents
A ................................................................................................................................2-1
B ..............................................................................................................................2-24
C..............................................................................................................................2-27
D..............................................................................................................................2-32
E ..............................................................................................................................2-40
G..............................................................................................................................2-41
K ..............................................................................................................................2-72
M..............................................................................................................................2-73
O..............................................................................................................................2-75
Q..............................................................................................................................2-77
R............................................................................................................................2-322
S ............................................................................................................................2-327
U............................................................................................................................2-477
V ............................................................................................................................2-479
2.1 A
2.1.1 ACTIVE VERSION
Shortcut
ACTIVE VERSION
Function
Distributes the version files in the package from the OMP to all the boards managed by the
OMP. The version files can be distributed regardless of whether the package is activated.
This command can be used before upgrade to distribute the version files to a specified
board to shorten the upgrade duration.
Command
ACTIVE VERSION:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYPE >,PKGI
D=< PKGID >,PKGNAME=< PKGNAME >;
INPUT PARAMETERS
Table 2-1 shows the input parameters of ACTIVE VERSION.
2-1

Table 2-1 ACTIVE VERSION Input Parameters
No Name Notes Type Range Default Option Instance
Count
1 MEID MEID INT 0-4095 85 RE-
QUIRED
1-1
2 BRD-
SERVER-
TYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGB-
S_2
OMP RE-
QUIRED
1-1
3 PKGID PKGID INT -922337203
6854775808-
922337203685
4775807
0 RE-
QUIRED
1-1
4 PKG-
NAME
PKGNAME STR-
ING
0-1000 "--" RE-
QUIRED
1-1
Output Parameters
Table 2-2 shows the output parameters of ACTIVE VERSION.
Table 2-2 ACTIVE VERSION OUTPUT PARAMETERS
No Name Type Notes Instance Count
2 DETAIL STRING DetailInfo 1-1
3 RESPONSE COMPLEX Response 1-1
4 PKGNAME STRING PkgName 1-1
5 FILERESULT STRING FileResult 1-1
Example
The following example shows how to activate the OMP version with the ID as 3775791137
and name a UMTS_V4.13.10.08P01.pkg from subnet 22.
ACTIVE VERSION:MEID= 22 ,BRDSERVERTYPE= OMP ,PKGID= 3775791137 ,PKG
NAME= "UMTS_V4.13.10.08P01.pkg" ;
2-2

Chapter 2 Command
------------- System Command -------------
Result
--------
Successful execution
--------
DetailInfo
------------
No Detail
------------
No. |PkgName |FileResult
----------------------------------------------------------------
1 UMTS_V4.13.10.08P01.pkg version operates successfully
----------------------------------------------------------------
Rows: 1
2.1.2 ADD ALMWOBBLE
Shortcut
ADD ALMWOBBLE
Function
Add a new wobble rule.
Command
ADD ALMWOBBLE:NE=< NE >,ALARMCODE=< ALARMCODE >,WOBBLENUM=<
WOBBLENUM >,WOBBLETTL=< WOBBLETTL >,CHECKTTL=< CHECKTTL >;
INPUT PARAMETERS
Table 2-3 shows the input parameters of ADD ALMWOBBLE.
Table 2-3 ADD ALMWOBBLE Input Parameters
Count
1 NE Ne ID INT 0-65535 - RE-
QUIRED
1-1
2 ALARM-
CODE
Alarm
Code
INT 0-429496
7295
- RE-
QUIRED
1-1
3 WOB-
BLENUM
Wobble
Number
INT 1-50 - RE-
QUIRED
1-1
4 WOB-
BLETTL
Wobble
TTL
INT 60-86400
0
- RE-
QUIRED
1-1
2-3

Count
5 CHECK-
TTL
Check
TTL
INT 10-3600 - RE-
QUIRED
1-1
Output Parameters
Table 2-4 shows the output parameters of ADD ALMWOBBLE.
Table 2-4 ADD ALMWOBBLE OUTPUT PARAMETERS
1 RESULT STRING Result 1-1
Example
ADD ALMWOBBLE:NE= 1 ,ALARMCODE= 2 ,WOBBLENUM= 2 ,WOBBLETTL= 3600
,CHECKTTL= 60 ;
2.1.3 ADD RUNBATCH PERIODIC POLICY
Shortcut
ADD RUNBATCH PERIODIC POLICY
Function
A policy is a procedure that is defined in the network management system. It defines
behavior modes of the network management system in specific conditions. Operators can
use policy management to define behaviors of the network management system. Policy
management specifies the operations that the network management system performs
automatically when a certain condition is satisfied, simplifying management tasks.
A policy contains two parts: policy conditions and policy activities. A policy activity
implementation is triggered by a policy event. Policy activity application is triggered
by loading the policy. When a policy event occurs, policy conditions are checked. If
conditions are satisfied, the activities specified in the policy are performed automatically.
Policy management is applied in the following aspects:
1. Back up data automatically.
2. Export the report periodically.
3. Increase the alarm severity of the alarm if the same alarm state persists over a certain
time.
4. Delete the node from the view of the network management system if the node persists
in the Down state over a certain time.
5. Execute various system operations periodically or at the scheduled time.
6. Others.
2-4

Chapter 2 Command
Based on policy events that trigger a policy, policies fall into two types: periodic policies
and timing policies.
The ADD RUNBATCH PERIODIC POLICY command is used to create a periodic policy.
The policy that is executed periodically is called a periodic policy. Its attributes include
interval and start time. Periodic policy is triggered by timing event and it is executed by
the policy server in the network management system.
Impact on the system: None
Command
ADD RUNBATCH PERIODIC POLICY:POLICYNAME=< POLICYNAME >,POLICYSTA
TUS=< POLICYSTATUS >,STARTTIME=< STARTTIME >,INTERVALTIME=[< DAY >][-<
HOUR >][-< MINUTE >][-< SECOND >],FILENAME=< FILENAME >[,ARGS=< ARGS >];
INPUT PARAMETERS
Table 2-5 shows the input parameters of ADD RUNBATCH PERIODIC POLICY.
Table 2-5 ADD RUNBATCH PERIODIC POLICY Input Parameters
No Name Notes Type Range De-
fault
Option In-
stance
Count
1 POLICY-
NAME
Policy name, the identification
of a policy name.
STR-
ING
0-1000 - REQUI-
RED
1-1
2 POLICYS-
TATUS
Policy status. Two values are
available: active, suspend.
The policy does not take
effect if it is in Suspend
status. The policy takes effect
if it is in active status.
Enu-
m
Sus-
pend:
Sus-
pend
Active:
Active
AC-
TIVE
REQUI-
RED
1-1
3 START-
TIME
The start time of executing a
policy.
DAT-
E
- - REQUI-
RED
1-1
4 DAY Day. INT 0-2999 0 ANY
OP-
TION
1-1
5 HOUR Hour. INT 0-23 0 ANY
OP-
TION
1-1
6 MINUTE Minute. INT 0-59 0 ANY
OP-
TION
1-1
2-5

fault
Option In-
stance
Count
7 SECOND Second. INT 0-59 0 ANY
OP-
TION
1-1
8 INTER-
VALTIME
The end time of executing a
policy.
CO-
M-
PLEX
0-1000 - REQUI-
RED
1-1
9 FILE-
NAME
Script file name (*.txt):
You can specify a file name
which ends in *.txt. By
default, the file is stored in
the directory of the server,
ums-svr/mmlbatchfiles/policy.
2) You can specify the
relative path, such as
runbatch/test.txt. This file is
stored in the path of server 1,
ums-svr/runbatch/test.txt.
If the script file is in the root
directory of the server, the
script file name is: ./test.txt or
.test.txt.
STR-
ING
0-128 - REQUI-
RED
1-1
10 ARGS Filtering conditions to be set
when a policy is created.
STR-
ING
0-1000 - ANY
OP-
TION
1-100
Output Parameters
Table 2-6 shows the output parameters of ADD RUNBATCH PERIODIC POLICY.
Table 2-6 ADD RUNBATCH PERIODIC POLICY OUTPUT PARAMETERS
1 RESULT STRING The execution result is displayed, showing
that the policy is created successfully or the
execution is failed.
1-1000
Example
The following example shows how to create a RUNBATCH PERIODIC POLICY that is
named “aaa”.
ADD RUNBATCH PERIODIC POLICY:POLICYNAME= "aaa" ,POLICYSTATUS= ACTI
VE ,STARTTIME= "2008-810-13 13:48:22" ,INTERVALTIME= "0"-"0"-"8"-"0" ;;
2-6

Chapter 2 Command
Result
------
Creat policy aaa successfully
2.1.4 ADD RUNBATCH TIMING POLICY
Shortcut
ADD RUNBATCH TIMING POLICY
Function
time.
6. Others.
Based on the policy events that trigger a policy, policies fall into two types: periodic policies
The ADD RUNBATCH PERIODIC POLICY command is used to create a timing policy. The
policy that is executed at a scheduled time is called a timing policy. Its attribute includes
the fixed time information. The policy is triggered by timing event and it is executed by
the policy server in the network management system. With this function, operations can
be executed at the scheduled time which is set in the unit of year, month, or week. For
example, the time can be set to “Once a day”. And a certain time is set, such as 20:00,
indicating that the policy is executed at 20:0 every day.
Impact on the system: none.
2-7

Command
ADD RUNBATCH TIMING POLICY:POLICYNAME=< POLICYNAME >,POLICYSTATU
S=< POLICYSTATUS >,ONLYONCE=< ONLYONCE >,FILENAME=< FILENAME >[,AR
GS=< ARGS >];
INPUT PARAMETERS
Table 2-7 shows the input parameters of ADD RUNBATCH TIMING POLICY.
Table 2-7 ADD RUNBATCH TIMING POLICY Input Parameters
fault
Op-
tion
Inst-
ance
Count
1 POL-
ICY-
NAME
Policy name, the identification
of a policy name.
STR-
ING
0-1000 - RE-
QUIR-
ED
1-1
2 POLI-
CYSTA-
TUS
Policy status. Two values are
available: active, suspend.
The policy does not take
effect if it is in Suspend
status. The policy takes
effect if it is in active status.
Enum Suspend:
Suspend
Active:
Active
Active RE-
QUIR-
ED
1-1
3 ONLY-
ONCE
The policy is executed only
once and the execution time
is specified.
DATE - - RE-
QUI-
RED
OP-
TION
1-1
4 ONCE-
DAY
The policy is executed once
a day and the execution time
is specified.
DATE - - RE-
QUI-
RED
OP-
TION
1-1
5 WEEK Week. Enum Sunday:
Sunday
Monday:
Monday
Tuesday:
Tuesday
Wednesday:
Wednesday
Thursday:
Thursday
Mon-
day
RE-
QUIR-
ED
1-1
2-8

Chapter 2 Command
fault
Op-
tion
Inst-
ance
Count
Friday:
Friday
Saturday:
Saturday
6 SHOR-
TTIME1
Time. DATE - - RE-
QUIR-
ED
1-1
7 ONCE-
WEEK
The policy is executed once a
week and the execution time
is specified.
COM-
PLEX
- - RE-
QUI-
RED
OP-
TION
1-1
8 DAY1 Day. Enum 1:1
2:2
3:3
4:4
5:5
6:6
7:7
8:8
9:9
10:10
11:11
12:12
13:13
14:14
15:15
17:17
18:18
19:19
20:20
21:21
22:22
23:23
24:24
25:25
26:26
27:27
28:28
29:29
1 RE-
QUIR-
ED
1-1
2-9

fault
Op-
tion
Inst-
ance
Count
30:30
31:31
32:Last Day
9 SHOR-
TTIME2
Time. DATE - - RE-
QUIR-
ED
1-1
10 ONCE-
MON-
TH
a month and the execution
time is specified.
COM-
PLEX
- - RE-
QUI-
RED
OP-
TION
1-1
11 MONT-
H
Month. Enum 1:1
2:2
3:3
4:4
5:5
6:6
7:7
8:8
9:9
10:10
11:11
12:12
1 RE-
QUIR-
ED
1-1
12 DAY2 Day. Enum 1:1
2:2
3:3
4:4
5:5
6:6
7:7
8:8
9:9
10:10
11:11
12:12
13:13
14:14
15:15
16:16
17:17
1 RE-
QUIR-
ED
1-1
2-10

Chapter 2 Command
fault
Op-
tion
Inst-
ance
Count
18:18
19:19
20:20
21:21
22:22
23:23
24:24
25:25
26:26
27:27
28:28
29:29
30:30
31:31
13 SHOR-
TTIME3
Time. DATE - - RE-
QUIR-
ED
1-1
14 ONCE-
YEAR
a year and the execution time
is specified.
COM-
PLEX
- - RE-
QUI-
RED
OP-
TION
1-1
15 FILE-
NAME
Script file name (*.txt):
You can specify a file name
which ends in *.txt. By
default, the file is stored in
the directory of the server,
ums-svr/mmlbatchfiles/policy.
2) You can specify the
relative path, such as
runbatch/test.txt. This file is
stored in the path of server 1,
ums-svr/runbatch/test.txt.
If the script file is in the root
directory of the server, the
script file name is: ./test.txt or
.test.txt.
STR-
ING
0-128 - RE-
QUIR-
ED
1-1
16 ARGS Filtering conditions to be set
when a policy is created.
STR-
ING
0-1000 - ANY
OP-
TION
1-100
2-11

Output Parameters
Table 2-8 shows the output parameters of ADD RUNBATCH TIMING POLICY.
Table 2-8 ADD RUNBATCH TIMING POLICY OUTPUT PARAMETERS
No Name Type Notes Instance
Count
1 RESULT STRING The execution result is displayed, showing
that the policy is created successfully or the
execution is failed.
1-1000
Example
The following example shows how to create a RUNBATCH TIMING POLICY that is named
“aaa”.
ADD RUNBATCH TIMING POLICY:POLICYNAME= "aaa" ,POLICYSTATUS= Active ,O
NLYONCETIME= "2008-10-13 16:07:22" ,FILENAME= "test.txt" ,ARGS= "1"&"2" ;;
Result
------
Creat policy aaa successfully
------
2.1.5 ADD VERSION
Shortcut
ADD VERSION
Function
This command executes the following operations:
1. Download an installation package from the FTP/SFTP server and install the package
to the board.
2. Write the package information to the package information table.
3. Write the version file attribute information to the full table.
The FTP/SFTP service must be enabled before using this command, and the installation
package must be located in the specified directory. This command is used for version
upgrade.
Command
ADD VERSION:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYPE >,PKGID=<
PKGID >,PKGNAME=< PKGNAME >;
INPUT PARAMETERS
Table 2-9 shows the input parameters of ADD VERSION.
2-12

Chapter 2 Command
Table 2-9 ADD VERSION Input Parameters
Count
QUIRED
1-1
2 BRD-
SERVER-
TYPE
Board
Server
Type
Enu-
m
OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGB-
S_2
OMP RE-
QUIRED
1-1
3 PKGID Package
ID
INT -922337203
6854775808-
9223372036854
775807
0 RE-
QUIRED
1-1
4 PKG-
NAME
Package
Name
ST-
R-
ING
0-1000 "" RE-
QUIRED
1-1
Output Parameters
Table 2-10 shows the output parameters of ADD VERSION.
Table 2-10 ADD VERSION OUTPUT PARAMETERS
5 OPERESULT Enum 0:Operation Success
1:Operation Failed
1-1
6 DETAILRE-
SULT
STRING DetailResult 1-1
Example
The following example shows how to remotely add an OMP version with the ID as
3641446708 and name a UMTS_V4.13.10.04P01.pkg to subnet 40.
ADD VERSION:MEID= 40 ,BRDSERVERTYPE= OMP ,PKGID= 3641446708 ,PKGNAM
E= "UMTS_V4.13.10.04P01.pkg" ;
2-13

------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
No. |PkgName |OperationResult |DetailResult
-------------------------------------------------------------------------------
1 UMTS_V4.13.10.04P01.pkg Operation Success version operates successfully
-------------------------------------------------------------------------------
Rows: 1
2.1.6 APPLY MUTEXRIGHT
Shortcut
APPLY MUTEXRIGHT
Function
This command applies NE mutex right by the local client terminal. During the routine
maintenance, when multiple client terminals modify configuration data at the same time,
data can be disordered. To avoid this problem, the mutex right of the NE must be applied
before the configuration data is modified. After the command is executed successfully, the
result information of the mutex right application operation (success/failure) is output.
Command
APPLY MUTEXRIGHT:[SUBNET=< SUBNET >][,NE=< NE >];
INPUT PARAMETERS
Table 2-11 shows the input parameters of APPLY MUTEXRIGHT.
Table 2-11 APPLY MUTEXRIGHT Input Parameters
Count
1 SUBNET SubNet-
work ID
STRING 0-214740
0000
- ANY
OPTION
1-1
2 NE NE ID STRING 0-214740
0000
- ANY
OPTION
1-1
2-14

Chapter 2 Command
Output Parameters
Table 2-12 shows the output parameters of APPLY MUTEXRIGHT.
Table 2-12 APPLY MUTEXRIGHT OUTPUT PARAMETERS
Example
The following example shows how to apply the mutex right of subnet 0 NE 0. If the
command is executed successfully, the information about “Succeeded in applying mutex
right” is returned.
APPLY MUTEXRIGHT:SUBNET= "0" ,NE= "0" ;
Result
------------------------------------------------
Succeeded in applying mutex right.
------------------------------------------------
2.1.7 APTDACTIVE VERSION
Shortcut
APTDACTIVE VERSION
Function
Distributes the version files in the package from the OMP to a specified board. The version
files can be distributed regardless of whether the package is activated. This command can
be used before upgrade to distribute the version files to a specified board to shorten the
upgrade duration.
Command
APTDACTIVE VERSION:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYPE
>,PKGID=< PKGID >,PKGNAME=< PKGNAME >,PHYSADDRESS=< PHYSADDRESS
>;
INPUT PARAMETERS
Table 2-13 shows the input parameters of APTDACTIVE VERSION.
Table 2-13 APTDACTIVE VERSION Input Parameters
Count
QUIRED
1-1
2-15

Count
2 BRD-
SERVE-
RTYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGBS_2
OMP RE-
QUIRED
1-1
3 PKGID PKGID INT -9223372036854775
808-9223372036854
775807
0 RE-
QUIRED
1-1
4 PKG-
NAME
PKG-
NAME
STR-
ING
0-1000 "" RE-
QUIRED
1-1
5 PHY-
SAD-
DRESS
PHYSA-
DDRES-
S(rack/s-
helf/slot-
/cpu)
STR-
ING
0-1000 "" RE-
QUIRED
1-20
Output Parameters
Table 2-14 shows the output parameters of APTDACTIVE VERSION.
Table 2-14 APTDACTIVE VERSION OUTPUT PARAMETERS
6 DETAILRESULT STRING DetailResult 1-1
Example
APTDACTIVE VERSION:MEID= 22 ,BRDSERVERTYPE= OMP ,PKGID= 3775791137
,PKGNAME= "UMTS_V4.13.10.08P01.pkg" ,PHYSADDRESS= "1/2/7/1";
2-16

Chapter 2 Command
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
|DetailResult
-------------------------------------------------------------------------------
version operates successfully
-------------------------------------------------------------------------------
Rows: 1
2.1.8 APTDCONFIRM VERSION
Shortcut
APTDCONFIRM VERSION
Function
Confirms that the activated patch package operates on a specified board after board
restart. The corresponding patch package must be activated through the APTDACTIVE
VERSION command before using this command. If you want the patch package activated
through the APTDACTIVE VERSION command to be used after board restart, this
command can be used. It makes the confirmed patch version continue to operate after
the specified board is re-powered on.
Command
APTDCONFIRM VERSION:MEID=< MEID >,PKGID=< PKGID >,PKGNAME=< PKGNA
ME >,PHYSADDRESS=< PHYSADDRESS >;
INPUT PARAMETERS
Table 2-15 shows the input parameters of APTDCONFIRM VERSION.
Table 2-15 APTDCONFIRM VERSION Input Parameters
Count
QUIRED
1-1
2-17

Count
854775808-
922337203685
4775807
0 RE-
QUIRED
1-1
3 PKG-
NAME
PKGNAME STR-
ING
0-1000 "" RE-
QUIRED
1-1
4 PHYSAD-
DRESS
PHYSAD-
DRESS(ra-
ck/shelf/sl-
ot/cpu)
STR-
ING
0-1000 "" RE-
QUIRED
1-20
Output Parameters
Table 2-16 shows the output parameters of APTDCONFIRM VERSION.
Table 2-16 APTDCONFIRM VERSION OUTPUT PARAMETERS
Example
he following example shows how to confirm a version for CPU 1, slot 3, shelf 2, rack 1,
subnet 21 in default mode. In this example, the version package ID is 2697010944 and
the name is RMP_SLAVE_4.12.10.08P31.pkg.
APTDCONFIRM VERSION:MEID= 21 ,PKGID= 2697010944 ,PKGNAME= "RMP_SLAV
E_4.12.10.08P31.pkg" ,PHYSADDRESS= "1/2/3/1" ;
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
-----------------------------------------------------------------
2-18

Chapter 2 Command
1 RMP_SLAVE_4.12.10.08P31.pkg version operation succeeds
-----------------------------------------------------------------
Rows: 1
2.1.9 APTDDEACTIVE VERSION
Shortcut
APTDDEACTIVE VERSION
Function
Deactivates the version package that is activated by using the APTDACTIVE VERSION
command. A maximum of 20 boards can be specified. This command is used if a version
package is not required on a specified board.
Command
APTDDEACTIVE VERSION:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYP
E >,PKGID=< PKGID >,PKGNAME=< PKGNAME >,PHYSADDRESS=< PHYSADDRES
S >;
INPUT PARAMETERS
Table 2-17 shows the input parameters of APTDDEACTIVE VERSION.
Table 2-17 APTDDEACTIVE VERSION Input Parameters
Count
QUIRED
1-1
2 BRDS-
ERVER-
TYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGBS_2
OMP RE-
QUIRED
1-1
3 PKGID PKGID INT -922337203685477
5808-92233720368
54775807
- RE-
QUIRED
1-1
4 PKG-
NAME
PKG-
NAME
STR-
ING
0-1000 "" RE-
QUIRED
1-1
2-19

Count
5 PHY-
SAD-
DRESS
PHYSAD-
DRESS(r-
ack/shelf-
/slot/cpu)
STR-
ING
0-1000 "" RE-
QUIRED
1-20
Output Parameters
Table 2-18 shows the output parameters of APTDDEACTIVE VERSION.
Table 2-18 APTDDEACTIVE VERSION OUTPUT PARAMETERS
Example
The following example shows how to deactivate an specified OMP version package with
the ID as 3641446708 and name as UMTS_V4.13.10.04P01.pkg on the board of CPU 1,
slot 1, shelf 3, rack 1.
APTDDEACTIVE VERSION:MEID= 40 ,BRDSERVERTYPE= OMP ,PKGID= 36414467
08 ,PKGNAME= "UMTS_V4.13.10.04P01.pkg" ,PHYSADDRESS= "1/3/1/1" ;
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
No. |PkgName |FileResult |DetailResult
-------------------------------------------------------------------------------
---------------------
1 UMTS_V4.13.10.04P01.pkg All appointed deactivations failed All appointed
deactivations failed
-------------------------------------------------------------------------------
---------------------
Rows: 1
2-20

Chapter 2 Command
2.1.10 APTDQUERY ALLPKG
Shortcut
APTDQUERY ALLPKG
Function
Queries a specified version package information table. This command displays only the
information about the version package that is activated through the APTDACTIVE VER
SION command. If a board uses an unexpected version, you can use this command to
check whether a specified package is activated.
Command
APTDQUERY ALLPKG:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYPE >;
INPUT PARAMETERS
Table 2-19 shows the input parameters of APTDQUERY ALLPKG.
Table 2-19 APTDQUERY ALLPKG Input Parameters
Count
QUIRED
1-1
2 BRD-
SERVER-
TYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EG-
BS_2
OMP RE-
QUIRED
1-1
Output Parameters
Table 2-20 shows the output parameters of APTDQUERY ALLPKG.
Table 2-20 APTDQUERY ALLPKG OUTPUT PARAMETERS
4 PKGTYPE STRING PkgTye 1-1
5 PKGID STRING PkgId 1-1
6 VERNO STRING VerNo. 1-1
2-21

8 PHYSADDRESS STRING PhysAddress 1-1
9 APTDACTIVETIME STRING AptdActiveTime 1-1
10 ACTIVESTATE Enum 0:Backup
1:Default Active
2:Appointed Active
1-1
11 CONFIRMSTATE Enum 0:UNCONFIRM
1:DFTCONFIRM
2:APTDCONFIRM
255:--
1-1
Example
The following example shows how to query the version information and status of a specified
OMP board in subnet 40.
APTDQUERY ALLPKG:MEID= 40 ,BRDSERVERTYPE= OMP ;
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
No. |PkgTye |PkgId |VerNo. |PkgName |PhysAddress |AptdActiveTime
|ActiveState |ConfirmState
-------------------------------------------------------------------------------
--------------
1 -- -- -- -- -- --
Appointed Active APTDCONFIRM
-------------------------------------------------------------------------------
--------------
Rows: 1
2.1.11 APTDVALIDATE VERSION
Shortcut
APTDVALIDATE VERSION
2-22

Chapter 2 Command
Function
Makes a specified board run the latest activated version after one or more packages are
activated. A maximum of 20 boards can be specified. This command is used for version
upgrade. It may cause board reset and the use of the new version.
Command
APTDVALIDATE VERSION:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYP
E >,PHYSADDRESS=< PHYSADDRESS >,VALIDATEMODE= HOTPATCH ;
INPUT PARAMETERS
Table 2-21 shows the input parameters of APTDVALIDATE VERSION.
Table 2-21 APTDVALIDATE VERSION Input Parameters
Count
QUIRED
1-1
2 BRDS-
ERVER-
TYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGBS_
2
OMP RE-
QUIRED
1-1
3 PHY-
SAD-
DRESS
PHYSAD-
DRESS(r-
ack/shelf-
/slot/cpu)
STR-
ING
0-1000 "--" RE-
QUIRED
1-20
4 VALI-
DATE-
MODE
VALI-
DATE-
MODE
Enum COMMON:COM-
MON
HOTPATC:HOT-
PATCH
AL:ALL
COM-
MON
RE-
QUIRED
1-1
Output Parameters
Table 2-22 shows the output parameters of APTDVALIDATE VERSION.
Table 2-22 APTDVALIDATE VERSION OUTPUT PARAMETERS
2-23

4 PHYADDRESS STRING PhyAddress 1-1
5 BOARDRESULT STRING BoardResult 1-1
Example
APTDVALIDATE VERSION:MEID= 40 ,BRDSERVERTYPE= OMP ,PHYSADDRESS=
"1/3/1/1" ,VALIDATEMODE= COMMON ;
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
No. |PhyAddress |BoardResult
-------------------------------------------------------------------------------
1 -- Version validation command successful.
Starting target boards validation
2 1/3/1/1 version operates successfully
-------------------------------------------------------------------------------
Rows: 2
2.2 B
2.2.1 BACKUP
Shortcut
BACKUP
Function
This command backs up the system configuration data to the storage file. In the routine
maintenance, you can use this command to back up the system configuration data to the
file so that you can use the RESTORE command to recover the backup file in the system
when errors occur in the following configuration maintenance process. After the command
is executed successfully, the system configuration data is backed up to the file, and the
path where the backup result file is stored is output.
2-24

Chapter 2 Command
Command
BACKUP:[POS=[< SUBNET >][-< NE >]][,FILENAME=< FILENAME >][,DESC=< DESC
>];
INPUT PARAMETERS
Table 2-23 shows the input parameters of BACKUP.
Table 2-23 BACKUP Input Parameters
Count
1 POS Position COM-
PLEX
- - ANY
OPTION
1-3000
2 FILE-
NAME
File name STRING 0-100 "Config-
Data"
ANY
OPTION
1-1
3 DESC Descrip-
tion
STRING 0-1000 - ANY
OPTION
1-1
101 SUBNET SubNet-
work ID
STRING 0-214740
0000
- ANY
OPTION
1-1
102 NE NE ID STRING 0-214740
0000
- ANY
OPTION
1-1
Output Parameters
Table 2-24 shows the output parameters of BACKUP.
Table 2-24 BACKUP OUTPUT PARAMETERS
Example
The following example shows how to back up configuration data of subnet 0 and NE 0 to
the file. After the operation is successful, the path where the backup file is stored in the
server is returned.
BACKUP:POS= "0"-"0" , FILENAME= "test" ,DESC="NE 0-0 configuration data, all funct
ion services are normal.";
Result
--------------------------------------------------------------
Successful [2]
File path (Server)
/home/oracle/netnumen/AutoInstall/ums/ums-svr/cmdata/cmbak/test_20121016_152602.zip
--------------------------------------------------------------
2-25

2.2.2 BACKUPLOG
Shortcut
BACKUPLOG
Function
A network management system can have multiple users. To trace each user's operations
performed on the network management system, such as querying, adding, editing,
deleting, or login, the log management system is introduced into the network management
system. With the use of the log management system, each user's operations on the
network management system can be traced. Data tracing helps to restore data if data is
deleted or modified accidentally. In this way, data integrity is protected.
Log management includes operation log, security log, and system log. Operation log takes
the record of basic operations that a user performs on the network management system,
such as creating, deleting, modifying data, and executing MML commands.
To prevent the loss of log management information caused by system crash or other
accidents, the network management system provides the log backup function. The
Backup Log command is used to implement the function.
All logs including operation logs, security logs, and system logs are stored in the ums-sv
rbackupsysmanagerlog directory of the server in .zip format.
Two parameters are optional. One is AUTOBACKUP and the other is MANUALBACKUP.
If AUTOBACKUP is enabled, the system performs log backup once a day automatically.
If MANUALBACKUP is enabled, the system performs log backup based on the set time.
The unit is Day. At least one parameter must be set.
If the command is executed successfully, the returned result is successful. If the command
is executed unsuccessfully, the returned result is failed.
Command
BACKUPLOG:AUTOBACKUP=< AUTOBACKUP >;
Or
BACKUPLOG:MANUALBACKUP=< MANUALBACKUP>;
INPUT PARAMETERS
Table 2-25 shows the input parameters of BACKUPLOG.
2-26

Chapter 2 Command
Table 2-25 BACKUPLOG Input Parameters
No Name Notes Ty-
pe
Range De-
fault
Option Instance
Count
1 AUTO-
BACKUP
The log is backed up
once a day automatically.
En-
um
FALSE:
false
TRUE:
true
- ANY
MulitI-
OPTION
1-1
2 MANUAL-
BACKUP
The logs are backed up
manually.
INT 1-10000 - ANY
MulitI-
OPTION
1-1
Output Parameters
Table 2-26 shows the output parameters of BACKUPLOG.
Table 2-26 BACKUPLOG OUTPUT PARAMETERS
1 RE-
SULT
STR-
ING
The execution result information is displayed. 1-1000
Example
The following example shows how to cancel log backup.
No more backup log
BACKUPLOG:AUTOBACKUP=False;
Result
--------
Cancel auto backup successfully.
--------
Manual backup log
BACKUPLOG:MANUALBACKUP=5;
Result
--------
Manual backup log successfully, the file path is: ./ums-svr/backup/sysmanager/log
--------
2.3 C
2.3.1 CONFIRM VERSION
Shortcut
CONFIRM VERSION
2-27

Function
Confirms that the activated patch packages operate on the boards after board restart. The
corresponding patch package must be activated through the ACTIVE VERSION command
before using this command. If you want the patch package activated by default to be used
after board restart, this command can be used. It makes the confirmed patch version
continue to operate after any board is re-powered on.
Command
CONFIRM VERSION:MEID=< MEID >,PKGID=< PKGID >,PKGNAME=< PKGNAME >;
INPUT PARAMETERS
Table 2-27 shows the input parameters of CONFIRM VERSION.
Table 2-27 CONFIRM VERSION Input Parameters
Count
1 MEID MEID INT 0-4095 85 REQUIRED 1-1
6854775808-
9223372036854
775807
0 REQUIRED 1-1
3 PKG-
NAME
PKG-
NAME
STR-
ING
0-1000 "--" REQUIRED 1-1
Output Parameters
Table 2-28 shows the output parameters of CONFIRM VERSION.
Table 2-28 CONFIRM VERSION OUTPUT PARAMETERS
Example
The following example shows how to confirm the version whose ID is 2697010944 and
name is RMP_SLAVE_4.12.10.08P31.pkg by default for subnet 21.
CONFIRM VERSION:MEID= 21 ,PKGID= 2697010944 ,PKGNAME= "RMP_SLAVE_4.1
2.10.08P31.pkg" ;
2-28

Chapter 2 Command
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
-----------------------------------------------------------------
1 RMP_SLAVE_4.12.10.08P31.pkg version operation succeeds
-----------------------------------------------------------------
Rows: 1
2.3.2 CREATE
Shortcut
CREATE
Function
This command creates configuration data records. This command is used when
configuration data requires to be added in base station commissioning and routine
maintenance. The command structure is complicated. You can obtain the MML command
by using either of the following methods:
1. Create a piece of configuration data in GUI interface, and then click the button with
“M” next to the storage button .
2. In the configuration management and data export, select export in MML format.
After the command is executed successfully, the system adds the corresponding
configuration data. If the command is executed unsuccessfully, the failure cause is
returned.
The added configuration data has no effect on the system before it is synchronized to NEs.
After the added configuration data is synchronized to the NE, configuration data of different
MOCs have different effects on the system. The configuration data of some services may
cause NE restart or cell recreation. You should not synchronize the added configuration
data to the NEs unless absolutely necessary.
Command
CREATE:[MOC=< MOC >][,MOI=< MOI >][,ATTRIBUTES=< ATTRIBUTES >][,EXTEND
S=< EXTENDS >];
2-29

INPUT PARAMETERS
Table 2-29 shows the input parameters of CREATE.
Table 2-29 CREATE Input Parameters
Count
1 MOC MOC STRING 0-100 - ANY
OPTION
1-1
2 MOI MOI STRING 0-214740
0000
- ANY
OPTION
1-1
3 ATTRIBU-
TES
Attributes STRING 0-214740
0000
- ANY
OPTION
1-1
4 EX-
TENDS
Extends
attributes
STRING 0-214740
0000
- ANY
OPTION
1-1
Output Parameters
Table 2-30 shows the output parameters of CREATE.
Table 2-30 CREATE OUTPUT PARAMETERS
Example
The following example shows how to create a subnet whose ID is 2, type is 1, and alias is
test. After the command is executed successfully, the information about creation success
and ID of the created subnet are returned.
CREATE :MOC= "SubNetwork" ,MOI= "SubNetwork=2" ,ATTRIBUTES="SUBNETWOR
KTYPE=1,SubNetwork=2,USERLABEL=Test";
Result
--------------------------------------
Succeeding
in creating.
SubNetwork=2
---------------------------------------
2.3.3 CREATE VERSION
Shortcut
CREATE VERSION
2-30

Chapter 2 Command
Function
Import version from external file system to OMM server and generate information in version
database. This command can be used to create initial version or import version from
external file system. Some board may run initial version after rebooting. Recreate initial
version may change their running version when rebooted.
Command
CREATE VERSION:MEID=< MEID >,CREATETYPE=< CREATETYPE >,FILEPATH=<
FILEPATH >;
INPUT PARAMETERS
Table 2-31 shows the input parameters of CREATE VERSION.
Table 2-31 CREATE VERSION Input Parameters
Count
QUIRED
1-1
2 CRE-
ATE-
TYPE
CRE-
ATE-
TYPE
Enum COMMON:COM-
MON
OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGBS_2
COMMON RE-
QUIRED
1-1
3 FILEP-
ATH
FILEPA-
TH
STRING 0-1000 "--" RE-
QUIRED
1-1
Output Parameters
Table 2-32 shows the output parameters of CREATE VERSION.
Table 2-32 CREATE VERSION OUTPUT PARAMETERS
4 PKGTYPE STRING VerType 1-1
5 PKGID INT PkgId 1-1
6 VERNO STRING VerNo. 1-1
2-31

8 PKGPATH STRING PkgPath 1-1
9 FILESIZE STRING FileSize 1-1
10 MAKETIME STRING MakeTime 1-1
11 ISINITVER Enum 0:NO
1:YES
1-1
Example
The following example shows how to deliver a common version to
the database of subnet 40. In this example, the version path is
/home/RNC_Version/4.13.10x04P01/RELEASE/UMTS_V4.13.10.04P01.pkg.
CREATE VERSION:MEID= 40 ,CREATETYPE= COMMON ,FILEPATH= "/home/RNC_
Version/4.13.10x04P01/RELEASE/UMTS_V4.13.10.04P01.pkg" ;
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
No. |VerType |PkgId |VerNo. |PkgName
|PkgPath |FileSize |MakeTime |IsInitVer
-------------------------------------------------------------------------------
-----------------------
1 UMTS Patch 3641446708 4.13.10.04P01 UMTS_V4.13.10.04P01.pkg
null 430274976 2013-09-12 NO
-------------------------------------------------------------------------------
-----------------------
Rows: 1
2.4 D
2.4.1 DEACTIVE VERSION
Shortcut
DEACTIVE VERSION
2-32

Chapter 2 Command
Function
Deactivates the version package that is activated by using the ACTIVE VERSION
command. This command can be used when you decide not to use a package.
Command
DEACTIVE VERSION:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYPE >,P
KGID=< PKGID >,PKGNAME=< PKGNAME >;
INPUT PARAMETERS
Table 2-33 shows the input parameters of DEACTIVE VERSION.
Table 2-33 DEACTIVE VERSION Input Parameters
Count
QUIRED
1-1
2 BRD-
SER-
VER-
TYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGBS_2
OMP RE-
QUIRED
1-1
3 PKGID PKGID INT -92233720368547758
08-922337203685477
5807
1 RE-
QUIRED
1-1
4 PKG-
NAME
PKG-
NAME
STR-
ING
0-1000 - RE-
QUIRED
1-1
Output Parameters
Table 2-34 shows the output parameters of DEACTIVE VERSION.
Table 2-34 DEACTIVE VERSION OUTPUT PARAMETERS
2-33

Example
The following example shows how to deactivate the default OMP version package with the
ID as 3641446708 and the name as UMTS_V4.13.10.04P01.pkg in subnet 40. The board
deactivated with the default version is of CPU 1, slot 1, shelf 1, rack 1.
DEACTIVE VERSION:MEID= 40 ,BRDSERVERTYPE= OMP ,PKGID= 3641446708 ,PK
GNAME= "UMTS_V4.13.10.04P01.pkg" ,PHYSADDRESS= "1/3/1/1" ;
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
|DetailResult
-------------------------------------------------------------------------------
version operates successfully
-------------------------------------------------------------------------------
Rows: 1
2.4.2 DEL ALMWOBBLE
Shortcut
DEL ALMWOBBLE
Function
Delete a wobble rule.
Command
DEL ALMWOBBLE:NE=< NE >,ALARMCODE=< ALARMCODE >;
INPUT PARAMETERS
Table 2-35 shows the input parameters of DEL ALMWOBBLE.
2-34

Chapter 2 Command
Table 2-35 DEL ALMWOBBLE Input Parameters
Count
1 NE Ne ID INT 0-65535 - RE-
QUIRED
1-1
2 ALARM-
CODE
Alarm
Code
INT 0-429496
7295
- RE-
QUIRED
1-1
Output Parameters
Table 2-36 shows the output parameters of DEL ALMWOBBLE.
Table 2-36 DEL ALMWOBBLE OUTPUT PARAMETERS
Example
DEL ALMWOBBLE:NE= 1 ,ALARMCODE= 2 ;
2.4.3 DELETE
Shortcut
DELETE
Function
This command deletes configuration data records.
This command can be used when configuration data requires to be deleted in routine
maintenance.
After the data is modified in batches and saved, the corresponding MML deletion command
is available in the pop-up dialog box
After the command is executed successfully, the configuration data is deleted.
Impact on the system: The deleted configuration data has no effect on the system before
it is synchronized to the NE. After the deleted configuration data is synchronized to
the NE, configuration data of different MOCs have different effects on the system. The
configuration data of some services may cause NE restart or cell recreation. Therefore,
be cautious.
Command
DELETE:[MOC=< MOC >][,MOI=< MOI >][,EXTENDS=< EXTENDS >];
2-35

INPUT PARAMETERS
Table 2-37 shows the input parameters of DELETE.
Table 2-37 DELETE Input Parameters
Count
1 MOC MOC STRING 0-100 - ANY
OPTION
1-1
2 MOI MOI STRING 0-214740
0000
- ANY
OPTION
1-1
3 EX-
TENDS
Extends
attributes
STRING 0-214740
0000
- ANY
OPTION
1-1
Output Parameters
Table 2-38 shows the output parameters of DELETE.
Table 2-38 DELETE OUTPUT PARAMETERS
Example
The following example shows how to delete NE 4 in subnet 0. After the command is
successfully executed, the returned result is “ 1 instance(s) of NEManagedElement
deleted”.
DELETE:MOC= " NEManagedElement" ,MOI= "SubNetwork=0,MEID=4" ;
Are you sure to delete it?
Result
----------------------------------------------------------------------
1 instance(s) of NEManagedElement deleted.
----------------------------------------------------------------------
2.4.4 DELETE VERSION
Shortcut
DELETE VERSION
Function
This command executes the following operations:
1. Delete the installation package information from the package information table.
2. Delete the version file information from the full table.
3. Delete the version files of the package from the OMP disk.
2-36

Chapter 2 Command
The corresponding version package must be deactivated before using this command. This
command can delete unnecessary version packages.
Command
DELETE VERSION:MEID=< MEID >,BRDSERVERTYPE=< BRDSERVERTYPE >,PKG
ID=< PKGID >,PKGNAME=< PKGNAME >;
INPUT PARAMETERS
Table 2-39 shows the input parameters of DELETE VERSION.
Table 2-39 DELETE VERSION Input Parameters
Count
QUIRED
1-1
2 BRD-
SERVER-
TYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGBS_
2
OMP RE-
QUIRED
1-1
775808-9223372
036854775807
1 RE-
QUIRED
1-1
4 PKGNAME PKGNAME STR-
ING
0-1000 - RE-
QUIRED
1-1
Output Parameters
Table 2-40 shows the output parameters of DELETE VERSION.
Table 2-40 DELETE VERSION OUTPUT PARAMETERS
4 PKGNAME STRING PackageName 1-1
Example
The following example shows how to delete the OMP version with the ID as 3641446708
and name a UMTS_V4.13.10.04P01.pkg from subnet 40.
2-37

DELETE VERSION:MEID= 40 ,BRDSERVERTYPE= OMP ,PKGID= 3641446708 ,PKG
NAME= "UMTS_V4.13.10.04P01.pkg" ;
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
No. |PackageName |FileResult
----------------------------------------------------------------
----------------------------------------------------------------
Rows: 1
2.4.5 DEL POLICY
Shortcut
DEL POLICY
Function
time.
6. Others.
2-38

Chapter 2 Command
The DEL POLICY command is used to delete the existed policy, including timing policy
and periodic policy. Generally, this command is used to delete a policy when it is useless.
Usually, a policy name is used as an index for deleting a policy.
A policy name is a uniquely user-defined name.
If you can find the relevant policy after specifying the policy name, a message of “Delete
policy successfully”will be displayed. Otherwise, a message of “Operation fails” will be
displayed.
Command
DEL POLICY:POLICYNAME=< POLICYNAME >;
INPUT PARAMETERS
Table 2-41 shows the input parameters of DEL POLICY.
Table 2-41 DEL POLICY Input Parameters
No Name Notes Type Range Default Option In-
stance
Count
1 POLICY-
NAME
Policy name, the
identification of a policy
name.
STR-
ING
1-1000 - REQUI-
RED
1-1
Output Parameters
Table 2-42 shows the output parameters of DEL POLICY.
Table 2-42 DEL POLICY OUTPUT PARAMETERS
1 RE-
SULT
STRING The execution result is displayed, showing that
the policy is deleted successfully or the execution
is failed.
1-1000
Example
The following example shows how to delete a policythat is named “aaa”.
DEL POLICY:POLICYNAME= "aaa" ;
Result
Delete policy aaa successfully
2-39

2.5 E
2.5.1 EXECUTE POLICY INSTANTLY
Shortcut
EXECUTE POLICY INSTANTLY
Function
time.
6. Others.
Based on the policy events that trigger a policy, policies fall into two types: periodic policies
With the use of this command, the execution script of a policy will be executed once the
policy name is specified.
The result can be successful or failed.
Command
EXECUTE POLICY INSTANTLY:POLICYNAME=< POLICYNAME >;
INPUT PARAMETERS
Table 2-43 shows the input parameters of EXECUTE POLICY INSTANTLY.
2-40

Chapter 2 Command
Table 2-43 EXECUTE POLICY INSTANTLY Input Parameters
No Name Notes Typ-
e
Ran-
ge
De-
fault
Option Instance
Count
1 POLICY-
NAME
Policy name, the
identification of a policy
name.
ST-
R-
ING
0-10
00
- RE-
QUIRED
1-1
Output Parameters
Table 2-44 shows the output parameters of EXECUTE POLICY INSTANTLY.
Table 2-44 EXECUTE POLICY INSTANTLY OUTPUT PARAMETERS
1 RESULT STRING Execution result. 1-1000
Example
The following example shows how to instantly execute a policy that is named “aaa”.
EXECUTE POLICY INSTANTLY:POLICYNAME= "aaa" ;
Result：
Execute policy aaa successfully
2.6 G
2.6.1 GET BOOT
Shortcut
GET BOOT
Function
Checks the Current boot type and next-time Boot type of the active and standby OMP
boards or independent boards. Before changing the Boot type, you can use this command
to check the Current boot type.
Command
GET BOOT:MEID=< MEID >,BOARDTYPE=< BOARDTYPE >,BRDSERVERTYPE=<
BRDSERVERTYPE >;
INPUT PARAMETERS
Table 2-45 shows the input parameters of GET BOOT.
2-41

Table 2-45 GET BOOT Input Parameters
fault
Option Instance
Count
1 MEID MEID INT 0-4095 85 REQUIRED 1-1
2 BOARD-
TYPE
BOARD-
TYPE
Enum MAS-
TER:MASTER
SLAVE:SLAVE
MAS-
TER
REQUIRED 1-1
3 BRD-
SERVER-
TYPE
Board
Server
Type
Enum OMP:OMP
ECMM:ECMM
EGBS:EGBS
EGFS:EGFS
EXFS:EXFS
EGBS_2:EGB-
S_2
OMP REQUIRED 1-1
Output Parameters
Table 2-46 shows the output parameters of GET BOOT.
Table 2-46 GET BOOT OUTPUT PARAMETERS
5 MSSTATE STRING MSState 1-1
6 CURBOOTTYPE STRING CurBootType 1-1
7 NEXTBOOT-
TYPE
STRING NextBootType 1-1
Example
The following example shows how to query the boot mode of the main OMP in subnet 40.
GET BOOT:MEID= 40 ,BOARDTYPE= MASTER ,BRDSERVERTYPE= OMP ;
2-42

Chapter 2 Command
------------- System Command -------------
Result
--------
--------
DetailInfo
------------
No Detail
------------
No. |FileResult |MSState |CurBootType |NextBootType
-------------------------------------------------------------------------------
1 version operates successfully Master Boot from board Boot from board
-------------------------------------------------------------------------------
Rows: 1
2.6.2 GET CELLSTATUS
Shortcut
GET CELLSTATUS
Function
This command is used to query the debugging state of a cell at the controller side. The
cell debugging state can be: Normal (0), Debugging(2), Alarm debugging(5), Performance
debugging (6)The default is normal state.
If the cell is set to the debugging state, the cell does not report alarm and performance
data to the EMS.
If the cell is set to the alarm debugging state, the cell does not report alarms to the EMS
but reports performance data to the EMS.
If the cell is set to the performance debugging state, the cell does not report performance
data to the EMS but reports alarms to the EMS.
After the cell is set to a debugging state, the rules for all carriers under the cell to report
alarm and performance data must be consistent with those for the cell.
Command
GET CELLSTATUS:PRODUCT=< PRODUCT >,MEID=< MEID >[,SITEID=< SITEID >][,C
ELLID=< CELLID >][,CONFIGSET=< CONFIGSET >];
INPUT PARAMETERS
Table 2-47 shows the input parameters of GET CELLSTATUS.
2-43

Table 2-47 GET CELLSTATUS Input Parameters
Count
1 PROD-
UCT
Product
informa-
tion
STRING 1-40 - RE-
QUIRED
1-1
2 MEID ME ID
of the
controller
INT 0-4095 - RE-
QUIRED
1-1
3 SITEID SITE ID INT 0-65535 - ANY
OPTION
1-1
4 CELLID Cell ID INT 0-65535 - ANY
OPTION
1-1
5 CON-
FIGSET
Snapshot
or mod-
ification
area iden-
tifier
INT 0-1 1 ANY
OPTION
1-1
Output Parameters
Table 2-48 shows the output parameters of GET CELLSTATUS.
Table 2-48 GET CELLSTATUS OUTPUT PARAMETERS
2 EXCEPTION STRING Exception 1-1
3 DESCRIPTION STRING CELL MAINTAIN
INFO
1-1
Example
The following example shows how to query the debugging state of cell 1 of NodeB office
1 under the UMTS managed NE 2233.
GET CELLSTATUS:PRODUCT= "wcdma" ,MEID= 2233 ,SITEID= 1 ,CELLID= 1 ;
2-44

Chapter 2 Command
------------- System command -------------
Result
------
0
------
Cell debugging state information
------------------
PRODUCT-MEID-SITEID-CELLID-MAINTAINSTANCE
wcdma-2233-1-1-2
------------------
2.6.3 GETCMDLOG
Shortcut
GETCMDLOG
Function
A network management system can have multiple users. To trace each user's operations
performed on the network management system, such as querying, adding, editing,
deleting, or login, the log management system is introduced into the network management
system. With the use of the log management system, each user's operations on the
network management system can be traced. Data tracing helps to restore data if data is
deleted or modified accidentally. In this way, data integrity is protected.
Log management includes operation log, security log, and system log. Operation log takes
the record of basic operations that a user performs on the network management system,
such as creating, deleting, modifying data, and executing MML commands.
The GETCMDLOG command is used to query the history operation logs of all users on the
network managements system. The user can set the amount of logs which is displayed
on each page and the amount of pages. The optional parameters are as follows:
User Name: Once the user name is specified, only the operation logs matching the user
name are returned in the query result.
IP: Once the IP address is specified, only the operation logs matching the IP address are
returned in the query result.
Start Time: Once the Start Time is set, the operation logs matching the start time are
queried.
End Time: Once the End Time is set, the operation logs matching the end time are queried.
CMDCODE: Each operation has its CMDCODE. Once the CMDCODE is specified, only
the operation logs matching the CMDCODE are returned in the query result.
2-45

ISSUCCESS: The value can be 0 or non-zero number. 0 indicates that the successful
operation logs are returned in the query result. Other non-zero numbers indicate that the
failed operation logs are returned in the query result.
LOGRANK: The user’s operations are classified into different ranks. Once the LOGRANK
is specified, only the operation logs matching the LOGRANK are returned in the query
result.
PAGENO and PAGENUM: Both parameters are usually used together. For example, if
PAGENO is set to 2 and PAGENUM is set to 10, ten lines of the result are displayed on one
page and the second page is displayed. Namely, lines from 11 through 20 are displayed.
The returned result includes the following:
Serial Number: The serial number indicates which line of the result is returned.
LOGID: This parameter indicates the log ID. Each log has a unique log ID.
LOGRANK: The user’ operations are classified into different ranks.
User Name: This parameter indicates the user who executed the operation.
CMDCODE: This parameter indicates the code that identifies the same type of operations.
Operation Name: This parameter indicates the operation name, such as MML operation.
Details: This parameter presents the detailed operation information, such as policy
operation information.
ISSUCCESS: This parameter indicates whether the operation is successful or not. The
value can be 0 or non-zero number. 0 indicates that the operation is successful. Other
non-zero numbers indicate that the operation is failed.
Failure Reason: IF the operation is failed, the failure reason is described here.
IP: This parameter indicates the access IP of the client.
CONMODE: This parameter indicates the mode of connecting to the network management
system. Generally, it is GUI or MML terminal.
Start Time and End Time: The two parameters indicate the start time and end time of
executing the operation.
Command
GETCMDLOG:[USERNAME=< USERNAME >][,IP=< IP >][,STARTTIME=< STARTTIME
>][,ENDTIME=< ENDTIME >][,CMDCODE=< CMDCODE >][,LOGID=< LOGID >][,CONM
ODE=< CONMODE >][,ISSUCCESS=< ISSUCCESS >][,LOGRANK=< LOGRANK >][,P
AGENO=< PAGENO >][,PAGENUM=< PAGENUM >];
INPUT PARAMETERS
Table 2-49 shows the input parameters of GETCMDLOG.
2-46

Chapter 2 Command
Table 2-49 GETCMDLOG Input Parameters
fault
Option Instance
Count
1 USER-
NAME
User name. If “aa”is specified,
only the operation logs of the “aa”
user are returned in the query
result.
STR-
ING
0-100
000
- ANY
OP-
TION
1-100000
2 IP Operation IP. STR-
ING
0-100
000
- ANY
OP-
TION
1-100000
3 START-
TIME
The operation logs matching the
start time are queried.
DAT-
E
- - ANY
OP-
TION
1-1
4 END-
TIME
The operation logs matching the
end time are queried.
DAT-
E
- - ANY
OP-
TION
1-1
5 CMD-
CODE
Log operation code. STR-
ING
0-100
000
- ANY
OP-
TION
1-100000
6 LOGID Log ID. INT - - ANY
OP-
TION
1-100000
7 CON-
MODE
The connection mode of the
client. If the client is connected to
the network management through
the configuration window of the
network management system, the
connection mode is GUI.
STR-
ING
0-100
000
- ANY
OP-
TION
1-100000
8 ISSUC-
CESS
0 indicates that logs of successful
operations are obtained. 1
indicates that logs of failed
operations are obtained.
INT - - ANY
OP-
TION
1-100000
9 LO-
GRANK
Log rank. Once the LOGRANK
is specified, only the operation
logs matching the LOGRANK are
obtained.
INT - - ANY
OP-
TION
1-100000
10 PAG-
ENO
Page number, which is used with
PAGENUM. If PAGENO is set to
2, the second page of the result
is displayed.
INT 1-100
000
- ANY
OP-
TION
1-1
2-47

fault
Option Instance
Count
11 PA-
GENUM
The amount of logs displayed
on each page. It is used with
PAGENO. If PAGENO is set to 2
and PAGENUM is set to 10, ten
lines of the result are displayed on
one page and the second page is
displayed.
INT 1-100
00000
- ANY
OP-
TION
1-1
Output Parameters
Table 2-50 shows the output parameters of GETCMDLOG.
Table 2-50 GETCMDLOG OUTPUT PARAMETERS
1 INFORMATION STRING The execution result information
is displayed.
1-1
2 LOGID INT Log ID 1-1
3 LOGRANK STRING Log Rank 1-1
4 USERNAME STRING User Name 1-1
5 CMDCODE STRING Cmd Code 1-1
6 OPSET STRING Operation Set 1-1
7 DETAIL STRING Detail 1-1
8 ISSUCCEED STRING Is Succeed 1-1
9 FAILREASON STRING Fail Reason 1-1
10 CLIENTIP STRING Client IP 1-1
11 CONMODE STRING Connect Mode 1-1
12 STARTTIME STRING Start Time 1-1
13 ENDTIME STRING End Time 1-1
14 OPRES STRING Operation Resource 1-1
15 DESCRIPTION STRING Description 1-1
16 LOG COMPLEX The log information is returned. 1-100000
Example
The following example shows how to query logs.
GETCMDLOG:USERNAME= admin ,IP= 10.62.57.118, ,STARTTIME= "2013-08-06 09:1
6:28" ,ENDTIME= "2013-09-07 09:16:28" ,ISSUCCESS= "0" ,PAGENO= 1 ,PAGENUM=
10 ;
2-48

SJ-20140527134054-017-ZXUR 9000 UMTS (V4.13.10.15) MML Command Reference_594423.pdf

SJ-20140527134054-017-ZXUR 9000 UMTS (V4.13.10.15) MML Command Reference_594423.pdf

Recommended

Recommended

More Related Content

Similar to SJ-20140527134054-017-ZXUR 9000 UMTS (V4.13.10.15) MML Command Reference_594423.pdf

Similar to SJ-20140527134054-017-ZXUR 9000 UMTS (V4.13.10.15) MML Command Reference_594423.pdf (20)

SJ-20140527134054-017-ZXUR 9000 UMTS (V4.13.10.15) MML Command Reference_594423.pdf