Huawei Guide M2000

M2000

V200R008C01

Northbound File Interface Developer Guide

Issue 02

Date 2008-09-05

Part Number

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Introduction to Northbound File Interface...........................................................................1-11.1 Definition of Northbound Interface.................................................................................................................1-21.2 Definition of Northbound File Interface.........................................................................................................1-21.3 Parameters for Connecting the Northbound File Interface.............................................................................1-2

2 Introduction to Alarm Export Tool and File.........................................................................2-12.1 Alarm Export Tool..........................................................................................................................................2-22.2 Alarm Export File............................................................................................................................................2-22.3 Alarm Export Operations................................................................................................................................2-5

2.3.1 Modifying the Configuration File of the Alarm Export Tool................................................................2-52.3.2 Setting Automatic Export of Alarm Files..............................................................................................2-62.3.3 Setting the Termination of Automatically Exporting Alarm Files.........................................................2-6

3 Introduction to Configuration Data Export File...................................................................3-1

4 Introduction to Configuration Export Files (Flat Export)...................................................4-1

5 Introduction to Performance Data Export Tool and File....................................................5-15.1 Performance Data Export Tool.......................................................................................................................5-25.2 Configuration file of the Performance Data Export Tool................................................................................5-25.3 Performance Data Export File.........................................................................................................................5-65.4 Operations Related to the Performance Data Export Tool............................................................................5-10

5.4.1 Modifying the Configuration File of the Performance Data Export Tool............................................5-115.4.2 Setting Export Tasks on the M2000 Client..........................................................................................5-145.4.3 Starting the Performance Data Export Tool.........................................................................................5-165.4.4 Stopping the Performance Data Export Tool.......................................................................................5-16

5.5 Troubleshooting for the Performance Export Tool.......................................................................................5-17

6 Introduction to NE-Based Performance Data Export Tool and File.................................6-16.1 Introduction to NE-Based Performance Data Export Tool.............................................................................6-26.2 Introduction to Configuration Files of NE-Based Performance Data Export Tool.........................................6-26.3 Introduction to NE-Based Performance Data Export File...............................................................................6-76.4 Operations Related to NE-Based Performance Data Export Tool..................................................................6-9

6.4.1 Starting NE-Based Performance Data Export Tool...............................................................................6-96.4.2 Stopping NE-Based Performance Data Export Tool............................................................................6-10

M2000Northbound File Interface Developer Guide Contents

Issue 02 (2008-09-05) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

6.5 Troubleshooting for NE-Based Performance Data Export Tool...................................................................6-11

7 Introduction to Export File of Inventory Management...................................................... 7-17.1 Export File of Inventory Management............................................................................................................7-2

7.1.1 NE Types of Inventory Management.....................................................................................................7-27.1.2 The Types of Export File of Inventory Management.............................................................................7-37.1.3 The Default Path of Export File of Inventory Management..................................................................7-37.1.4 The Naming Way of Export File of Inventory Management.................................................................7-37.1.5 The Format of Export File of Inventory Management...........................................................................7-4

7.2 Related Operations on Inventory Management Exporting..............................................................................7-67.2.1 Automatically Exporting Inventory Management Files.........................................................................7-67.2.2 Stopping Automatically Exporting Inventory Management Files.........................................................7-77.2.3 Manually Exporting Inventory Management Files................................................................................7-7

7.3 The Inventory Types of Each NE....................................................................................................................7-87.3.1 RNC Inventory Types............................................................................................................................7-87.3.2 NodeB Inventory Types.......................................................................................................................7-137.3.3 BSC6000 Inventory Types...................................................................................................................7-197.3.4 BSC6000Site Inventory Types.............................................................................................................7-237.3.5 MSC Server Inventory Types...............................................................................................................7-287.3.6 MGW Inventory Types........................................................................................................................7-317.3.7 SGSN Inventory Types........................................................................................................................7-357.3.8 GGSN80 Inventory Types....................................................................................................................7-397.3.9 HLR Inventory Types...........................................................................................................................7-437.3.10 PCU Inventory Types.........................................................................................................................7-477.3.11 BSC Inventory Types.........................................................................................................................7-517.3.12 ICS Inventory Types..........................................................................................................................7-537.3.13 UAG Inventory Types........................................................................................................................7-57

Index.................................................................................................................................................i-1

ContentsM2000


ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-09-05)

Figures

Figure 1-1 Location of the Northbound interface.................................................................................................1-2Figure 2-1 Example of a file in .csv format..........................................................................................................2-4

M2000Northbound File Interface Developer Guide Figures


iii

Tables

Table 3-1 File format............................................................................................................................................3-2Table 4-1 File format of configuration data.........................................................................................................4-2Table 5-1 Export periods and time ranges............................................................................................................5-6Table 5-2 Parameters of performance data export tasks.....................................................................................5-15Table 6-1 Description of the parameters in the configuration file........................................................................6-4Table 7-1 List of supported NE Types.................................................................................................................7-2Table 7-2 Format of the export file of inventory management............................................................................7-4Table 7-3 Rack and its attributes..........................................................................................................................7-9Table 7-4 Frame and its attributes........................................................................................................................7-9Table 7-5 Slot and its attributes..........................................................................................................................7-10Table 7-6 Board and its attributes.......................................................................................................................7-11Table 7-7 Port and its attributes..........................................................................................................................7-12Table 7-8 HostVer and its attributes...................................................................................................................7-12Table 7-9 RNCCell and its attributes.................................................................................................................7-13Table 7-10 Rack and its attributes......................................................................................................................7-13Table 7-11 Frame and its attributes....................................................................................................................7-14Table 7-12 Slot and its attributes........................................................................................................................7-15Table 7-13 Board and its attributes.....................................................................................................................7-15Table 7-14 Port and its attributes........................................................................................................................7-16Table 7-15 Antenna and its attributes.................................................................................................................7-17Table 7-16 HostVer and its attributes.................................................................................................................7-18Table 7-17 NodeBCell and its attributes............................................................................................................7-18Table 7-18 Rack and its attributes......................................................................................................................7-19Table 7-19 Frame and its attributes....................................................................................................................7-20Table 7-20 Slot and its attributes........................................................................................................................7-20Table 7-21 Board and its attributes.....................................................................................................................7-21Table 7-22 Port and its attributes........................................................................................................................7-22Table 7-23 HostVer and its attributes.................................................................................................................7-23Table 7-24 BTS and its attributes.......................................................................................................................7-23Table 7-25 Rack and its attributes......................................................................................................................7-23Table 7-26 Frame and its attributes....................................................................................................................7-24Table 7-27 Slot and its attributes........................................................................................................................7-25Table 7-28 Board and its attributes.....................................................................................................................7-25

M2000Northbound File Interface Developer Guide Tables


v

Table 7-29 Port and its attributes........................................................................................................................7-27Table 7-30 HostVer and its attributes.................................................................................................................7-27Table 7-31 Rack and its attributes......................................................................................................................7-28Table 7-32 Frame and its attributes....................................................................................................................7-28Table 7-33 Slot and its attributes........................................................................................................................7-29Table 7-34 Board and its attributes.....................................................................................................................7-30Table 7-35 Port and its attributes........................................................................................................................7-31Table 7-36 HostVer and its attributes.................................................................................................................7-31Table 7-37 Rack and its attributes......................................................................................................................7-32Table 7-38 Frame and its attributes....................................................................................................................7-32Table 7-39 Slot and its attributes........................................................................................................................7-33Table 7-40 Board and its attributes.....................................................................................................................7-34Table 7-41 Port and its attributes........................................................................................................................7-35Table 7-42 HostVer and its attributes.................................................................................................................7-35Table 7-43 Rack and its attributes......................................................................................................................7-36Table 7-44 Frame and its attributes....................................................................................................................7-36Table 7-45 Slot and its attributes........................................................................................................................7-37Table 7-46 Board and its attributes.....................................................................................................................7-38Table 7-47 Port and its attributes........................................................................................................................7-39Table 7-48 HostVer and its attributes.................................................................................................................7-39Table 7-49 Rack and its attributes......................................................................................................................7-40Table 7-50 Frame and its attributes....................................................................................................................7-40Table 7-51 Slot and its attributes........................................................................................................................7-41Table 7-52 Board and its attributes.....................................................................................................................7-42Table 7-53 Port and its attributes........................................................................................................................7-43Table 7-54 HostVer and its attributes.................................................................................................................7-43Table 7-55 Rack and its attributes......................................................................................................................7-44Table 7-56 Frame and its attributes....................................................................................................................7-44Table 7-57 Slot and its attributes........................................................................................................................7-45Table 7-58 Board and its attributes.....................................................................................................................7-46Table 7-59 Port and its attributes........................................................................................................................7-47Table 7-60 HostVer and its attributes.................................................................................................................7-47Table 7-61 Rack and its attributes......................................................................................................................7-48Table 7-62 Frame and its attributes....................................................................................................................7-48Table 7-63 Slot and its attributes........................................................................................................................7-49Table 7-64 Board and its attributes.....................................................................................................................7-50Table 7-65 Port and its attributes........................................................................................................................7-51Table 7-66 HostVer and its attributes.................................................................................................................7-51Table 7-67 BSCModule and its attributes..........................................................................................................7-52Table 7-68 BSCFrame and its attributes.............................................................................................................7-52Table 7-69 BSCBoard and its attributes.............................................................................................................7-52Table 7-70 BSCBTSEquipment and its attributes..............................................................................................7-52

TablesM2000


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-09-05)

Table 7-71 BSCBTSFrame and its attributes.....................................................................................................7-53Table 7-72 BSCBTSBoard and its attributes......................................................................................................7-53Table 7-73 Rack and its attributes......................................................................................................................7-53Table 7-74 Frame and its attributes....................................................................................................................7-54Table 7-75 Slot and its attributes........................................................................................................................7-55Table 7-76 Board and its attributes.....................................................................................................................7-55Table 7-77 Port and its attributes........................................................................................................................7-56Table 7-78 HostVer and its attributes.................................................................................................................7-57Table 7-79 Rack and its attributes......................................................................................................................7-57Table 7-80 Frame and its attributes....................................................................................................................7-58Table 7-81 Slot and its attributes........................................................................................................................7-59Table 7-82 Board and its attributes.....................................................................................................................7-59Table 7-83 Port and its attributes........................................................................................................................7-60Table 7-84 HostVer and its attributes.................................................................................................................7-61

M2000Northbound File Interface Developer Guide Tables


vii

About This Document

PurposeThis document provides the information about M2000 Northbound file interface. The documentalso provides the operation guide for connecting the NMS.

Related VersionsThe following table lists the product versions related to this document.

Product Name Version

M2000 V200R008C01

Intended AudienceThe intended audiences of this document are:

l Network administrator

Update History

02(2008-08-20)The second formal release. Added Introduction to Configuration Export Files (Flat Export).

01(2008-03-20)Initial release. Also, the first formal release.

Organization1 Introduction to Northbound File Interface

This describes the definition of the Northbound interface, and the definition and parameters ofthe Northbound file interface.

2 Introduction to Alarm Export Tool and File

This describes the alarm export tool, the formats of alarm export files, alarm export operations,and troubleshooting.

M2000Northbound File Interface Developer Guide About This Document


1

3 Introduction to Configuration Data Export File

This describes the configuration data export files: their detailed formats, deletion strategy, andfile types.

4 Introduction to Configuration Export Files (Flat Export)

This describes the file path, categories, quantities, rules for naming files, format description,deletion strategy, and modification description of configuration export files.

5 Introduction to Performance Data Export Tool and File

This describes the performance data export tool and file.

6 Introduction to NE-Based Performance Data Export Tool and File

This describes the NE-based performance data export tool and file.

7 Introduction to Export File of Inventory Management

This introduces the export file of inventory management.

Conventions1. Symbol Conventions

The following symbols may be found in this document. They are defined as follows

Symbol Description

DANGERIndicates a hazard with a high level of risk that, if not avoided,will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk which, ifnot avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if not avoided,could cause equipment damage, data loss, and performancedegradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save yourtime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

2. General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files,directories,folders,and users are in boldface. Forexample,log in as user root .

About This DocumentM2000


2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-09-05)


Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

3. Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{x | y | ...} Alternative items are grouped in braces and separated by verticalbars.One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets andseparated by vertical bars.One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by verticalbars.A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Alternative items are grouped in braces and separated by verticalbars.A minimum of zero or a maximum of all can be selected.

4. GUI Conventions


Boldface Buttons,menus,parameters,tabs,window,and dialog titles are inboldface. For example,click OK.

> Multi-level menus are in boldface and separated by the ">" signs.For example,choose File > Create > Folder .

5. Keyboard Operation


Key Press the key.For example,press Enter and press Tab.

Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+Ameans the three keys should be pressed concurrently.

Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the twokeys should be pressed in turn.

6. Mouse Operation

M2000Northbound File Interface Developer Guide About This Document


3

Action Description

Click Select and release the primary mouse button without moving thepointer.

Double-click Press the primary mouse button twice continuously and quicklywithout moving the pointer.

Drag Press and hold the primary mouse button and move the pointerto a certain position.

About This DocumentM2000


4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-09-05)

1 Introduction to Northbound File Interface

About This Chapter

This describes the definition of the Northbound interface, and the definition and parameters ofthe Northbound file interface.

1.1 Definition of Northbound InterfaceThe Northbound interface is an interface between the Element Management System (EMS) andthe Network Management System (NMS).

1.2 Definition of Northbound File InterfaceThe M2000 exports data from the database to specified files through the Northbound fileinterface. Then the NMS extracts information from these files stored on the M2000 serverthrough the FTP protocol.

1.3 Parameters for Connecting the Northbound File InterfaceThrough the Northbound file interface, the NMS is connected to the M2000 server through theFTP protocol.

M2000Northbound File Interface Developer Guide 1 Introduction to Northbound File Interface


1-1

1.1 Definition of Northbound InterfaceThe Northbound interface is an interface between the Element Management System (EMS) andthe Network Management System (NMS).

On the Northbound interface, the NMS obtains the information about the NEs managed by theEMS and delivers operation commands. The NE information includes the alarm, configuration,and performance data. The Northbound interface is as shown in Figure 1-1.

Figure 1-1 Location of the Northbound interface

In the mobile communication network, the M2000 is an EMS. The M2000 reports the alarm,configuration, and performance data to the NMS through the Northbound interface.

1.2 Definition of Northbound File InterfaceThe M2000 exports data from the database to specified files through the Northbound fileinterface. Then the NMS extracts information from these files stored on the M2000 serverthrough the FTP protocol.

At present, the M2000 Northbound file interface supports the transmission of the alarm,configuration, and performance data.

