You are on page 1of 78

AMOS Operation

Contents

 MoShell overview
 MOM overview
 Overview on commands and syntax for MO and PM
handling
 Overview on COLI commands, file transfer
Overview on MoShell

 MoShell is a suite of tools for O&M of CPP-based


nodes.
 CPP is the Connectivity Packet Platform on which are
based the following nodes: RNC, RBS, MGW, RXI.
 All these nodes have in common the CPP part which
handles functionality for core and transport.
 The application part differs between these nodes and
handles the functionality that is specific for each of
these nodes.
Overview on MoShell
APPLICATION

RNC application RBS application MGW application

CPP
Core Area Transport Area (NCH)
- Equipment handling - Physical line termination
- SW loading (E1,T1,STM-1,etc)
- System upgrade - ATM, IMA
- Internal switching - ATM Adaption Layers (AAL2,
- O&M AAL5, UniSAAL, NniSAAL,
- Processor redundancy Q.AAL2)
- Error recovery - Network Synchronization
- Trace and debug support - Ethernet and IP
- Restart handling - SS7 (MTP3, M3UA, SCCP)
- File system
- Operating system
Overview on MoShell

The following O&M services can be accessed in the node:


 OSE shell (a.k.a COLI): provides a set of commands on each individual
board. Mainly geared towards trouble-shooting, not intended for
configuration.
 File service: for transfer of files between to/from the node (SW files,
logfiles, ROP files, etc)
 MIB (Managed Information Base): the database containing all the MOs
(Managed Objects) of the node. MOs are used for configuration and
trouble-shooting of the resources in the node.
 Scanners: the database containing all the Performance Management
Scanners of the node. Scanners are used for defining the contents of the
Performance Measurements (i.e. to specify which counters/events shall
be logged in the ROP files).
Overview on MoShell

 MOs are identified using 3 ways:


– RDN relative distinguished name
– LDN local distinguished name
– FDN full distinguished name
 MOs are addressed in 6 ways mainly:
– All
– Proxy ids
– Link handler
– Mo group
– Board group
– Mo filter
AMOS Operation
Overview
Warning

Advanced Managed Object Scripting (AMOS) is an


extremely powerful command line utility that may cause
substantial damage to a Network Element. It is the
operator’s responsibility to ensure that they have read and
fully understood all AMOS command descriptions and that
they have proficient training in the usage of AMOS
commands before attempting to execute any commands
against Network Elements.

DANGER
What is AMOS or Moshell ?
 AMOS is a feature of OSS-RC which is available from OSS-
RC 5.3. It has been developed as the customer version of
Moshell. The AMOS and Moshell commands are the same,
except the lab commands and internal ericsson commands
which are not available in AMOS.
Eg
 Some Ericsson internal commands: fget, fset, facc - Not available in AMOS
 Some Lab Commands: pset, pcr, pdeb, pbl, pdel - Not available in AMOS

 AMOS can be used to connect to different CPP Nodes


mainly the MGW, RNC and NodeB’s.
Services provided by AMOS / Moshell
AMOS is a text-based Operation and Maintenance (O&M) client providing access
to the following services:
 Alarm Service (AS) - can be used to retrieve the list of alarms currently
active on each Managed Object (MO).
 Configuration Service (CS) -is used to read and change configuration data.
Configuration data is stored in MO attributes.
 File Transfer (FTP/HTTP) – to download and upload files and directories to
and from a Network Element (NE).
 Inventory Service - The Inventory Service allows AMOS to get a list of all
Hardware (HW) and Software (SW) defined on the NE.
 Log Service (LS) - allows AMOS to save a log of certain events such as
changes in the configuration data, alarms raising and ceasing, NE or board
restarts etc.
 Notification - allows AMOS to subscribe and receive notifications from the
Network Elements. This informs AMOS about parameter and alarm state
changes in the MOs.
 Performance Measurement Service (PM) -is used to monitor statistics
