U31 R18 Configuration Application Operation Guide

NetNumen U31 R18Unified Element Management System

Configuration Application Operation Guide

Version: V12.12.43

ZTE CORPORATIONNo. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright 2013 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2013-06-20 First edition

Serial Number: SJ-20130524154927-012

Publishing Date: 2013-06-20 (R1.0)

SJ-20130524154927-012|2013-06-20 (R1.0) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Wireless Configuration Application Overview....................... 1-1

1.1 Functions........................................................................................................... 1-1

1.2 Implicit Prerequisites .......................................................................................... 1-3

Chapter 2 Wireless Configuration Application Operations .................... 2-1

2.1 Interconnection Parameter Management ............................................................. 2-1

2.1.1 Comparing Interconnection Parameters in Batches .................................... 2-2

2.1.2 Modifying Interconnection Parameters in Batches ...................................... 2-4

2.2 NE Relation Management ................................................................................... 2-6

2.2.1 Filtering NE Relations............................................................................... 2-6

2.2.2 Exporting NE Relations to an XLS File....................................................... 2-8

2.3 NE Stability Management.................................................................................... 2-8

2.3.1 Managing Stability Events....................................................................... 2-10

2.3.2 Managing Maintenance Plans ................................................................. 2-15

2.4 Base Station Status Management ..................................................................... 2-19

2.4.1 Querying Base Station Statuses.............................................................. 2-20

2.4.2 Setting the Status of a Base Station ........................................................ 2-23

2.4.3 Exporting Base Station Statuses ............................................................. 2-25

2.4.4 Importing Base Station Statuses.............................................................. 2-26

2.5 Base Station Priority Management..................................................................... 2-27

2.5.1 Querying Base Station Priorities .............................................................. 2-28

2.5.2 Setting the Priority of a Base Station........................................................ 2-30

2.5.3 Exporting Base Station Priorities ............................................................. 2-31

2.5.4 Importing Base Station Priorities.............................................................. 2-32

2.6 Site Transfer .................................................................................................... 2-33

2.6.1 Exporting Configuration Data of a Source Site.......................................... 2-35

2.6.2 Transferring an Online Site ..................................................................... 2-36

2.6.3 Transferring an Offline Site ..................................................................... 2-36

2.6.4 Viewing Operation Results Related to Site Transfer .................................. 2-38

2.6.5 Halting a Site Transfer Process ............................................................... 2-39

2.7 Inter-Element Configuration Data Import and Export ........................................... 2-40

2.7.1 Exporting Configuration Data .................................................................. 2-40

2.7.2 Importing Configuration Data................................................................... 2-43

I


2.8 Neighbor Cell Tool ............................................................................................ 2-44

2.8.1 Verifying Attributes Consistency .............................................................. 2-45

2.8.2 Importing Modified Attributes................................................................... 2-48

2.9 User Label Relation Management ..................................................................... 2-49

2.9.1 Verifying User Label Consistency ............................................................ 2-49

2.10 Cell Maintenance Status Management............................................................. 2-52

2.10.1 Querying Cell Statuses ......................................................................... 2-52

2.10.2 Setting Cell Statuses ............................................................................ 2-53

2.11 Cell Broadcast Management ........................................................................... 2-55

2.11.1 Short Message Status........................................................................... 2-55

2.11.2 Opening the CBC Management Window ................................................ 2-57

2.11.3 Channel Management........................................................................... 2-57

2.11.4 Cell Management ................................................................................. 2-59

2.11.5 Area Management ................................................................................ 2-64

2.11.6 Short Message Management................................................................. 2-66

2.12 Configuration Data Collection .......................................................................... 2-75

2.12.1 Creating a Configuration Data Collection Template ................................. 2-76

2.12.2 Collecting Configuration Data ................................................................ 2-78

2.13 Radio Configuraiton Data Import ..................................................................... 2-80

2.13.1 Overview ............................................................................................. 2-80

2.13.2 Importing Radio Configuration Data ....................................................... 2-81

2.14 GSM BCCH Frequency Scheduling Tool .......................................................... 2-82

2.14.1 Importing the Frequency List ................................................................. 2-83

2.14.2 Generating a Scheduled Task................................................................ 2-85

2.15 TD Carrier Frequency Maintenance Management............................................. 2-87

2.15.1 Querying the Maintenance Status of a Carrier Frequency........................ 2-88

2.15.2 Setting the Maintenance Status of a Carrier Frequency........................... 2-90

Figures............................................................................................................. I

Tables .............................................................................................................V

Glossary .......................................................................................................VII

II


About This ManualPurpose

This manual provides instructions for the centralized configuration and maintenance ofradio access network products in the NetNumenTM U31 R18 Unified Element ManagementSystem (NetNumen U31).

Intended Audience

This manual is intended for:

l Maintenance engineersl Network planning and optimization engineers

What Is in This Manual

This manual contains the following chapters:

Chapter Summary

1, Wireless Configuration

Application Overview

Provides an overview of the wireless configuration application

module in the NetNumen U31 system, including supported

functions and radio access systems.

2, Wireless Configuration

Application Operations

Describes how to use the wireless configuration application

module for centralized configuration and maintenance.

Related Documentation

The following documentation is related to this manual:

l NetNumen U31 R18 Unified Element Management System Topology ManagementOperation Guide

l NetNumen U31 R18 Unified Element Management System MML CommandReference

Conventions

This manual uses the following typographical conventions:

Typeface Meaning

Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.

Note: provides additional information about a certain topic.

I


II


Chapter 1Wireless ConfigurationApplication OverviewThe NetNumen U31 system provides a wireless configuration application module thatsupports centralized configuration and maintenance of radio access network products. Aconfiguration or maintenance operation may be required on multiple Network Elements(NEs) at the same time. Such inter-NE operation cannot be completed by individualOperation & Maintenance Modules (OMMs) of these NEs. The wireless configurationapplication module can be used to implement interNE configuration and maintenanceoperations in a centralized manner.

Table of Contents

Functions ...................................................................................................................1-1Implicit Prerequisites ..................................................................................................1-3

1.1 FunctionsFor a description of the functions supported by the wireless configuration applicationmodule, refer to Table 1-1.

Table 1-1 Wireless Configuration Application Functions

Function Description

Interconnection parameter

management

Compares interconnection parameters in batches between a

BSC/RNC and corresponding BTSs/Node Bs, and modifies

inconsistent interconnection parameters in batches.

NE relation management Manages the relations between a BSC/RNC and the BTSs/Node

Bs under its control.

NE stability management l Queries stability events occurring in an NE during a period

and exports the query results as a stability report.

l Adds the information of an NE maintenance plan to exclude

the stability events occurring during maintenance in the

stability report.

Base station status management Queries, sets, imports, and exports base station statuses.

Base station priority management Queries, sets, imports and exports base station priorities.

Inventory management Manages the hardware, software, and firmware inventory

uploaded from NEs.

1-1


NetNumen U31 R18 Configuration Application Operation Guide

Function Description

Site transfer Supports online and offline site transfer.

Inter-element configuration data

import and export

Exports and imports configuration data in file format between

different NEs for quick configuration.

Neighbor cell tool Verifies the consistency of attributes between an OMM and

related external cells to ensure correct neighbor relations, and

verifies the integrity of neighbor relations for a cell.

User label relation management Verifies the consistency between the user labels of local cells

