3G OSS Tools Ericsson Huawei

3G OSS tools - overview Multivendor Program

For internal use only 1 © Nokia Siemens Networks

Document Info Title

OSS tools, Ericsson and Huawei 3G

Reference Target Group

NPO UTRAN

Technology

WCDMA, Ericsson and Huawei

Software Release

OSS 10, W10, RAN12

Service

Service Item Version

Ver. 1.0

Version Date

2 June 2011

Version

Date

Section

Comment

1.0

2 June 2011

All

First Draft


Contents  HUAWEI  M2000 Client  RNC LMT  NodeB LMT  ERICSSON  Common components  Technology-specific application suites


M2000 Client Introduction Topology management Network monitoring Performance management Configuration management Data management Software management Security management Log management Network tracing Task management


Introduction iManager M2000 is the most important Huawei tool for operation & maintenance of Huawei RAN. M2000 is a centralized management platform that can perform various operations including data configuration, alarm management, performance management and software management. M2000 follows the server-client concept. Server is centrally located in customer premises and is interconnected to various NE over IP network. It is normally running on Sun Microsystems servers and on Solaris operating systems together with Sybase as database. The M2000 client can be installed in a windows PC and requires only IP connectivity with M2000 server, correct firewall configuration and authentication user rights.

With M2000, we have a powerful, consistent, comprehensive and easy to use tool to perform basically all tasks related to operation & maintenance and most basic operations will be introduced in the following slides.


Topology management (1/2) The most basic feature of M2000 is the possibility to show visual representation and geographical location of all the NE of the network. We can enable this view by clicking:  Left click on “Topology”→ “Main Topology” With topology management we can:

• • • • •

View the location of each NE (RAN, CN, transmission) Quickly query alarms of NE View connection status of each NE Quickly query performance of NE

Quickly open LMT client of NE


Topology management (2/2) The GUI of topology management consists of 3 blocks:



Physical topology navigation: Provides a non-graphical representation of the hierarchy of NE in the network

 

Topology Tool Bar: Shortcuts to perform operations fast and accurate

Physical topology view: Provides the graphical view of the NE and facilitates the quick query functions Topology Tool Bar

Physical topology view Physical topology navigation


Network monitoring (1/2) Network monitoring is the M2000 suite that provides alarm management functionality and can be initiated by  Left click on “Monitor”→ “Browse Alarm List” With network monitoring we can:

• • • • • • •

View all NE alarms in real-time Acknowledge alarms View details alarm description and handling recommendations Filter alarms Export alarm data Handle user-defined alarms Create performance based alarms


Network monitoring (2/2) The GUI of topology management consists of 3 blocks:



Alarm list view: Provides a list of all the alarms full-filling filtering criteria, together with most important alarm information

 

Alarm details pane: Provided all details of the specific alarm entry Handling description: Provides the handling information and suggestions for the specific alarm

ID.

Alarm list view

Alarm details pane For internal use only 9 © Nokia Siemens Networks

Handling description

Performance management (1/5) Performance management is the M2000 suite that provides performance analysis functionality and can be initiated by menu “Performance” in M2000 menu bar:  Left click on “Performance” With network performance management we can:

• • • • • •

Apply KPI queries on specific objects and time segments Store performance counters for all NE Activate/De-activate counter reporting from NE Check integrity of measurement results Create alarms based on KPIs Create extended counters and KPIs


Performance management (2/5) Performance management is the M2000 works in interconnection with the NE. M2000 through a file interface collects the performance files from all NE every measurement period.

Both Measurement counters and measurement objects can be activated/de-activated within M2000. When M2000 collects all relative data, it has to filter them through a NE specific mediation software and then store the corresponding data into the Sybase database. All user queries applied through M2000 client are now processes in the Sybase database (performance database)


Performance management (3/5) The GUI for querying performance is enabled by:



Left click on “Performance” → “Query Result” → “New Query”

The parameter input pop up window consists of 5 blocks:



Measurement units pane: Provides a list with all the measurements units, grouped under measurement set under every different NE type. For every measurement unit selected, there correspond different counters and measurement objects to be queried



Object setting list: Provides a list with all possible measurement objects to be queried under specified measurement unit. We can double-click and select multiple objects



Counter setting list: Provides a list with all possible measurement counters to be queried under specified measurement unit. We can double-click and select multiple counters or KPIs



Other settings list: Provides a list with all other settings related to the query, like time segment, counter aggregation period, sorting method etc.



Selection list: Provides a view of all the measurement objects and measurement counters selected in the previous steps.


Performance management (4/5) Object setting list

Counter setting list

Other settings list

Measurement units pane

Selection list


Performance management (5/5) When the query is executed, we are able to view the query result in the “Query Result” window, which consists of 3 blocks:

 

Template list: Provides a list with all saved queries (templates) for automated or future use



Data pane: Provides all the data fulfilling the querying conditions

View option list: Provides with all possible options for visualizing the performance query result. We can select from table view, line chart and bar chart

Template list

View option list

Data pane


Configuration management (1/4) There are 2 different ways to view the configuration through M2000. One is the normal MML querying option and the other is the M2000 specific MIT (Management Information Tree) browser. We can enable this view by clicking:  Left click on “Maintenance”→ “MML command” and  Left click on “Configuration”→ “MIT Browser” With configuration management we can:

• • • • • •

Query configuration of each NE (RAN, CN, transmission) Change configuration of each NE Managing inventory data Starting NE LMT Staring CME Starting Telnet


Configuration management (2/4) The GUI of MML command consists of 5 blocks:



NE window: Provides all NE that support the MML command feature. Different NE types are grouped according to their software version



Navigation tree: Provides all MML for the specified NE, together with help functionality and search feature

  

Command output window: Provides the output of the executed MML command given by the NE Command display window: Displays the MML command and all related parameters

Command input window: Provides the GUI interface for creating the MML command according to the NE specifications


Configuration management (3/4)

Command output window NE window Command display window

Command input window Navigation tree


Configuration management (4/4) The GUI of MIT Browser consists of 2 blocks:



MIT: MIT is structured in a tree structure which is composed on the following layers: NE Type, NE, Management Object Class (MOC), Management Object (MO)



Object information: Displays the configuration information of the selected MO

MIT

Object information


Data management (1/2) With the data management feature of M2000 we are able to create backup in both M2000 and individual NE. We can enable this view by clicking:  Left click on “Maintenance”→ “Backup Management” → “System Backup” and  Left click on “Maintenance”→ “Backup Management” → “NE Backup”

With topology management we can:

• Take a backup of M2000 (full or incremental) • Take a NE backup


Data management (2/2) The GUI of MML command consists of 5 blocks:

  

NE window: Provides all NE that support the backup feature NE Backup list: Provides the full list of backup made for the selected NE Task list: Indicates the list with all backups made or planned to be performed for all NE

NE Backup list NE window

Task list


