1 of 23

Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

BASIC MOSHELL COMMANDS

Introduction to moshell........................................................................................................2
Introduction to moshell commands.....................................................................................2
Cell Lock Sequence.............................................................................................................6
Cell unlock sequence...........................................................................................................8
Iub blocking sequence.........................................................................................................8
Iub unlock sequence............................................................................................................9
Alarm checking..................................................................................................................10
Check cell status................................................................................................................12
Check if a node is carrying traffic.....................................................................................14
View traffic statistics.........................................................................................................17
Check card status...............................................................................................................18
Reload a node with the current backup or a previous one.................................................20
Resetting a card..................................................................................................................21
 2 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

Introduction to moshell
Moshell is an UNOFFICIAL Ericsson tool (although in new versions of OSS, an official
Moshell version called AMOS is already included). You could say that it is a command-
based Element Manager, which is usually much faster and more efficient than using
EMAS itself. This document attempts to show the use of some basic moshell commands,
which can facilitate the monitoring work in Orange.

To connect to a node using moshell:

1) Inside the OSS, open a console and go to the /home/crorz1/moshell directory for
zones 1 and 5, and /home/crorz2/moshell for zone 2.
2) Once in the corresponding directory, use the command ./moshell NODE_NAME.

Moshell uses its own database to translate node name to IP address, so it is possible that
there are nodes that have not been included in that database. Therefore, if there is no
moshell contact NODE_NAME, you should always try ./moshell IP_ADDRESS.

Once connected to the node, it will be necessary to run the lt all command to load all the
objects.

Introduction to moshell commands

First of all, we are going to try to define the concepts of objects and proxy, in the
MOshell environment. Moshell works on Java, and each of the node elements (RNC,
RBS), whether related to SW or HW, is identified with an object. Each object has a name
and a number that identifies said object. This number is called the proxy.

203 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp2

proxy object name

204 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp1

On the other hand, in moshell we talk about children and parents, where the child is
defined on its parent (in emas it will be the relationship between the objects that appear
 3 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

when displaying a parent object), in moshell it can be seen given that the children contain
the string that defines the parent, as illustrated in the following example:
289 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1 PARENT

290 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbchDeviceSet=1 SON

Once we have clarified the difference between the name and the proxy of the object, and
between parents and children, we can define a series of moshell commands, which are the
most used, and which can be used with practically all objects.

lt + object type: command used to load objects, that is, so that we can list them and
execute actions on them. The most appropriate thing is, once connected to the node, to
load all the objects. To do this, use lt all.

pr + object proxy or object name: command used to list an object, that is, to list a
specific object. For example:
080717-181140_9999CX> pr pp3

081006-17:10:11 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
MO Proxy
===================================================================================
202 Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp3
===================================================================================
Total: 1 MOs

080717-181140_9999CX> pr 202

081006-17:10:31 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
MO Proxy
===================================================================================
202 Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp3
===================================================================================
Total: 1 MOs

lpr + object name: command used to list an object and all its children. Below we
illustrate the difference between using pr and lpr (pr shows all objects that contain tx, and
lpr shows these objects and their children):
OFFLINE_080717-181140_9999CX> pr tx

081006-17:12:47 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
MO Proxy
===================================================================================
96 Equipment=1,RfCable=RU1_3_TX
289 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1
309 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1
345 Equipment=1,RfCable=RU1_2_TX
412 Equipment=1,RfCable=RU1_1_TX
520 SwManagement=1,Repertoire=RBS_TXB
700 SwManagement=1,SwAllocation=RBS_TXB
===================================================================================
 4 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

Total: 7 MOs

OFFLINE_080717-181140_9999CX> lpr tx

081006-17:12:50 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
MO Proxy
===================================================================================
96 Equipment=1,RfCable=RU1_3_TX
289 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1
290 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbchDeviceSet=1
291 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,HsDbchDeviceSet=1
292 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DpProgram=CXP9011041/6_R1U01
293 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,EScDeviceSet=1
294 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1
295 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=6
296 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=5
297 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=4
298 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=3
299 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=2
300 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=1
301 Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,EDbchDeviceSet=1
309 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1
310 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,HsDbchDeviceSet=1
311 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,EScDeviceSet=1
312 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,EDbchDeviceSet=1
313 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1
314 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=6
315 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=5
316 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=4
317 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=3
318 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=2
319 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=1
320 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DpProgram=CXP9011041/6_R1U01
321 Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbchDeviceSet=1
345 Equipment=1,RfCable=RU1_2_TX
412 Equipment=1,RfCable=RU1_1_TX
520 SwManagement=1,Repertoire=RBS_TXB
700 SwManagement=1,SwAllocation=RBS_TXB
===================================================================================
Total: 31 MOs