scanners or event filters.
Starting AMOS from OSS
Step Comment Action
1 In OSS Common This opens the AMOS main
Explorer command shell.
Workspace Menu, NB: Not working in our case
select OSS team to check
<tools> -> <AMOS>
2 Run the UNIX command This will launch AMOS against
amos <node name> the specified Network Element.

Alternatively
2 Run the UNIX command This will launch AMOS against
amos <node ip the specified IP Address.
address>
Starting AMOS from OSS

You need Citrix, and IP Address of OSS (10.1.28.6), Username and


Password and permission to Launch AMOS under user rights.
Starting AMOS from Winfiol
› Connect to OSS using the OSS IP Address 10.1.28.6
› Run the UNIX command
amos <node ip address>
eg.
amos 10.201.4.4

› Other telnet tools can be used ie …


– SecureCRT
– Putty
Same method as winfiol
Stopping AMOS

Step Comment Action


1 In AMOS main command This stops AMOS running.
shell run the command q,
quit, exit or bye
Ipdatabase
 The ipdatabase is a file where you can store for each node of
the network:
– nodename (arbitrary)
– ipaddress or dns name
– password (optional)

 The ipdatabase file should be saved as


/opt/ericsson/amos/moshell/sitefiles
 To view the naming convention and contents of the file use
UNIX commands
cat ipdatabase
Or
more ipdatabase
Starting AMOS from data in IPdatabase
› Connect to OSS using the OSS IP Address 10.1.28.6
› Run the UNIX command
amos mgw01
grambire@mhuas01> amos mgw01
› __ __ ____ _____
› /\ | \/ |/ __ \ / ____|
› / \ | \ / | | | | (___
› / /\ \ | |\/| | | | |\___ \
› / ____ \| | | | |__| |____) |
› /_/ \_\_| |_|\____/|_____/
› OSS Framework for MoShell-9.0c

› $amosrb_pid = 27292

› Checking ip contact...OK

› HELP MENU : h
› BASIC MO COMMANDS : m
› OTHER MO COMMANDS : n
› OTHER COMMANDS : o
› PM COMMANDS : p
› QUIT : q

› MGW01> lt all
AMOS Operation

Concepts
AMOS Concepts
 Unix Command
 Supported Function Key
 Command Piping
 Regular Expression
 Managed Object Model
 MO Tree and MO Naming Conventions
 Services Layer
 User Specific Settings
Basic Unix command
 pwd/!pwd print the working directory
 ls/!ls list files
 ls [options][directory][file]
 -a List all files including hidden file starting with ‘.‘
 -l (-l is character not one) shows file or directory, size,
modified date and time, file or folder name and owner of
file and it’s permission.
 -t sort output by modification time
 --help displays a help screen summarizing the command
syntax
 mkdir mkdir <directory> ... create directories
 ls ls [-la] [<dirname> ...] list files
 cd cd [<dirname>] change the working directory
 mv mv <source> ... <destination> rename/move files
 rm rm [-f] <filename> ... remove files
 rmdir rmdir [-f] <directory> ... remove (empty) directories
 cp cp <source> ... <destination> copy files
Supported function keys

Ctrl+F or right arrow Move forward one character


Ctrl+B or left arrow Move backward one character
up arrow Previous command in history buffer
down arrow Next command in history buffer
backspace Delete one character backward
Ctrl+A or home Go to beginning of line
Ctrl+E or end Go to end of line
Ctrl+U Erase all characters
backward
Ctrl+K Erase all characters forward
Ctrl+INSERT Copy to clipboard
Shift-INSERT Paste from clipboard
Command Piping
The Piping command is used to filter an expect string in the
output.

Examples:

MHMGW08> cabx | grep ET


Shows all ET boards installed in the the MGW08.

MHMGW08 > lh mesc te log read|grep "gcpErrorCode=500"


Shows all gcpErrorCode=500 on the mesc board groups
Regular Expressions

. Match any single character


