THOT

SOLUTIONS

Amos/Moshell
Course objective
• Get to know the work environment of AMOS and
MOSHELL
• Differences between AMOS and MOSHELL
• Know and understand the main commands used in the
MOSHELL environment
 NOTE

WARNING! Advanced Managed Object Scripting (AMOS)

is an extremely powerful command line utility that can
cause substantial damage to a network element. It is
the operator's responsibility to ensure that they have
read and fully understood all AMOS command
descriptions and are competently trained in the use of
AMOS commands before attempting to execute any
commands against network elements.

AMOS and MOSHELL

• AMOS is a feature of OSS-RC that is available since OSS-

 RC 5.3. It has been developed as the customer version of
MOSHELL. The AMOS and MOSHELL commands are the
same, except the lab commands and Ericsson internal
commands which are not available in AMOS.
• Some internal Ericsson commands: fget, fset, facc - Not
available in AMOS
• Some lab commands: pset, pcr, pdeb, pbl, pdel - Not
available in AMOS

Services

• Alarm Service (AS)

• Configuration Service (CS) File Transfer
 (FTP/HTTP)
• Inventory Service (IS)
• Registration Service (LS)
• OSE Shell Notification (COLI)
• Performance Measurement (PM) Service
 Secure and non-secure access

)
LOVES
 Starting AMOS and MOSHELL
Command Action Result
LOVES Run the command This will open AMOS in offline
>masters mode

Run the command:

This will open an AMOS
>amos <node_IP>
session to a network object.

MOSHELL Run the command This will open a MOSHELL

>moshell <node_IP> session to a network object
 Leaving AMOS

Passe Action Result

d
1 This will close only the current
In an AMOS session, run one
AMOS session.
of the following commands:
> q
> quit
> exit
> bye
AMOS/MOSHELL operation

Object Management
 Concepts

• AMOS Command Line

• command pipeline
• Regular Expression Managed Object
• Managed object model
• MO Tree and MO Naming Conventions
• Services and protocols User-specific configuration

AMOS Supported Shortcuts

• Ctrl + F or right arrow Move forward one character
• Ctrl + B or left arrow Go back one character
• Up arrow Previous command in buffer
• Down arrow Next command in buffer
• Backspace Delete a character backwards
• Ctrl + D or Del Delete a character forward
• Ctrl + A or home , Go to the beginning of line
• Ctrl + E or end , Go to the end of the line
• Ctrl + U Delete all backward characters
• Ctrl + K Delete all forward characters
• Ctrl + F Move forward one word
• Ctrl + B Move back a word
• Ctrl + INSERT Copy to clipboard
• Shift + INSERT Paste from clipboard

Pipes

> The Pipe “|” command used to filter a specific string in a

command output
 Examples:
> str | grep CBE22A
Shows the status of cell CBE22A

> cabx | grep RAX

Shows all RAX boards installed on NodeB

Regular expressions

• . Find any information

• * Matches 0 or more occurrences of the above information.
• [] Matches a character or range of characters within the
brackets
• [^] DO NOT INCORPORATE the range of characters or characters
within
the brackets
• | o´ ^ Find matches from the beginning of the string
• $ Find matches from the end of the string
• ! Denial; do not match
• % Match in reverse order
• () Group regular expressions
 Examples:
to* Find a or aa or aaa

.*

Wildcard that matches 0 or more occurrences of any character

[az] Match all letters from A to Z

[abe] Matches letters A, B and E

[^3] Matches any character but not 3

3|5|6 Matches 3, 5 and 6.

^a.*4$ Matches a string that starts with a and ends with 4, with any character in
between.

cell(11|23|45) Group regular expressions together using square brackets that match
cell11 or cell23 or cell45
 Managed Object Model
• The MOM is a document that describes the SW version of a
particular node:
• All the different types of MO (kinds of MO)
• Attributes contained in each MO class
• Relationships (parents/children) between MO classes
• Actions supported by each MO class The MOM can be
found on ALEX and at the links below:

CPP MOM:
• MOM
https://extinfo.uab.ericsson.se/cpp_mom/

• RNC: http://wrn.ericsson.se/~emogroup/mom/ MOM

• RBS: http://wrn.ericsson.se/~enrbsmom/mom/
MO Tree and Naming Convention.
Local Distinguish Name (LDN)
MOs are organized in a hierarchical structure. Each MO instance is
uniquely identified on the node by its Local Distinguish Name (LDN).

Example:
ManagedElement=1
ManagedElement=1,Equipment=1
ManagedElement=1,Equipment=1,Subrack=MS
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1,Prog
ram=DbmFpgaLoader
 MO Tree and Naming Conventions

Relative Distinguish Name(RDN)

The string located at the far right of an LDN, just after the last comma, is
called the Relative Distinguish Name (RDN).

It is a relative way to approach an MO instance

EXAMPLE :
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19, PlugInUnit=1, Program=DbmFpgaLoader
ManagedElement=1,Equipment=1,Subrack=MS,Slot=23, PlugInUnit=1, Program=DbmFpgaLoader
 MO Tree and Naming Conventions

Full Distinguish Name (FDN)

The Full Distinguish Name (FDN) adds a network element prefix in front of
the LDN of each MO instance to specify which node this MO belongs to.

Example:

SubNetwork=AUS, SubNetwork=H2RG_0201, MeContext=St_Leonards_Station_2065010 ,

ManagedElement=1, TransportNetwork=1, AtmPort= MS-24-1
 Service layer

• Management Information Base (MIB)

Management Object Class
 ipdatabase

The ipdatabase is a file where each node on the network can store:
1. Node name (arbitrary)
2. IP address or DNS name
3. Password (optional)

The ipdatabase file should be saved in:

/home/your_user/moshell/sitefiles/ipdatabase
 Features
The O&M user can access the MOs through several services:
• Configuration Service (CS): read and change configuration data; configuration
data is stored in MO attributes
• Alarm Service (AS): Retrieves the list of currently active alarms on each MO
• Notification Service (NS): subscribe and receive notifications from the node,
informing about parameter changes/alarms in the MOs
• Inventory Service (IS): Get a list of all HW and SW defined on the node
• Logging Service (LS) – Keeps a log of certain events such as configuration
changes, alarms rising and stopping, node and card reboots, and JVM events
• Performance Measurement (PM): Configuring statistical scanners or event
filters; Statistics counters are stored in MO pm attributes and sent to an XML
file every 15 minutes. Events are sent to binaries every 15 minutes
 MO Attributes (attribute status)

• Operation status
–Enable
– Disable
• administrative status
– Locked
–Unlocked
– Shutting_down
• Availability status
– No_Status
– In_Test
–Failed
– Power_Off
– Off_Line
 Actions of MOs

• Some MOs have defined actions that are used to execute

particular operations related to the MO on which it is executed

• Some actions do not require any MO attributes

• Other actions involve one or more attributes

Commands
 Command Descriptions
RNCSM10>h
------------------- BASIC MO COMMANDS --------------------
mom[tc] lt/ltc[1-
9] lc[1-9]/lcc
Print description of MO classes, CM/FM attributes, actions, enums and
structs.
Load MO tree (full or partial) and build proxy table.
Load MO tree (full or partial) and build proxy table.
cvls/cvmk/cvms/cvset Configuration Version (CV) handling.
inv[hr] Complete HW/SW inventory. Includes information about RPUs, licensing,
JVM, devices, XPs, etc.
cab[slxradgtm] Display of miscellaneous COLI printouts relating to hw, sw, restarts, leds,
cpu load, errors, disk

--------------------- OTHER COMMANDS ---------------------

uv Print or change moshell configuration settings (also called "user variables").
Print scripting variables.
pv !/l Execute a unix command on the PC/workstation.
 Command Descriptions
--------------------- PM COMMANDS -------------------------------
pmom[ac]/lmom[c] Print description of PM counters (pmom) or log attributes.
pget/lpget Read PM attribute(s) from MO(s).
hpget[c]/lhpget[c] Read PM attribute(s) from MO(s), print horizontally one line per
M.O.

---------------------HELP CHAPTERS ---------------------------------

0 Installation, security, and user settings
1 Revision History
2 Tutorial
3 Command syntax, regular expressions
• RNCSM01>h pget

pget/lpget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>]

 Command Descriptions
Read PM attribute(s) from MO(s).

USMSNE18> h inv inv[hr] [<Filter>] [<stateFilter>]

Complete HW/SW inventory. Includes information about RPUs, licensing, JVM, devices, XPs, ISL, etc.

This command performs a complete HW/SW inventory via the MO interface. All SW including JVM, RPU, and
Device SW (spm,dsp,fpga) is shown. Licensing (features and capacity) as well as overview of the ISL links is
also shown.
 Navigating MOM from Amos

There are currently two variations of the MOM command:

• mom shows all attributes except PM attributes

• pmom is used to view PM attributes

RNCSM10> h mom

mom[tc] [<moclass/struct/enum>|all] [<attribute/action>|all] [<attr- type>|

all] [<attr-flags>|all] [<attr-desc>]
Navigating the MOM from Amos
• See the MOM Tree structure:
Example:
• OFFLINE_WIURNC1_KGET_20110919_175714> momt atmp

LDNs containing AtmPort

• ManagedElement[1],TransportNetwork[1],AtmPort[0-1000]
• ManagedElement[1],TransportNetwork[1],AtmPort[0-1000],VplTp[0-]
• ManagedElement[1],TransportNetwork[1],AtmPort[0-1000],VplTp[0-],VpcTp[0-1]
• ManagedElement[1],TransportNetwork[1],AtmPort[0-1000],VplTp[0-],VpcTp[0-
1],VclTp[0- 5000]

MO classes over AtmPort

ManagedElement[1],TransportNetwork[1],AtmPort[0-1000]

MO classes under AtmPort

VplTp[0-]
VpcTp[0-1]
VclTp[0-5000]
MO Services
• Configuration Management Service

Operation purpose Related Moshell Commands Protocol

GetChildren To list the LDNs of the MOs currently present in the MIB lt, lc corba (CM)

GetAttribute To read the value of one more attributes. get, hget, pget, st, prod, inv, etc.

CallAction To call an action on an MO acc (acl)

SetAttribute To change the value of an attribute, (as long as it is not set, bl, deb
restricted or read-only)

CreateMO To create an MO cr

DeleteMO To delete an MO del, rdel

Using Regular Expressions
Fault management services

Operation Purpose Related Moshell Protocol

command

GetAlarms List of active alarms to the corba (FM)

Acknowledge/unacknowledge Confirm Not supported in amos or

Acknowledge an alarm moshell

pr/lpr [<moGroup>|<moFilter>|<proxy(s)>]

Prints the MO LDN and proxy ID for all or part of the MO tree currently loaded in moshell.

RNCSM01> pr ms-27-4

8667 TransportNetwork=1,AtmPort=MS-27-4
Using Regular Expressions
RNCSM01> lpr ms-27-4

MO Proxy