Before using the Northbound file interface, ensure that:l The alarm export tool is running on the M2000 server.l The performance export tool is running on the M2000 server.l Data export tasks are configured on the M2000 server.

1.3 Parameters for Connecting the Northbound FileInterface

Through the Northbound file interface, the NMS is connected to the M2000 server through theFTP protocol.

The NMS uses the user name and default password as ftpuser and ftpuser respectively.

1 Introduction to Northbound File InterfaceM2000


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 02 (2008-09-05)

NOTE

You can set the password of ftpuser when installing the M2000 server.

For details about the export tool and export format of alarm files, see 2 Introduction to AlarmExport Tool and File.

For details about the format of configuration files, see 3 Introduction to Configuration DataExport File.

For details about the export tool and export format of performance files, see 5 Introduction toPerformance Data Export Tool and File.

For details about the export tool and export format of performance files(by NE), see 6Introduction to NE-Based Performance Data Export Tool and File.

For details about the Export format of Inventory Management File, see 7 Introduction to ExportFile of Inventory Management.

M2000Northbound File Interface Developer Guide 1 Introduction to Northbound File Interface


1-3

2 Introduction to Alarm Export Tool and File

About This Chapter

This describes the alarm export tool, the formats of alarm export files, alarm export operations,and troubleshooting.

2.1 Alarm Export ToolThe alarm export tool exports alarms from the alarm database to the files in the specified directoryon the server. The alarms consist of current fault alarms, historical fault alarms, event alarms,and shielded alarms.

2.2 Alarm Export FileThis describes the path, categories and quantities, rules for naming files, and formats of alarmexport files.

2.3 Alarm Export OperationsAlarm export operations consist of modifying the configuration files of the alarm export tool,setting the automatic alarm export, and stopping the automatic alarm export.

M2000Northbound File Interface Developer Guide 2 Introduction to Alarm Export Tool and File


2-1

2.1 Alarm Export ToolThe alarm export tool exports alarms from the alarm database to the files in the specified directoryon the server. The alarms consist of current fault alarms, historical fault alarms, event alarms,and shielded alarms.

Functions of the Alarm Export ToolThe exported alarms still exist in the database.

Configuration File of the Alarm Export ToolThe configuration file of the alarm export tool is <M2000 server installation folder>/etc/conf/english/fmexportsvc_field.xml

l The configuration file <M2000 server installation folder>/etc/conf/english/fmexportsvc_field.xml is used for the files in .csv format. This configuration file definesthe name (in the first row), value, and sequence of alarm information fields in the CSV file.

l The configuration file <M2000 server installation folder>/etc/conf/english/fmexportsvc_field.xml is used for the files in .xml format. This configuration file definesthe name, value, and sequence of alarm information fields in the XML file.

Automatic Alarm ExportAfter export function is started, the alarm export tool automatically exports the new alarms afterthe previous alarms are exported from the alarm database to an alarm export file at a specifiedtime every day.

2.2 Alarm Export FileThis describes the path, categories and quantities, rules for naming files, and formats of alarmexport files.

Path of Alarm Export FilesBy default, all alarm export files are saved in the /export/home/omc/var/fileint/fm/ directory.If this directory is not available when you export alarm files, the export tool will automaticallycreate this directory.

Categories and Quantities of Alarm Export FilesDuring the alarm export, the current fault alarms, historical fault alarms, event alarms, andshielded alarms are exported to separate files. Each file records a maximum of 5,000 alarms. Ifthe alarm number of a type exceeds 5,000, the export tool saves extra alarms to a new exportfile.

Rules for Naming Alarm Export Filesl Naming Rules

2 Introduction to Alarm Export Tool and FileM2000



Issue 02 (2008-09-05)

Alarm export files are named in the following format: Date and Time [DST]-Alarmcategory-auto-Sequence number.Extension, where:– Date and Time together show the time when the alarms are exported, DST indicates the

daylight saving time is used, [] indicates that the sign is not used in non-DST period.– Alarm category shows the category of the exported alarms. The value can be current-

alarm, history-alarm, event-alarm, and shielded-alarm, which represent the current faultalarm, historical fault alarm, event alarm, and shielded alarm respectively.

A maximum of 5,000 alarms of the same category can be exported to one file. To exportmore than 5,000 alarms, the alarms other than the first 5,000 alarms are exported to anotherfile.The time duration of the alarm export files being maintained before deletion variesaccording to different server model and the number of NEs managed by the M2000.These files are numbered sequentially from 1. If only one file is enough to store the exportedalarms, the file number is 1.Extension name indicates the format of a file. The file can be in .xml or .csv format. If youselect compression mode for export, the extension name should be .zip.

l ExamplesThe file 20051206120300-current-alarm-auto-1.xml indicates:– The file is in .XML format.

– The exported alarms are current fault alarms.

– The alarms are exported at 12:03 on December 6, 2005.

The file 20051206120300-current-alarm-auto-1.zip indicates:– The file is in .zip format.

– The exported alarms are current fault alarms.

– The alarms are exported at 12:03 on December 6, 2005.

Formats of Alarm Export Filesl CSV

The first row in the CSV file lists the fields recording the alarm information, such as theNE name, alarm name, and alarm severity. From the second row, each row records an alarm.The configuration file <M2000 server installation folder>/etc/conf/english/fmexportsvc_field.xml is used for files in .csv format. This configuration file defines thename (in the first row), value, and sequence of alarm information fields in the files in .csvformat. You can modify this configuration file. For details, see 2.3.1 Modifying theConfiguration File of the Alarm Export Tool.Figure 2-1 is an example of a file in .csv format.



2-3

Figure 2-1 Example of a file in .csv format

l XMLIn an XML file, the <Record name="AlarmRecord"></Record> section recordsthe information of an alarm. The configuration file <M2000 server installation folder>/etc/conf/english/fmexportsvc_field.xml is used for the files in .xml format. Thisconfiguration file defines the name, value, and sequence of alarm information fields in theXML file. You can modify this configuration file. For details, see 2.3.1 Modifying theConfiguration File of the Alarm Export Tool.The following information is an example of a file in .XML format:<?xml version="1.0" encoding="utf-8" ?> <ExportFileInfo name="AlarmRecords"><Record name="AlarmRecord"> <column name="Csn">1001</column> <column name="ProductID">NMS</column> <column name="NEType">OMC</column> <column name="NEFDNName">iMAP</column> <column name="DevCsn">5</column> <column name="Id">Under-voltage with Input -48V</column> <column name="Type">Internal</column> <column name="AlmLevel">Critical</column> <column name="Status">Acknowledged</column> <column name="OccurDateTime">2006/12/29 12:34:04+08:00</column> <column name="AckDateTime">2007/1/6 09:14:06+08:00</column> <column name="ClearDateTime">2007/1/7 09:14:06+08:00</column> <column name="Operator">< system ></column>




Issue 02 (2008-09-05)

<column name="ClearOperator">admin</column> <column name="ExtendInfo" /> <column name="LinkFDN" /> <column name="LinkFDNName" /> <column name="LinkType" /> <column name="AlarmIdentifier" /> <column name="AlarmId">12</column> </Record></ExportFileInfo>

2.3 Alarm Export OperationsAlarm export operations consist of modifying the configuration files of the alarm export tool,setting the automatic alarm export, and stopping the automatic alarm export.

2.3.1 Modifying the Configuration File of the Alarm Export ToolBefore you export alarm files, set the number of fields, field sequence, and name description ofalarm information in the alarm export tool configuration file according to the following steps.

2.3.2 Setting Automatic Export of Alarm FilesAfter you set automatic alarm export, the alarm export tool automatically exports the alarmsgenerated in the alarm database after the last automatic export to a file in a specified format ata scheduled time every day.

2.3.3 Setting the Termination of Automatically Exporting Alarm FilesThis describes the procedure for setting the termination of automatically exporting alarm files.

2.3.1 Modifying the Configuration File of the Alarm Export ToolBefore you export alarm files, set the number of fields, field sequence, and name description ofalarm information in the alarm export tool configuration file according to the following steps.

PrerequisiteYou have logged in to the M2000 server as root.

Procedure

Step 1 Go to the M2000 installation folder.

The default M2000 installation path is /opt/OMC.

By default, run the following command:

# cd /opt/OMC

Step 2 To edit the configuration file, run the following command:

# vi etc/conf/english/fmexportsvc_field.xml

NOTE

Modify the configuration file according to the attached modification guide.

Step 3 To make the modified configuration file effective, run the following commands:

# . ./svc_profile.sh



2-5

# svc_adm -cmd reload

----End

2.3.2 Setting Automatic Export of Alarm FilesAfter you set automatic alarm export, the alarm export tool automatically exports the alarmsgenerated in the alarm database after the last automatic export to a file in a specified format ata scheduled time every day.

PrerequisiteYou have logged in to the M2000 client.

Procedure

Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.

Step 2 Click the Alarm Data Export on the navigation tree to view a task record.

Step 3 Double-click the task record. The Attribute window is displayed. Set Common Parametersand Extended Parameters.

Step 4 Click OK. The automatic export configuration is complete.

----End

2.3.3 Setting the Termination of Automatically Exporting AlarmFiles

This describes the procedure for setting the termination of automatically exporting alarm files.

Prerequisitel The conditions for the automatic alarm export are met.

l You have logged in to the M2000 client.

Context

After the automatic alarm export is enabled, you can stop it manually at any time.

For details on setting the automatic alarm export, see 2.3.2 Setting Automatic Export of AlarmFiles.

Procedure


Step 2 Click the Alarm Data Export in the navigation tree to view a task record.

Step 3 Right-click the task record and choose Suspend from the shortcut menu. The automatic exportof alarm files is stopped.

----End




Issue 02 (2008-09-05)

3 Introduction to Configuration Data ExportFile

This describes the configuration data export files: their detailed formats, deletion strategy, andfile types.

Path of Configuration Export Files

l File path of configuration data that is manually exported

The configuration data files that are manually exported are saved to a client directoryspecified by users,and it also automatically saves the export data to the/export/home/omc/var/fileint/cm/manualExport directory.

l File path of configuration data that is periodically exported

The configuration data files that are periodically exported are saved to the /export/home/omc/var/fileint/cm/autoExport/ directory.

Categories and Quantities of Configuration Export Files

When exporting configuration data, save each output of an NE to a new file.

Rules for Naming Configuration Export Files

l Rules for naming files

For automatic export, the files are named in the following format: CMExport_NEname_NE IP_Date and time.xml.

where,

– NE name indicates the name of an NE whose configuration data is exported.

– NE IP indicates the IP address of an NE.

– Date and time indicate when configuration data is exported. The format isYYYYMMDD.

For manual export, files are named by the user. Two export formats are available, that is,XML and CSV.

l Examples

M2000Northbound File Interface Developer Guide 3 Introduction to Configuration Data Export File


3-1

If the NE name is test1, the NE IP is 11.11.11.11, and the export time is 2005-06-25, thefile name is CMExport_test1_11.11.11.11_2005062509.xml.

Format of Configuration Export FilesThe configuration data files that are exported manually have the same format as the configurationdata files that are exported automatically. Configuration data files can be in the format of xmlor csv.

The description of files in .xml format is as follows:

Table 3-1 describes the format of configuration files.

Table 3-1 File format

Format Description

<MOTree> NE MO Tree.One exported configuration files corresponds to one NE, and thus only onepair of <MOTree> exists in a configuration file.

<MO> Corresponding to one MOI. The hierarchy is consistent with the MIT tree.The NE instance is at the top. Under the NE instance are equipment instanceand function instance. Under the equipment instance are several frameinstances.

<attr name> The attributes of the MOI.

<className> The name of the MOC that the MOI belongs to.

The instance of a file in .xml format is as follows:

<MOTree> <MO className="MSCServerNE" fdn=".3221229568.3221233664.3221282816"> <attr name="IP">100.0.44.122</attr> <attr name="InternalId">MSOFTX3000V100R005C10B318</attr> <attr name="MOIndex">0_1_1</attr> <attr name="className">MSCServerNE</attr> <attr name="district">110000</attr> <attr name="entityVersionId">3</attr> <attr name="fdn">.3221229568.3221233664.3221282816</attr> <attr name="isLocked">false</attr> <attr name="latitude">154.0</attr> <attr name="longitude">281.0</attr> <attr name="matchVersion">iManagerM2000_MSOFTX3000_MATCH_CHS_V200R005C01B021 </attr> <attr name="medPartition">default_med_partition</attr> <attr name="name">MSCServer</attr> <attr name="neID">0</attr> <attr name="neType">7</attr> <attr name="neVersion">MSC9880 MSOFTX3000V100R005C10B318</attr> <attr name="omcID">1</attr> <attr name="productID">2</attr> <attr name="realLatitude">0DN</attr> <attr name="realLongitude">0DE</attr> <attr name="subnetworkID">1</attr> <MO className="MSCServerFunction" fdn=".3221229568.3221233664.3221282816. 3221491712"> <attr name="CLASSNAME">MSCServerFunction</attr> <attr name="MOIndex">0</attr>

3 Introduction to Configuration Data Export FileM2000



Issue 02 (2008-09-05)

<attr name="className">MSCServerFunction</attr> <attr name="fdn">.3221229568.3221233664.3221282816.3221491712</attr> <attr name="name">MSCServerFunction</attr> <attr name="neID">0</attr> <MO className="SRVNODE" fdn=".3221229568.3221233664.3221282816.3221491712. 3221663744"> <attr name="MOIndex">0_LOCAL</attr> <attr name="SN">LOCAL</attr> <attr name="SN_IDX">0</attr> <attr name="className">SRVNODE</attr> <attr name="fdn">.3221229568.3221233664.3221282816.3221491712. 3221663744</attr> <attr name="name">Server name=LOCAL</attr> </MO> <MO className="MSCServerTimeZone" fdn=".3221229568.3221233664. 3221282816.3221491712.3221352448"> <attr name="MOIndex">.3221229568.3221233664.3221282816</attr> <attr name="className">MSCServerTimeZone</attr> <attr name="fdn">.3221229568.3221233664.3221282816.3221491712. 3221352448</attr> <attr name="name">EMSTZ</attr> <attr name="neID">0</attr> </MO></MO></MO></MOTree>

NOTE

In the example, some information is displayed in two lines because of the large quantity of the information.In actual configuration data files, the information occupies only one line.

The description of files in .csv format is as follows:

Every two lines in files in .csv format represent an MOI. A space line is used to separate eachtwo MOIs. Compared with files in .xml format, files in .csv format have no hierarchy relation.