and those specified in neighbor relations.

Cell broadcast management Provides management functions for the cell broadcast

service, including channel management, cell management,

area (broadcast domain) management, and short message

management.

Cell status management Queries and sets cell statuses.

Configuration data collection Collects configuration data of NEs from corresponding OMMs.

Radio configuration data import Imports radio configuration data from a predefined XML file to

specific NEs.

Note:

l BSC = Base Station Controller

l RNC = Radio Network Controller

l BTS = Base Transceiver Station

l CBC = Cell Broadcast Center

The available wireless configuration application functions vary with different radio accesssystems. For a description of supported functions for different systems, refer to Table 1-2.

Table 1-2 Supported Functions for Different Radio Access Systems

Function UMTS GSM GSM-R LTE-TDD LTE-FDD TD-SCDMA

Interconnection

parameter

management

- - -

NE relation

management

NE stability

management

Base station status

management

Base station priority

management

1-2


Chapter 1 Wireless Configuration Application Overview

Function UMTS GSM GSM-R LTE-TDD LTE-FDD TD-SCDMA

Inventory management

Site transfer - - -

Inter-element

configuration data

import and export

- -

Neighbor cell tool - -

User label relation

management - - - -

Cell broadcast

management - - - - -

Cell status

management- - - - -

Configuration data

collection - - -

Radio configuration

data import - - - -

Note:

l UMTS = Universal Mobile Telecommunication System

l GSM = Global System for Mobile communication

l GSM-R = GSM for Railway

l LTE-TDD = Long Term Evolution-Time Division Duplex

l LTE-FDD = Long Term Evolution-Frequency Division Duplex

l TD-SCDMA = Time Division-Synchronization Code Division Multiple Access

"" indicates that the function is supported for the radio network system. "-" indicates that the function is not supported for the radio network system.

1.2 Implicit PrerequisitesFor all operations subsequent to this section, the following prerequisites are presumed tohave been met:

l The NetNumen U31 client has been started and successfully connected to the server.l The communication between the NetNumen U31 server and managed NEs is normal.l Users have successfully started the NE agent of the NEs that are to be configured or

maintained.l The permissions for wireless configuration application operations have been acquired.

1-3



This page intentionally left blank.

1-4


Chapter 2Wireless ConfigurationApplication OperationsTable of Contents

Interconnection Parameter Management....................................................................2-1NE Relation Management ..........................................................................................2-6NE Stability Management ...........................................................................................2-8Base Station Status Management ............................................................................2-19Base Station Priority Management ...........................................................................2-27Site Transfer.............................................................................................................2-33Inter-Element Configuration Data Import and Export.................................................2-40Neighbor Cell Tool ....................................................................................................2-44User Label Relation Management ............................................................................2-49Cell Maintenance Status Management .....................................................................2-52Cell Broadcast Management ....................................................................................2-55Configuration Data Collection ...................................................................................2-75Radio Configuraiton Data Import ..............................................................................2-80GSM BCCH Frequency Scheduling Tool ..................................................................2-82TD Carrier Frequency Maintenance Management ....................................................2-87

2.1 Interconnection Parameter ManagementThe interconnection parameter management allows users to compare and modifyinterconnection parameters in batches to ensure parameter consistency between a BaseStation Controller (BSC)/Radio Network Controller (RNC) and the Base TransceiverStations (BTSs)/Node Bs under its control in a GSM, UMTS, or TD-SCDMA network.

Note:

Before performing interconnection parameter management, users must specify theBSC/RNC to which each BTS/Node B belongs in the NetNumen U31 system.

2-1



2.1.1 Comparing Interconnection Parameters in BatchesThis procedure describes how to compare the interconnection parameters between anRNC and the Node Bs under its control in a UMTS network to verify the consistency of theinterconnection parameters.

Prerequisite

Users have specified the RNC to which each Node B belongs in the NetNumen U31system.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > InterNE Compare from the menu bar. The InterNE Manage Optiondialog box is displayed, see Figure 2-1.

Figure 2-1 InterNE Manage Option Dialog BoxSelecting the Product Type

2. Select the product type (for example, TD-SCDMA), and click Next. The availableoperations are displayed, see Figure 2-2.

2-2


Chapter 2 Wireless Configuration Application Operations

Figure 2-2 InterNE Manage Option Dialog BoxSelecting the Management Type

3. Select Compare, and then click Next. An NE tree containing all managed RNCs inthe system is displayed, see Figure 2-3.

Figure 2-3 InterNE Manage Option Dialog BoxSelecting RNCs

4. Select the required RNCs, and then click Next. The selected RNCs and the Node Bsunder its control are displayed in the NE tree, see Figure 2-4.

2-3



Figure 2-4 InterNE Manage Option Dialog BoxSelecting the NODEBs

5. Select the required NodeBs, and then click OK. The InterNE Batch Compare Resultdialog box is displayed.

6. Expand the NE tree in the left pane, and select the RNC. The comparison result ofinterconnection parameters between the RNC and the selected Node Bs is displayedon the Statistics tab in the right pane.

Note:

In the Comparative result (Y/N) column, Y indicates consistent interconnectionparameters, and N indicates inconsistent interconnection parameters.

7. To show the comparison details of the interconnection parameters between a specificNode B and the RNC, click the tab corresponding to the Node B ID.

8. To export the comparison result to an XLS file, do the following:

a. In the InterNE Batch Compare Result dialog box, click Export. The Save dialogbox is displayed.

b. Select a directory for saving the comparison result, enter a file name, and thenclick Save. A message confirming the successful data export is displayed.

An XLS file containing the comparison result is available in the selected directory.Users can open the XLS file to view the interconnection parameters exported from thesystem.

End of Steps

2.1.2 Modifying Interconnection Parameters in BatchesThis procedure describes how to modify inconsistent interconnection parameters betweenan RNC and the controlled Node Bs in a UMTS network.

2-4



Note:

The interconnection parameter modification function is only available for UMTS andTD-SCDMA products.

Prerequisite

Users have compared the interconnection parameters between the RNC and the Node Bsand exported the comparison results to an XLS file.

Steps

1. Open the XLS file containing the comparison results.

2. Modify inconsistent parameters, and change the modification status corresponding tothe modified parameters to "Y".

3. Save and close the XLS file.

4. In the client window, select Configuration > Common Wireless ConfigurationApplication > InterNE Compare from the menu bar. The InterNE Manage Optiondialog box is displayed.

5. Select UMTS, and then click Next.

6. Select Modify, and then click Next. The InterNE Modify dialog box is displayed, seeFigure 2-5.

Figure 2-5 InterNE Modify Dialog Box

7. Click . The Open dialog box is displayed.

8. Select the directory where the modified XLS file is saved, click the XLS file, and thenclick Open. The selected file path is displayed in the InterNE Modify dialog box.

9. Click OK. The InterNE Batch Compare Result dialog box is displayed, showing themodification results of interconnection parameters between the RNC and differentNode Bs on separate tabs.

End of Steps

2-5



2.2 NE Relation ManagementIn the NetNumen U31 system, a BSC/RNC and the BTSs/Node Bs under its control canbe deployed separately. For example, an RNC is configured and maintained by an OMM,but a Node B under its control is managed by another OMM. Considering this possibility,users are required to add an NE relation for each BTS/Node B in the system. The NErelation specifies which BSC/RNC is used to control a BTS/Node B.