* Match 0 or more occurrences of the previous character
[] Match a character or range of characters inside the
brackets
[^] Do NOT match character or character range inside the
brackets
| Or
^ Match from the beginning of the string
$ Match from the end of the string
! Negation; do not match
% Match in reverse order
() Group regular expressions
Regular Expressions Example

a* Match a or aa or aaa
.* Wildcard that matches 0 or more occurrences of
any character
[a-z] Matches all letters from a to z
[abe] Matches letters a, b and e
[^3] Matches any character but not 3
3|5|6 Matches 3 or 5 or 6
^a.*4$ Matches a string beginning with a and
finishing with 4, with any character in the middle.
cell(11|23|45) Group regular expressions together using
brackets this matches cell11 or cell23 or cell45
Using Regular Expressions
MTMGW04> lpr ES-2-3-1-ima25.*vc102

091102-10:52:24 192.168.202.1 7.1j RNC_NODE_MODEL_K_9_16 stopfile=/tmp/25820


===================================================================================
Proxy MO
===================================================================================
2580 TransportNetwork=1,AtmPort=ES-2-3-1-ima25,VplTp=vp1,VpcTp=1,VclTp=vc102
===================================================================================
Total: 1 MOs

MTMGW04> lpr ES-2-3-1-ima25.*vc10[0-4]

091102-10:54:53 192.168.202.1 7.1j RNC_NODE_MODEL_K_9_16 stopfile=/tmp/27517


===================================================================================
Proxy MO
===================================================================================
2208 TransportNetwork=1,AtmPort=ES-2-3-1-ima25,VplTp=vp1,VpcTp=1,VclTp=vc100
2209 TransportNetwork=1,AtmPort=ES-2-3-1-ima25,VplTp=vp1,VpcTp=1,VclTp=vc102
===================================================================================
Total: 2 MOs
Service Layer
 Management Information Base (MIB)
MIB

ManagedElement=1
Equipment=1
Subrack=MAIN
MOClass MO Identity
Slot=1
RDN: Slot=2
Slot=2
LDN: ManagedElement=1,Equipment=1,Subrack=MAIN,Slot=2

Subrack= CTRL
Slot=1

Slot=2

TransportNetwork=1
AtmPort=MSE3-21-2

The Management Information Base (MIB) is the set of all existing MO’s
at any given time. The MOs are organised in a hierarchical tree.
Connecting to MIB
 To be able to access the node’s MIB, you need to first run the
command “lt all”.
 The command “lt all” reads the list of all MOs currently existing in the
MIB and their LDN (Local Distinguished Name).
MGW01> lt all

130920-17:06:15 10.201.4.4 9.0c stopfile=/tmp/10596


Checking MOM version...MGW_NODE_MODEL_B_16_24
Parsing MOM (cached): /home/grambire/moshell/jarxml/MGW_NODE_MODEL_B_16_24.xml.cache.gz ......................Done.
.Fetching IOR file...Done.
Connecting to 10.201.4.4:56834 (CorbaSecurity=OFF, corba_class=2, java=1.7.0_21, jacoms=R74G10, jacorb=R74D01, jacsec=R61HH01)
**** Welcome to the Simple Mo Browser (version 3.0)!
Trying file=C:/cygwin/home/grambire/moshell_logfiles/logs_moshell/tempfiles/20130920-170607_7108/ior7108
**** Test Construction OK
****

$mobrowser_pid = 12164

Connected to 10.201.4.4 (SubNetwork=ONRM_RootMo_R,SubNetwork=MGW,MeContext=MHMGW01,ManagedElement=1)


Connected to 10.201.4.4 (SubNetwork=ONRM_RootMo_R,SubNetwork=MGW,MeContext=MHMGW01,ManagedElement=1)
Last MO: 4933. Loaded 4933 MOs. Total: 4934 MOs.

MHMGW01>
MO tree and naming conventions
Relative Distinguished Name (RDN)
 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=ATM-4-1

 AtmPort is the MO Class, ATM-4-1 is the MO identity.