8667 TransportNetwork=1,AtmPort=MS-27-4
8668 TransportNetwork=1,AtmPort=MS-27-4,VplTp=vp1
8669 TransportNetwork=1,AtmPort=MS-27-4,VplTp=vp1,VpcTp=1
8670 TransportNetwork=1,AtmPort=MS-27-4,VplTp=vp1,VpcTp=1,VclTp=vc1444
8671 TransportNetwork=1,AtmPort=MS-27-4,VplTp=vp1,VpcTp=1,VclTp=vc1443

RNCSM02> lpr ES-1-27-1.*vc12043

090206-14:49:02 10.107.240.8 7.1f RNC_NODE_MODEL_G_5_30 stopfile=/tmp/8944 ==========================================

========================================
MO Proxy
======================================================================

9178 TransportNetwork=1,AtmPort=ES-1-27-1,VplTp=vp1,VpcTp=1,VclTp=vc12043
======================================================================

Total: 1 MOs

RNCSM02> lpr ES-1-27-1.*vc1204[1-4]

Using Regular Expressions
======================================================================

MO Proxy
======================================================================

9177 TransportNetwork=1,AtmPort=ES-1-27-1,VplTp=vp1,VpcTp=1,VclTp=vc12044
9178 TransportNetwork=1,AtmPort=ES-1-27-1,VplTp=vp1,VpcTp=1,VclTp=vc12043
9179 TransportNetwork=1,AtmPort=ES-1-27-1,VplTp=vp1,VpcTp=1,VclTp=vc12042
9180 TransportNetwork=1,AtmPort=ES-1-27-1,VplTp=vp1,VpcTp=1,VclTp=vc12041

Total: 4 MOs
RNCSM02> lpr ExternalGsmCell=1PIN47 $

090206-14:58:18 10.107.240.8 7.1f RNC_NODE_MODEL_G_5_30 stopfile=/tmp/8944

======================================================================
MO Proxy
======================================================================
24890 RncFunction=1,ExternalGsmNetwork=40,ExternalGsmCell=1PIN47B
24891 RncFunction=1,ExternalGsmNetwork=40,ExternalGsmCell=1PIN47A
24904 RncFunction=1,ExternalGsmNetwork=40,ExternalGsmCell=1PIN47C
======================================================================
Total: 3 MOs

RNCSM02> pr ExternalGsmCell=1PIN47
Using Regular Expressions
090206-14:58:38 10.107.240.8 7.1f RNC_NODE_MODEL_G_5_30 stopfile=/tmp/8944
======================================================================
MO Proxy
======================================================================
24890 RncFunction=1,ExternalGsmNetwork=40,ExternalGsmCell=1PIN47B
24891 RncFunction=1,ExternalGsmNetwork=40,ExternalGsmCell=1PIN47A
24904 RncFunction=1,ExternalGsmNetwork=40,ExternalGsmCell=1PIN47C

Total: 3 MOs
RNCSM01> lpr Subrack=MS,Slot=28,PlugInUnit=1

MO Proxy

159 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1

160 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321120_R51HV02

161 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1322250_R51TK01

162 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321409_R51SZ01

163 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,SwitchCoreUnit=1

164 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1322166/3_R51SZ01

165 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321407_R51SZ01

166 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321121_R51GD01

167 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1322165/12_R51SZ01

RNCSM01> lpr %Subrack=MS,Slot=28,PlugInUnit=1

MO Proxy

167 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1322165/12_R51SZ01
Using Regular Expressions
166 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321121_R51GD01

165 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321407_R51SZ01

164 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1322166/3_R51SZ01

163 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,SwitchCoreUnit=1

162 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321409_R51SZ01

161 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1322250_R51TK01

160 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1,Program=CXC1321120_R51HV02

159 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1

Total: 9 MOs

st/lst [<moGroup>|<moFilter>|<proxy(s)>|all] [<state-filter>]

Prints the states of the MO's (operationalState and administrativeState when applicable).
Example :
RNCSM01> lst Utrancell=AITU01A

090210-12:11:11 10.108.240.8 7.1d RNC_NODE_MODEL_G_5_30 stopfile=/tmp/315

Proxy Adm State Op. State MO

492 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=AITU01A,Rach=1

1366 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=AITU01A
1993 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=AITU01A,Hsdsch=1
2620 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=AITU01A,Pch=1
Using Regular Expressions
3247 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=AITU01A,Fach=1
3873 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=AITU01A,Hsdsch=1,Eul=1

Total: 6 MOs
str[12ft] [<csvfile>] [<filter-options>] [ | <unix cmds>]

Prints the status of IubLinks/AbisLinks and their associated cells and channels (RNC/BSC only).
Example:
RNCSM01> str
Following 183 sites are up:

MOD IUBLINK CELLNAMES CFRPHEM1 CFRPHEM2 CFRPHEM3 CFRPHEM4 CFRPHEM5 CFRPHEM6 ICD12
ATMPORTS -----------------------------------------------------------------------------------
THOT...................................................................................................................................................................................................................1
NOTE........................................................................................................................................................................................................3
AMOS and MOSHELL............................................................................................................................................................................4
Services.....................................................................................................................................................................................................5
Starting AMOS and MOSHELL...............................................................................................................................................................7
Leaving AMOS.........................................................................................................................................................................................8
Concepts.....................................................................................................................................................................................................10
AMOS Supported Shortcuts.......................................................................................................................................................................10
Using Regular Expressions
Pipes...........................................................................................................................................................................................................11
Regular expressions....................................................................................................................................................................................12
Examples:................................................................................................................................................................................................14
Managed Object Model..............................................................................................................................................................................15
CPP MOM:..........................................................................................................................................................................................15
MO Tree and Naming Convention.........................................................................................................................................................16
Local Distinguish Name (LDN)..........................................................................................................................................................16
Relative Distinguish Name(RDN)......................................................................................................................................................17
Full Distinguish Name (FDN).............................................................................................................................................................18
Service layer...............................................................................................................................................................................................19
ipdatabase...................................................................................................................................................................................................21
Features.......................................................................................................................................................................................................22
The O&M user can access the MOs through several services:...........................................................................................................22
MO Attributes (attribute status)..............................................................................................................................................................23
Actions of MOs..........................................................................................................................................................................................24
Navigating MOM from Amos......................................................................................................................................................................29
Navigating the MOM from Amos...............................................................................................................................................................30
cr..........................................................................................................................................................................................................48
acl/lacl.................................................................................................................................................................................................52
u+/u-....................................................................................................................................................................................................55
al/alt.....................................................................................................................................................................................................56
run.......................................................................................................................................................................................................58
MOBATCH.........................................................................................................................................................................................61
Using Regular Expressions
Examples:............................................................................................................................................................................................65
pget......................................................................................................................................................................................................75
Reboots.....................................................................................................................................................................................................105
Log Management.........................................................................................................................................................................................110
Checking reboot information...................................................................................................................................................................111

> str –m 3
Shows the status of the cells in module 3 only
RNCSM01> str -m 3

-----------------------------------------------------------------------------------------------------

MOD IUBLINK CELLNAMES CFRPHEM1 CFRPHEM2 CFRPHEM3 CFRPHEM4 CFRPHEM5 CFRPHEM6 ICD12 ATMPORTS

3 Iub_USMJAI09_0028 AJAI09-A/B/C 111111 111111 111111 11111

3 Iub_USMMRB10_0065 AMRB10-A/B/C 111111 111111 111111 11111

3 Iub_USMMRB13_0067 AMRB13-A/B/C 111111 111111 111111 11111

3 Iub_USMMRB28_0074 AMRB28-A/B/C 111111 111111 111111 11111

3 Iub_USMMRB54_0085 AMRB54-A/B/C 111111 111111 111111 11111

3 Iub_USMMRB81_0155 AMRB81-A/B/C 111111 111111 111111 11111

3 Iub_USMOCO07_0093 AOCO07-A/B/C 111111 111111 111111 11111

3 Iub_USMVMN02_0146 AVMN02-A/B/C 111111 111111 111111 11111
Using Regular Expressions
Following 2 sites are totally or partially unavailable:

MOD IUBLINK CELLNAMES CFRPHEM1 CFRPHEM2 CFRPHEM3 CFRPHEM4 CFRPHEM5 CFRPHEM6 ICD12 ATMPORTS

3 Iub_USMOCO80_0152 AOCO80-A/B/C 100011 100011 100011 11111

3 Iub_USMPINI1_0116 APINI1-A/B/C 111111 LLLLLL LLLLLL 11111

************************************************************
get/lget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all]
[<value-filter>]

This command obtains one or more attributes from one or more MOs.

Example:
RNCSM01> lget utrancell=AMRB10A primaryscramblingcode

===================================================================
M.O. Attribute Value
===================================================================
UtranCell=AMRB10A primaryScramblingCode 50
===================================================================
Total: 1 MOs
Using Regular Expressions
kget

• “KGET" is identical to “get", except that the output is formatted slightly

differently to allow data import into some external tools such as
MCOM, Cywin. "Kget" should mainly be used when taking MO dumps
(lt all;Kget)
Using Regular Expressions
set[m][c][1][i]/lset[m][c][1][i] <moGroup>|<moFilter>|<proxy(s)> <attribute> [<value>]

The set/lset command changes or sets an attribute on one or more MO(s).

Example:
> set cell primarycpichpower 310

To set string attributes:

> set sid sib11 sib11repperiod=128, sib11startpos=20
Set administrativestate on following MOs ?
============================================================
159 Equipment=1,Subrack=MS,Slot=28,PlugInUnit=1
============================================================
Are you sure [y/n]? n
Using Regular Expressions
rset
The “rset” command changes an attribute of an MO that is restricted (Use the mom command to
check if the MO attribute is restricted).
RNCSM01> lset utrancell=AMRB10A utrancellid 0985
ID M.O. UtranCellId Result

5263 UtranCell=AMRB10A 0985 !!!! Processing failure

:se.ericsson.cello.moframework.AttrNotSettableException TAG :"AttrNotSettable"
VARIABLES :"$moType" = "UtranCell", "$attrName" = "UtranCellId"

Total: 1 MOs attempted, 0 MOs set

RNCSM01> mom utrancell utrancellid

#####################################################################################
MO Class Attribute Type Flags
#####################################################################################
ExternalUtranCell ExternalUtranCellId string
restricted,noNotification,mandatory

Naming attribute. Contains the value part of the RDN.

UtranCell UtranCellId string

restricted,noNotification,mandatory
Using Regular Expressions
RNCSM01> rset utrancell=AMRB10A utrancellid 0985

080313-11:44:14 138.85.80.46 7.0t RNC_NODE_MODEL_G_5_24 stopfile=/tmp/1816 Set

restricted attribute utracellid on following MOs ?
==========================================================================
5263 RncFunction=1,UtranCell=AMRB10A
==========================================================================
Are you sure [y/n] ? and

Logging del(get)/set/bl/deb commands to file:

/home/euseeca/moshell_logfiles/logs_moshell/undo/
undo_RNC4_080313-114423.log

Recursive Delete following MOs ?