The NE relation management allows users to view, filter, and export the NE relationsbetween BSCs/RNCs and BTSs/Node Bs managed by the NetNumen U31 system.

2.2.1 Filtering NE RelationsThis procedure describes how to filter out specific NE relations in the system.

Prerequisite

l The NE Relation Management dialog box is displayed.l The NE relation has been configured in the NE Relation Management dialog box.

Steps

1. Click Filter. The NE Relation Data Filter dialog box is displayed, see Figure 2-6.

2-6



Figure 2-6 NE Relation Data Filter Dialog Box

2. Set the related parameters. For a description of the parameters, refer to Table 2-1.

Table 2-1 Description of NE Relation Filtration Parameters

Parameter Description

Product Options:

l GSM

l TD

l UMTS

l All

In this example, All is selected.

OMM-R Name/OMM-R SubnetWorkID/OMM-R

NE ID/OMM-B Name/OMM-B

SubnetWorkID/OMM-B NEID

Set the filtration keywords.

In this example, set OMM-B NEID to 8.

3. Click OK. All NE relations related to the subnets whose IDs contain the keyword "7"are displayed in the NE Relation Management dialog box, see Figure 2-7.

2-7



Figure 2-7 NE Relation Filtration Results

4. To show all NE relations in the NE Relation Management dialog box again, clickFilter, select All from the Product list, clear all filtering keywords, and then click OK.

End of Steps

2.2.2 Exporting NE Relations to an XLS FileThis procedure describes how to export NE relations from the NetNumen U31 system toan XLS file.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > NE Relation Management. The NE Relation Management dialogbox is displayed, showing all NE relations specified in the system.

2. Click Export. The Save dialog box is displayed.

3. Select a directory for saving the exported NE relations, enter a file name, and then clickSave. A message confirming the successful export of the NE relations is displayed.

4. ClickOK. An XLS file containing the NE relations is generated in the selected directory.

End of Steps

2.3 NE Stability ManagementThe NetNumen U31 system collects stability events from all managed NEs, storesthe collected events in the database, and generates statistical reports as required.The collected events include those occurring during maintenance. Users can add themaintenance information in the system to exclude the events during maintenance fromthe stability report because these events do not reflect the actual stability of NEs.

The following explains two concepts involved in NE stability management: stability eventand maintenance plan.

2-8



Stability Event

A stability event refers to a failure event occurring in a board of an NE that influencesthe NE stability. An NE collects stability events from all its boards and sends the collectedinformation to the alarm mail box of the NetNumen U31 system. The stability managementapplication monitors the alarm mail box in real time and determines the severity level ofeach stability event in accordance with the weight of board type and the weight of boardredundancy mode.

l Weight of board type

The system sets the weight of board type for an event depending on the type of theboard where the event occurs. Boards in an NE are classified into two types: interfaceboard and processing board. The weight of a processing board event is higher thanthat of an interface board event.

l Weight of board redundancy mode

The system sets the weight of board redundancy mode for an event depending onthe redundancy mode of the board where the event occurs, the quantity of redundantboards, board type, and bandwidth. A board supports various redundancy modes,including no redundancy, 1+1 backup, and load sharing. The weight of boardredundancy of an event that occurs in a board configured with no redundancy modeis higher than the weight of an event that occurs in a board configured with the 1+1backup or load sharing mode.

The system defines three severity levels in descending order: All, Part, and Light. Forexample, the severity level (All) of an event reported by a processing board (higher weightof board type) in no redundancy mode (higher weight of board redundancy) is higher thanthe severity level (Light) of an event reported by an interface board (lower weight of boardtype) in redundancy mode (lower weight of board redundancy).

The system can count the duration of stability events occurring in an NE during a periodby severity level and generate an NE stability report. The statistical result in the reportcontains the following four parts:

l Total duration of stability events at the severity level "All"l Total duration of stability events at the severity level "Part"l Total duration of stability events at the severity level "Light"l Total duration of stability events occurring during maintenance

Maintenance Plan

The stability of an NE may be influenced during routine NE maintenance. The stabilityevents occurring during maintenance should be neglected to ensure appropriateevaluation of the NE stability. Users can specify a maintenance plan in the system,including the start time, end time, involved NE type, maintenance operations, andmaintenance objects, to exclude the stability events occurring during the maintenance.When generating an NE stability report, the system does not count the events occurringduring the maintenance.

2-9



2.3.1 Managing Stability Events

2.3.1.1 Querying Stability Events

This procedure describes how to query stability events received by the NetNumen U31system during a specific period.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > NE Stability Management. The NE Stability Management dialogbox is displayed, see Figure 2-8.

Figure 2-8 NE Stability Management Dialog Box (Stability Event Tab)

2. From the Begin Time list, select a start date in the pop-up calendar, and then clickOK.

3. From the End Time list, select an end date in the pop-up calendar, and then click OK.

4. Select a time zone from the Time Zone list.

5. Click Search. The stability events during the specified period are displayed on theStability Event tab, see Figure 2-9.

2-10



Figure 2-9 Stability Event Query Result

The Event Class column shows the original classes of the alarms corresponding tothe events reported by the NEs. The classes will be updated in the report generatedafter NE stability is analyzed.

End of Steps

2.3.1.2 Exporting Stability Events

This procedure describes how to export stability events to an XLS file.

Prerequisite

Users have successfully queried the stability events to be exported in the NE StabilityManagement dialog box.

Steps

1. In the NE Stability Management dialog box, click Export Result on the StabilityEvent tab. The Save dialog box is displayed.

2. Select a directory for saving the stability events, enter a file name, and then click Save.A message confirming the successful export of the stability events is displayed.

3. Click OK. An XLS file containing the exported stability events is generated in theselected directory.

End of Steps

2.3.1.3 Exporting an NE Stability Report

This procedure describes how to export the stability events during a specific period as anNE stability report to an XLS file.

Prerequisite

Users have successfully queried the stability events during the period in the NE StabilityManagement dialog box.

2-11



Steps

1. In the NE Stability Management dialog box, click Export Report on the StabilityEvent tab. The Save dialog box is displayed.

2. Select a directory for saving the NE stability report, enter a file name, and thenclick Save. A message confirming the successful export of the NE stability report isdisplayed.

3. Click OK. An NE stability report in XLS format is generated in the selected directory.

4. To view the contents in the NE stability report, double-click the XLS file. The NEstability report is displayed, see Table 2-2.

Table 2-2 NE Stability Report

NE Stability Report

NE IDAll-Break

Time(s)

Part-

Break

Time(s)

Light-

Break

Time(s)

Instability

Time(s)

Planned

Instability

Time

Stability

Percent

Stability

Percent

(Planned

Except)

Useless

Time

in Year

(minute)

BSC1-1 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

BSC10-10 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

BSC1023-1023 7562.00 0.00 0.00 7562.00 0.00 99.743% 99.743% 126.00

BSC1024-1024 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

BSC11-11 80119.00 0.00 0.00 80119.00 0.00 97.273% 97.273% 1335.31

BSC12-12 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

BSC123-123 12062.00 0.00 0.00 12062.00 0.00 99.589% 99.589% 201.03

BSC133-133 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

BSC135-135 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

BSC14-14 0.00154927

.120.00 38731.78 0.00 98.682% 98.682% 0.00

BSC15-15 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