MO tree and naming conventions
LDN - Local Distinguised Name

 This is used to uniquely identify an MO within a node.


 The LDN shows the hierarchy above the MO, within the
Managed Element’s MO tree.
Example:
ManagedElement=1,TransportNetwork=1,AtmPort=ATM-4-1

Example
ManagedElement=1
ManagedElement=1,Equipment=1
ManagedElement=1,Equipment=1,Subrack=MAIN
ManagedElement=1,Equipment=1,Subrack=MAIN,Slot=4
ManagedElement=1,Equipment=1,Subrack=MAIN,Slot=4,PlugInUnit=1
ManagedElement=1,Equipment=1,Subrack=MAIN,Slot=4,PlugInUnit=1,Program=DbAgent
MO tree and naming conventions

FDN - Full Distinguished Name


 This is used to uniquely identify an MO within a
network (used by RANOS/CNOSS/OSS-RC).
 Example:
SubNetwork=ONRM_RootMo,SubNetwork=MGW,MeContext=
MTMGW04,ManagedElement=1
FDN - Full Distinguished Name
Managed Object Class (MOM)
Managed Object Class (MOM)
MO Attributes (States Attributes)

 Operation State
– Enable
– Disable
 Administrative State
– Locked
– Unlocked
– Shutting_down
 Availability Status
– No_Status
– In_Test
– Failed
– Power_Off
– Off_Line
Example Managed Object Class

State Attributes

Specific Attributes
Common Attributes
Managed Object Model
 That’s a model need to be followed when dealing with MGW
nodes.
When MOM says anything, we always have to obey.
 The MOs are organised in a hierarchical tree.
MIB

ManagedElement=1

Equipment=1
Subrack=MAIN
N
MOClass MO Identity
Slot=1

Slot=2 RDN: Slot=2


LDN: ManagedElement=1,Equipment=1,Subrack=MAIN,Slot=2

Subrack=1

Slot=1

Slot=2

TransportNetwork=1
AtmPort=ATM-4-1
Managed Object Model MOM
Below is the list of MO’s with their related description:
MO Name Description
Ds0Bundle Allows you to specify timeslots for an E1 to use for speech or
signalling.
TdmTermGrp Specifies a Ds0Bundle to use for Speech
Mtp2TpItu Specifies a Ds0Bundle to use for Narrowband signalling
Mtp3bSrs Specifies a signalling point code to a destination, one
Mtp3bSrs must be created for every node the M-MGw wants
to signal to.
Mtp3bSls Specifies a signalling link set, which contains all the signalling
links towards a specific destination. One signalling link set
must be created for every node directly connected to the M-
MGw, which it wants to talk to
Mtp3bSr Creates a signalling route for a destination, which specifies
what signalling link set can be used to reach the specified
destination
Mtp3bSlItu Creates an ITU signalling link (broadband or narrowband) to a
destination
Vmgw Used to terminate the signalling from the MSC to the
MGw,allowing the MSC to request and release resources from
the M-MGw
Managed Object Model MOM

MO Name Description
VplTp Specifies the VPI for an ATM connection
VpcTp Is used to terminate/originate the VPI definition from the VplTp
VclTp Specifies the VCI for an ATM connection and also terminates the
VCI
Aal5TpVccTp Specifies an AAL5 (signalling) termination for ATM
NniSaalTp Terminates a broadband signalling defined by an Aal5TpVccTp
Aal2Ap Specifies a termination for AAL2, this is used to analyse any
signalling for AAL2 coming in or out of the M-MGw
AtmTrafficDescriptor Used to specify the number of cells/second that can be
used for an ATM connection(used by VplTp& VclTp)
Browsing MOM from AMOS
View the MO description:

MHMGW01> mom vcltp

130920-16:41:46 10.201.4.4 9.0c MGW_NODE_MODEL_B_16_24 stopfile=/tmp/3660

