AMOS.pdf

AMOS

Advanced MO Scripting

Fraz [email protected]

Ericsson Confidential AMOS Overview 2008-04-152

Managed Object Model

• The Basic building block of a Managed Object Model (MOM) is an MO.

• MO represents a resource in the node, either a “physical resource” such as plug-in unit or a “logical resource” such as a software program or a protocol

• Whether it’s a physical or a logical resource, there are parameters associated with MO called MO attributes. An MO can be configured by setting values for the MO attributes.

They can be categorized as following

• Configuration Management: Stored Permanently e.g. administrative state

• Fault Management: Not stored permanently e.g. availability status

• Performance Management: Not stored permanently e.g. pmNoReqDeniedAdm

MO Attributes


Managed Object Model – Managed Object Structure

• Each MO is identified by its “instance”.

• MOs are organized in a hierarchical structure. Top on the hierarchy is root MO, known by instance “ManagedElement”. This is the highest MO in the node.

ManagedElement=1

Equipment=1

TransportNetwork=1

Subrack=MS

Subrack=ES-1

Slot=18

Slot=19

AtmPort=MS-6-1

PlugInUnit=1

Program=dbmF pgaLoader


• The string at the left of the equality sign is known as MO Class and at the right is known as MO Identity.

• Classes can have more than 1 subclasses also known as Children.

• From previous example: ManagedElement, Equipment, Subrack etc. are classes and 1, 1 and MS are their identities respectively.

• Similarly ManagedElement=1 has a child called Equipement=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).

ManagedElement=1

Equipment=1Subrack=MS

Slot=19

PlugInUnit=1

Program=dbmFpgaLoader

Class Identity

Managed Object Model – Managed Object Identification


RDN (Relative Distinguished Name)

• RDN is used to identify an MO in relation to its nearest parent in the MO tree.

• It includes both MO Class and MO identity

• RDN is unique under its immediate parent, however there could be another MO instance with the same RDN under a different parent MO.

• Example: RDN of the lowest MO in above example is Program = DbmFpgLoader

LDN (Local Distinguished Name)

• LDN of an MO contains the MO classes and identities of all parents of that MO

• It is used to uniquely identify an MO within a Network Element.

• Example: LDN of the last MO is

ManagedElements=1, Equipment=1, Subrach=MS, Slot=19, PlugInUnit=1, Program=dbmFpgLoader

FDN (Full Distinguished Name)

• FDN is used to uniquely address each MO when a node is connected to a Network Management System such as OSS. It adds a network prefix in front of the LDN for this purpose.

Managed Object Model – MO Class and Identity


MO Object Model (Example 1)

• Following lists all the sub-classes of highest MO class: ManagedElement.

• Complete list of Classes with identities along with children and attributes can be found in Alex.



MO Object Model (Example 2)

• Following lists the complete parent tree and sub-classes of class UtranCell

• Example of the attributes of UtranCell would be accessClassBarredCs, primaryCpichPower, qQualMin, PmNoRrcCsReqDeniedAdm etc.



AMOS - Startup

• There are 2 ways to launch the AMOS tool.

1. WRAN Explorer: Tools AMOS

2. Right Click on the main screen Administration Shell Tool

Launching AMOS


• Logging Screen and prompt

AMOS - Startup


st6242@glne2cx2> h

st6242@glne2cx2> h <command>

To get a list of all commands

To get help on specific command

AMOS – Startup – Logging into RNC

• Moshell <RNC IP Address> command launches AMOS


Loading Managed Objects

After logging into RNC, a proxy table should be built with the Managed Objects. There are two commands that can be used to load Managed Objects:

Loading a proxy table with all MOs

> lt all

> lc all

Unloading all MOs

> lu all

AMOS – Basic RNC Commands

lt: lt stands for Load Managed Object types. ltc stands for Load Managed Object Types and their Children.

lc: lc command is for loading the LDNs of the children Managed Objects lying under a Managed Object or group of Managed Objects.


Loading all Managed Objects of a particular type

To load Managed Object of a particular type following command is used

> lt <motype>

Example

• > lt utrancell

Loading a subset of Managed Object types that have a particular value

To load Managed Object of a particular type following command is used

Examples

• Following loads all Untran Cells whose operational state attribute has a value of 0

> lt utrancell operationalstate==0

• Following loads all Untran Cells with Operational and Administrative state value of 0

> lt utrancell operationalstate==0 OR administrativestate==0

AMOS – Basic RNC Commands – Loading Managed Objects


To read the configuration and fault management (CM and FM) attributes from a managed object the get command is used.

Examples

• Following displays all CM and GM attributes of all UtranCells in an RNC

> get utrancell

• In order to display the attributes only for a specific MO e.g. SCCLU0221

> get utrancell=SCCLU0221

• Attributes of a sector can also be displayed

> get utrancell=SCCLU02217

• Displaying value of a specific attribute for all MOs

> get utrancell CPICH

AMOS – Basic RNC Commands – Reading Attributes