Each MOI contains a line of attribute names and a line of attribute values. An attribute namemaps to an attribute value. In addition, each MOI contains the following two fields: classnameand fdn. The classname field indicates the table name of a database, namely, the belonged MOC.The fdn field identifies an MOI.

The instance of a file in .csv format is as follows:IP InternalId MOIndex className district entityVersionId fdn isLockedlatitude longitude matchVersion medPartition name neID neType neVersion omcID productID realLatitude realLongitude subnetworkID100.0.44.122 MSOFTX3000V100R005C10B318 0_1_1 MSCServerNE 110000 3.3221229568.3221233664.3221282816 FALSE 154 281 iManagerM2000_MSOFTX3000_MATCH_CHS_V200R005C01B021 default_med_partition MSCServer 0 7 MSC9880 MSOFTX3000V100R005C10B318 1 2 0DN 0DE 1 CLASSNAME MOIndex className fdn name neID MSCServerFunction 0 MSCServerFunction .3221229568.3221233664.3221282816.3221491712 MSCServerFunction 0 MOIndex SN SN_IDX className fdn name 0_LOCAL LOCAL 0 SRVNODE .3221229568.3221233664.3221282816.3221491712.3221663744 Servername=LOCAL MOIndex className fdn name neID .3221229568.3221233664.3221282816 MSCServerTimeZone .3221229568.3221233664.3221282816.3221491712.3221352448 EMSTZ 0

NOTE

In the example, the configuration data files is displayed in more lines because of the large quantity of theinformation. In actual configuration data files, the information occupies only one line.

M2000Northbound File Interface Developer Guide 3 Introduction to Configuration Data Export File


3-3

Deletion of Configuration Export FileThe system saves only one configuration file for the same NE each day, and only three copiesof the export file of the same NE are reserved. In this case, the first exported configuration fileis deleted in the further export. The same NE mentioned here refers to the NE whose name isthe same with the IP address.

If a third-part file management tool is used, the configuration rules of the third-part filemanagement tool are applied to manage the configuration files automatically exported.

Automatically Exporting NE Configuration DataThe automatic export function of the M2000 client supports the automatic export of NEconfiguration information.

1. Choose Maintenance > Task Management to view the Task Management window.2. Click the Configuration Data Export in the navigation tree to view a task record.3. Double-click the task record to view the Attribute dialog box. Set common parameters

and extended parameters.4. Click OK to finish the automatic export configuration.

Manually Exporting NE Configuration DataThe M2000 enables you to manually export configuration data of physical NEs. You can savethe configuration in relevant path.

1. Choose Configuration > MIT Browsing to view the MIT Browsing window.2. Expand the navigation tree and select a physical NE whose configuration data to be

exported.3. Right-click the NE and choose Export from the shortcut menu. The Configuration Data

Export dialog box is displayed.4. Type the file name and file saving path.5. Select the file saving type.6. Click Save.

3 Introduction to Configuration Data Export FileM2000



Issue 02 (2008-09-05)

4 Introduction to Configuration Export Files(Flat Export)

This describes the file path, categories, quantities, rules for naming files, format description,deletion strategy, and modification description of configuration export files.

NOTE

l In the current version, only BSC6000, RNC, and NodeB supports the flat export. For functionssupported by other NEs, see3 Introduction to Configuration Data Export File .

l The differences between flat export and the original configuration export are as follows: configuringthe saving days of export files, compressing export files, and flattening objects of MO instances inexport files.

Path of Configuration Export Files

l Path of configuration data that is manually exportedThe configuration data files that are manually exported are saved to a client directoryspecified by users,and it also automatically saves the export data to the/export/home/omc/var/fileint/cm/manualExport directory.

l Path of configuration data that is periodically exportedThe configuration data files that are periodically exported are saved to the /export/home/omc/var/fileint/cm/autoExport/ directory.

Categories and Quantities of Configuration Export Files

When exporting configuration data, save each output of an NE to a new file.

Rules for Naming Configuration Export Files

l Naming ruleFor automatic export, the files are named in the following format: CMExport_NEname_NE IP_Export time.xml.The NE name indicates the name of an NE whose configuration data is exported.NE IP indicates the IP address of an NE.Export time indicate when configuration data is exported. The format is YYYYMMDD.

M2000Northbound File Interface Developer Guide 4 Introduction to Configuration Export Files (Flat Export)


4-1

For manual export, files are named by the user. Three export formats are available, that is,xml, csv, and txt.

l ExampleIf the NE name is test1, the NE IP address is 10.161.85.204, and the Export time is 15:00at 2008-05-17,the file name is CMExport_test1_10.161.85.204_2008051715.xml.

Format of Configuration Export FilesThe formats of manual export and automatic export of configuration files are the same. Theformats are xml and csv.

The xml format:

Table 4-1 describes the files in xml format.

Table 4-1 File format of configuration data

Format Description

<MOTree> The NE MO treeAn exported configuration file corresponds to one NE, and thus only onepair of <MOTree> exists in a configuration file.

<MO> An <MO> corresponds to one MOI. The upper layer is the NE instance,which is followed by the other object instances. The object instances in thismodel do not interact with each other.

<attr name> Attribute of MOI

<className> Name of the MOC to which the MOI belongs

The following information is an example of the configuration export file:

<MOTree> <MO className="BSC6000NE" fdn=".3221229568.3221233664.3221282816"> <attr name="IP">10.161.101.230</attr> <attr name="fdn">.3221229568.3221233664.3221282816</attr> <attr name="latitude">224.0</attr> <attr name="longitude">279.0</attr> <attr name="matchVersion">iManagerM2000_BSC6000_MATCH_ENG_V200R006C01B451</attr> <attr name="name">BSC6000</attr> <attr name="neID">0</attr> <attr name="neType">BSC6000</attr> <attr name="neVersion">BSC6000V900R008C01</attr> <attr name="realLatitude">0DN</attr> <attr name="realLongitude">0DE</attr> <attr name="vendorName">huawei</attr> <MO className="BSC6000CPU" fdn=".3221229568.3221233664.3221282816.3221512192"> <attr name="CfgAdminState">Unlock</attr> <attr name="CpuNo">0</attr> <attr name="IS_MAIN_CHILD">True</attr> <attr name="MOIndex">0_0_4_0</attr> <attr name="OVERLOAD_THRESHOLD">85</attr> <attr name="SlotNo">4</attr> <attr name="SubRackNo">0</attr> <attr name="TYPE">MPC8280</attr> <attr name="UNDERSHOOT_THRESHOLD">75</attr>

4 Introduction to Configuration Export Files (Flat Export)M2000



Issue 02 (2008-09-05)

<attr name="className">BSC6000CPU</attr> <attr name="fdn">.3221229568.3221233664.3221282816.3221512192</attr> <attr name="name">CPU No.=0, Slot No.=4, Subrack No.=0</attr> <attr name="neID">0</attr> </MO> <MO className="BSC6000Cabinet" fdn=".3221229568.3221233664.3221282816.3221364736"> <attr name="CabinetNo">0</attr> <attr name="CabinetType">False</attr> <attr name="MOIndex">0_0</attr> <attr name="className">BSC6000Cabinet</attr> <attr name="fdn">.3221229568.3221233664.3221282816.3221364736</attr> <attr name="name">Cabinet No.=0</attr> <attr name="neID">0</attr> </MO> </MO></MOTree>

NOTE

In this example, some portions of the export file are displayed in two rows because the export file has largecontents. In the export file, these portions are actually displayed in one row.

The csv format:

In the csv file, two rows represent an MOI, which is separated by an empty row. There is nohierachical relation in the .csv file.

Each MOI contains a row of attribute name and a row of attribute value. The attribute name andvalue correspond to each other. Each MOI also contains the classname and fdn fields. Theclassname field corresponds the name of MOC, and fdn uniquely identifies an MOI.

The following information is an example of the configuration export file:

IP className fdn latitude longitude matchVersion name neID neType neVersion realLatitude realLongitude vendorName 10.161.100.175 BSC6000NE .3221229568.3221233664.3221282972 355 535 iManagerM2000_BSC6000_MATCH_ENG_V200R006C01B451 175 158 BSC6000 BSC6000V900R008C01 0DN 0DE huawei

CellIndex InterCellHyst MOIndex MinOffset NCellInterfType Neb2GCellIndex PBGTMargin className fdn name neID 1 4 158_1_3 0 0 3 68 BSC60002GAdjRel .3221229568.3221233664.3221282972.3222368260 Neighbor 2G Cell Index=3, cell index=1 158

CfgAdminState CpuNo IS_MAIN_CHILD MOIndex OVERLOAD_THRESHOLD SlotNo SubRackNo TYPE UNDERSHOOT_THRESHOLD className fdn name neID Unlock 0 TRUE 158_0_26_0 85 26 0 MPC8280 75 BSC6000CPU .3221229568.3221233664.3221282972.3222130730 CPU No.=0, Slot No.=26, Subrack No.=0 158

NOTE

In this example, some portions of the export file are displayed in multiple rows because the export file haslarge contents. In the export file, these portions are actually displayed in one row.

Deletion of Configuration Export File

For configuration data files that are automatically exported, the system saves only oneconfiguration file for the same NE each day. By default, the system saves the files exported bythe same NE for seven days. You can modify the configuration file to change the saving days.Configuration files whose saving period expires are deleted in the next export. The same NEmentioned here refers to the NE whose name is the same with the IP address.



4-3

Description of Configuration FilesYou can modify the tool to configure the /export/home/omc/var/etc/CMServer/NbiDataExportPara.xml file. You can configure the partial settings of the export function.

The contents of configuration files are as follows:<NbiDataExport> <ExpFileReservedDays name="exported file reserved days" value="7"/> <SupportGzip name="is support gzip" value="false"/> <ViewPoint name="Itf-N_DataExport"/> <NeTypes> <NeType name="BSC6000NE"/> </NeTypes> </NbiDataExport>Modify the ExpFileReservedDays and SupportGzip parameter items in the configuration file.

NOTEIf you modify ExpFileReservedDays and SupportGzip, you need to restart the CMServer service.

1. Modify parameters in ExpFileReservedDays.Set the saving days of export files. The default value is 7. You can modify the value ofExpFileReservedDays to set the saving days of export files.

2. Modify parameters of SupportGzip.Set whether to compress the result file.l If you set SupportGzip to false, the system does not compress the result file.

l If you set SupportGzip to true, the system compress the result file using the UNIXstandard and generates a compressed file with the extension name of gz.

3. Restart the CMServer service to validate the parameters.Switch to the installation directory of the M2000 (/opt/OMC by default) and run thefollowing command: # cd /opt/OMC # . ./svc_profile.sh # svc_adm -cmd restartsvc CMServer

NOTEThe functions of modifying the saving days and compressing files are applied to only scheduled export.The manual export does not support these functions.

Automatically Exporting NE Configuration DataYou can configure the automatic export function in the M2000 client.

1. Choose Maintenance > Task Management. The Task Management window isdisplayed.

2. Click Configuration Data Export in the navigation tree to view a task record.3. Double-click the task record to view the Attribute dialog box. Set common parameters

and extended parameters.4. Click OK to finish the automatic export configuration.

Manually Exporting NE Configuration DataThe M2000 enables you to manually export configuration data of physical NEs. You can savethe configuration in relevant path.

1. Choose Configuration > MIT Browsing to view the MIT Browsing window.

4 Introduction to Configuration Export Files (Flat Export)M2000



Issue 02 (2008-09-05)

2. Expand the navigation tree and select a physical NE whose configuration data to beexported.

3. Right-click the NE and choose Export from the shortcut menu. The Configuration DataExport dialog box is displayed.

4. Type the file name and file saving path.5. Select the file saving type.6. Click Save.



4-5

5 Introduction to Performance Data ExportTool and File

About This Chapter

This describes the performance data export tool and file.

5.1 Performance Data Export ToolThe performance export tool automatically exports performance results.

5.2 Configuration file of the Performance Data Export ToolThe configuration file of the performance data export tool exists in the directory /export/home/omc/var/etc/pm/tool/PMExpParam.xml. You can configure the partial settings of the exportfunction. You can modify the configuration file to set the performance export.

5.3 Performance Data Export FileThis describes the path, categories and quantities, and rules for naming performance export files.This also gives examples to illustrate performance export files.

5.4 Operations Related to the Performance Data Export ToolStarting the performance export tool and stopping the performance export tool.

5.5 Troubleshooting for the Performance Export ToolThis describes the procedure for performance export file when an performance export task fails.

M2000Northbound File Interface Developer Guide 5 Introduction to Performance Data Export Tool and File


5-1

5.1 Performance Data Export ToolThe performance export tool automatically exports performance results.

After the performance export tool starts, it automatically exports specified performance resultsto a file when the preset period ends. The exported performance results still exist in theperformance database.

5.2 Configuration file of the Performance Data Export ToolThe configuration file of the performance data export tool exists in the directory /export/home/omc/var/etc/pm/tool/PMExpParam.xml. You can configure the partial settings of the exportfunction. You can modify the configuration file to set the performance export.

The contents of the configuration file are as follows:

<TimeSegmentSet> <BeginTime Name="Begin time." Value="2006-10-29 00:00"/> <EndTime Name="End Time." Value="2006-10-29 23:59"/></TimeSegmentSet><GeneralSet> <CounterSortMode Name="Counter display and sort mode." Value="0"/> <CounterValueFormat Name="Counter value fromat." Value="0"/> <QueryTimeMode Name="Query result time mode." Value="0"/> <DisplayTimeZone Name="Display time zone information." Value="0"/> <DisplayDstOffSet Name="Display timezone offset information." Value="0"/> <DeleteFileTime Name="Delete file time." Value="1:30"/> <QueryHours Name="Query result hours." Value="5"/> <QueryExportFormat Name="Query result export format." Value="0"/> <FileExportMode Name="File export format." Value="1"/> <OMCServerName Name="OMC server name." Value=""/> <RANShared Name="RAN shared and result transmit mode" IsShared="0" TransmitMode="2"/> <GZip Name="Compress file or not." Value="0"/> <TemplateMode Name="Template File Name Format" Value="0"/></GeneralSet><EffectiveSet> <PMDBConnNum Name="PMDB database connection number." Value="10"/> <MethodThreadNum Name="Active method's thread number." Value="2"/> <TableThreadNum Name="Process table's thread number." Value="3"/> <BulkReaderNum Name="Bulk read record number." Value="5000"/></EffectiveSet>

The following part describes the configuration items:

<TimeSegmentSet> configures a time segment for exporting results to a file.

l BeginTimeThis item sets the start time for exporting results.