st + proxy object or object name: command used to list a stateful object, that is, to view
an object and its state. For example:
080717-181140_9999CX> st pp3

080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
Proxy Adm State Op. State MO
===================================================================================
202 0 (LOCKED) 0 (DISABLED)
Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp3
===================================================================================
Total: 1 MOs

080717-181140_9999CX> st 202

081006-17:21:19 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
Proxy Adm State Op. State MO
===================================================================================
 5 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

202 0 (LOCKED) 0 (DISABLED)

Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp3
===================================================================================
Total: 1 MOs

lst + object name: command used to list an object and all its children with state. Below
we illustrate the difference between using st and lst (st shows all objects containing
stateful tx, and lst shows such objects and their stateful children):

080717-181140_9999CX> st tx

081006-17:22:23 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
Proxy Adm State Op. State MO
===================================================================================
289 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1
309 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1
===================================================================================
Total: 2 MOs

080717-181140_9999CX> lst tx

081006-17:22:55 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

===================================================================================
Proxy Adm State Op. State MO
===================================================================================
289 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1
290 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbchDeviceSet=1
291 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,HsDbchDeviceSet=1
293 0 (DISABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,EScDeviceSet=1
294 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1
295 0 (DISABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=6
296 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=5
297 0 (DISABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=4
298 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=3
299 0 (DISABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=2
300 1 (ENABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=1
301 0 (DISABLED) Equipment=1,Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1,EDbchDeviceSet=1
309 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1
310 0 (DISABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,HsDbchDeviceSet=1
311 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,EScDeviceSet=1
312 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,EDbchDeviceSet=1
313 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1
314 0 (DISABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=6
315 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=5
316 0 (DISABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=4
317 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=3
318 0 (DISABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=2
319 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbccDeviceSet=1,DbccDevice=1
321 1 (ENABLED) Equipment=1,Subrack=1,Slot=10,PlugInUnit=1,TxDeviceGroup=1,DbchDeviceSet=1
===================================================================================
Total: 24 MOs

get + proxy object or object name: command used to view the attributes of an object.
For example:
OFFLINE_080717-181140_9999CX> get pp2

081006-17:24:48 OFFLINE_080717-181140_9999CX.log 7.1a RBS_NODE_MODEL_K_2_3 stopfile=/tmp/1092

 6 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

===============================================================================================
==================
203 Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp2
===============================================================================================
==================
E1PhysPathTermId pp2
administrativeState 1 (UNLOCKED)
aisReporting false
availabilityStatus 0 (NO_STATUS)
crc4Mode 2 (AUTOMATIC)
degDegM 7
degDegThr 30
idlePattern 0 (UNDEFINED)
lineNo 2
loopback 0 (NONE)
operationalState 1 (ENABLED)
rdiReporting false
reservedByImaLink ImaGroup=1-1-ima1,ImaLink=2
reservedBySync
reservedByTraffic
shutDownTimeout 1800
userLabel
===============================================================================================
==================
Total: 1 MOs

bl+ proxy object or object name: command used to block an object that can be blocked
(not all objects can be blocked).

lbl+ object name: command used to lock an object that can be locked and all its children
that can also be locked (not all objects can be locked). SPECIAL ATTENTION WITH
THIS COMMAND SINCE WE CAN BLOCK OBJECTS THAT WE DO NOT WANT
TO BLOCK.

Cell Lock Sequence

Connect with moshell to the RNC from which node B hangs.

1) Determine the cells we want to block: lst UtranCell=Cell_Name (the number that identifies the
sector is not included so that all of them are listed).

MAD01R01> lst UtranCell=010139

080924-20:32:36 10.192.7.140 7.1a RNC_NODE_MODEL_G_5_30 stopfile=/tmp/28659
================================================================================
===
Proxy Adm State Op. State MO
================================================================================
===
33985 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393
33996 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Pch=1
33998 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Hsdsch=1
33999 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Hsdsch=1,Eul=Eul_0101393
 7 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

34005 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Fach=1

34010 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Rach=1
34032 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392
34039 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Hsdsch=1
34040 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Hsdsch=1,Eul=Eul_0101392
34048 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Fach=1
34051 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Pch=1
34068 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Rach=1
34079 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391
34102 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Fach=1
34109 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Rach=1
34115 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Pch=1
34120 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Hsdsch=1
34121 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Hsdsch=1,Eul=Eul_0101391
================================================================================
===
Total: 18 MOs

2) Cell Lock

Cells can be locked in two different ways:

-Using the Proxy (number that identifies the MO): bl Proxy (cells are blocked)
For example in this case

080924-20:32:36 10.192.7.140 7.1a RNC_NODE_MODEL_G_5_30 stopfile=/tmp/28659

================================================================================
===
Proxy Adm State Op. State MO
================================================================================
===
33985 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393
33996 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Pch=1
33998 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Hsdsch=1
33999 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Hsdsch=1,Eul=Eul_0101393
34005 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Fach=1
34010 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Rach=1
34032 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392
34039 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Hsdsch=1
34040 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Hsdsch=1,Eul=Eul_0101392
34048 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Fach=1
34051 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Pch=1
34068 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Rach=1
34079 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391
34102 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Fach=1
34109 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Rach=1
34115 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Pch=1
34120 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Hsdsch=1
34121 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Hsdsch=1,Eul=Eul_0101391

MAD01R01>bl 33985 34032 34079

 8 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

-Using the string that identifies the MO (Simpler): lbl UtranCell=Cell_Name ( both cells
and channels will be blocked)

For example in this case

MAD01R01> lbl UtranCell=010139

Cell unlock sequence

Connect with moshell to the RNC from which node B hangs.

1) Determine the cells we want to unlock: lst UtranCell=Cell_Name (the number that identifies
the sector is not included so that all of them are listed).

2) Cell unlocking

Cells can be unlocked in two different ways, as in the case of blocking, but it is advisable to do so
by using the string: ldeb UtranCell=Cell_Name ( both cells and channels will be unlocked)

For example in the previous case

MAD01R01> ldeb UtranCell=010139

Iub blocking sequence

Connect with moshell to the RNC from which node B hangs.

1) Determine cells that we want to block: lst Iub_nameIub

MAD01R01> lst Iub_010139

080924-20:52:19 10.192.7.140 7.1a RNC_NODE_MODEL_G_5_30 stopfile=/tmp/28659

=========================================================================
==========
Proxy Adm State Op. State MO
=========================================================================
==========
21205 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391
21206 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NodeSynchTp=2
21207 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NodeSynchTp=1
21210 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NbapCommon=1
 9 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

21211 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NbapDedicated=1

=========================================================================
==========
Total: 5 MOs
2) Iub block
You can block the Iub or related objects (Sync and Nbap) in two different ways:

-Using the Proxy (number that identifies the MO): bl Proxy

For example in this case

Proxy Adm State Op. State MO

=========================================================================
==========
21205 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391
21206 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NodeSynchTp=2
21207 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NodeSynchTp=1
21210 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NbapCommon=1
21211 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391,NbapDedicated=1
=========================================================================
==========
Total: 5 MOs

MAD01R01>bl 21206 21207 21210 21211

-Using the string that identifies the MO (Simpler): lbl Iub_nameIUb ( both cells and
channels will be blocked)

For example in this case

MAD01R01> lbl Iub_010139

Iub unlock sequence

Connect with moshell to the RNC from which node B hangs.

1) Determine cells that we want to unlock: lst Iub_nameIub

MAD01R01> lst Iub_010139

080924-20:52:19 10.192.7.140 7.1a RNC_NODE_MODEL_G_5_30 stopfile=/tmp/28659

=========================================================================
==========
Proxy Adm State Op. State MO
=========================================================================
==========
21205 1 (ENABLED) RncFunction=1,IubLink=Iub_0101391
 10 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

21206 1 (LOCKED) 1 (DISABLED) RncFunction=1,IubLink=Iub_0101391,NodeSynchTp=2

21207 1 (LOCKED) 1 (DISABLED) RncFunction=1,IubLink=Iub_0101391,NodeSynchTp=1
21210 1 (LOCKED) 1 (DISABLED) RncFunction=1,IubLink=Iub_0101391,NbapCommon=1
21211 1 (LOCKED) 1 (DISABLED) RncFunction=1,IubLink=Iub_0101391,NbapDedicated=1
=========================================================================
==========
Total: 5 MOs

2) Iub block

Cells can be unlocked in two different ways, as in the case of blocking, but it is advisable to do so
by using the string : ldeb Iub_nameIUb ( both sync and Nbap will be unlocked)

For example in this case

MAD01R01> ldeb Iub_010139

Alarm checking
In both rbs and rnc, alarms can be queried using moshell. To do this, use either the al
command (brief description) or the wing command (detailed description).
MADB0139> al

080924-21:07:17 10.161.9.89 7.1a RBS_NODE_MODEL_J_5_17 stopfile=/tmp/13758

Connecting to 10.161.9.89:56834 (CorbaSecurity=OFF, corba_class=2, jarcorb=R1D01,
jacsec=R1D01, jacoms=R51EL18)
Trying file=/home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-210705_13728/ior13728
Resolving the alarm service in WHO...
Simple Alarm Client initialized...
Starting to retrieve active alarms
Nr of active alarms are: 1
=========================================================================
=======================
Sever Specific Problem Cause Mo-Reference
=========================================================================
=======================
Warn Auto-Configuration of Board Not Possible unavailable Subrack=1,Slot=20
>>> Total: 1 Alarms (0 Critical, 0 Major)

MADB0139> wing

080924-21:08:19 10.161.9.89 7.1a stopfile=/tmp/13865

Fetching IOR file...Done.
Connecting to 10.161.9.89:56834 (CorbaSecurity=OFF, corba_class=2, jarcorb=R1D01,
jacsec=R1D01, jacoms=R51EL18)
Trying file=/home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-210731_13840/ior13840
Resolving the alarm service in WHO...
Simple Alarm Client initialized...
 11 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

Starting to retrieve active alarms

Nr of active alarms are: 1
=========================================================================
=======================
Sever Specific Problem Cause Mo-Reference
=========================================================================
=======================
Warn Auto-Configuration of Board Not Possible unavailable Subrack=1,Slot=20

Alarm Id : SubNetwork=mxulrn_R,SubNetwork=MAD01R01,MeContext=MADB0139_1
Event Time: Jun 19, 2008 5:21:12 AM
Perceived Severity: Warning
Managed Object Class: Slot
Managed Object Instance :
SubNetwork=mxulrn_R,SubNetwork=MAD01R01,MeContext=MADB0139,ManagedElement=1,E
quipment=1,Subrack=1,Slot=20
Specific Problem : Auto-Configuration of Board Not Possible
Probable Cause: unavailable
Additional Text:
Acknowledged by:
Acknowledgment Time: Oct 15, 1582 1:00:00 AM
Acknowledgment State: 2
System DN : SubNetwork=mxulrn_R,SubNetwork=MAD01R01,MeContext=MADB0139
Notification Id: 2
Additional Info:
>>> Total: 1 Alarms (0 Critical, 0 Major)

It is also possible to list an alarm history, both in the RNC and in the RBS. Lga command.
MADB0139> lga

080924-21:13:23 10.161.9.89 7.1a stopfile=/tmp/13865

Trying password from ipdatabase file: /home/rfcadmin/reelfma/moshell//sitefiles/ipdatabase...
Startdate=19661031.151320, Enddate=20080925.191326
........Get /c/logfiles/alarm_event/ALARM_LOG.xml
/home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-210731_13840/
alarmLog13865.xml ... okay
=========================================================================
===========================================
Timestamp (UTC) S Problem Cause MO-reference
=========================================================================
===========================================
2007-08-24 11:14:06 AL M IMA Group Insufficient Links local_node_transmission_error
ImaGroup=1-2-ima1
2007-08-24 11:15:02 AL M System Clock in Holdover Mode replaceable_unit_problem
Synchronization=1
2007-08-24 12:14:02 AL M TimDevice_RadioClockIsNotStable loss_of_synchronisation
Subrack=1,Slot=4,PlugInUnit=1,YourDeviceGroup=1,TimDeviceSet=1,TimDevice=1
2007-08-24 14:28:54 AL M PDH Loss of Signal loss_of_signal
Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm=pp1
2007-08-24 14:29:47 AL * PDH Loss of Signal loss_of_signal
 12 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm=pp1
2007-08-24 14:29:49 AL * IMA Group Insufficient Links local_node_transmission_error
ImaGroup=1-2-ima1
2007-08-24 14:29:49 AL * NodeSynchTp_ConnectionLost loss_of_signal
Iub=Iub_0101391,NodeSynchTp=1
2007-08-24 14:30:58 AL * System Clock in Holdover Mode replaceable_unit_problem
Synchronization=1

Check cell status

Connect with moshell to the RNC from which node B hangs and use the command lst
UtranCell=Cell_Name (the number that identifies the sector is not included so that all of them are
listed). This command will list both the UtranCell and the different channels so that you can check
if all the channels are up, ENABLED status (Pch, Fach, Rach, Hsdch –HSDPA channel-, Eul –
EUL channel).

MAD01R01> lst UtranCell=010139

080924-21:17:45 10.192.7.140 7.1a RNC_NODE_MODEL_G_5_30 stopfile=/tmp/28659

=========================================================================
==========
Proxy Adm State Op. State MO
=========================================================================
==========
33985 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393
33996 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Pch=1
33998 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Hsdsch=1
33999 1 (UNLOCKED) 1 (ENABLED)
RncFunction=1,UtranCell=0101393,Hsdsch=1,Eul=Eul_0101393
34005 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Fach=1
34010 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101393,Rach=1
34032 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392
34039 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Hsdsch=1
34040 1 (UNLOCKED) 1 (ENABLED)
RncFunction=1,UtranCell=0101392,Hsdsch=1,Eul=Eul_0101392
34048 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Fach=1
34051 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Pch=1
34068 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101392,Rach=1
34079 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391
34102 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Fach=1
34109 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Rach=1
34115 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Pch=1
34120 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,UtranCell=0101391,Hsdsch=1
34121 1 (UNLOCKED) 1 (ENABLED)
RncFunction=1,UtranCell=0101391,Hsdsch=1,Eul=Eul_0101391
=========================================================================
==========
Total: 18 MOs
 13 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

You can also check the status of all cells and channels hanging from a given RNC. To do this,
you must connect to said RNC using moshell and use the str command. This command will list
the status of all cells and channels, showing those with problems at the bottom, where 0 means
DISABLED, 1 ENABLED and L LOCKED.

MAD01R01> str

080924-21:23:55 10.192.7.140 7.1a RNC_NODE_MODEL_G_5_30 stopfile=/tmp/28659

Logging to file: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/

strLog28659
0% ~50% ~100%
.................................................................................................
Log close: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/
strLog28659

Following 170 sites are up:

----------------------------------------------------------------------------------------------------
MOD IUBLINK CELLNAMES CFRPHEM1 CFRPHEM2 CFRPHEM3 CFRPHEM4 CFRPHEM5
CFRPHEM6 ICD12 ATMPORTS
----------------------------------------------------------------------------------------------------
1 Iub_0100811 010081-1/2/3 111111 111111 111111 11111
1 Iub_0100831 010083-1/2/3/4/5/6 1111 1111 1111 111111 111111 111111 11111
1 Iub_0102141 010214-1/2/3 111111 111111 111111 11111
1 Iub_0102571 010257-1/2/3 111111 111111 111111 11111
1 Iub_0103281 010328-1/2/3 111111 111111 111111 11111
1 Iub_0103311 010331-1/2/3 111111 111111 111111 11111
1 Iub_0103431 010343-1/2/3 111111 111111 111111 11111
1 Iub_0103441 010344-1/2/3 111111 111111 111111 11111
1 Iub_0104401 010440-1/2/3 111111 111111 111111 11111
1 Iub_0104911 010491-1/2/3 111111 111111 111111 11111
1 Iub_0104921 010492-1/2/3 111111 111111 111111 11111
1 Iub_0108161 010816-1/2/3 111111 111111 111111 11111
1 Iub_0109001 010900-1/2/3 111111 111111 111111 11111
1 Iub_0109071 010907-1/2/3 111111 111111 111111 11111
1 Iub_0109431 010943-1/2/3 111111 111111 111111 11111
12 Iub_0161431 016143-1/2 111111 111111 11111
12 Iub_0164101 016410-1/2/3 1111 1111 1111 11111
12 Iub_0164151 016415-1/2 1111 1111 11111
----------------------------------------------------------------------------------------------------

Following 13 sites are totally or partially unavailable:

----------------------------------------------------------------------------------------------------
MOD IUBLINK CELLNAMES CFRPHEM1 CFRPHEM2 CFRPHEM3 CFRPHEM4 CFRPHEM5
CFRPHEM6 ICD12 ATMPORTS
----------------------------------------------------------------------------------------------------
2 Iub_0101671 010167-1/2/3 000000 000000 000000 10011
2 Iub_0160061 016006-1 L0000L 10011
3 Iub_0958121 095812-1/2/3 LLLLLL LLLLLL LLLLLL 10011
4 Iub_0101611 010161-1/2/3 L0000L L0000L L0000L 10011
 14 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

4 Iub_0138201 013820-1/2/3 LLLLLL LLLLLL LLLLLL 1LLLL

4 Iub_0960141 096014-1/2/3 L0000L L0000L L0000L 10011
5 Iub_0135511 013551-1/2/3 L000LL L000LL L000LL 1LLLL
5 Iub_0958201 095820-1/2/3 1111LL 1111LL 1111LL 11111
7 Iub_0104391 010439-1/2/3 L00000 L00000 L00000 10011
8 Iub_0104241 010424-1/2/3 L0000L L0000L L0000L 11111
9 Iub_0101541 010154-1/2/3 L00000 L00000 L00000 11111
10 Iub_0106401 010640-1/2/3 L000 L000 L000 100LL
12 Iub_0960991 096099-1 L0000L 10011
----------------------------------------------------------------------------------------------------

Cell availability: 491 of 526 cells are up (93.3 %)

Site availability: 170 of 183 sites are fully operational (92.9 %)
Unlocked Cell availability: 491 of 497 unlocked cells are up (98.8 %)

Check if a node is carrying traffic

There are several ways to check whether a node B has traffic.

On the one hand, by connecting through moshell to the RBS , you can check the number of
radiolinks established in each sector with the get command. noOfradioLinks

MADB0139> get . noOfradioLinks

080924-21:33:37 10.161.9.89 7.1a RBS_NODE_MODEL_J_5_17 stopfile=/tmp/13865

=========================================================================
========================================
MO Attribute Value
=========================================================================
========================================
Sector=3,Carrier=1,RadioLinks=1 noOfRadioLinks 6
Sector=2,Carrier=1,RadioLinks=1 noOfRadioLinks 3
Sector=1,Carrier=1,RadioLinks=1 noOfRadioLinks 13
=========================================================================
========================================
Total: 3 MOs

Additionally, you can check how many UEs (users) are connected to a certain RNC and with what
type of call. To do this, connect via moshell to the RNC and use the uer command.

For example:

MAD01R01>uer

080924-21:35:33 10.192.7.140 7.1a RNC_NODE_MODEL_G_5_30 stopfile=/tmp/28659

Trying password from ipdatabase file: /home/rfcadmin/reelfma/moshell//sitefiles/ipdatabase...
 15 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

Checking available boards on nodes...

Logging to file: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/

boLog28659
...........................................................................................................................................................
...........................................................................................................................................................
.................................................................................................................................
Log close: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/
boLog28659

Logging to file: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/

boLog28659
...........................................................................................................................................................
...........................................................................................................................................................
....................................................................................................................
Log close: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/
boLog28659

Created following board-groups: all, allp, mp, bp, tu, coremp, ommp, scx, sccpmp, aal2ap,
aal2ncc, aal2cpsrc, aal2rh, xp, ranapmp, rnsapmp, mod, modact, modsb, mod<sr>, mod <mod>,
cc, cc<sr>, cc<mod>, dc, dc<sr>, dc<mod>, pdr, pdr<sr>, pdr<mod>, spb,
spb<sr>, spb<mob>.
>>> Type "bp" to view available board-groups and "bp <group>" to view group contents.

Created following MO-groups: cc[0-9]dev, dc[0-9]dev, pdr[0-9]dev.

>>> Type "mp" to view available MO-groups and "pr <group>" to view group contents.

Logging to file: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/

uerLog28659
...........................................................................................................................................................
..................................
Log close: /home/sv/moshell_logfiles/logs_moshell/tempfiles/20080924-201814_28611/
uerLog28659

Printing all active UeContexts (max 50 per module).

==============================================================================================
===========================
MOD IMSI/TMSI CTXT SRNC CommCh RL1 RL2 RL3 DCdev CoreNetId UERC UERC_LABEL (ESTAB_CAUSE)
==============================================================================================
===========================
1 214034245074503 322 101 109431:5654 0019sp4 P 2143 16 PS Interactive 384/HS - HS-DSCH
(14:origHighPrioSignaling)
1 214033245114539 800 101 100811:483 100811:483 100811:482 0019sp3 C 2143 2 Speech (0:origConversational)
1 214033445142877 1173 101 103311:1982 0020sp3 P 2143 4 Packet RACH/FACH (8:termBackground)
1 214036145148885 574 101 103281:1963 103281:1963 103281:1964 0021sp4 C 2143 2 Speech (0:origConversational)
1 214034258132802 400 101 109431:5655 109431:5655 0019sp3 C 2143 2 Speech (0:origConversational)
1 214031003075032 368 101 103311:1981 103311:1981 0020sp4 C 2143 2 Speech (0:origConversational)
1 214034258270302 598 101 144661:26791 101681:1004 0019sp3 C 2143 2 Speech (0:origConversational)
1 214033343608152 388 101 144661:26793 144661:26793 144661:26792 0020sp4 C 2143 2 Speech
IMSI

16 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

(5:termConversational)
1 214032458088690 636 101 100811:483 100811:483 0021sp3 C 2143 2 Speech (5:termConversational)
1 214032046032875 12 101 100811:483 100811:482 0020sp3 C 2143 2 Speech (0:origConversational)
1 214034045271652 866 101 144661:26791 0019sp2 P 2143 4 Packet RACH/FACH (2:origInteractive)
1 214031045226029 18 101 103431:2055 0019sp4 P 2143 15 PS Interactive 64/HS - HS-DSCH (10:IRAT_cellReselection)
1 214034245004146 1026 101 103311:1982 103311:1982 143371:26018 143371:26017 0020sp4 P 2143 15 PS Interactive
64/HS - HS-DSCH (14:origHighPrioSignaling)

This command provides information about the Imsi, the cell or cells to which the user is
connected, and the type of traffic being carried.

1 214034245074503 322 101 109431:5654 0019sp4 P 2143 16 PS Interactive 384/HS - HS-DSCH

IMSI Cell (cellId) Traffic type

 17 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

View traffic statistics

You can check traffic statistics on an RNC. To do this, connect to the RNC using moshell, and
execute the pmr command. Using the pmr command will create statistics for the previous 15
minutes. If you want to check a longer time frame, you can use pmr –m number_hours , which
will show statistics of the last number_hours (the more hours, the longer this command will take,
and if the number of hours is very high, the RNC may not have data).
Once the command is executed, a menu will appear with different types of statistics.

MAD01R01> pmr -m 1

1) RNC Node Traffic Performance