Examples (Cont.)

• Displaying value of a specific attribute

> get utrancell=SCCLU02217 CPICH

• Displaying value of a more than 1 attributes e.g. CPICH and qQualMin

> get utrancell=SCCLU02217 CPICH|qQualMin



Examples (Cont.)

• Displaying value of RNC level HO parameters



Examples (Cont.)

• Displaying status of “g” links



“set” can be used to change value of parameters

• In the example, CPICH power of a cell SCCLU02217 is being changed from 31.1 dBm to 31.0 dBm

> get utrancell=SCCLU02217 PrimaryCpichPower 310

AMOS – Basic RNC Commands – Changing Parameters


Following commands are used to print Managed Object Data that is currently loaded from the Network Element.

Printing Managed Objects

“pr” command is used to print MOs as following.

Examples

• Giving “pr” command only, prints all MOs currently loaded. If no Mos are previously loaded in an RNC, following commands will display list of cells

> lt utrancell

> pr

• To print all MOs with a specified RDN value, following command is used

> pr <RDN>

Example

> pr utrancell

AMOS – Basic RNC Commands – Printing Managed Object Data


Printing State of Managed Objects

“st” command is used to print the state of MOs as following.

• To print state of all UtranCell MOs

> st utrancell

• To print state of a particular UtranCell Mo

> st untrancell=SCCLU0221

• To print state of all Utrancells MOs starting with SCCLU

> st untrancell=SCCLU



• To print state of all disabled utrancell MOs

> st untrancell dis

• To print state of all disabled utrancell MOs

> st untrancell dis

• To print state of the channels in the cell

> lst untrancell=SCCLU02217


Printing State of Managed Objects (Cont.)


Printing Status of Cells, Links and Channels

To print the state of cells, Iubs and channels, one line per site, following command is used

Example:

• To print state of all UtranCell MOs

> str



• Using these commands are helpful when cells’ last digit doesn’t define the sector.

> st utrancell

The way output of “str” is displayed can be changed using “str1” or “str2” commands.


Printing Status of Cells, Links and Channels (Cont.)


The outputs from the following commands can be piped through external UNIX utilities like sort, grep, less or more

• To print an overview of all active alarms

> al

• To print an overview of all active alarms chronologically

> alt

AMOS – Basic RNC Commands – Alarm Handling

Example:


• To count no of specific type of alarm e.g. to count no. of Major alarms

> al | grep –c “Maj”

• To print the active alarm list with detailed information following command is used

> ala

• To print the active alarm list with acknowledged and unacknowledged alarms separately

> alk

AMOS – Basic RNC Commands – Alarm Handling


“pmom” or “pget” can be used to print list and description of PM counters

• Following command sequence can be used to print PM counters only for Utrancell class

> pmom utrancell

AMOS – Basic RNC Commands – PM Commands

Viewing All PM Counters for an MO


• PM KPI reports based on counters can be produced by using “pmr”. Following the command, a menu is printed, prompting the user to enter the chosen report.

• If the g switch is used (e.g. pmrg command) then all availabe reports are printed without prompting the user.

• In order to print description of a particular PM counter

> pmom pmTotNoRrcConnectReqCsSucc

Printing KPI reports



• 36 different reports for SC RNC have been defined as shown below



• Selecting “16” would print the top 20 offenders in Speech RRC failure. By default the time span is the last 1 hour.

• In order to see the statistics of the last “x” no. of hours, e.g. 3 hours

> pmr –m 3



• In order to see the statistics starting from 5 hrs ago and then 3 hrs from there on i.e. duration of 2 hrs

> pmr –m 5 –p 3

• The "-s" and "-e" options are used for specifying an absolute time span. The timestamp should be in the format yyyymmdd[.hhmm]

In order to print the report from 04/01/2008 to 04/03/2008

> pmr –s 20080401 –p 20080403


Displaying counter values

• In order to display counter values, “pmx” command is used.

Example: In order to display counters values for “total no. of CS RRC connection requests” for a particular sector, following command sequence is used

> pmx UtranCell=SCCLU00017 PmTotNoRrcConnectReqCs



Displaying counter values (Cont.)


• The pipe symbol “|” does not work for all AMOS post processed commands so the work around is to perform the following

1. l+

2. <run command>

3. l-

• Example is given on next slide

• By default the data returned by AMOS after executing a command on a Network Element is not stored. The storage of AMOS data may be achieved by using the “l+” and “l-” commands.

AMOS – Basic RNC Commands – Logging AMOS Data


Example

AMOS – Basic RNC Commands – Logging AMOS Data

• The path to the default log is always the same as in above example. Unix commands can be run on this log filea and it can be retrieved through FTP.


AMOS – Basic RNC Commands – Misc.

• “hi” command shows the previous used commands in that session


Fraz [email protected]

Date post:	30-Jan-2016
Category:	Documents
Upload:	zinou2009
View:	149 times
Download:	12 times

AMOS.pdf

Documents