Software management (1/2) With the software management feature of M2000 we are able to perform remotely some important operations related to software upgrades in different NE. We can enable this view by clicking:  Left click on “Software ”→ “Browser”  Left click on “Software ”→ “NE File Transfer”  Left click on “License” With software management we can:

• • • • • •

Upload NE software to M2000 Download NE software from M2000 to NE Load/Activate/Confirm/Deactivate NE patches Activate/distribute RAN license Upload Data from NE to M2000 Get other files from NE like internal log files


Software management (2/2) The GUI of MML command consists of 5 blocks:

 

Navigation tree: Provides the list with all NE that support the software broswing feature



Task list: Indicates the list with all tasks made or planned to be performed for all NE

Content window: Contains the full list of all Software/Patches/Data/Logs for the selected NE stored in the M2000 server

Content window Navigation tree

Task list


Security management (1/2) With the security management feature of M2000 we are able to define the security policies for all users accessing either M2000 or each individual NE. Log management will be introduced in the following slides. We can enable security management features by clicking:  Left click on “Security”

With security management we can:

• • • • • • •

Perform centralized user management Define different authorities to different user accounts Create local NE user right and accounts

Support of SSL login and certificates Assign authorities in both M2000 level and NE level Create user groups to inherit user rights Monitoring user sessions


Software management (2/2) The GUI of the security management consists of 3 blocks:



Navigation tree: Provides the list with all users as well as user groups. Each one of those can be configured by the following tabs



User rights tab: Contains the full list of all command rights/NE access rights/rules and generally all authentication rights for the specified users or user group



Command group: Indicates the selection of different MML command groups to be assigned to the specified user or user group. This panel differs based on the NE

User rights tab

Command group Navigation tree For internal use only 24 © Nokia Siemens Networks

Log management (1/2) With the log management feature of M2000 we are able to monitor all operations performed in both NE and M2000. We can enable this view by clicking:  Left click on “System” → “Log Management” With log management we can:

• Record M2000 operation/security/system logs • Record NE operation/security/system logs • Automatic synchronizing NE logs


Log management (2/2) A depiction of a typical Log query (system log) can be found hereunder:


Network tracing (1/3) Network tracing is a new integrated feature in M2000. With this feature we are able to perform basic tracing functionality in both UE and cell level. A more detailed tracing functionality can be performed by the NE locally. We can enable traces by clicking:  Left click on “Monitor” → “Trace Collection Management”

With network tracing we can:

• • • • • •

Create standard/detailed UE trace Create standard/detailed cell trace Verifying UE performance

Handling VIP complaints Locating TAC/IMSI based problems Checking radio coverage of NodeB


Network tracing (2/3) The GUI of network tracing consists of 5 blocks:



Navigation tree: Displays all possible types of tracing functionality available in current M2000 version



Import/Export pane: Provides with information about all importing tracing files or exporting tracing

data



Operation button: Provides functionalities like starting/deleting/copying traces, as well as import/export procedures

 

Trace list: Displays all trace information for already open tracing items Shortcut menu: Provides a fast way to perform various actions after first selecting a specific trace


Network tracing (3/3)

Navigation tree


Import/Exp ort pane

Operation button

Trace list

Shortcut menu

Task management (1/3) Integrated task management is a feature of M2000 that allows the user to perform automated tasks and offers a great variety of solutions. We can enable tasks by clicking:  Left click on “Maintenance ” → “Task Management” With task management we can:

• Create one-time tasks or periodic tasks • Provides with database capacity management tasks, like performance data dump, alarm and log dump

• Provides tasks for exporting file interface for performance, configuration, logs, inventory and alarms

• Provides synchronization tasks for NE configuration data, NE logs, alarms and inventory • Provides other types of tasks like CME upload, NE backup, script execution, frequency scan


Task management (2/3) The GUI of network tracing consists of 4 blocks:



Navigation tree: Displays all possible types of tasks to be defined. We can select the appropriate tasks and edit its profile and features



Task result information panel: Provides the information about the task selected once it is finished

 

Button panel: We can use those buttons to provide with central management of the tasks

Task list: Displays all timing tasks that are currently on the server side with all detailed information. Different color in this list identifies different task state, like completed, suspended, active or idle


Task management (3/3)

Navigation tree


Task result information panel

Button panel

Task list



RNC LMT Introduction MML command window Alarm management Trace management Performance monitoring Device maintenance


Introduction Local Maintenance Terminal (LMT) is considered as the first level of support for operation & maintenance in Huawei RNC. In RAN12 and latest versions, LMT doesn’t require local installation but is a web-based version. Nevertheless, some LMT tools are available also offline (LMT offline tools). Both online and offline functionality of LMT will be shown in the following slides. In order to connect to LMT, all we need is an IP connectivity with the RNC, proper configuration of the firewall and authentication user rights. Each LMT window refer to one and only one RNC, and this is exactly why with LMT we can not perform centralized operation & maintenance, but only local (for 1 NE)


MML command window (1/3) MML command window is the most basic functionality of the RNC LMT. With this we are able to execute all authorized commands to the NE and get corresponding feedback. We can enable tasks by clicking:  Left click on “MML” tab

With MML command window we can:

• • • • • •

Execute RNC configuration commands Execute RNC maintenance commands Rollback functionality

Undo/Redo functionality Run MML commands in batches Apply configuration commands in online/offline mode


MML command window (2/3) The GUI of MML command window consists of 5 blocks:



Common Maintenance tab: Displays the RNC response to the MML command previously executed. This can be either the reply to a query MML command or a execution feedback to a configuration command.

 

Operation Record tab: Displays MML commands already runned

Help Information tab: Displays the help information provided by Huawei to the MML command in use. There we can find detailed parameter explanation and suggestions.



Manual editing area: Provides the possibility to copy & paste & execute directly MML commands once we know the exact syntax of it. This area can also be used for a small batch of MML commands



Command Input box: Provides a GUI interface to facilitate correct syntax of MML commands. Using this box, we can correctly build the MML commands of our choice and directly execute the in the live network


MML command window (3/3) Common Maintenance tab

Operation Record tab

Help Informatio n tab

Manual editing area For internal use only 38 © Nokia Siemens Networks

Command Input box

Alarm management (1/3) Alarm management is a basic functionality of the RNC that enables us to view the alarms in the NE in real time. We can enable tasks by clicking:  Left click on “Alarm” tab With alarm management we can:

• • • • • • • •

View two types of alarms (event alarms and fault alarms) View four types of alarm severities (critical, major, minor, warning) View the location/root cause of the alarm (power, transmission, hardware, software, etc) Store history alarms for multiple days

Filter alarms according to configuration View alarm handling suggestions Manually removing alarms Operate external alarm box


Alarm management (2/3) The GUI of Alarm management window consists of 4 blocks:

  

Browse Alarm tab: Displays all the open alarms in the RNC side , both fault and event alarms. Alarm Log tab: Displays all the log of alarms, that are already cleared in the RNC side.