==========================================================================
5263 RncFunction=1,UtranCell=AMRB10A
==================================================================
======================== .Delete following MOs ?

5267 RncFunction=1,UtranCell=AMRB10A,Fach=1
5266 RncFunction=1,UtranCell=AMRB10A,Hsdsch=1
5265 RncFunction=1,UtranCell=AMRB10A,Pch=1
5264 RncFunction=1,UtranCell=AMRB10A,Rach=1
Using Regular Expressions
5263 RncFunction=1,UtranCell=AMRB10A

bl[s]/lbl[s] <moGroup>|<moFilter>|<proxy(s)>

The bl/lbl command sets the administrative state of an MO to 0.

Examples:
bl aal2.*ca[246]
Block aal2 and those that end in ca2, ca4, ca6
lbl USMSNE08
Block all Mo's from the USMSNE08 site (Utrancell, Control Channels and Iub Link).
bl 234 256 248
Block proxies 234, 256, and 248
bl 001500
Block a card the same as:

lbl subrack=ms,slot=15,pluginunit=1$
bls / lbls
Option "s" is for soft lock. The administrative state is set to 2 ("shutting down"), which means
that the resource will have about 30 seconds of grace period to transfer traffic to other
resources, before it is blocked. The administrative status will automatically change to 0 after the
Using Regular Expressions
grace period of around 30 seconds.

Example:

RNCSM01> bls 530

===============================================================================
Id MO AdministrativeState
Result
===============================================================================
530 Subrack=MS,Slot=5,PlugInUnit=1 2
>>>Set.
==================================================================
============================= Total: 1 MOs attempted, 1 MOs set
RNCSM01>st 530
===============================================================================
Proxy Adm State Op. State M.O.
===============================================================================
530 2 (SHUTTINGDOWN) 1 (ENABLED) Equipment=1,Subrack=MS,Slot=5,PlugInUnit=1
==================================================================
============================= Total: 1 MOs

deb/ldeb
The ldeb command unlocks an attribute

Example:
RNCSI01> ldeb BCAS01A
Using Regular Expressions
===========================================
362 RncFunction=1,UtranCell=BCAS01A,Rach=1
980 RncFunction=1,UtranCell=BCAS01A
1438 RncFunction=1,UtranCell=BCAS01A,Hsdsch=1
1896 RncFunction=1,UtranCell=BCAS01A,Pch=1
=========================================== Are you Sure [y/n ] ? and

Id MO AdministrativeState Result
362 UtranCell=BCAS01A,Rach=1 1 >>>Set.
980 UtranCell=BCAS01A 1 >>>Set.
1438 UtranCell=BCAS01A,Hsdsch=1 1 >>>Set.
1896 UtranCell=BCAS01A,Pch=1 1 >>>Set.
Total: 6 MOs attempted, 6 MOs set

fget
Allows you to read attributes that are not described in the MOM ("Force" get).

Example:

RNCSM01> get pluginunit resourceid

==================================================================
M.O. Attribute Value
==================================================================
Total: 0 MOs
Using Regular Expressions
RNCSM01> fget pluginunit resourceid
================================
MO Attribute value
================================ resourceid 23
Subrack=MS,Slot=28,PlugInUnit=1 resourceid 22
Subrack=MS,Slot=27,PlugInUnit=1 resourceid 21
Subrack=MS,Slot=26,PlugInUnit=1
cr
This command creates an MO, given its LDN.
The LDN does not need to contain ManagedElement = 1 at startup.
The command syntax is: cr <ldn>

Note:
• If there are required attributes, to complete, the function will request them.
• If there are optional restricted attributes to populate, the function will request them.
• Type d to use the default value (which is often blank)
• The reason d is needed is that entering nothing cancels the command.
• To specify an attribute of type Struct, use the following syntax: attr1 = val1, attr2 = val2, attr3 =
val3...
Using Regular Expressions
Example of the create command:

RNCSM01>cr rncfunction=1,Iublink=1

071119-09:19:20 138.85.80.46 7.0r RNC_NODE_MODEL_G_5_24 stopfile=/tmp/3284

Attribute 1 of 4, rbsId (long): 1
Attribute 2 of 4, preferredSubrackRef (moRef:Subrack):
Enter mo LDN: Subrack=ES-1
Attribute 3 of 4, userPlaneTransportOption (structRef:TransportOprtionDef): atm=1,ipv4=0
Attribute 4 of 4. controlPlaneTransportOption (structRef:TransportOptDef): atm=1,ipv4=0
Attribute 1 of 1, userPlaneIpResourceRef (moRef:IpAccessHostPool): d
Enter mo LDN:
>>> [Proxy ID = 5468] MO name :ManagedElement=1,RncFunction=1,IubLink=1
Using Regular Expressions
del/rdel

The "del" command deletes one or more MO(s). The "rdel" command deletes MO(s) along
with the children and reserved attributes of the MO.

An MO can only be deleted when its reserved list is empty and when it has no children. If the
MO has children and/or a non-empty reserved By attribute, it is possible to use the rdel / lrdel
command instead.

The command syntax is:

del/ldel <moGroup>|<moFilter>|<proxy(s)>
Using Regular Expressions
RNCSM01> 5155

5155 RncFunction=1,IubLink=99
Warning: Undo Mode is currently inactive Are you Sure [y/n] ? and
Deleting...

5155 RncFunction=1,IubLink=99
>>> Mo deleted
Total: 1 MOs attempted, 1 MOs deleted
iublink RNCSM01>=1$

4691 RncFunction=1,IubLink=1
Warning: Undo Mode is currently inactive Are you Sure [y/n] ? and
Deleting...

4691 RncFunction=1,IubLink=1
!!!! Processing failure
:se.ericsson.wcdma.rnc.roam.mao.commonmo.ProcessingFailureException TAG
:"ProcessingFailureException" VARIABLES :"$Message" = "IubLink could not be
deleted, there are still references to cell(s)"
Total: 1 MOs attempted, 0 MOs deleted
Using Regular Expressions
acl/lacl
The acl/lacl command lists the actions that can be performed on an MO
The syntax of this command is:

acl/lacl <moGroup>|<moFilter>|<proxy(s)>|all [<action-filter>]

Using Regular Expressions
USMCBE21> acl retdevice

MO Proxy action Nr of Params

THOT 1
NOTE 3
AMOS and MOSHELL 4
Services 5
Starting AMOS and MOSHELL 7
Leaving AMOS 8
Concepts 10
AMOS Supported Shortcuts 10
Pipes 11
Regular expressions 12
Examples: 14
Managed Object Model 15
CPP MOM: 15
MO Tree and Naming Convention. 16
Local Distinguish Name (LDN) 16
Relative Distinguish Name(RDN) 17
Using Regular Expressions
Full Distinguish Name (FDN) 18
Service layer 19
ipdatabase 21
Features 22
The O&M user can access the MOs through several services: 22
MO Attributes (attribute status) 23
Actions of MOs 24
Navigating MOM from Amos 29
Navigating the MOM from Amos 30
cr 48
acl/lacl 52
u+/u- 55
al/alt 56
run 58
MOBATCH 61
Examples: 65
pget 75
Reboots 105
Log Management 110
Checking reboot information 111
Using Regular Expressions

RNCSM01> lacl AtmPort=MS-26-1,VplTp=16,VpcTp=1,VclTp=vc44

MO Proxy action Nr of Params

1505 AtmPort=MS-26-1,VplTp=16,VpcTp=1,VclTp=vc44 eteLoopBack 0

RNCSM01> lacl Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1

1722 Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1 activate 0

1722 Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1 deactivate 0
1722 Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1 emergencyActivate 0
1722 Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1 localInhibit 0
1722 Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1 localUninhibit 0
MO Proxy action Nr of Params

u+/u-
Handling undo mode (To revoke del/rdel/set commands). Likewise, it can be used to
generate MO Scripts.
u+ To start the "undo mode"
u+s To start the "simulated undo mode"
u- To stop the "undo mode" (or simulated undo mode)
or? To check if "undo mode" is active or not
Using Regular Expressions
or! To convert moshell command files to trun/emas format or undo logfiles to command
files

While running in "undo mode", the MO data is saved in a special log file for all MOs on
which the following commands are executed running undo mode:
- del/ldel
- rdel/lrdel
- bl/lbl
- deb/ldeb
- set

al/alt
The syntax
al[atkc] [-a|-u <alarm_id>] [ | <unix cmds>]

Prints the list of active alarms. Acknowledge/Unacknowledge an alarm.

The output can be piped through external Unix utilities such as "sort", "grep", "less", "plus", etc.
It is possible to combine several options, for example: al, ala, altk, alatk, altkc, etc.
• al: The list of active alarms is printed in general format, only four fields are displayed per alarm.
Using Regular Expressions
• ala: Same as a, but the full detailed list is added below the summary table.
• alt: same as a, but the time field is added to the table and the alarms are sorted
chronologically.
• alk: Same as a, but the list is separated into two parts, one for unacknowledged alarms and one for
acknowledged alarms.
• alc: Same as a, but each alarm is displayed in CSV format and all fields are displayed for each alarm.
Using Regular Expressions
USIPGE07> alt
Starting to retrieve active alarms
Nr of active alarms are: 2
Date & Time (Local) S Specific Problem Reference 1969- Cause Mo-
12-31 21:00:59 w Auto-Configuration of Board Not
Possible unavailable
Subrack=1,Slot=2
1969-12-31 21:04:33 M OpticalInterfaceLink_OpticalInterfaceLinkFailure equipment_malfunction
OpticalInterfaceLink=3-UL
>>> Total: 2 Alarms (0 Critical, 1 Major)

USIPGE07> alt | grep OpticalInterfaceLink=3-UL

090209-18:11:32 10.113.241.29 7.1d RBS_NODE_MODEL_J_5_17 stopfile=/tmp/4924
1969-12-31 21:04:33 M OpticalInterfaceLink_OpticalInterfaceLinkFailure equipment_malfunction
OpticalInterfaceLink=3-UL

run

• The run command executes a command file in moshell format.

Using Regular Expressions
• This applies to commands such as "lt / ltc", "lc / lcc", "del", "bl", "set",
where confirmation is entered automatically when executing a command
file.
• Comments can be put in the command file using the # sign. The command
file must be one command per line
Using Regular Expressions
Example:
Practice 0
Updating the primaryCpichPower parameter for some cells in
the same RNC.
Create the file “MyCommandFile.txt” or “.mos” and
upload it to the Moshell Server
lt all
lset utrancell=amrb10A primaryCpichPower 300
lset utrancell=amrb10B primaryCpichPower 290
lset utrancell=amrb10C primaryCpichPower 310
lset utrancell=asee01A primaryCpichPower 320
lset utrancell=asee01B primaryCpichPower 300
lset utrancell=asee01C primaryCpichPower 315

• run /home/U1310656/scripts/MyCommandFile.txt
Using Regular Expressions
MOBATCH

Mobatch is used to run moshell sessions on multiple nodes in parallel.