2) RNC Node Traffic Performance, Hour by Hour
3) RNC Node Traffic Performance, ROP by ROP
4) RNC Module Traffic Performance
5) RNC MP Load
6) RNC MP Load, Hour by hour
7) RNC UtranCell RRC Performance
8) RNC UtranCell Speech Performance
9) RNC UtranCell CS Data Performance
10) RNC UtranCell PS Data Performance
11) RNC UtranCell Throughput and NrUsers
12) RNC UtranCell HSPA Performance
13) RNC UtranCell IRAT Performance
14) RNC UtranCell Soft HO Performance
15) RNC UtranCell Uplink RTWP/RSSI
16) RNC Worst 20 UtranCells for RRC Failure Rate Contribution
17) RNC Worst 20 Utrancells for Speech RRC Failure Rate
18) RNC Worst 20 Utrancells for PS Failure Rate
19) RNC Worst 20 Utrancell for Speech RAB Setup
20) RNC Worst 20 Utrancell for PS RAB Setup
21) RNC Worst 20 UtranCells for Speech Drop Rate Contribution
22) RNC Worst 20 UtranCells for Old HS Drop Rate Contribution
23) RNC Worst 20 UtranCells for Soft HO Failure Contribution
24) RNC Worst 20 UtranCells for High Uplink RTWP/RSSI
25) RNC IubLink RRC Performance
26) RNC IubLink Speech Performance
27) RNC IubLink CS Data Performance
28) RNC IubLink PS Data Performance
29) RNC IubLink Soft HO Performance
30) RNC IurLink Drop Rate
31) RNC AtmPort RRC Performance
32) RNC AtmPort Speech Performance
33) RNC AtmPort CS Data Performance
34) RNC AtmPort PS Data Performance
35) RNC UtranCell Availability Report, Hour by Hour
36) RNC UtranCell RAB failure breakdown
37) RNC Q.Aal2 Setup Performance (Aal2Ap)
38) RNC Q.Aal2 Setup Performance (Aal2Ap) per QoS Class
 18 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

