Moshell Users Guide User

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 159 [warning: Documents this large are best viewed by clicking the View PDF Link!]

Informational
USER GUIDE 1(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
MoShell 18.0m User Guide
This document presents an overview of the functionality included in MoShell, command line syntax, revision history and other
important information.
It is important that all engineers working with MoShell read this document before using the tool as it contains important operational
information.
Contents
1 Introduction 5
1.1 Contact ........................................................... 5
1.2 MO concept ......................................................... 6
1.3 O&M services and protocols ................................................ 6
1.4 MO Tree and MO Naming Conventions .......................................... 7
1.4.1 LDN - Local Distinguished Name ......................................... 7
1.4.2 RDN - Relative Distinguished Name ........................................ 7
1.4.3 FDN - Full Distinguished Name .......................................... 8
1.5 MOM - Managed Object Model .............................................. 8
1.6 Moshell Functionality .................................................... 8
1.6.1 Alarm Service .................................................... 8
1.6.2 OSE shell ...................................................... 8
1.6.3 Configuration Service ................................................ 9
1.6.4 Performance Management Service ........................................ 9
1.6.5 Log service ..................................................... 9
1.6.6 File transfer ..................................................... 9
2 Installation and user settings 10
2.1 Installation for Unix (Solaris/Linux) ............................................. 10
2.2 Installation for Windows (using Cygwin) .......................................... 10
2.3 Moshell directory structure ................................................. 11
2.4 Starting an moshell session ................................................ 12
2.4.1 Starting up Moshell ................................................. 12
2.4.2 Loading the MO Tree ................................................ 13
2.4.3 Performing Actions on Loaded MO Stubs ..................................... 13
2.5 User-specific settings .................................................... 13
2.5.1 File properties .................................................... 14
2.6 Settings related to telnet/ftp/ssh/sftp communication ................................... 14
2.7 CORBA settings ....................................................... 15
2.8 Ports used by moshell ................................................... 15
2.9 Running moshell across secure tunnels (RSG) ...................................... 16
3 Command syntax, including Regular Expressions 16
3.1 How MOs are Identified ................................................... 16
3.1.1 RDN - Relative Distinguished Name ........................................ 16
3.1.2 LDN - Local Distinguised Name .......................................... 16
3.1.3 FDN - Full Distinguished Name .......................................... 16
3.2 How to address the MOs in MO-related commands ................................... 17
3.3 Regular Expressions .................................................... 18
3.4 How to specify attribute values in set/cr/acc commands ................................. 20
3.5 Moshell command line ................................................... 20
3.6 Piping ............................................................ 21
4 Command descriptions 21
4.1 Basic MO commands .................................................... 21
4.1.1 mom[abcdfloprtuxsi] [<moclass/struct/enum>] [<attribute/action>] [<attr-type>] [<attr-flags>] [<description>] 21
4.1.2 lt/clt/ltc[1-9] <motype-filter>|root|all [<attribute==value> AND/OR <attribute==value>] ............. 23
4.1.3 lc/lcc[1-9] <moGroup>|<moFilter>|<proxy(s)>|all ................................. 23
4.1.4 ld[c] <ldn> ...................................................... 24
4.1.5 lu/llu <moGroup>|<moFilter>|<proxy(s)> ..................................... 24
4.1.6 pr[s][m]/lpr[s][m] [<moGroup>|<moFilter>|<proxy(s)>] [<mimName>] ...................... 24
4.1.7 ma[i]/lma[i] <moGroup> <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>] [<value-filter>] ....... 25
4.1.8 mr[i]/lmr[i] <moGroup> <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>] [<value-filter>] ....... 25
4.1.9 mp .......................................................... 26
4.1.10 get[m][i]/lget[m][i] [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>] ........ 26
1
Informational
USER GUIDE 2(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.1.11 hget[c][m][i]/lhget[c][m][i] <moGroup>|<moFilter>|<proxy(s)> [<attribute-filter>] [<value1-filter>] [<value2-
filter>] [<value3-filter>] etc... ............................................ 27
4.1.12 kget[m]/lkget[m] [<moGroup>|<moFilter>|<proxy(s)>] [<attribute-filter>] [<attribute-type>] [<attribute-flag>]
[<attribute-description>] .............................................. 28
4.1.13 fro/lfro[m] <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>|all] [<value-filter>] ............. 28
4.1.14 sql/select <command> [ | <unix-cmds>] ...................................... 29
4.1.15 st/lst <moGroup>|<moFilter>|<proxy(s)>|all [<state-filter>] ............................ 29
4.1.16 prod <moGroup>|<moFilter> [<productdata-filter>] ................................ 29
4.1.17 lk/llk <moGroup>|<moFilter>|<proxy(s)> ..................................... 29
4.1.18 lko/llko <moGroup>|<moFilter>|<proxy(s)> .................................... 30
4.1.19 set[m][c][1][i]/lset[m][c][1][i] <moGroup>|<moFilter>|<proxy(s)> <attribute> [<value>] ............. 30
4.1.20 eset[c][1]/leset[c][1] <moGroup>|<moFilter>|<proxy(s)> <attribute-filter> [<value>] .............. 31
4.1.21 rset/lrset <moGroup>|<moFilter>|<proxy(s)> <attribute> [<value>] ....................... 31
4.1.22 bl[s]/lbl[s] <moGroup>|<moFilter>|<proxy(s)> ................................... 31
4.1.23 deb/ldeb <moGroup>|<moFilter>|<proxy(s)> ................................... 32
4.1.24 acl/lacl <moGroup>|<moFilter>|<proxy(s)>|all [<action-filter>] .......................... 32
4.1.25 acc[e][n]/lacc[e][n] <moGroup>|<moFilter>|<proxy(s)>|all <action> ....................... 32
4.1.26 cr[e][n] <ldn> .................................................... 33
4.1.27 del[b]/ldel[b] <moGroup>|<moFilter>|<proxy(s)> ................................. 34
4.1.28 rdel/lrdel <moGroup>|<moFilter>|<proxy(s)> ................................... 34
4.1.29 gm[c][d]/lgm[c][d] <moGroup>|<moFilter>|<proxy(s)> .............................. 35
4.1.30 sc[g][w][d] [<parameterlist>] ............................................ 36
4.1.31 safe+/safe-/safe? .................................................. 36
4.1.32 s+/s++/s-/s? ..................................................... 37
4.1.33 u+[s]/u-/u? [<file>] ................................................. 37
4.1.34 run[x][1][1p][1r] [-l <lineNr>] <command file> [<var1>] [<var2>] ... ........................ 39
4.1.35 trun[is1cr] <moScript>|<http://ipaddress/script> ................................. 39
4.1.36 Ctrl-Z; touch /tmp/xxxx; fg (abort MO command) ................................. 42
4.1.37 pol[b][c][d][h][i][k][m][p][s][r][u][w][y] [-m <mo>] [<interval>] [<waitTime>] [<checkTime>] ........... 42
4.1.38 re[i] .......................................................... 43
4.1.39 getmom [<momversion>] .............................................. 43
4.1.40 parsemom [<momFile>] .............................................. 44
4.1.41 flt/fltc <motype-filter> ................................................ 44
4.1.42 fget[i]/lfget[i] <moGroup>|<moFilter>|<proxy(s)>|all [<attribute>] ........................ 44
4.1.43 eget/leget <moGroup>|<moFilter>|<proxy(s)>|all [<attribute>] .......................... 44
4.1.44 sget/lsget/skget/lskget/shget/lshget <moGroup>|<moFilter>|<proxy(s)>|all ................... 44
4.1.45 fset[i]/lfset[i] <moGroup>|<moFilter>|<proxy(s)>|all <attribute> [<value>] [<attribute-type>] .......... 44
4.1.46 facc/lfacc <moGroup>|<moFilter>|<proxy(s)>|all <action> [<param1>] [<param2>] .............. 45
4.1.47 fdel/lfdel <moGroup>|<moFilter>|<proxy(s)> ................................... 46
4.2 Other MO commands .................................................... 46
4.2.1 cvls/cvmk/cvms/cvset/cvrm[u]/cvrbrm/cvcu/cvget[f][u][d]/cvput/cvls1/cvre/cvfa/cvfd .............. 46
4.2.2 inv[hlxbpctrgfa] [<Filter>] [<stateFilter>] ...................................... 47
4.2.3 cab[adefghlmrstxc] [ | <unix-cmds> ] ....................................... 51
4.2.4 sdi[eacr] ....................................................... 53
4.2.5 stc[p][r] [<Filter>] [<stateFilter>] .......................................... 54
4.2.6 std[ar] [<filter>] ................................................... 55
4.2.7 stv[b][r] [<Filter>] [<stateFilter>] .......................................... 58
4.2.8 stt[r] [<Filter>] [<stateFilter>] ............................................ 59
4.2.9 ste[gr] [<Filter>] [<stateFilter>] ........................................... 59
4.2.10 sti[bcfopr] [<Filter>] [<stateFilter>] ......................................... 62
4.2.11 sts .......................................................... 67
4.2.12 str .......................................................... 68
4.2.13 dcg[meiasrfkx] [-m <rophours>] [-d <logdays>] [-b <boards|boardgroup>|all] [-k <nrdumps>] [-f <mofilter>]
[<logdir>] ...................................................... 70
4.2.14 hc[iuzd][v] [-r|-x <numbers>] [<hclogfile>|<hclogdir>|<hcreportdir>] [<hclogfile2>|<hclogdir2>] ........ 71
4.2.15 diff[a][d][m][o][x][i]/ldiff[a][d][m][o][x][i] ....................................... 72
4.2.16 lkr[a] ......................................................... 75
4.2.17 resub <IubLink> [<VplTp>|<Subrack>] [<VplTp>] ................................. 77
4.2.18 ir[cdpsomt] [<IubLink>] [<CM>] [<period>] .................................... 77
4.2.19 rinp[c][m] </path/to/rinpm.json> .......................................... 79
4.2.20 tg[r][c][d] ....................................................... 80
4.2.21 ueregprint/uer[d][t][i][s][p][v] [-m <mod>|-i <imsi>|-u <ueref>|-n <maxUes>|-c <utrancell>|-r <iublink>]
[<attribute-filter>[=<value>]|all] ........................................... 82
4.2.22 ced[h][p][s][g][r] [-m <module(s)>|-c <utrancell>|-r <iublink>|-s <rsite>] [ | <unix-cmds>] ............ 85
4.2.23 al[atkcg][u] [-a|-u <alarm-id>] [ | <unix-cmds>] .................................. 87
2
Informational
USER GUIDE 3(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.2.24 - lg[abcdefghijklmnopqrstuvwxyz012345] [-l <input-directory|logfile|zipfile>] [-m <minustime>] [-p <plustime>]
[-s <startdate>] [-e <enddate>] [-g <boardgroup>] [-n <nodefilter>] [-x <XBlog-filter|ESIlog-filter> ] [-b <xb> ]
[-d <nrdumps>] [<destination-directory>] [|<unix-cmds>] ............................. 88
4.3 Other commands ...................................................... 93
4.3.1 uv [<string>|<var>=value] ............................................. 93
4.3.2 pv [<string>] ..................................................... 94
4.3.3 !/l <unix-command> ................................................. 94
4.3.4 l+[m][m][s][o]/l-/l? [<logfile>] ............................................ 94
4.3.5 dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>] ........................ 95
4.3.6 dbd[p] [<cvname>|<dbdat-file>|<cvzip-file>] [<cvname>|<dbdat-file>|<cvzip-file>] ............... 101
4.3.7 dbcv[r] ........................................................ 101
4.3.8 <ose/coli command> [|<unix-cmds>] ....................................... 102
4.3.9 coli .......................................................... 104
4.3.10 comcli ........................................................ 104
4.3.11 ecli .......................................................... 104
4.3.12 esci ......................................................... 104
4.3.13 netconf[g] [<commandfile>] ............................................ 104
4.3.14 c+/c1/c2/c-/c?/c0 .................................................. 104
4.3.15 <linux/rcs-coli/comcli command> [|<unix-cmds>] ................................. 105
4.3.16 mcl[d] [<moClass-filter>] [<command-filter>] ................................... 106
4.3.17 mcc/lmcc <moGroup>|<moFilter>|<proxy(s)> <comcli commands(s)> [|<unix-cmds>] ............. 106
4.3.18 bo[ar]/ba[swdpmu]/br[wdm]/be[0-50]/bp ...................................... 106
4.3.19 lh[z] <boardGroup>|<moGroup> <OSE-command>|run <commandfile> [ | <unix-cmds>] ........... 109
4.3.20 mon[?][d][u][f][s][t][k][a][-] [<board(s)|<boardGroup(s)>] [</path/to/logfile>] ................... 109
4.3.21 sql+/sql-/sql? [<heap>] ............................................... 111
4.3.22 pgu[c][f][r] [-p <board1,board2,...>] /path/to/newLM [<cvcomment>] ...................... 111
4.3.23 procload/proctemp [|<unix-cmds>] ......................................... 112
4.3.24 proglist/progkill [-e] [<string>] [|<unix-cmds>] ................................... 113
4.3.25 fte <te-command> [<trace-groups>|all] [<string>] [|<unix-cmds>] ........................ 113
4.3.26 goxb[acib] [-p <advpw>] <commands> [|<unix-cmds>] .............................. 113
4.3.27 ftree[f][d][1] [<lnh>/][<directory>] [| <unix-cmds>] ................................. 114
4.3.28 ftget[1][c]/ftput[1][c]/ftdel[1][a]/ftrun [<options>] <source>[/*] [<destination>] .................. 115
4.3.29 htget <remotefile> [<localfile/localdir>] ...................................... 116
4.3.30 edit <remotefile> .................................................. 116
4.3.31 fclean[f|ff|a|d|e] [<lnh>/][<directory>] [-f <filename-filter>] ............................ 117
4.3.32 hi [<commandFilter>], !<commandNr> ...................................... 118
4.3.33 time[t] <command>|<logfile> ............................................ 118
4.3.34 pipe <command> | <unix-command> ....................................... 118
4.3.35 lmid[c][h]/upid[om] <pattern>|refresh ....................................... 118
4.3.36 p/w/pw/b ....................................................... 119
4.3.37 prox[+-] ....................................................... 119
4.3.38 col .......................................................... 119
4.3.39 ul ........................................................... 119
4.3.40 conf[bld][+-] ..................................................... 120
4.3.41 gs[+-]/gsg[+-] .................................................... 120
4.3.42 ip2d <ip-address> .................................................. 120
4.3.43 d2ip/h2ip <number> ................................................ 120
4.3.44 h2d/d2h <number> ................................................. 121
4.3.45 h2b/b2h <number> ................................................. 121
4.3.46 d2b/b2d <number> ................................................. 121
4.3.47 rb2ip [<iublink>] ................................................... 121
4.3.48 encpw <password> ................................................. 122
4.3.49 mos2ro <moshell.zip> ............................................... 122
4.3.50 gpg <file> ...................................................... 122
4.3.51 wait <delay>|<newtime> .............................................. 122
4.3.52 wf[o][a][t] <file> ................................................... 123
4.3.53 return ........................................................ 123
4.3.54 print ......................................................... 124
4.3.55 alias/unalias <alias> <command> ......................................... 124
4.3.56 lf[c] <file> ...................................................... 124
4.3.57 bg[g]/bgs/bgw [<commands>|<id(s)>|all] [<maxtime>] .............................. 124
4.3.58 - smd[slcr] [-m <days>] [-s <size>] [-f <filter>] [-o a|s|n] [-u <user>|all] [-d <directory>] [-n <max>] . . . . . . 125
4.3.59 pe[c][l][k] [<polling interval>|<pid>] [<trigger>] [<action script>] [<number of iterations>] ........... 126
4.3.60 q/by/exit/quit [<exitcode>] ............................................. 127
4.4 PM commands ....................................................... 127
4.4.1 pmom[acdpo] [<moclass>] [<counter>] [<data-type>] [<flags>] [<description>] ................ 127
3
Informational
USER GUIDE 4(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.4.2 kmom[d] [<area>] [<kpiname>] [<MOclass>] [<formula>] [<kpidescription>] .................. 127
4.4.3 pget/lpget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>] ............ 128
4.4.4 spget/lspget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>] ........... 128
4.4.5 hpget[c][m]/lhpget[c][m] <moGroup>|<moFilter>|<proxy(s)> [<attribute-filter>] [<value1-filter>] [<value2-
filter>] [<value3-filter>] etc... ............................................ 128
4.4.6 pdiff/lpdiff [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>] ............ 128
4.4.7 hpdiff[m]/lhpdiff[m] [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value1-filter>] [<value2-
filter>] [<value3-filter>] ............................................... 128
4.4.8 pmx[hfdnsckwlb3zeity] [<mofilter>|<mogroup>] [<counter-filter>|<kpi(s)>] [-l <zipfile>|<directory>] [-w <web-
directory>] [-m <minushours>] [-p <plushours>] [-s <startdate>[.<starttime>]] [-e <enddate>[.<endtime>]]
[-a|-d|-h] [-o <outputFormat>] [-tz <hrs>] [-f <formulafile>] [-j <precision>] [-mo <regexp>] [| <unix-cmds>] . 129
4.4.9 pmr[agfkwop3z] [-g <mofilter>|<mogroup>] [-z <mogroup>] [-r <report(s)>] [-l <zipfile>|<directory>] [-w <web-
directory>] [-i <iubCellModule-file>] [-f <formulafile>] [-c <configfile>] [-m <minushours>] [-p <plushours>]
[-s <startdate>[.<starttime>]] [-e <enddate>[.<endtime>]] [-o <outputFormat>] [-t <thresholdfile>] [-tz <hrs>]
[|<unix-cmds>] ................................................... 131
4.4.10 pme[fd][cgurv] [<pm_logdir>] [-b <boardgroup>] [-f ] [-m <minushours>] [-p <plushours>] [-s <start-
date>[.<starttime>]] [-e <enddate>[.<endtime>]] ................................. 134
4.4.11 pst [<scan-filter>|<scan-proxy>] [<scan-state>] .................................. 135
4.4.12 pgets[m][n][r] [<scan-filter>|<scan-proxy>] [<contents-filter>] .......................... 135
4.4.13 pcr[pcfpdaz]/lpcr[pcfpdaz] <ScannerName|JobName> <moclass-filter>|<moinstance-filter>|<mo-
group>|<counter-file> [<counter-filter>] [<granularity>] .............................. 136
4.4.14 pcrk[f][v][d] [<kpidefinitionfile>] [<granularity>] .................................. 137
4.4.15 pbl <scan-filter>|<scan-proxy> ........................................... 138
4.4.16 pdeb <scan-filter>|<scan-proxy> .......................................... 138
4.4.17 pdel <scan-filter>|<scan-proxy> .......................................... 138
4.4.18 emom [uetr|gpeh|ctr|all] [<event-filter>] ...................................... 138
4.4.19 pset[d] ........................................................ 138
5 Lazy 140
5.1 Software Upgrade CPP ................................................... 140
5.2 Software Upgrade ECIM/COM ............................................... 140
5.3 RNC Iub operations ..................................................... 141
5.4 Common RNC Iub Integration Problems ......................................... 141
5.5 Common RNC Iu/Iur Integration Problems ........................................ 142
6 Scripting 142
6.1 Preset Variables ....................................................... 143
6.2 Variable assignment .................................................... 144
6.3 Hashtables (arrays) ..................................................... 149
6.4 If/Else constructs ...................................................... 149
6.5 For constructs ........................................................ 150
6.6 User-defined functions ................................................... 152
6.7 Nesting for and if statements ................................................ 153
6.8 Example scripts ....................................................... 154
7 Utilities 154
7.1 Network Management Tools ................................................ 155
7.2 Parameter Auditing Tools .................................................. 155
7.3 PM Tools ........................................................... 155
7.4 Miscellaneous Tools .................................................... 156
8 Server Maintenance 156
8.1 Hanging Processes ..................................................... 156
8.2 Disk full ........................................................... 156
8.3 Run out of memory ..................................................... 156
9 Offline Mode and Multi Mode 157
9.1 Offline Mode ......................................................... 157
9.2 SQL Mode .......................................................... 158
9.3 Multi Mode .......................................................... 158
10 Revision History 159
4
Informational
USER GUIDE 5(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
1 Introduction
1.1 Contact
For bug reports, installation issues, change requests etc. please use the forum on the moshell homepage.
TR for MoShell
Put bug reports on the web page (see Section 1.1) or write them in MHWEB:
To write an MoShell TR/CR in MHWEB:
1. Product should be AMOS CXC 172 4313
2. MHO should be LMIR7-BASIC
In order to get the fastest resolution to your problem, please add the following information to your TR or bug report:
uv and pv printout
Any complete printout relevant to the fault
How to recreate the fault (you can for instance include the hi printout showing all the commands that led to the fault)
5
Informational
USER GUIDE 6(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
1.2 MO concept
****************************************
| O&M Client |
| (eg: EMAS/OE/RANOS/moshell,etc.) |
****************************************
|
|
****************************************
| CS,PM,AS,NS,IS,LS Service Layer |
****************************************
|
|
**********|******************************
*+++++++ *
*| | *
*| MAO | Management Adaption Layer*
*| | *
MO--> *| | ------------------------ *
*| FRO | *
*| | Resource Layer *
*| RO | *
*| | *
*+++++++ *
*****************************************
The O&M client can access the MOs through a number of services:
Configuration Service (CS): to read and change configuration data. Configuration data is stored in the MO attributes.
Performance Measurement (PM): to setup statistics scanners or event filters. The statistics counters are stored in MO
pm-attributes and output to an XML file every 15 minutes. The events are output into binary files every 15 minutes.
Alarm Service (AS): to retrieve the list of alarms currently active on each MO.
Notification Service (NS): to subscribe and receive notifications from the node, informing about parameter/alarm changes in
the MOs.
Inventory Service (IS): to get a list of all HW and SW defined in the node.
Log Service (LS): to save a log of certain events such as changes in the configuration, alarms raising and ceasing,
node/board restarts, jvm events, O&M security events, etc
The MO is a way of modelling resources in a CPP node. It consists of:
1. A Management Adaption Layer which is implemented in java, in the MP running the jvm (the O&M MP).
The purpose of the MAO (Management Adaptation Object) is to interface towards the various O&M services described
above.
2. A Resource Layer consisting of Facade Resource Object (FRO) and a Resource Object (RO) which are implemented in C
and run on the various boards. The RO is the actual resource modelised by the MO. The purpose of the FRO is to act as
an interface between the MAO and the RO, by handling the configuration transactions and storing configuration data for the
RO.
1.3 O&M services and protocols
The MO services described above (CS, AS, PM, IS, NS) are carried by the IIOP protocol (Internet Inter-ORB Protocol), also
called CORBA (Common Object Request Broker Architecture).
At startup, the node generates its IOR (Interoperable Object Reference) and stores it in a nameroot.ior file which can be used by
the O&M client to access the node. The IOR file contains the node’s IP address and some specifications as to how the clients
can send requests to the node.
The OSE-shell (also called COLI) can be accessed through telnet/ssh or locally, through the serial port (RS232). It gives direct
access to the operating system, the file system, and parts of the FRO/RO layer.
6
Informational
USER GUIDE 7(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Figure 1: CPP nodes have various access methods for different services. For Managed Services like CS, CORBA is used. For the
command shell, ssh or telnet is used. To collect PM XML ROP files FTP is used.
1.4 MO Tree and MO Naming Conventions
1.4.1 LDN - Local Distinguished Name
The MOs are organised in a hierarchical structure.
Each MO instance is uniquely identified in the node by its Local Distinguished Name (LDN).
The highest MO in a node, the so called root MO is the ManagedElement. This MO represents the whole node.
There is only one instance of the ManagedElement MO in the node and it is referenced by the LDN: ManagedElement=1
The string at the left of the equal sign is called the MO class (or MO type) and the string at the right of the equal sign is called the
MO identity. In the case of the root MO, the MO class is ManagedElement and the identity is 1.
If an MO is located further down in the MO tree, the LDN must contain the MO classes and identities of all the parents of that MO,
in a sequence going from the root MO down to the MO in question. See example below:
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,Program=DbmFpgaLoader
From this example, we can see that the ManagedElement has a child called Equipment=1 which has a child called Subrack=MS
(representing the main subrack of the node), which has a child called Slot=19 (representing the slot in position 19), which has a
child called PlugInUnit=1 (representing the board located in that slot), which has a child called Program=DbmFpgaLoader
(representing one of the programs loaded in that board).
The LDN of the lowest MO (the one called Program=DbmFpgaLoader) contains the address of all successive parents of that
MO all the way up to the ManagedElement.
1.4.2 RDN - Relative Distinguished Name
The string located at the far right of an LDN, just after the last comma, is called a Relative Distinguished Name (RDN).
It is a unique way of addressing a MO instance in relation to its closest parent.
This means that there is only one MO instance with the RDN Program=DbmFpgaLoader under the parent MO
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1. However, there could be another MO instance with
the same RDN under a different parent MO. For instance, there could be an MO instance with the RDN
Program=DbmFpgaLoader under the parent MO ManagedElement=1,Equipment=1,Subrack=MS,Slot=23,PlugInUnit=1.
Therefore the RDN is a relative way of addressing an MO instance.
7
Informational
USER GUIDE 8(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
1.4.3 FDN - Full Distinguished Name
When a node is connected to a Network Management System such as OSS-RC, there is a need to uniquely address each MO
within the whole network. The Full Distinguished Name (FDN) adds a network element prefix (MIB prefix) in front of the LDN of
each MO instance in order to specify which node this MO belongs to. See the figure below, summing up the FDN/LDN/RDN
concept:
FDN (Full Distinguished Name)
<------------------------------------------------------------............................................................>
LDN (Local Distinguished Name)
<----MIB Prefix-----------------------><--------------................................................................>
MoClass Identity
<-----> <---> RDN (Relative Distinguished Name)
<--------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1 RDN
<-------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1 RDN
<----->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS RDN
<---------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS,Slot=19 RDN
<------------------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1,Program=DbmFpgaLoader
1.5 MOM - Managed Object Model
Each MO class contains a number of attributes which are used to store configuration data or performance measurement data.
Each MO class can also support a number of defined actions. These represent certain operations which can be performed by the
MO. A typical example is the action restart which will cause the MO to restart the resource it is responsible for (e.g. a board, a
program, etc.).
The Managed Object Model (MOM) is a reference document describing all the MO Classes that can exist in a node, together with
their attributes and actions.
The format of the MOM can be UML, XML, HTML, or MS-Word.
The XML version of the MOM is usually stored on the web server of the node at the address:
http://<ipaddress>/cello/oe/xml/<filename>.xml
The MOMs for each SW release is also stored in HTML format on http://cpistore.ericsson.se
1.6 Moshell Functionality
MoShell is a text-based O&M client providing access to the following services:
Configuration service (CS)
Alarm service (AS)
Performance management service (PM)
Log service (LS)
OSE shell (COLI)
File transfer (ftp/http)
Access to all services is supported both in secure mode (secure Corba, ssh, sftp) and unsecure mode (unsecure corba, telnet,
ftp).
1.6.1 Alarm Service
The list of active alarms can be retrieved with the commands al (to show an overview) or ala (the same as al, with more
details).
1.6.2 OSE shell
Any OSE shell command can be typed at the moshell prompt and the output can be piped through external utilities (which exist in
your workstate/server) if required.
Examples:
8
Informational
USER GUIDE 9(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
te log read
te log read | grep ERROR
Only the $prompt is supported. For instance, it is not possible to type lhsh 000100 and expect a prompt to that board.
The workaround is to type the command on the same line as the link handler shell, eg lhsh 000100 te log read or
put a semicolon after the lhsh xxxx, eg lhsh 001400 ; te log read ; vii ; llog . Type h ose at the
moshell prompt for more info.
Other commands which require a shell such as sqlc have their own implementation. See Section 4.3.8.
Any Loco commands should be written as loco ts\nloco ... You can achieve this automatically using aliases, see
Section 4.3.55.
1.6.3 Configuration Service
Moshell supports the following 6 operations from the configuration service:
1. GetChildren to load all or parts of the MO-tree
2. GetAttribute to read the attributes of an MO
3. CallAction to perform an action on an MO
4. SetAttribute to set (change) the value of an MO attribute
5. CreateMO to create a new MO in the node
6. DeleteMO to delete an MO from the node
1.6.4 Performance Management Service
Moshell supports the following operations from the performance management service:
List Scanners and Event Filters
Create Scanner
Stop Scanner
Resume Scanner
Delete Scanner
Set Event Filter
1.6.5 Log service
Moshell supports fetching and parsing of the following logs:
availability log
system log
event log
alarm log
command log
O&M security event log
COLI log
Hardware inventory log
JVM events log (upgrade log)
1.6.6 File transfer
Moshell can download/upload files and directories to/from the node, using http, ftp or sftp.
9
Informational
USER GUIDE 10(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
2 Installation and user settings
2.1 Installation for Unix (Solaris/Linux)
Copy the moshell installation package moshellxxx.zip to your home directory /home/youruser or to the temp directory /tmp.
Very important: do not store the zip file inside the moshell folder otherwise the installation will be corrupted.
Then go to the folder containing the zipfile (cd <folder>) and run the following commands:
unzip -o moshellxxx.zip
bash moshell_install
When prompted to enter the directory where you want to install moshell, it is recommended to specify your HOME directory ( ~).
If you have executed moshell_install from your home directory then you can press the enter key and the current directory is
selected.
If a previous moshell installation already exists, it is recommended to install in the same directory as the old one. This way, all
your custom files (jar/xml files, site files, etc.) get copied across to the new revision and the old revision gets moved to a different
location so you can still access it if needed.
When prompted to enter the path to java, make sure to use Oracle Java. Other Java distributions such as OpenSDK are not
supported by moshell.
Note: In the case of AMOS installation use option -a, ie: bash moshell_install -a (must be run as root on OSS
masterserver).
Note: for linux 64-bit, the 32-bit libc library is required, the package name is libc6-i386 or glibc.i686 or ia32-libs.
(Other packages which may be needed for certain commands are python and expect.)
Running moshell for the first time:
If you have set the PATH variable correctly in your ~/.bashrc file, you should be able to run moshell from any directory. E.g:
moshell <ipaddress>
If this is the first time moshell is installed in this location, then it will download a number of jar files from the node. No progress
indicator will be shown so just be patient as it will take a few minutes. Progress can be seen by doing "ls -l" in the moshell/jarxml
directory. For more information about user settings etc, check the user guide.
If the Moshell execution fails on linux with the following error:
moshell/commonjars/lib/lin64/filefuncs.so: cannot restore segment prot after reloc: Permission denied
Then try to run the following commands, while logged in as root:
chcon -t texrel_shlib_t ./commonjars/lib/lin64/libz.so.1
chcon -t texrel_shlib_t ./commonjars/lib/lin64/filefuncs.so
If Moshell is unable to connect to the node on port 22, try executing the program moshell/commonjars/ssh manually. If it fails with
the following error:
moshell/commonjars/ssh: error while loading shared libraries: cannot restore segment prot after reloc: Permission denied
Then try running the following command, while logged in as root:
chcon -t texrel_shlib_t commonjars/ssh
2.2 Installation for Windows (using Cygwin)
When running on Windows, Moshell uses a unix emulator known as Cygwin.
Go directly to step 10, MoShell Installation, if you have already installed and configured Cygwin previously.
1. Download and execute the file http://www.cygwin.com/setup-x86.exe
2. Choose "Install from internet", then click Next.
3. Root Directory C:\cygwin (It is not recommended to choose a different directory, especially if it contains spaces).
4. Choose a Download Site. For instance http://sourceware.mirror.tds.net is known to work well but probably others work fine
too.
10
Informational
USER GUIDE 11(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
5. In the "Select Packages" View menu, choose "Category", then add the following packages:
under Archive select zip and unzip
under Database, select postgresql
optional: under Editors select vim (if you want to be able to edit files with vi)
under Graphics, select gnuplot
under Libs, select libglib2.0_0
under Net select curl,inetutils,openssh,openssl
under Perl select perl,perl-XML-Simple, and perl-IO-Tty
under Python select python2
under Tcl select expect
6. Click Next, install will start. Wait for installation to complete.
7. Copy the file moshell/examples/cygwin_install/cygwin_install.txt to C:/Cygwin (also available from
http://newtran01.au.ao.ericsson.se/moshell/cygwin_install.txt). .
8. Click on Start –> Run.
In the "Run" window, type: cmd , then press <enter>.
A DOS window opens. At the DOS prompt, execute the following commands:
c:
cd cygwin
bin\perl.exe cygwin_install.txt
This will create the following files: c:/cygwin/etc/profile,c:/cygwin/cygwin.bat,
c:/cygwin/home/youruserid/.bashrc,c:/cygwin/home/youruserid/.minttyrc,
c:/cygwin/home/youruserid/.inputrc.
If those files already exist, they are automatically moved to the folder c:/cygwin/tmp/installbackup.
9. Open a new cygwin terminal window. The window should be black with white text and the prompt should like this: [~]$
If not, then go through all the steps again and make sure you haven’t missed out anything.
More info about Cygwin installation issues can be found at: http://cygwin.com/faq/faq0.html
Uninstall instructions for cygwin can be found at
http://cygwin.com/faq/faq.setup.html#faq.setup.uninstall-all
10. Moshell installation. Follows these steps if you already have a working Cygwin environment.
Copy the moshell installation package moshellxxx.zip to your home directory c:/cygwin/home/youruserid
Open the cygwin shell and run:
unzip -o moshellxxx.zip
bash moshell_install
When prompted to enter the directory where you want to install moshell, it is recommended to specify your HOME directory
( ~).
If you have executed moshell_install from your home directory then you can press the enter key and the current
directory is selected.
If a previous moshell installation already exists, it is recommended to install in the same directory as the old one. This way,
all your custom files (jar/xml files, site files, etc.) get copied across to the new revision and the old revision gets moved to a
different location so you can still access it if needed.
When prompted to enter the path to Java, just type java .
11. Running moshell for the first time
If you have set the PATH variable correctly in your ~/.bashrc file, you should be able to run moshell from any directory. E.g:
moshell <ip-address>
2.3 Moshell directory structure
The moshell directory contains a number of files and subdirectories:
11
Informational
USER GUIDE 12(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
logfiles/ To store the logfiles generated by the various utililites (moshell, mobatch, swstat, etc.)
examples/ Example of input files required by the utilities (command files, site files, etc.)
cmdfiles/ Place to store your command files (to be used by mobatch, monode, telbatch, telnode, etc)
sitefiles/ Place to store your sitefiles (to be used by mobatch, telbatch, swstat, swup, etc.)
jarxml/ Place to store jar files (oms.jar and vbjorb.jar) and xml-MOM files (used by Moshell). Specific to certain nodes.
commonjars/ Place to store jar files common to all nodes
moshell The file used to startup moshell. Contains some customizable variable settings.
mobatch Run moshell commands on several nodes in parallel
gawk Script interpreter used by the various utilities
prog.awk, funcs.awk Main code for moshell, cannot be run on its own.
moshellUserGuide.pdf Help file
rncaudit Audit and consistency check of rnc data towards cell data CDR, utranrelations CDR, baseline, uerc, etc.
swstat To view SW revisions, CV’s and delete old upgrade packages
rbsaudit Audit and consistency check of rbs data towards rbs data and baseline. Generation of mobatch corrective scripts.
swup Network SW upgrades
cvms create and set cv’s on several nodes in parallel
momdoc convert MOM from xml to html
mocmd generate moshell command file from a baseline parameter file
2.4 Starting an moshell session
This section gives a brief overview of how to get started once you have installed moshell.
2.4.1 Starting up Moshell
A Moshell session is started from the Unix shell prompt using command: moshell <node-name>|<node-address>
If connecting with node name, an entry must exist in the ipdatabase file reference the node name against an ip or dns address.
Other ways of starting moshell are described by typing moshell on its own as well as in chapter Section 9(Offline mode/multi
mode Chapter) .
Upon startup, and running the command "lt all", moshell will go through the following steps:
1. Download the node’s IOR file and store it on the workstation. The node’s IOR file is fetched from
http://nodeipaddress/cello/ior_files/nameroot.ior
2. Check the node’s MOM version The node’s MOM is fetched from http://nodeipaddress/cello/oe/xml/<filename> where
<filename> is one of the files listed in the user variable xmlmomlist. The MOM version is derived from the "mim" tag inside
the MOM file, eg: <mim name="RNC_NODE_MODEL_E" version="5" release="3"> becomes
RNC_NODE_MODEL_E_5_3. If this MOM version does not exist on the workstation (under moshell/jarxml directory),
then it is downloaded from the node and stored in that directory. If the MOM version could not be figured out (ie. moshell
could not find any MOM on the node), the MOM specified in the moshell uservariable default_mom is used.
3. Parse the MOM and generate an internal table specifying all MO classes, attributes, and actions supported by the node.
4. Initiate CORBA communication with the node by using the information contained in the IOR file.
5. Read the FDN of the Root MO
6. Ready to receive commands from the user
At this stage, it is possible to access the Alarm Service and OSE shell but the Configuration Service is limited since Moshell
doesn’t have any knowledge of what MO instances are contained in the node’s MO tree (apart from the root MO).
The following commands are of use at this stage:
h- to show the help and list of commands. Can be used with a command name after to show help about that command.
The menus are split into two (mand n) only for readability purposes.
12
Informational
USER GUIDE 13(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
2.4.2 Loading the MO Tree
Once Moshell first connects to the node it has no knowledge of the MO structure on the node (execept for the ManagedElement
MO class). In order to get attributes or call actions you first need to load the MO stubs onto your Moshell client.
The whole MO tree can be read with command lt all. The LDN of each MO of the MO tree is then allocated a "proxy" number
and stored in an internal table in Moshell memory. The internal proxy table can be printed via the command pr which will show
for each MO, the LDN and the proxy number.
When performing an operation on an MO (get, set, action, etc.), either the proxy number or the LDN can be given as argument.
In fact, by using a Regular Expression matching part of the LDN, an operation can be performed on several MOs at a time.
More information about this can be found in Section 3or by typing h syntax at the prompt.
To save memory on the workstation, it is possible to load only parts of the MO tree instead of the whole MO tree.
For instance, by typing lt pluginunit, only the LDNs of MOs whose MO class is PlugInUnit will be read.
Instead of typing the whole MO class, it is possible to type a regular expression that will match the MO class.
In this case, lt plu would be the same as lt pluginunit, since the string plu matches pluginunit
More information about this in Section 4or by typing h lt and h lc at the prompt.
2.4.3 Performing Actions on Loaded MO Stubs
To perform operations on one or several MOs which you loaded in the previous section, follow the command syntax shown on the
menu.
1. Example: To read the MO attributes of the MO with LDN
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1 you would type the following:
pr plu #then lookup the proxy identity of that MO
get <proxy> #enter the MOs proxy identity as argument to the "get" command
OR
lget ms,slot=19,pluginunit=1$
2. Example: To read the MO attributes of all MOs whose MO class is PlugInUnit
get plu #the get command will operate on all MOs whose RDN matches "plu"
More info about this in Section 3or by typing h syntax at the Moshell prompt.
Help for each command can be found in Section 4or by typing h <command-name> at the Moshell prompt.
!!! Important note for CDMA nodes !!! Most CDMA nodes do not keep a MOM on the node’s harddisk.
To force moshell to use the correct MOM, here are some workarounds:
store the correct MOM in your directory moshell/jarxml, then, after the moshell startup, use the command
parsemom <mom> to parse the correct MOM, or specify the path to this MOM in your default_mom user variable (see
Section 2.5 for info on user variables).
store the correct MOM on the node at /c/public_html/cello/oe/xml/CelloMOM.xml
check if the node has a MOM that is under a different file name than is specified in the moshell uservariable xmlmomlist.
This can be done by doing ls /c/loadmodules_norepl or ftree /c/loadmodules_norepl and search for a MOM
file (file extension .xml)
2.5 User-specific settings
There are a number of moshell configuration parameters (called user variables) which can be set either permanently or on a
session basis. These settings have a default value which is defined in the file moshell/moshell. If one or more user variables
need to be changed from the default value, it is recommended to store the new setting in one of the moshellrc files (~/.moshellrc
or moshell/jarxml/moshellrc or moshell/jarxml/moshellrc.$USER) instead of the moshell file. This way, the new setting will be
kept even after an moshell upgrade.
It is also possible to define user variables on a session basis by:
1. using the command uv [var=value] from the moshell prompt (type h uv for more info)
2. or use the -v option from the command line when starting moshell (type moshell on its own for more info)
It is possible for many users to run moshell from a central location and have their logfiles, credential files, user variables and
13
Informational
USER GUIDE 14(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
aliases stored in their own home directory. This is mainly intended for Solaris or Linux networks where many users will be able to
run moshell from a common location without having to install it in their home directory. The common location can be the vobs or
any user’s home directory, for example the administrator’s account or a common account.
The administrator can define a number of user variables and aliases and save them into the moshell/jarxml/moshellrc file.
These user variables and aliases will apply to all users and will be kept after each moshell installation. It is also possible for the
administrator to define individual moshellrc files which will be located as moshell/jarxml/moshellrc.$USER .
Each user can also define their own settings and aliases and save them into the ~/.moshellrc file in their home directory. If this
file is not present, it will be created automatically and can be modified any time.
All user variables that are defined in the file moshell/moshell can be given a new value in the moshell/jarxml/moshellrc and/or
the ~/.moshellrc and/or the moshell/jarxml/moshellrc.$USER file.
The user variables defined in moshell/jarxml/moshellrc.$USER override those defined in ~/.moshellrc which override those
defined in moshell/jarxml/moshellrc, which in turn override those defined in the file moshell/moshell.
Here is a short list of user variables, look inside the moshell file for more info on each variable:
disk_check - check if enough free disk space on the workstation: 0=no check, 1=warning only, 2=exit if not enough space
disk_limit - the minimum free disk space required by the disk check, default 1G (1 Gigabyte).
java - path to Java executable
ip_database - path to the IP database file (see example of this file in moshell/examples/mobatch_files)
secure_shell, secure_ftp, username, ip_connection_timeout, ip_inactivity_timeout - see Section 2.6 for info
corba_class, security_method, credential, sa_credential, sa_password, sls_urls, sls_username, sls_password - see
Section 2.7 for information
default_mom - path to the default MOM, to use in case no MOM is found on the node
prompt_highlight - to enable or disable the bold font of the prompt
set_window_title - to enable or disable the display of a window title
http_port - to specify the HTTP port value (e.g 80 for CPP, 8080 for simcello)
keepLmList - files that shouldn’t be deleted by the fclean command.
bldebset_confirmation, lt_confirmation - to specify if confirmation message shall be given in lt/bl/deb/set commands.
logdir - path to the logfiles directory (this one can only be changed from moshellrc or .moshellrc, not uv or -v)
a few more variables, see the moshell file for further details
Look in the moshell file for a more complete list and detailed explanation of each variable.
2.5.1 File properties
All files and subdirectories belonging to the moshell package are NON-writeable to outside users. Only the owner of the account
where moshell is installed can make modifications to the installation. The only exception is the subdirectory moshell/jarxml
which is writeable to everyone. The reason is because all users need to be able to store new xml MOM files in that directory
(since the xml MOM gets frequently updated for every new node SW release).
Note: the same jar files can be used by all users, regardless of what CPP SW is running on the node. For instance, it’s ok to use
CPP 4 jar files towards a CPP 3 node. This also the case as CPP 5.1 moves towards JacORB.
2.6 Settings related to telnet/ftp/ssh/sftp communication
The following user variables relate to telnet/ftp communication.
All settings can be either set in moshell file, in ~/.moshellrc or via the uv command in the moshell session. See Section 2.5 and
h uv for more info. Also check the moshell file for more info on each variable.
username - which username to use when logging in to the node via telnet/ftp/ssh/sftp
secure_shell - whether to use telnet or ssh for access to OSE shell
secure_ftp - whether to use ftp or sftp for file transfers.
ip_connection_timeout - timeout for the establishment of telnet/ftp/ssh/sftp connections
ip_inactivity_timeout - inactivity timeout for telnet/ftp/ssh/sftp connections
14
Informational
USER GUIDE 15(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
telnet_port/http_port/ftp_port/secure_port - to use a different port for telnet/http/ssh/sftp. Useful for connecting to
SimCello/CPPemu or running moshell over the RSG using port forwardings.
node_login - whether to login or not (no login for SimCello or backup mode)
So, in order to enable ssh/sftp instead of telnet/ftp, do one of the following:
1. Set the variables secure_shell and secure_ftp in moshell file to the value 1 (not recommended since the value will get
reset at the next moshell install/upgrade).
2. OR Add the following lines in the ~/.moshellrc or the moshell/jarxml/moshellrc file
secure_shell=1
secure_ftp=1
3. OR Run the following commands from the Moshell prompt (the setting will only be valid for the current session):
uv secure_shell=1
uv secure_ftp=1
4. OR start moshell with the option -v secure_shell=1,secure_ftp=1
See Section 2.5 to find out more about setting user variables.
Important Note regarding the ip_connection_timout: By default, this timeout is set to 45 seconds in the moshell file. Certain OSE
shell commands might not print any output for a longer period of time, eg: format,rcp, etc. To avoid having a connection
timeout when running these commands, it is advised to extend the ip_connection_timeout prior to running the command, by
doing uv ip_connection_timeout=600 (for example).
2.7 CORBA settings
To specify which corba SW and corba security settings moshell should be using, use the following values of the user variable
corba_class.
corba_class=1 : connect in secure mode with the visibroker (vbjorb) software
security_method=1 (requires java >= 1.2.2) : use a host credential host.p12, only supported for nodes running
CPP5.0 and below. The uservariable credential must be set accordingly, to point to the host.p12 file. The
host.p12 file is downloaded from the PKS server or from the node.
security_method=2 (requires java >= 1.3.1) : use a stand-alone credential sam.pbe. The sam.pbe file is
downloaded from the SLS server, its path and password must be given in the uservariables sa_credential and
sa_password.
corba_class=2 (requires java >= 1.3.1) : connect in unsecure mode with the prismtech (jacorb) SW.
corba_class=3 (requires java >= 1.4.2_05) : connect in secure mode with the jacorb SW, using a stand-alone credential
sam.pbe. The sam.pbe file is downloaded from the SLS server, its path and password must be given in the uservariables
sa_credential and sa_password.
corba_class=4 (requires java >= 1.4.2_05) : connect in secure mode with the jacorb SW, using a network-mode
credential ssucredentials.xml which is automatically downloaded from SLS server. The username and password for
SLS login must be specified in the uservariables sls_username and sls_password. The address of the SLS is read
from the node but can also be specified in the uservariable sls_urls.
corba_class=5 (requires java >= 1.4.2_05) : connect in secure mode with the jacorb SW, using an already downloaded
network-mode credential ssucredentials.xml. The path to the ssucredentials.xml file must be given in the
uservariable nm_credential.
For more information about how to set the user variables, see Section 2.5 and h uv. Also check the moshell file for more info on
each variable.
2.8 Ports used by moshell
If there is a firewall between moshell and the nodes, then the following TCP ports need to be open in the firewall:
For CPP nodes:
1. Corba:
port 56834: for unsecure corba (O&M SL1)
port 56836: for secure corba (O&M SL2 and SL3)
2. Http: 80
15
Informational
USER GUIDE 16(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
3. SSH/SFTP: 22
4. Telnet: 23 (optional)
5. Ftp: 21 (optional). If ftp is used, an additional port range needs to be open for the data connection (21 is for control only).
6. Target monitor: TCP ports 33077 to 33087 and UDP 33078-33079 . Needed in order to monitor the trace and error log with
the "mon" command.
7. Optional: for subscription to Corba CS/FM notifications, using the utility runClient.sh (-c/-a options): callback port range
53248-55295 from the node to the client. This is not needed for moshell, only for the utility runClient.sh -c/-a options.
For ECIM/COM nodes:
1. RCS nodes (MSRBSv2/TCU):
HTTPS: 443 and 8443
SSH: 830 (NETCONF), 2023 (COMCLI), 4192 (COLI)
SFTP: 22 (from Node), 2024 (to Node)
TLS: 6513 (NETCONF), 9830 (COMCLI), 9831 (COLI)
Trace streaming from Node: TCP 5342/5343 (MP traces), and UDP 33079 (BB traces)
2. Pico nodes: 22 (SFTP), 9830 (COMCLI), 830 (NETCONF)
3. Other nodes: 22 (APG43L), 2024 (BSP), 830 (PGM), ...
More info in the CPI document "Node Hardening Guidelines"
2.9 Running moshell across secure tunnels (RSG)
Please refer to instruction in the file moshell/examples/misc/RSG_tunnels_instruction.txt
3 Command syntax, including Regular Expressions
3.1 How MOs are Identified
MOs can be identified using the RDN, LDN or FDN.
3.1.1 RDN - Relative Distinguished Name
This is used to identify an MO in relation to its nearest parent in the MO tree.
The RDN contains MO Class (also called MO Type), the equal sign, and MO identity. Example:
AtmPort=MS-24-1
AtmPort is the MO Class,MS-24-1 is the identity.
3.1.2 LDN - Local Distinguised Name
This is used to uniquely identify an MO within a node.
The LDN shows the hierarchy above the MO, within the Managed Element’s MO tree. Example:
ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1
3.1.3 FDN - Full Distinguished Name
This is used to uniquely identify an MO within a network (used by RANOS/CNOSS/OSS-RC). Example:
SubNetwork=AUS,SubNetwork=H2RG_0201,MeContext=St_Leonards_Station_2065010,ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1
16
Informational
USER GUIDE 17(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
3.2 How to address the MOs in MO-related commands
The first argument in the MO-related commands is usually used to specify the MOs that should be used by the command.
There are currently six different ways to specify the MO(s):
1. all
All loaded MOs will be affected. Example:
a) get all userlabel to get attribute UserLabel on all MOs
Note: instead of all, it is also possible a regex wildcard such as .or *. This has the same effect.
2. Proxy ID(s)
All MO(s) with the given proxy id(s) will be operated upon.
To specify several MO proxies, there are two ways:
Specify each Proxy ID with a space in between. Example:
a) pr025to print the MO proxies 0, 2 and 5.
Give a range of Proxy IDs. Examples:
a) pr 4-10 prints MO proxies from 4 to 10.
b) pr 10-4 prints all MO proxies from 10 down to 4 (reverse order, useful for deleting MOs).
c) acc 10-20 restart calls the action restart on MOs with proxy 10 up to 20.
Note: proxy ranges and individual proxy Ids can be mixed on the same line.
Example: pr 0 2 3-5 8 10-12
3. Link handler (for PluginUnit and Spm MOs only!). Examples:
a) acc 001400 restart - to restart the MO Subrack=MS,Slot=14,PlugInUnit=1.
b) bl 001900/sp0.lnh - to lock the first SPM on the SPB in slot 19 with LDN:
Subrack=MS,Slot=19,PlugInUnit=1,Spu=1,Spm=1. Note that MOs start counting from 1 and the link handlers start
from 0!
4. MO Group
MO Groups are user defined groups of MOs. All MO(s) belonging to the given MO group will be operated upon.
To create a MO group, see command description for ma/lma in Section 4.1.7. MO groups can also be created with the
commands hget/lhget,lk/llk,st/lst,pdiff/lpdiff.
Note: In RNC, running the bo command will automatically create a number of MO groups containing the cc/dc/pdr device
MOs for each module.
5. Board Group
MOs (PlugInUnit or Spm) mapped onto the boards belonging to the given board group will be operated upon.
Example 1:
baw sccp sccp All boards with the swallocation matching "sccp" will go into the board group "sccp"
bl sccp All PlugInUnit or Spm MOs connected to boards of this board group will be locked
Example 2: in RNC, using the default board groups created after running the bo command:
acc mod10 restart
pr dc10
acc dc10 restart the board group dc10 is mapped onto the Spm MOs
bl dc10dev in this case we are using the MO group containing the Device MOs, see above
6. MO-Filter (regular expression)
MO(s) whose LDN/RDN match the regular expression pattern will be affected.
If the command starts with lthen the pattern will match agains the LDN.
If the command doesn’t start with l, then the pattern will match against the RDN.
If the command doesn’t start with l, and the filter contains no commas, then the pattern will match against the RDN.
17
Informational
USER GUIDE 18(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
If the command doesn’t start with l, and the filter contains commas, then the pattern will match against the LDN but will not
include the children. (Note: this particular syntax is not supported in multimode).
Examples:
a) pr ms-24-1
TransportNetwork=1,AtmPort=MS-24-1
b) lpr ms-24-1
TransportNetwork=1,AtmPort=MS-24-1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc32
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc33
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc337
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc332
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc34
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc35
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc40
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc64
c) pr ms,slot=5,plug
Equipment=1,Subrack=MS,PlugInUnit=1
d) lpr ms,slot=5,plug
Equipment=1,Subrack=MS,PlugInUnit=1
Equipment=1,Subrack=MS,PlugInUnit=1,Program=basic
Equipment=1,Subrack=MS,PlugInUnit=1,Program=nss
Equipment=1,Subrack=MS,PlugInUnit=1,Programs=spas
....
When using the MO-Filter, it is a good idea to test the pattern with pr/lpr command before issuing a get/set/acc/cr/del
command, in order to see which MOs will be matched by the pattern.
Sometimes, a second or third argument can be given, which is usually a string matching the attribute or attribute value that you
want to display.
3.3 Regular Expressions
Note: MOSHELL pattern matching is NOT case sensitive
The search string that is used in the filters is a Unix Regular Expression (like the patterns used in the grep -E command).
Therefore, special meta-characters such as . * [ ] ^$ can be used.
Short description of some meta-characters:
“. - any single character
“*” - 0 or more occurences of the previous character
[ ] - matches a character or range of characters inside the brackets
[^] - NOT matching a character or range of characters inside the brackets
| - OR
^- beginning of string
$ - end of string
! - negation
% - reverse order
Examples of using meta-characters:
a*means a or aa or aaa, etc.
.*is like a wildcard as it matches 0 or more occurences of any character
[a-z] matches all letters from a to z
[abe] matches letters a,b, and e
18
Informational
USER GUIDE 19(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
[^3] matches any character but not 3
3|5|6 matches 3 or 5 or 6
^a.*4$ matches a string beginning with a and finishing with 4, with any character in the middle
Regular expressions can also be grouped together using brackets, e.g:
cell(11|23|45) matches cell11 or cell23 or cell45
Examples of using regular expressions in the filters:
1. lpr ms-24-1.*vp2
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc34
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc35
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc40
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc64
2. lpr %ms-24-1.*vp2
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc64
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc40
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc35
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc34
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2
3. lpr !loadmodule|program
All MOs except those matching loadmodule or program will be printed
4. lpr 20.*os
Equipment=1,Subrack=1,Slot=20,PlugInUnit=1,Etm4=1,Os155PhysPathTerm=1
Equipment=1,Subrack=1,Slot=20,PlugInUnit=1,Etm4=1,Os155PhysPathTerm=2
5. pr cc[1-4]
TransportNetwork=1,AtmCrossConnection=AtmCC1
TransportNetwork=1,AtmCrossConnection=AtmCC2
TransportNetwork=1,AtmCrossConnection=AtmCC3
TransportNetwork=1,AtmCrossConnection=AtmCC4
6. pr cc[135]
TransportNetwork=1,AtmCrossConnection=AtmCC1
TransportNetwork=1,AtmCrossConnection=AtmCC3
TransportNetwork=1,AtmCrossConnection=AtmCC5
7. lpr =6.*prog.*=1
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=15
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=1
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=14
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=13
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=12
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=11
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=10
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=19
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=18
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=17
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=16
8. lpr =6.*prog.*=1$
Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=1
9. lpr ms-24-1
TransportNetwork=1,AtmPort=MS-24-1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc32
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc33
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc337
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp1,VpcTp=1,VclTp=vc332
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc34
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc35
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc40
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc64
10. lpr ms-24-1.*=vc[^3]
19
Informational
USER GUIDE 20(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc40
TransportNetwork=1,AtmPort=MS-24-1,VplTp=vp2,VpcTp=1,VclTp=vc64
3.4 How to specify attribute values in set/cr/acc commands
1. For attributes of type Struct, use the following syntax: attr1=val1,[,attr2=val2[,attr3=val3]]]...
Example:
set sid sib11 sib11repperiod=128
set mtp3bspitu sppriority prioslt=2
set mtp3bspitu sppriority prioslt=2,prioco=2
2. For attributes of type MoRef, just type the MO LDN (without ManagedElement=1). E.g.:
lset AtmPort=1221,VplTp=vp1 atmTrafficDescriptor
transportnetwork=1,atmtrafficdescriptor=C1P4500
It is also possible to skip the first parent (eg TransportNetwork,SwManagement, etc). E.g.:
cr rncfunction=1,utrancell=30451,utranrelation=30451to305212
Attribute 1 of 1, utrancellref (moRef:UtranCell): utrancell=30521
3. For attributes of type array of MoRefs, separate each element of the array with spaces. Eg:
set jvm admclasspath loadmodule=oms loadmodule=vbjorb ...
acc aal2pathdistributionunit=1 addPath
Parameter 1 of 1, aal2PathVccTpId (sequence-moRef-Aal2PathVccTp):
aal2pathvcctp=csa aal2pathvcctp=csb
4. For attributes of type array of Struct, separate each element of the array with semicolons. Eg:
set rncfunction aliasPlmnIdentities
mcc=300,mnc=23,mnclength=2;mcc=345,mnc=32,mnclength=2;mcc=208,mnc=123,mnclength=3
5. For attributes of type array of integer/long/float/string/boolean, separate each element of the array with commas or spaces.
Eg:
set antfeedercable=6 ulattenuation 10,10,10,10,10,10,10,10,10
set antfeedercable=6 ulattenuation 10 10 10 10 10 10 10 10 10
set jvm options -Xms65000k,-Dhttp.root=/c/public_html,
-Dse.ericsson.security.PropertyFileLocation=/c/java/SecurityManagement.prp
set cell=3041 ActiveOverlaidCDMAChannelList true,true,false,true
set cell=3041 ActiveOverlaidCDMAChannelList true true false true
acc managedelementdata addDhcpServerAddress
Parameter 1 of 1, ipAddressArray (sequence-string): 10.1.1.3,10.1.1.4
6. For attributes of type array of integer, it is also possible to specify ranges of values.
Eg, in the command below, the attribute will be set to 1,2,3,4,5,23,24,25,26
set IpInterface=1,DscpGroup=1 dscpValues 1-5,23-26
7. To input an empty value:
in set command, just leave the value field blank. Eg:
set 0 userlabel
set reliableprogramuniter admpassiveslot
in cr command, type null or d. This is only supported for non-mandatory (restricted) attributes, because mandatory
attributes must be given a value.
in acc command, type null. This is only supported for parameters of type MoRef or String.
3.5 Moshell command line
The command line uses the Readline library from bash. Here are some of the supported function keys:
right arrow or Ctrl-f - move forward one character
left arrow or Ctrl-b - move backward one character
up arrow - previous command in history buffer
20
Informational
USER GUIDE 21(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
down arrow - next command in history buffer
backspace - delete one character backward
Ctrl-d or <del> - delete one character forward
Ctrl-a or <home> - go to beginning of line
Ctrl-e or <end> - go to end of line
Ctrl-u - erase all characters backward
Ctrl-k - erase all characters forward
Alt-f - move forward one word
Alt-b - move backward one word
select or select + ctrl-<insert> - copy to clipboard
<insert> or shift-<insert> - paste from clipboard
Note about command history: if you type the beginning of a command and then use the up/down arrow key, you will see all
previous commands starting with this string
3.6 Piping
Some commands support piping, e.g. All OSE shell commands, lh, tg, str, etc.
This is usually indicated in the menu and the help for that command. Some examples are:
te log read | grep ERROR
lh mp te log read | grep ERROR
str | grep cell=30456
For other commands that don’t support piping (like MO commands), the workaround is to save the output to a logfile then run the
unix command on that logfile by using the lor !command. Example:
l+ #open the logfile, an arbitrary name will be given
prod loadmodule #run the command
l- #close the logfile
l sort $logfile #run unix command sort on the logfile.
l grep -i basic $logfile
Note: $logfile is automatically set by MoShell to contain the name of the latest log file created.
4 Command descriptions
Here all the commands and their syntax which are possible using Moshell are supported. Each of the OSE shell commands are
not mentioned specifically, but it is possible to run all of them through Moshell.
4.1 Basic MO commands
4.1.1 mom[abcdfloprtuxsi] [<moclass/struct/enum>] [<attribute/action>] [<attr-type>] [<attr-flags>] [<description>]
Print description of MO Classes, CM/FM Attributes, Actions, Enumerations and Structures.
Regular expressions can be used in the various filters. There are five levels of filtering, as shown in the command syntax.
Options:
a: show only the definitions relating to application MOs
b: shows the default attribute values.
c: show all the MO classes specified in the filter as well as their children/grandchildren/etc classes.
d: gives a shorter printout, without the description part.
f: shows the attribute flags (only applies when combined with options "b", "r", "l")
i: only show the EricssonOnly attributes
21
Informational
USER GUIDE 22(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
l: shows the attribute value lengths.
p: show only the definitions relating to platform MOs (CPP)
r: shows the valid attribute value range.
x: show unidirectional and bidirectional MO relationships
t: show MO containment relationships and cardinality. The command momt shows three tables: first table with all valid
LDNs, second table with parent MO(s), and third with children MO(s). The first argument can be used to show only MO
classes matching the filter. The options o, u, l (momto/momtu/momtl) can be used to show only certain specific tables:
momtl for the LDN table, momto for the parent table (MOs over), and momtu for the children table (MOs under). The option
s is used to show the systemCreated flag in the LDN table and parent table (eg: momts / momtls).
Some of the options can be combined, see examples below.
After execution of the MOM command, two scripting variables are automatically created:
$moclass_filer : contains a regular expression matching all MO classes that were printed by the command
$attrib_filter : contains a regular expression matching all attributes that were printed by the command
These variables can then be used in the "get" command to read attributes matching certain MOM conditions based on the
attribute name, data type, flag, or description text. In kget command, it is possible to specify the MOM conditions directly from the
kget command arguments.
Examples:
1. momt - View the whole MO tree
2. momt atmp - View all possible parents and children of the AtmPort MO
3. mom atmp - View a description of the AtmPort MO
4. momcd atmp - List all MO classes under the AtmPort MO
5. momc atmp - View a description of all MO classes under the AtmPort MO
6. mom vcl - View a description of the MO class VclTp
7. mom vcl . - View a description of all attributes of MO class VclTp
8. momdi . . . !readonly - List all EricssonOnly attributes that are not readOnly
9. momd . restart - List all attributes and actions matching the word restart
10. momd . . struct - List all attributes of type struct and/or all actions containing struct parameters
11. momd . . . restricted - List all attributes that have the restricted flag
12. momd utrancell . . !restricted|readonly - List all utrancell attributes that do not have the restricted or readonly
flag
13. momd . . . . license - List all MOs, attributes and actions whose description contains the word license
14. mom . . . . license - View the description of all MOs, attributes and actions whose description contains the word
license
15. momd restart . - List all struct or enumerates matching the word restart
16. mom restart . - View the description of all struct or enumerates matching the word restart
17. momd . . enumref:admst - List all attributes of type enumRef:AdmState
18. mom adminproductda . - View a description of all struct members contained in struct AdminProductData
19. momd . . sequence:moref restricted - List all attributes of type sequence:moRef who have a flag restricted
20. momb utrancell - List the default values for all attributes in the MO class UtranCell
21. mombf utrancell . . !restricted - List the default values for all UtranCell attributes that do not have the flag
restricted
22. mombr . power|pwr - List the default values and valid ranges for all attributes that match the word power or pwr
23. momx - Show the relationships between MO classes
24. momx iublink - Show the relationships to and from IubLink
25. momx iublink.*utrancell|utrancell.*iublink - Show the relationships between IubLink and UtranCell
26. momx reservedby - Show the relationships connected via reservedBy attribute
27. mom . . ^moref, then get . $attrib_filter - Print attribute values for all attributes of data type moRef
22
Informational
USER GUIDE 23(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.1.2 lt/clt/ltc[1-9] <motype-filter>|root|all [<attribute==value> AND/OR <attribute==value>]
Load MO tree (full or partial) and build proxy table.
lt stands for Load MO Types,clt stands for Conditional Load mo Types,ltc stands for Load MO Types and their Children. The
numeric option in ltc is for specifying the number of levels of children to load. Without the option, all levels of children are loaded.
This command queries the node to find out which MOs it contains and creates a table with the MO LDNs and a proxy number.
The first argument of the lt/clt/ltc command can be:
root clear the proxy table and allocate a proxy for the root MO (ManagedElement)
all clear the proxy table, then load the whole MO tree and build a proxy table with all MO instances.
all!<motype-filter> clear the proxy table, then build a proxy table with all MO’s except some MO classes.
<motype-filter> get a proxy for all MO types matching the specified pattern.
Examples:
1. lt atmpor - load all MOs of type matching the string "atmpor", this will usually be the AtmPort MOs
2. clt atmpor - conditionally load all MOs of type matching the string "atmpor". Loading only performed if no MOs of this
type are already loaded.
3. ltc equipm - load the Equipment MO and all its children (all the way down)
4. ltc1 equipm - load the Equipment MO and only one level of children
5. ltc2 transp - load the Transport MO and two level of children
6. lt ^utrancell|fach|rach|pch - load all utrancells, fach, rach, pch MOs
7. lt iub - load all iublinks
8. lt all!relation - load all MOs except the utranrelation/gsmrelation MOs.
The pattern in motype-filter is a regular expression, more information can be found with command h syntax and h pr
The argument root/all clears the proxy table, whereas lt <motype-filter> doesn’t, so the MO LDNs get appended to the
existing table.
If the same MO type is loaded several times, only the latest fetched instance is kept. Previously fetched instances of that MO type
are deleted from the internal table.
The second argument (optional) is a filter constraint for the attribute value. Example:
1. lt utrancell operationalState==0 - load proxys for all disabled cells
2. lt utrancell primaryCpichPower==270 - load proxys for all cells that have pichpower=270
3. lt all operationalState==0 OR administrativeState==0 - load proxys for all MOs in the node that have
opstate 0 or admstate 0.
4. ltc rncfunction operationalState==0 - load proxys for all MOs under RncFunction that have opstate 0.
Note: This type of search is very hard for the node if it has to search through a large number of MOs (ie several thousand).
For more information about Filter constraint, refer to Reference [?].
4.1.3 lc/lcc[1-9] <moGroup>|<moFilter>|<proxy(s)>|all
Load MO tree (full or partial) and build proxy table.
The lc command is for loading the LDNs of the children MOs lying under an MO or group of MOs. lc on its own or combined
with the numeric option "1" will only load the direct children. With the numeric options 2 to 9 it is possible to specify the number of
levels of children to be loaded. The "c" option (lcc command) is for loading all possible levels of children under the MO.
The parameters of the command are:
all clear the proxy table, then load the whole MO tree and build a proxy table with all MO instances.
<proxy(s)> - load children of one or several MO’s given their proxy id. For example:
lc 0 load the direct children of the ManagedElement MO (only one level of children)
lc2 0 load two levels of children under ManagedElement MO
lcc 0 load all levels of children of the ManagedElement MO (same as lc all or lt all).
23
Informational
USER GUIDE 24(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
lc567load children of proxys 5, 6, and 7.
<moFilter> - loads children of all MOs whose RDN match the pattern. For example:
lc3 transportnetwork=1 load three levels of children under TransportNetwork MO
lc cell=3002 loads direct children for MOs whose RDN match cell=3002
lcc ms-24-1 loads children of all MOs whose RDN match ms-24-1
The pattern in mo-filter is a regular expression, more information can be found with command h syntax and h pr.
4.1.4 ld[c] <ldn>
Load one MO instance and (optionally) the MO tree below it
ld stands for Load LDN. This command loads a proxy for an MO, given its LDN. The LDN doesn’t need to contain
ManagedElement=1, this is assumed.
The MO types are not case sensitive but the MO-ID is.
With the coption, the subtree below the MO is also loaded.
Examples:
ld transportnetwork=1,atmport=MS-6-1,vpltp=vp1,vpctp=1,vcltp=36 - load the MO instance that has this
LDN
ldc equipment=1 - load the MO with LDN "Equipment=1" as well as the MO tree below it.
4.1.5 lu/llu <moGroup>|<moFilter>|<proxy(s)>
Unload MOs from MO tree.
The purpose is to reduce the size of the proxy table by unloading unwanted MOs. This is useful on large nodes with > 50,000
MOs. Memory usage on the workstation will be reduced and MO commands will be faster. The typical case is to unload all
relation MOs in the RNC (UtranRelation and GsmRelation) which are very numerous but not used in most commands.
Example:
lt all
lu relation
4.1.6 pr[s][m]/lpr[s][m] [<moGroup>|<moFilter>|<proxy(s)>] [<mimName>]
Print MO LDNs and proxy ids for all or part of the MO tree currently loaded in moshell.
Options:
s(silent) : to print only the total number of MOs matched in each MO class.
m(mim) : to print the mimName of each MO instance. Only applicable for COM/ECIM nodes.
Examples:
pr - print all MOs
pr 0-1000 - prints the MOs with proxy id 0 to 1000
lpr subrack=ms - print all MOs whose LDN match subrack=ms. This will print the MO Subrack=MS as well as all its
children.
pr !utranrel - print all MOs except those with an RDN matching utranrel
For further information see Section 3or h syntax.
Note: The pr command is useful to test patterns used in mo-filters. For instance, some patterns will match more MOs than
expected, which will result in executing a command on some unwanted MO’s. Therefore, it is good to first try the pattern on the
pr/lpr command, then do it "for real" on a command that actually communicates with the node. The pr/lpr command also
shows the total number of MOs matching the pattern.
24
Informational
USER GUIDE 25(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.1.7 ma[i]/lma[i] <moGroup> <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>] [<value-filter>]
Add MO(s) to an MO group.
The first argument (mandatory) indicates the name of the MO-Group.
The second argument (mandatory) indicates the Proxy Id’s or MO-Filter of the MOs to match.
If no further arguments are given then the MOs whose RDN/LDN match the MO-filter (or who have the corresponding proxy) will
be put in the MO-Group.
If further arguments are given then a get or pget command is performed using the second/third(/fourth) argument of the ma/lma
command.
If option "i" was given (mai/lmai) then the command "geti" is used instead of "get".
The third argument will be a string to match the attribute and the fourth (if it’s used) will match the value.
If the attribute is of any other type than MoRef, then the MO(s) whose attribute match the fourth argument will be put in the group.
If the attribute is of type MoRef, then the MO(s) contained in the attribute is put in the group (except if there is a fourth argument).
Refer to the following examples:
ma test atmport.*24-1 - all MOs whose RDN match atmport.*24-1 are put in the group test
lma test atmport.*24-1 - all MOs whose LDN match atmport.*24-1 are put in the group test
ma test atmport operationalst 0 - all MOs whose RDN match atmport and who have operationalState matching
"0" will be put in the group test
ma test atmport physpathterm - all MOs who are referenced through the attribute physpathermId of the MOs
matching atmport will be put in the group test (since physpathermId is an attribute of type MoRef)
lma test subrack=ms,slot=10,program loadmodule - all loadmodule MOs connected to program MOs running
on slot 10 in main subrack will be put in the group test (since loadmodule is an attribute of type MoRef)
ma test atmport physpatherm slot=23 - all atmports whose physpatherm reference matches slot=23 will be put in
the group test
ma test reliableprogram admactiveslot slot=10 - all reliableprograms that are on slot 10 will be put in the
group test
ma test vcltp pmrec 0 - all vcltps with 0 pmreceivedcells are put in the group
ma test 34,58,42 - include MO instances with proxy id 34, 42, and 58 in the group
mai test sectorcarrier= noOfUsedTxAntennas ^1$ - include all sectorcarriers that have exactly one antenna
Two-step example: To put all unlocked-disabled MOs in a group in order to lock them:
ma test all operational 0
ma test1 test administ 1
bl test1
To put all cells belonging to module 3 in a group in order to lock them
ma iubmod3 iublink module =3$
ma cellmod3 iubmod3 reservedby
bl cellmod3
To put all vcltps that have 0 receivedcells and more than 0 transmitted cells in a group in order to find out which upper layers are
affected
ma faultyvcltp vcltp pmrec ^0
mr faultyvcltp vcltp pmtrans ^[^0]
lk faultyvcltp
Note: it is also possible to create MO groups with the commands hget/lhget, st/lst, lk/llk, and pdiff/lpdiff.
4.1.8 mr[i]/lmr[i] <moGroup> <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>] [<value-filter>]
Remove an MO group or remove MOs from an MO group (MOs will NOT be deleted, only the group).
Exactly the same syntax as ma described in Section 4.1.7 except that the MOs matching will be removed from the MO-Group
instead of added.
25
Informational
USER GUIDE 26(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.1.9 mp
Print all defined MO groups. See ma command in Section 4.1.7 for more info about MO groups.
Note: To print the contents of a group, use the pr <mo-group> command.
4.1.10 get[m][i]/lget[m][i] [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>]
Read CM/FM attribute(s) from MO(s).
Options:
m: for reading the attributes via MibManager instead of Corba. Only applicable on CPP nodes with C15.1 or higher.
i: to print internalmom attributes. Only applicable to MSRBSv2 (DUS Gen2). Please make sure to activate the feature
"Hidden Parameter Access" (CXC4012188/FAJ1214785) on the node for faster printout.
Note: to read PM attributes, use pget/lpget (see Section 4.4.3).
Examples:
1. Get all attributes from all MOs except those whose RDN matches utranrel or iub
get !(utranrel|iub)
2. Get all attributes from MOs whose proxies range from 10 to 30
get 10-30
3. From all MOs, get productdata containing the string 0843 (can be useful to find out which MO’s are related to a certain
loadmodule)
get all product 0843
4. From all Utrancells, get sintersearch attribute different from 10
get utrancel sinter !10
5. Get traffic descriptors for all VclTp(s)
get vc trafficdes
6. Get VcpTp(s) used by all cross-connections
get cross vc
7. Get piutype for all MO’s under "Equipment"
lget equip piutype
8. get attenuation values for all cables (in RBS)
get cable atten
9. get all attributes in nodesynch MO, belonging to site 1164 (in RNC)
lget 1164,nodesy
10. get all attributes in MO’s under "RadioNetwork" matching pwr or power or sir
lget radion p.*w.*r|sir
11. view which cells are connected to which iub’s (in RNC)
get cell iub
12. get all attributes from nodebfunction MO, except those matching "overload"
get nodebfunc !overload
13. get the attribute loadCtrlPrioOfMta via the internalmomread/testmomdump command
geti . loadCtrlPrioOfMta
Important information:
1. when doing a get <mo(s)> or get <mo(s)> all, one CORBA request is sent for each MO, asking for all attributes of
that MO.
2. when doing a get <mo(s)> <attribute(s)>, a CORBA request is sent for up to 100 MOs at a time, asking for the
specified attributes of those MOs.
26
Informational
USER GUIDE 27(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
The implications of this is that it is faster but:
1. if one or more attributes cannot be read due to some exception (eg: fRO not accessible), then all attributes will return the
same exception, even if they can be read.
2. if one or more MOs contain one or more attributes that cannot be read, then all MOs within that CORBA request will return
the same exception even if they can be read.
The workaround for the first problem is to find out which attribute is causing the problem. The command sget/lsget can be
used for this. The sget command reads each attribute one by one. The attribute(s) that is/are causing the exception(s) will then
be easy to spot.
It is then possible to use the standard "get" command with with the negative filter (!) to exclude the "faulty" attribute.
get nodebfunction !overload - all attributes of the nodebfunction MO except those matching "overload" will be read.
pget utrancell !pmnoofrrc - all pm attributes of the utrancell MO except those matching "pmnoofrrc" will be read.
The workaround for the second problem is to lower the speed of reading so that only one MO instead of 100 is read per CORBA
request.
This is done using the speed command.
Example: st all - one MO is returning an exception which means that up to 100 MOs cannot be read. Instead do:
speed 1
st all
speed 100
The command will be slower but the exception will only affect the MO(s) that have it and not the "healthy" ones.
The speed command affects get,pget,kget,prod, and st commands.
By default, speed is set to 100, which means that up to 100 MOs share the same CORBA request.
By running the command speed 1, the exception will not affect the other MOs. However the speed will be slower. It is possible
to use a value from 1 to 200 to define the speed. It is recommended to not use a speed higher than 100 since this takes more
memory from the node.
Type speed on its own to see the current speed.
Scripting and variable assignment with get
It is possible to store the output into a variable
Example:
1. Store one value into a variable
get utrancell pich > $pich
2. Store many values into an array
for $mo in utrancellgroup
$mordn = rdn($mo)
get $mo pich > $pichTable[$mordn]
done
Refer to the Section 6(Scripting Chapter) for more information.
4.1.11 hget[c][m][i]/lhget[c][m][i] <moGroup>|<moFilter>|<proxy(s)> [<attribute-filter>] [<value1-filter>] [<value2-filter>]
[<value3-filter>] etc...
Read CM/FM attribute(s) from MO(s), print horizontally one line per MO (instead of one line per attribute).
Options:
c: display the output in CSV format for easier export to excel (for instance).
m: print all MOs in a single table instead of separate tables per MO class
i: to print internalmom attributes, similar as "geti" but horizontally. Only applicable to MSRBSv2 (DUS Gen2). Please make
sure to activate the feature "Hidden Parameter Access" (CXC4012188/FAJ1214785) on the node for faster printout.
Example:
hget reliableprogramuniter slot|operational print the RPU attributes admActiveSlot, admPassiveSlot and
operationalMode
27
Informational
USER GUIDE 28(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
hget reliableprogramuniter slot|operational slot=10 . ^2 print all RPUs that are defined on slot10
(active), any slot for passive, and 2 for the operationalmode
hget reliableprogramuniter slot|operational !slot=10 . !^1 print all RPUs that are not defined on slot10
(active), any slot for passive, and operationalmode is not equal to 1
hget loadmodule type|productdata print the attributes loaderType and productData on all LoadModule MOs. Note
that productData is a struct containing 5 members so the productData attribute will take up 5 columns
hget loadmodule type|productdata@name only print the attribute loaderType and the structmember
productData:productName passive, and operationalmode is not equal to 1
hgetm port state print all attributes matching the word "state" on all MOs matching the word "port" and display all lines
in one single table instead of a separate table per MO class.
For "slow" hget, use "shget/lshget": reads only one attribute at a time.
4.1.12 kget[m]/lkget[m] [<moGroup>|<moFilter>|<proxy(s)>] [<attribute-filter>] [<attribute-type>] [<attribute-flag>]
[<attribute-description>]
Display CM/FM attributes in exportable printout format.
Same as get/lget, but with a different output format to allow import of the dump into external tools like MCOM, CCT, ETRAN.
The moption is for reading the attributes via MibManager instead of Corba. Only applicable on CPP nodes with C15.1 or higher.
To collect a MO dump via MibManager, set the uservariable mibmgr_threshold with uv command. Refer to info in the file
moshell/moshell.
For "slow" kget, use "skget/lskget": reads one attribute at a time.
The 2nd to 5th arguments have the same meaning as the arguments used in the "mom" command.
Examples:
kget : print all MO attributes
kget !relation= : print all attributes except from MOs with RDN matching "relation="
kget . . moref : print all attributes of data type matching "moref"
kget . . . ericsson : print all attributes with flag matching "ericsson"
kget . . . . dbm : print all attributes with description matching "dbm"
4.1.13 fro/lfro[m] <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>|all] [<value-filter>]
Read MO persistent data from node database via SQL.
The fro/lfro command reads only the froId connecting the MAO and FRO parts of the MO.
The from/lfrom command reads all MAO/FRO data of the MO.
The command syntax and printout format is identical to that of the get/lget command.
Examples:
from upgradepackage=cxp9012014_r5a - print MAO/FRO persistent data for MO
UpgradePackage=CXP9012014_R5A
from 0 - print MAO/FRO persistent data for the ManagedElement MO
fro plugin - print froId for all pluginunit MOs
fro plugin . 5 - print the PlugInUnit MOs who have a froid matching the value 5
fro plugin . ^5$ - print the PlugInUnit MOs who have a froid equal to 5
lfro ms,slot=10,plugin sairesource > $sai - save the sairesourceid of a particular pluginunit into a
variable $sai
Note: If the SQL client LM (CXC1325608) is not started, the fro[m] command starts it automatically using the "sql+" command.
After the session, the SQL client should be turned off using the "sql-" command. Type "h sql+" for more info.
28
Informational
USER GUIDE 29(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.1.14 sql/select <command> [ | <unix-cmds>]
To run a SQL command while in db.dat mode. The db.dat, cv.zip, or dbdump.zip is loaded with moshell option "-d".
Examples:
select *from tables | grep pgm
select *from tables where name like ’%iur%’
select *from cspgmresource_01 where pno=’CXC 132 0784’
4.1.15 st/lst <moGroup>|<moFilter>|<proxy(s)>|all [<state-filter>]
Print state of MOs (operationalState and administrativeState when applicable).
It is similar to writing get/lget <mo> state, the only difference is that it presents the two states side-by-side in a more visible
way.
The state filter matches towards both the Operational state and the Administrative state.
Examples:
st - view state of all MOs
st all dis - view all disabled MOs
lst equip dis - view all disabled MOs under "Equipment"
st all 1.*0view all MOs which are unlocked and disabled
st all ^0 - view all MOs which are locked:
lst sector - view state of all MOs under "Sector" (in RBS)
lst cell - view state of all channels in all 3 cells in the RBS
lst cell=120 - view state of all channels in cells starting with 120 (in RNC)
4.1.16 prod <moGroup>|<moFilter> [<productdata-filter>]
Print the attribute productData on applicable MO(s).
It is similar to typing "hget <mo> productdata". This command prints product data of all MO(s). It is similar to typing
get all productdata, except that the productData appears in one row. It is possible to filter only MOs matching a certain
product identity. Examples:
prod loadmodule cxc1320784 - print all MOs matching "loadmodule" and where the value of productData attribute
matches "cxc1320784"
MO classes that have a productdata attribute can be found via mom command:
mom all all struct:.*productdata
Typically, this includes Slot, Subrack, PiuType and LoadModule.
4.1.17 lk/llk <moGroup>|<moFilter>|<proxy(s)>
View all MO(s) linked to an MO, and their states (adminstrativeState and operationalState).
Examples:
lk mtp3bsrs= - View all core network interface stacks
lk ranap=cs - View all MO’s linked to Ranap=cs
lk iublink=iub-12 - View all MO’s linked to iub 12
lk atmport=ms-24-1 - View all MO’s linked to atmport MS-24-1 (and its VclTp’s)
lk eutrancellfdd=1a - View all MO’s linked to EUtranCellFDD=1A
29
Informational
USER GUIDE 30(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.1.18 lko/llko <moGroup>|<moFilter>|<proxy(s)>
The old lk. Obsolete command, use lk/llk instead.
Output format of e.g. lko ranap=cs:
===================================================================================
MOs linked to 1316 RncFunction=1,Ranap=cs (-,E)
===================================================================================
localSccpApRef Ranap=cs ---> (-,E) SccpSp=1,SccpScrc=1,SccpAp=1
sccpGlobalTitleRef Ranap=cs ---> (-,-) SccpSp=1,SccpScrc=1,SccpGlobalTitle=1
remoteSccpApRef Ranap=cs ---> (-,E) SccpSp=1,SccpScrc=1,SccpAp=2
reservedBy SccpSp=1,SccpScrc=1,SccpAp=1 ---> (-,-) SccpSp=1,SccpScrc=1,SccpEntitySet=1
mtp3bApId SccpSp=1,SccpScrc=1,SccpAp=2 ---> (-,E) Mtp3bSp=1,Mtp3bAp=1
reservedBy SccpSp=1,SccpScrc=1,SccpAp=2 ---> (-,-) SccpSp=1,SccpScrc=1,SccpEntitySet=2
routeSetId Mtp3bSp=1,Mtp3bAp=1 ---> (-,E) Mtp3bSp=1,Mtp3bSrs=1
reservedBy SccpSp=1,SccpScrc=1,SccpEntitySet=2 ---> (-,-) SccpSp=1,SccpScrc=1,SccpGlobalTitle=2
slsReservedBy Mtp3bSp=1,Mtp3bSrs=1 ---> (-,E) Mtp3bSp=1,Mtp3bSls=1
reservedBy Mtp3bSp=1,Mtp3bSls=1 ---> (-,E) Mtp3bSp=1,Mtp3bSrs=1,Mtp3bSr=1
nniSaalTpId Mtp3bSp=1,Mtp3bSls=1,Mtp3bSl=2 ---> (-,E) NniSaalTp=csb
nniSaalProfileId NniSaalTp=csb ---> (-,-) NniSaalProfile=1
aal5TpVccTpId NniSaalTp=csb ---> (-,E) Aal5TpVccTp=csb
processorId Aal5TpVccTp=csb ---> (U,E) Subrack=MS,Slot=9,PlugInUnit=1
vclTpId Aal5TpVccTp=csb ---> (-,E) AtmPort=MS-7-1,VplTp=vp12,VpcTp=1,VclTp=vc34
atmTrafficDescriptrId AtmPort=MS-7-1,VplTp=vp12,VpcTp=1,VclTp=vc34---> (-,-) AtmTrafficDescriptor=U3P4500M3000
nniSaalTpId Mtp3bSp=1,Mtp3bSls=1,Mtp3bSl=1 ---> (-,E) NniSaalTp=csa
nniSaalProfileId NniSaalTp=csa ---> (-,-) NniSaalProfile=1
aal5TpVccTpId NniSaalTp=csa ---> (-,E) Aal5TpVccTp=csa
processorId Aal5TpVccTp=csa ---> (U,E) Subrack=MS,Slot=8,PlugInUnit=1
vclTpId Aal5TpVccTp=csa ---> (-,E) AtmPort=MS-6-1,VplTp=vp11,VpcTp=1,VclTp=vc34
atmTrafficDescriptrId AtmPort=MS-6-1,VplTp=vp11,VpcTp=1,VclTp=vc34---> (-,-) AtmTrafficDescriptor=U3P4500M3000
===================================================================================
In the middle column is the originating MO. In the far right column is the referenced MO. In the left column is the attribute
containing the referenced MO. The letters in brackets show the administrativeState and operationalState of the referenced MO:
U= Unlocked
L= Locked
E= Enabled
D= Disabled
-= Not Applicable
4.1.19 set[m][c][1][i]/lset[m][c][1][i] <moGroup>|<moFilter>|<proxy(s)> <attribute> [<value>]
Set an attribute value on one or several MO’s.
Only attributes that do not have the flag readOnly or restricted can be set. Use the mom command to check the flags of an
attribute. For restricted attributes, it is possible to use the rset command.
Options:
m: for setting several attributes simultaneously in the same MO, using a single transaction for all attributes in each MO.
Needed for changing certain attributes in the RNC UtranCell (locationAreaRef, uarfcnDl, uarfcnUl).
1: for setting one attribute on many MOs simultaneously, using a single transaction for all the MOs. Needed for changing
certain attributes in the eNB EUtranCell (tac, frameStartOffset, subframeAssignment, specialSubframePattern).
c: for setting an attribute to its current value. When using this option, the attribute value shall not be specified since the
existing attribute value is used.
i: to set an attribute via "internalmomwrite" command. Only applicable to RCS nodes (MSRBSv2/TCU).
Note: These options cannot be combined.
Examples:
set cell primarycpichpower 250 - set primarycpichpower to 250 on all cells (in RNC)
lset uerc= sirmin 60 - set sirmin to 60 on all MO’s under uerc (in RNC)
lset ms,slot=1,pluginunit=1$ userlabel - set an empty value for the userLabel of this PluginUnit
set mtp3bspitu sppriority prioslt=2 - set an attribute of type struct
setc iublink= preferredsubrackref - set the preferredsubrackref attribute to its current value on all Iublinks, in
order to evenly spread the sites across all modules.
- setting three attributes simultaneously on a MO (split on several lines for readability)
setm utrancell=3012 locationarearef locationarea=9
servicearearef locationarea=9,servicearea=1
routingarearef locationarea=9,routingarea=1
set1 ^eutrancellfdd= tac 1280 - set the tac attribute simultaneously on all EUtranCellFDD in the eNB.
30
Informational
USER GUIDE 31(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
seti . loadCtrlPrioOfMta false - set the attribute loadCtrlPrioOfMta via internalmomwrite command
Please see Section 3and specifically Section 3.4 for more information on how to set values for each specific attribute type (e.g.
Struct,array of MoRef,array of Struct, etc).
4.1.20 eset[c][1]/leset[c][1] <moGroup>|<moFilter>|<proxy(s)> <attribute-filter> [<value>]
Set one or several attributes on one or several MO’s, using regexp matching on the attribute name.
Same as set command except that the second argument uses regular expression matching on the attribute name so all
attributes whose name match the filter will be affected by the operation. Refer to the help of the set command for more
information about syntax and command options cand 1.
Examples:
Activate all features in the RBS/ERBS. The attribute is called featureStatexxxx , where xxx is the name of the feature. All
MOs that have an attribute matching the word "featurestate" will have that attribute set to 1
>> eset . featurestate 1
Change the ENodeBFunction::eNodeBPlmnId on ERBS. The EUtranCellFDD::bPlmnList must be changed at the same
time in one transaction.
>> eset1 ^enodebf|^eutrancellfdd plmn mcc=240,mnc=99,mnclength=2
4.1.21 rset/lrset <moGroup>|<moFilter>|<proxy(s)> <attribute> [<value>]
Set attribute value on a restricted attribute or change the MOid of an MO.
Arestricted attribute is an attribute that can only be set when the MO is created.
The rset command works by doing rdel/lrdel on the MO and recreating all previously deleted MOs using the new attribute
value.
To change the MOid of an MO, the attribute name should be made up of the MOclass followed by "id", eg: atmportid, pluginunitid,
etc.
Example 1, change a restricted attribute:
rset unisaaltp=.*1004 unisaalprofileid unisaalprofile=win30a
Example 2, change the MOid:
rset utrancell=cell123 utrancellid cell456
4.1.22 bl[s]/lbl[s] <moGroup>|<moFilter>|<proxy(s)>
Lock or soft-lock MO(s).
Works by setting the administrativestate to 0 (hard-lock) or 2 (soft-lock).
The soption is for soft-lock. The administrativestate is set to 2 ("shutting down") which means that the resource will have a grace
period to handover traffic to other resources, before it gets locked. The administrativestate will automatically go over to 0 after the
grace period, which can be between a few seconds to a couple of minutes, depending on the MO type.
The administrativeState will automatically go over to 0 after the grace period of around 30 seconds.
Without the soption, the resource is locked immediately.
To unlock an MO, use the command deb/ldeb.
Examples:
1. bl aal2.*ca[246] - block aal2paths ca2, ca4, ca6
2. lbl subrack=ms,slot=19 - block all MO(s) under subrack=ms,slot=19
3. bl 234 256 248 - block proxys 234, 256, and 248
4. bl 001500 - block a board. Same as lbl subrack=ms,slot=15,pluginunit=1$.
5. bls 001500 - soft-block a board.
31
Informational
USER GUIDE 32(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Note: there is also an OSE command called bl. If the OSE command needs to be run instead of the moshell command, just type
a "\" (backslash) in front. E.g.: \bl
4.1.23 deb/ldeb <moGroup>|<moFilter>|<proxy(s)>
Unlock MO(s).
Works by setting the administrativestate to 1.
To lock an MO, use the command bl/lbl.
1. ldeb subrack=ms,slot=19 - deblock all MO(s) under subrack=ms,slot=19
2. deb 001900 - deblock a board. Same as ldeb subrack=ms,slot=19,pluginunit=1$)
4.1.24 acl/lacl <moGroup>|<moFilter>|<proxy(s)>|all [<action-filter>]
Lists available MO actions.
Examples:
1. acl all restart - View all restart actions
2. acl all [^(restart)(eteloopback)] - View all actions except restart and eteloopback
3. acl sync - View all actions related to the synchronisation MO. Output:
------------------------------------------------------------------------------
Proxy MO Action Nr of Params
------------------------------------------------------------------------------
396 Synchronization=1 changeSyncRefPriority 2
396 Synchronization=1 removeSyncRefResource 1
396 Synchronization=1 resetLossOfTracking 1
396 Synchronization=1 addSyncRefResource 2
4. acl all listrou - Find the MO with action matching regular expression listrou:
-------------------------------------------------------------------------------------------------
Proxy MO Action Nr of Params
-------------------------------------------------------------------------------------------------
471 Ip=1,IpRoutingTable=1 listRoutes 0
4.1.25 acc[e][n]/lacc[e][n] <moGroup>|<moFilter>|<proxy(s)>|all <action>
Execute an MO action.
If the action requires parameters, these will be prompted for. If no value is entered at a prompt, the action is aborted. In order to
be avoid being prompted for the parameters, use option "n" (accn/laccn), then the parameters can be given on the same line as
the command.
Options:
n: action parameters will not be prompted for and shall be input on the command line. Eg:
accn 0 manualrestart 0 0 0
e: for action parameters of type struct, there will be a separate prompt for each individual struct member.
Examples:
1. Restart a board:
acc 001400 restart - Same as:
lacc subrack=ms,slot=14,pluginunit=1$ restart
acc 001900/sp0.lnh restart - Same as:
lacc subrack=ms,slot=19,.*,spm=1$ restart
2. Restart the node:
acc 0 manualrestart
3. List the IP routing table:
acc ip listroutes
4. Perform End-To-End loopback on VclTp MOs:
lacc atmport=ms-24-1 eteloopback
32
Informational
USER GUIDE 33(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
5. Perform PhaseMeasurement on NodeSynchTp MOs:
acc nodes performPhaseMeasurement
6. Add a new synchronization reference:
acc sync addSyncRefResource
Note 1: To specify an attribute of type Struct, use the following syntax:
attr1=val1,attr2=val2,attr3=val3...
This is the same syntax as used in set and cr commands, and is not case sensitive. Example (in the case of routingTableEntry
in action deleteStaticRoute) (note: line split for readability):
destinationIpAddr=10.1.10.0,destinationNetworkMask=255.255.255.0,
nextHopIpAddr=10.128.15.1,routeMetric=3
Alternatively, the option ecan be used, in which case each struct member is prompted on a separate line (command:
acce/lacce).
Note2: Action manualRestart on ManagedElement MO
This action can be restricted with the uservariable restart_confirmation. See description in the file moshell/moshell.
Node restarts usually result in decrementing of the attribute ConfigurationVersion::rollbackCounter which leads to node
rollback upon reaching zero. However the action manualRestart on ManagedElement is a special case which does not lead
to decrement of the rollbackCounter, when executed from moshell/AMOS.
4.1.26 cr[e][n] <ldn>
Create an MO.
When run without option, the command will prompt the user to enter the values for all mandatory and restricted attributes. The
order in which the attributes are prompted is the same order in which they are listed inside the XML MOM file. Restricted
attributes are optional, type dto select default value. To abort, type <enter> at the prompt.
Options:
e: to receive a separate prompt for each individual struct member, useful when inputting attribute values of type struct
n: allow the user to enter any attribute name and value. Each attribute name and value shall be entered on a separate line
with space between the attribute name and value. Any attribute can be specified, does not have to be a mandatory or
restricted attribute. Type "end" once all attributes have been entered.
Examples:
cr swmanagement=1,upgradepackage=FAB102572%2_R14D.xml
cr rncfunction=1,iublink=2456
cre swmanagement=1,loadmodule=CXC123456_R9A
crn rncfunction=1,iublink=90
Notes:
To specify an empty attribute value, type null or d.
To specify an attribute of type Struct, use the following syntax:
attr1=val1,attr2=val2,attr3=val3...
This is the same syntax as used in set command, and is not case sensitive. Example, in the case of productdata in loadmodule
(note: line split for readability!):
productnumber=CXC1322155/2,productrevision=R3C08,productname=test,
productinfo=test,productiondate=20010229
Alternatively, the option ecan be used, in that case, each struct member is prompted on a separate line (command: cre).
An moshell script for MO creation can be automatically generated by using the simulated undo mode: u+s ,del <mo> ,u- ,
then edit the undocommandfile with the required values. By default the undo script will contain crn commands. To use cr
commands instead of crn, do uv use_crn=0.
By default, the mandatory/restricted attributes that are marked as deprecated are not prompted by the cr command. This
behaviour can be changed by setting the uservariable exclude_deprecated to 0.
33
Informational
USER GUIDE 34(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
As in the ld command, the LDN doesn’t need to contain ManagedElement=1.
The mo-types are not case sensitive but the mo-id is.
4.1.27 del[b]/ldel[b] <moGroup>|<moFilter>|<proxy(s)>
Delete MO(s).
An MO can only be deleted when its reservedBy list is empty and when it does not have any children. If the MO does have
children and/or a non-empty reservedBy attribute, it is possible to use the rdel/lrdel command instead.
The command first prints the MO(s) to be deleted, then asks for confirmation. Once the MO(s) are deleted, they are also
removed from the proxy list.
To delete all MOs that have just been created by a script, just check the range of proxies that were created and delete them in the
reverse order. This can be done easily by using the reverse proxy order.
Example: proxies 22 to 46 were created by a CREATE script (in run or trun). To undo it:
del 46-22
To delete an MO and all its children, just use the % sign in front of the ldn/rdn filter. Example:
ldel %ms,slot=20,plug will delete the programs first then the piu
To delete an MO group in the reverse order of the proxies, put the % sign in front of the MO group name. Example:
del %mymogroup - will delete all MOs of the MO group "mymogroup" in the reverse order of their proxies
Note:
The following MOs can only be deleted while in state LOCKED: PlugInUnit, EUtranCell, TermPointToENB, GpsReceiver,
IpAccessHostEt, IpAccessHostGpb, IpAccessHostSpb, IpSyncRef .
By default, the "del" command will automatically perform the locking prior to deleting, unless the "b" option has been used (delb).
4.1.28 rdel/lrdel <moGroup>|<moFilter>|<proxy(s)>
Delete MO(s) together with children and reserving MOs.
For MO classes shown in the list below, the command finds out all the related MOs, then presents the list of MOs to be deleted
and asks the user for confirmation. For all other MO classes, the command acts in the same way as a regular "del" operation, ie,
just tries to delete the MO itself.
List of MO classes for which rdel acts recursively:
Aal0TpVcctp
Aal1TpVcctp
Aal2Ap
Aal2PathDistributionUnit
Aal2PathVcctp
Aal2RoutingCase
Aal5TpVccTp
AntennaNearUnit
AtmCrossConnection
AtmPort
Cdma2000Cell
Ds0Bundle
EUtranCellFDD
EUtranCellTDD
EutranFrequency
ExternalCdma2000Cell
ExternalCdma20001xRttCell
34
Informational
USER GUIDE 35(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
ExternalENodeBFunction
ExternalEUtranCellFDD
ExternalEUtranCellTDD
ExternalGeranCell
ExternalGsmCell
ExternalUtranCell
ExternalUtranCellFDD
ExternalUtranCellTDD
ImaGroup
IpEthPacketDataRouter
IuLink
Iub
IubLink
IurLink
M3uAssociation
Mtp2TpItu/Ansi/Ttc/China
Mtp3bSlItu/Ansi/Ttc/China
Mtp3bSls
Mtp3bSrs
NbapCommon
NbapDedicated
NniSaalTp
NodeSynchTp
PacketDataRouter
Ranap
Rnsap
SectorEquipmentFunction
UniSaalTp
UtranCell
VclTp
Vmgw
VpcTp
VplTp
4.1.29 gm[c][d]/lgm[c][d] <moGroup>|<moFilter>|<proxy(s)>
Generate MO Creation/Deletion script.
Options:
c: Generate MO Creation script.
d: Generate MO Deletion script.
The output of the command is a command file containing the creation/deletion commands.
By default the create statements will use the crn command but it is possible to use the cr command by setting uv use_crn=0
It is possible to convert the command file to trun format with the u! command.
Examples:
35
Informational
USER GUIDE 36(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
lgmc equipment=1 : Generate a MO script to create all the MOs under Equipment=1 . Parent and referenced MOs will
be created before children and reserving MOs.
gmd subrack=1,slot=2,pluginunit=1 : Generate a MO script to delete the MO Subrack=1,Slot=2,PlugInUnit=1 .
Children and reserving MOs will be deleted before parent and reserved MOs.
4.1.30 sc[g][w][d] [<parameterlist>]
Read/Write/Reset SystemConstants.
Options:
g("get") : read system constants
w("write") : set system constants
d("default"): reset system constants
Syntax:
scg [const [ > $var]] : read one or all constants
scw const1:val1,const2:val2,... : write one or more constants
scd const1,const2,... : reset one or more constants to default
scd all : reset all constants to default
Syntax examples:
scg : read all system constants
scg 915 : read the value of system constant "915"
scg 915 > $var : read the value of system constant "915" and store to a variable
scd 915 : reset system constant 915 to its default value
scd 915,2102,2085 : reset system constant 915, 2102, 2085 to their default value
scd all: reset all system constants to their default value
scw 915:14 : set system constant 915 to the value 14
scw 915:14,2102:1,2085:1 : set system constants 915 to 14, 2102 to 1, 2085 to 1
4.1.31 safe+/safe-/safe?
Purpose: Apply strict MO matching rules on MO WRITE commands
safe+ : apply safe MO syntax, no proxy id or no regular expression matching for MO WRITE commands, exact MO
name(s) must be given (case insensitive is allowed)
safe- : allow proxy id and regular expression matching (this is the default setting)
safe? : check the current setting
List of MO WRITE commands: bl, bls, deb, del, rdel, fdel, set, eset, rset, fset, acc, facc
Examples:
bl utrancell=11 - will lock cell=11 only (cell=111, or cell=11a , etc. would not be affected)
bl utrancell=11|utrancell=12|utrancell=13 - will lock cell=11, cell=12, cell=13
bl utrancell=11|12|13 - same as above
bl utrancell=11|12|13|iublink=1 - will lock cell=11/12/13 and iublink=1
bl pluginunit=1 - nothing will happen as there are several MO instances with this name
bl subrack=ms,slot=28,pluginunit=1 - will lock this MO as the name given is unique
The setting is off by default but can be saved to "on" by adding the line safe_syntax=1 in the file moshell/jarxml/moshellrc or
the file /.moshellrc
36
Informational
USER GUIDE 37(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.1.32 s+/s++/s-/s?
Purpose: Sort MO list in alphabetical order instead of proxy order.
s+ : activate alphabetical sorting of the MO list by order of LDN (sort_proxy=1)
s++ : activate alphabetical sorting of the MO list by order of MO class (sort_proxy=2)
s- : go back to default behaviour where the MO list is sorted by proxy number (sort_proxy=0)
s? : check if alphabetical sorting is active or not
Once the s+/s++ command has been entered, the alphabetical sorting takes effect on all subsequent MO commands such as, pr,
get, set, st, etc.
Type s- to revert to the default behaviour of sorting by proxy number.
To change the default behaviour, it is possible to use the uservariable sort_proxy, eg, adding the line sort_proxy=1 in the
file ~/.moshellrc
Example:
Default behaviour: MOs are displayed in the order of the proxy numbering. The order of the proxy numbering depends on the
order with which the MOs were created on the node.
RNC32> pr uerc=
===================================================================================
Proxy MO
===================================================================================
2587 RncFunction=1,UeRc=0
2591 RncFunction=1,UeRc=16
2604 RncFunction=1,UeRc=91
2620 RncFunction=1,UeRc=1
2628 RncFunction=1,UeRc=17
2643 RncFunction=1,UeRc=70
2644 RncFunction=1,UeRc=59
2670 RncFunction=1,UeRc=2
Activate MO list sorting and run some MO commands. MOs now appear in alphabetical order.
RNC32> s+
Proxy sorting: activated.
RNC32> pr uerc=
===================================================================================
Proxy MO
===================================================================================
2587 RncFunction=1,UeRc=0
2620 RncFunction=1,UeRc=1
2670 RncFunction=1,UeRc=2
2754 RncFunction=1,UeRc=3
4071 RncFunction=1,UeRc=4
....<cut>....
RNC32> hget uerc= userlabel
=================================================================================================================
MO userLabel
=================================================================================================================
UeRc=0 Idle
UeRc=1 SRB (13.6/13.6)
UeRc=2 Conv. CS speech 12.2
UeRc=3 Conv. CS unkn (64/64)
UeRc=4 Interact. PS (RACH/FACH)
UeRc=5 Interact. PS (64/64)
UeRc=6 Interact. PS (64/128)
4.1.33 u+[s]/u-/u? [<file>]
Handling of undo mode (for cr/del/rdel/set/bl/deb/acc commands). Can be used for generation of MO scripts as well.
37
Informational
USER GUIDE 38(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
u+ To start the undo mode
u+s To start the simulated undo mode
u- To stop the undo mode
u? To check if undo mode is active or not
u! To convert moshell ".mos" command files to netconf ".xml" format or trun ".mo" format (and vice-versa), or undo ".log"
logfiles to ".mos" command files, see description further down for more info.
While running in "undo mode", the MO data is saved in a special logfile for all MOs on which the following commands are run:
cr
del/ldel/rdel/lrdel
bl/lbl/deb/ldeb
set/lset
acc/lacc
Upon stopping of undo mode, an undo file is generated to revert the MO configuration changes. It can also be used for deleting
and recreating MOs when one needs to change a restricted attribute.
The undo file will contain the following commands:
del commands to remove created MOs.
cr commands to put back deleted MOs.
bl/deb commands to change MOs back to their original administrative state.
set commands to change MOs back to their original attribute values.
acc commands to revert certain MO actions. This only works on actions that have an opposite, see note below.
When running the simulated undo mode (u+s), all MO operations (cr/del/rdel/bl/deb/set) are simulated. Two command
files are generated, one for deletions and one for creation.
The files generated by undo mode and simulated undo mode are stored in the following variables:
$undologfile
$undodelcommandfile (simulated undo mode only)
$undocommandfile
Conversion functionality (u!): The u! command takes as input one of the files generated by the undo mode. Different output will
be generated depending on the input file.
if the input file is an undologfile (.log), the output will be an undodelcommandfile and an undocommandfile
if the input file is an undodelcommandfile or an undocommandfile (.mos), the output will be:
in case of CPP node: an undotrunfile ($undotrunfile) which is a command file in trun/emas format (.mo)
in case of COM node: an undoxmlfile ($undoxmlfile) which is a command file in netconf format (.xml)
if the input file is an undotrunfile (trun/emas format ".mo"), the output will be an undocommandfile (run format ".mos")
Note: to undo create commands run from a "trun" script, just run a delete on the proxy range in reverse order. See
Section 4.1.27 or h del for more info.
Note: the undo mode currently cannot reverse a set command done on an attribute of type sequence of struct.
Note: the following actions are currently supported in the undo mode:
addPath/removePath
addDhcpServerAddress/removeDhcpServerAddress
setAutoActivate/setAutoDown
activateRemoteSp/inactivateRemoteSp
addRemoteSp/removeRemoteSp
activate/deactivate
localInhibit/localUninhibit
activateLinkSet/deactivateLinkSet
38
Informational
USER GUIDE 39(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
blockSignalingRoute/deBlockSignalingRoute
addRepertoire/deleteRepertoire
addSlot/deleteSlot
addCicRange/removeCicRange
addNri/removeNri
addTdmTermGrpMos/removeTdmTermGrpMos
addSyncrefResource/deleteSyncrefResource
addAal2ApToRc/removeAal2ApFromRc
writeSystConst/resetSystConst, deleteConst/writeConst
changeFrequency, pnpChangeFrequency, setFrequencyBand
removeIpAccessHostMos/addIpAccessHostMos
manualMspSwitch, manualSwitch, switch
4.1.34 run[x][1][1p][1r] [-l <lineNr>] <command file> [<var1>] [<var2>] ...
Run a command file in moshell format.
The command file layout is the same as for monode and mobatch. See examples in moshell/examples/mobatch_files.
It shall contain all lines to be sent to the moshell prompt, including password (for ose commands), but NOT confirmations (y).
This applies to commands such as lt/ltc,lc/lcc,del/ldel,bl/lbl,set/lset where confirmation is automatically entered
when running a command file.
Comments can be put in the command file using the #sign. By typing <TAB>, the unix file system is displayed, making it easier
to find the location of the command file.
If some arguments are given after the command file, the scripting variables $1, $2, $3, etc. will be set to the corresponding
values. The variable $0 will be set to the whole line contents. Type "h scripting" for info.
Options:
1: to execute the file in one transaction and commit. Only applicable for COM nodes. To run a MO script in one transaction
on CPP nodes, use trun1.
1p: to execute the file in one transaction and prompt for commit/rollback. Only applicable for COM nodes.
1r: to execute the file in one transaction and rollback. Only applicable for COM nodes.
x: to stop execution of the file upon failure of a MO WRITE command (create, delete, set, action). The following scripting
variables are set automatically when the script stops:
$errorline points to the line number where the script stopped
$errorcmdline points to the line number of the last command that failed
$nextcmdline points to the line number of the next command to execute
Switches:
-l <lineNumber>: to start file execution at a specific line number.
4.1.35 trun[is1cr] <moScript>|<http://ipaddress/script>
Run a command file in EMAS/MoTester format.
Execute a command file in EMAS/MoTester format.
By typing <TAB>, the unix file system is displayed, making it easier to find the location of the command file.
It is also possible to specify a file located on a web server (eg. when the script is located on the CPP node).
The following commands are supported: ECHO, CREATE, SET, SETM, SETU, DELETE, ACTION, CHECK, CHECKM, CALL,
CALLREL, WAIT.
Lines can be commented out by adding // at the beginning of each line.
See examples below. For more info, refer to MoTester documentation in moshell/examples/motester/runMoTester.html .
39
Informational
USER GUIDE 40(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
By default, the command file halts when a command fails.
Options:
i: ignore exceptions, the execution does not halt when a command fails.
s: simulated run, the command file execution is simulated, no commands are actually executed on the node. Can be used
to verify the syntax of a script prior to running it for real. The simulated mode is always used in "offline mode" or "simulated
undo mode", regardless of the "trun" options.
1: executes the whole script in one transaction, then prompts for confirm or rollback. This option should be used with great
care and only when absolutely necessary (e.g. when changing IP address of the node, see example script in
moshell/examples/misc/ip_change.mo). In regular usage, it is recommended to not use this option as it has been
observed to cause database corruptions in certain cases, for instance when creating/deleting certain types of MOs within
the same transaction. Database inconsistencies can be checked with the command dbc.
c: used in combination with option 1above, will avoid the prompt by automatically confirming the transaction
r: used in combination with option 1above, will avoid the prompt by automatically rolling back the transaction
Command description. See syntax examples further down.
ECHO: the script will echo some text on the screen
CREATE: create a new MO instance
DELETE: delete a MO instance
ACTION: perform a MO action
SET: set one MO attribute
SETM: set several MO attributes
SETU: set a single struct member (whereas with SET/SETM, all struct members must be specified)
CHECK: check that an attribute value is equal to a given value
CHECKM: enhanced "check" - supports non-transactional get operation and multiple attributes
WAIT: pause the script execution for a given number of milliseconds
CALL: execute another MO script. If the path of the script is not an absolute path then the current working directory will be
searched.
CALLREL: execute another MO script. If the path of the script is not an absolute path the the directory of the main script will
be searched.
TRANSACTION: mark the beginning or end of a transaction. All operations executed between the statements
"TRANSACTION BEGIN" and "TRANSACTION END" will be executed within one single transaction.
CORBATIMEOUT: set a different idle timeout for the script, to override the value of the uservariable "corba_timeout".
Script example:
//Echo a comment
ECHO "Start Test"
//Create a MO
CREATE
(
parent "ManagedElement=1,SwManagement=1"
identity "ROJ1192104_3_R4"
moType PiuType
exception none
nrOfAttributes 3
productData Struct
nrOfElements 5
productNumber String "ROJ1192104/3"
productRevision String "R4"
productName String "TUB"
productInfo String "TU"
productionDate String "20030116"
boardWidth Integer 3
role Integer 2
)
//Delete a MO
DELETE
(
mo "ManagedElement=1,SwManagement=1,PiuType=ROJ1192104_3_R4"
exception none
40
Informational
USER GUIDE 41(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
)
//Set an attribute
SET
(
mo "ManagedElement=1,Equipment=1,Jvm=1"
exception none
admClasspath Array Reference 4
"ManagedElement=1,SwManagement=1,LoadModule=Oms"
"ManagedElement=1,SwManagement=1,LoadModule=Asms"
"ManagedElement=1,SwManagement=1,LoadModule=VbjOrb"
"ManagedElement=1,SwManagement=1,LoadModule=Cma"
)
//Set several attributes in one MO
SETM
(
mo "ManagedElement=1,RncFunction=1,UtranCell=Iub-1-1"
exception none
uarfcnDl Integer 10738
uarfcnUl Integer 9788
)
SETM
(
mo "ManagedElement=1,RncFunction=1,Sid=1"
exception none
sib1 Struct nrOfElements 2
sib1RepPeriod Integer 32
sib1StartPos Integer 4
sib2 Struct nrOfElements 2
sib2RepPeriod Integer 128
sib2StartPos Integer 118
)
//Set an incomplete struct attribute. Missing struct members will be set to their current value.
SETU
(
mo "ManagedElement=1,RncFunction=1,Sid=1"
exception none
sib1 Struct nrOfElements 1
sib1RepPeriod Integer 32
)
//Execute an MO action
ACTION
(
actionName addRepertoire
mo "ManagedElement=1,SwManagement=1,SwAllocation=TB_LLP"
exception none
nrOfParameters 1
Ref "ManagedElement=1,SwManagement=1,Repertoire=Cello_Common_MP"
returnValue ignore
)
//Read an attribute with transactional get and compare to a reference value
CHECK
(
mo "ManagedElement=1,RncFunction=1,UtranCell=Iub-1-1"
exception none
uarfcnDl 10738
)
//Read one or more attributes with transactional get and compare to reference values
CHECKM
(
mo "ManagedElement=1,RncFunction=1,UtranCell=Iub-1-1"
exception none
uarfcnDl 10738
uarfcnUl 9788
)
//Read one or more attributes with null transaction and compare to reference values
CHECKM
(
mo "ManagedElement=1,RncFunction=1,UtranCell=Iub-1-1"
exception none
transaction null
uarfcnDl 10738
uarfcnUl 9788
)
41
Informational
USER GUIDE 42(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
//Read one or more attributes with null transaction and print the values without comparing
CHECKM
(
mo "ManagedElement=1,RncFunction=1,UtranCell=Iub-1-1"
exception none
transaction null
compare no
uarfcnDl
uarfcnUl
)
//wait 2 seconds (time given in milliseconds)
WAIT 2000
//run another MO script
CALL("/home/eric/scripts/newfile.mo")
//run another MO script using a path relative to the path of the main script
CALLREL("test.mo")
//run some operations in a single transaction
TRANSACTION BEGIN
<put some commands here>
TRANSACTION END
//set a different idle timeout for the script (in seconds), to override the uv "corba_timeout"
CORBATIMEOUT 1800
4.1.36 Ctrl-Z; touch /tmp/xxxx; fg (abort MO command)
Abort an MO command or a "for" loop.
To abort an MO command (like get/st/set/acc...) or a for loop, two steps are needed:
First type Ctrl-Z, to suspend moshell. Then, at the unix prompt, create an empty file /tmp/xxxx (where xxxx is the process
number indicated in moshell menu and in the window’s title bar) and resume moshell. This is done with the following command:
touch /tmp/xxxx ; fg
If the moshell prompt doesn’t come back even after typing <enter> a number of times, try again suspending (ctrl-z) and resuming
(fg).
4.1.37 pol[b][c][d][h][i][k][m][p][s][r][u][w][y] [-m <mo>] [<interval>] [<waitTime>] [<checkTime>]
Poll the node until the MO service is up or until an operation has completed.
Options applicable for CPP nodes:
s: poll the node until telnet/ssh server is up.
h: poll the node until http server is up.
r: poll the node until http server is down. Eg to find out when the node restart has begun.
d: poll the node until the action startHealthCheck is completed.
m: poll the node until /c disk mirroring is completed.
k: poll the node until the system clock is in locked mode.
c: poll the node until the ConfigurationVersion has completed its ongoing operations, by monitoring the attribute
currentMainActivity. Useful to use after action restore/forcedRestore.
u: poll the node until the UpgradePackage has completed its ongoing operations, by monitoring the attribute
progressHeader. If progressHeader is awaiting_confirm, the confirmUpgrade action will be sent automatically
to the node.
Options applicable for COM nodes:
h: poll the node until COM port is up.
r: poll the node until COM port is down. Eg to find out when the node restart has begun.
u: poll the node until the UpgradePackage MO has completed its ongoing operations, by monitoring the attribute
reportProgress. If the UpgradePackageState is waiting_for_commit, the confirm action will be sent automatically
42
Informational
USER GUIDE 43(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
to the node.
b: poll the node until the Brm* MO (BrmBackup,BrmBackupManager,BrmBackupScheduler,BrmFailsafeBackup) has
completed its ongoing operations.
i: poll the node until the KeyFileManagement has completed its ongoing operations.
w: poll the node until the SwM MO has completed its ongoing operations.
y: poll the node until the CertM/NodeCredential MO has completed its ongoing operations.
p: poll any MO that has a progress attribute, using option -m <mo>.
Only one option can be given at a time, ie, it is not supported to combine several options. If no options are given, then it will poll
the node until the MO service is up. Note that this polling is done automatically before each MO command. If the loaded CV has
changed during the polling then moshell will automatically reload the MOM and MIB (getmom,parsemom,lt all).
Arguments (optional):
<interval> : to specify the time in seconds between each polling. Default value is 10 seconds.
<waitTime> : to specify the time in seconds to wait before starting to poll. Default is 20 seconds (60 seconds for polu).
The reason for this waiting time is because it can take some time before the node starts to execute an operation.
<checkTime>: to specify the time in seconds to wait before checking the result of an action, when using options ’c’ or ’u’.
Default value is 60 seconds.
To abort the polling, do ctrl-z, then touch <stopfile> (the path to stopfile is printed in the window title), then fg. See
h ctrl-z for more info.
Examples: Performing various operations on a UpgradePackage and polling the node in between each, to find out when it’s
possible to carry on.
acc upgradepackage=CXP9012014_R10CD nonblockinginstall
polu
acc upgradepackage=CXP9012014_R10CD verifyupgrade
polu
acc upgradepackage=CXP9012014_R10CD rebootnodeupgrade
Note: if polu is executed on a node which is being upgraded from ENM or the OSSRC SMO application, then the uservariable
polu_confirmupgrade should be set to 0 to prevent polu from confirming the upgrade. Otherwise this would confuse SMO.
Refer to the description of this uservariable inside the file moshell/moshell.
4.1.38 re[i]
Disconnect and reconnect to the CM service (mobrowser) and/or the PM service (pmtester).
This is useful if the security settings have changed on the node during the moshell session. The "i" option is to refetch the iorfile
which is necessary if the IORfile has changed on the node (this happens for instance when going from vbjorb to JacORB or
changing to corba security). Note that when moshell first starts up, it is neither connected to CM nor PM.
To connect to CM service, just use the re command, the lt command or any other MO commands (eg pr,get, etc). As soon as
moshell has connected to the CM service the userlabel/site attribute of ManagedElement will be read and prompt will be set
accordingly.
To connect to PM service, just type the pst command which will list all scanners defined on the node.
If there is a node restart with change of CORBA supplier, ie going from Vbjorb (cpp3/4/5) to JacORB (cpp5.1 and above) or
vice-versa, then it is necessary to issue the rei command which will also refetch the IOR file.
It is NOT necessary to type re after a node restart/upgrade or jvm restart, as long as the corba definitions have stayed the same
(corba supplier and corba security setting). Moshell stays connected all the time, though it may not be possible to perform
operations while the restart is happening.
4.1.39 getmom [<momversion>]
Check the MOM version currently stored on the node or download a MOM from newtran01 server.
When the command is run on its own, without argument, a check will be done to find the MOM version of the node. For CPP
nodes, the check is done by reading the header of the MOM file stored under http://<NodeIpAddress>/cello/oe/xml. For COM
nodes, the check is done by reading the identifier and version attributes in the Schema MOs. Usually this check is done
43
Informational
USER GUIDE 44(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
automatically when moshell connects to the MO service.
When the command is run with an argument, then it will try to fetch the corresponding MOM file from the newtran01 server and
store it in the jarxml folder.
Example:
>> getmom RNC_NODE_MODEL_K_9_115_COMPLETE
4.1.40 parsemom [<momFile>]
Parse an xml MOM file
Without argument, the parsemom command just reparses the current MOM version. Can be used in conjunction with the
getmom command to check and parse the current MOM.
With argument, the parsemom command will parse a different MOM to the one currently loaded in moshell. Can be useful if an
incorrect MOM is stored on the node or if just wanting to browse a MOM offline. Example:
parsemom moshell/jarxml/RNC_NODE_MODEL_D_3.xml
4.1.41 flt/fltc <motype-filter>
Load proxys for an MO type that is not defined in the MOM. ("Force" lt/ltc).
Can be useful in case the xml MOM isn’t up to date with the node SW, or in case there is no xml MOM.
Example: flt rncsystemparameters
4.1.42 fget[i]/lfget[i] <moGroup>|<moFilter>|<proxy(s)>|all [<attribute>]
Read attributes that are not listed in the MOM (f="Force").
With fget/lfget, the exact attribute name must be specified in the command.
Any attribute can be displayed as long as it is supported by the node SW.
Options:
i: to read an attribute via "internalmomread" command. Only applicable to RCS nodes (MSRBSv2/TCU).
Examples:
fget ^pluginunit= resourceid
fgeti ^eutrancellfdd= loadCtrlPrioOfMta
fgeti ^eutrancellfdd=7 dlCyclicPrefix > $var
4.1.43 eget/leget <moGroup>|<moFilter>|<proxy(s)>|all [<attribute>]
Read attributes that are not listed in the MOM (e="Extended").
With eget/leget, the attribute name is optional, or an attribute filter can be used.
Only attributes listed in the file moshell/commonjars/extendedMOM.txt can be shown. The attributes of this file can also be
shown in the commands get/kget/sget if the uservariable use_extended_mom is set to 1 (default: 0).
Example: eget plug res
4.1.44 sget/lsget/skget/lskget/shget/lshget <moGroup>|<moFilter>|<proxy(s)>|all
Read CM/FM attributes from MO(s), one by one ("Slow" get).
Slow but useful in case the standard "get" command is not working due to some attribute returning an exception.
4.1.45 fset[i]/lfset[i] <moGroup>|<moFilter>|<proxy(s)>|all <attribute> [<value>] [<attribute-type>]
Set an attribute that is not described in the MOM ("Force" set).
44
Informational
USER GUIDE 45(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Can be useful in case the xml MOM isn’t up to date with the node SW, or in case there is no xml MOM (e.g. MGW application
part).
The syntax is similar to the "set" command except that the attribute type has to explicitely specified using the reference list below.
Options:
i: to set an attribute via "internalmomwrite" command. Only applicable to RCS nodes (MSRBSv2/TCU). With "i" option, the
attribute type should not be specified.
Examples:
lfset subrack=ms,slot=20,pluginunit=1$ administrativestate 0 i
fseti ^eutrancellfdd= loadCtrlPrioOfMta false
Following attribute types are supported:
iinteger/long/enum
llonglong
sstring
bboolean
rmoref
ffloat
tstruct
ai array of integer/long/enum
al array of longlong
as array of string
ab array of boolean
ar array of moref
af array of float
at array of structref
4.1.46 facc/lfacc <moGroup>|<moFilter>|<proxy(s)>|all <action> [<param1>] [<param2>]
Perform actions that are not defined in the MOM ("force" action).
Can be useful in case the xml MOM isn’t up to date with the node SW, or in case there is no xml MOM.
If the parameter is a an integer or a string, the parameter type does not need to be specified as in the example below.
Example:
lfacc Sector=1,Carrier=1,HsDschResources=1 startRDBTCellHidden 16
facc CommContexts=1 readHsMusOnCCHidden 0
Otherwise it should be explicitely specified, using the reference list below. Examples:
lfacc Equipment=1,Subrack=1,Slot=4,PlugInUnit=1,RaxDeviceGroup=1,UbchDeviceSet
defineCqiPatternHidden 0 5 15,16,17,18,19:ai
Following parameter types are supported:
iinteger/long/enum
llonglong
sstring
bboolean
rmoref
ffloat
tstruct
ai array of integer/long/enum
al array of longlong
45
Informational
USER GUIDE 46(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
as array of string
ab array of boolean
ar array of moref
af array of float
at array of structref
4.1.47 fdel/lfdel <moGroup>|<moFilter>|<proxy(s)>
Delete MO(s), including systemCreated MOs.
Works in the same way as the regular del/ldel command except that it also tries deleting the systemCreated MOs, whereas
the del command skips them.
Though the systemCreated MOs cannot be deleted, this command can be useful when generating set commands in "simulated
undo mode" for those systemCreated MOs.
4.2 Other MO commands
4.2.1 cvls/cvmk/cvms/cvset/cvrm[u]/cvrbrm/cvcu/cvget[f][u][d]/cvput/cvls1/cvre/cvfa/cvfd
CV backup handling: list, make local, make remote, remove, setstartable.
A set of commands similar to the "cv" commands in OSE but operate through MO interface instead of telnet/ssh.
Command syntax and description (CPP):
cvcu: display the current cv information only (equivalent of "cv cu").
cvls [<cv-filter>]: display both the current cv information (equivalent of cv cu) and cv list (equivalent of cv ls). It
is possible to filter the output of cvls to only show CVs where the CV name or CV attributes match a certain string. The
proxy Id of the CVs can be used in the commands cvrm and cvget. The display of CV proxy Id can be disabled with
command "safe+".
cvls1: similar to the cvls command except that it executes via the OSE shell instead of the MO service.
cvmk <cvname> [<operator>] [<comment>] : create a local cv backup. Operator name and comments (not longer
than 40 characters) can be given as argument.
cvset <cvname>|<cv-Id>: set a cv as startable.
cvms <cvname> [<operator>] [<comment>] : create a cv and make it startable (combination of cvmk and cvset)
cvget[f] <cvname>|<cv-filter>|<cv-Id> [<destdir>] : make a remote backup of a cv to the workstation. The
operation is done with the MO action putToFtpServer unless option "f" has been specified, in which case the transfer will be
done by FTP/SFTP. The second argument is optional. If not given, a default folder is chosen for the backup
~/moshell_logfiles/logs_moshell/cv/<node>/<date>_<time>/
cvgetu <UP> : make a remote backup of all CVs connected to a specific UP (same as cvget but with the UP as
argument).
cvgetd <cvname>|<cv-filter>|<cv-Id> [<destdir>] : download the DB dump (dbdump.zip) for one or more
CVs. This is only applicable for CPP OSE nodes that support the MO action generateDbDump. The DB dump is a text
dump of the db.dat and can be read in SQL mode ("moshell -d /path/to/dbdump.zip") to perform DB consistency check
without need for the Polyview SW.
cvput <zipped-cvfile> : transfer a remote CV backup (zip file) from the workstation to the node. The operation is
done with the MO action getFromFtpServer.
cvrm <cvname>|<cv-filter>|<cv-Id> : remove one or more cv’s. If the argument does not match an existing CV
then all CVs matching that string will be removed. A confirmation message is printed before removal. The CV(s) will
automatically be removed from rollback list when necessary.
cvrmu <UP> : remove all CV’s connected to a specific UP (same as cvrm but with the UP as argument).
cvrbrm : remove one or more cv’s from the rollback list. If the argument does not match an existing CV then all CVs
matching that string will be removed. A confirmation message is printed before removal.
cvfa : activate robust reconfiguration (same as MO action Configuration.activateRobustReconfiguration)
cvfd : deactivate robust reconfiguration (same as MO action Configuration.deactivateRobustReconfiguration)
Command syntax and description (COM):
46
Informational
USER GUIDE 47(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
cvcu : display the current backup information only.
cvls [<cv-filter>] : same as above plus the list of SwVersions, UpgradePackages and BrmBackups. The Id field of
the BrmBackup can be used in the commands cvrm and cvget.
cvmk <cvname> : create a local backup.
cvre <cvname>|<cv-Id> : restore a backup (equivalent to doing a cvset followed by node restart on CPP)
cvrm <cvname>|<cv-filter>|<cv-Id> : remove one or more backups from the node. If the argument does not
match an existing backup then all backups matching that string will be removed. A confirmation message is printed before
removal.
cvrmu <UP> : remove all backups connected to a specific UP (same as cvrm but with the UP as argument).
cvget <cvname>|<cv-filter>|<cv-Id> [<destdir>] : export a backup to the workstation. The second argument
is optional. If not given, a default folder is chosen for the backup
~/moshell_logfiles/logs_moshell/cv/<node>/<date>_<time>/
cvgetu <UP> : export all backups connected to a specific UP (same as cvget but with the UP as argument).
cvput <zipped-cvfile> : transfer a backup (zip file) from the workstation to the node.
cvfa : activate failsafe backup (same as MO action BrmFailsafeBackup.activate)
cvfd : deactivate failsafe backup (same as MO action BrmFailsafeBackup.deactivate)
cvfda : same as cvfd but the Post_failsafe_backup will be added to the RestoreEscalationList
cvfdc : same as cvfda but all SYSCR backups will be deleted and removed from RestoreEscalationList
Examples:
cvls: List all CVs
cvls CXP9011274_R9A: List all CVs using Upgradepackage CXP9011274_R9A
cvms RNC11_Final: Create a cv and make it startable (no userid or comments given)
cvms RNC11_Final eanzmagn cell power increased to 33dBm: Create a cv and make it startable (userid and
comments given)
cvrm Temp: Remove all cv’s whose name match the string "Temp"
cvrm !Final: Remove all cv’s whose name don’t match the string "Final"
cvrm !Final|RNC: Remove all cv’s whose name don’t match the string "final" or the string "RNC"
cvget RNC11_Final: Make a remote backup of a CV to the workstation where moshell is runing
cvget RNC11.*Fi: Make a remote backup of all CVs whose name matches RNC11.*Fi
cvput /home/eric/RNC11_Final.zip: Transfer a remote cv backup from the workstation to the node
cvrm 1-15: Remove the oldest 15 CVs.
cvget 3,5,8: Fetch CV number 3, 5, and 8 from the cv list.
cvset 23 : Set CV number 23 as startable
cvrmu CXP9011274_R9A: Remove all CVs/Backups connected to the UP CXP9011274_R9A
cvgetu CXP9011274_R9A: Export/fetch all CVs/Backups connected to the UP CXP9011274_R9A
cvfa: Activate failsafe/robust configuration
cvfd: Deactivate failsafe/robust configuration
cvfdc: Deactivate failsafe and delete all SYSCR backups (Gen2 only)
4.2.2 inv[hlxbpctrgfa] [<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 and COLI 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.
Options:
The options are used to reduce the number of tables displayed. Without options, all tables are displayed.
h: HW information only.
47
Informational
USER GUIDE 48(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
x: HW, CPRI, and RF information (TX/RX/VSWR and RU to Cell mapping)
xf : same as "x" but without CPRI.
xt : same as "x" but without RF and temperature.
xa : same as "x" but with RU mapping to Antenna/TMA/RET instead of Cell
xaf : same as "x" but with RU mapping to both Cell and Antenna/TMA/RET
xtaf: same as "xaf" but without TX/RX/VSWR/temperature (quicker)
l: licensing information only (feature and capacity licenses)
p: show CPU load of the PlugInUnits: obsolete, replaced by command "lh all procload".
r: re-read the inventory data from the node.
c: print the tables in CSV format
b: show receiver BER values in the CPRI tables
g: display graphical view of CPRI and RF connection (RBS/ERBS/MSRBS)
The first time the command is run, it takes a bit longer because the data has to be fetched from the node before parsing. The
following times the command is run, the existing data is parsed again, unless the rswitch is used ("refresh"), in which case, the
data is fetched again and parsed. When no options are specified, all the information will be displayed except BER and Antenna
(which can be printed with options "b" and "a" respectively).
Arguments:
The first argument (general filter) allows to only show the lines matching the filter string. Negative filter is supported by
putting a exclamation mark in front of the filter. See examples further down.
The second argument (state filter) allows to only show the lines where the MO status matches the state filter.
Printout description:
the first table shows the MP/BP hardware info, position, and status. The GE column (when subrack contains CMXB) shows
the connection status to the 10G IP backplane (attribute EthernetSwitchModule::backPlanePortState), the CE column
(when subrack contains SCXB) shows the connection status to the 1G IP backplane (attribute
ControlSwitch::backPlanePortState). The column "c/p" shows the disk usage on /c or /p (depending if it is a central MP or
regular MP), and the column "/d" shows the disk usage of the /d volume.
the second table shows the AuxiliaryUnits (XP) hardware/software info, status, temperature in Celsius, and uptime in days
("UPT" column).
the third table shows the subracks and backplanes HW info. The switchState field consists of three digits: the state of the
switch, the state of plane A, and the state of plane B.
the next table shows the ISL links. The ISL links are only applicable in nodes containing several subracks, eg RNC/MGW.
All ISL links connecting the main subrack to each extension subrack are shown. The status of each link is shown: 1st digit
corresponds to "operationalStateSync" and the 2nd digit corresponds "operationalStateTraffic". The ports connected to
each ISL are shown, including the type of board (SCB/SXB) and the port state (active/passive).
the next table shows the RDS/DOT inventory. Only applicable for RBS/ENB with IRU (Indoor Radio Unit). The description of
the fields can be found further down in this help.
the next table shows the CPRI links, as well as IDL and IPL links when present (Inter-DU links, Inter-PIMCU links). Only
applicable for RBS/ENB.
the next table shows the RF ports of the radio units, one line per port. See description further down.
the next two tables shows the list of features and capacity and their licensing status
The FAJ numbers are read primarily from the License.xml file on the node and if not found there, they are read from the
excel sheets on https://ericoll2.internal.ericsson.com/sites/SW_License_Handling_Community/SWLicenseHandling/
ELIS/Wiki/License
The information about restricted features is read from the documents 2/22104-FGB101135 and 4/19812-FGB101135.
the next table shows the java loadmodules that are running in the JVM.
the next table shows the configuration and status of the ReliableProgramUniters (RPU).
the last table shows the Programs running in each processor including devices.
Description of the "state" column:
State information is always abbreviated to one digit, in the same way as for other printouts such as stt, stv, str, etc.
1 = unlocked enabled
48
Informational
USER GUIDE 49(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
0 = unlocked disabled
L = locked (opstate could be enabled or disabled)
Description of the LED columns:
FAULT: RED
OPER: GREEN
MAINT: YELLOW or BLUE (old boards use YELLOW, new boards use BLUE)
STAT: YELLOW (only applicable for EvoC)
Description of the fields in the RDS/DOT table (only applicable for RBS/ENB containing IRUs with DOTs):
MO/FRU: the MO name of the AuxPlugInUnit/FieldReplaceableUnit representing this DOT unit
LNH/ID: the linkhandler address and port number (1 to 8) of the IRU to which the DOT is connected
RDS: the product name of the DOT unit
ST: the state of the AuxPlugInUnit/FieldReplaceableUnit MO representing this DOT unit
P: the PowerOverEthernet status. Read from the command eqpm rdPoe status all (1=detected:true,
0=detected:false)
C: the Connection status. Read from the command rdc dump all (1=RD_OPERATIONAL,
0=RD_FAILED/NOT_PRESENT)
T: the LTU status. Read from the command rdsh all hal ltu lock (1=LOCKED, 0=NOT_LOCKED)
TX/RX: the status of the DOT’s TX/RX branch A and B respectively. Read from the command rdc dump all (1=ENABLE,
0=DISABLE)
TEMP: the temperature of the DOT, in Celsius. Read from the command rdsh all temp.
VII: the status of the visual indicator of the DOT. Read from the command rdsh all vind.
FAULT: indicates the presence of alarms on the DOT. Read from the command eqpm rdFault dump
Description of the fields in the CPRI table (only applicable for RBS/ENB):
ID: an arbitrary reference number for the link, also used in the SFP tables.
T: Type. E=Electrical, O=Optical, I=Internal (eg IDL or IPL). For Optical links, there are three additional tables showing the
product information and diagnostics for the SFP’s located at the extremities of each CPRI link (SFP= Small Form-factor
Pluggable transceiver). See description further down.
RiL: the name of the RiLink MO representing this CPRI link.
BPBP: B=Board state, P=Port state. The state of PlugInUnit/AuxPluginUnit/FieldReplaceableUnit MO and RiPort MO on
each side of the CPRI link.
R: Role. M=Master, S=Slave. Master is always on the left hand side Slave on the right.
LENGTH: Cable length. The cable length is obtained from the CPRI link delay value in nanoseconds which is then divided
by 4.9 to obtain the cable length (assuming a delay of 4.9ns per meter of cable, or two thirds of the speed of light)
BER: the counter value of the received Bit Error Rate. NZ=Non-Zero (=> there are Bit Errors on this port).
Description of the fields in the SFP diagnostics table (only applicable for RBS/ENB containing optical CPRI links):
ID: the unique id of the CPRI link which can be used to match against the connection and product information in the above
two tables of the printout.
LINK: indicates if the CPRI link is Up or Down according to the information from the COLI command "ricr".
WL: the wavelength of the laser, in nm.
TEMP: temperature of the SFP in Celsius
TXbs: the TX bias level in percent of the low/high warning thresholds. Calculated with the formula 100 * (Bias - LowLimit) /
(HighLimit - LowLimit). Should not be negative or higher than 100%. Acceptable values are typically in the range of 1% to
50%, depending on SFP vendor.
TXdBm: the transmitted power in dBm
RXdBm: the received power in dBm
BER: the counter value of the received Bit Error Rate. NZ=Non-Zero (=> there are Bit Errors on this port).
DlLoss/UlLoss: the difference in dB between the TX power of the sending port and the RX power of the remote port.
49
Informational
USER GUIDE 50(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Acceptable values should be between -1 dB and +3dB when using short point-to-point connections (length < 200m). When
using longer connections and/or with xWDM filters/splitters then the loss values should be compared according to expected
link budget, taking into account the losses filters/splitters/connectors.
Consistency checks: three checks are performed on the content of the SFP A0 area. Check #1 is the preamble (should be
0304), check #2 is the checksumBase (bytes 2-62->63), check #3 is the checksumExtended (bytes 64-94->95). If any of
these checks fail the VENDORNAME will show FAULTY_SFP and the VENDORPROD will show which of the checks that
failed.
If the CPRI link is down or the SFP voltage is not between 2 and 4V, then some of the diagnostics values will show "NA" ("Not
Applicable").
Description of the fields in the RF ports table
AuxPiu/FRU: the MO name of the AuxPlugInUnit/FieldReplaceableUnit MO representing this radio unit.
LNH: the linkhandler address of the radio unit, can be used to connect to the radio with command "lhsh".
BOARD: the product name of the radio unit
RF: the RF port on the radio unit
BP: B=Board state, P=Port state. The state of the AuxPlugInUnit/FieldReplaceableUnit MO and RfPort MO.
TX (W/dBm): the currently transmitted power in Watts and dBm.
VSWR (RL): the VSWR and Return Loss in dB
RX (dBm): the received power in dBm
Sector: the Sector MO or SectorEquipmentFunction MO connected to the RF port is represented by "SR" or "SE",
respectively. SR is applicable for WRBS, and SE is applicable for ENB and MSRBSv2. If there is an asterisk next to the
SR/SE name, then it means that this sector uses mixedModeRadio.
Cells: for WRBS, shows the RbsLocalCells connected to that RF port and their state and localCellId values. For ENB and
MSRBS LTE, it shows the EUtranCellxDD MO names, and their corresponding state, cellId and PCI values. For MSRBS
WCDMA, it shows the NodeBLocalCell name in the following way: NB=<localcellgroup>/<localcell>/<sectorcarrier> ,
followed by their respective state and localCellId values. For MSRBS GSM, it shows the GsmSector/Trx in the following
way: GT=<gsmsector>/<trx>
AG: the name of the AntennaUnitGroup MO connected to this RF port.
AS: the name of the AntennaSubunit MO connected to this RF port (AS=x/y =>
AntennaUnitGroup=x,AntennaUnit=y,AntennaSubunit=1)
RET/TMA: the name of the AntennaNearUnit MO (RET or TMA) connected to this RF port (RET=x/y or TMA=x/y =>
AntennaUnitGroup=x,AntennaNearUnit=y)
Description of the fields in the graphical view
each box represents a FieldReplaceableUnit (MSRBS) or PlugInUnit/AuxPlugInUnit (RBS/ERBS). Inside each box are the
MO id, the board type, and the link handler. On the side of each box are the CPRI port names. On the bottom of each RU
box are the RF ports and corresponding sector/cells.
each line represents a CPRI connection. On the CPRI connection are listed:
the ID number from the CPRI tables described above. Next to it is the RiLink number when applicable
(MSRBS/ERBS).
the link type (E/O) and bit rate (eg: O25 = Optical 2.5 GB/s).
the length expressed in meters (considering delay of 5 ns per meter), when applicable (MSRBS/ERBS).
+---------+ +----------+
| | A O25 D1 | 2 |
| |-----1/1-----| RRUS11B4 |
| | 181m | BXP_0 |
| | +----------+
| | |A |B
| 1 | SE=1 FDD=1
| DUS3201 |
| 000100 | +-----------+
| | B O25 D1 | 3 |
| |-----2/2-----| RRUS11B13 |
| | 180m | BXP_1 |
| | +-----------+
| | |A |B
50
Informational
USER GUIDE 51(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
+---------+ SE=2 FDD=2
Examples:
inv CXC132055 –> only rows matching CXC132055 will appear. This is convenient to lookup the name of an LM and in
see which boards it is running.
inv : –> only RPU information will be printed.
inv nss –> to see which loadmodules contain the string "nss" and in which boards they are running.
inv . L|0 –> only rows where the state of the MO is locked or disabled will appear.
inv roj L|0 –> only rows matching "ROJ" and where the state is locked or disabled will appear.
inv !program –> only rows NOT matching the word "program" are displayed.
4.2.3 cab[adefghlmrstxc] [ | <unix-cmds> ]
Display of miscellaneous COLI printouts relating to hw, sw, restarts, leds, cpu load, errors, disk/ram usage
This command is only applicable to CPP nodes. On RCS nodes "cab/cabx" aliases to "invx" and "cabr/caba" aliases to "lgg".
The cab command offers a number of options, it is possible to combine several options, eg: cabslxrdg,cablx,cabxs, etc.
The command cabslxrdgm will give the maximum amount of information.
Note: Most options are now obsolete and superceded by other commands such as "inv", "proctemp", "procload", and "fte".
Options:
h: prints MP/BP HW info and led status, MP temperature, and coreMgr status. If no options are given then this is the
default option. Superceded by "inv" and "proctemp" commands.
t: same as "h" but without the temperature, nor the TX/VSWR values (in RBS/ENB)
x: same as "h" plus led and hw info for the XP boards (eg: TMA, MCPA, Fans, RU, RRU, etc.). With option "c" ("cabxc") the
output is in CSV format. Superceded by "inv" command.
s: same as "h" plus list of programs running in all MP/BP. Superceded by "inv" command.
r: prints all MP/BP restarts grouped by board. To see this info in chronological order, use the command "lgg". Abnormal
restarts are highlighted in red.
a: prints only abnormal MP/BP restarts.
d: print disk usage. Disks that are getting over a certain limit will appear in color. The limit can be defined in cabview file.
f: print disk and flash usage.
g: print MP/BP HW errors (e.g. faulty disk, faulty RAM, etc).
m: print MP/BP RAM memory usage.
e: print MP/BP added T&E trace conditions. Superceded by fte s command.
l: MP/BP/SP processor load. Superceded by procload command.
The following OSE commands are run and parsed by the various "cab" functions:
h:pboot sh par, vii, mirror s, ppctemp, boardtemp
t:pboot sh par, vii, mirror s
x:pboot sh par, vii, mirror s, ps port*, par get SYS_HW*, listObj subrack, getAttrObj subrack, warpA/warpB read, warp3
txpwr, fui get temp, fui get vswr
s:pboot sh par, vii, mirror s, listloaded
l:pboot sh par, capi prio, capi core all
r:llog -l
a:llog -l Only restarts with error code not matching 0xB0AD or 1010[9-F] or containing a PMD are printed
d/f:vols, ls /d/loadmodules
g:pboot sh par, dumpelg
m:pboot sh par, mmu, mm -p
e:pboot sh par, te s, te s -restart
51
Informational
USER GUIDE 52(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Note 1: Regarding the CoreManager status: If a board has got a CoreManager status, it means that the board is running the
Core Manager programs (EqmMgr, Database, LoaderServer). If the node is configured with Fault Tolerant Core, there are two
boards running the Core Manager functionality. One board is Active and the other one is Standby.
When the node is configured with Fault Tolerant Core, the /c drive is mirrored between the two Core Manager boards.
If the status of the Standby board is StandbyReady, then it means that the /c drive is correctly mirrored and the standby board
can take over the active role at any time, in case the active board fails or restarts.
If the status of the Standby board is StandbyWriting, then it means that the /c drive is performing a small update and the standby
board can take over in a short while, as soon as the disks are updated.
If the status of the Standby board is StandbySync, then it means that the /c drive is performing a complete update and the
standby board will not be able to take over until this is completed. The progress is shown as a percentage value (eg:
StandbySync-56%).
Note 2: When many commands are to be sent, the cab function will put them into a command file, transfer that file (via (s)ftp) to
the node and run that file from within the node, using the shell -f command.
This will save time instead of having to send each command one by one to the node.
There is a user variable called fast_cab_threshold which determines the number of boards in the node above which a command
file will be transferred to the node.
See Section 2.5 and the moshell file for more info about user variables.
Note 3: Regarding PMD Ids appearing in cabr/caba:
A Post-Mortem Dump (PMD) may be associated with an abnormal board restart. In this case, the PMD Id is shown in cabr/caba
commands. It is possible to show and collect the PMD files with the command lgp. Alternatively the commands
dump list -a,ftreef /c/pmd, or lg1 can also be used to show the PMD files.
Note4: Regarding TX power calculation in "cabx":
For RU PL4:
TXPwrA=(DL_PM_PA0_C0+DL_PM_PA0_C1+DL_PM_PA0_C2+DL_PM_PA0_C3)*16384*powerClassA/(1228800*8491396)
TXPwrB=(DL_PM_PA0_C0+DL_PM_PA0_C1+DL_PM_PA0_C2+DL_PM_PA0_C3)*16384*powerClassB/(1228800*8491396)
Where:
DL_PM_PA0_Cx are read from RU COLI commands "warpA read" for TXA och "warpB read" for TXB
powerClass is read from RU COLI command "db list *currentPowerClass", or "txm rh all wrk dump"
For RU PL5:
TXPwrA=pwrClassA *268435456/8491396 *( 10^(B0/10) + 10^(B1/10) + ... + 10^(B7/10) )
TXPwrB=pwrClassB *268435456/8491396 *( 10^(A0/10) + 10^(A1/10) + ... + 10^(A7/10) )
Where:
A0 to A7 and B0 to B7 are read from RU COLI command "warp3 txpwr" or "warp:0/warp:1 txpwr"
powerClass is read from RU COLI command "db list *currentPowerClass", or "txm rh all wrk dump"
Note5: Regarding RSSI measurement in "cabx" for WRBS:
The RSSI is value is read from the MP trace bus_receive on CDCI_TR. A asterisk in front of a TrDevice in the printout indicates
that this TrDevice has reported a measurement. TrDevices without asterisk could be due to that this is a TX or that the cell is
disabled.
Note6: Regarding VSWR measurements in "cabx":
For most RUs/RRUs, the main command used for printing the return loss is fui get vswr <tx>. On AIR21, AIR32, RUS12m,
and mRRUS12, the command used is fuia get antquality <tx> and does not show the return loss but an antenna
connection quality indicator value ranging from 1 to 5, where 1 is bad, and 5 is good.
Note7: Refreshing of the cache.
The cab command reads most of its data from the node each time it is executed. However there is some static data such as
board list and cell list which is read only once and then kept in a cache. If this information has changed during the session, it is
possible to refresh the cache by running the "bor" command.
Note8: DU Temperature is read with:
DUW10/20/30: trace4 on process SriBcThread, sensor3 (0x4B)
DUW11/31/41: coli command readPower, sensor 1 (0x4D)
52
Informational
USER GUIDE 53(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
DUL20/21: coli command boardtemp, sensor0
DUS31/41/ODS: coli command boardtemp, sensor1
4.2.4 sdi[eacr]
System Diagnostics CPRI.
Perform a system diagnostics test of the RBS/ENB CPRI links.
Options:
e : show the Cells connected to each CPRI link.
a : show any alarms associated with each CPRI link (only applicable for ENB and MSRBSv2, not WRBS Gen1).
c : print the tables in CSV format
r : re-read the data from the node.
Printout format, first table
Each line in this table represents a CPRI link.
ID: arbitrary number to identify the CPRI link
RiL: MO name of the associated RiLink (only applicable for ENB/MSRBS, not WRBS)
Type: E=Electrical, O=Optical, 25=2.5Gb/s , 49=4.9Gb/s, 98=9.8Gb/s, 103=10.3Gb/s
Res: the result of the test, OK, NOK (Not OK), OKW (OK with Warning), NT (Not Tested = when a port or board on the link
is locked)
MO1-MO2: a shortened LDN of the CPRI port MO on each side of the link
BOARD1-BOARD2: the board type on each side of the link
AlmIDs: the list of alarms associated with the RiLink, RiPorts or FRU/PIU/AuxPius connected to the link (only applicable on
ENB/MSRBS)
Cells: the list of Cells (EUtranCell, NodeBLocalCell, RbsLocalCell, GsmTrx, etc) associated with any radios connected to
the link
Issue: a short description of the test result including information about which particular checks failed.
=================================================================================================================================
ID ;RiL ;Type ;Res ;MO1-MO2 ;BOARD1-BOARD2 ;AlmIDs ;Cells ;Issue (Failed checks)
=================================================================================================================================
1 ;1 ;O98 ;OK ;1/1(A) 1/1/RU-1-1(D1) ;DUS4102 RRUS82B41 ; ;TDD=1 TDD=2 ;Passed
2 ;2 ;O98 ;NOK ;1/1(B) 1/1/RU-1-1(D2) ;DUS4102 RRUS82B41 ; ;TDD=1 TDD=2 ;Fiber Loss DL (DlLoss-UlLoss=4.5)
3 ;3 ;O25 ;OK ;1/1(C) 1/2/RU-1-2(D1) ;DUS4102 RRUS62B41D ; ;TDD=3 ;Passed
4 ;4 ;O98 ;NOK ;1/1(D) 1/3/RU-1-3(D1) ;DUS4102 RRUS62B41D ;1,2 ;TDD=4 ;Fiber BER DL (BER2=NZ)
...
15 ;13 ;O25 ;OKW ;XMU03(11) RRU-101(D1) ;XMU03 RRUS12B2 ; ;FDD=9A_1 ;Conditionally Passed (Unable to read Far-end SFP data.)
---------------------------------------------------------------------------------------------------------------------------------
Printout format, second table
This table is only printed if the option "a" was given and if there are alarms affecting CPRI links.
Each line in this table represents an alarm, could be an active alarm, or a past alarm that has been toggling during the past 24
hours
AlmID: an arbitrary number to identify the alarm, this number is found next to one or more CPRI links in the first table
IDs: the list of CPRI link IDs that have this alarm
RiLs: the list of RiLink MOs that correspond to the CPRI link IDs
Status: A=Active, if the alarm is still active. T=Toggling, if the alarm is not active but has been toggling in the past 24 hours.
In case of toggling alarm, it will show how many times the alarm has toggled and how many hours/minutes ago was the last
time since the alarm toggled.
=====================================================================================================================================
AlmID ;IDs ;RiLs ;Status ;Alarm
=====================================================================================================================================
1 ;4 ;4 ;T 8x 12h28m ;Link Degraded - RiLink=4 (High BER at far end of the link. Near end port:PlugInUnit=1,RiPort=D (transportType=NOT_SET))
53
Informational
USER GUIDE 54(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
2 ;4 ;4 ;T 8x 12h30m ;Link Degraded - RiLink=4 (High BER at near end of the link. Near end port:PlugInUnit=1,RiPort=D (transportType=NOT_SET))
-------------------------------------------------------------------------------------------------------------------------------------
=====================================================================================================================================
AlmID ;IDs ;RiLs ;Status ;Alarm
=====================================================================================================================================
1 ;5 ;5 ;A ;Inconsistent Configuration - FieldReplaceableUnit=6 (No hardware detected for the configured FieldReplaceableUnit )
2 ;6 ;6 ;A ;Inconsistent Configuration - FieldReplaceableUnit=7 (No hardware detected for the configured FieldReplaceableUnit )
3 ;5 ;5 ;A ;Link Failure - RiLink=5 (No signal detected (link start time-out). ManagedElement=1,Equipment=1,FieldReplaceableUnit=1,RiPort=E (transportType=NOT_SET) )
4 ;6 ;6 ;A ;Link Failure - RiLink=6 (No signal detected (link start time-out). ManagedElement=1,Equipment=1,FieldReplaceableUnit=1,RiPort=F (transportType=NOT_SET) )
5 ;1,2,3,4,5,6 ;1,3,5,2,4,6 ;A ;Hardware Failure Imminent - Subrack=1,Slot=1,PlugInUnit=1 (HDFault, Read sector Failure)
-------------------------------------------------------------------------------------------------------------------------------------
Printout format, third table
This table is only printed if some CPRI links failed the test.
Each line in this table represents a particular type of issue.
IDs: the list of IDs for the CPRI links that had a issue of this type
RiLs: this list of RiLink MOs corresponding to each CPRI link listed in the IDs column (only applicable for ENB/MSRBS, not
WRBS)
Issue and Recommended Action: a longer description of the problem, followed by some recommendations for corrective
actions for each type of issue.
=================================================================================================================================
IDs ;RiLs ;Issue and Recommended Actions.
=================================================================================================================================
2 ;2 ;Fiber Issue - Far End Reports Excessive Optical Power Loss.
-------------------------------------------------------------------------------------------------------------------------------------
1) Troubleshoot to determine where optical power is being lost or Bit Errors are detected. Start at the port fiber connection reporting the loss and work back to the transmitter on the other end. (i.e. dirty, damaged or bent fiber, improperly mated connection)
2) Refer to and follow Ericsson CPI "Handling SFP Modules and Optical Cables" for proper handling, Cleaning, inspection and testing of fiber and optical interfaces.
*************************************************************************************************************************************
4 ;4 ;Fiber Issue - Far End Reporting Bit errors.
-------------------------------------------------------------------------------------------------------------------------------------
1) Troubleshoot to determine where optical power is being lost or Bit Errors are detected. Start at the port fiber connection reporting the loss and work back to the transmitter on the other end. (i.e. dirty, damaged or bent fiber, improperly mated connection)
2) Refer to and follow Ericsson CPI "Handling SFP Modules and Optical Cables" for proper handling, Cleaning, inspection and testing of fiber and optical interfaces.
*************************************************************************************************************************************
4.2.5 stc[p][r] [<Filter>] [<stateFilter>]
Display state and configuration of Atm/Tdm CrossConnections.
The filter allows to only show the rows matching the filter string. The stateFilter allows to only shows the MOs matching the state
filter.
The first time the command is run, it takes a bit longer because the data has to be fetched from the node before parsing. The
following times the command is run, the existing data is parsed again, unless the rswitch is used (refresh), in which case, the
data is fetched again and parsed.
The first field is the MO id of the Atm/Tdm CrossConnection.
The second field is the state information, consists of five digits:
1st digit: operationalState of the Atm/Tdm CrossConnection MO (0=disabled, 1=enabled)
2nd and 3rd digits: operationalState of the VclTp MOs (A and B side).
4th and 5th digits: only applicable if "p" option was used. Shows the status of the pget on VclTp MOs (A and B side). Set to
0 if the transmittedCells counter has incremented but the receivedCells counter has not incremented within a given time
period (by default 25 seconds, can be changed in the uservariable pm_wait): this indicates that there is no response from
the remote end.
The third and fourth field are the MoId for VclTpA and VclTpB, abbreviated in the following way: AtmPortId/VplTpId/VclTpId
The fifth and sixth fields are the actual Vpi/Vci value for VclTpA and VclTpB. Can be useful in case the MoId of the VclTp does
not match the Vpi/Vci value.
The seventh and eigth fields are the MoId for the traffic descriptor of VclTpA and VclTpB.
The last field is the userLabel of the AtmCrossConnection MO.
54
Informational
USER GUIDE 55(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Note: in the case of TdmCrossConnections, the third and fourth fields show the Timeslot in the Ds0Bundles A and B. The fifth
and sixth fields show the Moid of the Ds0Bundle A and B.
Examples:
1. stc 2051 - show all crossconnections where the information matches "2051" (in the case below, where the atmport is
2051)
2. stc .*0- show all crossconnections that are not working properly.
Printout format, AtmCrossConnection:
=========================================================================================================================
CCId CSSPP VclTpA VclTpB Vp/VcA Vp/VcB TD-A TD-B UserLabel
=========================================================================================================================
MGTS44500_MSC6_AAL2a 11110 2041.*1.*501 2071.*1.*501 1/501 1/501 C2P12000 C2P12000 MGTS44500_MSC6_AAL2a
MGTS44500_MSC6_AAL2b 11111 2041.*1.*502 2071.*1.*502 1/502 1/502 C2P12000 C2P12000 MGTS44500_MSC6_AAL2b
SOLVER44800_MSC6_AAL2a 10101 2051.*1.*136 2071.*3.*512 1/136 3/512 C2P12000 C2P12000 SOLVER44800_MSC6_AAL2a
MGTS45600_MSC9_AAL2a 11100 2052.*1.*300 2041.*1.*300 1/300 1/300 U2P3520M3520 U2P3520M3520 MGTS45600_MSC9_AAL2a
Printout format, TdmCrossConnection:
=========================================================================================================================
CCId CSS TSA TSB Ds0A Ds0B UserLabel
=========================================================================================================================
1192_1191_ts16 101 1 1 1,Slot=27.*E1.*=1277,Ds0.*=127702 1,Slot=27.*E1.*=1276,Ds0.*=127602 TS 16 127702_port1191
4.2.6 std[ar] [<filter>]
Display state and configuration of devices (RNC and MGW only).
Argument (optional):
Only lines matching the filter will be displayed. If no argument, all lines are displayed.
Example:
std fax - show fax devices (mgw)
std pdr - show pdr devices (rnc)
std 0020 - show devices on board 0020
Options:
r: to refresh the printout. In MGW the device data is locally cached and updated when the "r" option is given. This is the
same behavious as in commands such as bo, stc, stt, stv, inv, etc. In RNC, the "r" option forces moshell to re-check the
device to module relationship. All other data is refreshed each time, even without the "r" option.
a: to fetch some additional device usage information.
std on MGW
The first table (only printed with option a) shows the DSP SW and usage for each MSB board. The GMD field indicates the status
of the GRA-GPB ("G"), the MSB ("M") and DSPs ("D"). The GRA-GPB and MSB status correspond to the state of the
corresponding PlugInUnit: L=locked, 1=enabled, 0=disabled. The DSP status is found from the command pingdsp on MSB3
and mmpp pingdp on MSB4. The DSP SW is found from the command rev on MSB3 and mmpp dspc devt on MSB4. The
DeviceType and all remaining fields are found from the command gradsl on GRA-GPB:
Set = DevSetNr : device set id
ResId = resourceId
nRes = nrOfResources : total nr of allocated resources for this device set
nIdle = nrOfIdle : nr resources not in use
graCap = graRdCapacity : available capacity expressed in PUs available for normal calls
dspCap = dspRdCapacity : rdScaledCapacity (reported by DSP and used by MFD only) is available devices
expressed as remaining PUs
totCap = rdCapacityTot : total capacity expressed in PUs (reported by RD in attachCfm)
rej = nrTimeoutRej : number of rejected requests because of 30+30ms + 1 sec DSP supervision timer timeout.
At this point DSP is marked as failed
nRest = nrGraOrderedDspRestarts : number of GRA ordered DSP restarts because of 30+30ms + 1+10 sec DSP
supervision timer timeout
dupCep = nrOfDupCeps : current number of duplicated CEPs in this RD
More info found in gradsl printout description in M-MGw Traffic Control Troubleshooting Guideline 25/1553-AXM 101 01/7
55
Informational
USER GUIDE 56(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
======================================================================================================================================
Sr Slot Lnh Board GRA DSP GMD DeviceType SW Set ResId nRes nIdle graCap dspCap totCap rej nRest dupCep
======================================================================================================================================
3 7 730700 MSB3 7304 1 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 2 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 3 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 4 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 5 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 6 111 MPC CXC1327801/8_R3D01 326 11088 24 24 55542 55542 55542 0 0 0
3 7 730700 MSB3 7303 7 111 IM CXC1327799/8_R3E01 327 100 100
3 7 730700 MSB3 7304 8 111 CSD_GSM_MFH CXC1327794/8_R3D01 328 11112 36 36 55650 55650 55650 0 0 0
3 7 730700 MSB3 7304 9 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 10 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 11 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 12 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 0 0 0
3 7 730700 MSB3 7304 13 111 CSD_DIGITAL CXC1327791/8_R3D01 329 11148 16 16 55650 55650 55650 0 0 0
3 7 730700 MSB3 7304 14 111 CSD_DIGITAL CXC1327791/8_R3D01 329 11148 16 16 55650 55650 55650 0 0 0
3 7 730700 MSB3 7304 15 111 CSD_MODEM CXC1327792/8_R3D01 330 11180 16 16 55650 55650 55650 0 0 0
3 7 730700 MSB3 7304 16 111 CSD_FAX CXC1720519/8_R3D02 331 11196 5 5 55650 55650 55650 0 0 0
The second table shows the device status and availability for each MSB board.
The MD field indicates the status of the MSB ("M") and DSPs ("D").
The MSB status corresponds to the state of the corresponding PlugInUnit: L=locked, 1=enabled, 0=disabled.
The DSP status is found from the command pingdsp on MSB3 and mmpp pingdp on MSB4. If all DSPs are ALIVE, the state is
1, otherwise it is 0.
The remaining fields are read from the action getBoardDetails on MsDeviceGroup:
nDev = nrOfRds : The number of Root Devices (RD) on the board, configured with the same devices (set of services)
as pointed out by the deviceType attribute.
%Lock = capacityDependencyLockedDev : The fraction (
%Dis = capacityDisabledDev : The fraction (
maxDev = maxNrOfDev : A theoretical maximum number of configured devices on the board.
More info in MOM "mom dev getboarddetails".
===========================================================================================
Sr Slot Lnh Board MD SwAllocation DeviceType nDev %Lock %Dis maxDev
===========================================================================================
3 7 730700 MSB3 11 MGW_MSB3_Profile_16 CSDDigital 2 0 0 32
3 7 730700 MSB3 11 MGW_MSB3_Profile_16 CSDGSMFH 1 0 0 36
The third table shows the device status and availability for each device pool.
In MGW R2/R3, the usage is given as a number, in MGW R4, it is given as a percentage.
======================================================================
DevPool Total %Idle %Busy %Failed %DepLock %DepFail
======================================================================
CSDDigitalPool 256 100 0 0 0 0
CSDGSMFHPool 288 100 0 0 0 0
CSDModemPool 128 100 0 0 0 0
std on RNC
Shows the configuration, status and usage of RNC devices, CC, DC, PDR.
State information is abbreviated in the following way:
1 = unlocked enabled
0 = unlocked disabled
L = locked (enabled or disabled)
I = idle (the device is not handling calls)
A = active (the device is handling calls)
B = busy (the device is fully used and cannot handle more calls)
Options:
r: re-read the device configuration information. Without r, only device state and usage is updated.
a: show additional device information relating to the device usage. Note: the use of this option means the moshell will run
the command drh_dcrh_topdata all which may cause module restart on certain RNC SW releases, see TR
WRNae26272. If the RNC is running a SW release containing the correction of TR WRNae26272, then it is safe to run
stda. Otherwise, just run std without the aoption.
The correction for this TR is included in RNC SW P6.1.4 (CXP9012842_R3BD) and P7.0.1 (CXP9012995_R6CF).
56
Informational
USER GUIDE 57(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Printout description for device tables:
Note: some of the fields are only shown when running option a(stda).
Common fields:
The MOD and GPB column show the module MP controlling the device.
The SPM and DEV columns show the MO id of the Spm and Device MOs.
The G column shows the state of the module MP (GPB).
The D column shows the state of the Device MO.
The S column shows the state of the Spm MO.
The U column shows the usageState of the Device MO.
CC device specific fields:
--------------------------------------------------------------------------------------
TYP MOD GPB SPB SPM DEV GDS U LNH CPU UEs Cells(DRH/CCS/max)
--------------------------------------------------------------------------------------
CC 4 ES1-15 SPB21 ES1-10-1 ES1-10-1 111 A 011000/sp0.lnh 18% 5 52 52 96
....
CPU shows the CPU load of the Device and is read from the variable spCpuLoad in the drh_ccrh_topdata printout in
module MP.
UEs shows the number of UEs handled by the device and is read from the uelist printout in CC SP.
Cells/DRH shows the number of Cells handled by the device and is read from the drh_ccrh_topdata printout in
module MP.
Cells/CCS also shows the number of Cells handled by the device but it is read from the celllist command in CC SP.
Cells/max shows the maximum number of Cells supported by the device (shown on RNC >= P7) The two values
Cells/DRH and Cells/CCS should always be the same, otherwise it indicates a discrepancy between DRH and CCS.
DC device specific fields:
-------------------------------------------------------------------------------------------------------
TYP MOD GPB SPB SPM DEV GDS U LNH CPU Res HsUEs UEsDcs UEsDch UEsDrh gbrResourcePoints
-------------------------------------------------------------------------------------------------------
DC 1 MS-14 SPB21 MS-19-5 3 111 A 001900/sp4.lnh 26% 10% 14 22 15/150 16/150 530/5100
DC 1 MS-14 SPB21 MS-20-3 4 111 A 002000/sp2.lnh 34% 11% 23 22 21/150 23/150 540/5100
....
CPU is read from the variable cpuLoad in the drh_dcrh_topdata printout in module MP.
Res is the percentage of resourcePoints used out of maxResourcePoints (read from drh_dcrh_topdata all)
UEsDcs is read from the uelist printout in DC SP.
the following columns are read from the drh_dcrh_topdata all printout in module MP: HsUEs–>noOfHsCapableUes,
UEsDch–>noOfUesOnDch/maxNoOfUesOnDch,UEsDrh–>noOfUesOnDch/maxNoOfUesOnDch,
gbrResourcePoints–>gbrResourcePoints/maxResourcePoints.
UEs/DCS is read from the uelist printout in DC SP.
PDR device specific fields:
-------------------------------------------------------------------------------------------------------
TYP MOD GPB SPB SPM DEV GDS U LNH CPU UEs RABs aal5 usedCapacity
-------------------------------------------------------------------------------------------------------
PDR 1 MS-14 SPB21 MS-19-1 MS-19-1 111 A 001900/sp0.lnh 3.7% 55 406 95 3796/215000
...
CPU is read from the command spp -p xxxx00/spx.lnh sp procload 1 on central MP or capi prio and
capi core 0 on PDR devices (depending on RNC SW release)
UEs is read from the uelist printout in PDR SP.
RABs and aal5 correspond to the variables noOfRabs and noOfAal5Conns in the drh_pdrrh printout in module MP.
usedCapacity is read from usedCapacity/maxCapacity in drh_pdrrh in module MP.
Module summary table:
These table show the device usage on module basis.
The fields are the same as in the tables above except for the DC summary table which contains some additional fields, read from
the printout lh mod drh_trbr_data:
ATM: noOfAtmTrBr
57
Informational
USER GUIDE 58(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
IP: noOfAtmToIpTrBr
BEE: noOfBeesTrBr
Also in the CC summary table, the field "max" is replaced by the field "GPB" which indicates the number of cells that are handled
by the GPB of that RncModule. The field "GPB" is read via the attributes IubLink::rncModuleRef and IubLink::reservedBy
SPB summary table:
In this table we get an overview of all the SPB boards, their device states, usage, and module allocation.
The State column shows first the state of the SPB PlugInUnit, then the state and usage of its devices.
The Module column shows which module is handling each device.
--------------------------------------------------------------------------------
Sr Slot Lnh Board SwAlloc Type State Usage Module
--------------------------------------------------------------------------------
MS 19 001900 SPB21 SPB_TYPE_A PCDDD 1-11111 AAAAA 1 1 13 8 8
4.2.7 stv[b][r] [<Filter>] [<stateFilter>]
Display state, user, and bandwidth usage for ATM ports and channels.
Options:
b: to get the bandwidth usage for AtmPorts. Requires running some COLI commands.
r: to refresh the data (ie. re-read from node).
Arguments:
the first argument matches on the whole line
the second argument matches only the state field ("VU")
Examples:
stvb ms-6-1 print ATM data for AtmPort=MS-6-1 and all VPs/VCs underneath it
stv p4500 print ATM data for all VPs/VCs using a traffic descriptor with peak cell rate 4500
stv . 0|L print all Ports/VPs/VCs with state disabled or locked
Printout format:
The field ResrvBw/TraffDesc shows:
the AtmTrafficDescriptor for VclTp MOs. For VC’s used by Aal2Path, the Aal2 QoS is shown in brackets.
the reserved bandwidth (in cells/s) for AtmPort and VplTp MOs. E.g. 353000/353207 means 353000 cells/s reserved
out of 353207 available. The available bandwidth for AtmPort is obtained from the COLI command
aet_atmmp etatmportfro <fro> and is only shown when option bis specified. The reserved bandwidth for
VplTp is obtained from the traffic descriptor of VplTp (total bandwidth) and the sum of the traffic descriptors of VclTp
(used bandwidth). The cellrate used by a traffic descriptor is the PeakCellRate in case of CBR and the
MinimumCellRate for UBR/UBR+.
The field User shows the MO using the VclTp. For Aal2PathVccTp MOs, the information in brackets shows the aal2PathId
and reserving Aal2Ap. For PacketDataRouter MOs, the information in brackets shows the PdrDevice position, the
Aal5TpVccTp MOid, the rncIpAddress, and the cnIuLinkIpAddress. For Mtp3bSl MOs, the information in brackets shows
the SignallingLinkCode (SLC), the linkState, the proceduralState, and the usageState, same as in stt printout. Refer to stt
help for more info about the Mtp3bSl information.
The field Mshows the RncModule handing the User.
The field VU shows the state of the VP/VC followed by the state of the User. L=locked, 0=disabled, 1=enabled. E.g. VU=10
means that the VclTp is enabled but the User MO is disabled. For Aal2PathVccTp MOs, there is an extra digit which
represents the remoteBlockingState (0=remotely_blocked, 1=remotely_unblocked, ?=undefined). Note that the
remoteBlockingState is not shown when the Aal2PathVccTp is locked. For PacketDataRouter MOs, there is an extra digit
which represents the state of the PdrDevice MO.
Example printout:
======================================================================================================================
VclTp VPI/VCI ResrvBw/TraffDesc VU M User
======================================================================================================================
AtmPort=MS-6-1 / 1 ---------------------------------------
AtmPort=MS-6-1,VplTp=1 2 224000/353000 1 ---------------------------------------
AtmPort=MS-6-1,VplTp=1,.*VclTp=vc34 2/34 U3P4500M3000 11 Mtp3bSpItu=Iu1,Mtp3bSls=Iuc-1-2300-3,Mtp3bSlItu=1
AtmPort=MS-6-1,VplTp=1,.*VclTp=vc50 2/50 U3P4500M3000 11 Mtp3bSpItu=Iu1,Mtp3bSls=Iup-2-2810-3,Mtp3bSlItu=1
58
Informational
USER GUIDE 59(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
AtmPort=MS-6-1,VplTp=1,.*VclTp=vc90 2/90 C2P12000(AB) 111 1 Aal2PathVccTp=Iu1-1-1 (1, Aal2Ap=Iu1)
AtmPort=MS-6-1,VplTp=1,.*VclTp=vc91 2/91 C2P12000(AB) 111 1 Aal2PathVccTp=Iu1-1-2 (2, Aal2Ap=Iu1)
...<cut>...
AtmPort=MS-6-1,VplTp=1,.*VclTp=Pdr1Gtpu1 2/230 U3P66600M5000 11 RncModule=1,PacketDataRouter=Pdr1Gtpu1
AtmPort=MS-6-1,VplTp=1,.*VclTp=Pdr1Gtpu2 2/231 U3P66600M5000 11 RncModule=1,PacketDataRouter=Pdr1Gtpu2
AtmPort=MS-26-1 / 1 ---------------------------------------
AtmPort=MS-26-1,VplTp=1 1 13804/14650 1 ---------------------------------------
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc34 1/34 C1P5 11 1 IubLink=1,NodeSynchTp=1
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc35 1/35 C1P5 11 1 IubLink=1,NodeSynchTp=2
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc36 1/36 U3P1000M80 11 1 IubLink=1,NbapCommon=1
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc37 1/37 U3P1000M80 11 1 IubLink=1,NbapDedicated=1
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc38 1/38 U3P1000M80 11 1 Aal2Sp=1,Aal2Ap=Iub1
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc39 1/39 C2P6657(AB) 111 1 Aal2PathVccTp=Iub1-1 (101, Aal2Ap=Iub1)
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc40 1/40 C2P6657(AB) 110 1 Aal2PathVccTp=Iub1-2 (102, Aal2Ap=Iub1)
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc43 1/43 U3P1000M80 11 1 IubLink=1,NbapCommon=1
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc44 1/44 U3P1000M80 11 1 IubLink=1,NbapDedicated=1
AtmPort=MS-26-1,VplTp=1,.*VclTp=vc45 1/45 U3P1000M80 11 1 Aal2Sp=1,Aal2Ap=Iub1
...<cut>...
4.2.8 stt[r] [<Filter>] [<stateFilter>]
Purpose: Display state and user of Physical Ports and Ds0Bundles.
Options:
r: to refresh the data (ie. re-read from node).
Arguments:
the first argument matches on the whole line
the second argument matches only the state field ("PUI")
Examples:
stt ms-26-1 print all ports and their users matching ms-26-1
stt . 0|L print all ports and their users who have state disabled or locked
stt mtp3 busy print all mtp3 links that are in usage state busy
stt mtp3 deact print all mtp3 links that are in linkstate deactivated
Printout format:
PUI : the first digit represents the state of the PhysicalPort/Ds0Bundle. The second digit (if present) represents the state of
the User. The third digit (if present) represents the state of the intermediate layer which can be IMA (when user is AtmPort)
or MTP2 (when user is Mtp3bSl). L=locked, 1=enabled, 0=disabled.
CG/KLM: circuit group and K.L.M (for channelised STM-1)
SLC/PCM: SignallingLinkCode for Mtp3bSl or pcmSystemNr for TdmTermGrp
User : the layer that is using the physical port. Usually an AtmPort in Utran nodes. Can also be a TdmTermGrp or an
Mtp3bSl in MGW. In case of Mtp3bSl, the linkState, proceduralState, and usageState are also shown.
Example printout RXI:
======================================================================================================================
Port CG/KLM PUI USER
======================================================================================================================
Subrack=MS,Slot=7,..*,Os155SpiTtp=pp1,Vc4Ttp=1 11 AtmPort=MS-7-1
...
Subrack=MS,Slot=24,.*,Os155SpiTtp=pp1,Sts1SpeTtp=1,Vt15Ttp=1,T1Ttp=1 1/1.1.1 11 AtmPort=MS-24-1-1-1
Subrack=MS,Slot=24,.*,Os155SpiTtp=pp1,Sts1SpeTtp=1,Vt15Ttp=2,T1Ttp=1 1/1.1.2 111 AtmPort=MS-24-ima1
Subrack=MS,Slot=24,.*,Os155SpiTtp=pp1,Sts1SpeTtp=1,Vt15Ttp=3,T1Ttp=1 1/1.1.3 111 AtmPort=MS-24-ima1
Example printout MGW:
======================================================================================================================
Port CG/KLM SLC/PCM PUI USER
======================================================================================================================
2,Slot=25,.*,E1PhysPathTerm=2251,Ds0.*=22511 1 LL TdmTermGrp=E1_MSC3_Slot25_Port1_TS1-29_31
2,Slot=25,.*,E1PhysPathTerm=2252,Ds0.*=22521 2 1L TdmTermGrp=E1_MSC3_Slot25_Port2_TS1-29_31
2,Slot=25,.*,E1PhysPathTerm=2253,Ds0.*=22531 3 11 TdmTermGrp=E1_MSC3_Slot25_Port3_TS1-29_31
2,Slot=25,.*,E1PhysPathTerm=2253,Ds0.*=22532 0 111 Mtp3bSpItu=2.*Sls=msc3.*SlItu=msc3_0 (available,initialized,active)
2,Slot=25,.*,E1PhysPathTerm=2254,Ds0.*=22541 4 11 TdmTermGrp=E1_MSC3_Slot25_Port4_TS1-29_31
4.2.9 ste[gr] [<Filter>] [<stateFilter>]
Purpose: Display state and configuration of Ethernet Ports.
Options:
r: to refresh the data (clear cache and re-read from node).
g: to print the RSTP tree in graphical format.
Arguments:
59
Informational
USER GUIDE 60(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
the first argument matches on the whole line.
the second argument matches only the state field ("S12" or "STL")
Command examples:
ste !nolink : show all lines except those containing the word "nolink"
ste . 0|L : show all lines containing a resource whose state is disabled or locked
ste forwarding : show all lines containing the word "forwarding"
Printout format, first table: This tables shows the properties for ethernet ports where IP distribution is performed, ie, where
IpInterfaces are defined. Each line corresponds to a GigabitEthernet MO (ETIPG/ETMFG) or a InternalEthernetPort MO
(ETMFX). Each column corresponds to an attribute of these MOs. Refer to the MOM for more detail on each attribute.
Position: the subrack, slot, and port number - GigaBitEthernet::portNo or 0 for InternalEthernetPort
Speed: GigaBitEthernet::actualSpeedDuplex
Conf: GigaBitEthernet::configuredSpeedDuplex
AutoNg: GigaBitEthernet::autoNegotiation
Mastr: GigaBitEthernet::masterMode
Prot: GigaBitEthernet::protectiveMode
DfRSw: GigaBitEthernet::defRoutersLinkSwitch
S: GigaBitEthernet::administrativeState&operationalState (0=unlocked&disabled, 1=unlocked&enabled, L=locked)
1: GigaBitEthernet::link1State
2: GigaBitEthernet::link2State. Note: this attribute is not applicable on EPB and will be shown as -.
ActiveLink: GigaBitEthernet::activeLink
Link: GigaBitEthernet::linkType
Frame: GigaBitEthernet::frameFormat or InternalEthernetPort::frameFormat
Vlans: the list of vlan ids for all IpInterfaces defined on that port (read from attribute vid or vlanRef on the children
IpInterface MOs). A vlan id value of -1 means that vlan is not used on that port ("vlan=false")
DscpPbitMap: GigaBitEthernet::dscpPbitMap or InternalEthernetPort::dscpPbitMap (only the pbit values are listed)
Example:
====================================================================================================================================
Board Position Speed Conf AutNg Mastr Prot DfRSw S12 ActiveLink Link Frame Vlans DscpPbitMap
====================================================================================================================================
MFG MS-06-1 1G_F 1G_F true true true false 111 1 (PRIMARY) FRONT 2DIX 20 0000000000101010003030300040404000505050000000600000000000000000
MFG MS-07-1 1G_F 1G_F true true true false 111 1 (PRIMARY) FRONT 2DIX 20 0000000000101010003030300040404000505050000000600000000000000000
MFX12 MS-24-0 2DIX 19 0000000000101010003030300040404000505050000000600000000000000000
MFX12 MS-25-0 2DIX 19 0000000000101010003030300040404000505050000000600000000000000000
====================================================================================================================================
Printout format, second table: Each line corresponds to a EthernetSwitch or EthernetSwitchPort MO (ETMFX), or a
EthernetSwitchModule or EthernetSwitchModulePort MO (CMXB), or a EthernetBridgePort (CMXB/CCIB in CAX subrack), as
well as the corresponding children MOs SwitchStp/SwitchPortStp. Each column corresponds to an attribute of these MOs. Refer
to the MOM for more detail on each attribute.
Position: the subrack, slot, and port number:
0: EthernetSwitch(Module)
1-7: EthernetSwitchPort::portNo
1-8: EthernetSwitchModulePort::portNo
Lag: The position of the port specified in masterPort of the connected Lag MO, when applicable.
lagSp: Lag::aggregatedPortSpeed, the speed of the Lag
Remote: SwitchStp::rootBridgeId or SwitchPortStp::remoteBridgeId -> if the Bridge Id is pointing to a switch inside the
node, the MAC address of the remoteBridge/rootBridge will be translated into the position of the switch. If the MAC address
is not found within the node but pointing to an outside switch, then the MAC address given in the remoteBridgeId will be
printed.
Speed: EthernetSwitch(Module)Port/EthernetPort::actualSpeedDuplex
Conf: EthernetSwitch(Module)Port/EthernetPort::operatingMode:configuredSpeedDuplex
AutoNg: EthernetSwitch(Module)Port/EthernetPort::operatingMode:autoNegotiation
60
Informational
USER GUIDE 61(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Sys/Ext: EthernetSwitchPort::systemPort or EthernetSwitchModulePort::externalPort or EthernetBridgePort::externalPort
S: EthernetSwitch(Module)Port/EthernetPort::administrativeState&operationalState (0=unlocked&disabled,
1=unlocked&enabled, L=locked)
T: EthernetSwitch(Module)Port/EthernetPort::trafficState
L: Lag:administrativeState&operationalState. Only applicable when the Port(s) are part of a Lag MO.
Prio: SwitchStp::bridgePriority or SwitchPortStp::priority
Cost: SwitchPortStp::actualPathCost
RtCost: SwitchPortStp::rootPathCost
Role-State: SwitchPortStp::stpRole and SwitchPortStp::stpState
Edge: SwitchPortStp::edgePortMode
PbitQMap: EthernetSwitch(Module)(Port)::pbitQueueMap
UnIng: EthernetSwitchPort::untaggedIngressVid&untaggedIngressPriority or
EthernetSwitchModulePort::untaggedIngressVlanRef&untaggedIngressPriority. Shows the vid and priority that will be
assigned to untagged ingress frames.
Vlans: EthernetSwitchPort::vlanMembership or EthernetSwitchModulePort::vlanRef&egressUntagVlanRef. Shows the list
of vlan ids supported by the port. Vlans on which egress frames will be untagged will be marked with a "U", eg "23U"
means that vlan id 23 will be untagged on egress.
Example, ETMFX:
=============================================================================================================================================
Board Position Remote Speed Conf AutNg Sys STL Prio Cost RtCost Role-State Edge PbitQMap UnIng Vlans
=============================================================================================================================================
MFX12 MS-24-0 ES4-26 1 32768 BRIDGE 10112233 101:0 0,101
MFX12 MS-24-1 MS-25 1G_F 1G_F true false 1 128 20000 100000 ROOT-FORWARDING EDGE_OFF 10112233 1:0 0,101
MFX12 MS-24-2 NOLINK 1G_F true false L 128 200000000 0 UNKNOWN-DISCARDING EDGE_OFF 10112233 1:0 0
MFX12 MS-24-3 NOLINK 1G_F true false L 128 200000000 0 UNKNOWN-DISCARDING EDGE_OFF 10112233 1:0 0
MFX12 MS-24-4 NOLINK 1G_F true false L 128 200000000 0 UNKNOWN-DISCARDING EDGE_OFF 10112233 1:0 0
MFX12 MS-24-5 ES1-03 1G_F 1G_F true false 1 128 20000 100000 ALTERNATE-DISCARDING EDGE_OFF 10112233 1:0 0,101
MFX12 MS-24-6 MS-24 1G_F 1G_F true true 1 128 20000 100000 DESIGNATED-FORWARDING EDGE_OFF 10112233 1:0 0,101
MFX12 MS-24-7 NOLINK 1G_F true false L 128 200000000 0 UNKNOWN-DISCARDING EDGE_OFF 10112233 1:0 0
....
Example, CMXB:
=============================================================================================================================================
Board Position Remote Speed Conf AutNg Ext STL Prio Cost RtCost Role-State Edge PbitQMap UnIng Vlans
=============================================================================================================================================
CMXB MS-03-0 MS-03 1 0 BRIDGE
CMXB MS-03-1 MS-03 1G_F 1G_F false false 1 128 20000 0 DESIGNATED-FORWARDING BPDU_FILTER 10234567 1:0 3005
CMXB MS-03-2 MS-03 10G_F 10G_F false false 1 128 2000 0 DESIGNATED-FORWARDING EDGE_OFF 10234567 1:0 1480,1481,2001,3005
CMXB MS-03-3 MS-03 10G_F 10G_F false false 1 128 2000 0 DESIGNATED-FORWARDING EDGE_OFF 10234567 1:0 1480,2001,3005
CMXB MS-03-4 MS-03 10G_F 10G_F false false 1 128 2000 0 DESIGNATED-FORWARDING EDGE_OFF 10234567 1:0 1480,2001,3005
CMXB MS-03-5 MS-03 1G_F 1G_F false true 1 128 20000 0 DESIGNATED-FORWARDING BPDU_FILTER 10234567 1:0 1480,1481
CMXB MS-03-6 NOLINK 10G_F false false L 128 2000 0 UNKNOWN-DISCARDING EDGE_OFF 10234567 1:0
CMXB MS-03-7 NOLINK 10G_F false false L 128 2000 0 UNKNOWN-DISCARDING EDGE_OFF 10234567 1:0
CMXB MS-03-8 NOLINK 10G_F false true L 128 2000 0 UNKNOWN-DISCARDING EDGE_OFF 10234567 1:0
.....
Printout format, option g:
Box with double-line border is the identified root bridge in the RSTP domain
stpState is marked in the middle of a line with "S" (DIS=DISABLED, BLO=BLOCKING, LIS=LISTENING,
DSC=DISCARDING, LEA=LEARNING, FWD=FORWARDING, UNK=UNKNOWN)
stpRole is marked in the middle of a line with "R" (R=ROOT, D=DESIGNATED, A=ALTERNATE, B=BACKUP,
U=UNKNOWN)
The arrow head (< or >) in the end of a line is the side where it is actually possible to determine which port that has the
relationship to the board where the line originates
The x is drawn on the side of the port where it is discarding
Only one link per LAG will be drawn (thicker), label will include port numbers of all links in the group
Bridge priority (P) is shown inside of a bridge
rootPathCost (PC) is shown for each link
Example, RNC3820:
0~~~~~~~~~~~~0
S NETWORK S
+---------------->S S<----------------+
| 0~~~~~~~~~~~~0 |
| |
61
Informational
USER GUIDE 62(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
| |
| Port 1, PC=0 Port 1, PC=2000 |
| R=D, S=FWD R=D, S=FWD |
| |
#============# +------------+
+---->H MS-03 H Port 2, PC=2000, R=R, S=FWD | MS-26 |<----+
| +-->H P=8192 H<----------------------------------| P=16384 |<--+ |
| | #============# +------------+ | |
| | | |
| | | |
| | Port 1, PC=2000 Port 1, PC=4000 | |
| | R=R, S=FWD R=R, S=FWD | |
| | | |
| | +------------+ +------------+ | |
| +---| ES1-03 | Port 2, PC=4000, R=A, S=DSC | ES1-26 |---+ |
| | P=32768 |<---------------------------------x| P=32768 | |
| +------------+ +------------+ |
| |
| |
| Port 1, PC=2000 Port 1, PC=4000 |
| R=R, S=FWD R=R, S=FWD |
| |
| +------------+ +------------+ |
+-----| ES2-03 | Port 2, PC=4000, R=A, S=DSC | ES2-26 |-----+
| P=32768 |<---------------------------------x| P=32768 |
+------------+ +------------+
4.2.10 sti[bcfopr] [<Filter>] [<stateFilter>]
Purpose: Display state and configuration of IP interfaces.
The printout consists of up to 7 tables:
the IpInterfaces table, one line per IpInterface MO.
the IpAccessHostEt table, one line per IpAccessHostEt MO.
the IpAccessHostGpb/Spb table, one line per IpAccessHostGpb or IpAccessHostSpb MO.
the IpAccessHostPool table, one line per IpAccessHostEt MO part of an IpAccessHostPool (applicable to RNC and MGW
only).
the IpEthPacketDataRouter table, one line per IpEthPacketDataRouter MO (applicable to RNC38xx only).
the M3uA table, one line per M3uAssociation MO (applicable to RNC and MGW only).
the Iub/S1/X2 table, one line per MO of type IubLink,Iub,TemPointToMMe,TermPointToENB (applicable to RNC/RBS/ERBS
only).
Options:
p: ping the remote destinations (printout will take more time to complete)
r: to refresh the data (clear cache and re-read from node).
f: only show the IpInterface/IpAccessHost overview table. Without this option, all tables are shown.
o: show the IpAccessHost froIds in the above tables.
b: only show the Iub/S1/X2 signalling interfaces (in RNC/RBS/ERBS). Without this option, all tables are shown.
c: only show the Core signalling interfaces (in RNC/MGW: SIGTRAN). Without this option, all tables are shown.
Arguments:
the first argument matches on the whole line
the second argument matches only the state field ("GS12MUP" or "GS12ISP" or "IRP")
Printout format, IpInterfaces table:
Each line corresponds to a IpInterface MO. Each column corresponds to an attribute of these MOs. Refer to the MOM for more
detail on each attribute.
Board: The type of ET board on which the IpInterface is located (ETIPG, ETMFG, ETMFX)
62
Informational
USER GUIDE 63(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Interface: the subrack and slot of the ET board, followed by a sequential number to distinguish between numerous
IpInterfaces defined on the same board.
Vid: the vlan ID, read from the attribute IpInterface::vid or IpInterface:vlanRef
Subnet: the value of the attributes IpInterface::subnet and IpInterface::networkPrefixLength
DefaultRouter: the number in brackets shows which is the active defaultRouter according to the attribute
IpInterface::defaultRouterTraffic. Also shown is the ip addess of the active default router, read from the attribute
IpInterface::defaultRouterX (where X is 0, 1, or 2)
rps: the value of IpInterface::rps
I: the value of IpInterface::operationalState (0=disabled, 1=enabled)
R: the value of IpInterface::defaultRouterXState (where X is 0, 1, or 2). Only applicable when rps=true, otherwise a "-" is
shown.
P: the ping status to the active defaultRouter (0=unreachable, 1=alive)
H: the state of each IpAccessHost connected to this IpInterface.
IpHosts: the list of IP hosts connected to this IpInterface. G=IpAccessHostGpb, Et=IpAccessHostEt, S=IpAccessHostSpb.
For each IpAccessHost, the location of the host is shown, not the MO name. To see the mapping of the host location vs MO
name, check the following two tables. In brackets next to IpAccessHostEt is shown the IpAccessHostPool using this host,
when applicable.
=======================================================================================================================
Board Interface Vid Subnet DefaultRouter Rps IRP HHH IpHosts
=======================================================================================================================
IPG MS-04-1 632 10.164.233.64/29 (0) 10.164.233.70 false 1-1 1 G=MS-5-1
IPG MS-04-2 652 10.164.233.0/26 (0) 10.164.233.61 true 111 111 S=MS-10-2 S=MS-23-1 S=MS-9-1
IPG MS-04-3 662 10.164.233.128/26 (0) 10.164.233.188 false 1-1 1 Et=MS-04-3 (IuB)
IPG MS-04-4 682 10.164.233.96/27 (0) 10.164.233.125 true 111 1 Et=MS-04-4 (IuR)
IPG MS-04-5 2001 192.168.101.0/24 (0) 192.168.101.1 false 1-1 1 Et=MS-04-5 (intraNode)
Printout format, IpAccessHostEt table:
Each line corresponds to a IpAccessHostEt MO. Description of the columns:
ET: The type of ET board on which the IpAccessHostEt is located (ETIPG, ETMFG, ETMFX)
Host: the subrack and slot of the ET board, followed by a sequential number to distinguish between numerous
IpAccessHostEt defined on the same board.
MOName: the name of the IpAccessHostEt MO.
Lnh: the linkhander address of the ET board. Needed in order to run the
EtHostMo_startPing/EtHostMo_startTraceRoute command.
Ntp: the value of attribute ntpDscp. Only shown when ntpServerMode is enabled on this host. If ntpServerMode is disabled
then a dash is shown instead.
Fro: the froId of the IpAccessHostEt. Needed in order to run the EtHostMo_startPing/EtHostMo_startTraceRoute
command. Only shown with option o.
HostIp: the IP address of the IpAccessHostEt.
Vid: the vlan ID of the IpInterface connected to this IpAccessHostEt.
H: the state of the IpAccessHostEt (L=locked, 1=enabled, 0=disabled).
IRP: the state of the IpInterface MO connected to this IpAccessHostEt. See description in table above.
IpAccessHostPool/IpAcccessSctp: the list of MOs using this host, first the Pools are listed, then the IpAccessSctp. For the
IpAccessSctp, it shows the position of the GPB on which the SCTP is located, not the MO name.
=======================================================================================================================
ET Host MOName Lnh Ntp Fro HostIp Vid HIRP IpAccessHostPool/IpAccessSctp
=======================================================================================================================
IPG Et=MS-04-2 MS-4-1 000400 - 1 192.168.101.4 2001 11-1 intraNode
IPG Et=MS-04-3 MS-4-3 000400 49 2 10.212.48.5 700 11-1 Iub MS-06,MS-08,MS-12,MS-16
IPG Et=MS-04-4 MS-4-2 000400 - 3 10.202.212.3 812 1111 Iu_Iur
IPG Et=MS-25-2 MS-25-1 002500 - 4 192.168.101.25 2001 11-1 intraNode
IPG Et=MS-25-3 MS-25-3 002500 49 5 10.212.48.6 700 11-1 Iub MS-06,MS-08,MS-12,MS-16
Printout format, IpAccessHostGpb/Spb table:
Each line corresponds to a IpAccessHostGpb/Spb MO. Description of the columns:
Host: the subrack and slot of the GPB/SPB where the IP host is located.
Board: the type of board where the IP host is located.
MOName: the name of the IpAccessHostGpb/Spb MO.
63
Informational
USER GUIDE 64(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
HostIp1/2: the IP addresses of the IP Host.
Interface1/2: the position of the IpInterfaces connected to the IP Host.
Vid1/Vid2: the vlan ID of the IpInterfaces connected to the IP Host.
H: the state of the IP Host (L=locked, 1=enabled, 0=disabled).
IRP1/2: the state of the IpInterfaces connected to the IP Host (see detailed description of the IRP state in first table).
=======================================================================================================================
Host Board MOName HostIp1 HostIp2 Interface1 Interface2 Vid1 Vid2 H IRP1 IRP2
=======================================================================================================================
G=MS-08 GPB53 MS-8 10.159.22.2 10.159.22.18 MS-26-2 MS-27-2 929 929 1 1-1 1-1
G=ES1-12 GPB53 ES-1-12 10.212.0.27 10.212.0.28 ES1-03-1 ES1-26-1 100 100 1 1-1 1-1
G=ES1-13 GPB53 ES-1-13 10.212.0.29 10.212.0.30 ES1-03-1 ES1-26-1 100 100 1 1-1 1-1
S=MS-19 SPB3 MS-19 10.159.18.7 10.159.18.8 MS-26-3 MS-27-3 945 945 1 111 111
S=MS-20 SPB3 MS-20 10.159.18.9 10.159.18.10 MS-26-3 MS-27-3 945 945 1 111 111
S=MS-21 SPB3 MS-21 10.159.18.11 10.159.18.12 MS-26-3 MS-27-3 945 945 1 111 111
Printout format, IpAccessHostPool table (RNC/MGW):
Each line corresponds to a IpAccessHostEt MO used by an IpAccessHostPool. Each column corresponds to an attribute of these
MOs.
Pool: the name of the IpAccessHostPool
HostEt: the position (Subrack-Slot) of the IpAccessHostEt MO, followed by a sequential number to distinguish between
numerous IpAccessHostEt defined on the same board.
HostIp: the attribute IpAccessHostEt::ipAddress
ET: the board type (ETIPG, ETMFG, or ETMFX)
Vid: the vlan ID of the IpInterface connected to this IpAccessHostEt.
P: the state of the IpAccessHostPool MO (L=locked, 1=unlocked&enabled, 0=unlocked&disabled)
H: the state of the IpAccessHostEt MO
I: the state of the IpInterface MO connected to this IpAccessHostEt, same as shown in the first table
R: the state of the active defaultRouter, same as shown in the first table
P: the ping status to the active defaultRouter, same as shown in the first table
Users: read from the attribute IpAccessHostPool::reservedBy. Shows "Rnc" if the pool is used by the RncFunction MO
(applicable to intraNode/BEES pool), else shows the number of IubLinks/IurLinks/IuLinks using this pool.
RNC:
=======================================================================================================================
Pool HostEt HostIp ET Vid PH IRP Users: Iuc Iur Iub
=======================================================================================================================
IUB MS-04-3 10.164.233.129 IPG 662 11 1-1 0 0 34
IUB MS-25-3 10.164.233.130 IPG 662 11 1-1 0 0 34
IUR MS-04-4 10.164.233.97 IPG 682 11 111 0 24 0
IUR MS-25-4 10.164.233.98 IPG 682 11 111 0 24 0
intraNode MS-04-5 192.168.101.4 IPG 2001 11 1-1 Rnc 0 0 0
intraNode MS-25-5 192.168.101.25 IPG 2001 11 1-1 Rnc 0 0 0
MGW:
=======================================================================================================================
Pool Type HostEt HostIp ET Vid PH IRP
=======================================================================================================================
A A MAIN-06-2 10.52.211.10 IPG 1180 11 1-
A A MAIN-14-1 10.52.211.11 IPG 1180 11 1-
A A MAIN-17-1 10.52.211.12 IPG 1180 11 1-
A A MSE1-14-2 10.52.211.13 IPG 1180 11 1-
Iu IU MAIN-06-2 10.52.211.10 IPG 1180 11 1-
Iu IU MAIN-14-1 10.52.211.11 IPG 1180 11 1-
Iu IU MAIN-17-1 10.52.211.12 IPG 1180 11 1-
Iu IU MSE1-14-2 10.52.211.13 IPG 1180 11 1-
Printout format, IpEthPacketDataRouter table (RNC):
Each line corresponds to a IpEthPacketDataRouter MO. Each column corresponds to an attribute of these MOs.
IpEthPdr: the position (Subrack-Slot) of the PdrDevice, followed by the attribute
IpEthPacketDataRouter::ipAddressSelection. Value 1 means IP_ADDRESS_1, value 2 means IP_ADDRESS_2. Value 11
means that both IpEthPacketDataRouter of that PdrDevice are using IP_ADDRESS_1 while 22 means that both are using
IP_ADDRESS_2 (which would mean that all traffic of the PdrDevice is routed to the same IpInterface instead of being
load-shared on both IpInterfaces)
SPB: the board type of the SPB hosting the PdrDevice
HostSpb: the position of the IpAccessHostSpb connected to this IpEthPacketDataRouter, followed by the number 1 or 2,
depending on the value of IpEthPacketDataRouter::ipAddressSelection
HostIp: the ip address of the IpAccessHostSpb, could be ipaddress 1 or 2, depending on the value of
IpEthPacketDataRouter::ipAddressSelection
64
Informational
USER GUIDE 65(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
ET: the board type of the IpInterface connected to this IpAccessHostSpb (ETIPG, ETMFG, or ETMFX)
Vid: the vlan ID of the IpInterface connected to this IpAccessHostSpb
E: the state of the IpEthPacketDataRouter MO (L=locked, 0=unlocked&disabled, 1=unlocked&enabled)
H: the state of the IpAccessHostSpb MO
U: the value of the usageState of the PdrDevice hosting this IpEthPacketDataRouter (I=Idle, A=Active, B=busy)
I: the state of the IpInterface MO connected to this IpAccessHostEt, same as shown in the first table
R: the state of the active defaultRouter, same as shown in the first table
P: the ping status to the active defaultRouter, same as shown in the first table
Iup: the value of IpEthPacketDataRouter::reservedBy. Shows which IP-based IuPS links can use this
IpEthPacketDataRouter for userplane connections. When empty, means that it can be used by all IP-based IuPS links.
=======================================================================================================================
IpEthPdr SPB HostSpb HostIp ET Interface Vid EH U IRP Iup
=======================================================================================================================
MS-19-1 SPB21 MS-19-1 114.126.135.176 MFG MS-07-1 2000 11 A 1-1 any
MS-19-2 SPB21 MS-19-2 114.126.135.181 MFG MS-26-1 2000 11 A 1-1 any
MS-20-1 SPB21 MS-20-1 114.126.135.177 MFG MS-07-1 2000 11 A 1-1 any
MS-20-2 SPB21 MS-20-2 114.126.135.182 MFG MS-26-1 2000 11 A 1-1 any
Printout format, M3uAssociation table (RNC/MGW):
Each line corresponds to a M3uAssociation MO. Each column corresponds to an attribute of these MOs.
the HostGpb column identifies the IpAccessHostGpb MO.
the Sctp column identifies the Sctp MO
the M3uA column identifies the M3uAssociation MO. At the beginning of the string is the identity of the parent Mtp3bSp
MO, then comes the identity of the M3uAssociation MO. A wildcard (.*) separates the two identities.
the Assoc column identifies the sctp association, given by the the gpb position and the association number. The
association number can be used in the printout sctphost_info -assoc <assocnumber>.
the GS12MUP column shows the various states, where: G=IpAccessHostGpb, S=Sctp, 1=IpInterface1, 2=IpInterface2,
M=M3uAssociation, U=User, P=ipac_ping (1=alive, 0=notalive). The ping is done only when "sti" is run with the option "p".
the A column shows the associationState of the M3uAssociation, where: I=inactive, A=active, E=established, D=down.
the LocalInterface column shows the local interface, can be a IpInterface MO or a FastEthernet MO. In the case of
FastEthernet, the letter "f" is appended to the identity as shown in the third line of the printout below. In brackets is
indicated whether the chosen interface is interface 1 or interface 2. The association tries to setup on interface 1 but if that
fails then it uses interface 2.
the RemoteInterface column shows which interface is used on the remote side, 1 or 2.
the LocalIp:Port and RemIp:Port columns show the ipaddress and sctp port of the association, for each side.
ther User column shows which application part is using this association. Could be GCP (Vmgw), Q.AAL2 (Aal2Ap),
RANAP, RNSAP.
Example MGW:
============================================================================================================================
HostGpb Sctp M3uA Assoc GS12 MUP A LocalInterface,Ip:Port RemInterface,Ip:Port User
============================================================================================================================
IPACGPB_2_6 Sctp_2_6 2.*msc2qa 0006:148 1111 111 A (1) 2-19 10.201.0.31:2905 (2) 10.202.10.20:2905 Vmgw=VMGW92
IPACGPB_2_6 Sctp_2_6 2.*nwp141a 0006:60 1111 111 D (2) 2-20 10.201.10.31:2905 (1) 10.201.12.141:2905 Aal2Sp=1,Aal2Ap=nwp141
SIG12_13 SIG12_13 2.*nwp206a 0012:5 1111 111 A (1) 1-12f 10.202.0.30:2905 (1) 10.202.2.206:2905 Aal2Sp=1,Aal2Ap=nwp206
Example RNC:
==================================================================================================================================
HostGpb Sctp M3uA Assoc GS12 MUP A LocalInterface,Ip:Port RemInterface,Ip:Port User
==================================================================================================================================
MS-8-1 MS-8 Iu.*mgw7-2521-1720 0008:21 1111 111 A (1) MS-7 10.207.2.121:2905 (1) 10.207.2.245:2905 Aal2Ap=Aal2routing-mgw7-2521-1720
MS-8-1 MS-8 Iu.*mgw71-2521-1730 0008:4 1111 111 A (1) MS-7 10.207.2.121:2905 (1) 10.207.2.246:2905 Aal2Ap=Aal2routing-mgw71-2521-1730
MS-8-1 MS-8 Iu.*Iuc-2521-1700 0008:18 1111 111 A (1) MS-7 10.207.2.121:2905 (2) 10.207.12.240:2905 Cn.*=23591,Iu.*=Iuc-1700,Ranap=Iuc-1700
MS-8-1 MS-8 Iu.*Iuc-2521-1710 0008:2 1111 111 A (1) MS-7 10.207.2.121:2905 (1) 10.207.2.242:2905 Cn.*=23591,Iu.*=Iuc-1710,Ranap=Iuc-1710
MS-8-1 MS-8 Iu.*Iup-2521-2207 0008:33 1111 111 A (1) MS-7 10.207.2.121:2905 (2) 10.207.4.1:2905 Cn.*=23591,Iu.*=Iup-2207,Ranap=Iup-2207
MS-8-1 MS-8 Iu.*Iup-2521-2271 0008:34 1111 111 A (1) MS-7 10.207.2.121:2905 (2) 10.207.4.17:2905 Cn.*=23591,Iu.*=Iup-2271,Ranap=Iup-2271
MS-8-1 MS-8 Iu.*Iur-2521-2522 0008:22 1111 111 A (1) MS-7 10.207.2.121:2905 (2) 10.207.12.122:2905 Iur.*=Iur-2521-2522,Rnsap=Iur-2521-2522
Printout format, IubLink table (RNC): This table shows the configuration and status of control plane connections for IP-based
IubLinks (for Iub user plane connections refer to the IpAccessHostPool table). Each line corresponds to a IubLink MO in RNC.
Each column corresponds to an attribute of these MOs.
Sctp: the value of IubLink::sctpRef. The position of the GPB hosting this Sctp is shown.
Mod: the value of IubLink::rncModuleRef.
65
Informational
USER GUIDE 66(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Host: the value of Sctp::ipAccessHostGpbId or Sctp::ipAccessSctpRef. Shows "Gpb" if IpAccessHostGpb is used or "Et" if
IpAccessSctp is used.
Interf1/Interf2: the position of the IpInterfaces used by the IpAccessHost(s).
LocalIp1/LocalIp2: the ip addresses of the IpAccessHost(s) used by the Sctp.
RemoteIp: the value of IubLink::remoteCpIpAddress1
IubLink: the name of the IubLink MO.
G: the state of the IpAccessHostGpb or IpAccessSctp used by the Sctp MO (0=locked, 1=unlocked&enabled,
0=unlocked&disabled)
S: the state of the Sctp MO
1: the state of IpInterface 1
2: the state of IpInterface 2
I: the state of the IubLink MO
S: the state of the NodeSynch MO
PP: the ping status from each IpInterface to the RemoteIp (0=unreachable, 1=alive). The first "P" corresponds to the ping
status from IpInterface 1, the second "P" corresponds to the ping status from IpInterface 2.
the NbapC_Assoc and NbapD_Assoc fields identify the sctp associations for NbapCommon and NbapDedicated. First
number is the local port number, then the remote port number, then the SCTP association reference number according to
the printout of sctphost_info -assoc -all. The number in brackets identifies the active IpInterface used for this
association.
=========================================================================================================================================
Sctp Mod Host Interf1 Interf2 LocalIp1 LocalIp2 RemoteIp IubLink GS12 ISPP NbapC_Assoc NbapD_Assoc
=========================================================================================================================================
MS-14 1 Gpb MS-25-1 MS-26-1 10.100.0.140 10.100.1.140 10.100.2.150 Iub-1 1111 1111 1:5101:30 (1) 2:5102:23 (1)
MS-14 1 Gpb MS-25-1 MS-26-1 10.100.0.140 10.100.1.140 10.100.2.150 Iub-10 1111 1111 1:5119:33 (1) 2:5120:26 (1)
Printout format, Iub table (RBS):
LocalIp: ipaddress of the IpAccessHostGpb or IpAccessHostEt used for Iub control plane
RemoteIp1/RemoteIp2: ip addresses used on the remote side (RNC) according to the printout of
sctphost_info -assoc -all
G: state of IpAccessHostGpb or IpAccessSctp MO
S: state of Sctp MO
I: state of IpInterface MO
C: state of NbapCommon MO
D: state of NbapDedicated MO
P: ping status, one ping for each remoteIp (0=unreachable, 1=alive)
the NbapC_Assoc and NbapD_Assoc fields identify the sctp associations for NbapCommon and NbapDedicated. First
number is the local port number, then the remote port number, then the SCTP association reference number according to
the printout of sctphost_info -assoc -all. The number in brackets identifies the active IpInterface used for this
association.
=======================================================================================================================
LocalIp RemoteIp1 RemoteIp2 IubLink GSI CDPP NbapC_Assoc NbapD_Assoc
=======================================================================================================================
10.2.35.143 10.2.35.16 10.2.35.17 Iub=1 111 1111 5113:1 (2) 5114:2 (1)
=======================================================================================================================
Printout format, S1/X2 interfaces in ERBS:
T: state of the TermPoint MO
S: state of the Sctp MO
H: state of the IpAccessHostEt MO
P: ping status to the active remote IP address (0=unreachable, 1=alive)
Assoc: the reference number of the SCTP association according to the printout of sctphost_info -assoc -all
TermPoint: "ENB" refer to TermPointToENB MO (X2), "Mme" refer TermPointToMME MO (S1).
=======================================================================================================================
66
Informational
USER GUIDE 67(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
LocalIp:Port RemoteIp:Port StandbyRemoteIp TSHP Assoc TermPoint
=======================================================================================================================
10.62.11.34:36422 10.62.11.33:36422 10.62.11.34 1111 71 ENB=104023
10.62.11.34:36422 10.64.193.81:36412 10.62.11.82 1111 68 Mme=MME010064193081
10.62.11.34:36422 10.64.193.91:36412 10.62.11.92 1111 70 Mme=MME010064193091
=======================================================================================================================
4.2.11 sts
Purpose: Display state and configuration of Network Synchronization.
The printout is read from the Synchronization MO on CPP nodes and all children MOs of Synchronization/Ntp/Ptp on COM
nodes.
Printout format CPP
The first line corresponds to the value of the attribute nodeSystemClock. If the node is part of a Node Group Synchronization
cluster then the next line will indicate the node group role (provider or receiver). The remaining lines correspond to the values of
the attributes syncReference,syncRefPriority,syncRefActivity,syncRefStatus.
Examples:
RNC01> sts
SystemClock: LOCKED_MODE
-------------------------------------------------------------------------------------
Prio Activity RefState AdmState OpState SyncReference
-------------------------------------------------------------------------------------
1 ACTIVE OK UNLOCKED ENABLED Subrack=MS,Slot=4,PlugInUnit=1,TimingUnit=1,TuSyncRef=1
2 INACTIVE OK UNLOCKED ENABLED Subrack=ES-2,Slot=2,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1
3 INACTIVE OK UNLOCKED ENABLED Subrack=ES-2,Slot=27,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1
4 INACTIVE OK UNLOCKED ENABLED Subrack=ES-3,Slot=2,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1
5 INACTIVE OK UNLOCKED ENABLED Subrack=ES-3,Slot=27,PlugInUnit=1,ExchangeTerminal=1,Os155SpiTtp=pp1
RBS14> sts
SystemClock: HOLD_OVER_MODE
-------------------------------------------------------------------------------------
Prio Activity RefState AdmState OpState SyncReference
-------------------------------------------------------------------------------------
1 INACTIVE FAILED UNLOCKED DISABLED IpAccessHostEt=1,IpSyncRef=1
2 INACTIVE FAILED UNLOCKED DISABLED IpAccessHostEt=1,IpSyncRef=2
Printout format MSRBS
The first line indicates the clock state in RadioEquipmentClock MO If the node is part of a Node Group Synchronization cluster
then the next line will indicate the node group role (provider or receiver). The table shows the attributes of each
RadioEquipmentClockReference MO. The priority is marked with an asterisk to indicated the active Reference. The MO referred
by the "encapsulation" attribute is shown on the right together with some of its attributes, in brackets.
Examples:
MSRBS1> sts
radioClockState : FREQUENCY_LOCKED
-------------------------------------------------------------------------------------
Prio ST syncRefType refStatus opQualLevel SyncReference
-------------------------------------------------------------------------------------
*1 1 SYNC_E NO_FAULT PRC Synchronization=1,SyncEthInput=TN_B (SFP_OPTICAL EthernetPort=TN_B)
2 1 FREQUENCY_PORT NO_FAULT PRC Synchronization=1,FrequencySyncIO=1 (FREQUENCY_1PPS FieldReplaceableUnit=1,SyncPort=1)
TCU> sts
radioClockState : FREQUENCY_LOCKED
-------------------------------------------------------------------------------------
Prio ST syncRefType refStatus opQualLevel SyncReference
-------------------------------------------------------------------------------------
2 0 NTP_FREQUENCY NTP_FAULT QL_UNKNOWN Ntp=1,NtpFrequencySync=1 (192.168.250.101:32751 Router=OAM,InterfaceIPv4=TN_B_oam,AddressIPv4=TN_B_oam)
*3 1 PTP_FREQUENCY NO_FAULT PRC Ptp=1,BoundaryOrdinaryClock=PTP_FREQUENCY (G_8265_1 Router=OAM,InterfaceIPv4=TN_B_oam,AddressIPv4=TN_B_oam)
4 1 PTP_FREQUENCY NO_FAULT PRC Ptp=1,BoundaryOrdinaryClock=PTP_FREQUENCY_IPV6 (G_8265_1 Router=OAM,InterfaceIPv6=TN_B_oam_ipv6,AddressIPv6=TN_B_oamipv6add)
67
Informational
USER GUIDE 68(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
5 1 GNSS_RECEIVER NO_FAULT GNSS Synchronization=1,TimeSyncIO=GPS (FieldReplaceableUnit=1,SyncPort=1)
7 1 PTP_TIME PTP_FAULT QL_UNKNOWN Ptp=1,BoundaryOrdinaryClock=PTP_TIME (IEEE_1588_J3 EthernetPort=TN_A)
4.2.12 str
Print status of the IubLinks/AbisLinks and their associated Cells and Channels (RNC/BSC only).
The command has two syntaxes, depending on the type of node.
CDMA BSC: str [ | <unix-cmds>]
------------------------------------------------------------------
SITE C1 C2 C3 ABIS BACKHAUL ATMPORTS
------------------------------------------------------------------
96 11 11 11 11 RBS1_Backhaul BHRBS1_Backhaul_BHSBackhaulSpan_1
------------------------------------------------------------------
The states of the channels are shown for each cell, as well as the states of the AbisCommon and AbisDedicated.
The MO-id of the BackHaul and the AtmPorts are also shown for each site.
State abbreviation: Lmeans Locked, 0means Disabled, and 1means Enabled.
UTRAN RNC: str[123ft] [<csvfile>] [<filter-options>] [ | <unix-cmds>]
To see the state of all or part of the cells/iubs/channels in the node, one line per site.
The filter options (-m,-s,-i,-c,-g,-t,-r) allow to get states on only part of the sites/cells, in order to speed up the output.
For example:
str -m 7,8,9 - print states only for modules 7, 8, and 9
str -s ms,es-1 - print states only for subracks ms and es-1
str -i 9012 - print states only for the MO Iublink=9012 and its connected cells
str -c 90121,90131 - print states only for the Iublink MOs connected to the MO UtranCell=90121 and UtranCell=90131
str -g clusterNorth - print states only for the Iublinks defined in the MO group "clusterNorth"
str -t a - print states only for ATM-based iublinks
str -t i - print states only for IP-based iublinks
str -t ai - print states for dual stack iublinks
str -r 9345 - print states for IubLinks connected to RSite=9345
There are five possible output formats:
The str printout uses an abbreviated naming of the cells where it is assumed that the last digit is identifying the sector. For
networks where the sector is not identified by the last digit, it can be handy to use str1 or str2 since the whole cell name will
then be shown for each sector.
The strt command shows the AtmPorts used by each site.
The str3 command shows cell status in a compressed format in order to fit 12 cells per line, see further down for details.
str
-----------------------------------------------------------------------------------------------
MOD IUBLINK CELLNAME CFRPHEU1 CFRPHEU2 CFRPHEU3 ICDS TN R
-----------------------------------------------------------------------------------------------
1 Iub_3011 3011-1/2/3 1111111 L000000 1000000 1111 I P
-----------------------------------------------------------------------------------------------
strt
-----------------------------------------------------------------------------------------------
MOD IUBLINK CELLNAME CFRPHEU1 CFRPHEU2 CFRPHEU3 ICDS TN TNPORTS
-----------------------------------------------------------------------------------------------
1 Iub_3011 3011-1/2/3 1111111 L000000 1000000 1111 AI MS-25-1 MS-26-1
8 Iub_3012 3012-1/2/3 1111111 1111111 1111111 1111 I MS-23 MS-24
-----------------------------------------------------------------------------------------------
str1
68
Informational
USER GUIDE 69(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
-----------------------------------------------------------------------------------------------
MOD IUBLINK CELLNAMES CFRPHEU1 CFRPHEU2 CFRPHEU3 ICDS
-----------------------------------------------------------------------------------------------
1 Iub_3011 30111 30112 30113 1111111 L000000 1000000 1111
-----------------------------------------------------------------------------------------------
str2
----------------------------------------------------------------------------------------
MOD IUBLINK ICDS CELL1 CFRPHEU CELL2 CFRPHEU CELL3 CFRPHEU
----------------------------------------------------------------------------------------
1 Iub_3011 1111 30111 1111111 30112 1111111 30113 1111111
----------------------------------------------------------------------------------------
str3
-----------------------------------------------------------------------
IUBLINK MOD TN R ICDS C01 C02 C03 C04 C05 C06 C07 C08 C09 C10 C11 C12
-----------------------------------------------------------------------
Iub-1523 1111 I P 1111 111 111 111 11 11 111
Iub-1526 1161 A N 1111 111 1 111 111 111 111
-----------------------------------------------------------------------
MOD: The RNC module that is handling the control plane for this Iub, corresponds to the attribute IubLink::rncModuleRef
IUBLINK: The MO name of the IubLink
CELLNAME: The name of the cells that are connected to that IubLink. The cell names correspond to the respective
sectors. Eg: 6306-1/2/3 means that: cell 63061 is connected to sector 1, cell 63062 is connected to sector 2, cell 63063 is
connected to sector 3.
CFRPHEU: The first digit is the state of the UtranCell MO. The following three digits are the state of the common channels
(Fach/Rach/Pch). The fifth digit (if present) represents the state of the hsdpa channel (Hsdsch). The sixth digit (if present)
represents the state of the enhanced uplink channel (Eul). The seventh digit (if present) represents the state of the EulFach
channel (EulFach).
ICDS: The first digit is the state of the IubLink. The second digit is the state of NbapCommon MO or SctpAssociation MO
handling Nbap Common. The third digit is the state of NbapDedicated MO or SctpAssociation MO handling Nbap
Dedicated. The fourth digit is the state of NodeSynch MO.
TN: The type of transport network used by the IubLink. A=ATM, I=IP, AI=DualStack
R: The Iub redundancy configuration of the IubLink, read from the attribute IubLink::poolRedundancy. P=Primary,
S=Secondary, N=No Redundancy. Only applicable for RNC in Pool with Iub Redundancy feature.
TNPORTS: The Subrack and Slot of the ETIP (in case of IP Iub) or ATMPORT (in case ATM or DualStack Iub)
CXX: A compressed cell status consisting of up to 3 digits per cell (XX is a number from 01 to 12):
1st digit is the combined state of UtranCell+Fach+Rach+Pch: if all four are up then it shows 1. If one or more are
locked it will show "L", "T", "S", or "U" depending on the type of lock (see below). If one or more are disabled then it
shows 0.
2nd digit is the state of HsDsch.
3rd digit is the combined state of Eul+EulFach (same rule applied as for 1st digit).
States values:
L= Locked
S= ShuttingDown
T= TPS power Locked (corresponds to the attribute tpsPowerLockState)
U= TPS power ShuttingDown
0= Unlocked & Disabled
1= Unlocked & Enabled
The output can be piped in external unix commands such as grep.
If a filename is given as argument, the output will be saved into this file in csv format (as well as being printed on the screen).
The foption (fast) is for printing without fetching the data. I.e. the data can be fetched once, then displayed in many different
ways without having to fetch it again each time.
Examples:
strf | grep 3011
str1f | sort -k 2 (sort on the second field)
69
Informational
USER GUIDE 70(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.2.13 dcg[meiasrfkx] [-m <rophours>] [-d <logdays>] [-b <boards|boardgroup>|all] [-k <nrdumps>] [-f <mofilter>]
[<logdir>]
Fetch data for TRs/CSRs, according to the Data Collection Guidelines.
The dcg command offers a number of options, it is possible to combine several options, eg: "dcgmsr"
Options for CPP nodes:
m: mandatory data. Includes modump, logfiles, pm ropfiles, CV’s, coli printouts.
e: emergency data. Subset of the mandatory data which can be taken in case of emergency, before doing board/node
restart. This option will usually be run on its own.
i: IP printouts
a: ATM/AAL2 printouts. By default only the AAL2 printouts are collected. To collect ATM printouts, use option "-b", see
below.
s: SS7 printouts
x: SPAS printouts
r: RNC specific printouts.
f: fetch logfiles, ropfiles, and CV. Three zipfiles are produced which can be used in offline mode in pmr, pmx, lg, and dbc.
Refer to the chapter "Offline mode" for more info.
k: take a MO dump (kget format). A zipfile is produced containing the MO dump and MOM of the node, it can be used in
offline mode by running "moshell <zipfile>". Refer to the chapter "Offline mode" for more info.
Options for COM nodes:
m: mandatory data. Includes modump, logfiles, pm ropfiles, coli printouts, and large ESI (RCS nodes).
By default dcgm collects a large ESI.
To get a small ESI, use dcge or the option -k 0, eg dcgm -k 0.
To get a static ESI, use the option -k -1 (static=small without callbacks, useful in case small ESI failed).
e: emergency data. Same as mbut with small ESI instead of large.
f: fetch logfiles and ropfiles. Two zipfiles are produced which can be used in offline mode in pmr, pmx, and lg. Refer to the
chapter "Offline mode" for more info.
k: take a MO dump (kget format). A zipfile is produced containing the MO dump and MOM of the node, it can be used in
offline mode by running "moshell <zipfile>". Refer to the chapter "Offline mode" for more info.
Switches:
-m <rophours>: the number of hours of ROP files to collect with pmrf, eg "-m 2". Default is 8 hours in dcge and 48 hours
in dcgm/dcgf. Note: the number of hours of Event ROP files to collect with pmef will be one fourth of this value (default: 2
hours in dcge and 12 hours in dcgm/dcgf).
-d <logdays> : the number of days of logfiles to collect with lgf, eg "-d 30". Default is 60 days in dcgm/dcgf. Note: to
specify hours or minutes, use "h" or "m", eg "-d 2h" to collect the last 2 hours.
-b <boards|boardgroup>|all : the ET boards on which dcgi/dcga will be run. When this option is not specified, dcga
collects no ET board data, while dcgi collects all ET boards data. Example: dcgi -b 000600,000700
-k <nrdumps> : the number of ENB DSP dumps to collect on CPP nodes, or the ESI granularity on RCS nodes (
1=large, 0=small, -1=static). Corresponds to the option -d in lg command. Default: 1 in dcgm, 0 in dcge.
If option -k -1 is specified on CPP nodes then the DCG proxy collection will be skipped (action DataCollection.runDcg()).
-f <mofilter>: the MO filter for MO dump collection. Eg "-f !relation=" to skip MOs such as UtranRelation/GsmRelation
in the MO dump.
Argument:
the directory where the collected data will be stored. If no directory is given, the directory
~/moshell_logfiles/logs_moshell/dcg/<node>/<date>_<time> is used.
Please refer to the command file in moshell/commonjars/scripts/dcg_datacollection.mos to view the various
commands that are run for each option. More info about each command can be found by typing h <command>
Note: for CPP nodes, if the MO layer is unavailable, it is possible to run dcg anyway by typing uv nocorba=1 before executing
dcg. Using nocorba=1 means that moshell will not attempt to connect to the MO service and will only run commands via
telnet/ftp/ssh/sftp.
70
Informational
USER GUIDE 71(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
4.2.14 hc[iuzd][v] [-r|-x <numbers>] [<hclogfile>|<hclogdir>|<hcreportdir>] [<hclogfile2>|<hclogdir2>]
Run a healthcheck report or compare healtcheck logs.
Options:
i: only perform checks applicable to pre-install phase (1-6, as well as 9,13 on RNC)
u: only perform checks applicable to pre-upgrade phase (5-8,10-12,14-17)
z: only perform checks applicable to post-upgrade phase (5-8,10-12,14-17, as well as 9 on RNC)
d: perform a diff between two HC log files or two HC log directories
v: verbose printout
Switches:
-r <numbers>: list of checks to perform. Eg: -r 1-3,5,7-10
-x <numbers>: list of checks to skip. Eg: -x 5,12-14
List of checks:
Check numbers Applicability
- 1: Disk space All
- 2: Number of UpgradePackages All
- 3: Number of CVs All
- 4: Security settings RNC
- 5: Alarm list All
- 6: License status All
- 7: HW status All
- 8: HW supported by release RNC
- 9: DB consistency RNC,RBS,ENB
- 10: Synchronization status All
- 11: NTP status RNC,RBS,ENB
- 12: Fault Tolerant Core status RNC
- 13: File System consistency RNC,RBS,ENB
- 14: Crash history All
- 15: Connectivity status All
- 16: Cell status All
- 17: Device status RNC
Arguments for hc[iuz][v]:
no argument: only applicable when connected to the node. Will generate a hclogfile, then parse it to generate a hcreportfile.
<hclogfile>: parse an existing hclogfile to generated a hcreportfile.
<hclogdir> : parse existing hclogfiles stored in a common folder to generate a set of hcreportfiles that will be stored in a
new folder.
<hcreportdir>: parse existing hcreportfiles stored in a common folder to generate a common report showing the check
results (OK, NOT OK, OK with Warning) for all the nodes whose logs are stored in that folder.
Output files produced by hc[iuz][v]:
HcLogFile: a file containing a set of moshell printouts taken from the node (eg: invl, dbc, etc). FileName format:
$logdir/hc/logs/.../HcLog_<NodeType>_<NodeName>-<NodeIp>_<HcVersion>.log.gz
ReportFile: a file generated by parsing a hclogfile according to a number of checks resulting in OK, OK with Warning, or
NOT OK. FileName format:
$logdir/hc/reports/.../HcReport_<NodeType>_<NodeName>-<NodeIp>_<HcVersion>.txt
Arguments for hcd[v]:
<hclogfile> : only applicable when connected to the node. Will generate a hclogfile, then compare it toward a hclogfile
previously collected from the same node.
<hclogfile> <hclogfile2>: compare two hclogfiles previously connected from a node to show differences such as active
alarms, scanner states, MO states, operable features, HW state, etc
<hclogdir> <hclogdir2> : compare a set of hclogfiles stored in two separate folders to show differences as listed above.
Only pairs of hclogfiles coming from the same node will be compared.
Output files produced by hcd[v]:
71
Informational
USER GUIDE 72(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
DiffFile: a file generated by parsing two hclogfiles (eg pre and post upgrade log) according to a number of checks resulting
in OK, OK with Warning, or NOT OK. FileName format:
$logdir/hc/reports/.../HcDiff_<NodeType>_<NodeName>-<NodeIp>_<HcVersion>.txt
Filter file:
This is a text file containing configuration settings to tailor the behaviour of the health checks. The default filter file is stored under
moshell/commonjars/scripts/hc/filterfile.txt and should not be modified as it contains the default settings. To modify certain
settings please create a separate filter file containing the settings to be modified and specify its path in the uservariable
hc_filter_file which can be specified in the /.moshellrc or moshell/jarxml/moshellrc .
Batch reports:
1) Collect a set of HcLogFiles and HcReportFiles from a batch of nodes by running:
mobatch <sitefile> ’hc[iuz] [-x <nrs>] [-r <nrs>]’
Note that the options [iuz], -x/-r are optional and only needed in case the user does not need to perform all checks, then
these options allow to save time by skipping collection of certain printouts from the node.
The mobatch job will save all HcLogFiles and HcReportFiles in a folder common for all nodes specified in the sitefile. The
path of this folder will be located under
moshell_logfiles/logs_moshell/hc/(logs|reports)/<date>/<sitefile>/<time>
The exact path can be found by looking inside one of the mobatch logfiles.
2) After the mobatch job is completed, open a moshell offline session not connected to any node (eg just type "moshell" on
its own) and run hc[iuz][v] or hcd[v] against the relevant hc/logs folder(s), according to arguments described further up in
this help. hc[iuz] typically should run toward the hc/reports folder while hcd should run toward a pair of hc/logs folders.
Eg: hc $logdir/hc/reports/<date>/<sitefile>/<time>
or: hcd $logdir/hc/logs/<date>/<sitefile>/<time1> $logdir/hc/logs/<date>/<sitefile>/<time2>
Description of the checks (criteria for OK):
1) Disk space: the amount of free disk space is at least 10% above the limit specified in the filterfile.txt (disk_space*). If
less than 10% above limit, the result will be OK with warning.
2) Number of UpgradePackages: the number of UpgradePackages is less than the limit specified in the filterfile.txt
(nr_ups).
3) Number of CVs: the number of CVs/Backups is less than the limit specified in the filterfile.txt (nr_cvs).
4) Security settings: corba security and ftp client are configured as unsecure
5) Alarm list: there are no active alarms with the severities listed in the filter file (alarm_severities)
6) License status: the license is installed and not in emergency state, the number of days remaining is above the limit
specified in filterfile.txt (license_days), there are no licenses with inconsistent states (eg
ACTIVE&ENABLED&INOPERABLE), the RNC HWAC codes and limits are valid.
7) HW status: no HW is in state unlocked&disabled, and the fault LEDs are OFF and the oper LEDs are ON.
8) HW supported by release: the HW product number/revision is same or higher as specified in the file HW_RNC.csv
9) DB consistency: the result of dbc command is OK
10) Synchronization status: the system clock is in state LOCKED mode.
11) NTP status: there are valid NTP servers
12) Fault Tolerant Core status: the passive core MP is in state StandbyReady.
13) File System consistency: the action ManagedElement.startHealthCheck() returned OK
14) Crash history: there have not been any Crash/PMDs in the past 14 days
15) Connectivity status: there are no unlocked&disabled MO instances of MO class listed in filterfile.txt
(connectivity_mocs)
16) Cell status: there are no unlocked&disabled MO instances of MO class listed in filterfile.txt (cell_mocs)
17) Device status: there are no unlocked&disabled MO instances of MO class listed in filterfile.txt (device_mocs)
4.2.15 diff[a][d][m][o][x][i]/ldiff[a][d][m][o][x][i]
Parameter auditing or MO dump comparisons.
Syntax 1:
Compare two or three MOs side by side. All attribute values that are different between the MOs will be printed.
72
Informational
USER GUIDE 73(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Example:
dif 4 32 17
Where 4, 32, 17 are the proxy identities of the MOs that should be compared.
Syntax 2:
diff[a][d][m][o][x][i]/ldiff[a][d][m][o][x][i] <moGroup>|<moFilter>|<proxy>|<modumpFile>|<modumpDir>
[<baselineFile>|<modumpFile2>|default] [<outputDir>]
Purpose: To compare an MO dump with a parameter baseline file or with another MO dump.
Options:
a: show the list of MOs and attributes that are in the reference but not in the node or dump.
d: compare against the default values in MOM (read from command "momb")
m: when comparing against parameter baseline, any parameter not found in the baseline will be compared against the
MOM default values instead.
o: when comparing two MO dumps, only the differences in configuration parameters will be shown (= attributes that are not
readOnly)
ox: same as diffo but with an additional table showing attribute name differences.
i: to audit the EricssonOnly ("internalmom") parameters of a Gen2 node, using "geti" command. Only applicable to
MSRBSv2 (DUS Gen2). Please make sure to activate the feature "Hidden Parameter Access" (CXC4012188/FAJ1214785)
on the node for faster printout.
Note: It is currently not supported to combine several options together (apart from "o" and "x")
When no option is specified, the attributes are compared against the recommended values in baseline (files
moshell/commonjars/pm/PARAM*)
User variables:
diffo_exclude_attributes : to exclude certain attributes from the MO dump comparison (diffo <dump1> <dump2>)
diffm_exclude_moclasses : to exclude certain MO classes from the MOM default value comparison (diffd and diffm)
diffm_exclude_attributes : to exclude certain attributes from the MOM default value comparison (diffd and diffm)
diffm_exclude_structs : to exclude certain structs from the MOM default value comparison (diffd and diffm)
First Argument:
<moGroup>|<moFilter>|<proxy>: to specify the MOs in the current node which should be used for the comparison.
<modumpFile>: to specify an modump, taken from this node or another node. The modump file should be a zipfile taken
by the command dcgk. Alternatively it can be a text or gzipped file containing the printout from the get or kget command.
<modumpDir>: to specify a directory containing modump logfiles. Only files with the extension ".log" will be used in the
comparison.
Second Argument (optional):
empty or "default": a baseline parameter file from moshell/commonjars/pm/PARAM* will be chosen according to the MOM
type and version of the current node or of the modump specified in the first argument. Note: typing "default" is only
necessary if one wants to specify a third argument (the outputDir).
If the uservariable custom_param_file is set then the file(s) specified in custom_param_file are read after the
PARAM* file, meaning that their values will override those of the PARAM* file. The default parameter baseline files in
moshell/commonjars/pm/PARAM* are extracted from the following documents: RNC: 3/19059-HSD10102. RBS:
4/19059-HSD10102. RXI: 5/19059-HSD10102. ENB: 19706-CXP102051/*
<baselineFile>: a specific baseline file is used as reference, instead of the default one.
In this case the file(s) specified in the uservariable custom_param_file are not read.
The format of a baseline file must consist of three words on each line: <mo> <attribute> <value>
The <mo> field can be either an MO class (e.g. PlugInUnit) or an MO LDN (e.g.
Subrack=MS,Slot=1,PlugInUnit=1)
It is also possible to write a tilde sign ( ) in front of the MO LDN, in which case it is treated as a regular expression.
For instance: ~UniSaalTp=.*q[ab]$ maxSduSize 128 means that the reference value only applies to the MOs
whose LDN matches that string.
The recommended value can be a single value or several values separated by commas. For instance -1,2,25,300 :
means any of these values is accepted as recommended value. If the recommended value is a sequence of Structs or
73
Informational
USER GUIDE 74(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
sequence of moRefs, then it shall be written on one single line. In case of sequence of Structs, the struct members must be
alphabetically sorted (in order of struct member name) and the struct member names shall not be specified, only the struct
member values. Example:
EthernetSwitch pbitQueueMap [8] = 0,1;1,0;2,1;3,1;4,2;5,2;6,3;7,3
EUtranFreqRelation eutranFreqToQciProfileRelation [9] = 0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,1 (FORBIDDEN),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci1;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci2;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci3;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci4;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci5;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci6;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci7;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci8;0,0,0,0,0 (ALLOWED),0 (ALLOWED),0,0,0,0 (ALLOWED),ENodeBFunction=1,QciTable=default,QciProfilePredefined=qci9
If the reference file contains several entries with the same MO / attribute, the following priority rules apply:
1. Lines with a fixed value take precedence over lines containing Iu/Iur/Iub, regardless of the order. Eg:
Sctp pathMaxRtx Iu, Iur: 4 Iub: 12
Sctp pathMaxRtx 13
-> The line with value 13 will be used, regardless if it is before or after the Iu/Iur/Iub line.
2. Lines containing a tilde: the first entry takes precedence. Eg:
~Sctp pathMaxRtx 13
~Sctp pathMaxRtx 14
-> The line with the value 13 will be used as reference.
3. Lines containing no tilde: the last entry takes precedence. Eg:
Sctp pathMaxRtx 13
Sctp pathMaxRtx 14
-> The line with the value 14 will be used as reference
More information about the reference file format can be found in the document
moshell/examples/audit_files/EAB_FJW-08_0071.doc
<modumpFile>: the two modump logfiles are compared and the following differences will be highlighted: differences in
attribute values, MOs found in one dump but not the other, attribute names found in one dump but not the other.
Third Argument:
<outputDir>: to specify the directory where to store the result files (csv comparison file and correction command file). If not
specified, a default directory and file names are chosen.
Result:
The result is shown on screen with space-separated fields and also saved in the result directory with comma-separated fields
(CSV). Also, in the result directory is a command file to align the current values to the baseline values. The path to the CSV result
file is saved in the moshell variable $diffcsvfile and the path to the command file is saved in the moshell variable
$diffcmdfile.
Please refer to the document moshell/examples/audit_files/EAB_FJW-08_0071.doc for more information.
Note about parameter baseline files:
Parameter baseline files are taken from the Winnow database and stored in CDM in excel format:
RNC: 3/19059-HSD10102
RBS: 4/19059-HSD10102
RXI: 5/19059-HSD10102
ENB: 19706-CXP102051/*
To use these files as reference for comparison, they need to be converted to text. This can be done by copy pasting the excel
sheet to a text file. Moshell keeps a text copy of the latest version of each of these files in the folder moshell/commonjars/pm. By
not specifying the baseline parameter file in the "diff" command will make moshell choose the best suited file for the node type
and mom version of the current node or modump file.
Examples:
diff . - Compare all MOs with the relevant baseline parameter file stored in moshell/commonjars/pm.
diffa . - Same as above but showing MO/attributes found in reference but not in node
diff . default ~/audit\_070110 - Same as above but store the results in the directory /audit_070110
diff ~/moshell_logfiles/logs_mobatch/2007-01-10/mysites/11-21 - Compare all modumps under that
directory against the relevant baseline parameter file stored in moshell/commonjars/pm
ldiff msplatform=1 mgw\_parameters\_r4.txt - Compare all MOs under msplatform=1 in the current node with
the baseline file "mgw_parameters_r4.txt"
74
Informational
USER GUIDE 75(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
diff . rnc10\_before\_upgrade.txt - Compare all MOs in the current node with the MO dump
"rnc10_before_upgrade.txt"
diff rnc10\_before\_upgrade.txt rnc10\_after\_upgrade.txt - Compare the MO dumps
"rnc10_before_upgrade.txt" and "rnc10_after_upgrade.txt"
diffo rnc10_before_upgrade.txt rnc10_after_upgrade.txt - Same as above but only the configuration
parameters are compared
diffd utrancell - compare all utrancell parameters against MOM default values.
4.2.16 lkr[a]
Print RNC Iub resources allocation.
Purpose:
display the repartition of IubLinks and UtranCells across rncModules and Subracks, to identify any uneven resource
allocations, for instance: rncModules that are handling more Iub/Cells than others, or CC devices that are handling different
Cells than their controlling module MP.
uneven allocation of IubLinks across RncModules can be corrected by the command resub iublink
uneven allocation of UtranCells across CC devices can be corrected by locking/unlocking the cells using command bl and
deb on the UtranCell MOs.
with the option a, an additional table shows the IubLinks whose AtmPort(s) are located in a different Subrack than the Iub
module resources. IubLinks can be moved to a different AtmPort or Subrack with the command
resub <iublink> <subrack> or resub <iublink> <atmport/vp>. Type h resub for info.
Printout example and description:
The first table, only printed with option a(lkra), shows the list of IubLinks whose AtmPort(s) are in a different Subrack than the
Iub module resources. The Sr column shows the Subrack containing the module resources, the Mod column shows the module
number, the IubLink column shows the Iub, and the AtmPort(s) column shows the port(s) used by the Iub. Example:
--------------------------------------------------------------
Sr Mod IubLink AtmPort(s)
--------------------------------------------------------------
MS 1 Iub-198 ES-1-27-2-1
MS 13 Iub-203 ES-1-27-2-1
MS 8 Iub-208 ES-1-27-2-1
MS 1 Iub-213 ES-1-27-2-1
MS 13 Iub-214 ES-1-27-2-1
MS 1 Iub-87 ES-1-3-1-1
MS 8 Iub-88 ES-1-3-1-1
MS 1 Iub-89 ES-1-3-1-1
MS 13 Iub-90 ES-1-3-1-1
MS 8 Iub-91 ES-1-3-1-1
MS 1 Iub-92 ES-1-3-1-1
MS 13 Iub-93 ES-1-3-1-1
MS 8 Iub-94 ES-1-3-1-1
MS 1 Iub-95 ES-1-3-1-1
MS 13 Iub-96 ES-1-3-1-1
--------------------------------------------------------------
The second table (which is the first table when option "a" is not used) shows the resources allocation, module by module.
Sr : the subrack containing the module resources
Mod : the module number
S: the state of the module MP: L=locked, 1=enabled, 0=disabled
GPB : the board type of the module MP
nIub : the number of IubLinks handled by the module MP. Having an equal number of IubLinks/Cells on each module gives
a better spreading of the load.
CellGPB: the number of UtranCells handled by the module MP
CellCC : the number of UtranCells handled by the CC devices controlled by that module MP.
nCC : the number of CC devices allocated to this RncModule.
75
Informational
USER GUIDE 76(159)
Prepared (also subject responsible, if other) No.
EAB Finn Magnusson 1553-CXC1328930
Document responsible/Approved Checked Date Rev. File
EAB Finn Magnusson 2018-10-30 BX moshellUserGuide.tex
Note: if the cell to CC device allocation has changed since the moshell session was started, the command "bor" needs to be run
in order to refresh the moshell cache, otherwise the values in "CellCC" field could be wrong.
Cell repartition by rncModule:
-----------------------------------------------
Sr Mod S GPB nIub CellGPB CellCC nCC
-----------------------------------------------
MS 60 1 GPB65 14 90 117 1
MS 80 1 GPB65 13 81 114 1
MS 110 1 GPB65 14 90 119 1
MS 140 1 GPB65 14 93 117 1
-----------------------------------------------
ES1 21 1 GPB65 14 99 118 1
ES1 81 1 GPB65 14 99 114 1
ES1 151 1 GPB65 14 111 119 1
ES1 181 1 GPB65 14 96 106 1
ES1 211 1 GPB65 14 105 103 1
ES1 2121 1 GPB75 13 102 114 1
ES1 2122 1 GPB75 13 87 114 1
-----------------------------------------------
ES2 3021 1 GPB75 14 93 140 1
ES2 3022 1 GPB75 14 99 0 0
ES2 3081 1 GPB75 14 90 140 1
ES2 3082 1 GPB75 14 93 0 0
ES2 3121 1 GPB75 15 99 140 1
ES2 3122 1 GPB75 14 96 0 0
ES2 3151 1 GPB75 14 99 114 1
ES2 3152 1 GPB75 14 96 113 1
ES2 3181 1 GPB75 14 102 120 1
ES2 3182 1 GPB75 14 102 99 1
ES2 3211 1 GPB75 14 93 87 1
ES2 3212 1 GPB75 14 93 0 0
-----------------------------------------------
The third table (which is the second table when option "a" is not used) is identical to the previous one but aggregated on Module
Board level. In the case of GPB5/GPB6 it will give the same figures as the previous table but in the case of multicore boards
(GPB75/EPB) it gives agg