l EndTimeThis item sets the end time for exporting results.

5 Introduction to Performance Data Export Tool and FileM2000



Issue 02 (2008-09-05)

NOTE

The set end time must be later than the start time.If the span between the start time and the end time is too long, the export function is affected.Therefore, you are advised to set the span to not more than five days.If you plan to collect the data of a long period, you can configure the start time and the end time forseveral times. For example, if you plan to collect the performance data from 2006-01-01 to2006-01-10, you can collect the performance data from 2006-01-01 to 2006-01-05 first by settingBeginTime=2006-01-01 00:00, EndTime=2006-01-05 00:00 in the configuration file. After theperformance data within the period is exported, you can collect the perform data from 2006-01-05to 2006-01-10 by setting the BeginTime=2006-01-05 00:05, EndTime=2006-01-10 00:00 in theconfiguration file.

l GeneralSetGeneralSet contains common configuration items, which can be modified as required.

l CounterSortModeThis item sets the sequence of counters in the result file.– If the value of CounterSortMode is set to 0, the counters in the exported file are

arranged in ascending order based on the character string sizes of counter names.– If the value of CounterSortMode is set to 1, the counters in the exported file are

arranged in ascending order based on counter IDs.– If the value of CounterSortMode is set to 2, the counters in the exported file are

arranged in ascending order based on the character string ASCII codes of counter names.l CounterValueFormat

This item sets a display mode for counter values in the result file.– If the value of CounterValueFormat is set to 0, the counter values of the measurement

unit that contains only non-character-string counters are not marked with quotationmarks in the exported result file. The counter values of the measurement unit thatcontains character-string counters, however, are marked with quotation marks.

– If the value of CounterValueFormat is set to 1, all the counter values in the exportedresult file are marked with quotation marks.

– If the value of CounterValueFormat is set to 2, none of the counter values in theexported result file are marked with quotation marks.

l QueryTimeModeThis item sets a time mode for querying results.– If the value of QueryTimeMode is set to 0, the result is queried according to server

time and displayed according to NE time. The name of the result file is server time andthe start time in the file is NE time.

– If the value of QueryTimeMode is set to 1, the result is queried according to servertime and displayed according to server time. The name of the result file is server timeand the start time in the file is server time.

l DisplayTimeZoneThis item sets whether to display the time zone information.– If the value of DisplayTimeZone is set to 0, the system does not display the time zone

information.– If the value of DisplayTimeZone is set to 1, the system displays the time zone

information.l DisplayDstOffSet

This item sets whether to display the DST offset information.



5-3

– If the value of DisplayDstOffSet is set to 0, the system does not display the DST offsetinformation.

– If the value of DisplayDstOffSet is set to 1, the system displays the DST offsetinformation.

l DeleteFileTimeThis item sets the execution time for deleting the overdue exported files.By default, the system deletes the overdue exported files at 01:30 in the morning every day.

l QueryHoursThis item sets the number of periods for querying the recollected results.After this item is set, the system checks whether there is recollected data available withinthe set time range once the timer is triggered.For example, if the value of QueryHours is set to 5, the system checks whether there isthe recollected data available within the time range 10:00 to 15:00 when the timer istriggered at 15:00. If the recollected data is available, the data is exported to thecorresponding file.

l QueryExportFormatThis item sets the implementation mode for exporting the recollected results.– If the value of QueryExportFormat is set to 0, export all the results and re-write the

existing exported files if the recollected data is available.– If the value of QueryExportFormat is set to 1, export the recollected data to another

file. The file name is different, which is pmresult_measurement unit ID_measurementperiod_start time_end time_recover_current system time.csv orpmresult_measurement unit ID_measurement period_start time_endtime_recover_current system time.xml. The existing exported files do not have anychange.

l FileExportModeThis item sets the format of file names.– If the value of FileExportMode is set to 0, a file name does not include the name of

the host or the name of the NE type.– If the value of FileExportMode is set to 1, a file name includes the name of the host

and the name of the NE type. The format of a file name is pmresult_Name of ahost_Name of the NE Type_150999067_5_200710121535_200710121540.xml, suchas pmresult_M2000svr-CDMA_HLR_150999067_5_200710121535_200710121540.xml.

l OMCServerNameThis item sets the name of the server. The value is null by default.– If the value of OMCServerName is not null, the name of the exported file is server

name_pmresult_function subset_measurement period_start time_end time.csv. Forexample, if the value of OMCServerName is set to MyServer, the name of an exportedfile is MyServer_pmresult_function subset_measurement period_start time_endtime.csv.

– If the value of OMCServerName is null, the name of the exported file ispmresult_function subset_measurement period_start time_end time.csv.

l RANSharedThis item sets whether the RAN sharing mode is used. The value is common mode bydefault.




Issue 02 (2008-09-05)

– If IsShared is set to 0, you can infer that RANShared is common mode.

– If IsShared is set to 1, you can infer that RANShared is RAN sharing mode.For the RAN sharing mode, you can set the TransmitMode parameter to determine themode to forward non-cell data. TransmitMode = 0 indicates that the data is forwardedto all operators. TransmitMode = 1 indicates that the data is forwarded to none of theoperators. TransmitMode = 2 indicates that the data is forwarded to only primaryoperators.

l GZipThis item sets whether to compress the result files.– If the value of GZip is set to 0, the result files are not compressed.

– If the value of GZip is set to 1, the result files are compressed according to the UNIXstandard. The extension of the compressed file is gz.

l TemplateModeThis item sets the format of the template name.– If the value of TemplateMode is set to 0, the template name is contained in the name

of the result file.– If the value of TemplateMode is set to 1, the template ID is contained in the name of

the result.The <EffectiveSet> portion is a parameter for setting the export efficiency. You are notallowed to modify the parameter because each configuration item is closely related to otherconfiguration items.

l PMDBConnNumThis item sets the number of connections allowable for the database.

l MethodThreadNumThis item sets the number of threads for initializing the active thread mode.

l TableThreadNumThis item sets the number of threads used by the timer for triggering the result processingtable.

l BulkReaderNumThis item sets the number of results read in batches at a time when the system queries resultsin the database result table.

NOTE

You are not required to restart the export tool after modifying BeginTime and EndTime of<TimeSegmentSet>. For the modification of other parameters, you must restart the export tool.

This describes how to set the parameters related with the export of the performance results ofintegrated task management.

In the version of M2000V200R005, the following parameters are added to the integrated taskmanagement. These parameters can be set directly on M2000 client.

NOTE

l The export function is controlled by the administration console and cannot be modified.

l The parameters such as saving days, measurement unit, measurement period, and delay can bedirectly set on M2000 client.

l File export path: /export/home/omc/var/fileint/pm/



5-5

The default path is /export/home/omc/var/fileint/pm/. It cannot be modified on M2000client.

l Saving days: 90You can modify the saving days. After this parameter is set, the system regularly deletesthe overdue exported result files.The system deletes the overdue exported result files once each day.

l Measurement unit, measurement period, export period, and delay.Set the number of a function subset, and the measurement period, export period (unit:minute), and delay (unit: minute; optional) of the function set. The measurement period,export period, and delay must be integer multiples of five, for example, 5, 15, 30, 60, or1,440. The delay must be integer multiples of five. The default delay is used if you do notset DELAY. The delay of function subsets has higher priority over the default delay.After you set all the parameters, the performance results of the specified time ranges areexported to the specified files after the preset delay ends. The time range is divided basedon the export period. Table 5-1 lists the common export periods and time ranges.

Table 5-1 Export periods and time ranges

Export Period(minute) Time Ranges

5 Every five minutes is a time range, for example, 00:00-00:05,00:05-00:10, 00:10-00:15, 00:15-00:20....

15 Every fifteen minutes is a time range, for example, 00:00-00:15,00:15-00:30, 00:30-00:45, 00:45-00:60....

30 Every half an hour is a time range, for example, 00:00-00:30,00:30-1:00, 1:00-1:30, 1:30-2:00....

60 Every one hour is a time range, for example, 0:00-1:00, 1:00-2:00,2:00-3:00, 3:00-4:00....

1440 Every day is a time range, for example, 0:00-24:00.

For example, if you set the export period to 60 minutes and the delay to 30 minutes, theperformance export tool exports the performance results of the time range 0:00-1:00 at1:30, and of the 1:00-2:00 at 2:30.

5.3 Performance Data Export FileThis describes the path, categories and quantities, and rules for naming performance export files.This also gives examples to illustrate performance export files.

Path of Performance Export Files

The file export path is set uniformly by the integrated task management function. By default,the files are exported to the /export/home/omc/var/fileint/pm/ directory, After the performanceexport tool starts, it creates a folder in the directory automatically on a daily basis. The folders




Issue 02 (2008-09-05)

are named in the pmexport_Date of the day format. The files that are generated on the sameday are saved in the same folder.

For example, the pmexport_20060215 folder saves all the performance files exported onFebruary 15, 2006.

the M2000 automatically creates the FTP user and performance export directory. In addition,the M2000 binds the directory with user rights to manage performance export files.

The NMS user can access the authorized directory through the FTP to obtain performance exportfiles.

Categories and Quantities of Performance Export FilesWhen performance results are exported, note the following two scenarios:l If function subsets are configured in performance files, save the result of each function

subset to a file.l If templates are configured in performance files, save the result of each template to a file.

Rules for Naming Performance Export Filesl Exporting files not by template

The name of the file for saving performance results can be pmresult_Function subsetID_Measurement period_Start time_End time.file type.Performance export files support the following formats:– .csv

– .xml

– .txt

For example, the name of the performance export filepmresult_67109445_30_200507041030_200507041100.csv indicates:– The time range is from 10:30 to 11:00 on July 4, 2005.

– The number of the function subset is 67109445.

– The measurement period is 30 minutes.

l Exporting files by templateA template can support the query of multiple function subsets at the same time.The rules for naming the file that is used to save performance results are as follows:– If a template contains only one function subset and a template ID is configured

The name of the file for saving performance results can be pmresult_Function subsetID_Measurement period_Start time_End time_Template ID.csv or pmresult_Functionsubset ID_Measurement period_Start time_End time_Template ID.xml.For example, the name of the performance export filepmresult_67109445_30_200507041030_200507041100_10001.csv indicates:– The time range is from 10:30 to 11:00 on July 4, 2005.

– The ID of the function subset is 67109445.


– The template ID is 10001.



5-7

– If a template contains only one function subset and a template name is configuredThe name of the file for saving performance results can be pmresult_Function subsetID_Measurement period_Start time_End time_Template Name.csv orpmresult_Function subset ID_Measurement period_Start time_End time_TemplateName.xml.For example, the name of the performance export filepmresult_67109445_30_200507041030_200507041100_TCPState.csv indicates:– The time range is from 10:30 to 11:00 on July 4, 2005.

– The ID of the function subset is 67109445.


– The template name is TCPState.

– If a template contains multiple function subsets and a template ID is configuredThe name of the file for saving performance results can be pmresult_Measurementperiod_Start time_End time_Template ID.csv or pmresult_Function subsetID_Measurement period_Start time_End time_Template ID.xml.For example, the name of the performance export filepmresult_30_200507041030_200507041100_10001.csv indicates:– The time range is from 10:30 to 11:00 on July 4, 2005.


– The template ID is 10001.

– If a template contains multiple function subsets and a template name is configuredThe name of the file for saving performance results can be pmresult_Measurementperiod_Start time_End time_Template Name.csv or pmresult_Measurementperiod_Start time_End time_Template Name.xml.For example, the name of the performance export filepmresult_30_200507041030_200507041100_ TCPState.csv indicates:– The time range is from 10:30 to 11:00 on July 4, 2005.


– The template name is TCPState.

Examples of Performance Export Files

l An example of the performance export file in .csv formatIn this example, the performance export file is set in .csv format.In the configuration file PMExpParam.xml, the configuration item CounterSortMode,which is set to 0 or 2, determines that the exported result file is displayed by the countername.The exported result file is as follows.– As the title, the first row is as follows:

Result Time | Granularity Period | Object Name | Reliability | Name of Counter 1 | Name of Counter 2 | ......

– The second row lists the units.The unit is displayed if the unit exists; otherwise, Null is displayed. The second row isshown as follows:




Issue 02 (2008-09-05)

Null | Minutes | Null | Null | Unit of Counter 1 | Unit of Counter 2 |......

– From the third row, the information about the performance results is displayed accordingto the field name in the first row. Each result record occupies one row.

For example:Result Time,Granularity Period ,Object Name,Reliability,"ABNORMAL RELEASE TIMES ","CIRCUIT BLOCKED BY PEER END TIMES","MSG FORMAT ERROR TIMES", "NO BLA TO T13 TIMES","NO CLF TO T5 TIMES",Minutes,,,times,times,times,times,times2005-12-6 4:30,30, "softx_test/Office:OFFICEDIR=2/subRouteNo:SRC=2/Group:TG=22",Reliable,11063,9071,24817,5903,52482005-12-6 4:30,30, "softx_test/Office:OFFICEDIR=3/subRouteNo:SRC=3/Group:TG=3",Reliable,6724,31445,31621,3221,21711

It is assumed that CounterSortMode=1 is set.In the configuration file PMExpParam.xml, the configuration item CounterSortMode,which is set to 1, determines that the exported result file is displayed by the counter ID.The exported result file is as follows.The first row is the title, as follows:Result Time | Granularity Period | Object Name | Reliability | Name of Counter 1 | Name of Counter 2 | ......The second row lists the units. The unit is displayed if the unit exists; otherwise, Null isdisplayed. The second row is shown as follows:Null | Minutes | Null | Null | Unit of Counter 1 | Unit of Counter 2 |......From the third row, the information about the performance results is displayed accordingto the field name in the first row.For example:Result Time,Granularity Period,Object Name,Reliability,"84149755","84149756","84149757","84149758","84149759","84149760","84149761","84149762",Minutes,,,times,times,times,times,times,times,times,times2006-05-23 15:00,30,"msc_b035/MSCServer:msc_b035",Reliable,9460,2824,31106,25564,5173,19433,16631,20223

l An example of the performance export file in .xml formatIn this example, the performance export file is set in .xml format.In the configuration file PMExpParam.xml, the configuration item CounterSortMode,which is set to 0 or 2, determines that the exported result file is displayed by the countername. The exported result file is as follows.<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE mdc SYSTEM "MeasDataCollection.dtd"><mdc><mfh><cbt>200511200900</cbt></mfh><md><mi><mts>200511200900</mts><gp>30</gp><mt>Duration of link in the In-service state</mt><mt>Number of signal units received in error</mt><mt>Duration of SL unavailability(for any reason)</mt><mt>Number of SIF and SIO octets transmitted</mt><mt>MSUs discarded due to SL congestion</mt><mv><moid>msc_zd/MSCServer:msc_zd</moid><r>0</r><r>0</r>



