4.nm oc04 e2 1 configuration application tools(v4)-83

8/12/2019 4.NM OC04 E2 1 Configuration Application Tools(V4)-83

1/42

Configuration Application Tools

ZTE University

Objects

To understand the definition of wireless

configuration application

To understand the functions of wireless


To master the common operations of wireless



2/42

Content

Overview of Wireless Configuration Application Definition of Wireless Configuration Application

Wireless Configuration Application Functions

Wireless Configuration Application Operations Batch Comparison of Interconnection Parameters

NE Relation Management

NE Stability Event Management

Operation & Maintenance Status Querying and Setting

VIP Node B Priority Management

Inventory Management

Base Station Transfer Management

Cell Tool Configuration Data Collection

Definition of Wireless ConfigurationApplication


3/42

Wireless Configuration Application FunctionsFunction Description

Batch Comparison of

Interconnection Parameters

Compare interconnection parameters

between RNCs and Node Bs in batch.

NE Relation Management Define the relation between the RNC and the interconnected Node B

manually.

NE Stability Event Management Query the stability events of the equipment during a period, and export the

query result as a report.

Operation & Maintenance Status

Querying and Setting

Query or set the status of a base station, such as normal, testing etc.

VIP Node B Priority Querying and

Setting

Query or set the priority of the node Bs.

Invenyory Management Manage the information of various boards uploaded from lower-level NMS

to the NetNumen M31 (RAN) network elements.

Base Station Transfer Platform Implement the transferring of base stations, including online transfer, offline

transfer and data export.

Cell Tool Provide check accord and check lone tools and offer systematic

modification and manual modification for inconsistency.

Configuration Data Collection This module is used to collect configuration data from each OMM and input

the data to the EMS.

Content










Cell Tool

Configuration Data Collection


4/42

Batch Comparison of Interconnection

Parameters

Comparing Interconnection Parameters inBatch Context

Compare the RNC with theinterconnected Node B to seewhether the parameters are inconsistency or not.

Steps Select [Configuration

Wireless ConfigurationApplication BatchComparison of InterconnectionParameters] in the main menuto open the InterNE Batch

Compare Option window. Select the product type, for

example, WCDMA, and clickthe button.

Select RNC-NODEB as thecomparison type, and click the button.


5/42

Comparing Interconnection Parameters in

Batch (continued)

Select the RNC to be

compared, and click the

button.

Comparing Interconnection Parameters inBatch (continued)

Select the Node B to be

compared, and click the

button to open the

InterNE Batch Compare

Result window.


6/42

Comparing Interconnection Parameters in

Batch (continued)

The detailed information of the interconnection

parameters camparison between the RNC and the

Node B are displayed on the tabs after the

Overview.

Content










Cell Tool



7/42


Click [ConfigurationWireless Configuration Application NERelation Management] in the main menu to enter the NE RelationManagement window.

Importing NE Relation Planning Data

Prerequisites You have started the client and successfully connected it to the NetNumen M31 (RAN) server.

NetNumen M31(RAN) server and the lower-level network elements are normally connected.

The NE Relation Management window is opened.

Context When you entering the NE Relation Management window for the first time, there is no

configuration data, and you need to import the network element relation data file manually. Theimported file is a .xls file.

Generally, the imported data file is written by the network administrator according to the actualrelation of equipment.

Steps Click the Import button in the NE Relation Management window to open the Input NE relation file

window.


8/42

Importing NE Relation Planning Data

(continued)

Click the button to open the Open window. Set the File

Location, File Name and File Type in the window. Click the

button to close the Open window.

Click the button in the Input NE Relationship dialog

box, the network element relation information in the file is

imported to the window.

Note:

If the imported data is the same with the existing data in the system,

an error message will appear.

Filtering NE Relation Data

Prerequisites

You have started the client andsuccessfully connected it to theNetNumen M31 (RAN) server.

NetNumen M31(RAN) serverand the lower-level networkelements are normallyconnected.

The NE Relation Managementwindow is opened.

Nework element relaiton dataalready exsit in the NE RelationManagement window.

Steps

Click the button in theNE Relation Managementwindow to open the NERelation Data Filter dialog box.


9/42

Filtering NE Relation Data (continued)

Select , , or in , to representGSM, TD-SCDMA and WCDMA products respectively.

Input the keywords in the OMM-R Name, OMM-R Subnet ID, OMM-RNE ID, OMM-B Name, OMM-B Subnet ID and OMM-B NE IDtextboxes.

Click the button to show the relations that satisfy all therequirements.

Deleting NE Relation Data


10/42

Exporting NE Relation Data

Content










Cell Tool



11/42


The object of NE Stability Event Manangement module are the NE boards. The NEmonitors the stability events on corresponding boards and timely records the messagesinto files. The NetNumen M31 (RAN) can be used to collect the original data of stabilityevents from each NE through scheduled task and set the weight of the events based onthe predefined rule and save them into the storage.