39) UeRc BLER

Enter the report number followed by a piping command if postprocessing required.
Eg "1" (no piping) or "3 | sort +2n". Type "m" to view the menu, type "x" to exit.
Your Choice:

The most useful option for Orange supervision will be

7) RNC UtranCell RRC Performance
25) RNC IubLink RRC Performance

, which shows the success and failure percentage of RRC connections (RRC CONNECTION
SETUP), and serves to identify sleeping cells (those with a very high RRC connection failure
percentage).

Check card status

You can check the status of the cards (slot, LED status, temperature, serial number) with the
cabx command.
 19 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

There is also the bo command, which is faster, but only shows the card and the slot.
 20 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

Reload a node with the current backup or a previous

one
If you want to restart a node, the best thing to do is to check the backups it contains. To
do this, use the cvls command.
 21 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

When restarting the node, it will do so with the backup defined as startable. In the
previous case you will do it with the cv called
OP_CXP9011610%1_R12G06_080922_0729.

To change the startable backup it will be done with the cv set Backup_name command. For
example:

MADB0139> cv set Fi_CXP9011610%1_R12G06_080619_0231

To restart the node acc 0 restart will be used. There are different types of restart: cold, warm,
refresh,… One or the other will be used depending on the type of problem.

The final script for node reboot is:

>cvls
>cv set cv_name_to_load
>acc 0 restart

On the other hand, if we want to make a backup before restarting the node (for example because
it seems to us that the one on the node is very old, we must keep in mind that the changes made
are not saved until a backup is made), we will have to use the cvms command. That is to say:
>cvms cv_name

Resetting a card.
Sometimes a single card reset is required. To do this, first you must find the string that identifies
the card (you can find out the subrack and slot using the cabx and bo commands).
 22 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

APN indicates the

slot

SMN indicates the subrack. SMN 0 Port. Some radiant system devices are connected to
corresponds to mainSubrack or node cards, and are accessible through this port.
subrack 1. 1 to subrack 2, etc…

For example in the previous case

CATB3115> lst Equipment=1,Subrack=1,Slot=17,PlugInUnit=1

 23 of 23
Prepared (also subject responsible if other) No.

EEM/GMW/ejandia
Approved Checked date Rev Reference

24/09/08 PA2

080924-22:34:32 10.161.9.89 7.1a RBS_NODE_MODEL_J_5_17 stopfile=/tmp/13865

=========================================================================
==========
Proxy Adm State Op. State MO
=========================================================================
==========
300 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=17,PlugInUnit=1

To restart the card, the Proxy or the string that identifies the MO will be used. That is, it can be
executed in two ways:

- acc Proxy manualRestart (in this case acc 300 manualRestart ).

- lacc string_MO manualRestart

(in this case lacc Equipment=1,Subrack=1,Slot=17,PlugInUnit=1$ manualRestart ).

Another way to reset the card is by connecting to it, with the lhsh command. As seen in the
previous paragraph, the position of the card can be seen with the cabx command. That way, to
connect to the card and restart it it would be

>lhsh XXYY00 reload

, where XX corresponds to the SMN (00, 01, 02,…) and YY to the slot (01,02,03,…). The default
reboot (without specifying any parameters) is warm, although it can be changed by adding the
refresh, cold, or coldwtest parameters.

If you want to restart any of the radiant system devices connected to node cards, and accessible
through a port, you can normally use the command

>lhsh XXYY00/port_A_dev_BB restart