5-9

<r>0</r><r>0</r><r>0</r><sf>false</sf></mv></mi></md><mff><ts>200511200930</ts></mff></mdc>

<sf></sf> indicates the reliability of the value for a object. sf is the abbreviation ofsuspect flag.

– <sf>false</sf>: indicates reliable.

– <sf>true</sf>: indicates unreliable.

It is assumed that CounterSortMode=1 is set.

In the configuration file PMExpParam.xml, the configuration item CounterSortModewhich is set to 1, determines that the exported result file is displayed by the counter ID.

l Format of an object name

The format of an object name is NE name (the first level)/identifier of object name (thesecond level):value of object name (the second level)/identifier of object name (the thirdlevel):value of object name (the third level)/identifier of object name (the fourthlevel):value of object name (the fourth level)/....

NOTE

The "/" symbol indicates the separator of object levels.

The identifier of an object at a layer is located on the left of the ":" symbol. The value of an objectat a layer is located on the right of the ":" symbol.

For example:

The name of an object with two levels can be RNC4/Cell:Label=Cell22081, CellID=22081.

The name of an object with three levels can be RNC4/MTP3BLinkSet:Label=LinkSet0,INDEX=0/MTP3BLink:Label=LindSet0,LKS=0,SLC=0.

5.4 Operations Related to the Performance Data Export ToolStarting the performance export tool and stopping the performance export tool.

5.4.1 Modifying the Configuration File of the Performance Data Export ToolModifying parameters of the configuration file of the performance data export tool, such asBeginTime, EndTime, CounterSortMode, CounterValueFormat, QueryTimeMode,DisplayTimeZone, and so on.

5.4.2 Setting Export Tasks on the M2000 ClientYou can set performance export tasks on the M2000 client.

5.4.3 Starting the Performance Data Export ToolThis describes the procedure for starting the performance data export tool.

5.4.4 Stopping the Performance Data Export ToolThis describes the procedure for stopping the performance data export tool.




Issue 02 (2008-09-05)

5.4.1 Modifying the Configuration File of the Performance DataExport Tool

Modifying parameters of the configuration file of the performance data export tool, such asBeginTime, EndTime, CounterSortMode, CounterValueFormat, QueryTimeMode,DisplayTimeZone, and so on.

ContextNOTE

You are not required to restart the export tool after modifying BeginTime and EndTime of<TimeSegmentSet>. For the modification of other parameters, you must restart the export tool.

Procedure

Step 1 Modify BeginTime.

This item sets the start time for exporting results.

Step 2 Modify EndTime.

This item sets the end time for exporting results.

NOTE

The set end time must be later than the start time.

If the span between the start time and the end time is too long, the export function is affected. Therefore,you are advised to set the span to not more than five days.

If you plan to collect the data of a long period, you can configure the start time and the end time for severaltimes. For example, if you plan to collect the performance data from 2006-01-01 to 2006-01-10, you cancollect the performance data from 2006-01-01 to 2006-01-05 first by setting BeginTime=2006-01-01 00:00,EndTime=2006-01-05 00:00 in the configuration file. After the performance data within the period isexported, you can collect the perform data from 2006-01-05 to 2006-01-10 by setting theBeginTime=2006-01-05 00:05, EndTime=2006-01-10 00:00 in the configuration file.

Step 3 Modify GeneralSet.

GeneralSet contains common configuration items, which can be modified as required.

Step 4 Modify CounterSortMode.

This item sets the sequence of counters in the result file.l If the value of CounterSortMode is set to 0, the counters in the exported file are arranged

in ascending order based on the character string sizes of counter names.l If the value of CounterSortMode is set to 1, the counters in the exported file are arranged

in ascending order based on counter IDs.l If the value of CounterSortMode is set to 2, the counters in the exported file are arranged

in ascending order based on the character string ASCII codes of counter names.

Step 5 Modify CounterValueFormat.

This item sets a display mode for counter values in the result file.l If the value of CounterValueFormat is set to 0, the counter values of the measurement unit

that contains only non-character-string counters are not marked with quotation marks in theexported result file. The counter values of the measurement unit that contains character-stringcounters, however, are marked with quotation marks.



5-11

l If the value of CounterValueFormat is set to 1, all the counter values in the exported resultfile are marked with quotation marks.

l If the value of CounterValueFormat is set to 2, none of the counter values in the exportedresult file are marked with quotation marks.

Step 6 Modify QueryTimeMode.

This item sets a time mode for querying displayed results.l If the value of QueryTimeMode is set to 0, the system queries displayed results in NE time

mode.l If the value of QueryTimeMode is set to 1, the system queries displayed results in server

time mode.

Step 7 Modify DisplayTimeZone.

This item sets whether to display the time zone information.l If the value of DisplayTimeZone is set to 1, the system displays the time zone information.

l If the value of DisplayTimeZone is set to 0, the system does not display the time zoneinformation.

Step 8 Modify DisplayDstOffSet.

This item sets whether to display the DST offset information.l If the value of DisplayDstOffSet is set to 1, the system displays the DST offset information.

l If the value of DisplayDstOffSet is set to 0, the system does not display the DST offsetinformation.

Step 9 Modify DeleteFileTime.

This item sets the execution time for deleting the overdue exported files.

By default, the system deletes the overdue exported files at 01:30 in the morning every day.

Step 10 Modify QueryHours.

This item sets the number of periods for querying the recollected results.

After this item is set, the system checks whether there is recollected data available within theset time range once the timer is triggered.

For example, if the value of QueryHours is set to 5, the system checks whether there is therecollected data available within the time range 10:00 to 15:00 when the timer is triggered at15:00. If the recollected data is available, the data is exported to the corresponding file.

<EffectiveSet> is a parameter for setting export efficiency. The configuration items are mutuallydependent. The configuration of this item cannot be modified.

Step 11 Modify QueryExportFormat.

This item sets the implementation mode for exporting the recollected results.l If the value of QueryExportFormat is set to 0, export all the results and re-write the existing

exported files if the recollected data is available.l If the value of QueryExportFormat is set to 1, export the recollected data to another file.

The file name is different, which is pmresult_measurement unit ID_measurementperiod_start time_end time_recover_current system time.csv or pmresult_measurement




Issue 02 (2008-09-05)

unit ID_measurement period_start time_end time_recover_current system time.xml. Theexisting exported files do not have any change.

Step 12 Modify FileExportMode.

This item sets the format of file names.l If the value of FileExportMode is set to 0, a file name does not include the name of the host

or the name of the NE type.l If the value of FileExportMode is set to 1, a file name includes the name of the host and the

name of the NE type. The format of a file name is pmresult_Name of a host_Name of theNE Type_150999067_5_200710121535_200710121540.xml, such aspmresult_M2000svr-CDMA_HLR_150999067_5_200710121535_200710121540.xml.

Step 13 Modify OMCServerName.

This item sets the name of the server. The value is null by default.

l If the value of OMCServerName is not null, the name of the exported file is servername_pmresult_function subset_measurement period_start time_end time.csv. Forexample, if the value of OMCServerName is set to MyServer, the name of an exported fileis MyServer_pmresult_function subset_measurement period_start time_end time.csv.

l If the value of OMCServerName is null, the name of the exported file is pmresult_functionsubset_measurement period_start time_end time.csv.

Step 14 Modify RANShared.

This item sets whether the RAN sharing mode is used. The value is common mode by default.

l If IsShared is set to 0, you can infer that RANShared is common mode.

l If IsShared is set to 1, you can infer that RANShared is RAN sharing mode.For the RAN sharing mode, you can set the TransmitMode parameter to determine the modeto forward non-cell data. TransmitMode = 0 indicates that the data is forwarded to alloperators. TransmitMode = 1 indicates that the data is forwarded to none of the operators.TransmitMode = 2 indicates that the data is forwarded to only primary operators.

Step 15 Modify GZip.

This item sets whether to compress the result files.

l If the value of GZip is set to 0, the result files are not compressed.

l If the value of GZip is set to 1, the result files are compressed according to the UNIX standard.The extension of the compressed file is gz.

Step 16 Modify TemplateMode.

This item sets the format of the template name.

l If the value of TemplateMode is set to 0, the template name is contained in the name of theresult file.

l If the value of TemplateMode is set to 1, the template ID is contained in the name of theresult file.

Step 17 Modify PMDBConnNum.

This item sets the number of connections allowable for the database

Step 18 Modify MethodThreadNum.



5-13

This item sets the number of threads for initializing the active thread mode.

Step 19 Modify TableThreadNum.

This item sets the number of threads used by the timer for triggering the result processing table.

Step 20 Modify BulkReaderNum.

This item sets the number of results read in batches at a time when the system queries results inthe database result table.

In the version of M2000V200R005, the following parameters are added to the integrated taskmanagement. These parameters can be set directly on M2000 client.

NOTE

l The export function is controlled by the administration console and cannot be modified.

l The parameters such as saving days, measurement unit, measurement period, and delay can be directlyset on M2000 client.

Step 21 Modify the saving days.

You can modify the saving days. After this parameter is set, the system regularly deletes theoverdue exported result files.

NOTE

The system deletes the overdue exported result files once for each day.

Step 22 Modify the measurement unit, measurement period, export period , and delay.

Set the number of a function subset, and the measurement period, export period (unit: minute),and delay (unit: minute; optional) of the function set. The measurement period, export period,and delay must be integer multiples of five, for example, 5, 15, 30, 60, or 1,440. The delay mustbe integer multiples of five. The default delay is used if you do not set DELAY. The delay offunction subsets has higher priority over the default delay.

After you set all the parameters, the performance results of the specified time ranges are exportedto the specified files after the preset delay ends. The time range is divided based on the exportperiod. Table 5-1 lists the common export periods and time ranges.

----End

5.4.2 Setting Export Tasks on the M2000 ClientYou can set performance export tasks on the M2000 client.

PrerequisiteYou have logged in to the M2000 client.

Procedure


Step 2 Choose File Interface > Performance Data Export in the navigation tree to view aperformance data export task.

Step 3 Use either of the following methods to view the Attribute dialog box:




Issue 02 (2008-09-05)

l Double-click a performance data export task in the task list.

l Select a performance data export task in the task list. Then click Attribute.

Step 4 Click the Extended Parameter tab.

Step 5 Set the performance data export task.

Table 5-2 describes the parameters of a performance data export task.

Table 5-2 Parameters of performance data export tasks

Parameter Description

File Format Three formats are available, that is,l .csv

l .xml

l .txt

Hold Days Sets the hold days of an exported file. For example, if this parameteris valued 90, you can infer that the file can be saved for 90 days afterthe day it is exported and that it is deleted after 90 days.

File Path Path for saving the exported file, which is set by the system.This parameter cannot be modified.

Measure Period The following five measure periods are available:l 5 minutes

l 15 minutes

l 30 minutes

l 60 minutes

l 24 hours

Function Subsets 1. Select the measure period from the Measure Period drop-downtab.

2. Select the export period from the Export Period drop-down list.The export period must be equal to or greater than the measureperiod.

3. Input the delay period to the Delay Period textbox. The exporttool exports files according to the export period and delay period.

4. Select the measure subset.

Template To export the performance data by using a template, you need toselect the template and set the delay time.

NOTE

For measurement subsets with the same measurement period, you can configure only one export period.

Step 6 Click OK.



5-15

Then the system saves the export task, according to which the export tool exports files at thescheduled time.

----End

5.4.3 Starting the Performance Data Export ToolThis describes the procedure for starting the performance data export tool.

PrerequisiteLog in to the M2000 server as root.

ContextThe performance export tool is a service, PMExport, provided by the M2000. It starts and stopsafter the M2000 starts and stops. You can start the performance export tool manually during theoperation of the M2000.

Procedure



# cd /opt/OMC

Step 2 Start the performance export tool.


# svc_adm -cmd startsvc PMExport

The performance export tool starts successfully if the following prompt is displayed:

PMExport [started ]

The performance export tool is running properly if the following prompt is displayed:

PMExport [running ]

----End

5.4.4 Stopping the Performance Data Export ToolThis describes the procedure for stopping the performance data export tool.

PrerequisiteLog in to the M2000 server as root.

ContextThe performance export tool is a service, PMExport, provided by the M2000. It starts and stopsafter the M2000 starts and stops. You can stop the performance export tool manually during theoperation of the M2000.




Issue 02 (2008-09-05)

Procedure



# cd /opt/OMC

Step 2 Stop the performance export tool.


# svc_adm -cmd stopsvc PMExport

The performance export tool stops if the following prompt is displayed:

PMExport............................stopped ------------cost: 3*1500(msec)------------ svc_adm : info : INDIE_STOP finished

The performance export tool is not running if the following prompt is displayed:

svc_adm:error:service is not running

----End

5.5 Troubleshooting for the Performance Export ToolThis describes the procedure for performance export file when an performance export task fails.

Operation Log of the Performance Export ToolAll information displayed during the operation of the performance export tool is recorded intothe <M2000 server installation folder>/var/logs/pmexport.trace file. Check the tool operationstatus in this file.

NOTE

If some performance export files are missing while others exist, the M2000 automatically conductssupplementary collection to obtain the lost data.

No Performance Results Are Exported to Files as ExpectedThe performance export tool starts and has been running for a while, however no performanceresults are exported as expected.

To correct the fault, perform the following steps:

1. Log in to the M2000 server as root.2. Go to the M2000 installation folder.

The default M2000 installation path is /opt/OMC.# cd /opt/OMC

3. Check that the service PMExport is running.# . ./svc_profile.sh# svc_adm -cmd status | grep PMExportThe performance export tool is not running if the following prompt is displayed:



5-17

PMExport [not running ]In such a situation, start the performance export tool manually. For details, see 5.4.3Starting the Performance Data Export Tool.The performance export tool is running properly if the following prompt is displayed:PMExport [running ]

4. Check the log file <M2000 server installation folder>/var/logs/pmexport.trace for errors.Proceed accordingly based on the error information.

NOTE

It is normal that the pmexport.trace file shows Time out!.

5. If the time zone where the NEs are located does not coincide with that of the M2000 server,set QueryTimeMode to 1 in the PMExpParam.xml file in the directory of /export/home/omc/var/etc/pm/tool.

Performance Export Tool's Special Treatment to Different Time Zones and DST1. The DST offset displayed in the name of an exported file does not refer to the DST.2. When you set QueryExportFormat to 0 and QueryTimeMode to 0, you can infer that