The system predefines the following three types of weight for different events andboards:

Entering the NE Stability Manager Window

Select [ConfigurationWireless Configuration Application NE Stability Event Management] in the main menu toopen the NE Stability Manager dialog box.


12/42

Querying the Stability Events of an NE

Exporting the Query Result of Stability Events


13/42

Exporting the Stability Report

Adding a Stability Event


14/42

Modifying a Stability Event

Deleting a Stability Event


15/42

Content











Introduction to Operation & MaintenanceStatus


16/42

Querying the Operation & Maintenance Status

Prerequisites You have started the client and successfully connected it to the NetNumen M31

(RAN) server

NetNumen M31 (RAN) server and the lower-level network elements are normallyconnected.

The Node Bs have been configured.

Steps: Click [ConfigurationWireless Configuration ApplicationOperation & Maintenance

Status Querying and Setting] in the Main Menu to open the Amo Select window.

Querying the Operation & Maintenance Status(continued)

Select the NE type to be checked according to your need.And the Maintain Status Query and Set window pops up.


17/42

Setting the Operation & Maintenance Status

Prerequisites You have started the client and

successfully connected it to theNetNumen M31 (RAN) server

NetNumen M31(RAN) serverand the lower-level networkelements are normallyconnected.

The Node Bs have beenconfigured.

The Maintain Status Query andSet window is opened.

Steps: In the Maintain Status Query

and Set window, select one line,or select continuous lines bydragging the mouse orpressing the shift key down, orselect individual lines bypressing down the ctrl key.Then right click the mouse, andselect Normal or Testing.

Setting the Operation & Maintenance Status(continued) The selected operation & maintenance status is changed. Click the

button to synchronize the modified operation & maintenance status on the NE.If the synchronization is succeeded, a window appears as the following.


18/42

Setting the Operation & Maintenance Status

(continued) After the operation, click the button to get the updated

operation & maintenance status information and verify the setting.

Exporting the Operation & MaintenanceStatus


19/42

Importing the Operation & Maintenance

Status

Content







VIP Node B Prior ity Management



Cell Tool



20/42

Introduction to Node B Priority

Base stations are classified into VIP, B-Class, C-Class and Normal Node B in

descending priority order.

You can get the alarm statistics of VIP, B-Class and C-Class base stations

separately in fault management module.

Querying the Priority of Node Bs

Prerequisites

You have started the client and

successfully connected it to the

NetNumen M31 (RAN) server


and the lower-level network

elements are normally

connected.

The Node Bs have been

configured.

Steps

Click [ConfigurationWireless

Configuration ApplicationVIP

Node B Priority Query and Set]

in the main menu to open the

Amo Select window.


21/42

Querying the Priority of Node Bs (continued)

Select the NE type to be queried, click the

button, the query result appears.

Setting the Priority of Node Bs

Prerequisites

You have started the client andsuccessfully connected it to theNetNumen M31 (RAN) server

NetNumen M31 (RAN) serverand the lower-level networkelements are normallyconnected.

The Node Bs have beenconfigured.

The VIP Node B Priority Setand Query window is opened.

Steps

Select one line or multiple linesin the VIP Node B PriorityQuery and Set window, rightclick the mouse, and select VIP,B Class, C Class or Normal inthe shortcut menu.


22/42

Setting the Priority of Node Bs (continued)

After the setting iscompleted, click the button toapply the settings onthe NE. And the resultis shown in the Resultcolumn.

After the operaiton,click the button to get theupdated information ofthe Node B priority atthe NE, thus to verifythe settings.

Exporting the Priority Information of Node Bs


23/42

Importing the Priority Information of Node Bs

Content










Cell Tool



24/42

Introduction to Inventory Management

Entering Inventory Management Window

Select [ConfigurationWireless ConfigurationApplicationInventory Management] in the mainmenu to open the Inventory Management] window.


25/42

Importing the Inventory Information from a

File

Exporting the Inventory Information to a File


26/42

Viewing SW and FW Inventory

Prerequisites You have started the client and successfully connected it to the NetNumen M31 (RAN) server


The Inventory Management window is opened.

Steps Select [ViewSW /FW Inventory] in the Inventory Management window to open the SW/FW

Inventory dialog box.

Viewing SW and FW Inventory (continued)

Click to show all software and firmware information in thesystem.


27/42

Synchronizing the Inventory Information of All

Subnets

Synchronizing the Inventory Information of aSubnet


28/42

Exporting the Inventory Information on

Schedule

Exporting the Inventory Information onSchedule (continued)

Steps

Click

[MaintenanceT

ask Management]

in the main menu

of NetNumen

M31 (RAN) to

open the Task

Management

window.


29/42

Exporting the Inventory Information on

Schedule (continued) In the Task Management Pane on the left of the Task management

window, select MMLTiming Task, then click the New Task button toopen the Create Task dialog box. Set Task Name, Task Descriptionand MML.