BSC151-151 0.00 0.00 0.00 0.00 0.00100.000

%

100.000

%0.00

2-12



Begin Date (Asia/Shanghai)2012-

04-25End Date (Asia/Shanghai) 2012-04-25

End of Steps

2.3.1.4 Generating NE Stability Reports on Schedule

In the NetNumen U31 system, a Man Machine Language (MML) task can be created forperiodic generation of required NE stability reports.

This procedure describes how to schedule an MML task for generating NE stability reportsweekly.

Steps

1. In the client window, select Maintenance > Task Management from the menu bar.The Task Management window is displayed.

2. In the left pane, click the MML Timing Task node in the Task Management tree, andthen click on the toolbar. The Create Task dialog box is displayed, see Figure 2-10.

Figure 2-10 Create Task Dialog BoxBasic Information Tab

3. On the Base Information tab, perform the following operations:

a. In Task Name, enter a task name.

b. From Task Status, select Active.

c. In Task Description, enter additional information for the new task as needed.

d. Click Edit Command.

e. Under MML, enter an appropriate MML command for generating an NE stabilityreport.

2-13



The following describes the MML command used for report generation.

MINOS CMD:TYPE="STABILITYREPORT"[,ATTRIB="period&path"]

The command is case-insensitive. For a description of two input parameters(period and path) in the command, refer to Table 2-3.

Table 2-3 Command Parameter Descriptions


period (Optional) Specifies the period during which the stability events are

required for report generation.

Unit: day

Default value: 1

Example: Set the parameter value to 7. Then the system queries the

stability events occurring in the previous seven days and generates an

NE stability report based on the query result.

path (Optional) Specifies the path for saving the generated NE stability reports.

Note: If the value of this parameter is null, the system saves the NE

stability reports in \ums-server\rundata\ftp\stability\ne\

by default.

The parameter value format varies with different operating systems on

the NetNumen U31 server.

l Windows: The double-backslash (\\) is used as the delimiting

character in the path, for example, D:\\EXPORT.

l Linux or UNIX: The slash (/) is used as the delimiting character in

the path, for example, /export/home/omc/netnumen/ums-ser

ver/rundata/ftp/stability/ne.

4. Click the Policy tab. The schedule parameters are displayed, see Figure 2-11.

2-14



Figure 2-11 Create Task Dialog BoxPolicy Tab

5. On the Policy tab, perform the following operations:

a. Under Plan Type, select Weekly from the list, and then select Monday.

b. Under Execution Time, enter the time when the task shall be run on the specifiedday, for example, 00:00:00.

c. Under Duration, set an effective period for the task or use the default start date(current date).

6. Click OK. The MML task for generating stability reports is displayed in the TaskManagement window. The system generates an NE stability report based on thestability events occurring in the previous seven days every Monday and saves thegenerated report in the required path.

End of Steps

2.3.2 Managing Maintenance Plans

2.3.2.1 Adding a Maintenance Plan

If an NE or board is involved in a maintenance plan, users can specify the maintenanceinformation in the NetNumen U31 system to exclude stability events caused bymaintenance operations so as to ensure the accuracy of corresponding NE stability report.

This procedure describes how to add a maintenance plan in the NetNumen U31 system.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > NE Stability Management from the menu bar. The NE StabilityManagement dialog box is displayed.

2-15



2. Click the Maintain Plan tab. The Maintain Plan tab is displayed, see Figure 2-12.

Figure 2-12 NE Stability Management Dialog BoxMaintain Plan Tab

3. Click the Add Plan button, or right-click a row in the maintenance plan list and selectAdd Plan from the shortcut menu. The Add Maintain Plan dialog box is displayed,see Figure 2-13.

Figure 2-13 Add Maintain Plan Dialog Box

2-16



4. Set required parameters in accordance with the actual maintenance information.

Note:

The start date of a maintenance plan cannot be earlier than the current date. Inaddition, a new maintenance plan cannot overlap with an existing plan.

For a description of the parameters in theAddMaintain Plan dialog box, refer to Table2-4.

Table 2-4 Parameter Descriptions for the Add Maintain Plan Dialog Box


Begin Time Start time of the maintenance plan

End Time End time of the maintenance plan

Time Zone Time zone for determining the start time and end time of the maintenance

plan

Operation Type Select the operation type, meaning the type of the object on which

maintenance operations are to be performed.

The options are: NE and Board.

NE Select the NE to be maintained.

The optional NEs are displayed in the format of "NE type-Subnetwork

ID-NE ID", for example, BSC1010.

Operation Object Select the object on which maintenance operations are to be performed.

The object display format depends on the operation type.

l If the operation type is NE, the optional objects are displayed in the

format of "Subnetwork ID-NE ID", for example, 280280.

l If the operation type is Board, the optional objects are displayed in

the format of "Rack No.-Shelf No.-Slot No.", for example, 1211.

Operation Description Maintenance plan description

Service Impacting Whether the maintenance plan affects services

Default: Yes

Emergency Whether the maintenance plan is urgent

Default: Yes

Roolback Whether the system can be restored when the maintenance plan fails

Default: Yes

Closure State Whether all maintenance operations in the plan are completed during

the specified period

Default: Yes

Comments Additional information about the maintenance plan

2-17



5. Click OK. A confirmation box is displayed, prompting the successful creation of themaintenance plan and asking users whether to add another maintenance plan.

6. Click No. The added maintenance plan is displayed on the Maintain Plan tab.

End of Steps

Related Task

Users can modify or delete the added maintenance plan as required.

2.3.2.2 Querying Maintenance Plans

This procedure describes how to query maintenance plans that have been added in theNetNumen U31 system by operation type and start date.

Steps


2. Click the Maintain Plan tab.

3. From Operation Type, select an operation type: NE, Board, or All.

4. From Start Date, select a date and click OK.

5. From Time Zone, select a time zone as required.

6. Click Search. The maintenance plans meeting the query conditions are displayed onthe Maintain Plan tab.

End of Steps

2.3.2.3 Exporting Maintenance Plans

This procedure describes how to export maintenance plans to an XLS file.

Prerequisite

Users have successfully queried the maintenance plans to be exported in the NE StabilityManagement dialog box.

Steps

1. In the NE Stability Management dialog box, click Export Result on the MaintainPlan tab. The Save dialog box is displayed.

2. Select a directory for saving the maintenance plans, enter a file name, and then clickSave. An XLS file containing the exported maintenance plans is generated in theselected directory.

End of Steps

2-18



2.3.2.4 Importing Maintenance Plans

This procedure describes how to add maintenance plans to the NetNumen U31 system byimporting a predefined XLS file.

Note:

An XLS file containing exported maintenance plans can be used as a template for editingmaintenance plans to be imported.

Prerequisite

The XLS file to be imported is available and has an appropriate content structure.

Steps


2. Click the Maintain Plan tab, and then click the Import button. The Open dialog boxis displayed.

3. Select the directory where the XLS file is saved, click the XLS file, and then clickOpen.A message confirming the successful import of the maintenance plans is displayed.

End of Steps

2.4 Base Station Status ManagementA base station works in one of the following four statuses:

l Normal status

The base station operates properly.

l Testing status

The base station is under test or maintenance. In this status, large amounts of alarmsare generated. All or some alarm and performance data generated during the test ormaintenance are not reported to the NetNumen U31 system.

The testing status does not influence the reporting of configuration data.