• The list of nodes must be defined in a "site file". Each node can be listed by its
node name.

• There is no limit to how many nodes can be listed within a site file. Mobatch
will run one moshell session per node listed in the site file. Up to 10 sessions will
run in parallel at any time. This limit can be changed with the "-p" option

Using : mobatch SiteFile.txt CommandFile.txt

Using Regular Expressions
mobatch example

U1310656@rjmas1o> bash
[~/moshell]$
[~/moshell]$ mobatch /home/U1310656/scripts/RNC_File.txt
/home/U1310656/scripts/Get_UtranRelation.txt /home/U1310656/scripts/Neighbour
Using Regular Expressions
MO Groups

*MP Prints all groups of MO's

OFFLINE_WIURNC1_KGET_20110919_175714> mp

MO-Group Nr of MOs

THOT...............................................................................................................................................................................................................1
NOTE....................................................................................................................................................................................................3
AMOS and MOSHELL........................................................................................................................................................................4
Services.................................................................................................................................................................................................5
Starting AMOS and MOSHELL...........................................................................................................................................................7
Leaving AMOS.....................................................................................................................................................................................8
Concepts.................................................................................................................................................................................................10
AMOS Supported Shortcuts...................................................................................................................................................................10
Pipes........................................................................................................................................................................................................11
Using Regular Expressions
Regular expressions................................................................................................................................................................................12
Examples:............................................................................................................................................................................................14
Managed Object Model..........................................................................................................................................................................15
CPP MOM:......................................................................................................................................................................................15
MO Tree and Naming Convention.....................................................................................................................................................16
Local Distinguish Name (LDN)......................................................................................................................................................16
Relative Distinguish Name(RDN)..................................................................................................................................................17
Full Distinguish Name (FDN).........................................................................................................................................................18
Service layer...........................................................................................................................................................................................19
ipdatabase...............................................................................................................................................................................................21
Features...................................................................................................................................................................................................22
The O&M user can access the MOs through several services:.......................................................................................................22
MO Attributes (attribute status)..........................................................................................................................................................23
Actions of MOs......................................................................................................................................................................................24
Navigating MOM from Amos..................................................................................................................................................................29
Navigating the MOM from Amos...........................................................................................................................................................30
cr......................................................................................................................................................................................................48
acl/lacl.............................................................................................................................................................................................52
u+/u-................................................................................................................................................................................................55
Using Regular Expressions
al/alt.................................................................................................................................................................................................56
run....................................................................................................................................................................................................58
MOBATCH.....................................................................................................................................................................................61
Examples:........................................................................................................................................................................................65
pget..................................................................................................................................................................................................75
Reboots.................................................................................................................................................................................................105
Log Management......................................................................................................................................................................................110
Checking reboot information...............................................................................................................................................................111

1.
To view the contents of an MO group, type "pr <mogroup>"
Examples:

RNCSM01> pr ms-6-1
RNCSM01> ma test ms-6-1
RNCSM01> pr test
Using Regular Expressions
RNCSM01> lpr ms-6-1
RNCSM01> lma test1 ms-6-1
RNCSM01> pr test1
RNCSM01> mp
RNCSM01> mr test
MO-Groups commands
Practice 1: Group all the cells belonging to module 9 into a group to
be able to block them.

RNCSM01> get iublink module

RNCSM01> get iublink module =9$
RNCSM01> ma iubmod9 iublink module =9$
Using Regular Expressions
RNCSM01> get iubmod9 module
RNCSM01> get iublink reserved
RNCSM01> ma cellmod9 iubmod9 reserved
Get RNCSM01> bl cellmod9
Operating AMOS/Moshell
Performance Management
PM Access
– Instantaneous counter values for MO Cello and RBS can be
PM
Commands
read via the "GetAttribute" operation of the CM service (amos
"pget" command).
– It is not possible to read instantaneous counters for MO RNC
through the CM Service.
– Counter values for a given ROP (output result period) can be
read from ROP XML files, as long as there is an active statistics
scanner containing these values.
– Events that occurred in a given ROP can be read from the
binary ROP files, as long as there is an active event scanner
containing these events.
PM
Commands
PM
Commands
operation Related moshell
command(s)
protocol

List Scanners and Event Filters pst

Create Statistics Scanner pcr

Stop Scanner pbl
corba (PM)
Resume Scanner pdeb
Delete Scanner pdel
Set Event Filter pset
View Scanner contents pgets
Read instantaneous counter value pget corba (CM)

Fetch and parse Statistics ROP files pmr/pmx

(xml) ftp/sftp
Fetch and parse Event ROP files pme
(binary)
 PM
Commands
RNCSM01>h pmom

pmom[acd]/lmom[c] [<moclass>] [<counter>] [<counter-description>] [<counter-

type>]
Print description of PM counters (pmom) or log attributes (lmom, CDMA only).
RNCSM01> pmom vcltp
#######################################################################
MO Class Pm Counters
#######################################################################
VclTp 2
currentPmRegister
pmBwUtilizationRx
pmBwUtilizationTx pmReceivedAtmCells pmTransmittedAtmCells

RNCSM01> pmom vcltp rec

#######################################################################
MO Class Pm Counter
#######################################################################
VclTp pmReceivedAtmCells
Performance monitoring counter for number of received ATM cells.
 PM
Commands
USMCBE22> pmom Carrier pmAverageRssi
090210-13:45:25 10.107.240.225 7.1d RBS_NODE_MODEL_J_5_17 stopfile=/tmp/667 ###############################
################################################## #########################
MO Class Pm Counter Type
##########################################################################################################
Carrier pmAverageRssi sequence:long
Received Signal Strength RSSI.
Measured on TR device(s) every 100 ms, and the average value is calculated at the same
rate. Stored as PDF, with 0.5 dB resolution for the first 61 values and range [-110.0..-
followed by t range [-80..-65] with a 5 db resolution.
80.0],
averageRssi o number of sampled values less than -110.0
averageRssi 0 number of sampled values in range -110.0..-109.5
averageRssi 1 number of sampled values in range -109.5..-109.0
averageRssi 2 number of sampled values in range -109.0..-108.5
3

averageRssi 59 number of sampled values in range [-81.0..-80.5[

averageRssi 60 number of sampled values in range [-80.5..-80.0[
averageRssi 61 number of sampled values in range [-80.0..-75.0[
averageRssi 62 number of sampled values in range [-75.0..-70.0[
averageRssi 63 number of sampled values in range [-70.0..-65.0[
averageRssi 64 number of sampled values greater t han or equal to -
UNDEFINED VALUE=-1 65.0
USE CASES=PM_100, PM_101
REQUIREMENT=CONGESTION_CONTROL_RBS_OBS:10
MaxLength=65
Viewing the list of events:

RNCSM01>h emom
emom [uetr|gpeh|ctr|all] [<event-filter>]
Display list of events available for each type of event-based scanner. ...<cut>...
PM
Commands
RNCSM01> emom uetr
The node's MOM version is: G_1_4_COMPLETE. Using following event files:
- /var/opt/ericsson/amos/jarxml/event/EVENT_RNC_UETR_E_1_0.txt
- /var/opt/ericsson/amos/jarxml/event/EVENT_RNC_CTR_E_1_0.txt
- /var/opt/ericsson/amos/jarxml/event/EVENT_RNC_GPEH_G_1_0.txt
UETR EVENTS
MEASUREMENT 5 MEASUREMENT_DOWNLINK_TRANSPORT_CHANNEL_BLER
MEASUREMENT_MAXIMUM_UE_TX_POWER
MEASUREMENT_TRANSMITTED_CODE_POWER
MEASUREMENT_UE_TRANSMITTED_POWER
MEASUREMENT_UPLINK_SIR
Measurement
pget
Based Counter
It can be used to read instantaneous counter values. Use the corba CM service,
such as "get". Works on most OMs except RNC MO (UtranCell).

RNCSM01>h pget
pget/lpget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all]

RNCSM01> pget atmport=ms-27-1

090317-15:58:14 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12176
===================== =========================================================
M.O. Attribute value
===================== =========================================================
AtmPort=MS-27-1 ========= ======= pmReceivedAtmCells 596521682
AtmPort=MS-27-1 pmSecondsWithUnexp 1197343
AtmPort=MS-27-1 pmTransmittedAtmCells 1684375003
===================== =========================================================
Total: 1 MOs
To read PM counter increments, use "PDIFF"
Measurement Based Counter
RNCSM01> pdfiff os155 pmmsses
090317-16:00:30 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12176
Logging to file: /home/U1310656/moshell_logfiles/logs_moshell/tempfiles/20090317-
150544_12148/boLog12176
Log close: /home/U1310656/moshell_logfiles/logs_moshell/tempfiles/20090317-
150544_12148/boLog12176
M.O. Counter
DiffValue
THOT 1
NOTE 3
AMOS and MOSHELL 4
Services 5
Starting AMOS and MOSHELL 7
Leaving AMOS 8
Concepts 10
AMOS Supported Shortcuts 10
Pipes 11
Regular expressions 12
Examples: 14
Managed Object Model 15
CPP MOM: 15
MO Tree and Naming Convention. 16
Measurement Based Counter
Local Distinguish Name (LDN) 16
Relative Distinguish Name(RDN) 17
Full Distinguish Name (FDN) 18
Service layer 19
ipdatabase 21
Features 22
The O&M user can access the MOs through several services: 22
MO Attributes (attribute status) 23
Actions of MOs 24
Navigating MOM from Amos 29
Navigating the MOM from Amos 30
cr 48
acl/lacl 52
u+/u- 55
al/alt 56
run 58
MOBATCH 61
Examples: 65
pget 75
Reboots 105
Log Management 110
Checking reboot information 111
Reading individual counter values from ROP files
RNCSM01>h pmx

- pmx[hfdn] [<mofilter>|<mogroup>] [<counter-filter>] [-l

<PMfiles-directory>] [-m <minushours>] [-p <plushours>] [-s
<startdate>[.<starttime>]] [-e <enddate>[.<endtime>]] [-a|- d|-
h] [| <unix-command>]

To display counter values, extracted from XML files. This

command calls the utilities
pmExtract/pmXtab/pmDiff.

Important: Only counters that are defined in an active scanner are

saved in a ROP file.
 PM Commands
Example: obtain the number of missed calls (dropped) during the last two hours
“pmx[hfdn]”
RNCSM01> pmxh utrancell=amrb01a pmNoNormalRabReleaseSpeech -m 2

080805-14:55:17 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12837

gzip1600.1.xml.gz/home/U
-dc /home/U1310656/moshell_logfiles/logs_moshel hell/pmfiles/10.108.240.8/pm_data/A20080805.1545-
/logs_moshell/pmfiles/10.108.24_0.8/pm_data/A20080805.1600-1615.1.xml.gz /pmfi_les/10.108.240.8/pm_data/A200808_05.1615-
6/moshell_log 1630.1.xml.gz
1600.1.xml.gz/home/U1310656/
/home/U1310656/moshe m_oshell_logfile_s /
o files/logs_mo shelogs
/home/U1310656/moshe o ff ii
it ogs_moshe _
en/10.108.240.8/
pm__data
/A20080805.1630-1645.1.xm
/home/U1310656/moshe
/home/U1310656/moshe
o
o
ff ii
is/ ogs_moshe
it ogs_moshe
pp mfi mfi mfi mfi pm__data
en/10.108.240.8/
. /A20080805.1645-1700.1.xm
pm__data .
/A20080805.1700-1715.1.xm
/home/U1310656/moshe o is/ ogs_moshe .
en/10.108.240.8/_ . _ pm__data
pm__data
/A20080805.1715-1730.1.xm
/home/U1310656/moshe o it ogs_moshe mfiles/10.108.240.8/
en/10.108.240.8/ /A20080805.173 0-1745.1.xm l l;$ . .
/home/U1310656/ / is/ utrancell=amrb01a" "pmnonormalrabreleasespeech"
moshe
// . mExtract
. it - -v g g" z z
_
/home/U1310656/moshe /pmXtab oris/ -cols ctr -fmt txt -m |
it
is/
Report from 2008-08-05 15:45 UTC to 2008-08-05 17:44 UTC
|

Date: 2008-08-05
time object pmNoNormalRabReleaseSpeech
15:45 UtranCell=AMRB01A 4
16:00 UtranCell=AMRB01A 2
16:15 UtranCell=AMRB01A 1
16:30 UtranCell=AMRB01A 3
16:45 UtranCell=AMRB01A 3
17:00 UtranCell=AMRB01A 4
17:15 UtranCell=AMRB01A 2
17:30 UtranCell=AMRB01A 3
Produce PM KPI reports, based on counter values in statistics ROP files and formulas in CPI
documentation.
Example:
 PM Commands
USMSNE18> pmr

“pmx[hfdn]”
gzip -dc /home/U1310656/moshell_logfiles/logs_moshell/pmfiles/10.107.245.49/pm_data/A20080805.1730-
1745.1.xml.gz/home/U1310656/moshell_logfiles/logs_moshell/pmfiles/10.107.245.49/pm_data/A20080805.1745-
1800.1.xml.gz
"^(WeightedAverage | UserBuffers|pmSumNumHsPdschCodesAdded|pmSumOfHsScchUsedPwr|pmTarget HsRate|
pmTransmittedCarrierPower|pmTransmittedCarrierPowerNonHs|pmUsedCqi)$"
1) Carrier Average Rssi and Transmitted Power
2) Downlink TXB RadioLink Setup Success Rate
3) Uplink TXB RadioLink Setup Success Rate
4) HSPA Throughput
5) HSDPA Congestion
6) HSDPA Measurements HsDschResources
7) HsDschResources AckNack
8) HSDPA Measurements IubDataStreams
9) HSDPA Test 1
10) HSDPA Test 2
Enter the report number followed by a piping command if postprocessing required.
Eg "1" (no piping) or "3 | sort +2n". Type "m" to view the menu, type "x" to exit.
VmI go CAmi~A.