Exporting the Inventory Information onSchedule (continued)

Click the Policy tab, set Plan Types, Execution Time andDuration Period. Click to complete setting the timingtask.


30/42

Content











Introduction to Base Station TransferManagement


31/42

Entering the Base Station Transfer

Management Window Select [ConfigurationWireless Configuration ApplicationBase

Station Transfer Management] in the main menu of NetNumenM31(RAN) to open the Transfer Base Station window.

Exporting the Data of the Base Station


32/42

Transferring a Base Station Online

Transferring a Base Station Offline

Prerequisites You have started the client and successfully connected it to the NetNumen M31 (RAN) server.


The Base Station Transfer window is opened.

The transfer plan file (*.xls) is available, which contains the information of the destination node.

The ZIP file is available, containing the configuration information of the source base station.

Context To transfer a source base station to the designated destination node according to the

configuration information of the source base station in the designated ZIP file. The information ofthe source base station will be deleted if the source base station is managed by the NetNumenM31 (RAN) system.

The Offline Transfer function can be used for transferring a base station managed by aNetNumen M31 (RAN) system to another NetNumen M31 (RAN) system.

Steps Click the button in the Transfer Base Station window to open the Open dialog box. In the Open dialog box, select the Location, File Name and File Type of the transfer plan file.

Click the button, the name of the selected transfer plan file is shown in the File Pathtextbox.

Select Offline Transfer from the Base Station Operation drop-down menu.

Select the Binding Mode according to the NE type.

If needed, select to delete the configuration information of the source base station.


33/42

Transferring a Base Station Offline (continued)

Click the button to open the Offline

Data dialog box.

Transferring a Base Station Offline (continued)

Click the button to openthe Open dialog box, select the ZIPfile that contains the source basestation information, and then clickthe button. The sourcebase station information is shown .

In the Site Info drop-down menu,select the Base Station Name to beviewedthen click the button, the information of theselected base station is shown inthe window.

Click to start transferring theconfiguration data of source basestation from the ZIP file to thedestination node. The configurationinformation of the source basestation will be deleted if the sourcebase station is managed by theNetNumen M31 (RAN) system.


34/42

Viewing the Base Station Transfer Result

Viewing the Base Station Transfer Result(continued) Click the button in the Transfer Base Station window to open the Result

Data dialog box.

Select the result type to be viewed from the Result Type drop-down menu. The resultinformation is shown in the list.


35/42

Halting the Transferring of a Base Station

Content










Cell Tool



36/42

Introduction to Cell Tool

Functions of the Cell Tool:

Check Lone

Prerequisites You have started the client and successfully connected it to the NetNumen M31

(RAN) server NetNumen M31(RAN) server and the lower-level network elements are normally

connected.

Steps: In the main Menu, select [ConfigurationWireless Configuration

ApplicationNeighbor Cell Tool] to open the Cell Tool dialog box.


37/42

Check Lone (continued)

Select Check Lone as the check type. Set the Product

Type in the parameter settings. Then select the subnet to

be checked.

Click the button after the Result File Location

textbox to open the Save dialog box. Set the Save In and

File Mame, and click the button.

Return to the Relation Cell dialog box and click the

button. The system starts checking the

neighbor cell relation and saves the check result in a

designated file. And the information of the check operationappears in the Result Information column.

Check Lone (continued)

Right click Result Information. Select Diplay

Result from the shortcut menu to show the

Operation Result dialog box.

Select the record to be modified. Click the

button, the system

strarts to execute consistency modification. And

the modification result is shown in the ResultInformation column in the Cell Tool.

Click the button in the Operation Result

dialog box to export the check result to a

designated file.


38/42

Importing External Modification Parameters

Content










Cell Tool



39/42

Introduction to Configuration Data Collection

Creating a Template

Select [ConfigurationConfiguration Data CollectionTemlate Management]in the main menu to enter the Template Management window.


40/42

Creating a Template (continued)

Click the Create

Template icon on

the toolbar of the

Temlate

Management window

to open the Create

Template dialog box.

Set parameters and

click the

button.

Getting Report

Prerequisites

You have started the client and successfully connected it to the


NetNumen M31(RAN) server and the lower-level network elements

are normally connected.

You have created the collection template.

Context

Collect the configuration data from each OMM. Send the data to

the EMS server and extract the data to a CSV file at the desiganteddirectory on EMS client.

Steps

Select [ConfigurationConfiguration Data CollectionReport

Management] in the main menu to enter the Configuration Report

management window.


41/42

Getting Report (continued)

Click the Get Report icon on the Configuration Report

Management toolbar to open the Get Report dialog box.

Getting Report (continued)

Select NE Type, RND-ID

and Template. Click the

button. The system

starts to collect

configuration data from

designated location and

generate a summary file.

The file information is

shown in the List of files.


42/42

4.nm oc04 e2 1 configuration application tools(v4)-83

Documents