l Fault Management (FM) testing status

The base station does not report all or some alarm data to the NetNumen U31 system.

l Performance Management (PM) testing status

The base station does not report all or some performance data to the system.

Base station status management supports the following operations:

2-19



l Querying base station statusesl Setting base station statusesl Exporting the query results of base station statusesl Importing base station statuses

2.4.1 Querying Base Station StatusesThis procedure describes how to query the statuses of specific base stations in a GSMnetwork.

Note:

For base stations (Node Bs) in a UMTS network, the statuses of the related RNCs are alsodisplayed in the query result.

Prerequisite

l The base stations have been configured in the NetNumen U31 system.l The connections between the base stations and the corresponding BSCs (OMMs) are

normal.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > Maintain Status Query and Setting from the menu bar. TheMaintainStatus Query and Setting dialog box is displayed, see Figure 2-14.

2-20



Figure 2-14 Maintain Status Query and Setting Dialog Box

In the topology tree, each Managed Element (ME) is identified by a string combiningME name and ME ID. Users can query the statuses of specific base stations by MEname and/or ID.

l If = is selected, the system queries the status of each base station with an MEname or ID that is the same as the entered keyword.

l If like is selected, the system queries the status of each base station with an MEname or ID containing the entered keyword.

Note:

If users set multiple query conditions related to ME name and ID, the system queriesthe statuses of base stations whose ME name and ID meet all the query conditions.

If users do not set any query condition, the system queries the statuses of all basestations belonging to the selected subnet.

2. In the EMS Server tree, click a subnet or an NE.

3. Click the status to be queried: All, Normal, Testing, FM Testing, or PM Testing.

4. Select = or like from the ME ID list, enter a keyword (for example, 1) in the text box,and then click Add. The query conditions are displayed in the lower area, see Figure2-15.

2-21



Figure 2-15 Query Conditions

5. Select = or like from the ME Name list, enter a keyword in the text box, and then clickAdd. The query conditions are displayed in the lower area.

6. Click OK. The base station statuses meeting the query conditions are displayed in theMaintain Status Query and Setting dialog box.l If an NE is selected in the EMS Server tree, see Figure 2-16 for the displayed

dialog box.l If a subnet is selected in the EMS Server tree, see Figure 2-17 for the displayed

dialog box.

Figure 2-16 Query Results of Base Station Statuses (with NodeB Office Information)

2-22



Figure 2-17 Query Results of Base Station Statuses (without NodeB OfficeInformation)

For a description of the buttons in the dialog box, refer to Table 2-5.

Table 2-5 Buttons in the Maintain Status Query and Setting Dialog Box

Button Description

Execute Sets the status of a base station.

Export Exports the query results to an XLS file.

Import Sets the statuses of base stations by importing an XLS file.

Refresh Refreshes the base station statuses in the query result.

Option Resets query conditions to initiate another query.

Close Closes the dialog box.

End of Steps

2.4.2 Setting the Status of a Base Station

Context

Users can set the status of one or multiple base stations as required.

The following procedure describes how to set the status of a base station from "Normal"to "Testing".

Prerequisite

l Users have successfully queried the status of the base station, and the query resultis displayed in the Maintain Status Query and Setting dialog box.

l The connection between the base station and the NetNumen U31 server is normal.

2-23



Steps

1. In the Maintain Status Query and Setting dialog box, click a row and right-click onthe selected row. A shortcut menu is displayed, see Figure 2-18.

Figure 2-18 Shortcut Menu for Setting Base Station Status

Note:

To set the statuses of multiple base stations to the same status at a time, users canpress and hold the Ctrl or Shift key while selecting each base station to be set.

2. Select Testing from the shortcut menu.

3. Click Execute. The Setting Reason dialog box is displayed, see Figure 2-19.

Figure 2-19 Setting Reason Dialog Box

4. Enter the reason for setting the base station status, and then click OK. A messageconfirming the successful execution of the status setting command is displayed.

5. Click OK. "Success" is displayed in the corresponding cell in the Result column.

2-24



Note:

If "Exception" is displayed in the cell, users can check the related logs to locate thefailure cause.

6. Click Refresh. The status of the base station in the Status Before column changesto "Testing".

End of Steps

Related Task

After the testing process is completed, users must set the status of the base station toNormal, so that the alarm and performance information can be reported to the NetNumenU31 system.

2.4.3 Exporting Base Station Statuses

Context

This procedure describes how to export base station statuses to a file.

Prerequisite


normal.

Steps

1. Perform either of the following operations as required.

To... Do...

Save all base station status data in the Maintain

Status Query and Setting dialog box to a filei. In the Maintain Status Query and Setting

dialog box, click Export. The Save dialog box

is displayed.

ii. Select a directory for saving the exported

base station statuses, enter a file name, and

then click Save. A message confirming the

successful export of the base station statuses

is displayed.

2-25



To... Do...

iii. Click OK. An XLS file containing the exported

base station statuses is generated in the

selected directory.

Save all base station status data in the system

to a filei. In the Maintain Status Query and Setting

dialog box, click Export All Data. The Save

dialog box is displayed.

ii. Select a directory, enter a file name, and

then click Save. A message confirming the

successful export of the base station statuses

is displayed.

iii. Click OK. A ZIP file containing all the base

station statuses in the system is generated in

the selected directory.

End of Steps

2.4.4 Importing Base Station StatusesThis procedure describes how to import base station statuses from a predefined XLS file.

Context

The base station status import function can be used to modify the statuses of multiple basestations at a time. Users can export the original base station statuses to an XLS file, enternew statuses for multiple base stations in the Status After column in the XLS file (seeFigure 2-20), and then import the modified XLS file to the NetNumen U31 system. Thenew statuses are displayed in the Maintain Status Query and Setting dialog box.

Figure 2-20 Base Station Statuses in an XLS File

2-26



Prerequisite


normal.l The XLS file to be imported is available and has an appropriate content structure.l The XLS file does not contain base stations that are not configured in the NetNumen

U31 system.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > Maintain Status Query and Setting from the menu bar. TheMaintainStatus Query and Setting dialog box is displayed.

2. Click Import. The Open dialog box is displayed.

3. Select the directory where the XLS file is saved, click the XLS file, and then clickOpen.The imported base station statuses are displayed in the Maintain Status Query andSetting dialog box, see Figure 2-21.

Figure 2-21 Example of Imported Base Station Statuses

End of Steps

2.5 Base Station Priority ManagementIn the NetNumen U31 system, themanaged base stations can be divided into VIP, Class-B,Class-C, and Normal base stations in descending order of priority. The priority attribute ofa base station can be used in other functional modules of the NetNumen U31 system. Forexample, users can use the fault management module to obtain the alarm statistics of VIPbase stations, Class-B base stations, and Class-C base stations separately.

Base station priority management supports the following operations:

l Querying base station prioritiesl Setting base station priorities

2-27



l Exporting base station prioritiesl Importing base station priorities

2.5.1 Querying Base Station PrioritiesThis procedure describes how to query the priorities of specific base stations.

Prerequisite

The connections between the base stations and the NetNumen U31 server are normal.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > VIP NodeB Priority Query and Setting from the menu bar. The VIPNodeB Priority Query and Setting dialog box is displayed, see Figure 2-22.

Figure 2-22 VIP NodeB Priority Query and Setting Dialog Box