the NE and the NM are in different time zones. For instance, if NE1 and NE2 are locatedin the time zones GMT+4:00 and GMT+10:00 respectively and the M2000 is in GMT+8:00,the result file is exported according to the GMT+8:00 of the server and the contents of theresult file are displayed according to NE time.In this situation, set QueryTimeMode to 1 and export the result according to the servertime.

3. Take the NM is in GMT-5 for example. The DST rule of 2006 specifies that you shouldset the time one hour earlier from 02:00 on April 2nd to 02:00 on October 29th. That is, setthe time 02:00 to 03:00 on April 2nd, and then set the time 02:00 to 01:00 on October 29th.For the period from 01:00 DST to 02:00 on October 29th, the rule for exporting results ofthis repeated period is as follows:l When you set QueryExportFormat to 0, and QueryTimeMode to 0 or 1, the NM is

in DST. The results of the last one or two periods from the time 01:00 DST on October29th to the time 01:00 DST on October 29th are exported with one hour delay. Theresults generated in the period from 01:00 DST on October 29th to 02:00 DST onOctober 29th and in the period from 01:00 on October 29th to 02:00 on October 29thare exported in the same file. The DST identifies the period to which the data belong.

l When you set QueryExportFormat to 1 and QueryTimeMode to 0 or 1, the NM isin DST. The last one or two results generated in the period from 01:00 DST on October29th to 01:00 on October 29th are exported in an hour delay. The data generated in theperiod from 01:00 on October 29th to 02:00 on October 29th cannot be exported.

For this period, Huawei recommends that you set QueryExportFormat to 0 andQueryTimeMode to 1. The results are exported based on the server time.




Issue 02 (2008-09-05)

6 Introduction to NE-Based Performance DataExport Tool and File

About This Chapter

This describes the NE-based performance data export tool and file.

6.1 Introduction to NE-Based Performance Data Export ToolThe performance data export tool implements the automatic export function by NE. Using thistool shortens the time for exporting the performance data file, and thus accelerate thetransmission of the file to the upper-layer NMS.

6.2 Introduction to Configuration Files of NE-Based Performance Data Export ToolThis describes the configuration files of the performance data export tool and the meaning ofeach parameter in the configuration files.

6.3 Introduction to NE-Based Performance Data Export FileThis part describes the path, type, and rule for naming the performance export file. In addition,the example of a performance export file is provided.

6.4 Operations Related to NE-Based Performance Data Export ToolThis describes how to start and stop the performance data export tool.

6.5 Troubleshooting for NE-Based Performance Data Export ToolThis describes the troubleshooting for the performance data export tool if an export task fails tobe performed.

M2000Northbound File Interface Developer Guide

6 Introduction to NE-Based Performance Data Export Tooland File


6-1

6.1 Introduction to NE-Based Performance Data Export ToolThe performance data export tool implements the automatic export function by NE. Using thistool shortens the time for exporting the performance data file, and thus accelerate thetransmission of the file to the upper-layer NMS.

After the tool runs, the Mediation Service of the performance mediation layer receives theperformance result file of an NE every time and then forwards the parsed data to the tool. Afterhandling the data, the tool exports the data to an .xml file by NE. Exporting the handled dataoccurs concurrently with archiving the performance results performed by the mediation layer.

NOTEExporting data by NE reduces the export delay.

6.2 Introduction to Configuration Files of NE-BasedPerformance Data Export Tool

This describes the configuration files of the performance data export tool and the meaning ofeach parameter in the configuration files.

The performance data export tool contains two configuration files:PMMedExportParam.xml and PMMedExportView.xml. The PMMedExportParam.xmlfile is used to set the functional items such as the format of the exported performance data andexported file management. The PMMedExportView.xml file is used to set the data view to beexported. This data view is based on the counters and periods measured by the M2000.

The two configuration files of the performance data export tool are respectively saved in thefollowing default directories: /opt/OMC/etc/PMMedExport/PMMedExportParam.xmland /opt/OMC/etc/PMMedExport/PMMedExportView.xml. The following part describesthe contents and parameters of the two configuration files.

PMMedExportParam.xml configuration file:

<?xml version="1.0" encoding="iso-8859-1"?><PMExpPara> <GeneralSet> <CounterSortMode Name="Counter display and sort mode." Value="1"/> <Counterseparator Name="Separator for counter name and string value" Value=" "/> <DeleteFileTime Name="Delete file time." Value="1:30"/> <ResultSaveDays Name="Result saving days." Value="7"/> <RANShared Name="RAN shared and result transmit mode" IsShared="0" TransmitMode="2"/> <NastarExport Name="Export NodeB data for Nastar Users." IsSupport="0"/> <GZip Name="Compress file or not." Value="0"/> <FtpPush Name="Inform ftp result automatically" Value="0"/> </GeneralSet> ...........................</PMExpPara>

The description of each parameter is as follows:

l CounterSortMode: Indicates the display and sort modes of the counters in the performancedata export file.




Issue 02 (2008-09-05)

– If this parameter is set to 0, the performance data in the exported file is displayed andsorted by counter name.

– If this parameter is set to 1, the performance data in the exported file is displayed andsorted by counter ID.By default, this parameter is set to 1, which is recommended for use.

l Counterseparator: Indicates the separator, namely, string format, between the counters inthe performance data export file.By default, Value is set to " ", which indicates that a space is used. If a counter name containsa space, you are advised to set the space to ";". If a counter ID contains a space, however,the space can be reserved.

l DeleteFileTime: Indicates the time for deleting the performance data export file. The formatis hour : minute, for example, Value = "1:30".

l ResultSaveDays: Indicates the time for saving the performance data export file, forexample, Value = "7". This value varies with actual situations.

l RANShared: Indicates the setting of functional items related to RAN sharing.– If IsShared is set to 1, it indicates that the RAN sharing function is enabled.

– TransmitMode: Indicates the mode of non-cell data shared between operators.– 0: All the data is written.

– 1: No data is written.

– 2: The data is written for only primary operators.

l NastarExport: Indicates whether the NodeB results need to be exported for use by theNastar.– If IsSupport is set to 0, it indicates that the results are not exported.

– If IsSupport is set to 1, it indicates that the results need to be exported to a file whoseformat is supported by the Nastar.By default, IsSupport is set to 0.

l GZip: Set whether to compress the result file– If the value is 0, do not compress the result file.

– If the value is 1, compress the result file complying with the UNIX standard. Acompression file with the extension .gz is generated.

l FtpPush：Set whether to enable the FTP initial upload– If the value is 0, disable the FTP initial upload.

– If the value is 1, enable the FTP initial upload.

l Other parameters are reserved and not used temporarily.

Not all the counters being measured on the M2000 are not all provided for the northbound.Therefore, the M2000 should provide an independent control view for the NMS and thus theinformation about the northbound exported counters can be set. The following part describeshow to provide such a control view by using the configuration file.

NOTE

The configuration file provides only one view for obtaining the northbound performance data. Anymodification of the view does not affect the measurement setting performed by the M2000 on NEs.Therefore, the exported counters and periods set in the configuration file can be used for obtaining the dataonly when the M2000 performance management system performs relevant measurement on NEs.

PMMedExportView.xml configuration file:




6-3

<ExportSetting FileVersion="1" FormatVersion="1.1" enableMedExp="false"> <NEType id="7" name="SGSN" exportMode="0" supportPeriods="30"> <Mu id="117440512" name="SGSN CDR" exportMode="1" supportPeriods="30"> </Mu> <Mu id="117440550" name="Gb mode L3 MM" exportMode="0" supportPeriods="30"> <Counter id="117454513" name="Gb mode GPRS attach request times" exportMode="1" supportPeriods="30"/> <Counter id="117454514" name="Gb mode GPRS attach accept timest" exportMode="1" supportPeriods="30"/> <Counter id="117454515" name="Gb mode GPRS attach reject times(illegal MS)" exportMode="1" supportPeriods="30"/> <Counter id="117454545" name="Gb mode GPRS attach reject(GPRS not allowed in PLMN)" exportMode="0" supportPeriods="30"/> </Mu> <Mu id="117440551" name="Gb mode attach" exportMode="2" supportPeriods="30"> <Counter id="117454513" name="Gb mode GPRS attach request times" exportMode="1" supportPeriods="30"/> <Counter id="117454514" name="Gb mode GPRS attach accept timest" exportMode="1" supportPeriods="30"/> <Counter id="117454515" name="Gb mode GPRS attach reject times(illegal MS)" exportMode="1" supportPeriods="30"/> <Counter id="117454545" name="Gb mode GPRS attach reject(GPRS not allowed in PLMN)" exportMode="0" supportPeriods="30"/> </Mu> </NEType> <NEType id="8" name="GGSN80" exportMode="0" supportPeriods="30"> </NEType></ExportSetting>

The settings in the PMMedExportView.xml configuration file involve counters and periods.They are set by hierarchy. The hierarchies are respectively NE type, functional subset, andcounter in sequence. The description of the parameters in the configuration file is listed in Table6-1.

Table 6-1 Description of the parameters in the configuration file

Parameter Type Value Description

ExportSetting - - Sets the export of the northboundperformance data.

FileVersion Unsigned int 0-232-1 Identifies the file version. Afterthe exported information ismodified, this parameter valuealso should be changed so that theexport service can determinewhether to load the data again.

FormatVersion string String of anytype

Identifies the file format version.This parameter value should bechanged if the format of theconfiguration file varies.




Issue 02 (2008-09-05)


enableMedExp bool true/false Whether to activate the mediationlayer to export data The exportservice obtains the data from themediation layer, and therefore,the prerequisite for enabling theexport function is to set thisparameter to true.NOTE

If the parameter value is changed,you must restart all the mediationservice to make effective, For details,see example 4.

NEType - - Sets the type of an NE.

id Unsigned int 0-1000NodeB: 3RNC: 4SGSN: 7GGSN: 8BSC6000:76

Identification of the type of aperformance NE

name String String of anytype

Name of an NE type, which isoptional

exportMode int 0, 1, and 2 0: Shields all the relevantcounters.1: Activates all the relevantcounters.2: Only the counters listed in asub-item are exported.

supportPeriods String Comprising 5,15, 30, 60, and1440

The exported measurementperiod, for example, if the 5-minute period and 30-min periodneed to be exported, you can type5 30.

Mu - - Setting of a measurement unit

id Unsigned int 0-232-1 Identification of a measurementunit


Name of a measurement unit




6-5


exportMode int 0, 1, and 2 0: Shields all the relevantcounters.1: Activates all the relevantcounters.2: Only the counters listed in asub-item are exported.


The exported measurementperiod, for example, if the 5-minute period and 30-min periodneed to be exported, you can type5 30. If this parameter is leftempty, use the setting forNEType.

Counter - - Export setting of a counter

id Unsigned int 0-232 -1 Counter identification


Counter name

exportMode int 0-1 0: Data is not exported.1: Data is exported.


The exported measurementperiod, for example, if the 5-minute period and 30-min periodneed to be exported, you can type5 30. If this parameter is leftempty, use the setting for Mu.

The configuration example of the configuration file is as follows:

1. If all the data reported by an NE is to be exported and the period is 15 minutes, you can setthe NE type as follows (taking the SGSN for example):<NEType id="7" name="SGSN" exportMode="1" supportPeriods="15"></NEType>

2. If all the counters of partial functional sub-items under the SGSN are to be exported andthe period is 15 minutes, you can set in the following way:l Change exportMode of NEType to 2, indicating that only the definitely listed functional

sub-items are exported.l Provide the information about the functional sub-items to be exported and set

exportMode to 1.The configuration is as follows:<NEType id="7" name="SGSN" exportMode="2" supportPeriods="15"> <Mu id="117440550" name="Gb mode L3 MM" exportMode="1" supportPeriods="15"> </Mu></NEType>

Other measurement units to be exported can be changed likewise.




Issue 02 (2008-09-05)

3. If only the specified counters are to be exported, you can set in the following way:

l Change exportMode of NEType to 2, indicating that only the definitely listedmeasurement sub-items are exported.

l Change exportMode of Mu to 2, indicating that only the definitely listed counters areexported.

l List the information about the counters to be exported and set exportMode to 1.

The configuration is as follows:<NEType id="7" name="SGSN" exportMode="2" supportPeriods="15"> <Mu id="117440551" name="Gb mode attach" exportMode="2" supportPeriods="15"> <Counter id="117454513" name="Gb mode GPRS attach request times" exportMode="1" supportPeriods="15"/> <Counter id="117454514" name="Gb mode GPRS attach accept timest" exportMode="1" supportPeriods="15"/> <Counter id="117454515" name="Gb mode GPRS attach reject times(illegal MS)" exportMode="1" supportPeriods="15"/> <Counter id="117454545" name="Gb mode GPRS attach reject(GPRS not allowed in PLMN)" exportMode="0" supportPeriods="15"/> </Mu> </NEType>

According to the preceding configuration, If the M2000 obtains the data whose counter IDsare respectively 117454513, 117454514, and 117454515 from the SGSN, the data isexported to the performance result file within the 15-min period. The data whose counterID is 117454545 cannot be exported because the exportMode value is 0.

4. If you need to activate the mediation layer to export data, set the value ofenableMedExpto true. Restart all the Mediation services to validate the setting. Theprocedure is as follows:

(1) Run commands to query the Mediation service. For example, svc_adm -cmd status|grep 'MediationService'.

(2) Restart the queried Mediation services. For example, if you query Mediation Service1and MediationService2, run commands as svc_adm -cmd restartsvcMediationService1 and svc_adm -cmd restartsvc MediationService2

.

6.3 Introduction to NE-Based Performance Data Export FileThis part describes the path, type, and rule for naming the performance export file. In addition,the example of a performance export file is provided.

Path of Performance Data Export File

The default path for saving the performance data export file is /export/home/omc/var/fileint/pmneexport[/index]/neexport_yyyymmdd/neName. The three variables, namely, [/index],yyyymmdd, and neName are described as follows:

l [/index]: index number of an operator

l yyyymmdd: date of saving the performance data

l neName: Generally, indicates the name of an NE. For the NodeB, however, this parameterrefers to the corresponding RNC name. If the RNC is not found, the default directory nameis adopted.




6-7

Type of Performance Data Export FileCurrently, the .xml format of the performance data export file is supported by the M2000.

Rule for Naming Performance Data Export FileThe rule for naming the performance data export file is: <Type><Startdate>.<Starttime>-[<Enddate>.]<Endtime>[_<UniqueId>][_-_<RC>].xml

The meaning of each field is as follows:

1. Type: Indicates whether the measurement results in the performance data export file areobtained from a single NE or multiple NEs.l A refers to a single NE and a single measurement period.

l B refers to multiple NEs and a single measurement period. This scenario is not used atpresent.

NOTEAt present, the performance data export file supports only the measurement performed in a singleperiod.

2. Startdate: Indicates the start date of a performance measurement period. The format isYYYYMMDD, which is explained as follows:l YYYY refers to year, comprised by four digits, such as 2008.

l MM refers to month, comprised by two digits, such as 01–12.

l DD refers to day, comprised by two digits, such as 01–31.

3. Starttime: Indicates the start time of a performance measurement period. The format isHHMMshhmm, which is explained as follows:l HH refers to the hour of the local time, comprised by two digits, such as 00-23 on a 24-

hour basis.l MM refers to the minute of the local time, comprised by two digits. The possible values

are 00, 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55.l s refers to the sign ("+" or "-") marking the difference between the local time and the

UTC time zone. If they are consistent, the sign can either be "+" or "-".l ++hh refers to the differential hour between the local time and the UTC time zone,

comprised by two digits, such as 00-23.l mm refers to the differential minute between the local time and the UTC time zone,

comprised by two digits, such as 00-59.4. Enddate: Indicates the end date of a performance measurement period. This field is not

contained in the name of the performance data export file. For the measurement performedwithin a single period, the value of Enddate is the same as that of Startdate.

5. Endtime: Indicates the end time of a performance measurement period, which is related tothe start time of a performance measurement period. The permitted minute values are 00,05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55.

6. UniqueId: Indicates the name/NodeID/other unique identifier of an NE, an EM, or adomain. For a single NodeB, RNCName.NodeBName can be used. For multiple NodeBs,RNCName.NodeB can be used.

NOTECurrently, multiple NodeBs cannot be written to the same file. The letter B in the suffix of the performancedata export file indicates that the file containing the data exported by multiple NEs.




Issue 02 (2008-09-05)

7. RC: Refers to the running statistical parameter starting from 1. If the file name is not unique,this field is added after the file name. For the measurement performed within a single period,this field is not required.

For example, file name: A20060626.2315+0200-2330+0200_RXTB

The file name indicates that the performance data is measured on an RNC type NE named RXTBon 2006-06-26. In addition, the measurement starts from 23:15 to 23:30, lasting 15 minutes. Thedelay compared with the UTC time zone is two hours.

Example of Performance Data Export FileThe example of a performance data export file is as follows:<?xml version="1.0" encoding="UTF-8"?>

<measCollecFile xmlns="http://latest/nmc-omc/cmNrm.doc#measCollec" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://latest/nmc-omc/cmNrm.doc#measCollec schema\pmResultSchedule.xsd"> <fileHeader fileFormatVersion="32.435 V7.2" vendorName="Huawei"> <fileSender elementType="RNC"/> <measCollec beginTime="2008-01-12T22:05:00+08:00"/> </fileHeader> <measData> <managedElement userLabel="testRNC"/> <measInfo measInfoId="67109391"> <granPeriod duration="PT300S" endTime="2008-01-12T22:10:00+08:00"/> <repPeriod duration="PT300S"/> <measTypes>67190519 67180678 67180677 </measTypes> <measValue measObjLdn="testRNC/Cell:Label=CELL100, CellID=100"> <measResults>31 31 31 </measResults> </measValue> </measInfo> </measData> <fileFooter> <measCollec endTime="2008-01-12T22:10:00+08:00"/> </fileFooter></measCollecFile>

6.4 Operations Related to NE-Based Performance DataExport Tool

This describes how to start and stop the performance data export tool.

6.4.1 Starting NE-Based Performance Data Export ToolThis describes how to start the performance data export tool.

6.4.2 Stopping NE-Based Performance Data Export ToolThis describes how to stop the performance data export tool.

6.4.1 Starting NE-Based Performance Data Export ToolThis describes how to start the performance data export tool.

PrerequisiteYou have logged in to the M2000 server as user root.

ContextThe performance data export tool serves as a service, PMMedExportX (X refers to a digit)provided by the M2000. It starts and stops after the M2000 starts and stops. If required, you can




6-9

manually start the performance data export tool when the M2000 system runs. In the distributedmode, PMMedExportX is distributed with Mediation. That is, each slave device distributed withthe Mediation service possesses a PMMedExportX service, for example, PMMedExport1 orPMMedExport2.

Procedure

Step 1 Switch to the M2000 installation directory. The default installation directory is /opt/OMC.

The default installation directory is /opt/OMC.


# cd /opt/OMC

Step 2 Start the performance data export tool.


# svc_adm -cmd startsvc PMMedExport1

l If the following message is displayed,PMMedExport1 [started ]You can infer that the performance data export tool is started successfully.

l If the following message is displayed,PMMedExport1 [running ]You can infer that the performance data export tool already runs.

----End

6.4.2 Stopping NE-Based Performance Data Export ToolThis describes how to stop the performance data export tool.

PrerequisiteYou have logged in to the M2000 server as user root.

ContextThe performance export tool serves as a service, PMMedExportX, provided by the M2000. Itstarts and stops after the M2000 starts and stops. If required, you can manually stop theperformance data export tool when the M2000 system runs.

Procedure

Step 1 Switch to the M2000 installation directory.

The default installation directory is /opt/OMC.


# cd /opt/OMC

Step 2 Stop the performance data export tool.





Issue 02 (2008-09-05)

# svc_adm -cmd stopsvc PMMedExport1

If the following message is displayed,

PMMedExport1 [stopped ]

You can infer that the performance data export tool is stopped successfully.

----End

6.5 Troubleshooting for NE-Based Performance Data ExportTool

This describes the troubleshooting for the performance data export tool if an export task fails tobe performed.

Operation Log of Performance Data Export ToolThe operation information about the performance export tool is recorded in the

M2000 server installation directory/var/logs/iMAP.pmmedexp[X]_agent.trace file. You canknow the operating status of the tool by viewing this file, and thus perform troubleshooting onexisting faults.

NOTEIn the distribution mode, the relevant operation information is recorded on each master device.

Configuration File Not Effective After Being ModifiedModify the PMMedExportParam.xml file:

1. The PMMedExportX service reads the PMMedExportParam.xml file from the the localserver when being initialized. Therefore, if the PMMedExportX file needs to be modified,you must simultaneously modify the PMMedExportParam.xml file on all the serversrunning the PMMedExportX service.

2. After modifying the configuration file, you must restart the relevant PMMedExportXservice. For details, see 6.4.1 Starting NE-Based Performance Data Export Tool.

Modify the PMMedExportView.xml file:

1. The PMMedExportView.xml file is loaded to the MediationServiceX andPMMedExportX services on the local server. Therefore, if the modification is required totake effect on all the servers, you must simultaneously modify the configuration file on allthe servers.

2. MediationServiceX reads the PMMedExportView.xml file from the local server whenbeing initialized and obtains the enableMedExp field. Therefore, if this field needs to bemodified, you must restart all the MediationServiceX services.

3. The PMMedExportX service checks the PMMedExportView.xml file on the local serverevery five minutes to obtain the FileVersion field. If the field value is modified, the filemust be reloaded. Therefore, if you modify the exported counters and period information,you must simultaneously modify the FileVersion field. The performance data export taskby NE automatically scans and loads the field. If the FileVersion field is not simultaneouslymodified, you need to restart all the PMMedExportX services. For details, see 6.4.1Starting NE-Based Performance Data Export Tool.




6-11

7 Introduction to Export File of InventoryManagement

About This Chapter

This introduces the export file of inventory management.

7.1 Export File of Inventory ManagementThis describes the NE types that the export file of inventory management supports, and also thetypes, save path, naming rule, and format description of the export file.

7.2 Related Operations on Inventory Management ExportingThe related operations on inventory management exporting involves exporting inventorymanagement files, stopping automatically exporting inventory management files, and manuallyexporting inventory management files.

7.3 The Inventory Types of Each NEThis introduces the thirteen supported inventory types of the RNC, NodeB, BSC6000,BSC6000 Site, MSC Server, MGW, SGSN, GGSN80, HLR, PCU, BSC, ICS, and UAG. Thisalso describes each inventory type and its attribute.

M2000Northbound File Interface Developer Guide 7 Introduction to Export File of Inventory Management


7-1

7.1 Export File of Inventory ManagementThis describes the NE types that the export file of inventory management supports, and also thetypes, save path, naming rule, and format description of the export file.

7.1.1 NE Types of Inventory ManagementThis describes the NE types of inventory management.

7.1.2 The Types of Export File of Inventory ManagementThis describes the types of export files of inventory management.

7.1.3 The Default Path of Export File of Inventory ManagementThis describes the default path of the export file of inventory management in the manual orscheduled manner.

7.1.4 The Naming Way of Export File of Inventory ManagementThis describes the naming way of the export file of inventory management.

7.1.5 The Format of Export File of Inventory ManagementThis describes the format of the export file of inventory management.

7.1.1 NE Types of Inventory ManagementThis describes the NE types of inventory management.

Supported NE Types

The NE types that are supported by the export file of inventory management are listed in thefollowing table.

Table 7-1 List of supported NE Types

NE Type Whether Supported

RNC Yes

NodeB DBS3800 Yes

NodeB3802C Yes

NodeB3806 Yes

NodeB3806A Yes

NodeB3812 Yes

NodeB3812A Yes

NodeB3812AE Yes

NodeB3812E Yes

BSC6000 Yes

BSC6000 Site Yes

7 Introduction to Export File of Inventory ManagementM2000



Issue 02 (2008-09-05)

NE Type Whether Supported

MSC Server Yes

MGW Yes

SGSN Yes

GGSN80 Yes

HLR Yes

PCU Yes

BSC(Include BSCBTS) Yes

ICS Yes

UAG Yes

7.1.2 The Types of Export File of Inventory ManagementThis describes the types of export files of inventory management.

The export file of inventory management supports manual export and scheduled export. Theexport file of inventory management can be in .xml, .csv, or .txt format.

7.1.3 The Default Path of Export File of Inventory ManagementThis describes the default path of the export file of inventory management in the manual orscheduled manner.

Default Path of Export File of Inventory Managementl Default path of the export file of inventory management in the manual manner

The inventory management data files that are manually exported are saved in a specifiedclient directory. Meanwhile, the backup data files are saved in the /export/home/omc/var/fileint/cm/InvtManualExport/ directory on the M2000 server.

l Default path of the export file of inventory management in the scheduled mannerThe inventory management data files that are exported at the scheduled time are saved inthe /export/home/omc/var/fileint/cm/InvtTimerExport directory.

7.1.4 The Naming Way of Export File of Inventory ManagementThis describes the naming way of the export file of inventory management.

Naming Way of Export File of Inventory ManagementCurrently, the export file of inventory management supports manual export and scheduledexport. In manual export, you can specify the rules for naming the export file of inventorymanagement on a client. In automatic scheduled export, the rules for naming the export file ofinventory management are as follows:



7-3

l Naming rule

In automatic export, the export file of inventory management is named W_M2000_NEtype_NE fdn_NE name.file format.The NE type refers to the actual type of a current NE, such as the RNC and theBSC6000.

The NE fdn, such as .3221229568.3221233664.3221282816, uniquely identifies an NE inthe M2000 system.

The NE name refers to the NE name that is displayed on a client topology.

The export file of inventory management can be in .xml, .csv, or .txt format.

l Example

For example, if the NE type is BSC6000, NE fdn is .3221229568.3221233664.3221282816,NE name is 211, NE format is in .csv format, then the name of the export file is as follows:

W_M2000_BSC6000_.3221229568.3221233664.3221282816_211.csv.

7.1.5 The Format of Export File of Inventory ManagementThis describes the format of the export file of inventory management.

Format of Export File of Inventory Management

Irrespective of manual export or automatic export, the export file of inventory management canbe in .xml, .csv, or .txt format. This section takes the export file in .xml format as an examplebecause the .csv or txt format does not used in the actual interconnection.

The following part takes the .xml format as an example.

Table 7-2 describes the purposes of flags in the export file of inventory management in .xmlformat.

Table 7-2 Format of the export file of inventory management

Format Description

<DATAPACKET>

Is a permanent flag and not changed.

<NE> Is used to record the basic information about existing NEs and supports threeattributes, that is, NEFdn, NEName, and NEType.

<TABLES> Contains one or more TABLE flags and does not contain any attribute.

<TABLE> Contains the type of and information about the actual inventory, and theattrname attribute that is used to indicate the inventory type.

ROWDATA Contains one or more records of the existing inventory type. The records areseparated by the ROW flag.

ROW Corresponds to an actual record. The attribute of the flag is the attribute nameand value of each record. For the meaning of each attribute name, see 7.3The Inventory Types of Each NE.




Issue 02 (2008-09-05)

The following part takes the export file of inventory management pertaining to the BSC6000 asan example:

<?xml version="1.0" encoding="iso-8859-1"?><DATAPACKET> <NE NEFdn=".3221229568.3221233664.3221282816" NEName="211" NEType="BSC6000NE"/> <TABLES> <TABLE attrname="Rack"> <ROWDATA> <ROW DateOfLastService="" DateOfManufacture="" InventoryUnitId="1" InventoryUnitType="Hardware" ManufacturerData="" RackNo="1" RackType="Local" SerialNumber="" UnitPosition="RackNo = 1" VendorName="Huawei" VendorUnitFamilyType="Rack" VendorUnitTypeNumber="0" VersionNumber=""/> </ROWDATA> </TABLE> <TABLE attrname="Frame"> <ROWDATA> <ROW DateOfLastService="" DateOfManufacture="" FrameNo="1" FrameType="GTCS" InventoryUnitId="1" InventoryUnitType="Hardware" ManufacturerData="" ModuleNo="-1" RackFrameNo="1" RackNo="0" SerialNumber="" UnitPosition="RackNo = 0, FrameNo=1" VendorName="Huawei" VendorUnitFamilyType="Frame" VendorUnitTypeNumber="0" VersionNumber=""/> </ROWDATA> </TABLE> <TABLE attrname="Slot"> <ROWDATA> <ROW DateOfLastService="" DateOfManufacture="" FrameNo="1" InventoryUnitId="14" InventoryUnitType="Hardware" ManufacturerData="" RackNo="0" SerialNumber="" SlotNo="14" SlotPos="1" UnitPosition="RackNo = 0, FrameNo=1,SlotNo=14,SlotPos=1" VendorName="Huawei" VendorUnitFamilyType="Slot" VendorUnitTypeNumber="0" VersionNumber=""/> </ROWDATA> </TABLE> <TABLE attrname="Board"> <ROWDATA> <ROW BiosVer="" BiosVerEx="" BoardName="GXPUM" BoardType="" DateOfLastService="" DateOfManufacture="" FrameNo="3" InventoryUnitId="0" InventoryUnitType="Hardware" Item="" LANVer="" LogicVer="" MBUSVer="" ManufacturerData="" ModuleNo="-1" RackNo="1" SerialNumber="" SlotNo="0" SlotPos="0" SoftVer="" SubSlotNo="-1" UnitPosition="RackNo= 1,FrameNo=3,SlotNo=0, SlotPos=0, SubSlotNo=0" VendorName="" VendorUnitFamilyType="Board" VendorUnitTypeNumber="0" VersionNumber=""/> </ROWDATA> </TABLE> <TABLE attrname="Port"> <ROWDATA> <ROW DateOfLastService="" DateOfManufacture="" FrameNo="0" InventoryUnitId="14" InventoryUnitType="Hardware" ManufacturerData="" RackNo="0" SerialNumber="" SlotNo="14" SlotPos="0" SubSlotNo="-1" UnitPosition="RackNo= 0, FrameNo=0, SlotNo=14, SlotPos=0, SubSlotNo=-1, PortNo=14" VendorName="Huawei" VendorUnitFamilyType="E1Port" VendorUnitTypeNumber="0" VersionNumber=""/>