Selecting option 4
1) Carrier Average Rssi and Transmitted Power
2) Donlink TXB RadioLink Setup Success Rate
3) Uplink TXB RadioLink Setup Success Rate
4) HSPA Throughput
5) HSDPA Congestion
6) HSDPA Measurements HsDschResources
7) HsDschResources AckNack
 PM Commands
“pmx[hfdn]”
8) HSDPA Measurements IubDataStreams
9) HSDPA Test 1
10) HSDPA Test 2
Enter the report number followed by a piping command if postprocessing required.
Eg "1" (no piping) or "3 | sort +2n". Type "m" to view the menu, type "x" to exit.
Your Choice: 4
gzip -dc /home/U1310656/moshell_logfiles/logs_moshell/tempfiles/20080805-154459_1908/pmrbuffer1908.gz | grep
-v ";$" |/home/U1310656/moshell/./pmXtab -fdef
/home/U1310656/moshell/./commonjars/pm/FORMULA_RBS_J_5_0.txt -x
"^(PSEulEfficiency|PSHsAvgTputPerCell|PSHsAvgTputPerUser|PSHsEfficiency)$" -i
"PSEulEfficiency|PSHsAvgTputPerCell|PSHsAvgTputPerUser|PSHsEfficiency" -m "(Sector=\w,Carrier=\w)" -a -p
6.1 -fmt txt
4) HSPA Throughput
Report from 2008-08-05 17:30 UTC to 2008-08-05 18:29 UTC
Start Time: 2008-08-05 17:30:00 End Time: 2008-08-05 18:15:00
object PSEulEfficiency PSHsAvgTputPerCell PSHsAvgTputPerUser
PSHsEfficiency
Sector=1,Carrier=1 N/A 1205.9 1015.1
97.3
Sector=2,Carrier=1 N/A 1482.9
985.6 98.9
Sector=3,Carrier=1 N/A 730.8 688.2
98.6
Enter the report number followed by a piping command if postprocessing required.
Eg "1" (no piping) or "3 | sort +2n". Type "m" to view the menu, type "x" to exit.
Your Choice:

It is possible to select a period of time for which you want the report: Example: Generate the report for the last
4 hours.
USMSNE18> pmr -m 4

080805-15:48:36 10.107.245.49 7.0q RBS_NODE_MODEL_J_5_17 stopfile=/tmp/1965

........................get /c/pm_data/A20080805.1430-1445:1.xml.gz /home/U1310656/moshell_logfiles/logs_moshell/pmfiles/10.107.245.49/pm_data/A20080805.1430 1445.1.xml.gz... OK "ManagedElement" "^(

1) Carrier Average Rssi and Transmitted Power

2) Downlink TXB RadioLink Setup Success Rate

 PM Commands
“pmx[hfdn]”
3) Uplink TXB RadioLink Setup Success Rate

4) HSPA Throughput

5) HSDPA Congestion

6) HSDPA Measurements HsDschResources

7) HsDschResources AckNack

8) HSDPA Measurements IubDataStreams

9) HSDPA Test 1

10) HSDPA Test 2

Enter the report number followed by a piping command if postprocessing required.

Eg "1" (no piping) or "3 | sort +2n". Type "m" to view the menu, type "x" to exit.

Your Choice : 1

gzip -dc /home/U1310656/moshell_logfiles/logs_moshell/tempfiles/20080805-154459_1908/pmrbuffer1908.gz | grep -v ";$" | /home/U1310656/moshell/./pmXtab -fdef

/home/U1310656/moshell/./commonjars/pm/FORMULA_RBS_J_5_0.txt -cols time -h -x "^(AvgRssi|AvgTxPwr)$" -i "AvgRssi|AvgTxPwr" -m "(Sector=\w+,Carrier= \w+)" -p 6.1 -fmt txt

1) Carrier Average Rssi and Transmitted Power

Report from 2008-08-05 14:30 UTC to 2008-08-05 18:29 UTC

Date: 2008-08-05
PM “pst”
Commands
pst [<scan-filter>|<scan-proxy>] [<scan-state>]

List all PM scanners and their status

RNCSM01> pst

090210-14:13:38 10.108.240.8 7.1d RNC_NODE_MODEL_G_5_30 stopfile=/tmp/315

PROXY SCANNER-NAME STATE

43 PREDEF.PRIMARY.STATS ACTIVE

87 PREDEF.SECONDARY.STATS ACTIVE

651 DEFAULT10000.UETR ACTIVE

660 DEFAULT10009.UETR SUSPENDED

661 DEFAULT10010.UETR ACTIVE

662 DEFAULT10011.UETR ACTIVE

663 DEFAULT10012.UETR SUSPENDED

664 DEFAULT10013.UETR ACTIVE

665 DEFAULT10014.UETR SUSPENDED

666 DEFAULT10015.UETR SUSPENDED

667 DEFAULT20000.CTR SUSPENDED

668 DEFAULT20001.CTR SUSPENDED

669 DEFAULT30000.GPEH SUSPENDED

670 DEFAULT30001.GPEH SUSPENDED

687 DEFAULT30018.GPEH SUSPENDED

688 DEFAULT30019.GPEH SUSPENDED

689 DEFAULT30020.GPEH SUSPENDED

PM
Commands
pst . act --> List only the active Scanners.

RNCSM01> pst . act

090210-14:17:34 10.108.240.8 7.1d RNC_NODE_MODEL_G_5_30 stopfile=/tmp/315

PROXY SCANNER-NAME STATE

======================================= =========================================
43 PREDEF.PRIMARY.STATS ACTIVE
87 PREDEF.SECONDARY.STATS ACTIVE
651 DEFAULT10000.UETR ACTIVE
654 DEFAULT10003.UETR ACTIVE
656 DEFAULT10005.UETR ACTIVE
657 DEFAULT10006.UETR ACTIVE
659 DEFAULT10008.UETR ACTIVE
661 DEFAULT10010.UETR ACTIVE
662 DEFAULT10011.UETR ACTIVE
664 DEFAULT10013.UETR ACTIVE
697 USERDEF.RNC_InterCell_Counters.Profile=SP_ID_119575282d740bb3355f8433cab49.Continuous=Y.STATS ACTIVE
699 USERDEF.All_RNC_Counters.Profile=SP_ID_11952f37c693cb1ababcd941c96ee.Continuous=Y.STATS ACTIVE

>>> Total: 12 Scanners

PM
Commands pcr[cfd]/lpcr[cfd] <scannerName> <moclass-filter>|<moinstance-filter>|<mo- group>|
<counter-file> [<counter-filter>] [<granularity>]

Create a Statistics Scanner.

RNCSM01> pcrc RLSUCC utrancell pmRlAddSuccessBestCell

090210-15:18:30 10.108.240.8 7.1d RNC_NODE_MODEL_G_5_30 stopfile=/tmp/315

>>> scannerId:703

RNCSM01> RLSUCC pgets

090210-16:26:51 10.108.240.8 7.1d RNC_NODE_MODEL_G_5_30 stopfile=/tmp/315

703 USERDEF.RLSUCC.STATS ACTIVE 900 6

UtranRelation 6 pmRlAddSuccessBestCellCsConvers

pmRlAddSuccessBestCellPacketHigh pmRlAddSuccessBestCellPacketLow pmRlAddSuccessBestCellSpeech pmRlAddSuccessBestCellStandAlone pmRlAddSuccessBestCellStream

>>> Total: 1 Scanners

pbl <scan-filter>|<scan-proxy>

Suspend a Scanner

RNCSM01> pbl RLSUCC

Suspend following scanners?

703 USERDEF.RLSUCC.STATS ACTIVE

PM
Are you sure [y/n]? and

Commands
703 USERDEF.RLSUCC.STATS

>>> Total: 1 Scanners

>>> Donate.

RNCSM01> RLSUCC pgets

703 USERDEF.RLSUCC.STATS SUSPENDED 900 6

UtranRelation 6 pmRlAddSuccessBestCellCsConvers

pmRlAddSuccessBestCellPacketHigh pmRlAddSuccessBestCellPacketLow pmRlAddSuccessBestCellSpeech