In the topology tree, each Managed Element (ME) is identified by a string combiningME name and ME ID. Users can query the priorities of specific base stations by MEname and/or ID.

l If = is selected, the system queries the priority of each base station with an MEname or ID that is the same as the entered keyword.

l If like is selected, the system queries the priority of each base station with an MEname or ID containing the entered keyword.

2-28



Note:

If users set multiple query conditions related to ME name and ID, the system queriesthe priorities of base stations whose ME name and ID meet all the query conditions.

If users do not set any query condition, the system queries the priorities of all basestations belonging to the selected subnet.

2. In the EMS Server tree, select one or multiple subnets.

3. Select the priority to be queried: All, VIP, B Class, C Class, or Normal.

4. Select = or like from the ME ID list, enter a keyword in the text box, and then clickAdd. The query conditions are displayed in the lower area.

5. Select = or like from the ME Name list, enter a keyword (for example, 12) in the textbox, and then click Add. The query conditions are displayed in the lower area, seeFigure 2-23.

Figure 2-23 Priority Query Condition Setting

6. Click OK. The base station priorities meeting the query conditions are displayed in theVIP NodeB Priority Query and Setting dialog box, see Figure 2-24.

2-29



Figure 2-24 Query Results of Base Station Priorities

For a description of the buttons in the dialog box, refer to Table 2-6.

Table 2-6 Buttons in the VIP NodeB Priority Query and Setting Dialog Box

Button Description

Execute Sets the priority of a base station.

Export Exports the query results to an XLS file.

Import Sets the priorities of base stations by importing an XLS file.

Refresh Refreshes the base station priorities in the query result.

Option Displays VIP NodeB Priority Query and Setting dialog box, where

the query conditions can be reset to initiate another query.

Close Closes the dialog box.

End of Steps

2.5.2 Setting the Priority of a Base Station

Context

Users can set the priority of one or multiple base stations as required.

This procedure describes how to set the priority of a base station from "Normal" to"Class-B".

Prerequisite

l Users have successfully queried the priority of the base station, and the query resultis displayed in the VIP NodeB Priority Query and Setting dialog box.

l The connection between the base station and the NetNumen U31 server is normal.

2-30



Steps

1. In the VIP NodeB Priority Query and Setting dialog box, click a row and right-clickon the selected row. A shortcut menu is displayed, see Figure 2-25.

Figure 2-25 Shortcut Menu for Setting Base Station Priority

Note:

To set the priorities of multiple base stations to the same priority at a time, users canpress and hold the Ctrl or Shift key while selecting each base station to be set.

2. Select B Class from the shortcut menu.

3. Click Execute. A message confirming the successful execution of the priority settingcommand is displayed.

4. Click OK. "Success" is displayed in the corresponding cell in the Result column.

5. Click Refresh. The priority of the base station in the Priority Before column changesto "B Class".

End of Steps

2.5.3 Exporting Base Station Priorities

Context

After querying required base station priorities, users can export the query results to anXLS file.

The following procedure describes how to export base station priorities to an XLS file.

2-31



Prerequisite

Users have successfully queried the base station priorities to be exported in theVIPNodeBPriority Query and Setting dialog box.

Steps

1. In the VIP NodeB Priority Query and Setting dialog box, click Export. The Savedialog box is displayed.

2. Select a directory for saving the exported base station priorities, enter a file name,and then click Save. A message confirming the successful export of the base stationpriorities is displayed.

3. Click OK. An XLS file containing the exported base station priorities is generated inthe selected directory.

End of Steps

2.5.4 Importing Base Station PrioritiesThis procedure describes how to import base station priorities from a predefined XLS file.

Context

The base station priority import function can be used to modify the priorities of multiplebase stations at a time. Users can export the original base station priorities to an XLS file,enter new priorities for multiple base stations in the Priority After column in the XLS file(see Figure 2-26), and then import the modified XLS file to the NetNumen U31 system.The new priorities will be displayed in the VIP NodeB Priority Query and Setting dialogbox.

Figure 2-26 Base Station Priorities in an XLS File

Prerequisite

l The connections between the base stations and theNetNumenU31 server are normal.l The XLS file to be imported is available and has an appropriate content structure.

2-32



l The XLS file does not contain base stations that are not configured in the NetNumenU31 system.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > VIP NodeB Priority Query and Setting from the menu bar. The VIPNodeB Priority Query and Setting dialog box is displayed.

2. In the VIP NodeB Priority Query and Setting dialog box, click Import. The Opendialog box is displayed.

3. Select the directory where the XLS file is saved, click the XLS file, and then clickOpen.The imported base station priorities are displayed in the VIP NodeB Priority Queryand Setting dialog box, see Figure 2-27.

Figure 2-27 Imported Base Station Priorities

4. Click Execute. A message confirming the successful execution of the priority settingcommand is displayed.

5. Click OK. "Success" is displayed in each related cell in the Result column.

6. ClickRefresh. The priorities of the base stations in thePriority Before column changein accordance with the settings in the imported XLS file.

End of Steps

2.6 Site TransferThe NetNumen U31 system supports the transfer and swap of equipment in the samenetwork or between two networks of the same system (GSM, UMTS, or TD-SCDMA).

Before transferring the configuration data of a site in the NetNumen U31 system, atransfer plan file in XLS format must be made by professional engineers. The transferplan file contains the information of source nodes and destination nodes, and necessarymodification of the configuration information.

2-33