##################################################################################
MO Class Attributes/Actions
##################################################################################
VclTp
VclTpId,atmTrafficDescriptorId,availabilityStatus,counterActivation,externalVci,operationalState,reservedBy,userLabel
eteLoopBack
Virtual Channel Link Termination Point
Represents the termination of an external VC link in the node.
A maximum of 10 000 instances of this MO can be configured in a node.
The VC service category cannot be configured to UBR+ or CBR, if the parent VplTp has the service category set to UBR.
The service category is set by the attribute serviceCategory in AtmTrafficDescriptor.
Disturbances: Changing lower layer attributes may affect O&M connectivity, if they are part of the O&M connection.
Browsing MOM from AMOS
View the attributes and actions description:

MHMGW01> mom vcltp eteLoopBack

130920-16:48:40 10.201.4.4 9.0c MGW_NODE_MODEL_B_16_24 stopfile=/tmp/3660

#############################################################################################################################
#######
MO Class Action ReturnType Parameters
#############################################################################################################################
#######
VclTp eteLoopBack boolean 0
------------------------------------------------------------------------------------------------------------------------------------
Inserts end-to-end loopback cell into the VC. This cell is looped back by the corresponding far-end VCC endpoint.
true - the cell looped back by far-end is successfully received
false - the far-end did not answer or cell looped back by far-end is not received
This action can be used during troubleshooting to check if the VC is faulty.
Transaction required: Yes
ReturnType: boolean
************************************************************************************************************************************
MO services
CONFIGURATION MANAGEMENT SERVICE

Operation Purpose Related Moshell Protocol


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

GetAttribute To read the value of one or more attribute(s) get, hget, pget, st,, etc.

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

SetAttribute To change the value of an attribute (provided set, bl, deb


it is not restricted or readonly)

CreateMO To create an MO cr

DeleteMO To delete an MO del, rdel


MO services, cont
FAULT MANAGEMENT SERVICE

Operation Purpose Related Moshell command(s) Protocol

Get Alarms List active alarms al


corba (FM)
Cell status Cell availability Str (RNC Commands)
Managed Object Model

 The MOM is a document describing for each particular


node SW version:

– All the different types of MOs (MO classes)


– Attributes contained in each MO class
– Relationships (parents/children) between the MO classes.
– Actions supported by each MO class

 The MOM can be found in ALEX


mom online help
MHMGW08> mom tdmterm pcmSystemNr

130923-11:47:30 10.201.4.29 9.0c MGW_NODE_MODEL_B_15_115 stopfile=/tmp/1608

############################################################################################################################
########
MO Class Attribute Type Flags
############################################################################################################################
########
TdmTermGrp pcmSystemNr long restricted,noNotification,mandatory
------------------------------------------------------------------------------------------------------------------------------------
The unique identifier for the Time Division Multiplexing (TDM) termination group. Together with the timeslot number it is used to create the termination
identity.
Range: 0 to 2097151
************************************************************************************************************************************
MHMGW08> mom tdmterm

130923-11:47:01 10.201.4.29 9.0c MGW_NODE_MODEL_B_15_115 stopfile=/tmp/1608

##################################################################################
MO Class Attributes/Actions
##################################################################################
TdmTermGrp
TdmTermGrpId,administrativeState,availabilityStatus,cdvt,ds0BundleMoRef,mccMode,mobileAccessConn,nrMode,operationalState,partialFill,pcmS
ystemNr,reservedBy,routeParamGrpMoRef,userLabel
Contains a group of TDM Terminations corresponding to a CPP Ds0Bundle.
Note: During the MO creation the administrativeState atribute value should be "LOCKED" when specified.
----------------------------------------------------------------------------------
AMOS Operation
Command Line
al Command
*******************************************************
al[atkc] [-a|-u <alarm_id>] [ | <unix cmds>]
*******************************************************
Print the list of active alarms.
Acknowledge/Unacknowledge an alarm.
It is possible to combine several options, eg: al, ala, altk, alatk, altkc, etc.
al: active alarm list is printed in overview format, only four fields are shown per alarm.
ala: same as al, but the full detailed list is added underneath the overview table.
alt: same as al, but the time field is added to the table and the alarms are sorted
chronologically.
alk: same as al, but the list is separated in two parts, one for the unacknowledged
alarms, and one for the acknowledged alarms.
alc: same as al, but each alarm is displayed in CSV format and all fields are shown
for each alarm.
Note: in alt and alk, the severity field is shortened to one character:
C for Critical
M for Major
m for minor
w for warning
l+/l-/l? Command