pmRlAddSuccessBestCellStandAlone pmRlAddSuccessBestCellStream

>>> Total: 1 Scanners

THIS COMMAND IS NOT AVAILABLE IN

AMOS
PM
Commands
pdeb <scan-filter>|<scan-proxy>

Resume scanner.
RNCSM01> pdeb 703
Resume following scanners?

703 USERDEF.RLSUCC.STATS SUSPENDED

Are you sure [y/n]? AND

703 USERDEF.RLSUCC.STATS >>> Donate.

>>> Total: 1 Scanners

RNCSM01> pages 703

703 USERDEF.RLSUCC.STATS ACTIVE 900 6

UtranRelation 6 pmRlAddSuccessBestCellCsConvers

pmRlAddSuccessBestCellPacketHigh pmRlAddSuccessBestCellPacketLow pmRlAddSuccessBestCellSpeech

pmRlAddSuccessBestCellStandAlone pmRlAddSuccessBestCellStream

>>> Total: 1 Scanners

PM
Commands
pdel <scan-filter>|<scan-proxy>

Delete a Scanner

RNCSM01> RLSUCC pdel

090210-17:10:30 10.108.240.8 7.1d RNC_NODE_MODEL_G_5_30 stopfile=/tmp/315 Delete following scanners?

703 USERDEF.RLSUCC.STATS ACTIVE

Are you sure [y/n]? and

703 USERDEF.RLSUCC.STATS >>> Donate.

>>> Total: 1 Scanners

RNCSM01> RLSUCC pgets

090210-17:10:42 10.108.240.8 7.1d RNC_NODE_MODEL_G_5_30 stopfile=/tmp/315

>>> Total: 0 Scanners

pset[d]
PM
Commands
Set the content of a scanner based on events (RNC/RBS/LTE only)
RNCSM01> pset PREDEF.30023.GPEH handover SL

692 DEFAULT30023.GPEH >>> Donate.

RNCSM01> pgets PREDEF.30023.GPEH

5===============================================================================

692 DEFAULT30023.GPEH SUSPENDED 5

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO04A

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO04B

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO04C

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO03C

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO03B

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO03A

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO01C

CELL ManagedElement=1,RncFunction=1,UtranCell=ASLO01B

RRC 2 RRC_HANDOVER_FROM_UTRAN_COMMAND

RRC_HANDOVER_FROM_UTRAN_FAILURE

GPEH_INTERNAL 3 INTERNAL_SOFT_HANDOVER_REPORT_RECEPTION

INTERNAL_SOFT_HANDOVER_EVALUATION

INTERNAL_SOFT_HANDOVER_EXECUTION

>>> Total: 1 Scanners

THIS COMMAND IS NOT AVAILABLE IN AMOS

Operating
Amos/Moshell
HW/SW
Configuration
HW/SW Overview Command: “inv”
inv command, shows the complete HW/SW inventory:

inv[hlxpbctrgf] [<Filter>] [<stateFilter>]

RNCSM01>inv

SMN APN BOARDTYPE M SWALLOCATION ST PRODUCTNUMBER REV MO

0 1 SCB SCB 1 ROJ1192108/2 R6F Subrack=MS,Slot=1, PlugInUnit=1,

0 4 YOUR B YOUR B 1 ROJ1192104/3 R4E Subrack=MS,Slot=4, PlugInUnit=1
0 5 YOUR B YOUR B 1 ROJ1192104/3 R4E Subrack=MS,Slot=5, PlugInUnit=1
Example: RBS

SMN APN BOARDTYPE SWALLOCATION ST PRODUCTNUMBER REV MO

0 1 CBU1 Main_CBU 1 ROJ1192209/1 R4B/A Subrack=1,Slot=1, PlugInUnit=1

0 2 ET-M4 RBS_ETM4 1 ROJ1192102/22 R1B Subrack=1,Slot=2,PlugInUnit=1
0 7 RAX13 RBS_RAXB 1 ROJ1192187/4 R1E Subrack=1,Slot=7, PlugInUnit=1(128 CE)
0 8 RAX13 RBS_RAXB 1 ROJ1192187/4 R1E Subrack=1,Slot=8, PlugInUnit=1(128CE)
0 9 RAX13 RBS_RAXB 1 ROJ1192187/4 R1E Subrack=1,Slot=9, PlugInUnit=1(128CE)
0 11 TX6HS-04 RBS_TXB 1 ROJ1192254/4 R1E Subrack=1,Slot=11, PlugInUnit=1(384CE)
0 12 RUIF RBS_RUIFB 1 ROJ1192245/2 R2A Subrack=1,Slot=12, PlugInUnit=1

Example: view only the RNC SW application

HW/SW Overview Command: “inv”
RNCSM01> inv rnc

Example: View only HW/SW that is locked or disabled

RNCSM01> inv . 0|L

HW/SW Overview Command: “inv”
Invl
It shows us all the features, license features, and their statuses.

UrFLINE-NIUKN-I-KuE i -2110919-1/3 /14> i nv I

180702-19:26:19 0FFLINEJIURNCl_Kget_20110919_175714 17.0m RNCJNODELMODEL_L1123 stopfile=/tmp/5400

RncFeature NO featurestate keyld licensestate servicestate FA] userLabel

FAJ1211
AgpsPosition!ng 1 (ACTIVATED) CXC4030025 1 (ENABLED) 1 (OPERABLE) A-GPS Positioning for commercial services
046
AmrNbMultiMode 1 (ACTIVATED) CXC4030048 1 (ENABLED) 1 (OPERABLE) FA3121985 Conversational RAB for multi mode AMR Speech, single rate radio bearer
AmrRate5ellubLoad 0 (DEACTIVATED) CXC4030058 0 (DISABLED) 0 (INOPERABLE) FAJ12H379 AMR rate sei. based on lub load
ArpToSpiMappingDL 0 (DEACTIVATED) CXC4030061 0 (DISABLED) 0 (INOPERABLE) FAJ1211382 H5PA QoS scheduling priority based on ARP

ArpToSpiMappingUL 0 (DEACTIVATED) CXC4030060 0 (DISABLED) 0 (INOPERABLE) FAJ12H382 HSPA QoS scheduling priority based on ARP
CbsReducedleBatteryConsumption 0 (DEACTIVATED) CXC4030070 0 (DISABLED) 0 (INOPERABLE) FAJ1211406 Cell Broadcast Service-EU battery consumption improvements

CellBroadcastService 0 (DEACTIVATED) CXC4030043 1 (ENABLED) 0 (INOPERABLE) FAJ1211326 Cell Broadcast Service

CellIdPositioning 1 (ACTIVATED) CXC4030024 1 (ENABLED) 1 (OPERABLE) FAJ121244 Positioning Service, Cell Accuracy
CellMocn 0 (DEACTIVATED) CXC4030033 1 (ENABLED) 0 (INOPERABLE) FAJ1211 One-PLMN-id per Frequency
DchLoad5haring 0 (DEACTIVATED) CXC4030076 0 (DISABLED) 0 (INOPERABLE) 301
FAJ1211468 Non-HSPA Interfrequency loadsharing
DlPsDchFc 0 (DEACTIVATED) CXC4O3OOO3 0 (DISABLED) 0 (INOPERABLE) FAJ121963 lub Flow Control
Dualstackub 0 (DEACTIVATED) CXC4O3OO37 0 (DISABLED) 0 (INOPERABLE) FAJ1211311 AIN & IP dual stack support in RBS

DynamicRabEstablishment 1 (ACTIVATED) CXC4030006 1 (ENABLED) 1 (OPERABLE) FAJ121845 Dynamic PS I/B RAB Establishment
EulCellEdgeCoverage 0 (DEACTIVATED) CXC4O3OO55 0 (DISABLED) 0 (INOPERABLE) FAJ12H376 Enhanced EUL Cell Edge Coverage
EulMbrQosProfiling 1 (ACTIVATED) CXC4030031 1 (ENABLED) 1 (OPERABLE) FAJ1211 HSDPA NBR for QoS profiling
091
Eul Service Indicator 0 (DEACTIVATED) CXC4030026 1 (ENABLED) 0 (INOPERABLE) FAJ1211 HSDPA & Enhanced Uplink Service Indicator
114

bo[r]/ba[swdp]/br[wd]/be[0-50]/bp
HW/SW Overview Command: “inv”
Manages groups of cards that can be used to execute COLI commands on multiple cards.
RNCSM02>bo

00 M BoardType Devs SwAllocation 01 M BoardType Devs SwAllocation 02 M BoardType Devs SwAllocation

00 SCB3 SCB 00 SCB3 SCB 00 SCB3 SCB

01 SCB3 SCB 01 SCB3 SCB 01 SCB3 SCB

02 SXB3 SXB 02 ET-MF4 ETMF4 02 ET-MF4 ETMF4

03 SXB3 SXB

04 YOUR B YOUR B

05 YOUR B YOUR B

06 ET-MF4 ETMF4 06 9 SPB21 CDDDD SPB_TYPE_B 06 11 SPB21 CDDDD SPB_TYPE_B

07 ET-MFG ETMFG 07 9 SPB21 CDDDD SPB_TYPE_B 07 11 SPB21 CDDDD SPB_TYPE_B

08 GPB53 GPB_SCCP AND 08 2 SPB21 CDDDD SPB_TYPE_B 08 5 SPB21 CDDDD SPB_TYPE_B

_ YOU
GPB_SCCP AND
09 GPB53 09 2 SPB21 CDDDD SPB_TYPE_B 09 5 SPB21 CDDDD SPB_TYPE_B
_ YOU
GPB_Central_E _ITU 10 3 SPB21 CDDDD
10 GPB53 b 10 6 SPB21 CDDDD SPB_TYPE
1 SPB_TYPE_
11 GPB53 GPB_Central_E _AND YOU
1
OFFLINE_WIURNC1_KGET_20110919_175714> bp
180702-19:22:15 OFFLINE_WIURNC1_Kget_20110919_175714 17.0m RNC_NODE_MODEL_L_1_123 stopfile=/tmp/5400

Board-Group Nr of Boards

aal2ap 15

aal2cpsrc 13

aal2ncc 11

--- _B
HW/SW Overview Command: “inv”
aal2nccadm 2

aal2rh 11

OFFLINE_WIURNC1_KGET_20110919_175714> pr aal2ap

180702-19:23:37 OFFLINE_WIURNC1_Kget_20110919_175714 17.0m RNC_NODE_MODEL_L_1_123 stopfile=/tmp/5400

MO Proxy

1903 SwManagement=1,ReliableProgramUniter=ans_aal2ap_12_c2

1927 SwManagement=1,ReliableProgramUniter=ans_aal2ap_12_MS-8-0

1950 SwManagement=1,ReliableProgramUniter=ans_aal2ap_12_MS-6-0

2097 SwManagement=1,ReliableProgramUniter=ans_aal2ap_12_MS-15-0

