
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
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.
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] [] [] [] [] [] 21 4.1.2 lt/clt/ltc[1-9] |root|all [ AND/OR ] 23 4.1.3 lc/lcc[1-9] |||all 23 4.1.4 ld[c] 24 4.1.5 lu/llu || 24 4.1.6 pr[s][m]/lpr[s][m] [||] [] 24 4.1.7 ma[i]/lma[i] |||all [] [] 25 4.1.8 mr[i]/lmr[i] |||all [] [] 25 4.1.9 mp 26 4.1.10 get[m][i]/lget[m][i] [|||all] [|all] [] 26

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] || [] [] [] [] etc 27 4.1.12 kget[m]/lkget[m] [||] [] [] [] [] 28 4.1.13 fro/lfro[m] |||all [|all] [] 28 4.1.14 sql/select [ | ] 29 4.1.15 st/lst |||all [] 29 4.1.16 prod | [] 29 4.1.17 lk/llk || 29 4.1.18 lko/llko || 30 4.1.19 set[m][c][1][i]/lset[m][c][1][i] || [] 30 4.1.20 eset[c][1]/leset[c][1] || [] 31 4.1.21 rset/lrset || [] 31 4.1.22 bl[s]/lbl[s] || 31 4.1.23 deb/ldeb || 32 4.1.24 acl/lacl |||all [] 32 4.1.25 acc[e][n]/lacc[e][n] |||all 32 4.1.26 cr[e][n] 33 4.1.27 del[b]/ldel[b] || 34 4.1.28 rdel/lrdel || 34 4.1.29 gm[c][d]/lgm[c][d] || 35 4.1.30 sc[g][w][d] [] 36 4.1.31 safe+/safe-/safe? 36 4.1.32 s+/s++/s-/s? 37 4.1.33 u+[s]/u-/u? [] 37 4.1.34 run[x][1][1p][1r] [-l ] [] [] 39 4.1.35 trun[is1cr] |

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 ] [-m ] [-p ] [-s ] [-e ] [-g ] [-n ] [-x ] [-b ] [-d ] [] [|] 88 4.3 Other commands 93 4.3.1 uv [|=value] 93 4.3.2 pv [] 94 4.3.3 !/l 94 4.3.4 l+[m][m][s][o]/l-/l? [] 94 4.3.5 dbc[s][a] [|||] 95 4.3.6 dbd[p] [||] [||] 101 4.3.7 dbcv[r] 101 4.3.8 [|] 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] [] 104 4.3.14 c+/c1/c2/c-/c?/c0 104 4.3.15 [|] 105 4.3.16 mcl[d] [] [] 106 4.3.17 mcc/lmcc || [|] 106 4.3.18 bo[ar]/ba[swdpmu]/br[wdm]/be[0-50]/bp 106 4.3.19 lh[z] | |run [ | ] 109 4.3.20 mon[?][d][u][f][s][t][k][a][-] [

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] [] [] [] [] [] 127 4.4.3 pget/lpget [|||all] [|all] [] 128 4.4.4 spget/lspget [|||all] [|all] [] 128 4.4.5 hpget[c][m]/lhpget[c][m] || [] [] [] [] etc 128 4.4.6 pdiff/lpdiff [|||all] [|all] [] 128 4.4.7 hpdiff[m]/lhpdiff[m] [|||all] [|all] [] [] [] 128 4.4.8 pmx[hfdnsckwlb3zeity] [|] [|] [-l |] [-w ] [-m ] [-p ] [-s [.]] [-e [.]] [-a|-d|-h] [-o ] [-tz ] [-f ] [-j ] [-mo ] [| ] . 129 4.4.9 pmr[agfkwop3z] [-g |] [-z ] [-r ] [-l |] [-w ] [-i ] [-f ] [-c ] [-m ] [-p ] [-s [.]] [-e [.]] [-o ] [-t ] [-tz ] [|] 131 4.4.10 pme[fd][cgurv] [] [-b ] [-f ] [-m ] [-p ] [-s [.]] [-e [.]] 134 4.4.11 pst [|] [] 135 4.4.12 pgets[m][n][r] [|] [] 135 4.4.13 pcr[pcfpdaz]/lpcr[pcfpdaz] ||| [] [] 136 4.4.14 pcrk[f][v][d] [] [] 137 4.4.15 pbl | 138 4.4.16 pdeb | 138 4.4.17 pdel | 138 4.4.18 emom [uetr|gpeh|ctr|all] [] 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

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.1 Contact
For bug reports, installation issues, change requests etc. please use the forum on the moshell homepage.
Put bug reports on the web page (see Section 1.1) or write them in MHWEB:
To write an MoShell TR/CR in MHWEB:
In order to get the fastest resolution to your problem, please add the following information to your TR or bug report:
TR for MoShell

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
**************************************** | 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:
The MO is a way of modelling resources in a CPP node. It consists of:
The purpose of the MAO (Management Adaptation Object) is to interface towards the various O&M services described above.
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.

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.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.

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
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
MoShell is a text-based O&M client providing access to the following services:
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.
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1,Program=DbmFpgaLoader

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
1.6.3 Configuration Service
Moshell supports the following 6 operations from the configuration service:
1.6.4 Performance Management Service
Moshell supports the following operations from the performance management service:
1.6.5 Log service
Moshell supports fetching and parsing of the following logs:
1.6.6 File transfer
Moshell can download/upload files and directories to/from the node, using http, ftp or sftp.

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.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 ) 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.
(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:
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:
Then try running the following command, while logged in as root:
chcon -t texrel_shlib_t commonjars/ssh
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.
moshell

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
In the "Run" window, type: cmd , then press .
A DOS window opens. At the DOS prompt, execute the following commands:
c:
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.
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
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 .
If you have set the PATH variable correctly in your ~/.bashrc file, you should be able to run moshell from any directory. E.g:
The moshell directory contains a number of files and subdirectories:
cd cygwin · moshell

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
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 |
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:
2. Check the node’s MOM version The node’s MOM is fetched from http://nodeipaddress/cello/oe/xml/<filename> where 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: 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.
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:
The menus are split into two (m and n) only for readability purposes.

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 3 or 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 4 or 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.
pr plu #then lookup the proxy identity of that MO get #enter the MOs proxy identity as argument to the "get" command
get plu #the get command will operate on all MOs whose RDN matches "plu"
More info about this in Section 3 or by typing h syntax at the Moshell prompt.
Help for each command can be found in Section 4 or by typing h 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:
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:
It is possible for many users to run moshell from a central location and have their logfiles, credential files, user variables and
lget ms,slot=19,pluginunit=1$

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:
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).
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.

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
So, in order to enable ssh/sftp instead of telnet/ftp, do one of the following:
uv secure_shell=1 uv 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).
To specify which corba SW and corba security settings moshell should be using, use the following values of the user variable corba_class.
– 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.
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.
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:
secure_shell=1 secure_ftp=1

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
For ECIM/COM nodes:
More info in the CPI document "Node Hardening Guidelines"
Please refer to instruction in the file moshell/examples/misc/RSG_tunnels_instruction.txt
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 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:
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:
AtmPort=MS-24-1 · ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1 · SubNetwork=AUS,SubNetwork=H2RG_0201,MeContext=St_Leonards_Station_2065010,ManagedElement=1,TransportNetwork=1,AtmPort=MS-24-1

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
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):
All loaded MOs will be affected. Example:
a) get all userlabel to get attribute UserLabel on all MOs
All MO(s) with the given proxy id(s) will be operated upon.
To specify several MO proxies, there are two ways:
a) pr 0 2 5 to print the MO proxies 0, 2 and 5.
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.
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!
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.
MOs (PlugInUnit or Spm) mapped onto the boards belonging to the given board group will be operated upon.
Example 1:
MO(s) whose LDN/RDN match the regular expression pattern will be affected.
If the command starts with l then 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.

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).
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
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.
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:
Examples of using meta-characters:

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
Regular expressions can also be grouped together using brackets, e.g:
Examples of using regular expressions in the filters:
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
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
TransportNetwork=1,AtmCrossConnection=AtmCC1 TransportNetwork=1,AtmCrossConnection=AtmCC2 TransportNetwork=1,AtmCrossConnection=AtmCC3 TransportNetwork=1,AtmCrossConnection=AtmCC4
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
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
Equipment=1,Subrack=1,Slot=20,PlugInUnit=1,Etm4=1,Os155PhysPathTerm=1 Equipment=1,Subrack=1,Slot=20,PlugInUnit=1,Etm4=1,Os155PhysPathTerm=2 · TransportNetwork=1,AtmCrossConnection=AtmCC1 TransportNetwork=1,AtmCrossConnection=AtmCC3 TransportNetwork=1,AtmCrossConnection=AtmCC5 · Equipment=1,Subrack=1,Slot=6,PlugInUnit=1,Program=1

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
Example:
set sid sib11 sib11repperiod=128 set mtp3bspitu sppriority prioslt=2 set mtp3bspitu sppriority prioslt=2,prioco=2
It is also possible to skip the first parent (eg TransportNetwork, SwManagement, etc). E.g.:
Attribute 1 of 1, utrancellref (moRef:UtranCell): utrancell=30521
set jvm admclasspath loadmodule=oms loadmodule=vbjorb ...
Parameter 1 of 1, aal2PathVccTpId (sequence-moRef-Aal2PathVccTp):
set antfeedercable=6 ulattenuation 10,10,10,10,10,10,10,10,10
set antfeedercable=6 ulattenuation 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
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
set 0 userlabel set reliableprogramuniter admpassiveslot
The command line uses the Readline library from bash. Here are some of the supported function keys:

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
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 l or ! 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
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.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.

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
Some of the options can be combined, see examples below.
After execution of the MOM command, two scripting variables are automatically created:
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.
![Page 23 of the Ericsson MoShell user manual — lt/clt/ltc[1-9] <motype-filter>|root|all [<attribute==value> AND/OR <attribute==value>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-23.webp?w=400)
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:
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 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:
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:
– 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).
![Page 24 of the Ericsson MoShell user manual — ld[c] <ldn>](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-24.webp?w=400)
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
– lc 5 6 7 load children of proxys 5, 6, and 7.
– 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 c option, the subtree below the MO is also loaded.
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:
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.
For further information see Section 3 or 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.
![Page 25 of the Ericsson MoShell user manual — ma[i]/lma[i] <moGroup> <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>] [<value-filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-25.webp?w=400)
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 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
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.

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.
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).
![Page 27 of the Ericsson MoShell user manual — hget[c][m][i]/lhget[c][m][i] <moGroup>|<moFilter>|<proxy(s)> [<attribute-filter>] [<value1-filter>] [<value2-filter>] [<value3-filter>] etc...](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-27.webp?w=400)
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:
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.
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:
$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).
Example:
![Page 28 of the Ericsson MoShell user manual — kget[m]/lkget[m] [<moGroup>|<moFilter>|<proxy(s)>] [<attribute-filter>] [<attribute-type>] [<attribute-flag>] [<attribute-description>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-28.webp?w=400)
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
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 m option 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.
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.
![Page 29 of the Ericsson MoShell user manual — sql/select <command> [ | <unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-29.webp?w=400)
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".
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 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.
4.1.16 prod <moGroup>|<moFilter> [<productdata-filter>]
Print the attribute productData on applicable MO(s).
It is similar to typing "hget 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:
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).

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:
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.
setm utrancell=3012 locationarearef locationarea=9
servicearearef locationarea=9,servicearea=1 routingarearef locationarea=9,routingarea=1
![Page 31 of the Ericsson MoShell user manual — eset[c][1]/leset[c][1] <moGroup>|<moFilter>|<proxy(s)> <attribute-filter> [<value>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-31.webp?w=400)
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
Please see Section 3 and 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 c and 1.
>> eset . featurestate 1
>> 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.
A restricted 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 s option 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 s option, the resource is locked immediately.
To unlock an MO, use the command deb/ldeb.

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
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.
4.1.24 acl/lacl <moGroup>|<moFilter>|<proxy(s)>|all [<action-filter>]
Lists available MO actions.
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
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.
![Page 33 of the Ericsson MoShell user manual — cr[e][n] <ldn>](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-33.webp?w=400)
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
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 e can be used, in which case each struct member is prompted on a separate line (command: acce/lacce).
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 d to select default value. To abort, type at the prompt.
cr swmanagement=1,upgradepackage=FAB102572%2_R14D.xml cr rncfunction=1,iublink=2456 cre swmanagement=1,loadmodule=CXC123456_R9A crn rncfunction=1,iublink=90
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!):
Alternatively, the option e can 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 , 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.
productnumber=CXC1322155/2,productrevision=R3C08,productname=test, · productinfo=test,productiondate=20010229
![Page 34 of the Ericsson MoShell user manual — del[b]/ldel[b] <moGroup>|<moFilter>|<proxy(s)>](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-34.webp?w=400)
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:
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
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:
del 46-22
![Page 35 of the Ericsson MoShell user manual — gm[c][d]/lgm[c][d] <moGroup>|<moFilter>|<proxy(s)>](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-35.webp?w=400)
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
4.1.29 gm[c][d]/lgm[c][d] <moGroup>|<moFilter>|<proxy(s)>
Generate MO Creation/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.
![Page 36 of the Ericsson MoShell user manual — sc[g][w][d] [<parameterlist>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-36.webp?w=400)
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
4.1.30 sc[g][w][d] [<parameterlist>]
Read/Write/Reset SystemConstants.
Syntax:
Syntax examples:
4.1.31 safe+/safe-/safe?
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

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.
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
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.

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
While running in "undo mode", the MO data is saved in a special logfile for all MOs on which the following commands are run:
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:
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:
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.
– 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)
![Page 39 of the Ericsson MoShell user manual — run[x][1][1p][1r] [-l <lineNr>] <command file> [<var1>] [<var2>] ...](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-39.webp?w=400)
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
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.
– $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:
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 .
![Page 40 of the Ericsson MoShell user manual — run[x][1][1p][1r] [-l <lineNr>] <command file> [<var1>] [<var2>] ...](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-40.webp?w=400)
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.
Command description. See syntax examples further down.
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
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
productData Struct · nrOfElements 5
![Page 41 of the Ericsson MoShell user manual — run[x][1][1p][1r] [-l <lineNr>] <command file> [<var1>] [<var2>] ...](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-41.webp?w=400)
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 )
)

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 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 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:
Options applicable for COM nodes:
![Page 43 of the Ericsson MoShell user manual — re[i]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-43.webp?w=400)
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.
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):
To abort the polling, do ctrl-z, then touch (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.
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
![Page 44 of the Ericsson MoShell user manual — parsemom [<momFile>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-44.webp?w=400)
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:
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.
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.
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).
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).
>> getmom RNC_NODE_MODEL_K_9_115_COMPLETE
![Page 45 of the Ericsson MoShell user manual — facc/lfacc <moGroup>|<moFilter>|<proxy(s)>|all <action> [<param1>] [<param2>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-45.webp?w=400)
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.
Following attribute types are supported:
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:
Otherwise it should be explicitely specified, using the reference list below. Examples:
Following parameter types are supported:

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
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.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):
Command syntax and description (COM):
![Page 47 of the Ericsson MoShell user manual — inv[hlxbpctrgfa] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-47.webp?w=400)
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
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.
The options are used to reduce the number of tables displayed. Without options, all tables are displayed.
![Page 48 of the Ericsson MoShell user manual — inv[hlxbpctrgfa] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-48.webp?w=400)
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
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 r switch 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:
Printout description:
The information about restricted features is read from the documents 2/22104-FGB101135 and 4/19812-FGB101135.
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.
![Page 49 of the Ericsson MoShell user manual — inv[hlxbpctrgfa] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-49.webp?w=400)
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
Description of the LED columns:
Description of the fields in the RDS/DOT table (only applicable for RBS/ENB containing IRUs with DOTs):
Description of the fields in the CPRI table (only applicable for RBS/ENB):
Description of the fields in the SFP diagnostics table (only applicable for RBS/ENB containing optical CPRI links):
![Page 50 of the Ericsson MoShell user manual — inv[hlxbpctrgfa] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-50.webp?w=400)
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.
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
Description of the fields in the graphical view
– 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

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
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.
The following OSE commands are run and parsed by the various "cab" functions:
![Page 52 of the Ericsson MoShell user manual — cab[adefghlmrstxc] [ | <unix-cmds> ]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-52.webp?w=400)
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
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%).
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.
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.
For RU PL4:
Where:
For RU PL5:
Where:
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.
For most RUs/RRUs, the main command used for printing the return loss is fui get vswr . On AIR21, AIR32, RUS12m, and mRRUS12, the command used is fuia get antquality 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.
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.
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)
![Page 53 of the Ericsson MoShell user manual — sdi[eacr]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-53.webp?w=400)
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
4.2.4 sdi[eacr]
System Diagnostics CPRI.
Perform a system diagnostics test of the RBS/ENB CPRI links.
Printout format, first table
Each line in this table represents a CPRI link.
======================================================================================================= ID ;RiL ;Type ;Res ;MO1-MO2 ;BOARD1-BOARD2 ;AlmIDs ;Cells ;Issue (Failed chec =======================================================================================================
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 (Dl 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 ... 15 ;13 ;O25 ;OKW ;XMU03(11) RRU-101(D1) ;XMU03 RRUS12B2 ; ;FDD=9A_1 ;Conditionally Pass
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 ;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
![Page 54 of the Ericsson MoShell user manual — stc[p][r] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-54.webp?w=400)
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 por
======================================================================================================= AlmID ;IDs ;RiLs ;Status ;Alarm ======================================================================================================= 1 ;5 ;5 ;A ;Inconsistent Configuration - FieldReplaceableUnit=6 (No hardwa 2 ;6 ;6 ;A ;Inconsistent Configuration - FieldReplaceableUnit=7 (No hardwa 3 ;5 ;5 ;A ;Link Failure - RiLink=5 (No signal detected (link start time-o 4 ;6 ;6 ;A ;Link Failure - RiLink=6 (No signal detected (link start time-o 5 ;1,2,3,4,5,6 ;1,3,5,2,4,6 ;A ;Hardware Failure Imminent - Subrack=1,Slot=1,PlugInUnit=1 (HDF
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 ;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 th 2) Refer to and follow Ericsson CPI "Handling SFP Modules and Optical Cables" for proper handling, Cle ******************************************************************************************************* 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 th 2) Refer to and follow Ericsson CPI "Handling SFP Modules and Optical Cables" for proper handling, Cle *******************************************************************************************************
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 r switch 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:
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.
![Page 55 of the Ericsson MoShell user manual — std[ar] [<filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-55.webp?w=400)
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
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,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:
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:
More info found in gradsl printout description in M-MGw Traffic Control Troubleshooting Guideline 25/1553-AXM 101 01/7
std on MGW
![Page 56 of the Ericsson MoShell user manual — std[ar] [<filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-56.webp?w=400)
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 3 7 730700 MSB3 7304 2 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 3 7 730700 MSB3 7304 3 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 3 7 730700 MSB3 7304 4 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 3 7 730700 MSB3 7304 5 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 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 3 7 730700 MSB3 7304 9 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 3 7 730700 MSB3 7304 10 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 3 7 730700 MSB3 7304 11 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 3 7 730700 MSB3 7304 12 111 UMTS_MFD CXC1327790/8_R3L01 325 9594 166 166 57300 57300 57300 3 7 730700 MSB3 7304 13 111 CSD_DIGITAL CXC1327791/8_R3D01 329 11148 16 16 55650 55650 55650 3 7 730700 MSB3 7304 14 111 CSD_DIGITAL CXC1327791/8_R3D01 329 11148 16 16 55650 55650 55650 3 7 730700 MSB3 7304 15 111 CSD_MODEM CXC1327792/8_R3D01 330 11180 16 16 55650 55650 55650 3 7 730700 MSB3 7304 16 111 CSD_FAX CXC1720519/8_R3D02 331 11196 5 5 55650 55650 55650
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:
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 CSDGSMFHPool 288 100 CSDModemPool 128 100
Shows the configuration, status and usage of RNC devices, CC, DC, PDR.
State information is abbreviated in the following way:
std on RNC
![Page 57 of the Ericsson MoShell user manual — std[ar] [<filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-57.webp?w=400)
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:
Common fields:
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
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
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 ...
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:
![Page 58 of the Ericsson MoShell user manual — stv[b][r] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-58.webp?w=400)
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
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.
Arguments:
Printout format:
– 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 and is only shown when option b is 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+.
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
![Page 59 of the Ericsson MoShell user manual — stt[r] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-59.webp?w=400)
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) ...... 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 ......
4.2.8 stt[r] [<Filter>] [<stateFilter>]
Purpose: Display state and user of Physical Ports and Ds0Bundles.
Arguments:
Printout format:
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.
Arguments:
![Page 60 of the Ericsson MoShell user manual — stt[r] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-60.webp?w=400)
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
Command examples:
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.
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.
![Page 61 of the Ericsson MoShell user manual — stt[r] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-61.webp?w=400)
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
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:
Example, RNC3820:
0~~~~~~~~~~~~0 S NETWORK S + >S S< + | 0~~~~~~~~~~~~0 | | |
![Page 62 of the Ericsson MoShell user manual — sti[bcfopr] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-62.webp?w=400)
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 |
4.2.10 sti[bcfopr] [<Filter>] [<stateFilter>]
Purpose: Display state and configuration of IP interfaces.
The printout consists of up to 7 tables:
Arguments:
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.
![Page 63 of the Ericsson MoShell user manual — sti[bcfopr] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-63.webp?w=400)
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
======================================================================================================================= 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 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:
![Page 64 of the Ericsson MoShell user manual — sti[bcfopr] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-64.webp?w=400)
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
======================================================================================================================= 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.
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.
![Page 65 of the Ericsson MoShell user manual — sti[bcfopr] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-65.webp?w=400)
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
======================================================================================================================= 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.
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.
![Page 66 of the Ericsson MoShell user manual — sti[bcfopr] [<Filter>] [<stateFilter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-66.webp?w=400)
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
========================================================================================================================================= 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 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:
=======================================================================================================================

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.
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.
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,Os155 3 INACTIVE OK UNLOCKED ENABLED Subrack=ES-2,Slot=27,PlugInUnit=1,ExchangeTerminal=1,Os15 4 INACTIVE OK UNLOCKED ENABLED Subrack=ES-3,Slot=2,PlugInUnit=1,ExchangeTerminal=1,Os155 5 INACTIVE OK UNLOCKED ENABLED Subrack=ES-3,Slot=27,PlugInUnit=1,ExchangeTerminal=1,Os15
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
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.
radioClockState : FREQUENCY_LOCKED Prio ST syncRefType refStatus opQualLevel SyncReference
*1 1 SYNC_E NO_FAULT PRC Synchronization=1,SyncEthInput=TN_B (SFP_OPTICAL Ethe 2 1 FREQUENCY_PORT NO_FAULT PRC Synchronization=1,FrequencySyncIO=1 (FREQUENCY_1PPS F
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 *3 1 PTP_FREQUENCY NO_FAULT PRC Ptp=1,BoundaryOrdinaryClock=PTP_FREQUENCY (G_8265_1 Ro 4 1 PTP_FREQUENCY NO_FAULT PRC Ptp=1,BoundaryOrdinaryClock=PTP_FREQUENCY_IPV6 (G_8265

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 7 1 PTP_TIME PTP_FAULT QL_UNKNOWN Ptp=1,BoundaryOrdinaryClock=PTP_TIME (IEEE_1588_J3 Eth
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.
SITE C1 C2 C3 ABIS BACKHAUL ATMPORTS 96 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: L means Locked, 0 means Disabled, and 1 means Enabled.
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:
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.
MOD IUBLINK CELLNAME CFRPHEU1 CFRPHEU2 CFRPHEU3 ICDS TN R
1 Iub_3011 3011-1/2/3 1111111 L000000 1000000 1111 I P
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

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
MOD IUBLINK ICDS CELL1 CFRPHEU CELL2 CFRPHEU CELL3 CFRPHEU
1 Iub_3011 1111 30111 1111111 30112 1111111 30113 1111111
IUBLINK MOD TN R ICDS C01 C02 C03 C04 C05 C06 C07 C08 C09 C10 C11 C12 Iub-1523 1111 I P 1111 11 11 111 Iub-1526 1161 A N 1111 111 1 111
– 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:
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 f option (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.
strf | grep 3011 str1f | sort -k 2 (sort on the second field)
![Page 70 of the Ericsson MoShell user manual — dcg[meiasrfkx] [-m <rophours>] [-d <logdays>] [-b <boards|boardgroup>|all] [-k <nrdumps>] [-f <mofilter>] [<logdir>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-70.webp?w=400)
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:
Options for COM nodes:
Switches:
Argument:
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
![Page 71 of the Ericsson MoShell user manual — hc[iuzd][v] [-r|-x <numbers>] [<hclogfile>|<hclogdir>|<hcreportdir>] [<hclogfile2>|<hclogdir2>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-71.webp?w=400)
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.
Switches:
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]:
Output files produced by hc[iuz][v]:
Arguments for hcd[v]:
Output files produced by hcd[v]:
![Page 72 of the Ericsson MoShell user manual — diff[a][d][m][o][x][i]/ldiff[a][d][m][o][x][i]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-72.webp?w=400)
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
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:
Description of the checks (criteria for OK):
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.
![Page 73 of the Ericsson MoShell user manual — diff[a][d][m][o][x][i]/ldiff[a][d][m][o][x][i]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-73.webp?w=400)
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] |||| [||default] []
Purpose: To compare an MO dump with a parameter baseline file or with another MO dump.
When no option is specified, the attributes are compared against the recommended values in baseline (files moshell/commonjars/pm/PARAM*)
User variables:
First Argument:
Second Argument (optional):
![Page 74 of the Ericsson MoShell user manual — diff[a][d][m][o][x][i]/ldiff[a][d][m][o][x][i]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-74.webp?w=400)
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 (F
If the reference file contains several entries with the same MO / attribute, the following priority rules apply:
-> The line with value 13 will be used, regardless if it is before or after the Iu/Iur/Iub line.
~Sctp pathMaxRtx 13 ~Sctp pathMaxRtx 14
-> The line with the value 13 will be used as reference.
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
Third Argument:
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.
Parameter baseline files are taken from the Winnow database and stored in CDM in excel format:
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.
![Page 75 of the Ericsson MoShell user manual — lkr[a]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-75.webp?w=400)
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
4.2.16 lkr[a]
Print RNC Iub resources allocation.
Purpose:
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.
![Page 76 of the Ericsson MoShell user manual — lkr[a]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-76.webp?w=400)
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
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 aggregated values for all RncModules of that board.
Cell repartition by Board: Sr Slot S GPB nIub CellGPB CellCC nCC MS 06 1 GPB65 14 90 117 1 MS 08 1 GPB65 13 81 114 1 MS 11 1 GPB65 14 90 119 1 MS 14 1 GPB65 14 93 117 1 ES1 02 1 GPB65 14 99 118 1 ES1 08 1 GPB65 14 99 114 1 ES1 12 1 GPB75 26 189 228 2 ES1 15 1 GPB65 14 111 119 1 ES1 18 1 GPB65 14 96 106 1 ES1 21 1 GPB65 14 105 103 1 ES2 02 1 GPB75 28 192 140 1 ES2 08 1 GPB75 28 183 140 1 ES2 12 1 GPB75 29 195 140 1 ES2 15 1 GPB75 28 195 227 2 ES2 18 1 GPB75 28 204 219 2 ES2 21 1 GPB75 28 186 87 1
The fourth table (which is the third table when option "a" is not used) shows an aggregated view of the previous table, on Subrack level. This is interesting to see if any Subracks are more loaded than others.
![Page 77 of the Ericsson MoShell user manual — resub <IubLink> [<VplTp>|<Subrack>] [<VplTp>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-77.webp?w=400)
USER GUIDE 77(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
Cell repartition by Subrack: Sr nMod nCC nIub CellGPB CellCC avIub avCell avCellCC MS 4 4 55 354 467 14 88 117 ES1 7 7 96 699 788 14 100 113 ES2 12 8 169 1155 953 14 96 119 Tot: 23 19 320 2208 2208
4.2.17 resub <IubLink> [<VplTp>|<Subrack>] [<VplTp>]
Moving Iub resources within or across Subracks (RNC >= P5).
There are three ways to run the command:
a) Respreading of Iub resources within a subrack: resub <iublink(s)>
The lkr command shows the repartition of Cells/IubLinks across rncModules, Cc devices and Subracks. The performance is affected when the resources allocation is uneven. The Cells/IubLinks resources can be evenly reallocated by using the command resub . Example:
b) Moving Iub resources to a different subrack: resub <iublink(s)> <subrack>
The lkra command shows the list of IubLinks whose AtmPort(s) are located in a different Subrack than the IubLink. This causes higher ISL load. The IubLink can then be moved to a different Subrack with the command resub . Example:
c) Moving Iub resources to different AtmPort/Vp: resub <iublink> <vp> [<vp>]
When there is is need for more Atm bandwidth it may be necessary to move an Iub to a different Atm port. This can be done with the command resub []. The second vp is optional and only needed for IubLinks that use two AtmPorts for redundancy.
Result:
4.2.18 ir[cdpsomt] [<IubLink>] [<CM>] [<period>]
Iub Redundancy operations for RNC in pool.
![Page 78 of the Ericsson MoShell user manual — resub <IubLink> [<VplTp>|<Subrack>] [<VplTp>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-78.webp?w=400)
USER GUIDE 78(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
Arguments (all optional):
Example printout from irc command:
============================================================================== Iub Redundancy Consistency Check for nodes: RNC01 (CM1) and RNC02 (CM2) ==============================================================================
![Page 79 of the Ericsson MoShell user manual — rinp[c][m] </path/to/rinpm.json>](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-79.webp?w=400)
USER GUIDE 79(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 printout from iro command:
The iro printout consists of 3 tables.
IUBLINK RNC MOD TN R ICDS C01 C02 C03 C04 C05 C06 C07 C08 C09 C10 C11 C12 RNC MOD TN R ICDS C01 C02 C03 C04 C05 Iub-1 CM1 1062 I P 1111 CM2 1162 I S 0000 Iub-10 CM1 1061 I P 1111 CM2 1163 I S 0000 Iub-44 CM1 2221 I N 1111 Iub-569 CM2 3081 I P 0000 CM1 3071 I S 1111
Availability Total Non-Redundant Redundant Redundant-Normal Redundant-Switched IubLinks 818/818 (100%) 273/273 (100%) 545/545 (100%) 108/108 (100%) 437/437 (100%) Cells 6357/6357 (100%) 2121/2121 (100%) 4236/4236 (100%) 840/840 (100%) 3396/3396 (100%) HS channels 6135/6135 (100%) 2043/2043 (100%) 4092/4092 (100%) 807/807 (100%) 3285/3285 (100%) EUL channels 5691/5691 (100%) 1884/1884 (100%) 3807/3807 (100%) 747/747 (100%) 3060/3060 (100%)
4.2.19 rinp[c][m] </path/to/rinpm.json>
Live Node Migration to RNC in Pool.
Arguments:
![Page 80 of the Ericsson MoShell user manual — tg[r][c][d]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-80.webp?w=400)
USER GUIDE 80(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.20 tg[r][c][d]
Print Resource Object information for all MOs in LmCell (RNC only).
Command Syntax:
tg[c][r] [||][:] [] [|] tgd [||][:] []
Purpose:
Arguments: By specifying the first argument, it is possible to filter the Cell/Iubs matching a specific FroId or MOid.
By specifying a second argument consisting of an RRT command or a list of cell parameters, it is possible to run an RRT-command or display certain cell parameters on all the actors that are matched by the first argument.
The list of available RRT commands can be seen by typing:
The list of available cell parameters can be seen by typing:
The printout can be piped into unix commands, like grep and sort.
– Common Channel Device (ccDevice): shows which SPM is used to handle the common channels of this cell
– ccDevice Module (ccMod): shows if a ccDevice is running on an SPM that doesn’t belong to the same module as the
Cell/Iub. This can be fixed by locking/unlocking the cell. It is always best to make sure that all cells are using a ccDevice located in their own module so that the load will be spread equitably on all ccDevices.
![Page 81 of the Ericsson MoShell user manual — tg[r][c][d]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-81.webp?w=400)
USER GUIDE 81(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 view the admission tree usage on all cells (P5 and after)
- to view the cell parameters ulinterference,celldata:errorstatus,etc. on all cells.
- to view the admission tree usage on all cells.
- to view those attributes on all the NbapCommon actors
Output examples:
MOD MFRO ModMP UtranCellId IubLinkId CfRO IfRO CellActor IubActor CcDev
1 0 001400 90121 9012 5 1 1/1/1/1/2/1.3 1/1/1/1/7/1.1/4 0019SP2 1 0 001400 90122 9012 4 1 1/1/1/1/2/1.2 1/1/1/1/7/1.1/4 0020SP0 1 0 001400 90123 9012 3 1 1/1/1/1/2/1.1 1/1/1/1/7/1.1/4 0020SP0
MO ulinterference spblocked spconfigflag cellrostate celldeleted errorstat celltraceactivated UtranCell=90121 -106 0 0 2 0 0 0 UtranCell=90122 -100 0 0 1 0 16002:CellNoDrhResources 0 UtranCell=90123 -100 0 0 1 0 16002:CellNoDrhResources 0
Description:
to view those attributes on all the NbapCommon actors
MO activestatus standbystatus currentcause currentavailabilitystatus rncrbslinkdown rncrbsdeactivated IubLink=1001 1 1 2 2 0 0 IubLink=1002 1 1 2 2 0 0
Description:

USER GUIDE 82(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
– CELLO_USAALEFI_OTHER == 2
– CELLO_USAALEFI_SERVER_MOVED == 3 (introduced in the feature Moveable CEP in P5MD)
to view those attributes on all the NbapCommon actors
MO totasedl totaseul currdlcode UtranCell=30101 320 160 3750 UtranCell=30102 0 0 3593 UtranCell=30103 0 0 3593 UtranCell=30104 1940 969 4218 UtranCell=30105 2064 1568 4375 UtranCell=30106 991 911 3984
Description:
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]
Print UE registry or UE context data (serving or drifting) for all active calls (RNC only).
The command ueregprint is a moshell alias that runs the coli command "ueregprint" on all RNC RANAP boards. It allows all the same arguments as the regular ueregprint command but does not require to specify the board on which it should run. This is especially useful for EvoC node where the UE registry is running in all the blades.
Example:
The command uer is a moshell command that prints the UE contexts in each module MP in order to show the details of call.
The following COLI commands are used: ueregprint (on C2/Ranap MP), drh_trbr rab (on PDR module MPs), and printUeCtxt (on module MP). No RRT commands are used.
![Page 83 of the Ericsson MoShell user manual — ueregprint/uer[d][t][i][s][p][v] [-m <mod>|-i <imsi>|-u <ueref>|-n <maxUes>|-c <utrancell>|-r <iublink>] [<attribute-filter>[=<value>]|all]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-83.webp?w=400)
USER GUIDE 83(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
Filtering Options:
The attribute-filter can be:
If the attribute-filter is empty, then three tables are printed:
– SRNC: the Serving RNC. Read from the variable sRncId.
– CommCh: the rbsid and cell id (cid) of the serving cell providing the Common Channels for this UE. Read from the
variable commonResData.cId
– RL1-4: the rbsid and cell id (cid) of the serving cells providing the radio links for this UE (up to 4 radio links per UE).
Read from the variables radioLink[0-3].cId
– DCdev: the DC device handling the call. Read from the variable drhRcSpId.
lh mod drh_trbr rab.
– CoreNetId: the Type of Core Network connecting the call: CS or PS. Read from the variables isCNConnected.*Circuit
and isCNConnected.*Packet. Also shows the Id of the Core Network used for the call (mcc/mnc/cnId). Read from the variables globalCnIdPs and globalCnIdCs.
– UERC: the UeRc used by the call. Read from the variable connType.
Examples (with empty attribute-filter):

USER GUIDE 84(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
matches iub.*1$ (works only on RNC P6 and above)
See output example below:
========================================================================================================================= MOD IMSI/TMSI CTXT CommCh RL1 RL2 RL3 DCdev PDRdev CoreNetId AGE UERC + ESTAB_CAUSE =========================================================================================================================
1 301020430130001 1826 746:2907 20:1174 0923sp3 P 24099 5 Interact. PS (64/64) (2:origInteractive) 1 301001920070001 287 68:1178 0022sp2 0019sp0:1 P 24099 00:00:52 5 Interact. PS (64/64) (2:origInteractive) 1 301000310030000 309 298:1875 0021sp3 0019sp0:0 CP 24099 00:01:28 9 Conv. CS speech 12.2 + Interact. PS (0/0) (2:origInteractive) 1 301010330100000 5778 680:2951 0923sp3 0019sp0:0 P 24099 00:01:59 4 Interact. PS (RACH/FACH) (2:origInteractive) 1 301001630000000 5565 582:2848 71:1205 0023sp2 C 24099 00:00:14 2 Conv. CS speech 12.2 (0:origConversational) ......
===================================================== UeRc M1 M8 M13 userLabel =====================================================
1 14 13 4 Standalone RRC on DCH 2 75 55 55 Speech 3 18 30 22 64kbps CS data, fixed rate 4 13 9 17 Packet RACH/FACH 5 5 1 2 PACKET 64/64 7 1 0 0 Packet 64/384 9 0 0 1 Speech + Packet 0kbps 14 0 0 1 CS data 64kbps + Packet 8/8 16 1 0 0 PS Interactive 384/HS - HS-DSCH 18 1 0 0 Packet 128/128 ===================================================== Tot: 128 108 102
===================================================== Cause M1 M8 M13 EstablishmentCause =====================================================
0 65 46 57 origConversational 2 22 13 22 origInteractive 5 30 40 19 termConversational 12 11 9 4 registration =====================================================
=============================================== UeRc Total % userLabel ===============================================
1 31 9.2 Standalone RRC on DCH 2 185 54.7 Speech 3 70 20.7 64kbps CS data, fixed rate 4 39 11.5 Packet RACH/FACH 5 8 2.4 PACKET 64/64 7 1 0.3 Packet 64/384 9 1 0.3 Speech + Packet 0kbps 14 1 0.3 CS data 64kbps + Packet 8/8 16 1 0.3 PS Interactive 384/HS - HS-DSCH 18 1 0.3 Packet 128/128 =============================================== Tot: 338 100
=============================================== Cause Total % EstablishmentCause ===============================================
0 168 49.7 origConversational 2 57 16.9 origInteractive 5 89 26.3 termConversational 12 24 7.1 registration ===============================================
Examples (with attribute-filter not empty):
8 301001800040001 $ UehUexCtxtD[1022]=0x4FE0D058 8 301001800040001 [1022].isActive() = 1 8 301001800040001 [1022].isCNConnected(uehCNidCircuit) = 0 8 301001800040001 [1022].isCNConnected(uehCNidPacket) = 1 8 301001800040001 [1022].sRncId = 301 8 301001800040001 [1022].softHoDone = 1 8 301001800040001 [1022].isPmRecordingActive = 0 8 301001800040001 [1022].recordingProt = 1 8 301001800040001 [1022].dlPcMethod = 3 8 301001800040001 [1022].dlRefPwrVal = -165 8 301001800040001 [1022].supportOfGsm = 1 8 301001800040001 [1022].tmpRanapConnId = -1 8 301001800040001 [1022].recordingMeas = 0 8 301001800040001 [1022].measBERrequested = 0 8 301001800040001 [1022].measBLERrequested = 0 etc • uer . aal2.*cepid$|softho|\.rcindex$ - for all UEs, print UeContext attributes that match the regexp "aal2.*cepid$|softho|˙rcindex$"
1 301001800060003 softHoDone=1 rcIndex=4 1 301001701000000 softHoDone=0 rcIndex=2 aal2Arr[0].cepId=477 aal2Arr[1].cepId=494 1 301001810040000 softHoDone=1 rcIndex=4 1 301001700000001 softHoDone=1 rcIndex=2 aal2Arr[0].cepId=76 aal2Arr[1].cepId=77 aal2Arr[2].cepId=141 aal2Arr[3].cepId=142 1 301001720000003 softHoDone=1 rcIndex=2 aal2Arr[0].cepId=507 aal2Arr[1].cepId=508 aal2Arr[2].cepId=332 aal2Arr[3].cepId=333 1 301001720110001 softHoDone=1 rcIndex=2 aal2Arr[0].cepId=424 aal2Arr[1].cepId=425 1 301001810000003 softHoDone=1 rcIndex=2 aal2Arr[0].cepId=476 aal2Arr[1].cepId=482 aal2Arr[2].cepId=166 aal2Arr[3].cepId=167 1 301001711000002 softHoDone=1 rcIndex=2 aal2Arr[0].cepId=52 aal2Arr[1].cepId=57 aal2Arr[2].cepId=170 aal2Arr[3].cepId=171
The path to the stopfile can be found in the window title.
![Page 85 of the Ericsson MoShell user manual — ced[h][p][s][g][r] [-m <module(s)>|-c <utrancell>|-r <iublink>|-s <rsite>] [ | <unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-85.webp?w=400)
USER GUIDE 85(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.22 ced[h][p][s][g][r] [-m <module(s)>|-c <utrancell>|-r <iublink>|-s <rsite>] [ | <unix-cmds>]
Print consumption of cell resources and rbs hw, cell supported features, cell coordinates (RNC only).
The r option can be used together with any of the above, in order to clear the moshell cache and fetch latest values from the node.
Filters:
The output can be filtered by piping through some unix commands, eg. grep or sort.
Printout format:
> ced MOD CELL cid fro ro PwrDl/Adm dlCode ulInt sf8d sf8u sf16d sf16u sf32d sf4u dlASE ulASE CPMcnt HScnt EULs EULns Eul2 Spch Fdcph Crn Hrn Ern CC_SP
1 Iub-1-1 1031 0 0 7.0% 75% 6.2% -111.8 0/8 0/8 0/16 0/16 0/32 0/4 0/500 0/500 0/15 0/10 1/32 0/100 0/4 0 0/0 1:0019sp1 1 Iub-1-2 1032 1 2 7.0% 75% 6.2% -111.8 0/8 0/8 0/16 0/16 0/32 0/4 0/500 0/500 0/15 0/10 4/32 0/100 0/4 0 0/0 1:0021sp1 1 Iub-1-3 1033 2 3 7.0% 75% 22.9% -111.8 1/8 0/8 0/16 1/16 0/32 0/4 39/500 8/500 0/15 0/10 3/32 0/100 0/4 0 0/0 1:0019sp1 1 Iub-2-1 1037 6 1 7.0% 75% 24.6% -111.8 1/8 0/8 0/16 2/16 1/32 0/4 53/500 20/500 0/15 0/10 0/32 0/100 0/4 0 0/0 1:0019sp1 1 Iub-2-2 1038 7 4 7.0% 75% 10.8% -111.8 0/8 0/8 0/16 2/16 1/32 0/4 12/500 19/500 0/15 1/10 0/32 0/100 0/4 0 0/0 8:0023sp1(!)
The fields in the "ced" printout correspond to the following variables in the "celldata" printout on Module MP:
![Page 86 of the Ericsson MoShell user manual — ced[h][p][s][g][r] [-m <module(s)>|-c <utrancell>|-r <iublink>|-s <rsite>] [ | <unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-86.webp?w=400)
USER GUIDE 86(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
> cedh MOD GRP IUBLINK fro ro nCell usedCEdl usedCEul gHoCEdl gHoCEul OtherCEdl OtherCEul dlRL ulRL nrUE leakingCellFroIds
1 0 b0157MDN 0 0 3 34/64 98/256 30/64 158/256 29/63 155/253 46 46 46 1 4 b0423MDN 5 2 2 2/64 6/128 62/64 122/128 61/63 120/126 3 3 3 1 8 b0407MDN 8 4 1 8/64 42/256 56/64 214/256 55/63 211/253 15 15 15 1 10 b0106MDN 9 5 3 40/96 125/256 56/96 131/256 55/95 128/253 48 48 49 147
> cedhp MOD GRP IUBLINK fro ro nCell usedCEdl usedCEul gHoCEdl gHoCEul OtherCEdl OtherCEul dlRL ulRL nrUE leakingCellFroIds
1 0 b0157MDN 0 0 3 53.1% 38.3% 46.9% 61.7% 46.0% 61.3% 46 46 46 1 4 b0423MDN 5 2 2 3.1% 4.7% 96.9% 95.3% 96.8% 95.2% 3 3 3 1 8 b0407MDN 8 4 1 12.5% 16.4% 87.5% 83.6% 87.3% 83.4% 15 15 15 1 10 b0106MDN 9 5 3 41.7% 48.8% 58.3% 51.2% 57.9% 50.6% 48 48 49 147
The fields in the "cedh/cedhp" printout correspond to the following variables in the "hwm print grp" printout on Module MP:
– from W11: nrUE=nrDlRL and and nrUlRL >= nrDlRL and nrDlRL >= nrDchUlRL and nrUlRL not more than double
This indicates that some resource has not been released properly in the cell. To release the resources in a leaking Cell, the
nrDlRL
![Page 87 of the Ericsson MoShell user manual — al[atkcg][u] [-a|-u <alarm-id>] [ | <unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-87.webp?w=400)
USER GUIDE 87(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
corresponding IubLink MO must be locked and unlocked.
Mod UtranCell CFRPHEMU Antenna and Cell Coordinates, feed into http://maps.google.com/maps?q=
21 CTU20847 111111-- 41.2383,-73.1937 41.2383,-73.193665 41.2424,-73.140621 41.2157,-73.149569 41.1996,-73.179159 41.2016,-73.215508 21 CTU20848 111111-- 41.2383,-73.1937 41.2383,-73.193665 41.2016,-73.215508 41.2208,-73.241665 41.2482,-73.245378 41.2710,-73.224885 21 CTU20849 111111-- 41.2383,-73.1937 41.2383,-73.193665 41.2710,-73.224885 41.2785,-73.189759 41.2672,-73.156478 41.2424,-73.140621 21 CTV20841 111111-- 41.2383,-73.1937 41.2383,-73.193665 41.2424,-73.140621 41.2157,-73.149569 41.1996,-73.179159 41.2016,-73.215508
The fields in "cedg" printout correspond to:
The coordinates are expressed in degree of latitude and longitude and can be fed in google maps to see the location of the cell, eg: http://maps.google.com/maps?q=41.2383,-73.1937
Mod UtranCell CFRPHEMU ABCDEFGHIJKLMNOPQRST cpc dBMC edchT2 enhDrx enhL2 eulDch eulTd fdpch hsAqm hsFach impL2 lBHo mC mCMimo q64 q64Mimo eulMC hsThp hs3MC db3MC 1111 cell17711 111111-L 00100000001100000100 0 0 1 0 1 1 0 1 0 0 1111 cell17712 111111-- 00100000001100010100 0 0 1 0 1 1 0 0 0 1 0 1 0 0 1111 cell17713 111111-- 00100000001100010100 0 0 1 0 1 1 0 0 0 1 0 1 0 0 1111 cell17714 T00000-- 00100000001100000100 0 0 1 0 1 1 0 1 0 0 1111 cell17715 T00000-- 00100000001100010100 0 0 1 0 1 1 0 0 0 1 0 1 0 0
The fields in "ceds" printout correspond to the following attributes:
4.2.23 al[atkcg][u] [-a|-u <alarm-id>] [ | <unix-cmds>]
Print the list of active alarms. Acknowledge/Unacknowledge an alarm.
> cedg · > ceds
![Page 88 of the Ericsson MoShell user manual — - 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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-88.webp?w=400)
USER GUIDE 88(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
Output can be piped through external unix utilities like "sort", "grep", "less", "more", etc.
On CPP nodes, the timestamps are printed by default in local timezone. For UTC time, use option "u", eg altu. On COM nodes, the timestamps are only printed in UTC time.
It is possible to combine several options, eg: al, ala, altk, alatk, altkc, etc. These options are as follows:
The options -a/-u can be used for acknowledging/unacknowledging an alarm. The alarm is identified by its alarm id which can be printed with ala or alc.
Moshell generated alarms: on CPP nodes, the alarm list is read from the Alarm Client Interface (ALCI), however, some additional alarms are generated from moshell in the case where some CPP features are activated and disabled or if TimDevice MOs are missing on RNC, since these MOs would not generate an alarm otherwise. This moshell feature is controlled by the uservariable "mosalarm" and is turned on by default which means that the "al" command takes about 1 or 2 seconds more to execute due to reading the status of those CPP features from the MO Client Interface.
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>]
Fetching and processing of node logs
All options can be combined together, except options d, w, x, f which can only be combined with options r and c.
CPP Log Options:
![Page 89 of the Ericsson MoShell user manual — - 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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-89.webp?w=400)
USER GUIDE 89(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
Pico Log Options:
RCS Log Options (MSRBSv2/TCU):
![Page 90 of the Ericsson MoShell user manual — - 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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-90.webp?w=400)
USER GUIDE 90(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
More information about export uservariables can be found in the file moshell/moshell.
Common Options (CPP/Pico/RCS):
Time filtering (CPP/Pico/RCS):
Offline usage:
The -l option allows to process the logfiles in offline mode, when not connected to the node. The argument of the -l option specifies the location where the logfile(s) are locally stored on the workstation. It can be:
By running the command lgf while connected to the node, it is possible to download all the logfiles to a local directory for later
![Page 91 of the Ericsson MoShell user manual — - 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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-91.webp?w=400)
USER GUIDE 91(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
offline processing. The local directory can be specified as argument. If not specified, a default location is chosen (~/moshell_logfiles/logs_moshell/lg/nodeaddress/date_time). The local directory is then automatically compressed and saved in a zipped archive.
XB log filters (CPP):
The XB log filter is specified with -x in the command lgk on nodes containing CMXB/SCXB boards, to specify the type of logs that will be displayed. The XB log filter shall be given as a combination of one or more of the following letters:
Example:
ESI log filters (RCS):
The ESI (Ericsson Support Information) log filter is specified with -x in the command lgk on RCS nodes (TCU/MSRBSv2), to specify the type of logs that will be displayed. The ESI log filter shall be given as a combination of one or more of the following strings, separated by commas:
![Page 92 of the Ericsson MoShell user manual — - 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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-92.webp?w=400)
USER GUIDE 92(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:
– CPP downtime is the time elapsed between the row CRIT Node down and the row Node operational. in syslog or the row NODE IN Operational in avlog (whichever row comes first).
– Application downtime is the time elapsed between the row CRIT Node down in syslog and the row RNC Node Restart Completed (RNC) , Cell .* enabled (WRBS) , VMGWs Unlocked/First VMGw Enabled (MGW), or NODE IN Operational RestartCompleted (ERBS) in avlog.
– Jvm downtime is the time elapsed between the row CRIT Node down in syslog and the row JVM Load Module is now operational in avlog or the row The Configuration Service is up and running in upgradelog.
Program CXCxxxx started in syslog (or the row Current properties in upgradelog) and the row The Configuration Service is up and running in upgradelog. Though the Jvm downtime is shown in the CPP downtime column, it is nevertheless only a Jvm downtime.
– The node downtime figures in the summary table at the end of the printout represent the highest value between
CPP downtime and Application downtime. The partial downtime figures are weighted against percentage of availability (when applicable).
– The start of the downtime is counted from the line NODE OUT ShutdownCommand or NODE OUT UnOperational (whichever comes first)
– The RCS downtime is counted until the line NODE IN Operational or NODE IN Operational ExtUpgradeRequest
– The Application downtime is counted until the line RestartCompleted

USER GUIDE 93(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.3.1 uv [<string>|<var>=value]
Display or change moshell configuration settings (also called "user variables").
The uv command used without any argument displays the values of all user variables that are usually specified in the moshell file and/or the ~/.moshellrc. See Section 2.5 and moshell file for more info about the functionality of these variables.
If a string is given as argument, then only the variables matching the string will be displayed.
The uv command also allows to change a variable’s value from within the moshell session.
For instance, if the variable secure_shell is set to 0 in the ~/.moshellrc, it will be possible to run an moshell session in secure shell mode by just typing uv secure_shell=1 at the moshell prompt. From that point on, all node connections that would have been performed using telnet will be performed using ssh.
Example:
Similar to the get command, it is possible to store the output of this command into a variable
Example:
uv ^credential > $credential
![Page 94 of the Ericsson MoShell user manual — pv [<string>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-94.webp?w=400)
USER GUIDE 94(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.3.2 pv [<string>]
To print all scripting variables or just those matching the .
For example:
The number of variables printed is saved to the variable $nr_of_vars Please refer to the "scripting" chapter for how to set a variable.
4.3.3 !/l <unix-command>
Execute a unix command on the PC/workstation
Either the ! or l can be used.
4.3.4 l+[m][m][s][o]/l-/l? [<logfile>]
Open/close moshell logfiles.
l+ is to open a logfile. If no logfile is given, then a default unique logfile is chosen.
The path of the default logfile is:
~/moshell_logfiles/logs_moshell/sessionlog/<DATE>_<NODE>.log
The m option is for mute, i.e.: no output will be displayed on the screen until the log is closed. All output will go to the logfile.
(the mm option is for extra mute, even less will be displayed on screen than with l+m).
The s option is for not printing the header "log open/log close". Can also be set with the loginfo_print user variable.
The o option is for overwriting the logfile, otherwise it is appended.
l- is for closing the logfile.
l? is for checking if a logfile is currently open.
It is possible to open several logfiles but only one at a time will be active. When one logfile is closed, logging will resume in the previous one. Examples:
l+ logfile1 #starts logging to logfile1, $logfile set to "logfile1" get pr l+ logfile2 #stops logging to logfile1 and starts logging to logfile2 #$logfile is set to "logfile2" vii l- #stops logging to logfile2 and resumes logging to logfile1 #$logfile set to "logfile1" vols l- #stops logging to logfile1, $logfile stays set to "logfile1"
In this example, logfile1 will contain the printouts from get, pr and vols, while logfile2 will contain the printout from vii.
![Page 95 of the Ericsson MoShell user manual — dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-95.webp?w=400)
USER GUIDE 95(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.3.5 dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>]
When there are inconsistencies in the SQL database, it can lead to problems such as traffic performance degradation, upgrade failures, or cyclic restarts. Often the symptoms appear only after the next node restart or upgrade so it is not easy to know since how long the data has been corrupted and how far back we should rollback to find a non-corrupted CV. Therefore it is a useful preventative measure to regularly perform a database consistency check.
Please refer to RAN PLM info 662, 664, 808, 914, 941, for more details on the different types of corruptions and possible remedies.
When the command is run on its own without option nor argument, it will make a CV (cvmk), fetch the db.dat file (ftget), remove the cv (cvrm), then analyse the db.dat on the workstation and look for corruptions.
The argument (optional) can either be:
Running a consistency check on the whole network
mobatch [-r] -d /path/to/folder dbc
In this case mobatch will run the moshell sessions in sql mode against the files instead of against the nodes. The first argument must specify the path to the folder containing the db.dat, cv.zip, or dbdump.zip files. The -r option is for recursive search in the folder, otherwise only the files directly under the folder are examined.
The configuration data of the node is kept in a SQL database in RAM memory on the central MP and can be backed up on disk (/d/configuration/cv) for permanent storage. The main purpose of the database is to store the persistent data of the MOs. An MO is made of up to three layers:
An MO always consists of one MAO. There is a one to one relation between the MO and its MAO. Underneath the MAO there can be one or more FROs, or in some cases no FRO. Examples: The SwAllocation MO consists only of a MAO without FRO/RO. The Mtp3bSpItu MO consists of one MAO and one FRO/RO. The Aal2PathVccTp MO consists of one MAO and two FROs/ROs. The FROs are used for controlling the actual resources, the ROs.
![Page 96 of the Ericsson MoShell user manual — dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-96.webp?w=400)
USER GUIDE 96(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 MAOs and FROs use separate SQL tables for data storage. The ROs do not store any persistent data as this is handled by FRO. The MAOs keep their persistent data in the SQL table modata_r2 or modata_r3. For the FROs, there is a separate table for each MO class. For instance the FROs of PlugInUnit MOs use the table cspiuresource, the FROs of Program MOs use the table cspgmresource, etc.
Printout example and comments
Important to keep in mind: the same fault can have appear in several of the checks below. For instance, an MO which has not been correctly deleted from the node could result in corruption shown in checks 8, 12, 13. A UtranRelation with incorrect frequencyRelationType will result in corruption shown in checks 17 and 18. Usually when the same fault appears in several checks, the fault that is higher up in the list is the one that should be fixed first.
****************** Comment ****************** The MOs above contain a "+" and space sign in their MO id. These characters are not known to have a system impact on the node but it is not recommended to use them as they may not be handled properly by the O&M client (moshell/AMOS/OSSRC). Having MOs in this list will give the result "OK with warnings". MOs can be renamed by using the "rset" command.
****************** Comment ****************** The MO above contains strictly forbidden characters in the MO id: "," and "=". Using these characters can cause cyclic node restarts, see TR HL11572/UABtr75948.
****************** Comment ****************** Here we have some MOs where the MAO is pointing to a non-existing FRO. Start moshell in sql mode towards the db.dat file (moshell -d /path/to/db.dat) and run the "get" command on these MOs. For instance, the "get" command will show that the IubLink MO has froId value 33 but when looking in the corresponding FRO table roamfroiublinkdbtable_09 with "sql select" command, we will see that there is no entry with this id.
****************** Comment ****************** Here we have the reverse situation than above. There is no entry in the MAO table which has a froId pointing to this FRO. We can run the command "fro externalgsmcell" to print the froId value of all MAO instances and we will see that none has the froId 198.
****************** Comment ****************** This indicates that there are several entries in the table modata_r2 which refer to the same MAO. Sometimes this can be a problem, especially if the MAO is connected to a FRO. In this case, Licensing MO is made only of a MAO layer so no FRO are affected. This particular problem is known in CPP5/CPP6 and fixed in CPP7. It has no system impact.
****************** Comment ****************** Here we have two different MAOs that point to the same FRO, this is not allowed since a FRO can only be connected to one MAO. We could check this by starting moshell in sql mode and running the "get" or "fro" command on these MOs to print the froid.
![Page 97 of the Ericsson MoShell user manual — dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-97.webp?w=400)
USER GUIDE 97(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
****************** Comment ****************** This check is a summary of issues found in points 3,4,5,6. We count the number of MAO and FRO instances for each MO class and show those where there is a mismatch. The faulty MO instances can be found in one of the previous four checks.
****************** Comment ****************** This indicates that some MOs have a reference to an MO that does not exist on the node. This can happen when a MO is deleted from the node, sometimes the system fails to remove it from reference attributes pointing to it. In example above, the reservedBy attribute of some MOs did not get updated properly when the MO IubLink=80 was deleted from the node.
****************** Comment ****************** The MAO knows its parent from the LDN. In some cases, the parent address is also stored in FRO by an attribute giving the froid of the parent MO in the MO tree. This check shows if the parent reference stored in MAO is different to the parent reference stored in FRO. In the first example, the discrepancy is due to the fact that two MAOs have the same froid (problem highlighted in check 6), this issue has a repercussion here since the children of this MO do not know which of the two MOs with froid 30 are the parent. In the second example, we see the froid of the parent points to a FRO that either does not exist or is not connected to any MAO. In the third example, we see that the froid of the parent points to a different MO than the one given in the LDN by MAO. Note: the number in brackets next to the LDN is the froId of that MAO.
****************** Comment ****************** MO references are sometimes kept in MAO or FRO only, but sometimes they are kept in both parts. It is important that an MO reference kept both in MAO and FRO should be the same in both. In the first example, the MO has a reference stored in MAO which is different to the one stored in FRO. In the second example, the reference stored in FRO points to two different MAOs, this is due to the problem highlighted in check 6 with duplicated froid. In the third example, the FRO reference points to a FRO that either does not exist or does not have a MAO. In the fourth example, the list of MO references is different in the MAO attribute ipAccessHostRef compared to the FRO attribute ipaccesshostfroid Note: the number in brackets next to the LDN is the froId of that MAO.
****************** Comment ****************** This check indicates that the MO on the left has a reference to the MO on the right (via the attribute stated in the middle) but does not appear in the reservedBy list of the MO on the right. To check this we start moshell in sql mode (moshell -d dbdat/cvzip) and perform the get command on the MO on the right and we see that the MO on the left cannot be found in the reservedBy list eventhough it has a reference to that MO. This is a one-way relation between the MOs and is a fault.
****************** Comment ****************** This is the opposite problem than the previous check. It indicates that the MO on the right (in this case the IubLink) appears in
![Page 98 of the Ericsson MoShell user manual — dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-98.webp?w=400)
USER GUIDE 98(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 reservedBy list of the MO on the left, even though it has no reference to that MO. To check this we start moshell in sql mode (moshell -d dbdat/cvzip) and perform the get command on the MO on the right. We will see no attribute containing any reference to the MO on the left. When we do the get command on the MO on the left we see that the MO on the right appears in the reservedBy list anyway. This is a one-way relation between the MOs and is a fault.
****************** Comment ****************** This check applies to MAO attributes of type sequence:moRef. It indicates if there is a discrepancy between the announced number of MO references in the attribute (shown at the beginning of the attribute value, in square brackets, eg: [5]), and the actual number of MOs listed in the attribute. In the example above, the attribute is supposed to be a sequence of 5 MOs but in fact it contains 7 MOs. To check, start moshell in sql mode and perform the "get" command on the MO.
****************** Comment ****************** This check shows the FROs that have a reference to a FRO that does not exist on the node. Only MOs which have not already been displayed in check number 10 will be displayed here. To find out the faulty FRO table and row, start moshell in sql mode and perform the "get" command on the MO.
****************** Comment ****************** This check shows the FRO tables which exist in multiple versions: the latest table version is shown on the left-hand side, and the list of old table versions is shown on the right-hand side. The old table versions should normally be removed at system upgrade.
****************** Comment ****************** This check looks at the syntax of the attribute data of the MAOs listed in the modata_r2/modata_r3 table. Any corrupted attribute data will be shown as an exception in the get printout for that MO. The correct syntax of each entry should be: MoType^Revision^LDN^PrimaryKey^attributeName^attributeData^ And the syntax of the attribute data should be: dataType AVCflag Data . With:
i=Integer, l=Long, b=Boolean AVCflag: T=isAVCNotifier , F=notAVCNotifier Sequence: dataType AVCflag noOfElements|attributeName|attributeData| Struct: dataType AVCflag noOfElements attributeName attibuteData
****************** Comment ****************** This check reports the list of MAOs whose parent does not have an entry in the modata_r2/modata_r3 table.
****************** Comment ****************** This check reports the list of MAOs that have a invalid FRO id, e.g. empty value instead of integer.
![Page 99 of the Ericsson MoShell user manual — dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-99.webp?w=400)
USER GUIDE 99(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
UtranCell=BU279M,UtranRelation=BU279N UtranCell=BU279K,UtranRelation=BU279N UtranCell=BU279L,UtranRelation=BU279N UtranCell=BU279L,UtranRelation=BU530L UtranCell=BU279M2,UtranRelation=BU279N UtranCell=BU279L2,UtranRelation=BU279N UtranCell=BU279L2,UtranRelation=BU530L2
****************** Comment ****************** This check reports the list of Instance-based PM scanners that contain MO instances which don’t exist anymore in the node. Any such scanners should be deleted and replaced with Class-based scanners or Instance-based scanners containing existing MO instances. The scanners can be printed in dbdat mode with pst/pgets. Refer to TR HR95951 or PLM info 914 for more info.
****************** Comment ****************** This check reports the list of instance-based PM scanners that contain more than 1000 MO instances. It is recommended to replace these scanners with Class-based scanners due to impact on the node JVM performance. The scanners can be printed in dbdat mode with pst/pgets. Refer to TR HR95951 or PLM info 914 for more info.
****************** Comment ****************** This check reports if the Jvm admClassPath contains any LMs that are not listed in the current UpgradePackage (attribute: ConfigurationVersion::currentUpgradePackage::loadModuleList)
****************** Comment ****************** This check reports if there are MAO instances where the corresponding FRO table is missing. The output shows the name of the missing FRO table and the corresponding MO class. This is a complement to check 3 which detects MAO instances where the FRO entry is missing from the FRO table but does not detect cases where the whole FRO table is missing.
101) FRO attributes containing the froId field but not the ldn field (HR88263): YES 1867 EUtraNetwork=1,ExternalENodeBFunction=5051-530675,ExternalEUtranCellFDD=5051-530675-2 parentref,eutranfrequenc 1868 EUtranCellFDD=SHBDEM2,EUtranFreqRelation=1275,EUtranCellRelation=5051-530675-2 parentref,neighborcellref
****************** Comment ****************** This check is specific for RBS/ERBS only and does not appear in other node types (RNC/MGW). This check shows if there are any attributes containing the text "
101) MTP3 pointCode collision (WRNae82362, SCS695737): YES Point code 13749348 used by Mtp3bSpAnsi=1 and Mtp3bSpAnsi=1,Mtp3bSrs=r821s
****************** Comment ****************** This check is specific for RNC/MGW nodes only and does not appear in other node types (RXI/RBS). This check shows if there are any MTP3 routes that use the same destinationPointCode as the node’s own point code. To check this, start moshell in sql mode and run the "get" command on both MOs listed to crosscheck that the pointcode is the same. The fault is described in TR WRNae82362.
102) Number of Fans mismatch (CSR 2101402/HQ64197): YES 23 Equipment=1,Subrack=MS nrOfFans: 4 nr_denib: 2
****************** Comment ****************** This check is specific for RNC/MGW nodes only and does not appear in other node types (RXI/RBS). In addition, it only applies to the nodes that use Subracks with fanConfiguration BFD528, eg. RNC3820, MGW GMPv4. The purpose is to check if the number of Fan MOs defined under each Subrack is the same as the number of fans specified in the attribute numberOfDenibDevices (if >0) or in the attribute Subrack::subrackProdType::fanConfiguration (if numberOfDenibDevices
103) Inconsistency in UtranRelation nodeRelationType or frequencyRelationType (HP94489/WRNae68940/WRNae72810): YES
· ·
![Page 100 of the Ericsson MoShell user manual — dbc[s][a] [<cvname>|<dbdat-file>|<cvzip-file>|<mobatch-folder>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-100.webp?w=400)
USER GUIDE 100(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
5596 UtranCell=Iub-10-1,UtranRelation=Softer-Iub-10-3 nodeRelationType: 1, actual: 0 (cellRef:UtranCell=Iub-10-3) 22205 UtranCell=U31618,UtranRelation=U31477 frequencyRelationType: 1, actual: 0 (f1=f2=1007) 37068 UtranCell=85276B,UtranRelation=1 frequencyRelationType: 0, actual: 1 (f1=10737, f2=10713)
****************** Comment ****************** This check is specific for RNC only and does not appear in other node types. It is only for MO instances of type "UtranRelation" and cross-checks the value of the attributes nodeRelationType and frequencyRelationType against the real setting. The first UtranRelation in the example has nodeRelationType set to 1 (Inter-RNC, meaning it is supposed to be a relation to an ExternalUtranCell) but the cellReference to which it is pointing to is an internal UtranCell, so it should actually have the nodeRelationType 0 instead of 1. The second UtranRelation MOs in the example has a discrepancy in the frequencyRelationType which is set to 1 (Inter-frequency) whereas the originating Cell and destination Cell have the same frequency, so it should actually be 0 (Intra-frequency). The third UtranRelation is the opposite scenario where the frequency of the originating Cell and destination Cell are different but the frequencyRelationType is set to 0 (Intra-frequency).
104) Inconsistency in UtranCell interFreqRelCntr or intraFreqRelCntr (HP94489/WRNae68940/WRNae72810): YES 364 UtranCell=85162B intraFreqRelCntr: 27, actual: 28 (by frequencyRelationType and uarfcnDl) 364 UtranCell=85162B interFreqRelCntr: 1, actual: 0 (by frequencyRelationType and uarfcnDl) 680 UtranCell=85276B intraFreqRelCntr: 25, actual: 24 (by uarfcnDl) 680 UtranCell=85276B interFreqRelCntr: 0, actual: 1 (by uarfcnDl)
****************** Comment ****************** This check is specific for RNC only and does not appear in other node types. It is only for MO instances of type "UtranCell" and cross-checks the value of the attributes intraFreqRelCntr and interFreqRelCntr against the real setting. The real setting is checked by checking the frequencyRelationType of the UtranRelations defined underneath the UtranCell. Both the frequencyRelationType attribute and the real frequencyRelationType (found out by looking at the uarfcn of originating and destination cell) are checked. To check this manually, start moshell in sql mode (moshell -d cvzip/dbdat) and run the command "lget utrancell=xxx cntr|freq.*type". It will show the value of the cell’s freqRelCntr and frequencyRelationType of underlying relations. If they mismatch, the cell is shown as mismatching "by frequencyRelationType and uarfcnDl". If they match but some of the frequencyRelationType settings are incorrect (see previous check 17) then the mismatch will by shown "by uarfcnDl". In the first two lines we can see that the UtranCell 85162B has 27 intra-frequency relations and 1 inter-frequency relations. When we check the frequencyRelationType attribute and the uarfcn of the originating and destination cells, both indicate that this is not correct. It appears that there is actually 28 intra-frequency relations and 0 inter-frequency relations. In the next two lines we can see that the UtranCell 85276B has 26 intra-frequency relations and 0 inter-frequency relations, but in reality there are 24 intra-frequency and 1 inter-frequency. In this case the frequencyRelationType setting of the UtranRelation is misleading and has been flagged in check 15.
105) Inconsistency in RncFunction cellRelCntr (HT37388): YES RncFunction=1 cellRelCntr=21743, nrOfRelations=21410 (1304 CoverageRelation, 6 EutranFreqRelation, 12 GsmRelation, 2
****************** Comment ****************** This check is specific for RNC only and does not appear in other node types. It checks that the value of the attribute cellRelCntr in the RncFunction MO should be equal to the total number of MO instances of type CoverageRelation+EutranFreqRelation+GsmRelation+UtranRelation. It can be checked manually with the command: prs relation= Note: from W15B onward, this inconsistency can be fixed by running the command facc rncfunction=1 recalculateInternalCounters
106) Inconsistency in UtranCell gsmRelHoAndCellReselCntr: YES 5289 UtranCell=U32194C gsmRelHoAndCellReselCntr: 21, actual: 22 17389 UtranCell=G32105C gsmRelHoAndCellReselCntr: 25, actual: 22
****************** Comment ****************** This check is specific for RNC only and does not appear in other node types. It checks that the value of the attribute gsmRelHoAndCellReselCntr in each UtranCell MO should be equal to the actual number of children GsmRelation MOs with mobilityRelationType=0. It can be checked manually with the command: get utrancell=xxx,gsmrelation mobilityRelationType ^0 Note: from W15B onward, this inconsistency can be fixed by running the command facc utrancell=xxx recalculateInternalCounters
107) Inconsistency in UtranCell cellReselectionCntr: YES 2749 UtranCell=32S1C1 cellReselectionCntr: 1, actual: 6 2753 UtranCell=32S1C2 cellReselectionCntr: 12, actual: 9
****************** Comment ****************** This check is specific for RNC only (>= W15B) and does not appear in other node types or older SW releases. It checks that the value of the attribute cellReselectionCntr in each UtranCell MO should be equal to the actual number of children UtranRelation
![Page 101 of the Ericsson MoShell user manual — dbd[p] [<cvname>|<dbdat-file>|<cvzip-file>] [<cvname>|<dbdat-file>|<cvzip-file>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-101.webp?w=400)
USER GUIDE 101(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
MOs with frequencyRelationType=1 and mobilityRelationType=0 or 2. It can be checked manually with the command: hget utrancell=xxx,utranrelation frequencyRelationType|mobilityRelationType 1 ^[02] Note: from W15B onward, this inconsistency can be fixed by running the command facc utrancell=xxx recalculateInternalCounters
108) Inconsistency in UtranCell handoverOnlyCntr: YES 2749 UtranCell=32S1C1 handoverOnlyCntr: 12, actual: 9 2753 UtranCell=32S1C2 handoverOnlyCntr: -4, actual: 2
****************** Comment ****************** This check is specific for RNC only (>= W15B) and does not appear in other node types or older SW releases. It checks that the value of the attribute handoverOnlyCntr in each UtranCell MO should be equal to the actual number of children UtranRelation MOs with frequencyRelationType=1 and mobilityRelationType=0 or 1. It can be checked manually with the command: hget utrancell=xxx,utranrelation frequencyRelationType|mobilityRelationType 1 ^[01] Note: from W15B onward, this inconsistency can be fixed by running the command facc utrancell=xxx recalculateInternalCounters
4.3.6 dbd[p] [<cvname>|<dbdat-file>|<cvzip-file>] [<cvname>|<dbdat-file>|<cvzip-file>]
Arguments:
or:
Uservariables:
4.3.7 dbcv[r]
Perform a DB consistency check (dbc) on the db.dat files of the CVs stored on the node.
The result of the dbcv execution is stored on the node at /c/public_html/dbcv.txt and is read by the cvls and al commands, if the uservariable use_dbcv is set to 1. The dbcv command only checks CVs with unknown DBC status, unless option r is given (dbcvr) in which case all CVs are checked again.
When use_dbcv=1 (and mosalarm=1), a Moshell generated alarm with severity Warning will appear in the al printout indicating the number of CVs where DBC status is NOK.
When use_dbcv=1, the cvls printout will contain an additional column DBC, showing the DB consistency status of each CV.
Example:
================================================================================================= Id CV Name Creation Date UpgradePackage Release Type Operator DBC Comment =================================================================================================
1 RNC11_W12.0 2013-07-24 12:23 CXP9014711/4_R4LB W12.0.2.10 other eanzmagn NOK none 2 RNC11_W14.0_OK 2014-02-16 11:23 CXP9021776/1_R3AA03 W14.0.1.0 other eanzmagn OK none 3 RNC11_W14.1.2.2 2014-12-22 06:58 CXP9021776/2_R4CA06 W14.1.2.2 other eanzmagn OK none =================================================================================================
![Page 102 of the Ericsson MoShell user manual — <ose/coli command> [|<unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-102.webp?w=400)
USER GUIDE 102(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 DBC column can show four different results:
4.3.8 <ose/coli command> [|<unix-cmds>]
Send a COLI command to the CPP node’s OSE shell. Type "h ose" for syntax help and "?" to view available commands.
The command are sent to the node using either telnet or ssh, depending on the value of the moshell setting secure_shell (See Section 2.6)
The password is not required if it is defined in the ipdatabase or the $password variable (otherwise, the user will be prompted to enter the password).
To find out all available COLI commands, type ? or lhsh ?
It’s possible to pipe the command to any external utility the machine which moshell is running on (such as grep). Example:
Several commands can be run on the same line by separating each command with a semicolon. If more than 5 commands are specified on the line, then these will be sent via a command file on the node (quicker). The user variable fast_coli_threshold controls the number of commands above which a command file will be transferred to the node. By default it is 5 but it is possible to reduce or increase this setting with the uv command (see chap 2.5 for more info on uservariables). For instance by setting fast_coli_threshold to 0, COLI commands will always run via command file, this can help to avoid printout corruptions (certain commands producing large printouts can sometimes get corrupted by spurious echo characters when run directly without command file).
Note that it is safer to do lhsh instead of lhsh ; command in case the board is not reachable. Example: if you want to format /d on board 001400: if you do lhsh 001400 ; formathd /d and the board 001400 is not reachable then the command is sent to the Hub MP whereas with the command lhsh 001400 formathd /d, if the board 001400 is not reachable then the command is not sent at all. But for certain commands like "te filter set", "te log freeze", "EtHostMo_startPing" or "MsbHostMo_StartPing", the semicolon has to be entered after the "lhsh" in order to force moshell to actually log into the board.
Running SQL commands
![Page 103 of the Ericsson MoShell user manual — <ose/coli command> [|<unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-103.webp?w=400)
USER GUIDE 103(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
Adding/Removing a static route:
Other examples:
Running CMXB commands on HCS node (RNC3820/MGW GMPv4).
Running CMXB/SCXB commands on EvoC (RNC8200).
Running telnet commands in MSB4 (MGW)
Running 3GSIM/CORBEN/LOCO commands · Running NCLI commands

USER GUIDE 104(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 telnet username (and password if applicable) must be entered after the telnet command, separated by semicolons and the exit command must be given at the end.
Running commands towards an AXE node (prerequisite: uservariable "lincli" must be set to 3).
Limitations: it is not possible to release the terminal in order to view "ordered" printouts.
4.3.9 coli
Open an interactive COLI or RCS-COLI session to the node.
4.3.10 comcli
Open an interactive COMCLI/ECLI session to the node. Only applicable for COM nodes.
4.3.11 ecli
Open an interactive ECLI session to the node. Only applicable for COM nodes.
4.3.12 esci
Start Ericsson Support Command Interface mode. Only applicable for EMCLI (RCS nodes).
4.3.13 netconf[g] [<commandfile>]
Open an interactive NETCONF session to the node or execute a NETCONF command file. Only applicable for COM nodes.
Witout option, the output is processed showing each command and reply on a individual line. More suitable for netconf "write" operations.
4.3.14 c+/c1/c2/c-/c?/c0
Switch between the COM node’s linux shell, rcs-coli shell or comcli shell.
To switch between the linux/rcs-coli shell and the comcli shell, use the command c+/c1/c2 :
If the node does not have a rcs-coli shell then the commands c1 and c2 will be equivalent, and it is also possible to use the command c-.
Changing shell password
![Page 105 of the Ericsson MoShell user manual — <linux/rcs-coli/comcli command> [|<unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-105.webp?w=400)
USER GUIDE 105(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 c? command is for checking what is the current shell.
By default, moshell will automatically send comcli/coli/linux commands to the appropriate shell. This feature can be deactivated by setting the uservariable smart_shell to 0 (1 is default). It is also possible to force a command to be sent to a specific shell by typing c+, c1, or c2. To return to automatic shell detection, it is possible to use the command c0.
4.3.15 <linux/rcs-coli/comcli command> [|<unix-cmds>]
Send CLI commands to the COM node’s linux shell, rcs-coli shell or comcli shell.
The commands are sent to the node over ssh. The password is not required if it is defined in the ipdatabase or the $password variable (otherwise, the user will be prompted to enter the password).
To print the list of linux commands, type "ls" on the list of directories shown in the $PATH environment variable (echo $PATH). To print the list of rcs-coli commands, type "help". To print the list comcli commands, type "?" in comcli mode.
To switch between the linux/rcs-coli shell and the comcli shell, use the command c+/c1/c2 :
If the node does not have a rcs-coli shell then the commands c1 and c2 will be equivalent, and it is also possible to use the command c-.
To switch between linux shell and rcs-coli shell, the uservariable linux_shell can be used:
Within the comcli shell, there are two modes: exec mode and config mode. Exec mode is the default. To switch to config mode type "configure". The comcli allows to perform MO commands (get, set, create, delete, action, etc). More information about the comcli shell can be found in the document 1/1553-FAE 151 01 ("CLI Style"). All MO commands can also be performed using moshell’s own MO commands.
It is possible to pipe a shell command to any external unix utility, eg "grep", "sort", etc. The pipe sign must be surrounded by a blank space on each side. It is also possible to use the built-in COMCLI command "filter", in that case no spaces shall be around the pipe sign. See examples below.
Each command line is sent in a separate ssh session, so in order to send several commands within the same ssh session, they need to be run on the same line by separating each command with a semicolon.
Refer to the moshell file for more information about the uservariables for COM nodes:
![Page 106 of the Ericsson MoShell user manual — mcl[d] [<moClass-filter>] [<command-filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-106.webp?w=400)
USER GUIDE 106(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.3.16 mcl[d] [<moClass-filter>] [<command-filter>]
List the available MO-Context COMCLI commands.
4.3.17 mcc/lmcc <moGroup>|<moFilter>|<proxy(s)> <comcli commands(s)> [|<unix-cmds>]
Execute MO-Context COMCLI commands.
Execute a COMCLI command from within a specific MO.
List all COMCLI commands applicable to all Router MOs and their children (the command ? or can be used to list COMCLI commands)
Print more help on the ping command in the MO InterfaceIPv4=TNA
Run the ping command from all AddressIPv4 MOs and pipe the output through grep
4.3.18 bo[ar]/ba[swdpmu]/br[wdm]/be[0-50]/bp
Manage board groups that can be used for running COLI commands on multiple boards.
Syntax:
The following board groups are always created by default after running any of the board commands (bo/ba/br/lh, etc) the first time:
![Page 107 of the Ericsson MoShell user manual — mcl[d] [<moClass-filter>] [<command-filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-107.webp?w=400)
USER GUIDE 107(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
In RNC, the following board groups are also created by default, containing MPs/SPMs connected to the various RNC modules:
In RBS, the following board groups are created by default: rax, tx, ru, asc.
In MGW the following board groups are created by default: mesc, licdb, ch, stc, gra, imra, raa, msb.
It is recommended to start by running the bo command (board overview) to view the available boards in the node.
The very first time bo is run on a node, it will take more time because it has to fetch data from the node. The following times, the existing data is shown again unless the r swith is used (command bor), in which case the data is fetched again from the node.
By default the bo command only shows slots that contain boards defined in the configuration (i.e. boards which are associated with a PlugInUnit MO) but by using option a it is possible to view all slots, even those which do not contain a PlugInUnit.
The ba command is used for adding boards into a group. The boards shall be identified by their position or a string matching the board type. The s switch adds any related SPMs to the board group.
The baw command is similar to the ba command except that the boards are identified by their SwAllocation and/or RncModule. Examples:
The bad command is for adding SPMs into a board group based on their device type. This is applicable to RNC only. Examples:
The bap command is for adding boards into a board group based on what program(s) they are running. The string is matched against the name of the Program MOs. All PlugInUnit MOs which contain a Program MO whose name matches the string are added to the group. Examples:
![Page 108 of the Ericsson MoShell user manual — mcl[d] [<moClass-filter>] [<command-filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-108.webp?w=400)
USER GUIDE 108(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 bau command is for adding boards into a board group based on what RPU(s) they are running. The string is matched against the reliableProgramLabel of the RPU MOs. All PlugInUnit MOs that have a RPU MO whose reliableProgramLabel matches the string are added to the group. Examples:
The bam/brm command is for adding/removing boards corresponding the PlugInUnit/Spm/PiuDevice MOs of an existing MO group. When specifying the "s" option ("bams") the children Spm/PiuDevice of the PlugInUnit will be included in the board group. Examples:
The br command is for removing a whole group or certain boards out of a group.
Negative filter (!) is supported in order to remove all boards except those matching the filter.
The brw command is similar to the br command except that the boards are identified by their SwAllocation and/or RncModule. Examples:
The bp command is for printing existing groups or the contents of a particular group. Examples:
The be command is for extracting a number of boards from a group. To be used in conjunction with "mon" to handle board groups that contain more than 50 boards (the current limit on target monitor). Examples:
Once the group is created, the lh command is used to run an OSE command on all boards of the group. See help of the "lh" command in next chapter for more info.
It is also possible to run MO commands on board groups. In this case, the MO command will execute against the MOs connected to these boards, ie the PlugInUnit or Spm MOs.
So, in order to lock/unlock some devices, use the MO group instead of the board group since the board group connects to the SPMs which don’t have an administrative state.
For example, bl cc1dev.
More info in h syntax.
![Page 109 of the Ericsson MoShell user manual — lh[z] <boardGroup>|<moGroup> <OSE-command>|run <commandfile> [ | <unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-109.webp?w=400)
USER GUIDE 109(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.3.19 lh[z] <boardGroup>|<moGroup> <OSE-command>|run <commandfile> [ | <unix-cmds>]
Run COLI commands on all boards of a board group or MO group.
The first argument of the "lh" command is the board group or MO group.
The second argument is the COLI command or list of COLI commands. If several COLI commands will be run on the boards they can either be separated by semicolons or run from a commandfile stored on the workstation.
Option:
It is possible to send multiple commands to each board of the board group by separating them with semicolons. Examples:
It is also possible to send a command file to each board of the group. Example:
When many commands are to be sent, the lh function will put them into a command file, transfer that file to the node (using (s)ftp) and run that file from within the node, using the shell -f command. This will save a lot of time instead of having to send each command one by one to the node.
There is a user variable called fast_lh_threshold which decides the number of commands above which a command file will be transferred to the node. See Section 2.5 and moshell file for more info about user variables.
4.3.20 mon[?][d][u][f][s][t][k][a][-] [<board(s)|<boardGroup(s)>] [</path/to/logfile>]
Start/stop/check CPP target monitor or Linux monitor session in TCP mode, UDP mode, or disk mode.
The mon command issues a set of COLI commands (tm, or ts) in order to open TCP or UDP ports from the boards on the node to the client. The boards address and/or board groups are given as argument to specify which boards the client will connect to.
Arguments:
TCP Monitor for Linux nodes (EvoC8300, MSRBSv2, TCU):
T&E Trace Streaming for Linux nodes is performed by using lttng-relayd (as server) and babeltrace/babelwrap (as client). The TCP ports 5342 (control) and 5343 (data) are used by default for transfer of traces from the node to the lttng server on the workstation. If those ports are occupied, then other consecutive ports will be automatically selected in the range up until 6342. The moshell uservariables lttng_port and lttng_range can be modified in order to change the starting TCP port and port range used for lttng trace streaming. The traces are flushed every 1 second for EvoC8300, and every 2 seconds for MSRBSv2/TCU. This can be changed via the uservariables lttng_flush_cpp / lttng_flush_rcs (value is in microseconds). The default buffer size is 4x4 MB for EvoC8300 and 4x1 MB for MSRBSv2/TCU. This can be changed via the uservariables lttng_buff_cpp or lttng_buff_rcs (value is in MB).
![Page 110 of the Ericsson MoShell user manual — lh[z] <boardGroup>|<moGroup> <OSE-command>|run <commandfile> [ | <unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-110.webp?w=400)
USER GUIDE 110(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 tracefiles stored on the lttng-relayd server are rotated according to the settings in lttng_tracefilesize_rcs/cpp and lttng_tracefilecount_rcs/cpp.
Applicable options:
UDP Monitor for MSRBSv2 (HiCap):
On MSRBSv2, the TCP monitor can only be used for trace streaming of MP traces. Baseband traces are monitored via the UDP HiCap monitor which uses router (as server) and viewer/capture/ltng-decoder (as client). By default:
Applicable options:
Options for CPP (OSE) nodes:
![Page 111 of the Ericsson MoShell user manual — sql+/sql-/sql? [<heap>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-111.webp?w=400)
USER GUIDE 111(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 command to start the monitor client is printed on the screen and also it is stored in the scripting variable $moncommand.
It is usually better to run the monitor client in a separate window than the moshell window but if this is not possible then it is also possible to run it from the moshell prompt, either in foreground or in background, eg:
The second method is especially useful when running moshell scripts. Then it is possible to put a wait statement while monitor is storing the traces in the logfile, then kill the monitor process using the command l kill -9 $background_pid, since the PID of the background process has been automatically stored in the variable $background_pid.
4.3.21 sql+/sql-/sql? [<heap>]
Start/stop/check the SQL client on the node (CXC1325608).
This command checks if the SQL client LM is already loaded or started. If not, it finds the latest version stored on disk, loads it and starts it. The argument can be used to specify a different heap size than the one that is pre-compiled in the LM. The heap size given will be in MB, should be an integer between 1 and 300. If no heap is given, the LM is loaded without specifying any heap value which means that it will use the default heap size that is specified in the LM.
4.3.22 pgu[c][f][r] [-p <board1,board2,...>] /path/to/newLM [<cvcomment>]
Program Upgrade. For lab use only, eg, to load black LMs.
Arguments
![Page 112 of the Ericsson MoShell user manual — procload/proctemp [|<unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-112.webp?w=400)
USER GUIDE 112(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 programs that are connected to an LM with the same product number will be identified and shown to the user. If the user confirms to go ahead, a loadmodule connected to the new LM will be created (if there isn’t already one on the node) and the programs using the old LM will be deleted and recreated towards the new LM. Then a cv is made and the user is prompted to restart the node so that the change will take effect.
This procedure is "cleaner" than hacking the sql tables since it uses the MO interface.
This command is implemented as an moshell script, the script can be seen in moshell/commonjars/scripts/pgu.mos. This shows that the user can define any new commands they need by adding an alias in the .moshellrc which will point to a script file. The parameters to the command will be sent to the script file via the positional parameters $1, $2, $3, etc. The variable $0 will be set to the whole line contents. See Section 4.1.34 for info.
4.3.23 procload/proctemp [|<unix-cmds>]
Print processor load or temperature.
The procload command is a wrapper for the COLI command capi (capi tot and capi core all) The proctemp command is a wrapper for the COLI command boardtemp all or temprt It can be run on individual boards or board groups.
The output of procload shows the total processor load of each processor in the board, followed by the processor load of the individual cores of each processor.
Switches
![Page 113 of the Ericsson MoShell user manual — proglist/progkill [-e] [<string>] [|<unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-113.webp?w=400)
USER GUIDE 113(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 output of proctemp shows the temperature displayed by each sensor of the board as well as the alarm limit for each sensor. The alarm limit for each sensor is displayed in brackets next to each sensor’s temperature. All temperature values are in Celcius.
4.3.24 proglist/progkill [-e] [<string>] [|<unix-cmds>]
List or restart programs on boards or board groups.
These two commands are wrappers for the COLI commands pglist/pm_pginfo and pgkill/pm_kill.
The proglist command lists the OSE programs running on MP, BP, or SP processor. The program handle, state, program number and name are shown. With option -e, the heap and pool size are also shown. It is also possible to add a filter after the -e option in order to show other program settings apart from the heap and pool. Eg: proglist -e stack shows all program settings matching the word stack. A list of all available program settings is shown at the end of the printout (when option -e is used).
The progkill command is used for restarting an individual program on a MP. If this command is used on a BP or SP then the whole processor restarts. A string which matches the program number or program name must be given as argument to the command. Eg: progkill java, or progkill 2844
4.3.25 fte <te-command> [<trace-groups>|all] [<string>] [|<unix-cmds>]
Filtered te (trace and error) command.
This command is a wrapper for the COLI commands te or bbte and works in two ways:
4.3.26 goxb[acib] [-p <advpw>] <commands> [|<unix-cmds>]
Run shell commands in XB boards (CMXB/SCXB/SMXB)
One or more XB commands can be run, each command to be separated by semicolons.
Syntax:
![Page 114 of the Ericsson MoShell user manual — ftree[f][d][1] [<lnh>/][<directory>] [| <unix-cmds>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-114.webp?w=400)
USER GUIDE 114(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
Dependencies:
4.3.27 ftree[f][d][1] [<lnh>/][<directory>] [| <unix-cmds>]
Recursive listing of a directory on the file system of the node or the workstation.
This command first checks if the directory exists on the workstation and if yes, its contents is printed from the workstation. Otherwise the command logs into the OSE shell of the node, checks if the directory exists on the node and prints its contents.
The directory can be entered either as a relative path or an absolute path. To list a directory on a different board, enter the linkhandler of the board followed by the absolute path. If no directory is entered then the current working directory will be listed.
The option d is for printing the subdirectories only.
The option f is for printing files only. Mainly useful on /c/pmd for increased speed and sorting by timestamp.
The option 1 is for non-recursive listing of a folder, same as ls -l.
It is possible to pipe the output to a unix command for filtering/sorting purposes.
![Page 115 of the Ericsson MoShell user manual — ftget[1][c]/ftput[1][c]/ftdel[1][a]/ftrun [<options>] <source>[/*] [<destination>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-115.webp?w=400)
USER GUIDE 115(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
It is possible to run ftree on several boards by using the lh command. Example:
ba bp 0-9999 # put all boards in a group called "bp" br bp gpb # remove all gpb boards from the "bp" group lh bp ftree /f # recursive listing of the /f drive on all bp boards
4.3.28 ftget[1][c]/ftput[1][c]/ftdel[1][a]/ftrun [<options>] <source>[/*] [<destination>]
Transfer files or directories to/from the node, using ftp or sftp.
Syntax:
Where "local" refers to the workstation and "remote" refers to the CPP node.
It is possible to transfer a whole directory to/from the node by specifying a source directory instead of a source file.
A subdirectory with the same name as the source directory will then be created under the destination folder, unless a asterisk is specified at the end of the source folder, eg:
To fetch the contents of a folder located on a local volume of the node, the path must be preceded by the board address following by exclamation mark.
The ftdel command removes an individual file or a set of files/directories inside a directory. With "a" option, also the directory itself will be removed.
The ftrun command allows to execute a command file containing a list of ftget/ftput/ftdel commands. This is quicker than executing the commands via "run" as all commands will be run within the same ftp/sftp session.
The options can be placed anywhere on the comand line but the source must be given before the destination.
If the destination is omitted then the current working directory is chosen.
Filtering option:
The -f option allows to specify a regular expression to only transfer the files matching that expression. See examples below.
Exclamation mark ! can be used as negative filter, meaning that any files that do NOT match the filter will be transferred, eg. ftget -f !tmp /c/usr
Time options:
The -s and -e options are used for specifying an absolute timespan: -s gives the starting date and -e gives the ending date. The format is yyyymmdd[.hhmm], for instance 20071230, or 20071230.0800.
The -m and -p options are used for specifying a timespan relative to today’s date: -m gives how long time backward and -p gives how long time forward. The format is in days, hours, or minutes, eg. 10d (10 days), 2h (2 hours), 30m (30 minutes).
ftget /d/usr/*
![Page 116 of the Ericsson MoShell user manual — htget <remotefile> [<localfile/localdir>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-116.webp?w=400)
USER GUIDE 116(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
/home/eric on the workstation
4.3.29 htget <remotefile> [<localfile/localdir>]
Download files using http or https.
This command allows to download a file to the workstation using http or https. Whether http or https will be used is decided from the uservariable secure_http (0=http, 1=https).
The remotefile can be specified with or without ipaddress.
If no ipaddress is specified then the file is fetched from the current node. If an ipaddress is specified the file can be fetched from a different server. It is also possible to specify the tcp port after the ip address eg :
The prefix http:// or https:// is optional.
4.3.30 edit <remotefile>
Edit a file on the node.
Moshell will download the file, spawn the text editor allowing to edit it and then upload it once the text editor is closed. If the file does not exist on the node it will be created.
The editor is specified in the editor user variable. By default, editor is set to the bash environment variable $EDITOR. If $EDITOR is not set, then vi will be used. To use another editor, add the following line in the ~/.moshellrc file: editor=/path/to/your/favorite/editor
![Page 117 of the Ericsson MoShell user manual — fclean[f|ff|a|d|e] [<lnh>/][<directory>] [-f <filename-filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-117.webp?w=400)
USER GUIDE 117(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.3.31 fclean[f|ff|a|d|e] [<lnh>/][<directory>] [-f <filename-filter>]
Removal of obsolete loadmodules OR recursive removal of a directory on the node.
This means any loadmodules that are present on the disk but are not defined in the current cv (ARMAMENT file and database) nor are listed in any of the existing upgrade packages on the node.
The directories which are "cleaned up" are:
It is possible to specify a list of loadmodules that are not to be cleaned up in the variable keepLmList in the moshell file. When the command has completed, a command file containing all remove commands is generated and the user is prompted with the choice to run it at once or at a later time.
![Page 118 of the Ericsson MoShell user manual — hi [<commandFilter>], !<commandNr>](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-118.webp?w=400)
USER GUIDE 118(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.3.32 hi [<commandFilter>], !<commandNr>
Print history of moshell commands entered during the current session.
By using the filter, it will only show those command matching that pattern. Example:
1 lt e1 2 st all dis 3 get 4 oper
To rerun e.g. command number 2, do:
4.3.33 time[t] <command>|<logfile>
Measure time taken by an moshell command or by each command in a moshell command file.
Arguments:
Example:
4.3.34 pipe <command> | <unix-command>
Execute a moshell command and pipe the output to a unix command.
This is useful for commands that don’t natively support direct piping, such as "mom", "h", "inv", etc It is not needed for commands that natively support direct piping, such as "lg", "pmx", "lh", etc
Example:
4.3.35 lmid[c][h]/upid[om] <pattern>|refresh
Print translation of loadmodule/upgradepackage product number or T&E error codes.
moshell> hi · !2

USER GUIDE 119(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
In addition, the LM name is printed beside the product number when using certain OSE shell commands:
For instance, when printing the contents of a directory such as /d/loadmodules or /c/loadmodules_norepl, the LM name will appear next to the product number. This functionality can be disabled by setting the user variable print_lmid to 0.
See Section 2.5 and Section 2.6 for more info about user variables.
If some names are missing from the printout, just run lmid refresh or bo and it will update the moshell LM reference file with all missing LM names. The refresh also happens automatically if no LM name is found for the pattern given.
The "c" option in lmid is to print the error codes list (aal2/mtp3/sccp/utrancell) which is used to decode error codes from the "te log read".
The "h" option in lmid is to print the HW translation table.
The "m" option in upid is to print the CXP to MOM version table.
The "o" option in upid is to print an overview, mapping of major SW releases only.
4.3.36 p/w/pw/b
Change moshell prompt and/or window title.
4.3.37 prox[+-]
Toggle display of proxy identities in printout of get command.
To print the proxy identities, type prox and the proxys will be printed for the remaining of the session. By typing prox one more time, the proxys will not be printed anymore.
The default behaviour is to not show the proxy identities (get_format=0) To change the default behaviour, it is possible to use the uservariable get_format, eg, adding the line get_format=1 in the file /.moshellrc.
4.3.38 col
Toggle display of colors.
By default, some lines will appear in different color in the te log read and cabrd printouts.
To disable the coloring, type col once; to reenable it, type col again.
This setting can be saved permanently in the uservariable show_colors.
4.3.39 ul
Toggle display of userLabel in st/lst and pget/lpget printouts.
![Page 120 of the Ericsson MoShell user manual — conf[bld][+-]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-120.webp?w=400)
USER GUIDE 120(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 userLabel is not shown.
Type ul to display this information for the remaining of the session. Type ul again to hide it.
This setting can be saved permanently in the uservariable show_userlabel.
4.3.40 conf[bld][+-]
Toggle confirmation on various MO commands.
By default, these commands require confirmation (y/n). Type one of these commands to disable confirmation. Type the command again and confirmation is re-enabled.
These settings can be saved permanently in the uservariables bldebset_confirmation, lt_confirmation, del_confirmation.
4.3.41 gs[+-]/gsg[+-]
Toggle display of old/new attribute value in setbldeb commands.
Purpose:
4.3.42 ip2d <ip-address>
Convert an IP address to a decimal number.
This can be used for instance when editing an entry in the ip fro table in the sql database, where ip addresses are stored in decimal format.
Example:
Similar to the get command, it is possible to store the output of this command into a variable. Example:
4.3.43 d2ip/h2ip <number>
Convert a decimal or hexadecimal number to an IP address.

USER GUIDE 121(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
This can be used for instance when decoding T&E traces or COLI printouts where ip addresses are written in decimal or hexadecimal format. Examples:
$ lhsh 001400 drh_trbr_data iphost ipHostFroId admState opState availStatus piuId smn apn ern atmPortId ipAddress linkHandlerName msgBoard 7 1 1 0 7 0 7 0 29 0xa641002 000700 hostReady applSciRunning
$ lhsh 000200 te log read [06:52:40.228] Ipet_app3dr_proc(IPET_APP3DR_SH_OBJ) app3dr_sh.c:5692 REC SIG:signo:190071 sender :100dc Rec: IPET_IPPSI_UDPSESSIONSETUP_IND. Ipet_remoteIpAddress = 174329861
Similar to the get command, it is possible to store the output of this command into a variable. Example:
4.3.44 h2d/d2h <number>
Convert an integer to hexadecimal or viceversa.
Example:
Similar to the get command, it is possible to store the output of this command into a variable. Example:
4.3.45 h2b/b2h <number>
Convert a binary to hexadecimal or viceversa.
Example:
Similar to the get command, it is possible to store the output of this command into a variable. Example:
4.3.46 d2b/b2d <number>
Convert a binary to decimal or viceversa.
Example:
Similar to the get command, it is possible to store the output of this command into a variable Example:
4.3.47 rb2ip [<iublink>]
Print the mapping of RNC IubLink MOs to RBS O&M IP addresses. Only supported in OSSRC.

USER GUIDE 122(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:
Similar to the get command, it is possible to store the output of this command into a variable Example:
4.3.48 encpw <password>
Create an encoded password for use in Moshell
Encoded passwords will be prefixed by "ENC?:". Make sure to keep this prefix when using the password
Encoded passwords can be used in moshellrc, ipdatabase files, scripts, on the command line and as input to MO creation
Example:
4.3.49 mos2ro <moshell.zip>
Generate an installation package for moshell read-only version.
Example:
The following operations are blocked in the read-only version: MO and Scanner create/delete/set/action. Also certain commands such as mon, fro, sql, pgu.
4.3.50 gpg <file>
Decrypt a gpg-encrypted ESI or PMD file, standalone or contained in a zip/tgz archive.
Example:
This command is for Ericsson personnel only. The gpg-encrypted file is decrypted on a remote CSDP server, accessible only from Ericsson Corporate Network with a Ericsson Corporate login. The Ericsson Corporate login for the CSDP server can be saved in the uservariables csdp_username and csdp_password.
4.3.51 wait <delay>|<newtime>
Wait for a specific duration in hrs, mins, secs, rops, or until specified time.
Default duration is in seconds. Use "m" for minutes, "h" for hours and "r" for ROPs. Default ROP duration is 15 minutes but can be changed with the uv rop_period (eg: to change rop duration to 5 minutes, type uv rop_period=5)
![Page 123 of the Ericsson MoShell user manual — wf[o][a][t] <file>](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-123.webp?w=400)
USER GUIDE 123(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 a ROP period is already started, it will wait until it finishes, then wait additionally the number of ROP periods specified.
To wait only until the current ROP is finished, use the command "wait 0r"
If the new time is before the current time (e.g. if current time is 9:30 and new time is 8:00), then the waiting will continue to the next day at that time.
To abort a wait statement, just type CTRL-C
4.3.52 wf[o][a][t] <file>
Write lines to a file.
Without options, the command will abort if the file already exists.
Example:
wf $tempdir/myfile.txt EUtranCellFDD administrativeState 0 EUtranCellTDD operationalState 1 EOF
4.3.53 return
To exit from a command file without exiting from MoShell (scripting).
Typically, the return command would be executed upon validation of a specific condition in the command file.
In order to use it in for loop, the break command has to be used in order to get out of the for loop, first.
In this example, we run a restart followed by running a trun script, 60 times.
If the trun script fails then we set the $return variable to 1 and break from the loop (note: the $command_result is a default variable which gets automatically set after running trun, see Section 6)
After the loop, there is a check to see if $return is 1, if yes, then "test failed" is printed, the commandfile is aborted and we are returned to the moshell prompt.
If $return was not set to 1, then it means we have completed all 60 iterations successfully and the final part of the script will be executed.
for 60 $return = 0 facc 0 manualrestart 0 0 0

USER GUIDE 124(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
trun $moshelldir/cmdfiles/rnc_commands.mos if $command_result = 1 $return = 1 break fi done if $return = 1 l echo "TEST FAILED" return fi l echo "TEST OK"
Another example of using the return command can be found in Section 6.5
4.3.54 print
To print a line or variable (scripting).
Handy when doing scripting to see what values will be substituted to a variable.
print $var print $table[$var]
4.3.55 alias/unalias <alias> <command>
Print or define command aliases.
Example:
Type alias on its own to list all defined aliases.
Use command "unalias" to undefine aliases. Example:
Aliases can be stored permanently in the ~/.moshellrc file, using the same syntax as above.
4.3.56 lf[c] <file>
Load a moshellrc file or a offline COLI file.
4.3.57 bg[g]/bgs/bgw [<commands>|<id(s)>|all] [<maxtime>]
Run some moshell commands in background or check status of background jobs.
Syntax:
![Page 125 of the Ericsson MoShell user manual — - smd[slcr] [-m <days>] [-s <size>] [-f <filter>] [-o a|s|n] [-u <user>|all] [-d <directory>] [-n <max>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-125.webp?w=400)
USER GUIDE 125(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 following variables and arrays keep track of the list of background jobs and their properties:
4.3.58 - smd[slcr] [-m <days>] [-s <size>] [-f <filter>] [-o a|s|n] [-u <user>|all] [-d <directory>] [-n <max>]
Server Maintenance - disk usage
Switches:
Examples - diagnostics with smd:
Examples - cleanup with smd:
![Page 126 of the Ericsson MoShell user manual — pe[c][l][k] [<polling interval>|<pid>] [<trigger>] [<action script>] [<number of iterations>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-126.webp?w=400)
USER GUIDE 126(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
Examples - cleanup with cronjobs:
Example of some cronjobs to remove ropfiles older than 30 days and compress logfiles older than 30 days (contents of "crontab -e" is shown). In this example the jobs are performed every saturday at 1:00 am.
# minute (0-59), # | hour (0-23), # | | day of the month (1-31), # | | | month of the year (1-12), # | day of the week (0-6 with 0=Sunday). # | command(s) # | 00 01 * * 6 find /home/user/moshell_logfiles -type f -name ’A*.1.xml.gz’ -mtime +30 -exec rm -f {} \; 00 01 * * 6 find /home/user/moshell_logfiles -type f -name ’*_ropfiles.zip’ -mtime +30 -exec rm -f {} \; 00 01 * * 6 find /home/user/moshell_logfiles -type f -name ’*.log’ -mtime +30 -exec gzip -f {} \;
4.3.59 pe[c][l][k] [<polling interval>|<pid>] [<trigger>] [<action script>] [<number of iterations>]
CPP post event functions
Arguments of the "pec" command (first three are mandatory):
– nodelog: hook will be triggered after specific log appeared in concrete node log (look at "lg" moshell command
description to get more information about node log)
Argument of the "pek" command (mandatory):

USER GUIDE 127(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.3.60 q/by/exit/quit [<exitcode>]
Exit moshell.
Any of the following commands can be used to exit moshell: q, by, exit, quit
The exit command supports specifying an exit code, eg: exit 1
4.4.1 pmom[acdpo] [<moclass>] [<counter>] [<data-type>] [<flags>] [<description>]
Print description of PM counters.
The type field refers to the data type of the counter value, e.g. an integer (long), or a sequence of integers.
The flags field refers to the properties of the counter, eg:
4.4.2 kmom[d] [<area>] [<kpiname>] [<MOclass>] [<formula>] [<kpidescription>]
Print description and formulas of KPIs.
![Page 128 of the Ericsson MoShell user manual — pget/lpget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-128.webp?w=400)
USER GUIDE 128(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.3 pget/lpget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>]
Read PM attribute(s) from MO(s).
Does not work on RNC MOs (UtranCell, IubLink, etc).
4.4.4 spget/lspget [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>]
Read PM attribute(s) one by one ("slow pget").
Slow but useful in case the standard "pget" command is not working due to some attribute returning an exception.
4.4.5 hpget[c][m]/lhpget[c][m] <moGroup>|<moFilter>|<proxy(s)> [<attribute-filter>] [<value1-filter>] [<value2-filter>] [<value3-filter>] etc...
Read PM attribute(s) from MO(s), print horizontally one line per MO (instead of one line per attribute).
Example:
4.4.6 pdiff/lpdiff [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value-filter>]
Print incrementation of PM attributes.
Runs two consecutive pget commands separated by a time interval equal to the value of the uservariable pm_wait (default 25 seconds). Displays the value by which the counter(s) incremented in the interval pm_wait. The list of MOs displayed are stored in an MO group called pdiff_group. Example1: check all VclTp MOs whose transmittedcells have incremented but whose receivedcells have not incremented (could point towards a transmission problem)
>> pdiff vcltp= transmit !^0 >> pdiff pdiff_group receive ^0 >> acc pdiff_group eteloopback (we can now perform a loopback test on those VclTp to check if they re
Example2: check all Os155SpiTtp MOs whose errored seconds have incremented.
>> pdiff os155 es !^0
4.4.7 hpdiff[m]/lhpdiff[m] [<moGroup>|<moFilter>|<proxy(s)>|all] [<attribute-filter>|all] [<value1-filter>] [<value2-filter>] [<value3-filter>]
Print incrementation of PM attributes, horizontally one line per MO (instead of one line per attribute)
This is the same functionality as "pdiff" except that the counters are printed side by side, one line per MO. For more information, refer to the help of the "pdiff" command.
![Page 129 of the Ericsson MoShell user manual — pmx[hfdnsckwlb3zeity] [<mofilter>|<mogroup>] [<counter-filter>|<kpi(s)>] [-l <zipfile>|<directory>] [-w <webdirectory>] [-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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-129.webp?w=400)
USER GUIDE 129(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:
4.4.8 pmx[hfdnsckwlb3zeity] [<mofilter>|<mogroup>] [<counter-filter>|<kpi(s)>] [-l <zipfile>|<directory>] [-w <webdirectory>] [-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>]
Display counter or KPI values, extracted from the statistics ROP files, or from the MOs in real-time.
– a regular expression matching the name(s) of the counter(s) that shall be printed, eg rrc.*success
– a regular expression matching the name(s) of the KPIs(s) that shall be printed, eg rrc.*success. The KPI formulas
are read from the default formula file in moshell/commonjars/pm or from the formula file specified in the "-f" option.
If the first and second arguments are omitted, the XML ROP files are parsed and the result is stored on file instead of being displayed to screen. The result files will be stored in the same location on the workstation as where the XML ROP files are stored, ie: ~/moshell_logfiles/logs_moshell/pmfiles/nodeipaddress. This location can be changed with the user variable pm_logdir.
Arguments
![Page 130 of the Ericsson MoShell user manual — pmx[hfdnsckwlb3zeity] [<mofilter>|<mogroup>] [<counter-filter>|<kpi(s)>] [-l <zipfile>|<directory>] [-w <webdirectory>] [-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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-130.webp?w=400)
USER GUIDE 130(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
It is possible to pipe the command into a unix command (eg: grep, sort, etc).
- Compare the evolution of the counter pmTotNoRrcConnectReq in the period 20140101 from 9:00 to 10:00 , with the period from 11:00 to 12:00 , and use bucket option.
Switches
![Page 131 of the Ericsson MoShell user manual — pmr[agfkwop3z] [-g <mofilter>|<mogroup>] [-z <mogroup>] [-r <report(s)>] [-l <zipfile>|<directory>] [-w <webdirectory>] [-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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-131.webp?w=400)
USER GUIDE 131(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
Performance scanners can be read with the pgets command and created with the pcr command or from OSS/ENM.
In the case of RAN nodes (RNC, RXI, RBS, eNodeB), the OSSRC/ENM does not allow external tools (such as moshell) to create/delete/modify a PM scanner. Any attempt to do this will result in OSSRC/ENM reverting the change. This is a feature of OSS/ENM and applies only to RAN nodes, not MGW.
Counter instances that are defined in several PM scanners will be reported by CPP as duplicated entries in the ROP files.
This can lead to unexpected results, such as counters with doubled values.
Usually the pmr/pmx commands can successfully ignore the duplicated counter entries but only when all the processed ROP files have the same type of counter duplication.
Unexpected values will occur when some of the processed ROP files have a duplication while other dont.
Therefore it is highly recommended to make sure that none of the counters are defined in several scanners at the same time.
The commands pgets and pmxs will show if there are any duplicated counter instances in the PM scanners.
4.4.9 pmr[agfkwop3z] [-g <mofilter>|<mogroup>] [-z <mogroup>] [-r <report(s)>] [-l <zipfile>|<directory>] [-w <webdirectory>] [-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>]
Produce PM KPI reports, based on counter values in statistics ROP files and formulas in CPI documentation.
Report choice
![Page 132 of the Ericsson MoShell user manual — pmr[agfkwop3z] [-g <mofilter>|<mogroup>] [-z <mogroup>] [-r <report(s)>] [-l <zipfile>|<directory>] [-w <webdirectory>] [-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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-132.webp?w=400)
USER GUIDE 132(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
– pmr -g tdmterm will show KPIs based on TdmTermGrp counters only
– pmr -g cellmod8 will show KPIs based on counters of cells belonging to module 8 only (where cellmod8 is a MO
group created with the commands ma iubmod8 iublink module =8$ and ma cellmod8 iubmod8 reserved)
To check that the KPIs are within certain criteria, a threshold file can be specified with the option -t.
Example of threshold file and syntax explanation can be found at moshell/examples/pm_files/thresholds.txt.
Any KPI that are outside the the criteria specified in the threshold file will be marked in red or purple, depending on the severity.
Example:
Each pmr report in the web page shows up as a table and in some cases a graph is also generated. Currently works best with Firefox, avoid IE.
The option "p" can be used to generate PNG files, using GnuPlot.
The GnuPlot package can be installed from cygwin "select packages" window: Graphics > gnuplot
Example:
For RNC, it is recommended to run the plot on selected cell by using MO group. Example:
If some ROP files contain counters marked with the "suspected faulty" tag (TRUE) then they are silently discarded unless the user has given the option k (e.g. pmrk) in which case the suspected faulty counter values will be kept. To identify which counter values are marked with the suspected faulty tag, the command pmxs can be used.
To use pmr online (ie when connected to a node) just skip the -l option.
The function will check if there are any new XML files on the node, download any new XML files to the workstation as long as their timestamp is within the timespan specified by the -m/-p/-s/-e options, get some MO configuration data and print the menu.
To run pmr offline, specify the location of the ROP files with the -l option. The location can be a folder or a zipfile produced by the pmrf command. Refer to the "Offline mode" chapter for more info.
If the command pmra is used then all ROP files are fetched. Otherwise, the ROP files of the last hour are fetched.
![Page 133 of the Ericsson MoShell user manual — pmr[agfkwop3z] [-g <mofilter>|<mogroup>] [-z <mogroup>] [-r <report(s)>] [-l <zipfile>|<directory>] [-w <webdirectory>] [-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>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-133.webp?w=400)
USER GUIDE 133(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 -m and -p options are used for specifying the timespan that the reports should cover, in hours or parts of hours.
The timespan is relative to the node’s current date/time if online, and relative to the most recent file timestamp if offline.
Example:
By default the timespan is for the last 1 hour.
The -s and -e options are used for specifying an absolute timespan. The timestamp should be in the format yyyymmdd[.hhmm] Example:
The -tz switch is for printing the timestamps a specific timezone. Eg: -tz +10 will show the timestamps in UTC+10 timezone.
It is possible to pipe each report into some unix commands. The pipe is done at the "Your Choice" prompt, after the menu listing all the reports. Example:
The output format can be specified with the -o option.
By default, the output is text but it is also possible to specify the following formats:
This file is only needed when offline, when printing reports aggregated on Iub/Module/AtmPort/Subrack level.
If ROP files have been collected with "pmrf" then the file is automatically included with the ROP files and will be used when parsing the ROP files offline. Otherwise, the path of the file can also be specified with the option "-i".
This file contains the following printouts:
get ^aal5tpvcctp= vcltpid get ^unisaaltp= aal5tpvcctpid get ^nbapcommon= unisaaltpref get ^iublink= rncmoduleref get ^utrancell= iublinkref get device= spmreference get ^ipaccesshostet= ipInterfaceMoRef get ^sctp= rpuid pr ^(ipinterface|pluginunit|atmport|vpltp|vcltp|ethernetswitchport|ethernetswitchmoduleport|internaleth
Counter instances that are defined in several PM scanners will be reported by CPP as duplicated entries in the ROP files.
This can lead to unexpected results, such as counters with doubled values.
Piping · Output format · IubCellModule file
![Page 134 of the Ericsson MoShell user manual — pme[fd][cgurv] [<pm_logdir>] [-b <boardgroup>] [-f ] [-m <minushours>] [-p <plushours>] [-s <startdate>[.<starttime>]] [-e <enddate>[.<endtime>]]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-134.webp?w=400)
USER GUIDE 134(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
Usually the pmr/pmx commands can successfully ignore the duplicated counter entries but only when all the processed ROP files have the same type of counter duplication.
Unexpected values will occur when some of the processed ROP files have a duplication while other dont.
Therefore it is highly recommended to make sure that none of the counters are defined in several scanners at the same time.
The commands pgets and pmxs will show if there are any duplicated counter instances in the PM scanners.
4.4.10 pme[fd][cgurv] [<pm_logdir>] [-b <boardgroup>] [-f ] [-m <minushours>] [-p <plushours>] [-s <startdate>[.<starttime>]] [-e <enddate>[.<endtime>]]
Fetch/decode event ROP files (RNC/RBS/ERBS/MSRBS).
The -m/-p/-s/-e options allow to specify the time period, see below for more information about time options.
The f option is for fetching the ROP files, the d option is for decoding them.
The c, g, u, r options are for specifying which type of event files shall be fetched/decoded. If none of these options are specified then all four types of event files are fetched/decoded:
The -b option allows to fetch GPEH files on certain modules only, eg: pmefdg -b mod1.
The -f option is for decoding with the decoder option --force.
It is possible to specify the path where the event ROP files are stored:
The ls -l printout of the node’s event ROP files directory is saved in the file "node_ls.log".
Time options:
The -m and -p options are used for specifying the timespan that the reports should cover, in hours or parts of hours. The timespan is relative to the node’s current date/time if online, and relative to the most recent file timestamp if offline.
Example:
By default the timespan is for the last 0.25 hour (15 minutes).
The -s and -e options are used for specifying an absolute timespan. The timestamp should be in the format yyyymmdd[.hhmm] Example:
![Page 135 of the Ericsson MoShell user manual — pst [<scan-filter>|<scan-proxy>] [<scan-state>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-135.webp?w=400)
USER GUIDE 135(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.11 pst [<scan-filter>|<scan-proxy>] [<scan-state>]
List all PM scanners and their state. Examples:
4.4.12 pgets[m][n][r] [<scan-filter>|<scan-proxy>] [<contents-filter>]
Print the counters defined in the scanner(s).
Without argument, all scanners/jobs are printed.
For a STATS/PM scanner, we see the following:
– deprecated: means that the counter is obsolete and will never be stepped.
– a number in square brackets: shown on PDF counters to indicate the number of elements in the array.
– notInMOM: means that the counter is implemented in RNC SW but not specified in the MOM. Should only happen on
pre-GA SW.
For an EVENT scanner (GPEH/UETR/CTR), we see the following:
It is possible to use a contents-filter. If used, then only the scanners containing a string matching the filter (not case sensitive) will be displayed.
![Page 136 of the Ericsson MoShell user manual — pcr[pcfpdaz]/lpcr[pcfpdaz] <ScannerName|JobName> <moclass-filter>|<moinstance-filter>|<mo-group>|<counter-file> [<counter-filter>] [<granularity>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-136.webp?w=400)
USER GUIDE 136(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
and if yes, in how many scanners and which ones
4.4.13 pcr[pcfpdaz]/lpcr[pcfpdaz] <ScannerName|JobName> <moclass-filter>|<moinstance-filter>|<mo-group>|<counter-file> [<counter-filter>] [<granularity>]
Create a Statistics Scanner or PmJob.
The granularity field is optional.
By default it will be set to 900 (15 minutes). In a RCS node, it may be necessary to run the following command (followed by node restart) before being able to select other granularity values: /misc/authlevel disabled;/pms/rp ecim
A negative filter (!) can be used on the moclass or counter filter in order to exclude certain MOs or counters. See more info about regular expressions used in the filters in Section 3.
![Page 137 of the Ericsson MoShell user manual — pcrk[f][v][d] [<kpidefinitionfile>] [<granularity>]](/cdn/reader/a6/a6147d0a96a87c01566ddc8dda876b43dcd964fb8c1b5a03a7e823f7c0156623/images/page-137.webp?w=400)
USER GUIDE 137(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
pcrf atmport_vcltp atmport|vcltp (not recommended)
Interaction with OSSRC/ENM:
Scanners/Jobs created from moshell/AMOS on a node controlled by OSS/ENM will be automatically deleted by OSS/ENM after a few minutes. It is possible to avoid this by:
Format of the counter file: The spaces at the beginning of the line are not necessary, they are just shown for readability purposes. To comment out some lines, just precede the line with a hash sign (#). Any words after the first word are ignored.
Example:
pmCellDowntimeAuto pmCellDowntimeMan pmChSwitchDch128Fach pmChSwitchDch384Fach pmChSwitchDch64Fach
It is also possible to take the printout from pmom as is. This will work as well and saves having to do any editing.
############################################# MO Class Pm Counters ############################################# UtranCell 296 pmCellDowntimeAuto pmCellDowntimeMan pmChSwitchDch128Fach pmChSwitchDch384Fach pmChSwitchDch64Fach pmChSwitchFachDch pmChSwitchFachIdle
It is also possible to use the following format for the counter file (for creating counters on MO instances where each MO instance will use a different set of counters).
Example:
ManagedElement=1,RncFunction=1,UtranCell=30124 pmRes1 pmRes2 ManagedElement=1,RncFunction=1,UtranCell=30125 pmRes3 ManagedElement=1,RncFunction=1,UtranCell=30126 pmRes2 pmRes4
It is also possible to take the printout of pgets as is. This is useful to clone an existing scanner, eg with a different rop period. Example:
l+ pgets l- pbl pcrf $logfile . 300
4.4.14 pcrk[f][v][d] [<kpidefinitionfile>] [<granularity>]
Create PmKpi definitions on the node.
AtmPort · pmReceivedAtmCells pmSecondsWithUnexp UtranCell

USER GUIDE 138(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 command first generates a copy of the existing PmKpi definitions, this can then be used to restore the current PmKpi MOs if needed. Then the kpidefinition file specified in the argument is used to generate a new set of PmKpi MOs which are then activated on the specified granularity.
Arguments:
4.4.15 pbl <scan-filter>|<scan-proxy>
Suspend a scanner. This means that counters defined in this scanner will not be recorded in XML files each granuality period.
4.4.16 pdeb <scan-filter>|<scan-proxy>
Resume a scanner.
4.4.17 pdel <scan-filter>|<scan-proxy>
Delete a scanner.
4.4.18 emom [uetr|gpeh|ctr|all] [<event-filter>]
Display list of events available for each kind of event-based scanner (RNC/RBS only).
The event reference files are stored in moshell/commonjars/eventfiles and are SW dependent.
MoShell automatically chooses the appropriate version of the event files so the user does not have to worry about this.
4.4.19 pset[d]
Set the contents of an event-based scanner (RNC/RBS/LTE/ENB/MSRBS).
Following syntaxes apply:
pset[d] [-s/-f :] | ||all
pset[d] [-s/-f :] | ||all
pset[d] [-s/-f :] | ||all
· [||all] [] [=] · | []

USER GUIDE 139(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
Use the emom command to view the list of events that apply for each measurement type.
Event scanners UETR/CTR are applicable for RNC only; UETRACE/CELLTRACE are applicable to LTE eNB; GPEH scanners are applicable to RNC and WRBS only.
The first argument is the scanner name or scanner proxy.
The second argument indicates the list of events to include, either using regular expression matching or from a file containing one event on each line. It is possible to use negative filter (!) to exclude certain events.
The following fields are optional, if no value is entered (or all in the case of GPEH/CELLTRACE utrancell-filter), no filter will be sent to the node who will then use a default setting:
List of additional filters that can be specified at the end of the command line with the syntax =:
For LTE eNB, the options -s/-f can be used to specify the output mode of the scanner:
If these options are used then the ip address and port for the stream must be given as argument to the option, example: -f 10.12.45.38:3402. If these options are not specified the the output of the scanner will be to FILE only.

USER GUIDE 140(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
supported by the node SW. The functionality of psetd is implemented as an moshell script, the script can be seen in moshell/commonjars/scripts/psetd.mos. The psetd command is called via an alias listed in the moshell file. Type alias to see the list of aliases. This shows that the user can define any new commands they need by adding an alias in the .moshellrc which will point to a script file. The parameters to the command will be sent to the script file via the positional parameters $1, $2, $3, etc. The variable $0 will be set to the whole line contents. See h run for info.
5.1 Software Upgrade CPP
Delete some old UpgradePackage if necessary to free up some disk space:
Create the UpgradePackage MO:
At the prompt, enter FTP Server Address where the UP is stored and the path to the UCF (Upgrade Control File). At the next prompts, enter FTP Server UserID and Password, or just d for default value (will be anonymous)
Perform the SW installation:
Monitor installation progress:
Perform the SW upgrade:
Monitor upgrade progress (confirmUpgrade will be done automatically):
Check that the new cv is using the new upgrade package
Delete some old UpgradePackage if necessary to free up some disk space:
Create the UpgradePackage MO:
At the firt prompt, enter the URI from where to fetch the package, eg sftp://@/ At the next prompt, enter the server password
Perform the SW installation:

USER GUIDE 141(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
Monitor installation progress:
Perform the SW upgrade:
Monitor upgrade progress (confirmUpgrade will be done automatically):
Check that the new cv is using the new upgrade package
When trying to integrate a new RBS, some data mismatch might cause the Iub, Cell, or Channels not to come up. Things to check are the values of:
Take a print of all MOs related to the Iub and check that the vci values match on both sides, check if any related MOs are down:
lk iublink= #in RNC lk iub= #in RBS
Find out the Aal2Ap used by that Iublink in RNC:
Check that the AAL2 addresses match on all sides:
get aal2routingcase= (in RNC and RXI) get aal2sp=1 (in RBS and RXI)
Check that the AAL2 path id’s match on both sides:
get aal2pathvcctp= pathid (in RNC, RBS, and RXI if applicable)
Check that the aal2 continuitycheck match on both sides:
get aal2pathvcctp= continu (in RNC, RBS, and RXI if applicable)

USER GUIDE 142(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
Check that localcellid match on both sides:
get cell= local (in RBS and RNC)
Perform a loopback test on all VCIs of that iub, to see if transmission is ok
Check RNC devices are ok
Check Cell error code, cellbarred, actor info, etc.
ced tgc/tgd (type "h tg" for info)
Check RNC/RBS general state, look for potential HW/SW faults
Check all cross-connects are ok
stc (mainly in RXI/MGW)
Find out the module MP that is handling the site and check if there are some errors:
get iublink= module lh modXX te log read
(to restart the module MP, you can use the command "acc modXX restart")
Take a print of all MOs related to the Iu and check that the VCI values match on both sides. Also check if any related MOs are down:
Perform a loopback test on all VCs of that interface, to see if transmission is OK:
Check that the pointcodes matches on both sides
Activate/deactivate a C7 link
Block/deblock an Aal2Path, check that the pathIds and a2ea addresses match on both sides:
bl/deb aal2pathvcctp= get aal2pathvcctp= pathid get routingcase=
Moshell supports the use of variables and logical constructs. These can be used directly from the command line or within MoShell command files.

USER GUIDE 143(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 following variables are set immediately after MoShell startup:
The following variables are set after the MOM has been parsed:
These variables can be handy to have when a script needs to know what SW revision is running in the node or what kind of node it is.
The following variables are set after running certain MO commands:
The following variables are set after running the commands bp/bo:
The following variables are set after running the cvls command:
The following variables are set after running one of the l+/u+/u- commands:

USER GUIDE 144(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 following variable is set after having logged on to the node via telnet/SSH or FTP/SFTP.
The contents of the variable can not be printed, it will only show if it’s empty or not. By setting this variable to empty (by doing: $password = ), this will force MoShell to check the password again. Useful in case the password has changed on the node during the MoShell session.
The $nr_of_vars variable is set after running the pv command.
This variable indicates the number of scripting variables that were printed in the last pv printout. By using pv together with a filtering pattern (eg: pv $table), it is possible to find out the number of variables that had matched the pattern, for instance the number of elements in a hashtable.
The $nr_of_lines variable is set after using the functions "readfile" or "testfile".
After using the function "testfile", this variable is set to 0 if the file does not exist and to 1 if the file exists.
After using the function "readfile", this variable is set to 0 if the file does not exist and to the number of liens in the file if the file exists. The difference between testfile and readfile is that testfile won’t actually read the file, it will just check if the file exists whereas readfile will test the file, then read it.
Example1:
$lineContent = testfile(/path/to/myfile) if $nr_of_lines = 0
l echo "File not found!" return fi
Example2:
$lineContent = readfile(/path/to/myfile) if $nr_of_lines = 0
l echo "File not found!" return fi for $lineNumber = 1 to $nr_of_lines
if $lineContent[$lineNumber] ~ thispattern
print We found it! The line is $lineNumber. return fi done
Example (list all scripting variables currently set via pv):
A variable value can be assigned in six ways, see below.

USER GUIDE 145(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
A variable can also be unassigned, using the unset command.
By using the command unset small, all variables are unset, except:
By using the command unset all, all variables are unset except the "system" variables.
NOTE: It is always good practice to unset a variable as soon as it is not needed anymore since having too many variables defined slows down the processing of the command line. It is also good to do unset all at the beginning and end of a command file (and before doing the return command) in order to avoid interference from un-needed variables. See the script examples in moshell/commonjars/scripts
To print all currently assigned variables, use the command printvar. To just print one variable, type:
pv (where the pattern matches the variable(s) to print)
The variable value can be assigned in six ways:
The variable to be assigned is on the left side of the equal sign and the value is on the right side. Each element must be separated by spaces. Example:
$i = 3 $node = RNC $password =
By running password = this sets the password to an empty value and will force MoShell to ask for the password again.
Example:
moshell -v upmo=CXP9011008_R1A03,ftpserv=10.1.0.16,secure_shell=1,secure_ftp=1 rnc34}
In this case, we can see that scripting variables ($upmo and $ftpserv) and user variables (secure_shell and secure_ftp) have been mixed in the same statement. This is OK because any variable that is not recognised as a user variable will be treated as a scripting variable.
The mo-filter and attribute-filter must be specified, then comes the redirection sign (>), then the variable name. If several attributes are printed, only the last attribute value gets assigned into the variable. Examples:
a) get 0 productName > $nodeType (result: $nodeType = RBS3202)
b) get ethernetlink ipaddress > $ipaddress (result: $ipaddress = 10.1.128.17)
c) get configurationversion currentupgrade > $currentUp (result: $currentUp =
d) get $currentUp administrativedata > $swRev (result: $swRev = Struct{5} >>> 1.productNumber =
CXP9011123 >>> 2.productRevision = R12F etc.)
e) pget EUtranCellFDD=1 pmRaSuccCbra > $pmra (result: $pmra = 157)
f) lfro subrack=ms,slot=1,pluginunit=1$ ^r > $froid (result: $froid = 0)
g) d2ip -4127129085 > $ip_addr (result: $ip_addr = 10.1.2.3)
h) h2d 0xa > $res (result: $res = 10)
i) uv ^credential > $credential (result: /home/ericsson/moshell/commonjars/host.p12)
The following numeric operations are supported:
print "$variable" · UpgradePackage=CXP9011123_R12F)

USER GUIDE 146(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
b) $i = $i + 1 (result: $i=2)
c) $j = $i * 3 (result: $j=6)
d) $k = $i * $j (result: $k=12)
e) $l = $i / $j (result: $l=0.333)
f) $m = $k % 5 (result: $m=2)
The Unix command must be surrounded by back-quotes (‘). Variables can be used within the Unix command. Examples:
$date = ‘date +%y%m%d-%H%M‘
(open a logfile, don’t display anything on the screen) te log read l-
(close logfile) $errors = ‘grep -c ERROR $logfile‘
lt configurationversion get configuration startable > $startable
print gensub(/..$/,"",1,cvname) sprintf("%02s",substr(cvname,length(cvname)-1)+1) }’‘ cvms $cvname
If the built-in function system is used instead of the back-quotes (‘) then the exit code of the unix command is saved to the variable (instead of its output).
Example:
$result = system(cp $file1 $file2)
The following string operations are supported: concatenation and substitution / replacement.
The concatenation is performed by juxtaposing the strings. Syntax for concatenation: $var = string1string2string3 (the strings are concatenated without space in between) or $var = string1 string2 string3 (the strings are concatenated with spaces in between)
Syntax for concatenation:
a) $var = string1string2string3 (the strings are concatenated without space in between)
b) $var = string1 string2 string3 (the strings are concatenated with spaces in between)
The substitution/replacement is performed using the -s switch to specify the string to substitute and the -r switch to specify the string it should be replaced with. If the -r switch is not used, then the string will be replaced by nothing. If the -g switch is specified, then all instances of the string to substituted, otherwise, only the first instance.
Syntax for substitution/replacement:
a) $var = origString -s strToSubstitute [-r strToReplaceItWith [-g]]
Regular expressions can be used in the string manipulations. Examples:
$var = abc_defabc ghi
(remove the logfile)

USER GUIDE 147(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
$var1 = $var -s abc
$var2 = $var -s \x20
$var3 = $var -s abc -g
$var4 = $var -s abc -r xyz
$var5 = $var -s abc -r xyz -g
$var6 = $var -s a.*c -r xyz
(result: $var7 = abc_defabc ghiABCxyz ghi, the three strings $var, ABC and $var6 have been concatenated)
$var8 = $var ABC $var6
Currently, the following functions exist:
Example 1:
lt iublink ma iub iub for $mo in iub
$mordn = rdn($mo) if $mordn ~ 1023
$var7 = $varABC$var6

USER GUIDE 148(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
lcc $mordn lbl $mordn, fi done
Example 2:
Example 3:
$table = readfile(/path/to/myfile) for $lineNumber = 1 to $nr_of_lines
print $table[$lineNumber] $word = split($table[$lineNumber]) if $word[1] ~ ^#
$nr_of_comments = $nr_of_comments + 1 fi unset $word unset $table[$lineNumber] done
(Note: by unsetting the entry we’ve just read - provided we don’t need it anymore - will make things faster)
Example 4:
Logging in to an unknown node with moshell -n option (no ip connectivity check) and checking the type of node
The loop is intended to keep checking if the node happens to be down at the time of the check.
$var80 = check_ip_contact($ipaddress,80) $var9830 = check_ip_contact($ipaddress,9830) $var4912 = check_ip_contact($ipaddress,4192) if $var4192 = ok
uv comcli=21 uv username=expert $password = expert break else if $var9830 = ok
uv comcli=11 uv username=root $password = root break else if $var80 = ok
uv comcli=0 break else
wait 30 $i = $i + 1 fi done
Example: The purpose of the little moshell script below is to make a customized CV name like: date_nodeType_swRev
cvls $date = ‘date +%y%m%d‘ (result: $date = 040930) get 0 productName > $nodeType (result: $nodeType = RBS3202) $nodeType = $nodeType -s RBS (result: $nodeType = 3202) get configurationversion currentupgrade > $currentUp
(result: $swRev = Struct{5} >>> 1.productNumber = CXP901913/2 >>> 2.productRevision = R12N >>> 3.productName = CXP901913%2_R12N ) $swRev=‘gawk -v currentsw="$swRev" ’BEGIN{ swrev=gensub(/\r|\n/,"","g",currentsw);
print gensub(/^.*Revision = | >>> 3.product.*$/,"","g",swrev) }’‘ (result: $swRev = R12N) cvms $date_$nodeType_$swRev (result: cvms 040930_3202_R12N )
return fi · for 10

USER GUIDE 149(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 index and the value of the hashtable can be a variable, a constant, or a mix of both.
All variable assignment methods described in Section 6.2 apply for assigning values into hashtables as well.
Assigning constants into a hashtable
>> $table[1] = hello >> $table[2] = hej >> $table[hoho] = 5 >> pv tab (result printout:) $table[hoho] = 5 $table[1] = hello $table[2] = hej
Assigning variables into a hashtable:
>> $mo = AtmPort=MS-6-1 >> $proxy = proxy($mo) >> $proxylist[$mo] = $proxy >> $mo = AtmPort=MS-6-2 >> $proxy = proxy($mo) >> $proxylist[$mo] = $proxy >> pv proxylist (result printout:) $proxylist[AtmPort=MS-6-1] = 103 $proxylist[AtmPort=MS-6-2] = 112
More examples on how to use hashtables are described in Section 6.5.
The if statement must be followed by a condition. The comparison operator of the condition must be surrounded by spaces. Zero or more else if statements can be used after the if statement. Zero or one else statements can be after the if or else if statements.
The end of the if/else structure must be specified with a fi statement. Each statement must be on its own line and can be followed by one or more commands. Several conditions can be combined, using the logical AND (&&), or the logical OR (||). Any number of AND/OR can be put on a line but NOT BOTH on the same line.
Grouping conditions with brackets is NOT supported.
The return command can be used to exit from the command file in case a certain condition is met. Type h return for more information on how to use this command.
Syntax examples:
command1 else if

USER GUIDE 150(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
A condition can use the following comparison operators:
The words around the operator can be either a variable or a single word but NOT a string containing spaces or a concatenation of a variable and string. Following conditions are syntaxically correct:
if $var1 = $var2 if mystring ~ $var if 10 > 3 if $i < 2
Following conditions are NOT syntaxically correct and will return unexpected results:
if mystring_$var1 ~ $var2 if mystring is this ~ your string
A condition can also just contain one variable, in which case it will check if the variables exists. The words around the operator can be either a variable or a single word but NOT a string containing spaces or a concatenation of a variable and string. Following conditions are syntaxically correct:
if $var1 = $var2 if mystring ~ $var if 10 > 3 if $i < 2
Following conditions are NOT syntaxically correct and will return unexpected results:
if mystring_$var1 ~ $var2 if mystring is this ~ your string
A condition can also just contain one variable, in which case it will check if the variables exists.
Example to check if a variable $var exists. If $ exists (i.e. has any value set) then it will do something..
...do something fi
Example to check for node type and see attenuation accordingly:
get 0 productname > $nodeType
if $nodeType ~ 3202 || $nodeType ~ 3104
get feeder attenuation set feeder attenuation 4 else if $nodeType ~ 3101
get feeder attenuation set feeder attenuation 16 else
get feeder attenuation fi
The parameter to the for construct can be:
if $var

USER GUIDE 151(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 end of the for structure must be specified with a done statement.
The wait command can be used in the body of the loop to specify a delay to wait in between each iteration. The delay can be in seconds, minutes, hours, or even ROP periods. (Type h wait, Section 4.3.51 for info.)
Do not use the sleep command as this will result in hanging if the loop is aborted.
The loop can be aborted any time by typing ctrl-z , then touch , then fg. The path is shown in the window title bar. Type h ctrl-z for more info about aborting.
The break command can be used within the loop to exit from the loop.
Syntax examples:
command1 wait done
get $mo > $variable $variable1 = set $mo $variable1 etc... done
te e trace$min process done
command1 command2 done · break fi done

USER GUIDE 152(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
Practical examples:
lt upgrade acc upgradepackage=xxx nonblockinginstall for ever
$return = 0 wait 10 get upgradepackage=xxx state > $upstate if $upstate ~ ^1
break else if $upstate ~ ^6
$return = 1 break fi done if $return = 1
return fi acc upgradepackage=xxx upgrade
run testcase_3.1.1.cmd wait 2m done
lt ^utrancell ma cell ^utrancell for $mo in cell
get $mo primarycpichpower $pich $pich = $pich + 1 set $mo primarycpichpower $pich done
ba spb spb for $board in spb
facc $board restart 0 1 done
lma programs_on_slot_19 subrack=ms,slot=19,.*program for $prog in programs_on_slot_19
$i = $i + 1 fro $prog ^res > $frolist[$i] done for $fro in $frolist
restartObj pgm $fro done
for $var = 20 to 14
$board = 00$var00 facc $board restart 0 1 done
Users can define their own functions, using the func/endfunc construct.
If the function is called with arguments, these are assigned to the variables $1, $2, $3, etc The variable $0 is set to the whole line
for 50

USER GUIDE 153(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
contents.
Example:
Here we are defining a function which checks the state of the mirrored disks and returns once the disks are in sync
#if $1 is undefined or different to an integer value #then we set it to 10 seconds if $1 ~ ^[0-9]+$
$wait_interval = $1 else
$wait_interval = 10 fi for ever
wait $wait_interval l+om $tempdir/diskstate lh coremp mirror s l- $res = ‘grep -c "Peer Disk Status: *Valid" $tempdir/diskstate if $res > 0
break fi done endfunc
$date = ‘date "+%Y-%m-%d %H:%M:%S"‘ for ever
$reply = readinput(Waiting from [$date]. Type "y" when ready: ) if $reply ~ ^[yY]
break fi done $date = ‘date "+%Y-%m-%d %H:%M:%S"‘ print "Finished waiting at [$date]" endfunc endfunc
First we are running a file containing all the definitions for our user-defined functions.
(Note that the functions can also be defined within the same script, but by keeping all functions in a separate file means that several command files can use the same functions)
We have called the function check_disk_state with an argument "5" which in this case will be used as the "$wait_interval" parameter in the function
run ~/myfunctions_define.mos for ever
check_disk_state 5 waitforuser facc 0 manualrestart 0 0 0 pol done
It is possible to nest one or more if/else statement within a loop statement and vice-versa. But it is currently not possible to nest an if/else statement within an if/else statement and a loop statement within another loop statement.
The current workaround is to put the for/if constructs into functions. See Section 6.6 for more info on functions.
Example:
The following script starts the install, then checks the state of the install every 10 seconds. Once the upgradepackage is installed, it starts the upgrade. Then it checks the state again and once the upgrade is in state awaitingconfirm, it confirms the upgrade.
func check_disk_state · func waitforuser

USER GUIDE 154(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
$UP = upgradepackage=CXP9011123_R12F acc $UP nonblockinginstall for ever
wait 10 get $UP state > $state if $state ~ ^1
break fi done get $UP state > $state if $state ~ ^1
acc $UP upgrade fi wait 120 for ever
wait 10 get $UP state > $state if $state ~ ^3
break fi done if $state ~ ^3
acc $UP confirmupgrade fi
Some more examples:
board_status -d 00 10 -c "mirror stat" | tee tmpfile.tmp board_status -d 00 11 -c "mirror stat" | tee -a tmpfile.tmp $tmp = ‘grep -c "Peer Disk Status: Valid" tmpfile.tmp‘ if $tmp > 0
wait 60 fi done
wait 300 #give it some time to run first for ever
pol 1 1 get upgradepackage=mypkg state > $state if $state ~ ^1
break #upgrade failed else if $state ~ ^3
break #upgrade complete fi wait 60 done
Example scripts can be found under moshell/commonjars/scripts and moshell/examples/scripting/
The moshell package includes a number of utilities that complement the moshell functionality. They are stored in the same directory as moshell but are executed as separate, stand-alone scripts.
for ever · break else

USER GUIDE 155(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
Detailed information about each utility can be found by executing the utility without any arguments. (Except for the PM tools where the help is shown by using the -help option, eg: pmExtract -help).
The network management utilities are for performing operations on many nodes in parallel. The list of nodes on which to perform the operations shall be stored in a file called the sitefile. The ip-addresses/DNS-names and passwords of all nodes of the network must be stored in a reference file called the ipdatabase.
The ipdatabase uses the following syntax:
(It is recommended to use the DNS-address instead of the IP-address).
It is also possible to specify user variables and/or scripting variables in the fourth column of the ipdatabase.
An example of a sitefile and an ipdatabase can be found in the directories moshell/examples/mobatch_files.
The following Network Management tools are currently included in Moshell:
a) to collect SW level and CV from many nodes in parallel.
b) to delete UP’s from many nodes in parallel.
The auditing tools are for offline postprocessing of Node logs (MO Dumps) and reference files in order to check parameter validity or health-checks.
The following tools are included with Moshell:
a) to parse moshell health-check logs and check for obsolete HW, HW faults, errors, etc.
b) to compare pre-check and post-check (eg health check logs before and after an upgrade or a testcase)
a) to convert a file from winnow baseline format to moshell command file
b) to convert a change_all script to moshell command file
The PM tools are for offline postprocessing of Performance Management XML files. They consist of a number of command-line tools, designed to be linked together in a pipeline (ie the output of one tool feeds into the next). The following PM tools are included in Moshell:
·

USER GUIDE 156(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
For more information, run the utility with the -help option (eg pmExtract -help) or have a look in the pmTools documentation. This document (which may not be the latest can also be found in moshell/examples/pm_files/pmTools.doc)
Some other tools included with Moshell are:
When running moshell on a server in a multi-user environment, there needs to be regular maintenance in order to clean up the disk and any hanging processes.
A known bug of moshell is that it doesn’t always shut down all of its spawned processes upon exiting which leads to CPU overload and run out of RAM memory. This problem should now be fixed thanks to the use of various timeouts but if this does not help, then it is recommended to regularly check the rogue processes using the unix command top.
Once the top command is running, you can type the following commands in the top screen:
– o time (to see the processes that have been running for the longest time)
– o size (to see the processes that are using up the most memory)
– o cpu (to see the processes that are using up the most cpu. this is the default).
For disk usage diagnostics and cleanup, please refer to the help of the smd command.
If you get the following error when trying to start moshell:
gawk: fatal: cannot create child process for ‘/tmp/readlineXXXX_hhmmss’ (fork: Not enough space)".
It means that you do not have enough memory (i.e. RAM + swap space) on the machine.
Try running the command top on the Solaris box (it might not exist on the box though).
If you can run it, you’ll see a line like this:

USER GUIDE 157(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
A fundamental rule of Operating System management is that your swap space should also be > 2x the memory, so in this box we have 512Mb of RAM so we should have at least 1Gb of RAM (it started with just 256Mb of RAM - and we had this problem after opening a few sessions of MoShell). As a rule - if you are running MoShell on a Solaris box you should give it at least 512Mb of RAM and ideally 2Gb of swap space.
Luckily - there is an easy way to add new swap space - this is to make a new "swap file" on the disk (then you don’t need to repartition everything). You can do this in Solaris by following these steps:
This will make a 2Gb file /usr/swapfile to be used as our extra swap space. But it’s not enabled as swap space yet.. To add it as swap space.
This adds it in as swap space. But this is not permanent, next time you reboot the machine it’ll disappear. You can make it permanent by adding the following line to (the end of) /etc/vfstab
See man vfstab for more details on /etc/vfstab
9.1 Offline Mode
The offline mode allows to run an moshell session against a set of logfiles of a node. When running moshell commands in offline mode, all information will be read from the logfiles, no communication taking place with the node.
The offline mode can be useful in several cases. For instance:
The following logfiles are used in offline mode:
It is possible to start moshell in offline mode by typing any of the following:

USER GUIDE 158(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 list of commands that are supported in offline mode can then be printed with the h command.
Type h for information on a specific command.
The SQL mode allows to run an offline moshell session against the configuration database of a node (db.dat or zipped CV).
To start moshell in SQL mode, use option -d, eg: moshell -d , moshell -d , or moshell -d Moshell then opens an SQL client session to the file and loads all the MO data into memory. To prevent loading MO data (for faster startup time), use the option -v nomo=1. Only sql commands will then be available. Note that the MO data when read from a CV/db.dat only contains the MO configuration attributes, not the MO state attributes. During startup, moshell also performs a consistency check on the various SQL tables of the database, to detect if there are any inconsistencies or corruptions. Currently not all moshell commands are supported in SQL mode, type h at the moshell prompt to see the list of supported moshell commands. It is also possible to run sql commands directly, e.g. sql select * from tables.
The Polyhedra database viewer which is used to load the CV/db.dat is currently delivered in two versions:
By default, moshell uses the newest version but it is possible to use the old version by starting moshell with option -v polyversion=0.
The multi mode allows an moshell session to be connect to several nodes at the same time.
The command syntax for starting moshell in multi mode is: moshell -m |
The sitelist consists of a comma separated list containing all the node names or ip/dns addresses.
The sitefile is a text file containing the list of nodes names or ipaddresses, on node per line.
Example:
If node names are used, they must be defined in the ipdatabase. For more information about ipdatabase and sitefile, see the help of the mobatch utility by typing "mobatch" from the unix prompt.
To print the list of commands which are supported in multi-mode, type h at the moshell prompt.
More information about a specific command can be obtained by typing h .
The multi mode is primarily geared towards commands that use the corba services CS/FM/PM.
Moshell commands that access the node via telnet/ssh/ftp/sftp are currently not supported in multi mode.
When moshell is running in multi mode, a prefix is appended in front of certain objects in order to distinguish between different nodes and MOM versions:
MOM handling in multimode:

USER GUIDE 159(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
same MOM, which may have unexpected effects.
Known limitations in multi mode (to be fixed in a later release)
The revision history has been moved into a file called README in the moshell directory.
Pages referenced in this manual — manufacturer, support and downloads.
Owners and our team usually reply within a day — and your question helps the next person too.
Be the first to ask — other owners or our team will answer.