Alarm Configuration tab: Displays the configuration of queried alarms, like alarm shield information, alarm severity reconfiguration, alarm box flag, etc



Alarm List Area: Provides all important information concerning the queried alarms like alarm severity, alarm ID, alarm raised time, location information etc


Alarm management (3/3) Alarm Configurat ion tab

Alarm Log tab

Browse Alarm tab

Alarm List Area For internal use only 41 © Nokia Siemens Networks

Trace management (1/4) Tracing procedure in Huawei RNC is a resource consuming procedure and therefore we need to use with major concern on the SPU load. When creating a new tracing task in the LMT, a binary command with all requested tracing parameters in sent to the OMU board in the RNC, which is responsible for assigning this task in the corresponding board/boards and in specific in the debugging modules. The debugging module of each board is responsible to filter all executed messages according to the needs of the specific trace and also inform the service module of the board.


Trace management (2/4) Trace management is a very crucial functionality of the RNC for troubleshooting. With trace management we are able to trace signaling in all interfaces of the RNC for user/cell/RNC level and identify all 3GPP IE we need to discover the root cause of any problem. We can enable tasks by clicking:  Left click on “Trace” tab With trace management we can:

• • • • • •

Initiate/save/browse traces View interpretation of tracing messages Manage tracing tasks and tracing files Trace Iu/Iupc/Iur/Iub/Uu interfaces Trace specific UE or cell Also enable IP/MNCDT/IOS traces


Trace management (3/4) The GUI of Trace management window consists of 3 blocks:



Trace Navigation Tree: Provides with drop down list that facilitates to initiate new tracing tasks, manage tracing tasks and tracing files.



Trace Data window: Displays all the corresponding signaling according to the tracing tasks configuration.



Progress window: Displays important information about on-going tasks


Trace management (4/4)

Trace Data window

Trace Navigation Tree


Progress window

Performance monitoring (1/4) Performance monitoring in Huawei RNC is a powerful way to monitor the resource utilization of the RNC in real-time. This is also a resource consuming procedure and therefore we need to use with major concern on the SPU load. When creating a new monitoring task in the LMT, a binary command with all requested monitoring parameters in sent to the OMU board in the RNC, which is responsible for assigning this task in the corresponding board/boards, either in service modules through debugging modules, or to the maintenance and configuration modules.


Performance monitoring (2/4) Performance monitoring is a RNC feature that enables us to monitor in real time resources like CPU usage, air interface resources etc. Thus, it provides an important tool to identify capacity bottlenecks in the network. We can enable tasks by clicking:  Left click on “Monitor” tab

With performance monitoring we can:

• • • • • • •

Monitor CPU usage Monitor transmission resources Monitor BER on E1/T1 links

Monitor link performance Monitor connection performance Monitor cell performance Monitor board resources


Performance monitoring (3/4) The GUI of Performance monitoring window consists of 3 blocks:



Monitor Navigation Tree: Provides with drop down list that facilitates to initiate new monitoring tasks.



Monitor Data Window: Displays all the corresponding depiction of the item that is selected to be monitored.





Performance monitoring (4/4)

Monitor Data Window

Monitor Navigation Tree


Progress window

Device maintenance (1/3) Device maintenance is a RNC feature that enables us to emulate the actual hardware of the RNC as if we were on RNC site. It also provides specific shortcut to facilitate operation & maintenance. We can enable tasks by clicking:  Left click on “Device Maintenance” tab

With Device maintenance we can:

• • • • • •

Emulate all subracks of the RNC and observe the RNC hardware as if we were on RNC site Query status of E1/T1/FE/GE/Optical ports Query the CPU usage

Query RNC board information Reset/Switch RNC boards Query DSP status


Device maintenance (2/3) The GUI of Device maintenance window consists of 3 blocks:



Device Navigation Tree: Provides with drop down list that facilitates to initiate new monitoring tasks.



Device Panel Window: Displays all the corresponding depiction of the item that is selected to be maintained.





Device maintenance (3/3)

Device Navigation Tree


Device Panel Window

Progress window



NodeB LMT Introduction MML commands Alarm management Topology management Trace management Common monitoring Software management Real-time specific monitoring


Introduction Local Maintenance Terminal (LMT) is considered as the first level of support for operation & maintenance in Huawei NodeB. It is a windows based software that has to be installed locally in a laptop/desktop. In order to connect to LMT, all we need is an IP connectivity either directly to NodeB local Ethernet port or remotely using the O&M plane of the Iub interface throught the RNC. Proper configuration of the firewall and authentication user rights is also needed. Each LMT window refer to one and only one NodeB, and this is exactly why with LMT we can not perform centralized operation & maintenance, but only local (for 1 NE).


MML commands MML command window is the most basic functionality of the NodeB LMT. With this we are able to execute all authorized commands to the NE and get corresponding feedback. We can enable tasks by clicking in the Navigation Tree:  Left click on “MML Command” tab

With MML command window we can:

• Execute NodeB configuration commands • Execute NodeB maintenance commands • Run MML commands in batches


Alarm management Alarm management is a basic functionality of the NodeB that enables us to view the alarms in the NE in real time, together is the most basic functionality of the RNC LMT. We can enable tasks by clicking:  Left click on “Fault Management”→ “Browse Alarm”

With Alarm management we can:

• • • • • • • •

View two types of alarms (event alarms and fault alarms) View four types of alarm severities (critical, major, minor, warning) View the location/root cause of the alarm (power, transmission, hardware, software, etc)

Store history alarms for multiple days and query alarm log Shield alarms according to configuration View alarm handling suggestions Export NodeB alarms

Operate external alarm box


Topology management Topology management is a NodeB feature that enables us to emulate the actual hardware of the NodeB as if we were on site. It also provides specific shortcut to facilitate operation & maintenance. We can enable tasks by clicking in the Navigation Tree:  Left click on “Maintenance” → “Topology Management”→ “Main Cabinet”

With Topology management we can:

• Emulate both baseband subrack of NodeB as well are RRC chain’s hardware as if we were on RNC site

• • • •

Query board/clock/version/alarm status Query E1/T1 status and working mode Query the CPU usage Reset/Switch/Block NodeB boards


Trace management Trace management is a very crucial functionality for NodeB troubleshooting. With trace management we are able to trace signaling in Iub/Uu interfaces and identify all 3GPP IE we need to discover the root cause of any problem. We can enable tasks by clicking in Navigation Tree:  Left click on “Maintenance” → “Trace Management”→ “Interface Trace Task” With Trace management we can:

• • • •

Trace all Iub/SCTP/IP/ICP/User/Cell/SAAL/MAC interfaces and protocols Browsing traced messages online/offline Suspend/resume/save tracing task View message translation


Common monitoring NodeB common monitoring is a feature that enables us to monitor in real time resources like CPU usage, board utilization etc. Thus, it provides an important tool to identify capacity bottlenecks in the network. We can enable tasks by clicking:  Left click on “Maintenance” → “Common Monitoring”→ “CPU/DSP usage”