2098 SwManagement=1,ReliableProgramUniter=ans_aal2ap_12_MS-11-0

2280 SwManagement=1,ReliableProgramUniter=ans_aal2ap_12_ES-1-11-0

2348 S

cab[slxradgtme] [ | <unix cmds>]

Viewing miscellaneous COLI prints related to hw, sw, reboots, leds, cpu load, errors, disk/ram usage
Options:
• cab: print MP/BP HW information and LED status, MP temperature and coreMgr status
• cabt: same as the cabin, but without the temperature
• cabx: same as cab plus, led and hw info for XP boards (p. ex: TMA, MCPA, Fans, etc.)
• cabl: same as cab but more MP/BP processor load
• cabs: same as cab list of programs running on all MP/BP
• cabr: print all MP/BP resets. Abnormal reboots are displayed in red. caba: print only an abnormal MP/BP reset.
HW/SW Overview Command: “inv”
• cabd: print disk usage. Discs that exceed a certain limit will appear in color. The limit can be defined in the cabview file
• cabg: print MP/BP HW errors (e.g. bad disk, bad RAM, etc.).
• cabm: print MP/BP RAM usage.
• fits: print MP/BP added T&E tracking conditions
HW/SW Overview Command: “cab”
USMSNE18> cab
SMN APN BOARD GREEN YELLOW RED PRODUCT NR REV DATE SERIAL NR TEMP COREMGR

0 1 CBU1 ON 16HZ OFF RED 119 2209/1 R5E 20071107 TU8G015363 +46C Active*

0 3 RAX ON 16HZ OFF RED 119 2187/14 R1C 20081014 TU8G527420

0 4 RAX13 ON 16HZ OFF RED 119 2187/4 R1E 20080128TM15032794

0 5 RAX13 ON 16HZ OFF RED 119 2187/4 R1E 20080128TM15032789

0 6 RAX13 ON 16HZ OFF RED 119 2187/4 R1E 20071108 TU8G016168

0 8 TX6HS-06 ON 16HZ OFF RED 119 2254/6 R1D 20070929 AE55726938

0 9 OBIF ON 16HZ OFF RED 119 2238/23 R1D 20071123 TB39509344

USMSNE18> cable

SMN APN BOARD GREEN YELLOW RED PRODUCT NR REV DATE SERIAL NR TEMP COREMGR

0 1 CBU1 ON 16HZ OFF RED 119 2209/1 R5E 20071107 TU8G015363 +46C Active*

0 3 RAX ON 16HZ OFF RED 119 2187/14 R1C 20081014 TU8G527420

0 4 RAX13 ON 16HZ OFF RED 119 2187/4 R1E 20080128 TM15032794

0 5 RAX13 ON 16HZ OFF RED 119 2187/4 R1E 20080128 TM15032789

0 6 RAX13 ON 16HZ OFF RED 119 2187/4 R1E 20071108 TU8G016168

0 8 TX6HS-06 ON 16HZ OFF RED 119 2254/6 R1D 20070929 AE55726938

0 9 OBIF ON 16HZ OFF RED 119 2238/23 R1D 20071123 TB39509344

Print SW information.
RNCSM01> lhsh 001400 pglist
$lhsh 001400 pglist
Program Information:
Handle: 1
Status: run
Resident : True
Name: CXC1320787_R50HX02 (SystemManage)
Argv:
Program Information:
Handle: 2
Status: run
Resident : True
Name: CXC1320742_R50HC03 (spas_connect)
Argv:
Program Information: ...<cut>...
Handle: 14
Status: run
Resident : True
Name : CXC1329858_R4J09 (RncLmModOm)
Argv:
$
RNCSM01> lhsh 001400 listloaded
Print Disk Information.
RNCSM01> hdinfo

090317-16:07:00 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12176 $ hdinfo

Hard Disk parameters:

Size in MB: 2079

Sector size: 512
No. of cyl.: 4029
No of heads: 16
Sectors/Track: 63
No of sectors: 4061232
HD PIO mode: 4
Model: SMART CF
Serial number: 2007071200EA3C1C0000
Firmware rev: 20060811
Configuration version (CV).
Management of configuration version (CV).

• Cvls: List of CVs

• Cvmk: make local CV
Example: cvmk CVname id comment
• Cvms: make CV remotely
Example: cvms CVname id comment
• Cvset: set a startable CV
Example: cvset CVname
• Cvrm: delete
Example: cvrm CVname
RNCSM01> ftree /d/configuration/cv

090317-16:08:14 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12176 /d/configuration/cv/

Configuration files
drwxrwxrwx 512 30 Jan 2009 17:22:31 /d/configuration/cv/USMMRBI8/
- r--r--r-- 341 30 Jan 2009 17:22:22 /d/configuration/cv/USMMRBI8/ipnetworkconfig.xml
- r--r--r-- 353 30 Jan 2009 17:22:22 /d/configuration/cv/USMMRBI8/nodeinformation.xml
- r--r--r-- 71264 30 Jan 2009 17:22:23 /d/configuration/cv/USMMRBI8/ARMAMENT
- r--r--r-- 40 30 Jan 2009 17:22:24 /d/configuration/cv/USMMRBI8/LLP.LMID
- r--r--r-- 75 30 Jan 2009 17:22:24 /d/configuration/cv/USMMRBI8/attribute
- rw-rw-rw- 1616763 30 Jan 2009 17:22:30 /d/configuration/cv/USMMRBI8/db.dat
- r--r--r-- 273 30 Jan 2009 17:22:31 /d/configuration/cv/USMMRBI8/md5checksums
- r--r--r-- 3 30 Jan 2009 17:22:31 /d/configuration/cv/USMMRBI8/ok
RNCSM01> get configurationversion=1
090317-16:10:08 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12176

3590 SwManagement=1,ConfigurationVersion=1

ConfigurationVersionId 1
actionResult Struct{6}
> >> 1.actionId = 161702691
> >> 2.time = Date: 2009-01-27, Time: 16:18:02.109
> >> 3.invokedAction = 3 (PUT_TO_FTP_SERVER)
> >> 4.mainResult = 0 (EXECUTED)
> >> 5.configurationVersionName = RNCSM01_08-11-2008
Configuration files
> >> 6.pathToDetailedInformation =
additionalActionResultData t[1] =
> >> Struct[0] has 2 members:
> >> 1.information = 20 (CV_BACKUP_NAME)
> >> 2.additionalInformation = RNCSM01_RNCSM01_08-11-2008.zip
autoCreatedCVIsTurnedOn true
corruptedUpgradePackages t[0] =
currentDetailedActivity 0 (IDLE)
currentLoadedConfigurationVersion Au_CXP9012014_R10CJ_090215_0401
currentMainActivity 0 (IDLE)
currentUpgradePackage UpgradePackage=CXP9012014_R10CJ
executingCv Au_CXP9012014_R10CJ_090317_0402
CV
handling
RNCSM01> acl configuration

090317-16:12:27 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12176

Proxy M.O. action Nr of Params

============================== ===============================================
========= cancelRestore 0
ConfigurationVersion=1
changeRestoreConfirmationDeadline 1
3590 ConfigurationVersion=1
3590 ConfigurationVersion=1 confirmRestore 0
3590 ConfigurationVersion=1 create 5
3590 ConfigurationVersion=1 delete 1
3590 ConfigurationVersion=1 forcedRestore 2
3590 ConfigurationVersion=1 getFromFtpServer 4
3590 ConfigurationVersion=1 putToFtpServer 6
3590 ConfigurationVersion=1 removeFromRollbackList 1
3590 ConfigurationVersion=1 restore 2
3590 ConfigurationVersion=1 setFirstRollbackList 1
3590 ConfigurationVersion=1 setStartable 1
3590 ConfigurationVersion=1 verifyRestore 1

3590
Reboots
Do not give PlugInUnit (MP/BP) Device Program on MP
(SPM/FPGA, etc.)

Coldest Forks Forks Forks

Cold Forks Forks Forks

Refresh Forks Forks

Warm Forks Forks Forks Forks

Hot Forks
Range resets
Rank T&E logs HW test HW reset SW reload Data in CLI Data in own Domain
contain er memory
segment

Hot Preserve d No No Conditional Preserved Cleared 4

Warm Preserve d No No Conditional Cleared Cleared 1, 2, 3, 4

Refresh Preserve d No Yes on MP/BP Not Forks Cleared Cleared 1, 2

necessarily on
FPGA/DSP/etc.

Cold Cleared Limited Forks Forks Cleared Cleared 1, 2, 3

ColdWTest Cleared Forks Forks Forks Cleared Cleared 1, 2, 3

Reset commands via MO interface
RNCSM01> mom restartrank
###############################################################################
Enum Values
###############################################################################
RestartRank 0:RESTART_WARM, 1:RESTART_REFRESH, 2:RESTART_COLD,
3:RESTART_COLDWTEST

- RESTART_WARM:
- RESTART_REFRESH:
- RESTART_COLD:
- RESTART_COLDWTEST:

RNCSM01> mom restartcause

###############################################################################
Enum Values
###############################################################################
RestartCause 2:piuRestartUpgrade, 1:piuRestartError

This attribute indicates the restart cause of plugInUnit. The defined values are:
1. piuRestartError: restart because of error.
2. piuRestartUpgrade: restart because of system upgrade.
- piuRestartUpgrade: This attributes indicates that the Piu restart cause is upgrade.
- piuRestartError: This attributes indicates that the Piu restart cause is error.
Reset commands via MO interface
RNCSM01> acc 0 manualrestart

Call Action manualrestart on following MOs

===================================
0 ManagedElement=1
===================================
Are you sure [y/n]? and

MO Proxy action Nr of Params

0 ManagedElement=1 manualRestart 3
Parameter 1 of 3, restartRank (enumRef-RestartRank):
Enter one of the following integers: 0:RESTART_WARM, 1:RESTART_REFRESH, 2:RESTART_COLD, 3:RESTART_COLDWTEST: 0
Parameter 2 of 3, restartReason (enumRef-RestartReason):
Enter one of the following integers: 0:PLANNED_RECONFIGURATION,
_ 1:UNPLANNED_NODE_EXTERNAL_PROBLEMS,
2:UNPLANNED_NODE_UPGRADE_PROBLEMS,
_ _ _
3:UNPLANNED_O_AND_M_ISSUE,
_ _
4 _ :UNPLA
_T_EST ,
_
NNED_CYC _ LIC_RECOVERY,:
UNPLANNED_CA_LL_PRO_CESSING_DEGRADATION
5:UNPLANNED _LOCKE
UNPLANNED_LOWCO_VERAGE :
D_RESOUR CES, 6:UNPLANNED_COLD_W
_ _ __
IT H_HW 7: __ _
,8
0
Parameter 3 of 3, restartInfo (string): eanzmagn
>>> Return value = null

Total: 1 MOs attempted, 1 MOs actioned

Card reset using MO LDN