*******************************************************
ll+[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 logfile is chosen.
* l- is for closing the logfile.
* l? is for checking if a logfile is currently open.
pr/lpr Command

*******************************************************
pr/lpr [<moGroup>|<moFilter>|<proxy(s)>]
*******************************************************
Print MO LDNs and proxy ids for all or part of the MO tree
currently loaded in moshell.
MO(s) whose LDN/RDN match the pattern will be
operated upon. If the command starts with "l" then the
pattern will match against the LDN. If the command
doesn't start with "l", then the pattern will match against
the RDN.
get/lget Command

*******************************************************
get/lget [<moGroup>|<moFilter>|<proxy(s)>|all]
[<attribute-filter>|all] [<value-filter>]
*******************************************************
Read CM/FM attribute(s) from MO(s).

Note: to read PM attributes, use pget/lpget.


This command fetches one or several attributes from one
or several MO's.
st/lst Command

 *******************************************************
 st/lst [<moGroup>|<moFilter>|<proxy(s)>|all] [<state-
filter>]
 *******************************************************
 Print state of MOs ( operationalState and
administrativeState when applicable).
kget Command

 “kget” is identical to “get” except that the output has


slightly different format in order to allow importing of
data in some external tools like MCOM. “kget” should
mainly be used when taking MO dumps.
 Before kget you need to do “lt all”.
u+/u- Command

*******************************************************
u+[s]/u-/u?/u! [<file>]
*******************************************************
Handling of undo mode (for set/bl/deb/acc commands). Can be used
for generation of MO scripts as well.

u+ To start the "undo mode"


u+s To start the "simulated undo mode"
u- To stop the "undo mode" (or simulated undo mode)
u? To check if "undo mode" is active or not
u! To convert moshell command files to trun/emas format or undo
logfiles to command files, see below for more info.
set/lset Command
*******************************************************
set[m][c]/lset[m][c] <moGroup>|<moFilter>|<proxy(s)> <attribute>
[<value>]
*******************************************************
Set an attribute value on one or several MO's.
MTMGW04> set Aal2PathVccTp=ATM-4-1-MTMGW09 continuityCheck false

130923-15:58:24 10.202.4.10 9.0c MGW_NODE_MODEL_B_15_115 stopfile=/tmp/6720


Set continuityCheck on following 12 MOs ?
===================================================================================
594 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC34
595 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC35
596 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC36
597 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC37
598 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC38
599 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC39
600 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC40
601 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC41
602 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC42
603 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC43
611 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC33
612 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC32
===================================================================================
Set continuityCheck on 12 MOs. Are you Sure [y/n] ? y
bl[s]/lbl[s] Command
*******************************************************
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).
Without the "s" option, the resource is locked immediately.
bl[s]/lbl[s] Command
MTMGW04> bl Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC34
130923-16:04:16 10.202.4.10 9.0c MGW_NODE_MODEL_B_15_115 stopfile=/tmp/6720
Block following 1 MOs ?
===================================================================================
594 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC34
===================================================================================
Block 1 MOs. Are you Sure [y/n] ? y

============================================================================================================
Id MO administrativeState Result
============================================================================================================
594 Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC34 0 >>> Set.
============================================================================================================
Total: 1 MOs attempted, 1 MOs set

MTMGW04> bls Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC35


130923-16:04:34 10.202.4.10 9.0c MGW_NODE_MODEL_B_15_115 stopfile=/tmp/6720
Soft-Block following 1 MOs ?
===================================================================================
595 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC35
===================================================================================
Soft-Block 1 MOs. Are you Sure [y/n] ? y