7-5

</ROWDATA> </TABLE> <TABLE attrname="Antenna"> <ROWDATA/> </TABLE> <TABLE attrname="HostVer"> <ROWDATA> <ROW HostVer="BSC6000V900R003C01B061" HostVerType="HOSTVER" sDesc=""/> </ROWDATA> </TABLE> <TABLE attrname="BTS"> <ROWDATA> <ROW SiteIndex="1" SiteName="22c" SiteType="BTS22C"/> </ROWDATA> </TABLE> </TABLES></DATAPACKET>

7.2 Related Operations on Inventory ManagementExporting

The related operations on inventory management exporting involves exporting inventorymanagement files, stopping automatically exporting inventory management files, and manuallyexporting inventory management files.

7.2.1 Automatically Exporting Inventory Management FilesAfter you enable the function of automatically exporting inventory management files, the systemautomatically exports inventory management files to files in specific format at predefined time.

7.2.2 Stopping Automatically Exporting Inventory Management FilesThis describes how to set the termination of automatically exporting inventory managementfiles.

7.2.3 Manually Exporting Inventory Management FilesBesides automatic export, you can also manually export inventory management files.

7.2.1 Automatically Exporting Inventory Management FilesAfter you enable the function of automatically exporting inventory management files, the systemautomatically exports inventory management files to files in specific format at predefined time.

Prerequisitel You have logged in to the M2000 client.

l You are authorized to perform inventory management.

Procedure


Step 2 Click Inventory Data Export in the navigation tree to view a task record.

Step 3 Double-click the task record to view the Attribute dialog box. Set Common Parameters andExtended Parameters.




Issue 02 (2008-09-05)

Step 4 Click OK to finish the automatic export configuration.

----End

7.2.2 Stopping Automatically Exporting Inventory ManagementFiles

This describes how to set the termination of automatically exporting inventory managementfiles.

Prerequisitel The conditions for the automatic inventory management data export are met.

l You have logged in to the M2000 client.


ContextAfter the export of automatic inventory management files is enabled, you can stop it manuallyat any time.

For details on setting the automatic export of inventory management files, see 7.2.1Automatically Exporting Inventory Management Files.

Procedure


Step 2 Click Inventory Data Export in the navigation tree to view a task record.

Step 3 Right-click a task record and choose Suspend from the shortcut menu to stop the automaticexporting of inventory management files.

----End

7.2.3 Manually Exporting Inventory Management FilesBesides automatic export, you can also manually export inventory management files.

Prerequisitel You have logged in to the M2000 client.


Procedure

Step 1 Select Configuration . The Inventory Management window is displayed.

Step 2 Right-click an NE node or MO node in the navigation tree and choose Export.

Step 3 Set the file name, save path, and save type of the file in the Save dialog box.

Step 4 Click Save to finish the automatic export configuration.



7-7

Step 5 Click OK to close the Message dialog box.

----End

7.3 The Inventory Types of Each NEThis introduces the thirteen supported inventory types of the RNC, NodeB, BSC6000,BSC6000 Site, MSC Server, MGW, SGSN, GGSN80, HLR, PCU, BSC, ICS, and UAG. Thisalso describes each inventory type and its attribute.

7.3.1 RNC Inventory TypesThis describes the RNC inventory types and their attributes.

7.3.2 NodeB Inventory TypesThis describes the NodeB inventory types and their attributes.

7.3.3 BSC6000 Inventory TypesThis describes the BSC6000 inventory types and their attributes.

7.3.4 BSC6000Site Inventory TypesThis describes the BSC6000 site inventory types and their attributes.

7.3.5 MSC Server Inventory TypesThis describes the MSC Server inventory types and their attributes.

7.3.6 MGW Inventory TypesThis describes the MGW inventory types and their attributes.

7.3.7 SGSN Inventory TypesThis describes the SGSN inventory types and their attributes.

7.3.8 GGSN80 Inventory TypesThis describes the GGSN80 inventory types and their attributes.

7.3.9 HLR Inventory TypesThis describes the HLR inventory types and their attributes.

7.3.10 PCU Inventory TypesThis describes the PCU inventory types and their attributes.

7.3.11 BSC Inventory TypesThis describes the BSC inventory types and their attributes.

7.3.12 ICS Inventory TypesThis describes the ICS inventory types and their attributes.

7.3.13 UAG Inventory TypesThis describes the UAG inventory types and their attributes.

7.3.1 RNC Inventory TypesThis describes the RNC inventory types and their attributes.




Issue 02 (2008-09-05)

Rack

Table 7-3 Rack and its attributes

Field Name of the Export File Meaning

DateOfLastService Indicates the last service date.

DateOfManufacture Indicates the production date.

InventoryUnitId Indicates the ID of the inventory unit.

InventoryUnitType Indicates the type of the inventory unit.

ManufacturerData Indicates the manufacturer data.

RackNo Indicates the rack number.

RackType Indicates the rack type.

SerialNumber Indicates the serial number.

UnitPosition Indicates the unit position.

VendorName Indicates the vendor name.

VendorUnitFamilyType Indicates the family type of the vendor unit.

VendorUnitTypeNumber Indicates the type number of the vendor unit.

HardwareVersion Indicates the hardware version number.

Frame

Table 7-4 Frame and its attributes




FrameNo Indicates the frame number.

FrameType Indicates the frame type.




RackFrameNo Indicates the number of the frame in the rack.





7-9







Slot

Table 7-5 Slot and its attributes










SlotNo Indicates the slot number.

SlotPos Indicates the slot position.









Issue 02 (2008-09-05)

Board

Table 7-6 Board and its attributes


BiosVer Indicates the BIOS version.

BiosVerEx Indicates the extended BIOS version.

BoardName Indicates the board name.

BoardType Indicates the board type.






BOMCode Indicates the BOM code.

LANVer Indicates the LAN version.

LogicVer Indicates the logic version.

MBUSVer Indicates the MBU version.


ModuleNo Indicates the module number.




SlotPos Indicates the slot position of the board.

SoftVer Indicates the software version of the board.

SubSlotNo Indicates the subslot number.





IssueNumber Indicates the issue number.




7-11

Port

Table 7-7 Port and its attributes



















HostVer

Table 7-8 HostVer and its attributes


HostVer Indicates the version number.

HostVerType Indicates the version type.

sDesc Indicates the description of the softwareversion.




Issue 02 (2008-09-05)

RNCCell

Table 7-9 RNCCell and its attributes


CellId Indicates the cell ID.

CellName Indicates the cell name.

Lac Indicates the location area code (LAC).

Locell Indicates the local cell ID.


MaxTxPower Indicates the maximum transimit power ofthe cell.

NodeBName Indicates the NodeB name.

PsCrambCode Indicates the primary downlink code.

Rac Indicates the routing area code.

Sac Indicates the service area.

UarfcnUpLink Indicates the uplink frequency.

UarfcnDownLink Indicates the downlink frequency.

UserLabel Indicates the user label.

7.3.2 NodeB Inventory TypesThis describes the NodeB inventory types and their attributes.

Rack












7-13







VersionNumber Indicates the version number.


Frame






















Issue 02 (2008-09-05)

Slot


















Board













7-15





















Port












Issue 02 (2008-09-05)












Antenna

Table 7-15 Antenna and its attributes












VersionNumber Indicates the version number.



7-17

HostVer






NodeBCell

Table 7-17 NodeBCell and its attributes


BbPoolType Indicates the type of a baseband resourcepool.

CabinetNo1 Indicates the cabinet number of poweramplifier 2.

CabinetNo2 Indicates the cabinet number of poweramplifier 2.

DI Indicates the desensitization intensity (dB).

DlFreq Indicates the downlink frequency.

HighSpeedMode Indicates the high speed movement mode.

HoRad Indicates the handover radius of a local cell.

Hsdpa Indicates whether the HSDPA is supported.

Locell Indicates the local cell ID.

MaxPower Indicates the maximum output power (0.1dBm) of a local cell.

Radius Indicates the radius of a local cell.

SecNo Indicates the sector number.

SiteNo Indicates the site number.

SlotNo1 Indicates the slot number of power amplifier1.

SlotNo2 Indicates the slot number of power amplifier2.

SpeedRate Indicates the speed rate (km/h).




Issue 02 (2008-09-05)


SubRackNo1 Indicates the subrack number of poweramplifier 1.

SubRackNo2 Indicates the subrack number of poweramplifier 2.

UlFreq Indicates the uplink frequency.

UlgroupNo Indicates the number of the uplink resourcegroup.

UserLabel Indicates the user label.

7.3.3 BSC6000 Inventory TypesThis describes the BSC6000 inventory types and their attributes.

Rack


















7-19

Frame



















Slot













Issue 02 (2008-09-05)










Board






















7-21












Port





















Issue 02 (2008-09-05)



HostVer






BTS

Table 7-24 BTS and its attributes


SiteIndex Indicates the site index.

SiteName Indicates the site name.

SiteType Indicates the site type.

7.3.4 BSC6000Site Inventory TypesThis describes the BSC6000 site inventory types and their attributes.

Rack










7-23











Frame






















Issue 02 (2008-09-05)



Slot



















Board








7-25






























Issue 02 (2008-09-05)

Port




















HostVer









7-27

7.3.5 MSC Server Inventory TypesThis describes the MSC Server inventory types and their attributes.

Rack
















Frame













Issue 02 (2008-09-05)











Slot




















7-29

Board

































Issue 02 (2008-09-05)

Port



















HostVer






7.3.6 MGW Inventory TypesThis describes the MGW inventory types and their attributes.



7-31

Rack
















Frame
















Issue 02 (2008-09-05)








Slot




















7-33

Board




























IssueNumber Indicates the issue version number.





Issue 02 (2008-09-05)

Port



















HostVer






7.3.7 SGSN Inventory TypesThis describes the SGSN inventory types and their attributes.



7-35

Rack
















Frame
















Issue 02 (2008-09-05)








Slot




















7-37

Board

































Issue 02 (2008-09-05)

Port



















HostVer






7.3.8 GGSN80 Inventory TypesThis describes the GGSN80 inventory types and their attributes.



7-39

Rack
















Frame
















Issue 02 (2008-09-05)








Slot




















7-41

Board

































Issue 02 (2008-09-05)

Port



















HostVer






7.3.9 HLR Inventory TypesThis describes the HLR inventory types and their attributes.



7-43

Rack
















Frame
















Issue 02 (2008-09-05)








Slot




















7-45

Board

































Issue 02 (2008-09-05)

Port



















HostVer






7.3.10 PCU Inventory TypesThis describes the PCU inventory types and their attributes.



7-47

Rack
















Frame
















Issue 02 (2008-09-05)








Slot




















7-49

Board

































Issue 02 (2008-09-05)

Port



















HostVer






7.3.11 BSC Inventory TypesThis describes the BSC inventory types and their attributes.



7-51

BSCModule

Table 7-67 BSCModule and its attributes



ModuleType Indicates the module type.

BSCFrame

Table 7-68 BSCFrame and its attributes




BSCBoard

Table 7-69 BSCBoard and its attributes


BoardNo Indicates the board number.



LogicalNo Indicates the logical number.


BSCBTSEquipment

Table 7-70 BSCBTSEquipment and its attributes


BTSType Indicates the site type.






Issue 02 (2008-09-05)

BSCBTSFrame

Table 7-71 BSCBTSFrame and its attributes





BSCBTSBoard

Table 7-72 BSCBTSBoard and its attributes






BoardNo Indicates the board number.




7.3.12 ICS Inventory TypesThis describes the ICS inventory types and their attributes.

Rack









7-53











Frame






















Issue 02 (2008-09-05)

Slot


















Board













7-55





















Port












Issue 02 (2008-09-05)












HostVer






7.3.13 UAG Inventory TypesThis describes the UAG inventory types and their attributes.

Rack









7-57











Frame






















Issue 02 (2008-09-05)

Slot


















Board













7-59





















Port












Issue 02 (2008-09-05)












HostVer








7-61

Index

Aalarm export

automatic, 2-2file

category and quantity, 2-2format, 2-2naming rule, 2-2path, 2-2

Cconfiguration export file

category and quantity, 3-1deletion, 3-1format, 3-1mode, 3-1naming rule, 3-1path, 3-1

CSV, 2-2

DDST, 5-11, 5-17

EEMS, 1-2

FFDN, 3-1FTP, 1-2, 1-2

Iinterface

Northbound file interface, 1-2Northbound interface, 1-2

MM2000, 1-2MIT, 3-1MO, 3-1

modifyingconfiguration file of the alarm export tool, 2-5configuration file of the performance data exporttool, 5-11

MOI, 3-1

NNMS, 1-2, 1-2

Pparameter

password, 1-2user name, 1-2

performance exportfile

category and quantity, 5-6naming rule, 5-6path, 5-6

operationstart, 5-16stop, 5-16

tool, 5-2configuration file, 5-2operation log, 5-17

Ssetting

automatic alarm export, 2-6termination of automatically exporting alarm file,2-6

TTime Zone, 5-17troubleshooting

no performance result, 5-17

XXML, 2-2, 2-2

M2000Northbound File Interface Developer Guide Index


i-1

Date post:	15-Apr-2016
Category:	Documents
Upload:	aayush1988
View:	136 times
Download:	16 times

Huawei Guide M2000

Documents