Professional Documents
Culture Documents
Document Info
Title Reference Target Group Technology Software Release Service NPO UTRAN WCDMA, Ericsson and Huawei OSS 10, W10, RAN12 OSS tools, Ericsson and Huawei 3G
Service Item
Version Version Date Ver. 1.0 2 June 2011
Version 1.0
Section All
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.
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
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
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.
Handling description
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
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)
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.
Selection list
Template list: Provides a list with all saved queries (templates) for automated or future use
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
Data pane: Provides all the data fulfilling the querying conditions
Template list
Data pane
Query configuration of each NE (RAN, CN, transmission) Change configuration of each NE Managing inventory data Starting NE LMT Staring CME Starting Telnet
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
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
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
Task list
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
Navigation tree: Provides the list with all NE that support the software broswing feature
Content window: Contains the full list of all Software/Patches/Data/Logs for the selected NE stored in the M2000 server Task list: Indicates the list with all tasks made or planned to be performed for all NE
Task list
Perform centralized user management Define different authorities to different user accounts Create local NE user right and accounts
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
Record M2000 operation/security/system logs Record NE operation/security/system logs Automatic synchronizing NE logs
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
Navigation tree
Operation button
Trace list
Shortcut menu
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
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
Navigation tree
Button panel
Task list
Contents
HUAWEI M2000 Client RNC LMT NodeB LMT ERICSSON Common components Technology-specific application suites
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 doesnt 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)
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
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.
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
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
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 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
Monitor CPU usage Monitor transmission resources Monitor BER on E1/T1 links
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.
Progress window
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
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.
Progress window
Contents
HUAWEI M2000 Client RNC LMT NodeB LMT ERICSSON Common components Technology-specific application suites
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
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
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
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
Emulate both baseband subrack of NodeB as well are RRC chains 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
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
Download/Activate new BOOTROM version Download/Activate new cold/hot software patch Download/Activate/Synchronize new NodeB software version
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
Contents
HUAWEI M2000 Client RNC LMT NodeB LMT ERICSSON Common components Technology-specific application suites
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
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
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.
O&M, optimization:
Access to all nodes and operation activities.
Presentation Functions
FMII FMXI
Agents
FMII
Main functions of Adaptation and Manager layers is to o receive alarms and error messages from specific network elements.
FMX
SUPI
FM Karnel
FMAI
The Alarm Agents are used to communicate with other systems (ex. NMS).
Managers
The Fault Manager eXpert (FMX) contains functions to incorporate expertise knowledge into the analysis of alarms and error messages.
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
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
Navigator pane
List Frame
Business Intelligence Server, BIS ENIQ server OSS-RC master server Windows Application Server, WAS
WAS Citrix Server BO XI 3
Sybase IQ Network client Sybase Open client
Citrix Client
BIS server is used to provide a Web-interface to EBID reports. BIS hosts the Business Object (BO) Enterprise XI 3 server installation.
MySQL
Sybase Open client
WE
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
Sybase IQ Measurement DB
OSS RC
Sybase ASE Measurement DB
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) .
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.
counters from network nodes 3GPP XML specified format(TS3 2.401 Rel 6.2.0)
RAN Optimization
activities Performance assessment Radio and Transport Network O&M
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
Right click on OSS-RC Workspace Menu Click on Configuration Click on Manage HW and SW inventory Click on Software Management Organizer Select Network view and select NEs Click on Network tab Click on Adjust
Click on OK Click on Network tab Click on Export Click on Export Software checkbox Click on Export Hardware checkbox Click on Export License checkbox
A Job is a series of activities (an activity executes a single task) that can be executed to fulfill a work order.
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
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 <Hostname> <IP address>
Job Manager
O&M activities
Handling with scripts
The Radio Network Optimisation application, is launched from the Main Menu in OSS: Applications Ericsson Performance Radio Network Optimisation
Recording is performed by
NCS New Recording wizard.
Cell Set is cell filter that is used to select group of cells or RNC on which measurements will be performed
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
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.
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
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
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
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.
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
RAN Optimization
activities: Neighbour relations, Identify antenna installation problems.
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.
GPEH file
RNO
performance assessment
RNO, performance
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 <proxy ID>
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 <logfile>.log file Default path for the saved log files is /moshell_log files/logs_moshell/sessionlog/<logfile>.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
MoShell (5/6)
MoShell Export Step-by-Step on RBS
Write lhget utrancell=all primaryCpichPower Write lhget utrancell=all maxTxPowerUl Write lhget utrancell=all maximumTransmissionPower
MoShell (6/6)
MoShell Export Step-by-Step on RBS
Write lhget AntFeederCable ulGain Write lhget AntFeederCable dlAttenuation Write lhget AntFeederCable ulAttenuation Write lhget sectorantenna antennaType Write lhget sectorantenna electricalAntennaTilt Write lhget sectorantenna mechanicalAntenaTilt
Prints UL gain of TMA/ASC Prints DL feeder loss Prints UL feeder loss Prints antenna type Prints electrical tilt value Prints mechanical tilt value as it was writen in the database
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
Contents
HUAWEI M2000 Client RNC LMT NodeB LMT ERICSSON Common components Technology-specific application suites
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
Parameter check
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
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
Consistency Check
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
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
TEI