============================================================================================================
Id MO administrativeState Result
============================================================================================================
595 Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC35 2 >>> Set.
============================================================================================================
Total: 1 MOs attempted, 1 MOs set

MTMGW04>
deb/ldeb Command
*******************************************************
deb/ldeb <moGroup>|<moFilter>|<proxy(s)>
*******************************************************
Unlock MO(s).
Works by setting the administrativestate to 1.

MTMGW04> deb Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC35


130923-16:12:10 10.202.4.10 9.0c MGW_NODE_MODEL_B_15_115 stopfile=/tmp/6720
Deblock following 1 MOs ?
===================================================================================
595 TransportNetwork=1,Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC35
===================================================================================
Deblock 1 MOs. Are you Sure [y/n] ? y

============================================================================================================
Id MO administrativeState Result
============================================================================================================
595 Aal2PathVccTp=ATM-4-1-MTMGW09-STM1-VP7-VC35 1 >>> Set.
============================================================================================================
Total: 1 MOs attempted, 1 MOs set
acl/lacl Command
*******************************************************
acl/lacl <moGroup>|<moFilter>|<proxy(s)>|all [<action-
filter>]
*******************************************************
Lists available MO actions.
 View all restart actions:
>> acl all restart
 View all actions except "restart" and "eteloopback"
>> acl all [^(restart)(eteloopback)]
 View all actions related to the synchronisation MO
>> acl sync
acc/lacc Command

*******************************************************
acc[e]/lacc[e] <moGroup>|<moFilter>|<proxy(s)>|all
<action>
*******************************************************
Execute an MO action.
If the action needs parameters, these will be prompted
for. If an action contains parameters,the value of each
parameter has to be entered at each prompt. If no
value is entered, the action is aborted.
acc/lacc Command
1.Restart a board:
 acc 001400 restart - Same as:
 lacc subrack=ms,slot=14,pluginunit=1$ restart
2.Restart the node:
 acc 0 manualrestart
3.List the IP routing table
 acc ip listroutes
4.Perform End-To-End loopback on VclTp MOs:
 lacc AtmPort=GMSE1-19-1-ima4 eteloopback
5.Add a new synchronization reference:
 acc sync addSyncRefResource
AMOS Operation
Performance Management
pmr Command