With Common monitoring we can:

• Monitor/Display/Save CPU usage • Monitor/Display/Save DSP usage


Software management Software management is a set of features in NodeB that facilitates in handling the software version and configuration of NodeB. It is a very important feature as it has to be used by field engineers in the initial hardware installation. We can enable tasks by clicking:  Left click on “Maintenance” → “Software Management”

With Software Management we can:

• • • • • •

Download/Activate new BOOTROM version Download/Activate new cold/hot software patch Download/Activate/Synchronize new NodeB software version

Backup configuration file Download a new configuration file Transfer Device Archives and other files


Real-time specific monitoring Real-time specific monitoring is a feature that enables us to monitor in real time critical resources of the NodeB and thus, it provides an important tool to identify capacity bottlenecks in the network. We can enable tasks by clicking:  Left click on “Maintenance” → “Realtime Specific Monitoring”

With Real-time specific monitoring we can:

• • • • • • • • •

Collect IP clock data Monitor traffic of transmission ports and links Query service resources of a cell

Measure RTWP Scan UL frequency Monitor NodeB RF output power Monitor NodeB temperature

Query NodeB baseband resources Monitor cell service throughput




Common components OSS Network Explorer (ONE) OSS Common Explorer The Fault Manager (FM) Ericsson Business Intelligence Deployment (EBID) The Network Statistics and Performance Management (NWS/PMS) The Software Management (SMO) The Health Check The Job Manager (JM) The Radio Network Optimization (RNO) • • • •

WNCS WMRR FFAX-W GEO-W

Event-Based Application (EBA) The Recording and Events Interface (REI) MoShell For internal use only 64 © Nokia Siemens Networks

OSS Network Explorer (ONE) (1/2) The OSS Network Explorer (ONE) is main application (system portal), that can navigate through all nodes and access to operation activities. ONE is graphical interface that provides topology and hierarchical overview of the network (both radio and core). All basic properties of the network and its nodes could be seen through ONE.

The OSS Network Explorer application, is launched from the Main Menu in OSS:  Left click on OSS Main Menu (“Start”) → “Applications” → “Ericsson” → “OSS Network Explorer”


OSS Network Explorer (ONE) (2/2) The GUI of ONE consists of four blocks:

 

Menu bar: provides access to available applications for operation and maintenance of the network

Network Browser pane: consists of the Active network browser view drop down list and the Network Browser. The topology in ONE is presented in a tree structure



Information List pane: provides access to applications associated to the individual network object that are available through ONE.



Property pane: shows the basic properties of a network object selected in the Network Browser.

Menu bar Information pane Network Browser pane Property pane


Tool overview: OSS Network Explorer Tool name

Data input type

Applicable interfaces / network elements

Main area of application / Use Cases

OSS Network Explorer

xml

all nodes supported by the OSS (RNC, RXI, RBS...)

• O&M, optimization: Access to all nodes and operation activities.

Vendors integrated: based on signalling traces, hence vendor independent


Required user expertise Minimal

Preparation effort prior to start of analysis

OSS Common Explorer (1/3) The OSS Common Explorer is a OSS suite of software that handles O&M tasks for the WCDMA, LTE and TD-SCDMA networks. It provides the user with interfaces for transferring information from network elements to the network management layer and offers a solid view, including WCDMA RAN information. The OSS Common Explorer application, is launched from the Main Menu in OSS:  Left click on OSS Main Menu (“Start”) → “Applications” → “Ericsson” → “OSS Common Explorer”


OSS Common Explorer (2/3) OSS Common Explorer is GUI interface for the folowing functions:

 Radio and Transport     

  

Network Configuration Parameter, Consistency and Health check Import/Export Fallback Area View properties Network element logs handling and collecting Node status analyzer Cell availability Element manager


OSS Common Explorer (3/3) OSS Common Export activity • Export of network configuration, all radio configuration and parameter data from the selected RNC and belonging RBSs (RNC level) • Step-by-Step Left click on OSS Main Menu (“Start”) Click on “Applications”” Click on “Ericsson”” Click on “OSS Common Explorer” Select RNC or set of RBSs on network element tree Right Click on selected networ element (RNC or RBS) Click on “Export NE”

Bulk CM export windoe will apear Select “Radio Topology” or “Both radio and Transport Topology” and write File name Click “Export”

• 3GPP Bulk CM export file is saved in XML format • Path /var/opt/ericsson/nms_umts_wran_bcg/files/export/cm_exp_.xml For internal use only 70 © Nokia Siemens Networks

Tool overview: OSS Common Explorer Tool name

Data input type



Required user expertise

OSS Common Explorer

xml


• Radio and Transport

Minimal

• • • • • • • •

Network Configuration Parameter, Consistency and Health check Import/Export Fallback Area View properties Network element logs handling and collecting Node status analyzer Cell availability Element manager

Vendors integrated: based on signalling traces, hence vendor independent


preparation effort prior to start of analysis

Fault Manager (FM) (1/3) 

Fault Manager receives alarms from network nodes equipment through alarm managers. The alarm managers log, record and translate the alarms to the format required by the Fault Management Kernel.



The FM Kernel is the main component of the Fault Manager. The input to the Kernel is error messages and alarm information (Alarm Records). The output is information that is processed, stored in databases, and made available to the presentation functions and agents.



Main functions of Adaptation and Manager layers is to o receive alarms and error messages from specific network elements.



The Alarm Agents are used to communicate with other systems (ex. NMS).



The Fault Manager eXpert (FMX) contains functions to incorporate expertise knowledge into the analysis of alarms and error messages.



Presentation Functions

Agents FMII

FMII FMXI

FMX

FM Karnel SUPI

System Admin tools

FMAI

Managers

Adaptations

The presentation functions are used by the user to view and work with the received alarms and error messages For internal use only 72 © Nokia Siemens Networks

Fault Manager (FM) (2/3)  Presentation processes as a part of Fault Manager system are mainly GUI: Alarm List Viewer, Alarm Status Matrix, Alarm Log Browser...

 The Alarm List Viewer shows the complete alarm situation for one or more network elements in the network

 The ASM (Alarm Status Matrix) shows the alarm status for a number of objects in a space efficient matrix.

 Alarm Log Browser is used to search for alarm information in the FM alarm log. For internal use only 73 © Nokia Siemens Networks

Fault Manager (FM) (3/3)  Alarm List Viewer has topology pane that is used to navigate and selecte network element. In the List Frame current alarms are listed.

Navigator pane

List Frame


Tool overview: Fault Manager Tool name

Data input type




Fault Manager

Alarm Records / Logs internal


• Radio and Transport

yes


Network O&M • Health check


Ericsson Business Intelligence Deployment (EBID) EBID consists from:

   

Business Intelligence Server, BIS Citrix Client