Users can obtain transfer plan templates for different products in a specific path in theinstallation directory of the client. The paths of these transfer plan templates follow thesame rule: \EMS\ERT\folder obtained from remote OMM (name format:

product and version\the path of templates on the OMM. For example, thetransfer plan templates for non-MO GSM products are located in the \EMS\ERT\ISMG

-R6.20.713b-B4.00.200m-\ums-clnt\deploy\template\rnc\template_EN

folder in the installation directory of the client.

The NetNumen U31 system provides the following functions to support site transfer:

l Exporting configuration data

Users can export the configuration information of the source nodes specified in thetransfer plan file from the system to a ZIP file. This ZIP file can be used for site transferlater.

l Transferring the configuration data for online source nodes

Users can transfer the configuration data of the source nodes specified in the transferplan file to the destination nodes, and then remove the source nodes from the system.

l Transferring the configuration data for offline source nodes

Users can transfer the configuration data of the source nodes from a predefinedZIP file to the destination nodes. If the source nodes are managed by the sameNetNumen U31 system, users can remove the source nodes from the system afterthe site transfer.

The offline site transfer function can be used for transferring equipment managed bya NetNumen U31 system to another NetNumen U31 system.

Note:l For a GSM or UMTS site, only the configuration data of base station controllers (BSC

or RNC) can be exported and transferred in the NetNumen U31 system. Users canonly export and transfer the configuration data of a base station (BTS or Node B) byusing a tool provided by the corresponding Operation & Maintenance Module (OMM).

l For a TD-SCDMA site, the configuration data of both RNC and Node B can beexported and transferred in the NetNumen U31 system.

If the process of data export, online transfer, or offline transfer is not completed within15 minutes, the system will forcibly end the process. The time limit is determined bythe following three parameters in the minos-movesite-wsf-time.xml file in the

ums-client\procs\ppus\minos.ppu\minos-cmc.pmu\minos-movesite-wsf

.par\conf\ directory:

l getsite waitting="15"

l transfersite waitting="15"

l deletesite waitting="15"

2-34



Users can change the parameter values to modify the time limit.

2.6.1 Exporting Configuration Data of a Source SiteThis procedure describes how to export the configuration data of the source site from thesystem to a ZIP file.

Prerequisite

The transfer plan file to be used is available, which contains the information of the sourcesite to be transferred.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > Transfer Site from the menu bar. The Transfer Site dialog box isdisplayed, see Figure 2-28.

Figure 2-28 Transfer Site Dialog Box

2. Click Select. The Open dialog box is displayed.

3. Select the directory where the transfer plan file is saved, click the file, and then clickOpen. The file name is displayed in File Path.

4. Select the type(s) of configuration data to be exported in accordance with theequipment type: Bind OMMR and/or Bind OMMB.

5. Click Execute. The export progress is displayed under Output Info. After theconfiguration data export is completed, the path and name of the generated ZIP fileare displayed too. The ZIP file is generated in the ums-client/works/full/tmp

/ftp/movesite/data/ directory.

End of Steps

2-35



2.6.2 Transferring an Online SiteThis procedure describes how to transfer the configuration data from a source site to adestination site when the source site is online in the NetNumen U31 system.

Prerequisite

The transfer plan file to be used is available, which contains the information of the sourcesite and destination site for the site transfer.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > Transfer Site from the menu bar. The Transfer Site dialog box isdisplayed.



4. Select Online Transfer from the Operation list.

5. Select the type(s) of configuration data to be transferred in accordance with theequipment type: Bind OMMR and/or Bind OMMB.

6. To delete the source site when the transfer is completed, select Delete Site.

7. Click Execute. The transfer progress is displayed under Output Info. If Delete Siteis selected, the source site will be deleted from the NetNumen U31 system after thesite transfer is completed.

End of Steps

2.6.3 Transferring an Offline SiteThis procedure describes how to transfer the configuration data from a source site to adestination site when the source site is offline in the NetNumen U31 system.

Prerequisite

l The transfer plan file to be used is available, which contains the information of thesource site and destination site for the site transfer.

l The ZIP file containing the configuration data of the offline source site is available.

Steps



2-36




4. Select Offline Transfer from the Operation list.

5. Select the type(s) of configuration data to be transferred in accordance with theequipment type: Bind OMMR and/or Bind OMMB.

6. To delete the source site when the transfer is completed, select Delete Site.

7. Click Execute. The Offline Data dialog box is displayed, see Figure 2-29.

Figure 2-29 Offline Data Dialog Box


9. Select the ZIP file that contains the configuration data of the source site, and then clickOpen. The file path is displayed in File Path.

Note:

If the transfer plan file specifies multiple source sites and destination sites, the systemwill transfer the configuration data of all source sites to the corresponding destinationsites. Users can view the attributes of a specific source site by selecting the site fromthe Site Info list and then clicking View in the Offline Data dialog box.

10. Click Ok. The transfer progress is displayed under Output Info in the Transfer Sitedialog box. IfDelete Site is selected and the source site is managed by this NetNumenU31 system, the source site will be deleted from the system after successful sitetransfer.

End of Steps

2-37



2.6.4 Viewing Operation Results Related to Site TransferThis procedure describes how to view the results of site transfer operations on the clientGUI.

Context

After a configuration data export, online site transfer, or offline site transfer operation isperformed, the system generates one to three CSV files containing the results of differentoperations. The recorded result in these files will be overwritten after another operation isperformed. For a description of the result files and the default file paths, refer to Table 2-7.

Table 2-7 Result File Descriptions

Result File Possible Operation Default File Path

CSV file containing

the result of obtaining

configuration data from a

source site

l Configuration data export

l Online site transfer

ums-client/works/full/tmp/ft

p/movesite/result/collect/

CSV file containing the

result of transferring

configuration data from a

source site to a destination

site


l Offline site transfer


p/movesite/result/transfer/

CSV file containing the

result of deleting a source

site


l Offline site transfer


p/movesite/result/delete/

Users can open a result file to view the result details or view the previous operation resulton the client GUI.

Prerequisite

A configuration data export, online site transfer, or offline site transfer operation has beenperformed in the NetNumen U31 system.

Steps


2. Click View Result. The Result Data dialog box is displayed, see Figure 2-30.

2-38



Figure 2-30 Result Data Dialog Box

3. Select a result type from the Result Type list. The operation result saved in thecorresponding CSV file is displayed, see Figure 2-31.

Figure 2-31 Result Data Dialog Box

End of Steps

2.6.5 Halting a Site Transfer ProcessThis procedure describes how to halt a site transfer process.

Context

If the NetNumen U31 system does not complete the export or transfer of configuration dataafter a long time, the process can be halted as required. After the process is halted, thesystem will not execute the commands that have not been sent to the corresponding site.

2-39



Caution!

Do not halt an export or transfer process unless absolutely necessary. Improper haltingof a process may result in inconsistent configuration data (for example, the configurationdata in the base station controller changes due to transfer operation but the configurationdata in the base station is not modified yet), or incompleted site transfer (for example, anew site is created but the source site is not deleted from the system).

Prerequisite

l The Transfer Site dialog box is open.l The system is exporting or transferring configuration data of a source site.

Steps

l In the Transfer Site dialog box, click Halt Operation. The halting result is displayedunder Output Info.

End of Steps

2.7 Inter-Element Configuration Data Import and ExportThe NetNumen U31 system supports the export and import of configuration data in GSM,UMTS, and LTE networks. The following export and import operations are supported:

l Exporting configuration data from multiple NEs to XLS or XML files.l Importing configuration data to multiple NEs from XLS or XML files for quick

configuration.

For NEs in different radio access networks, the system provides several configuration datatemplates by data type, such as radio data batch import and export template, and RNCequipment and transmission parameter import and export template. Users can obtain aconfiguration data template for a specific NE type and version by exporting configurationdata from an NE of this type. This template can be used for editing a file containing requiredconfiguration data for another NE of the same type and version.

2.7.1 Exporting Configuration DataThis procedure describes how to export configuration data from multiple NEs to individualXLS files.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > Inter ME Import and Export from the menu bar. The Inter MEConfiguration Import and Export dialog box is displayed, see Figure 2-32.

2-40



Figure 2-32 Inter ME Configuration Import and Export Dialog Box

2. (Optional) To modify the path where the configuration data is to be saved, selectSystem > Config Export Result File Path on the main menu. The Config ExportResult File Path dialog box is displayed.

a. Click Config. The Open dialog box is displayed.

b. Select a path and then click Open.

c. In the Config Export Result File Path dialog box, click OK.

3. Click Config Data Export under Operation Type Selection, and click a templateunder Operation Template Selection. The Add Operate Object and RemoveOperate Object buttons are activated on the lower part of the right pane, see Figure2-33.

Figure 2-33 Operation Type Config Data Export

2-41



4. Click Add Operate Object. The Add Object dialog box is displayed, see Figure 2-34.

Figure 2-34 Add Object Dialog Box

5. Select one or multiple objects in the NE tree, and then click OK. The selected objectsand corresponding files are displayed in the Inter ME Configuration Import andExport dialog box, see Figure 2-35.

Figure 2-35 Inter ME Configuration Import and Export Dialog Box Objects Selected

6. (Optional) To change the format of configuration data file to be saved, click thecorresponding cell in the Export Format column, and then select xls or xml from thelist.

2-42



7. Click OK. After the system successfully exports the required configuration data for anobject, "Success" is displayed in the corresponding cell in the Result column and anXLS or XML file is generated in the selected path.

End of Steps

2.7.2 Importing Configuration DataThis procedure describes how to import configuration data from predefined XLS or XMLfiles to multiple NEs.

Note:

To prepare a configuration data file in XLS format for an NE to be configured, users arerecommended to edit the configuration data based on an appropriate template. Users canexport configuration data from an existing NE of the same type and version to obtain thetemplate.

Prerequisite

l The NEs to be configured support the configuration data import function.l The XLS or XML files to be imported are available and comply with the corresponding

configuration data templates.l The configuration data to be imported is correct and applicable to the type and version

of the NEs.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > Inter ME Import and Export from the menu bar. The Inter MEConfiguration Import and Export dialog box is displayed.

2. (Optional) To modify the path where the configuration data is to be saved, selectSystem > Config Export Result File Path on the main menu. The Config ExportResult File Path dialog box is displayed.

a. Click Config. The Open dialog box is displayed.

b. Select a path and then click Open.

c. In the Config Export Result File Path dialog box, click OK.

3. Click an appropriate template under Operation Template Selection.

4. Click Add Data File. The Open dialog box is displayed.

5. Select the directory where the configuration data files are saved from the Look in list.

6. Select .xml file or .xls file from the Files of Type list.

2-43



7. Select a configuration data file to be imported, and then click Open. The file name isdisplayed in the Selected Data File List, see Figure 2-36.

Figure 2-36 Record in the Selected Data File List

8. Click the corresponding cell in the Operate Object No. column, and then select theNE to which the configuration data will be imported from the list.

9. Repeat Step 3 to Step 7 to add the other configuration data files and selectcorresponding NEs as required.

10. Click OK. The Please input verification code dialog box is displayed, see Figure2-37.

Figure 2-37 Please Input Verification Code Dialog Box

11. Enter the verification code as required, and click OK. After the system successfullyimports configuration data from a selected file to the required NE, "Success" isdisplayed in the corresponding cell in the Result column.

End of Steps

2.8 Neighbor Cell ToolThe NetNumen U31 system provides a neighbor cell tool for checking neighbor relations,including:

2-44



l Verifying that the external cell attributes on an OMM are consistent with those of theactual external cells

l Verifying the integrity of neighbor relations for a cell

In addition, the neighbor cell tool supports automatic and manual modification ofinconsistent attributes.

The procedure for verifying neighbor relation integrity is similar to that for verifying attributeconsistency. The subsequent section only describes how to verify the attribute consistency.

2.8.1 Verifying Attributes Consistency

Context

In the NetNumen U31 system, the attributes of some external cells may be specified for asubnet (OMM). The external cells can be configured as neighbor cells of a local cell. Userscan verify that appropriate attributes are specified on the OMM to ensure correct neighborrelations.

Note:

If an external cell is managed by another NetNumen U31 system, a ZIP file containing theattributes of this external cell is required for consistency verification. Users can contactZTE's maintenance engineers for how to obtain the ZIP file.

The following procedure describes how to verify the consistency between the external cellattributes specified on a UMTS OMM and those of the actual external cells.

Steps

1. In the client window, select Configuration > Common Wireless ConfigurationApplication > Neighbour Cell Tool from the menu bar. The Neighbour Cell Tooldialog box is displayed, see Figure 2-38.

2-45



Figure 2-38 Neighbour Cell Tool Dialog Box

2. Under Operate Functions List, click check accord.

3. Under Product Type, click UMTS. All available subnets are displayed under OperateObject Area, see Figure 2-39.

Figure 2-39 Operate Object Area

4. Select the check box corresponding to the subnet to be checked.

5. (Optional) If related external cells are managed by another NetNumen U31 system,perform the following operations:

a. Select Upload extern files. Additional buttons are activated in the OperateObject Area, see Figure 2-40.

2-46



Figure 2-40 Operate Object Area (External Files)

b. Click Browse. The Open dialog box is displayed.

c. Select the directory where the ZIP file containing the external cell attributes islocated, and then click Open. The file path is displayed in External Files.

d. Click Upload. A progress shows the uploading progress and is closed after theattributes uploading is completed.

6. Click Execute. A record containing the verification result is displayed under OperateHistory Area, see Figure 2-41.

Figure 2-41 Operate History Area

7. To view the verification result, right-click the record and then clickShowActionResult.The consistency verification result is displayed under Detail Information Area, seeFigure 2-42.

Figure 2-42 Consistency Verification Result in the Detail Information Area (ShowAction Result)

8. To view inconsistent attributes, right-click the record and then click Show Result. Thedetected inconsistent attributes are displayed under Detail Information Area, seeFigure 2-43.

2-47



Figure 2-43 Detected Inconsistent Attributes in the Detail Information Area (ShowResult)

Note:

The system supports automatic and manual modification of inconsistent attributes.

9. To automatically modify inconsistent attributes, click Modify start. A progress isdisplayed, showing the modification progress. After the modification is completed, amessage box is displayed, showing the operation result ID.

10. Click OK.

11. Under Operate History Area, rightclick the record of the modification operation andthen click Show Action Result. The modification result is displayed under DetailInformation Area.

End of Steps

2.8.2 Importing Modified AttributesWhen the automatic modification of inconsistent attributes fails, users can export theinconsistent attributes to a CSV file, check and modify the inconsistent attributes manuallyas required. The modified CSV file can be imported to the NetNumen U31 system tocomplete the attribute modification.

The following procedure describes how to modify inconsistent attributes manually.

Prerequisite

l The Neighbour Cell Tool dialog box is open.l An attribute verification operation has been performed and inconsistent attributes are

detected.

2-48



Steps

1. In the Neighbour Cell Tool dialog box, locate the operation result record underOperate History Area.

2. Right-click the record and then click Show Result. The inconsistent attributes aredisplayed under Detail Information Area.

3. Click export. The Save dialog box is displayed.

4. Select a directory for saving the exported attributes, use the default file name or entera new file name, and then click Save. A message confirming the successful export ofthe attributes is displayed.

5. Locate the generated CSV file containing the exported attributes in the selecteddirectory on the client.

6. Open the CSV file and modify the inconsistent attributes as required, and then savethe file.

7. Under Operate History Area, right-click the operation result record, and then clickImport Data. The Open dialog box is displayed.

8. Select the directory where the modified CSV file is saved, click the file, and then clickOpen. A progress scroll bar is displayed, indicating the modification progress. Afterthe modification is completed, a message showing the operation result ID is displayed.

9. Click OK.

10. Under Operate History Area, rightclick the record of the modification operationand click Show Action Result. The modification result is displayed under DetailInformation Area.

End of Steps

2.9 User Label Relation ManagementThe user label of a local cell should be specified in a neighbor relation between the localcell and an adjacent cell. If a user modifies the local cell's user label or the user label in theneighbor relation, an inconsistency occurs. The function of managing user label relationscan be used to overwrite the user label in the neighbor relation with the local cell's userlabel when the user label consistency is required.

The NetNumen U31 system can show the user labels of the local cells and those incorresponding neighbor relations for

U31 R18 Configuration Application Operation Guide

Documents

Transcript of U31 R18 Configuration Application Operation Guide