*******************************************************
pmr[agf] [-r <report(s)>] [-m <minushours>] [-p
<plushours>] [-s <startdate>[.<starttime>]] [-e
<enddate>[.<endtime>]
*******************************************************
Produce PM KPI reports, based on counter values in
statistics ROP files and formulas in CPI documentation.
Performance Measurements

 A few PM Commands:
 Operation Related moshell command(s)
 List Scanners and Event Filters pst
 View Scanner contents pgets
 Read instantaneous counter value pget
 Fetch and parse Statistics ROP files pmr/pmx
 Fetch and parse Event ROP files pme

 All the PM commands can be seen by typing “p” in moshell prompt


 A description of the counters can be seen by using the command
“pmom”
AMOS Operation
HW/SW Configuration
inv Command

Complete HW/SW inventory. Includes information about


RPUs, licensing, JVM, devices, XPs, ISL, etc.

This command performs a complete HW/SW inventory


via the MO interface. All SW including JVM, RPU, and
Device SW (spm,dsp,fpga) is shown. Licensing
(features and capacity) as well as overview of the ISL
links is also shown.
bo/bp Command

Manage board groups that can be used for running COLI


commands on multiple boards.
Note: in RNC, the "bo" command also creates a number
of default MO groups "ccXdev", "dcXdev", "pdrXdev",
where X is the module number.
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.
cab Command

*******************************************************
cab[slxradgtmeh] [ | <unix cmds>]
*******************************************************
Display of miscellaneous COLI printouts relating to hw,
sw, restarts, leds, cpu load, errors, disk/ram usage

The command cabslxrdgm will give the maximum


amount of information.
cab Command option

Options:
cab : prints MP/BP HW info and led status, MP temperature, and
coreMgr status
cabt : same as cab but without the temperature
cabx : same as cab plus led and hw info for the XP boards (eg: TMA,
MCPA, Fans, etc.)
cabl : same as cab but plus MP/BP processor load
cabs : same as cab plus list of programs running in all MP/BP
cabr : prints all MP/BP restarts. Abnormal restarts are shown in red.
caba : prints only abnormal MP/BP restarts.
cabd : print disk usage. Disks that are getting over a certain limit will
appear in color. The limit can be defined in cabview file.
cabg : print MP/BP HW errors (e.g. faulty disk, faulty RAM, etc).
cabm : print MP/BP RAM memory usage.
cabe : print MP/BP added T&E trace conditions.
SMN-APN-ERN
Link Handler value (LNH)

SMN APN ERN


(SwitchModuleNumber (AtmswitchPortNumber (ExecutionResourceNumber
=Subrack Position) =Slot Position) =Processor Position)

02 14 00
APN value:
The APN value is identical to the slot number except for the
last slot on the right which has APN=00.
Example in a 28-slot subrack:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Slot Number

S S
C C
B B

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 0 APN
ERN value:

The ERN value is always 00 for the MP/BP processor


and 1 to 99 for the device processors.
GMP V2 (BC 206)

SWITCH MODULE
SUBRACK NAME NUMBER

1 MAIN 00
2 ATM 01
5 GMSE1 57
6 GMSE2 89
GMP V3 (BC 3024)

SWITCH MODULE
SUBRACK NAME NUMBER
1 MAIN 00
2 MODULE1 01
3 MODULE2 65
4 MODULE3 73
5 MODULE4 89
6 MODULE5 97
GMP V3 (BC 40XX)
SWITCH MODULE
SUBRACK NAME NUMBER

1A MSE1 25
1B CONTROL 01
1C MSE2 33
2B MAIN 00
2C MSE3 49
Configuration Version handling
Configuration Version (CV) handling.
Cvls: List CV’s
Cvmk: make local CV
Example: cvmk CVname identification comment
Cvms: make remote CV
Example: cvms CVname identification comment
Cvset: setstartable
Example: cvset CVname
Cvrm: remove
Example: cvrm CVname
Restart Ranks
HW Data in own memory
Rank T&E logs HW reset SW reload Data in CLI container Domain
test segment

Hot Preserved No No Conditional Preserved Cleared 4

Warm Preserved No No Conditional Cleared Cleared 1, 2, 3, 4

Yes on MP/BP
Not necessarily
Refresh Preserved No Yes Cleared Cleared 1, 2
on
FPGA/DSP/etc.

Cold Cleared Limited Yes Yes Cleared Cleared 1, 2, 3

ColdWTest Cleared Yes Yes Yes Cleared Cleared 1, 2, 3


Restart commands from MO interface

Board restart using the MO LDN


MTMGW04> acc main,slot=9,pluginunit=1$ manualrestart
...<cut>...
Board restart using a board group
MTMGW04> acc sccmp manualrestart
...<cut>...
Logs Handling
*******************************************************
lg[aevsyuoldhmircfx] [-l <logdirectory|logfile>] [-m <minustime>] [-p <plustime>] [-s
<startdate>] [-e <enddate>] [|<unixcmds>]
*******************************************************
Fetching and/or processing of node logs (alarm, event, availability, system, etc)
Example: lgasevomr
a: parse alarm log
s: parse system log
e: parse event log
v: parse availability log
o: parse command log
m: merge the different logs together
r: refetch the logs from the node.

lga -s 20130901.0000 -e 20130905.1300


show alarm log entries between the dates 20130901 00:00 and 20130905 13:00
Checking Restart Information

MTMGW04> lgvsm
MTMGW04> lgd !Node restart times!
MTMGW04> lhsh 001400 llog –l !board restarts logs!
MTMGW04> cabr !all board!