ENIQ server OSS-RC master server Windows Application Server, WAS



BIS server is used to provide a Web-interface to EBID reports.



BIS hosts the Business Object (BO) Enterprise XI 3 server installation.

WAS

Citrix Server

BO XI 3 Web Server

BO XI 3 Sybase IQ Network client

BIS

Sybase Open client

WE

Sybase IQ Network client

MySQL Sybase Open client



BO Enterprise XI 3 provides mechanisms for accessing the Central Management Server (CMS).



The BO Enterprise XI 3 client tools is installed on the WAS server


ENIQ

OSS RC Sybase IQ Measurement DB

Sybase ASE Measurement DB

Network Statistics (NWS) / Performance Management Subsystem (PMS) (1/5) NWS is OSS Performance Management application, that receives and stores counters from network nodes. NWS consists of following components:

  

initiation and collection (SMIA, MIA, SGw, PDM-SPDM, PMS)

storage (SDM) presentation (PSA, NWS-A)

PMS is subsystem that retrieves the data from the WCDMA RAN Network Elements and notifies Statistical Datamart (SDM) about the arrival of the data.

Ericsson PM collects statistics in form of XML file (Ericsson 3G WCDMA performance statistics file format):



XML format following 3GPP specification, document, 3GPP XML specified format(TS32.401 Rel 6.2.0) .


Network Statistics (NWS) / Performance Management Subsystem (PMS) (2/5) Ericsson PM XML file, PM data storage

 WCDMA Counter and measurement storage Counter values and measurement results are stored at the NE’s as ROP files every 15 min in 3GPP XML specified format(TS32.401 Rel 6.2.0) . ROP files are generated at the NE’s and stored as a backup for at least 1 hrs, file location can be read by the MO attribute PmService::performanceDataPath. ROP files are automatically collected from the NE’s and transferred to file storage in OSS-RC and stored there for a configurable period of time( min: 24hrs, max: file storage size dependent.)

“Raw” PM data access, OSS-RC


Network Statistics (NWS) / Performance Management Subsystem (PMS) (3/5) Ericsson XML PM file, retrieving data files (via ftp transfer)

 Ericsson 3G WCDMA configuration file, Export procedure Performance data is automatically stored in OSS file storage and raw data can be transferred directly from file storage using ftp transfer or similar.

• Hostname: IP address of OSS. • Performance data file location: /var/opt/ericsson/nms_umts_pms_seg/segment1/XML • Access: file transfer using ftp transfer  Export file sample: Find an example of Ericsson RNC performance data file export: A20091207.1400-1415_SubNetwork=xxx3G,SubNetwork=Rsample, MeContext=sample_FDD_statsfile.xml Attached file is opened in either MS xl or text editor.

Find an example of Ericsson RNC/ RBS performance data file export: A20091207.1400-1415_SubNetwork=xxx3G,SubNetwork=RSample,MeContext=Rsample_statsfile.xml Attached file is opened in either MS xl or text editor.


Network Statistics (NWS) / Performance Management Subsystem (PMS) (4/5) Ericsson XML PM file, retrieving data files( via ftp transfer) /var/opt/ericsson/nms_umts_pms_seg/segment1/XML


Network Statistics (NWS) / Performance Management Subsystem (PMS) (5/5) WCDMA RAN Measurements 

WCDMA RAN Measurements is application for initiating data measurements in WCDMA



WCDMA RAN Measurements could be start from Main Menu



The different types of measurements can be initiated, This is done through “Data collection subscription profiles” window (“Add profile” wizard) • Statistic Profiles • UETR, User Equipment Traffic Recording • CTR, Cell Traffic Recording • GPEH, General Performance and Event Handling


Tool overview: Performance Management Subsystem (PMS) Tool name

Data input type




Performance Management Subsystem (PMS)

counters from network nodes 3GPP XML specified format(TS3 2.401 Rel 6.2.0)


• RAN Optimization

yes


activities • Performance assessment • Radio and Transport Network O&M


Tools SMO (Software Management Organizer) (1/4) SMO is application for remote software and hardware handling of GSM and UMTS Network Elements. It supports nodes based on AXE, GSM RBS, CPP, GSN WPP, J20, MPC, STN and IS, and provides a process oriented working environment for the user, and uniform software handling for different NE types. The SMO is launched from the Main Menu in OSS:  Left click on OSS Main Menu (“Start”) → “Applications” → “Ericsson” → “Configuration” → “Manage Hardware and Software Inventory” → “Software Management Organizer”


Tools SMO (Software Management Organizer) (2/4)  SMO have following functions: • • • • • •