RNCSM01> acc ms,slot=9,pluginunit=1$ manualrestart ...<cut>...
Reset commands via MO interface
Card reset using a card group.
CSM01> acc mod1 manualrestart
...<cut>...
Log Management
lg[aevsyuoldhmircfx] [-l <logdirectory|logfile>] [-m <minustime>] [-p <plustime>] [-s
<startdate>] [-e <enddate>] [|<unixcmds>]

- Obtaining and/or processing node logs (alarm, event, availability, system, etc.) Options:

- a: analysis alarm log (CELLO_ALARM_LOG.xml)

- e: analysis event log (CELLO_EVENT_LOG.xml)
- v: Analysis Availability Log (CELLO_AVAILABILITY_LOG.xml)
- s: analysis system analysis (/c/logfiles/systemlog/xxxsyslog)
- u: parse update log (Trace.log and Trace.log_old)
- o: analysis command log (CORBA_AUDITTRAIL_LOG.xml)
- and: parse securityevent log (CELLO_SECURITYEVENT_LOG.xml).
- l: parse coli log (SHELL_AUDITTRAIL_LOG.xml).
- h: parse hili parse (CELLO_HWINVENTORY_LOG.xml).
This file must first be generated with the "hili mk" command.
- d: Displays node reboot and system downtime, based on system log and availability information.
- x – Displays active alarms on a specific date/time, based on alarm log information.
- m: merge the different logs together (eg: lgaevm will merge alarm/event/availability logs). Not compatible with option "h".
- i: reverse chronological order.
- r: Search the node logs again.
- c: Print the output in csv format (semicolon separation).
- f: Just searches the logs and stores them in a directory on the workstation .
Checking reboot information
RNCSM01> lgvsm

RNCSM01>lgd Reset times

RNCSM01> lhsh 001400 llog –l card! reset log

RNCSM01> cabr
Operating
Amos/Moshell
U
T
R
A
OSE shell access
USMSNE18> lh ru went get devstat
$ lhsh 000900/port_0_dev_5 went get devstat

0009p0d5: Board: fuHw: Hw08P1, faultStatus: 0x0, temp: 30.0, sv: on, svTmaDegrad: on, comp: on

0009p0d5: Dev1: mode: {ModeAnt}, feedPow: highPow

0009p0d5: capability: {vswrAntSv | tma19Sv | ulGainConf | maxUlGain}

0009p0d5: svCtrl: 0xc500, faultStatus: 0x0000

0009p0d5: txFreq: 882800, sensitivity: 49, gainUl: 13.0, volt: 15705.1, curr: 89.1, dCycle: 0.0

0009p0d5: Dev2: mode: {ModeAnt}, feedPow: noPow

0009p0d5: capability: {resAntSv | tma19Sv | ulGainConf | maxUlGain}

0009p0d5: svCtrl: 0x0100, faultStatus: 0x0000

0009p0d5: txFreq: 0, sensitivity: 0, gainUl: 13.0, volt: 0.0, curr: 14.8, dCycle: 0.0

$ lhsh 000900/port_2_dev_7 went get devstat

0009p2d7: Board: fuHw: Hw08P1, faultStatus: 0x0, temp: 29.0, sv: on, svTmaDegrad: on, comp: on

0009p2d7: Dev1: mode: {ModeAnt}, feedPow: highPow

0009p2d7: capability: {vswrAntSv | tma19Sv | ulGainConf | maxUlGain}

0009p2d7: svCtrl: 0xc500, faultStatus: 0x0000

0009p2d7: txFreq: 882800, sensitivity: 49, gainUl: 13.0, volt: 15785.9, curr: 81.8, dCycle: 0.0

0009p2d7: Dev2: mode: {ModeAnt}, feedPow: noPow

0009p2d7: capability: {resAntSv | tma19Sv | ulGainConf | maxUlGain}

0009p2d7: svCtrl: 0x0100, faultStatus: 0x0000

0009p2d7: txFreq: 0, sensitivity: 0, gainUl: 13.0, volt: 0.0, curr: 0.0, dCycle: 0.0
$
OSE shell access
Reading the VSWR of each of the sectors:

USMSNE18> lh ru went get vswr

090212-16:16:18 10.107.245.49 7.1d RBS_NODE_MODEL_J_5_17

stopfile=/tmp/12123 $ lhsh 000900/port_0_dev_5 went get vswr 0009p0d5:
vswr: 20.8[dB] $ lhsh 000900/port_1_dev_6 went get vswr 0009p1d6: vswr:
20.3[dB] $ lhsh 000900/port_2 _dev_7 went get vswr 0009p2d7: vswr: 20.6[dB]
$
Use in User Context
RNC10> hour
uer [-m|-i|-n] [<mod>|<imsiFilter>|<maxUEs>] [<attribute-filter>|all]
This command prints and parses UE context data for the active UEs on the RNC. The
following COLI commands are used: ueregprint (in MP core) and printUeCtxt (in the MP
module). No RRT commands are used.
Examples:
- --> print UeContext data for all UEs in the node
- --> print UeContext data for 25 UEs only (randomly selected across the node and
>> uer proportionately spread across all the modules)
>> uer -n 25 - --> print UeContext data for all UEs whose IMSI match 0001.
- --> print UeContext data for all UEs in module 8.

>> uer -i 0001

>> uer -m 8
Use in User Context
RNC10> uer
Printing all active UeContexts. Up to 124 EUs will be printed.

IMSI MOD CTXT SRNC CommCh RL1 RL2 DCdev CoreNetId UERC UERC_LABEL

1 301001700020002 130 301 9:1027 30:1090 37:1109 0020sp2 C 3 64kbps CS data, fixed rate
1 301001720000004 153 301 18:1052 25:1073 0019sp2 C 2 Speech
1 301001800000004 185 301 5:1014 33:1099 0020sp2 C 2 Speech
8 301001821110000 1768 301 28:1083 21:1061 0022sp2 C 2 Speech

======== ===============
Total % userLabel
UeRc
======== ===============
= 6 5.2 Standalone RRC on DCH
2 54 47 Speech
3 8 7 64kbps CS data, fixed rate
4 18 15.7 RACH/FACH Packet

======== ===============
= Mod1 Mod8 userLabel

UeRc
======== ===============
= 2 4 Standalone RRC on DCH
2 33 21 Speech
3 5 3 64kbps CS data, fixed rate
Use in User Context
Maximum number of RADIOLINKS per call.
RNCSM01> get 161 maxact

M.O. Attribute value

Handover=1 maxActiveSet 3

Total: 1 MOs
Use in User Context
Printing UeContexts whose image matches 724051104120193 only. Up
to 1 EU will be printed.
RNCSM01> uer -i 724051104120193 UECAP

090317-16:50:35 10.108.240.8 7.0q RNC_NODE_MODEL_G_5_30 stopfile=/tmp/12176

Printing activate UeContexts whose imsis match 724051104120193 only.

MOD IMSI/TMSI ATTRIBUTES

10 724051104120193 ueCapability.maxSimultTrChDl=8 ueCapability.supportForTurboCodingUl=1

ueCapability.supportForTurboCodingDl=1
ueCapability.maxTransmTranspBlocksUl=32 ueCapability.maxReceivedTranspBlocksDl=32
ueCapability.maxTfcInTfcsUl=64 ueCapability.maxTfcInTfcsDl=128 ueCapability.maxReceivedBitsDl=8960
ueCapability.maxTransmBitsUl=8960 ueCapability.maxReceivedTurboCodedBitsDl=8960
ueCapability.maxTransmTurboCodedBitsUl=8960 ueCapability.maxReceivedPhysChBitsDl=9600
ueCapability.maxTransmDpdchBitsPer10msUl=9600 ueCapability.agpsCapabilityValidIndic=1
ueCapability.agpsCapability=3 ueCapability.hsPhysicalLayerCategory=8 ueCapability.maxRlcWindowSize=2047
ueCapability.hsAndEulCapabilityInfo=2 ueCapability.eulPhysicalLayerCategory=0
RNCSM01>h diff

diff/ldiff

2) Syntax 2: diff/ldiff <moGroup>|<moFilter>|<proxy>|<modumpFile>|<modumpDir>

[<baselineFile>|<modumpFile2>|default] [<outputDir>]
Use in User Context
To compare an MO dump with a parameter reference file or with another MO dump.
From a Unix shell run:
If it is a single node:
moshell <ipaddress> 'lt all ; diff. ‘
If there are multiple nodes:
mobatch <sitefile> 'lt all ; diff. ‘
To use other Baseline files:
moshell <ipaddress> 'lt all ; diff. mybaseline.txt'
For a greater number of nodes:
mobatch <sitefile> 'lt all ; diff. mybaseline.txt'
Audit parameters
RNCSM01> lt all

RNCSM01> diff .
Getting MO data from node, please wait...
Logging to file: /home/eanzmagn/moshell_logfiles/logs_moshell/diff/rnc37/20060708/213821_18721/RNC37.log

Log close: /home/eanzmagn/moshell_logfiles/logs_moshell/diff/rnc37/20060708/213821_18721/RNC37.log

Parsing file PARAM_RNC_G_1_0.txt ..............Donate.
Parsing file /home/eanzmagn/moshell_logfiles/logs_moshell/diff/rnc37/20060708/213821_18721/RNC37.log Donate.

M. Attribute CurrentValue ReferenceValue

O.
Aal2QosProfile=ad8 profileClassA.boundOnNodeDelay 8000 10000
Aal2QosProfile=ad8 profileClassB.boundOnNodeDelay 15000 20000
ChannelSwitching=1 downswitchTimerSp 60 2
ChannelSwitching=1 inactivityTimer 120 30

UtranCell=cell3711,Hsdsch=1 deltaAck2
UtranCell=cell3711,Hsdsch=1 deltaCqi2

Saved result in csv format: /home/eanzmagn/moshell_logfiles/logs_moshell/diff/rnc37/20060708/213821_18721/RNC37.csv ($diffcsvfile)

Created command file to correct differences: /home/eanzmagn/moshell_logfiles/logs_moshell/diff/rnc37/20060708/213821_18721/RNC37.cmd
($diffcmdfile)

RNCSM01> l cat $diffcsvfile

Comparing RNC37 (ip=172.31.98.137, momversion= RNC_NODE_MODEL_G_5_14 _COMPLETE) with
baseline_rnc_p5.txt on 060708-215630
Audit parameters
MO;Attribute;CurrentValue;ReferenceValue
Aal2QosProfile=ad8;profileClassA.boundOnNodeDelay;8000;10000

RNCSM01> l cat $diffcmdfile

#Command file for RNC37 (ip=172.31.98.137, momversion=RNC_NODE_MODEL_G_5_14_COMPLETE)
#reference file: baseline_rnc_p5.txt
#Comparison done on 060708-215630
lt all
gs+
confb+
lset Aal2QosProfile=ad8$ profileClassA boundOnNodeDelay=10000
lset Aal2QosProfile=ad8$ profileClassB boundOnNodeDelay=20000
lset ChannelSwitching=1$ downswitchTimerSp 2
lset ChannelSwitching=1$ inactivityTimer 30
End.