Ericsson Element Management

Element Manager Application Subsystem

As previously mentioned EMAS is a java-based tool used to carry out

element management of a number of different Node areas. It is

composed of a number of different views including:

� Radio View

� ATM View

� IP View

� Equipment View

� Signalling View

The new Element Manager tool (EM) includes a number of new

views, including licensing and transport stack relations

EMAS Radio View

Right pane shows

information, (channels

and cell relations in

this case)

Radio View gives

information on the

various cells,

channels and cell

relations in the

node. It also

shows Iub links

for the RNC

EMAS ATM View

Right pane shows

information, (ATM

ports, VCs, VPs ect in

this case)

ATM View gives

an overview of all

ATM transport

resources in the

node, including

ports, VCs, VPs,

AAL termination

points, IMA

groups

EMAS Equipment View

Right pane shows

information, (Boards and

their slots in this case)

Equipment view

gives an overview

of equipment in

the node, including

boards, subracks,

fan units, power,

and external

equipment for

Node-Bs

New Element Manager (EM)

EM is a new tool which combines and adds to the functionality of

the old EMAS and Object Explorer tools. It is:

� Model-based, and as such assumes some knowledge of the

MOM

� Is launched from a special installation package provided by

Ericsson. Can also be launched from OSS-RC 6.2 and newer

� Allows for user-defined, and some pre-defined views. Folders to

hold and create these views are automatically created on the users

PC with the installation of the launcher software

� Nodes that are UTRAN P7 or newer, require the use of new EM

Launching New Element Manager New software package allows for easy launch:

Ip address of the node EM is to be

launched for

EM Main Window

Tab titles include:

� Table (attribute information)

� MO Properties (each MO’s attributes)

� Description (describing each object)

MOM based

modelling is

used

View menu

also includes

user-defined

views

Launching ALEX From EM

Pressing F1 launches CPI

in the “ManagedElementData” Managed

Object the path to CPI used is set, using the

“documentServerAddress” attribute

EM Licensing View Graphically organises the licenses in the node

License title

Right hand pane

gives further

information on

each license,

including the

service it enables

EM ATM Relations View

Useful for configuration

troubleshooting as we can view faulty

parts of the transport stack at a glance

Stack shows

how the lower

layer ATM MOs

relate

(including phy

ports)

New view showing the ATM or IP transport stack

Can also be

launched for IP

User Defined Views in EM

View is stored on PC, and

so can be used with

different nodes

These are saved on the users PC in the form of XML files

Folder

automatically

created with EM

SW download

Sample User-Defined View

No attributes shown in right

hand pane

The top level

MO shown is

”Managed

Element”

The view is called

“Basic_view”

Altogether two

layers of MOs are

shown

XML File for This View

The top level

MO selected is

”Managed

Element”

A File for a More Detailed XML View

The top level

MO selected is

”Subrack” Three layers of

MOs to be

displayed

Specific

Attributes will

be viewed

Command Line Interface Tool As mentioned before the CLI tool can be used to access the node

resources, such as the filing system

� We access the tool by opening a terminal window from the OSS

desktop (or alternatively via the Node Status Analyser tool)

� Telnet into the node from the terminal window using the “telnet”

command followed by the node IP address

� Once in the node standard commands apply, including: “cd” to

change directory and “ls” to list contents

� More specific commands include “lhsh” to jump to a board, and

“vii” to get information on the status of the LEDs on the board. (See

handout with useful CLI commands for usage)

Node Command Line Interface Tool

NCLI is a MOM-based tool, and is

accessed from the regular CLI

� After telnetting in launch NCLI by

keying in “ncli”

� Restricted number of similtaneous sessions one any one node (2-5)

� Treats the node MOM as a UNIX filing

system, allows for jumping between MOs

� Actions may be performed only on the

MO the user is on

� Caution is advised as there are no safeguards against hazardous actions, such as locking the O&M board

“man” gives a list of commands

Advanced MO Scripting (AMOS) Tool

CLI-based tool that allows for MOM-based text

support

� Similar to the Ericsson MOshell tool

� Client not located on node, user must ensure

to upload MIB from node with each use

� More flexible than NCLI as it allows for filter-

matching of MO names, and displays all MO

information (attributes)

� Tasks include: “get” to get values “set” to

set attribute value, “create” to create an MO

and “delete” to delete one

� Commands starting with an “l” and “r” match by local and relative distingushed name

Chapter

Concludes