Collect hardware data from the network and export of hardware data to external inventory management systems (this is done with NIO (hardware inventory) Remote software upgrade, software inventory and distribution from OSS to NEs Backup administration Uniform handling of different NE types Distribute license key files to CPP NEs Perform hardware to software compliance checks during upgrade

 SMO includes a network topology tree view, where the user can access software inventory functions. The inventory is adjusted from the NE, and cached in a database by SMO.  Among others, SMO application consists of the following two components: • SMO GUI (Graphical User Interface) •

presents both interactive and scheduled software management activities SMO CLI (Command Line Interface) provides a subset of the functionality available in the GUI and it is mainly intended for scripting purposes


Tools SMO (Software Management Organizer) (3/4) SMO GUI Export activity • Step-by-Step

Right click on OSS-RC Workspace Menu

Click on “OK”

Click on “Configuration”

Click on “Network” tab

Click on “Manage HW and SW inventory”

Click on “Export”

Click on “Software Management Organizer”

Click on “Export Software” checkbox

Select “Network” view and select NEs

Click on “Export Hardware” checkbox

Click on “Network” tab

Click on “Export License” checkbox

Click on “Adjust”

Enter the filenames for export files

Click on “Export Software” checkbox

Click on “OK”

Click on “Export Hardware” checkbox

Click on “Export”

Click on “Export License” checkbox


Tools SMO (Software Management Organizer) (4/4) SMO GUI Export activity


Tool overview: Software Management Organizer (SMO) Tool name

Data input type

Software Management Organizer (SMO)



nodes based on AXE, GSM RBS, CPP, GSN WPP, J20, MPC, STN and IS

• Collecting hardware data from

• • • • •


the network and export of hardware data to external inventory management systems (this is done with NIO (hardware inventory) Remote software upgrade, software inventory and distribution from OSS to NEs Backup administration Uniform handling of different NE types Distribute license key files to CPP NEs Perform hardware to software compliance checks during upgrade


yes


Health Check (1/2) The Health Check is a diagnostic tool that check the state of network elements. Health Check is started from SMO.


Health Check (2/2) 

Checks Performed in Health Check • • • • • • • • • • •

Disk space: available disk space on the NE Cell availability: disabled cells and channels on the NE. Errors: errors on the NEs boards Upgrade package: current upgrade package loaded on the NE Red LED status: NEs boards that have the Red LED status ON. Abnormal restarts: NEs and boards that have abnormal restarts Link Device status: link devices that have an Operational State DISABLED for a NE. Disabled unlocked PIUs: NEs that have Plugin Units with an UNLOCKED administrative state and DISABLED operational state. Hardware: hardware loaded on the NE Alarm: alarm log of the selected NE Channel Element Capacity: available and licensed hardware capacity (DL and UL)



It is useful to run Health Check before and after the following: • • • •

Software upgrades Hardware upgrades Activating a Planned Configuration Area Reparenting an RBS




The result output file is generated both in XML and HTML

Tool overview: Health Check Tool name

Data input type

Health Check





RNC, RXI, RBS...

after: • Software upgrades • Hardware upgrades • Activating a Planned Configuration Area • Reparenting an RBS

minimal


Job Manager (JM) (1/3) Job manager is environment for script-handling and script-based application development. JM provides all the necessary functions for handling scripting towards all nodes supported by the OSS. JM application consists of following main components:  Job Editor List  Managed Object Command Line  Job Supervisor It is not recommend to start application/components from root, it should be started from NE:


Job Manager (JM) (2/3) Job Editor List is part of JM application, that helps user to list, schedule, import, export, copy, cut, and paste jobs. A job can be created, deleted, open, export and import by using toolbar buttons

A Job is a series of activities (an activity executes a single task) that can be executed to fulfill a work order.

Open New

Shedule Delete

export

import

There are some predefined tasks (CellAvailability...) that could be used in creating activity chain. The Job Editor is a component of the Job Manager application which is used to create and edit Jobs. Navigator pane


Job Manager (JM) (3/3) Job Supervisor is part of JM application which is used to supervise and run Jobs. All jobs are listed in job supervisor table in order of job ID.

Command Line Interface is a component of the Job Manager application which is used for the administration of jobs. The MO CLI is a shell script, startmoCli.sh, located in the following directory: /opt/ericsson/jm/bin CLI is run by command: ./startmoCli.sh


Tool overview: Job Manager Tool name

Data input type

Job Manager





all nodes supported by the OSS

• O&M activities

minimal

/

Handling with scripts


Radio Network Optimisation (RNO) RNO application The RNO application is part of OSS, and it contains of several functions in order to help in optimization activities of radio GSM and WCDMA network. Functions of the RNO WCDMA applications:  WNCS  FFAX-W  WMRR  GEO-W



The Radio Network Optimisation application, is launched from the Main Menu in OSS:

Left click on OSS Main Menu (“Start”) → “Applications” → “Ericsson” → “Performance” → “Radio Network Optimisation”


Tools used for Radio Network Optimisation (RNO) WNCS (1/8) 

WNCS (WCDMA Neighbor Cell Support) is function that helps to optimize neighbor relations at the same frequency in WCDMA network: missing and unnecessary neighbor relations could be detected. Functions is based on GPEH (General Performance Event Handling) measurements. That is event triggered reporting concept. WNCS can also include, in analysis, related counters: • pmRlAddAttemptsBestCellSpeech • pmRlAddSuccessBestCellSpeech WNCS schedules recordings of GPEH events, collects ROP files and later processes and presents results. First step is to set-up new WNCS recording: “File” → “New Recording” → “NCS” For internal use only 96 © Nokia Siemens Networks

Tools used for Radio Network Optimisation (RNO) WNCS (2/8) Recording

 Recording is performed by “NCS New Recording” wizard.

 In order to perform WCDMA NCS measurement “Measure WCDMA” check box must be checked. Data to measure specifies the source to collect data from.  Both GPEH events and Counters  Only GPEH events  Only Counters

Cell Set is cell filter that is used to select group of cells or RNC on which measurements will be performed


Tools used for Radio Network Optimisation (RNO) WNCS (3/8) Basic principle of GPEH measurements

 

The RNC/RBS can log different types of events.

Recording starts at the beginning of the next 15-minute Result Output Period (ROP) after activation from OSS.



The events are collected in GPEH data files (main file and subfiles). The main file contains administrative information about GPEH recording, while subfiles contains recorded events. Depending on size of records, there could be more subfiles for each ROP.



Events are grouped in:  RNC internal events: they are triggered by specific internal conditions (channel switch occurs, admission control request, terminates of connections, congestions, cell is not included in neighbor set...

 Inter node events: Layer 3 protocol messages as specified by 3rd Generation Partnership Project (3GPP). There are several group of inter node events according to the protocols (RRC, NBPA, RANAP, RNSAP, PCAP, SABP)



All events have list of parameters that define events: EVENT_PARAM_SCANNER_ID, EVENT_PARAM_TIMESTAMP_HOUR(MINUTE/SECONDS/MILLISEC), EVENT_PARAM_EVENT_ID, EVENT_PARAM_UE_CONTEXT, EVENT_PARAM_C_ID_xy... For internal use only 98 © Nokia Siemens Networks

Tools used for Radio Network Optimisation (RNO) WNCS (4/8) Basic principle of GPEH measurements



Main GPEH events, needed for WNCS, are:  INTERNAL_SOHO_DS_MISSING_NEIGHBOUR: Event is captured at reception of a measurement report for event 1a or event 1c, where the triggering cell is not included in neighbor set.



INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR: event is captured when handover proposal is received, where the proposed cell is included in the neighbor set, but not included in the monitored set.



Parameters of this events contains information of best cell, RNC_ID, trigger cell scrambling code, RSCP/ECNO of trigger cell...



When GPEH measurements are completed, WNCS can processes files and represent results



WNCS measurements can cover several ROPs, but for each ROP period separate files, with recorded event data, will be created.


Tools used for Radio Network Optimisation (RNO) WNCS (5/8) Overview report  Results of WNCS measurements can be seen in “RNO WNCS Overview Report” window



All cells, which were subject of measurements, are listed in the rows. Columns of the table could be sorted in order to identify most critical cells regarding to missing neighbors, drop calls...



Double click on the cell will open new table (“RNO – WNCS Cell Report”) with more details regarding neighbor relations. For internal use only 100 © Nokia Siemens Networks

Tools used for Radio Network Optimisation (RNO) WNCS (6/8) RNO – WNCS Cell report (Defined Neighours) 

In “Defined Neighbour” tab all neighbour relations that are defined are listed.



The list, for example, can be sorted according to the number of attempts to establish radio link (RL). So, relations with no or few RL attempts could be removed.



When the active set contains more than one cell, the monitored set (limited to 32 relations) will be a union of all defined neighbour relations for the cells in the active set. Those relations that could not fit into the monitored set are called unmonitored neighbours.



Unmonitored neighbour list could help to detect potential problems due to limited number of monitored relations. For internal use only 101 © Nokia Siemens Networks

Tools used for Radio Network Optimisation (RNO) WNCS (7/8) RNO – WNCS Cell report (Undefined Neighours)  Undefined list of neighbour relations is created owing to GPEH INTERNAL_SOHO_DS_MISSING_ NEIGHBOUR events.



The list, for examle, can be sorted according to the number of possible RL adding attempts (or number of missing events). So, potential relations could be add.



Number of drop calls due to missing relations, average RSCP, time in active set and/or Average EcNo could also be considered when decisions are taking regarding adding neighbour relations.



Probable cell name is yielded due to algorithm that maps a cell name according to scrambling code, distance of potential cell, cell positions... “Unknown” is reported if algorithm could not map cell name. For internal use only 102 © Nokia Siemens Networks

Tools used for Radio Network Optimisation (RNO) WNCS (8/8) RNO – WNCS : Export

 

Analysis could be performed offline, too. (for example in MS Excel) All WNCS data, relevant for analysis, could be export from “RNO – WNCS Overview Report” window. 



Left click on Menu (“File”) → “Export” → “Tab Separated File”

Example of WNCS export could be found in attached file:


Tools used for Radio Network Optimisation (RNO) WMRR 

WMRR is function in RNO application that could be used to:  Evaluate and supervise network performance and quality  Perform network tuning and optimization

   

The evaluation is performed due to statistics, that is collected from UE, RBS and RNC

WMRR uses PMS to initiate measurements towards a RNC/RBS. Tx Code Power on DL per spreading factor (4-256) is measuring on RBS. Threshold, distribution and percentile of Downlink Transmitted Code Power could be reported by WMRR function


Tools used for Radio Network Optimisation (RNO) FFAX-W 

FFAX-W is function in RNO application that could be used to identify antenna installation problems.



Signal level from two diversity antenna branches should be small. A significant difference could indicate that antenna branches are not performing optimally.

  

Swapped feeders or faulty feeders could be detected. SIR pdf counters on RBS are used in FFAX-W. The user can specify a number of Cells or Cell Sets on which recordings can be performed. An FFAX-W recording is then defined and scheduled.


Tools used for Radio Network Optimisation (RNO) GEO-W 

Geo-Observability for WCDMA (GEO-W) is function in OSS which can correlate performance data with geographical position.



The functionalities included in GEO-W are:  Activation and administration of the Geo-Observability measurements  Collection and processing of the data. Geographical position is included in data.  Generation of an output file. Format of output file is zipped tab-separated file.

 

GEO-W requires Geo-Observability Data (GEOD), optional function of RNC. Capacity for GEO-W is from 1000 up to 5000 cells at the same time, depending on UE fraction and reporting frequency.


Tool overview: Radio Network Optimisation (RNO) Tool name

Data input type





Radio Network Optimisation (RNO)

GPEH (General Performance Event Handling) measurements; PMS statistic data

RNC, RBS

• RAN Optimization

minimal

Performe recording


activities: Neighbour relations, Identify antenna installation problems.

EBA, Event Based Applications for WCDMA Event Based Statistics for WCDMA (EBS-W) 

Event Based Statistics for WCDMA (EBS-W) provides possibilities to create statistics based on events generated in RNC.



The General Performance Event Handling (GPEH) in the RNC is used to create and store the events in files.



EBS-W is optional feature that is used for GPEH events, through PMS interface. performance data with geographical position.

 

ENIQ also could use output from EBS-W. Measurements are initiated by EBS-W GUI, that is started from OSS Network Explorer.


Tool overview: EBA, Event Based Applications Tool name

Data input type




EBA, Event Based Applications

GPEH file

RNC

• RNO

minimal


performance assessment


Recording and Events Interface (REI)  The Recording and Events Interface (REI) is used to:  convert the binary ROP files to ASCII  enable access to CTR and UETR files  REI could be started from OSS Network Explore (Recording File Viewer)

 The Recording profiles supported in OSS:  User Equipment Traffic Recording (UETR): used to trace and record selected UE  Cell Traffic Recording (CTR): used to collect data for a number of UE connections within a certain recording area

 General Performance Event Handling (GPEH) s used to record events (node-internal performance events) as defined in the GPEH subscription profile For internal use only 110 © Nokia Siemens Networks

Tool overview: Recording and Events Interface (REI) Tool name

Data input type





Recording and Events Interface (REI)

GPEH file

RNC

• RNO, performance

minimal

Record event based measurements


assessment: convert the binary ROP files to ASCII enable access to CTR and UETR files

MoShell (1/6)  Moshell is a text-based Element Manager for Cello nodes (UMTS RNC/RBS/RXI/MGW and    

CDMA BSC/RBS). Online MOM browsing with search facility and display of MO tree (parent-children relationships) Command line handling based on the unix bash shell Direct access to OSE shell with possibility to pipe output through external utilities (grep, decoders, etc.) Supports telnet and ssh for access to OSE shell, ftp/sftp/http for file transfer

MoShell Supports:  MO configuration service, secure and unsecure  create/delete MO, get/set MO attribute, action on MO  MO alarm service, secure and unsecure  MOs can raise and acknowledge alarms and events  PM service, secure and unsecure (PM)  create/delete performance counters  OSE shell access, via telnet/ssh  Log service  File service (http/ftp/sftp) For internal use only 112 © Nokia Siemens Networks

MoShell (2/6)  Utilities (for help: execute without parameters)









 Mobatch - run moshell command files on several nodes in parallel  rncaudit/rbsaudit - compare data from one or several RNCs and/or RBSs with a set of reference data  netcheck - performing health-checks and pre/post comparison  swup - perform SW upgrades on several nodes in parallel  swstat - check the SW level throughout the network  swcomp - compare MP/BP SW between two nodes  pmExtract/pmXtab - process Statistics ROP files  restartcollector - gather network restart data and downtimes Useful (help) commands:  h - to show the help. Can be used with a command name after to show help about that command.  m - to show the first menu.  n - to show the second menu. MO could be address on several ways:  All  Proxy ID (retrieved by “pr plu” command)  MO group (defined by user, by command “ma/lma/mp”)  Board group Commands in MO Shell could be piped (Unix format) “|”  example “te log read | grep ERROR” (example) Get attributes of MO by get command  get


MoShell (3/6) Export activity  MoShell Export • All RNC or RBS Managed Objects (MOs), attributes, values, states etc. (RBS type, DCH and HSDPA powers, coordinates, azimuth, electrical & machanical downtilt, height and type, feeder loss...) • UNIX text format, export can be saved in .log file • Default path for the saved log files is /moshell_log files/logs_moshell/sessionlog/.log

 Commands: • • • •

l+ - open moshell logfile, l- - close moshell logfile lt all - load all MO Types pr/lpr - Print MO LDNs and proxy ids for all or part of the MO tree currently loaded in moshell. cabx - Print MP/BP HW info and led status, MP temperature, and coreMgr status, led and hw info for the XP boards (eg: TMA, MCPA, Fans, etc.) • get/lget - Read CM/FM attribute from MO. • hget/lhget - Read CM/FM attribute from MO, print horizontally one line per MO (instead of one line per attribute). • kget/lkget - Display CM/FM attributes in exportable printout format.


MoShell (4/6) MoShell Export • Step-by-Step on RNC

Right click on OSS-RC Workspace Menu

Click on “Open Terminal” Write “moshell RNC”; RNC is the name of RNC Write “l+ logfile1”; starts logging to a Write “lt all” Write “lpr RncFeature”

Prints all RNC features

Write “lhget RncFeature featurestate”

Prints all RNC features with state (activated/deactivated)

Write “lhget utrancell=all antennaposition”

Prints coordinates for all cells

Write “lhget utrancell=all uarfcnDl”

Prints DL uarfcn for all cells


MoShell (5/6) MoShell Export • Step-by-Step on RBS

Write “lhget utrancell=all primaryCpichPower”

Prints primaryCpichPower value

Write “lhget utrancell=all maxTxPowerUl”

Prints maxTxPowerUl value

Write “lhget utrancell=all maximumTransmissionPower”

Prints maximumTransmissionPower value

Write “l- logfile1”; stops logging to a Write “moshell RBS”; RBS is the name of RBS Write “l+ logfile2”; starts logging to a Write “lt all” Write “get . featurestate”

Prints all RBS features with state (activated/deactivated)

Write “get hsPowerMargin”

Prints hsPowerMargin value

Write “get productname”

Prints RBS type


MoShell (6/6) MoShell Export • Step-by-Step on RBS Write “lhget AntFeederCable ulGain”

Prints UL gain of TMA/ASC

Write “lhget AntFeederCable dlAttenuation”

Prints DL feeder loss

Write “lhget AntFeederCable ulAttenuation”

Prints UL feeder loss

Write “lhget sectorantenna antennaType”

Prints antenna type

Write “lhget sectorantenna electricalAntennaTilt”

Prints electrical tilt value

Write “lhget sectorantenna mechanicalAntenaTilt”

Prints mechanical tilt value as it was writen in the database

Write “lhget sector beamDirection”

Prints antenna azimuth value as it was writen in the database

Write “lhget sector height”

Prints antenna height value as it was writen in the database

Write “get . featurestate”

Prints all RBS features with state (activated/deactivated)

Write “l- logfile2”; stops logging to a


Tool overview: MoShell Tool name

Data input type




MoShell

Command line handling based on the unix bash shell. Supports telnet and ssh for access to OSE shell, ftp/sftp/http for file transfer

Cello nodes (UMTS RNC/RBS/RXI/ MGW and CDMA BSC/RBS)

• Configuration • Parameter and alarm

yes


check • Health check • Assessment (Export data for RAN optimization)




Technology-specific application suites  Parameter Check  Cell Availability  Consistency Check (CC)  TEI


Parameter check • Parameter Check application is run from the OSS Common Explorer • Parameter Check displays the changes in a parameter, new or removed parameters and new or removed Managed Objects. It is also possible to record if a parameter is off-track based on user-defined criteria • The Parameter check application provides the following functions and support: – Compares a data source file with an export of the current network or compares directly with the network – Compares parameters for a default value – Compares parameters in a default range – Plots a histogram for a single parameter across the network

• Parameter comparison analysis – Evaluate parameters deviating from MV parameter defaults. Consult assistance on evaluation if necessary. For internal use only 121 © Nokia Siemens Networks

Tool overview: Parameter check Tool name

Data input type




Parameter check

xml (bulk export file)

RNC, RBS

• Parameter check: o Compares a data source file

minimal

with an export of the current network or compares directly with the network o Compares parameters for a default value o Compares parameters in a default range o Plots a histogram for a single parameter across the network



Cell Availability tool (1/2) 

The “Cell Availability” is a stand-alone application, used to display the current status of all UTRAN cells. Application displays all locked and enabled cells.



Cell Availability could be launched directly from Web Explorer (http://caserver.ericsson.se:8080/car) or from Tools menu of the OSS Common Explorer GUI


Cell Availability tool (2/2) 

Application is using following counters for preparing report:  pmCellDowntimeAuto  pmCellDowntimeMan  pmHsDowntimeAuto  pmHsDowntimeMan  pmEulDowntimeAuto  pmEulDowntimeMan  pmMbmsDowntimeAuto  pmMbmsDowntimeMan



To use the Cell Availability application two scripts need to be run prior to launching the Cell Availability GUI:  startROPParser.sh script, which retrieves and parses counters of interest from ROP file.  startBulkParser.sh script, for NE information


Tool overview: Cell Availability tool Tool name

Data input type



Cell Availability tool

PMS (pm statistics)

RBS (cells)

• O&M minimal •Health check / RNO



preparation effort prior to start of analysis retrieves and parses counters of interest from ROP file (script)

Consistency Check • Consistency Check application is run from the OSS Network Explorer (ONE) in order to validate parameter changes.

• The WCDMA RAN Consistency Check (WCC) application is used to check that Network Elements in the WCDMA Radio Access Network have consistent data. If data is not consistent between Network Elements, problems can occur in the network.

• Using the Consistency Check interface, Network Elements can be selected and data can be checked for consistency. This is done by applying rules to selected Network Elements. The rules determine the areas of the configuration that are to be checked, which include the following: – Power – Data Matching – Cell neighbor – Capacity Management – Congestion Control – High Speed data links – AAL2 – Attribute Uniqueness – Cardinality Check

• Consistency check results can be stored and exported in various formats and reports. For internal use only 126 © Nokia Siemens Networks

Tool overview: Consistency Check Tool name

Data input type

Consistency Check





(RBS)

• RNO activities • Consistency of: o Power o Data Matching o Cell neighbor o Capacity Management o Congestion Control o High Speed data links o AAL2 o Attribute Uniqueness o Cardinality Check

minimal


Tools used for Export/Import configuration data TEI - Tool for Export and Import TEI is Ericsson offline application and it enables to transform Bulk CM Configuration Data exported from OSS Common Explorer into a MS Excel format. TEI application is able to interpret the changes done in the Excel spreadsheet view and is then able to generate Bulk CM import files from the spreadsheet format. TEI includes the following functionality:  Converts Bulk CM export configuration data into a spreadsheet format which can be edited using MS Excel



Generates Bulk CM import files from the edited spreadsheet reflecting the changes made in the spreadsheet

OSS Common Explorer export file can be imported to TEI in order to transform Bulk CM Configuration Data into MS Excel



Open “TEI” → Select “Bulk CM Export File to Microsoft Excel Spreadsheet” in “Choose a Conversion method” window → specify the paths and filenames for Input and Output files in “Files selection” section → press “Create”


Tool overview: TEI - Tool for Export and Import Tool name

Data input type





TEI

xml (bulk export file)


• RNO activities • RNO activities • Consistency of:

minimal

Export xml bulk file from OSS


Assessment (parameters, neighbors)

3G OSS Tools Ericsson Huawei

Recommend Documents