Huawei Guide M2000

M2000
V200R008C01
Northbound File Interface Developer Guide
Issue
02
Date
2008-09-05
Part Number
Huawei Proprietary and Confidential

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
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 written
consent 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.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

M2000
Contents
Contents
About This Document.....................................................................................................................1
1 Introduction to Northbound File Interface...........................................................................1-1
1.1 Definition of Northbound Interface.................................................................................................................1-2
1.2 Definition of Northbound File Interface.........................................................................................................1-2
1.3 Parameters for Connecting the Northbound File Interface.............................................................................1-2
2 Introduction to Alarm Export Tool and File.........................................................................2-1

2.1 Alarm Export Tool..........................................................................................................................................2-2
2.2 Alarm Export File............................................................................................................................................2-2
2.3 Alarm Export Operations................................................................................................................................2-5
2.3.1 Modifying the Configuration File of the Alarm Export Tool................................................................2-5
2.3.2 Setting Automatic Export of Alarm Files..............................................................................................2-6
2.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-1
5.1 Performance Data Export Tool.......................................................................................................................5-2
5.2 Configuration file of the Performance Data Export Tool................................................................................5-2
5.3 Performance Data Export File.........................................................................................................................5-6
5.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-11
5.4.2 Setting Export Tasks on the M2000 Client..........................................................................................5-14
5.4.3 Starting the Performance Data Export Tool.........................................................................................5-16
5.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-1

6.1 Introduction to NE-Based Performance Data Export Tool.............................................................................6-2
6.2 Introduction to Configuration Files of NE-Based Performance Data Export Tool.........................................6-2
6.3 Introduction to NE-Based Performance Data Export File...............................................................................6-7
6.4 Operations Related to NE-Based Performance Data Export Tool..................................................................6-9
6.4.1 Starting NE-Based Performance Data Export Tool...............................................................................6-9
6.4.2 Stopping NE-Based Performance Data Export Tool............................................................................6-10
Issue 02 (2008-09-05)

Contents
M2000
6.5 Troubleshooting for NE-Based Performance Data Export Tool...................................................................6-11
7 Introduction to Export File of Inventory Management...................................................... 7-1

7.1 Export File of Inventory Management............................................................................................................7-2
7.1.1 NE Types of Inventory Management.....................................................................................................7-2
7.1.2 The Types of Export File of Inventory Management.............................................................................7-3
7.1.3 The Default Path of Export File of Inventory Management..................................................................7-3
7.1.4 The Naming Way of Export File of Inventory Management.................................................................7-3
7.1.5 The Format of Export File of Inventory Management...........................................................................7-4
7.2 Related Operations on Inventory Management Exporting..............................................................................7-6
7.2.1 Automatically Exporting Inventory Management Files.........................................................................7-6
7.2.2 Stopping Automatically Exporting Inventory Management Files.........................................................7-7
7.2.3 Manually Exporting Inventory Management Files................................................................................7-7
7.3 The Inventory Types of Each NE....................................................................................................................7-8
7.3.1 RNC Inventory Types............................................................................................................................7-8
7.3.2 NodeB Inventory Types.......................................................................................................................7-13
7.3.3 BSC6000 Inventory Types...................................................................................................................7-19
7.3.4 BSC6000Site Inventory Types.............................................................................................................7-23
7.3.5 MSC Server Inventory Types...............................................................................................................7-28
7.3.6 MGW Inventory Types........................................................................................................................7-31
7.3.7 SGSN Inventory Types........................................................................................................................7-35
7.3.8 GGSN80 Inventory Types....................................................................................................................7-39
7.3.9 HLR Inventory Types...........................................................................................................................7-43
7.3.10 PCU Inventory Types.........................................................................................................................7-47
7.3.11 BSC Inventory Types.........................................................................................................................7-51
7.3.12 ICS Inventory Types..........................................................................................................................7-53
7.3.13 UAG Inventory Types........................................................................................................................7-57
Index.................................................................................................................................................i-1
ii

Issue 02 (2008-09-05)
M2000
Figures
Figures
Figure 1-1 Location of the Northbound interface.................................................................................................1-2
Figure 2-1 Example of a file in .csv format..........................................................................................................2-4
Issue 02 (2008-09-05)

iii
M2000
Tables
Tables
Table 3-1 File format............................................................................................................................................3-2
Table 4-1 File format of configuration data.........................................................................................................4-2
Table 5-1 Export periods and time ranges............................................................................................................5-6
Table 5-2 Parameters of performance data export tasks.....................................................................................5-15
Table 6-1 Description of the parameters in the configuration file........................................................................6-4
Table 7-1 List of supported NE Types.................................................................................................................7-2
Table 7-2 Format of the export file of inventory management............................................................................7-4
Table 7-3 Rack and its attributes..........................................................................................................................7-9
Table 7-4 Frame and its attributes........................................................................................................................7-9
Table 7-5 Slot and its attributes..........................................................................................................................7-10
Table 7-6 Board and its attributes.......................................................................................................................7-11
Table 7-7 Port and its attributes..........................................................................................................................7-12
Table 7-8 HostVer and its attributes...................................................................................................................7-12
Table 7-9 RNCCell and its attributes.................................................................................................................7-13
Table 7-10 Rack and its attributes......................................................................................................................7-13
Table 7-11 Frame and its attributes....................................................................................................................7-14
Table 7-12 Slot and its attributes........................................................................................................................7-15
Table 7-13 Board and its attributes.....................................................................................................................7-15
Table 7-14 Port and its attributes........................................................................................................................7-16
Table 7-15 Antenna and its attributes.................................................................................................................7-17
Table 7-16 HostVer and its attributes.................................................................................................................7-18
Table 7-17 NodeBCell and its attributes............................................................................................................7-18
Table 7-24 BTS and its attributes.......................................................................................................................7-23
Issue 02 (2008-09-05)

Tables
M2000
Table 7-67 BSCModule and its attributes..........................................................................................................7-52
Table 7-68 BSCFrame and its attributes.............................................................................................................7-52
Table 7-69 BSCBoard and its attributes.............................................................................................................7-52
Table 7-70 BSCBTSEquipment and its attributes..............................................................................................7-52
vi

Issue 02 (2008-09-05)
M2000
Tables
Table 7-71 BSCBTSFrame and its attributes.....................................................................................................7-53

Table 7-72 BSCBTSBoard and its attributes......................................................................................................7-53
Issue 02 (2008-09-05)

vii
M2000
About This Document
About This Document
Purpose
This document provides the information about M2000 Northbound file interface. The document
also provides the operation guide for connecting the NMS.
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
M2000
V200R008C01
Intended Audience
The 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.
Organization
1 Introduction to Northbound File Interface
This describes the definition of the Northbound interface, and the definition and parameters of
the 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.
Issue 02 (2008-09-05)

M2000
About This Document
3 Introduction to Configuration Data Export File

This describes the configuration data export files: their detailed formats, deletion strategy, and
file 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.
Conventions
1. Symbol Conventions
The following symbols may be found in this document. They are defined as follows
Symbol
Description
DANGER
WARNING
CAUTION
Indicates a hazard with a high level of risk that, if not avoided,

will result in death or serious injury.
Indicates a hazard with a medium or low level of risk which, if
not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not avoided,
could cause equipment damage, data loss, and performance
degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save your
time.
TIP
Provides additional information to emphasize or supplement

important points of the main text.
NOTE
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. For

example,log in as user root .
Issue 02 (2008-09-05)
M2000
About This Document
Convention
Description
Italic
Book titles are in italics.
Courier New
Terminal display is in Courier New.
3. Command Conventions
Convention
Description
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 vertical

bars.One is selected.
[ x | y | ... ]
Optional alternative items are grouped in square brackets and

separated by vertical bars.One or none is selected.
{ x | y | ... } *

bars.A minimum of one or a maximum of all can be selected.
[ x | y | ... ] *

bars.A minimum of zero or a maximum of all can be selected.
4. GUI Conventions
Convention
Description
Boldface
Buttons,menus,parameters,tabs,window,and dialog titles are in

boldface. For example,click OK.
>
Multi-level menus are in boldface and separated by the ">" signs.

For example,choose File > Create > Folder .
5. Keyboard Operation
Convention
Description
Key
Press the key.For example,press Enter and press Tab.
Key1+Key2
Press the keys concurrently.For example,pressing Ctrl+Alt+A

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

keys should be pressed in turn.
6. Mouse Operation
Issue 02 (2008-09-05)

M2000
About This Document
Action
Description
Click
Select and release the primary mouse button without moving the
pointer.
Double-click
Press the primary mouse button twice continuously and quickly

without moving the pointer.
Drag
Press and hold the primary mouse button and move the pointer
to a certain position.

Issue 02 (2008-09-05)
M2000
Introduction to Northbound File Interface
About This Chapter

This describes the definition of the Northbound interface, and the definition and parameters of
the Northbound file interface.
1.1 Definition of Northbound Interface
The Northbound interface is an interface between the Element Management System (EMS) and
the Network Management System (NMS).
1.2 Definition of Northbound File Interface
The M2000 exports data from the database to specified files through the Northbound file
interface. Then the NMS extracts information from these files stored on the M2000 server
through the FTP protocol.
1.3 Parameters for Connecting the Northbound File Interface
Through the Northbound file interface, the NMS is connected to the M2000 server through the
FTP protocol.
Issue 02 (2008-09-05)

1-1
M2000
1.1 Definition of Northbound Interface

The Northbound interface is an interface between the Element Management System (EMS) and
the Network Management System (NMS).
On the Northbound interface, the NMS obtains the information about the NEs managed by the
EMS 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 Interface

The M2000 exports data from the database to specified files through the Northbound file
interface. Then the NMS extracts information from these files stored on the M2000 server
through 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.
The performance export tool is running on the M2000 server.
Data export tasks are configured on the M2000 server.
1.3 Parameters for Connecting the Northbound File

Interface
Through the Northbound file interface, the NMS is connected to the M2000 server through the
FTP protocol.
The NMS uses the user name and default password as ftpuser and ftpuser respectively.
1-2

Issue 02 (2008-09-05)
M2000
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 Alarm
Export Tool and File.
For details about the format of configuration files, see 3 Introduction to Configuration Data
Export File.
For details about the export tool and export format of performance files, see 5 Introduction to
Performance Data Export Tool and File.
For details about the export tool and export format of performance files(by NE), see 6
Introduction to NE-Based Performance Data Export Tool and File.
For details about the Export format of Inventory Management File, see 7 Introduction to Export
File of Inventory Management.
Issue 02 (2008-09-05)

1-3
M2000
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 Tool
The alarm export tool exports alarms from the alarm database to the files in the specified directory
on the server. The alarms consist of current fault alarms, historical fault alarms, event alarms,
and shielded alarms.
2.2 Alarm Export File
This describes the path, categories and quantities, rules for naming files, and formats of alarm
export files.
2.3 Alarm Export Operations
Alarm export operations consist of modifying the configuration files of the alarm export tool,
setting the automatic alarm export, and stopping the automatic alarm export.
Issue 02 (2008-09-05)

2-1
M2000
2.1 Alarm Export Tool

The alarm export tool exports alarms from the alarm database to the files in the specified directory
on the server. The alarms consist of current fault alarms, historical fault alarms, event alarms,
and shielded alarms.
Functions of the Alarm Export Tool

The exported alarms still exist in the database.
Configuration File of the Alarm Export Tool

The 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 defines
the name (in the first row), value, and sequence of alarm information fields in the CSV file.

fmexportsvc_field.xml is used for the files in .xml format. This configuration file defines
the name, value, and sequence of alarm information fields in the XML file.
Automatic Alarm Export

After export function is started, the alarm export tool automatically exports the new alarms after
the previous alarms are exported from the alarm database to an alarm export file at a specified
time every day.
2.2 Alarm Export File

This describes the path, categories and quantities, rules for naming files, and formats of alarm
export files.
Path of Alarm Export Files

By 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 automatically
create this directory.
Categories and Quantities of Alarm Export Files

During the alarm export, the current fault alarms, historical fault alarms, event alarms, and
shielded alarms are exported to separate files. Each file records a maximum of 5,000 alarms. If
the alarm number of a type exceeds 5,000, the export tool saves extra alarms to a new export
file.
Rules for Naming Alarm Export Files

l
2-2
Naming Rules
Issue 02 (2008-09-05)
M2000
Alarm export files are named in the following format: Date and Time [DST]-Alarm
category-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 currentalarm, history-alarm, event-alarm, and shielded-alarm, which represent the current fault
alarm, 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 export
more than 5,000 alarms, the alarms other than the first 5,000 alarms are exported to another
file.
The time duration of the alarm export files being maintained before deletion varies
according 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 exported
alarms, the file number is 1.
Extension name indicates the format of a file. The file can be in .xml or .csv format. If you
select compression mode for export, the extension name should be .zip.
l
Examples
The 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 Files

l
CSV
The first row in the CSV file lists the fields recording the alarm information, such as the
NE name, alarm name, and alarm severity. From the second row, each row records an alarm.
fmexportsvc_field.xml is used for files in .csv format. This configuration file defines the
name (in the first row), value, and sequence of alarm information fields in the files in .csv
format. You can modify this configuration file. For details, see 2.3.1 Modifying the
Configuration File of the Alarm Export Tool.
Figure 2-1 is an example of a file in .csv format.
Issue 02 (2008-09-05)

2-3
M2000
Figure 2-1 Example of a file in .csv format
XML
In an XML file, the <Record name="AlarmRecord"></Record> section records
the 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. This
configuration file defines the name, value, and sequence of alarm information fields in the
XML file. You can modify this configuration file. For details, see 2.3.1 Modifying the
Configuration 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>
2-4

Issue 02 (2008-09-05)
M2000
<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 Operations

Alarm 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 Tool
Before you export alarm files, set the number of fields, field sequence, and name description of
alarm information in the alarm export tool configuration file according to the following steps.
2.3.2 Setting Automatic Export of Alarm Files
After you set automatic alarm export, the alarm export tool automatically exports the alarms
generated in the alarm database after the last automatic export to a file in a specified format at
a scheduled time every day.
2.3.3 Setting the Termination of Automatically Exporting Alarm Files
This describes the procedure for setting the termination of automatically exporting alarm files.
2.3.1 Modifying the Configuration File of the Alarm Export Tool

Before you export alarm files, set the number of fields, field sequence, and name description of
alarm information in the alarm export tool configuration file according to the following steps.
Prerequisite
You 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
Issue 02 (2008-09-05)

2-5
M2000
# svc_adm -cmd reload

----End
2.3.2 Setting Automatic Export of Alarm Files

After you set automatic alarm export, the alarm export tool automatically exports the alarms
generated in the alarm database after the last automatic export to a file in a specified format at
a scheduled time every day.
Prerequisite
You 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 Parameters
and Extended Parameters.
Step 4 Click OK. The automatic export configuration is complete.
----End
2.3.3 Setting the Termination of Automatically Exporting Alarm

Files
This describes the procedure for setting the termination of automatically exporting alarm files.
Prerequisite
l
The conditions for the automatic alarm export are met.
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 Alarm
Files.
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 export
of alarm files is stopped.
----End
2-6

Issue 02 (2008-09-05)
M2000
Introduction to Configuration Data Export

File
This describes the configuration data export files: their detailed formats, deletion strategy, and
file 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 directory
specified by users,and it also automatically saves the export data to the/export/home/omc/
var/fileint/cm/manualExport directory.
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_NE
name_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 is
YYYYMMDD.
For manual export, files are named by the user. Two export formats are available, that is,
XML and CSV.
l
Issue 02 (2008-09-05)
Examples
3-1
M2000
If the NE name is test1, the NE IP is 11.11.11.11, and the export time is 2005-06-25, the
file name is CMExport_test1_11.11.11.11_2005062509.xml.
Format of Configuration Export Files

The configuration data files that are exported manually have the same format as the configuration
data files that are exported automatically. Configuration data files can be in the format of xml
or 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 one
pair 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 instance
and function instance. Under the equipment instance are several frame
instances.
<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-2

Issue 02 (2008-09-05)
M2000
<attr name="className">MSCServerFunction</attr>
<attr name="fdn">.3221229568.3221233664.3221282816.3221491712</attr>
<attr name="name">MSCServerFunction</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>
</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 each
two 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 name
maps to an attribute value. In addition, each MOI contains the following two fields: classname
and 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 isLocked
latitude longitude matchVersion medPartition name neID neType neVersion
omcID productID realLatitude realLongitude subnetworkID
100.0.44.122 MSOFTX3000V100R005C10B318 0_1_1 MSCServerNE 110000 3
.3221229568.3221233664.3221282816 FALSE 154 281 iManagerM2000_MSOFTX3000_MATCH_CHS_V200R005C01B0
MSC9880 MSOFTX3000V100R005C10B318 1 2 0DN 0DE 1
CLASSNAME
MOIndex
className
fdn
name
MSCServerFunction
0
MSCServerFunction
.3221229568.3221233664.3221282816.3221491712
neID
MSCServerFunction
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
NOTE
In the example, the configuration data files is displayed in more lines because of the large quantity of the
information. In actual configuration data files, the information occupies only one line.
Issue 02 (2008-09-05)

3-3
M2000
Deletion of Configuration Export File

The system saves only one configuration file for the same NE each day, and only three copies
of the export file of the same NE are reserved. In this case, the first exported configuration file
is deleted in the further export. The same NE mentioned here refers to the NE whose name is
the same with the IP address.
If a third-part file management tool is used, the configuration rules of the third-part file
management tool are applied to manage the configuration files automatically exported.
Automatically Exporting NE Configuration Data

The automatic export function of the M2000 client supports the automatic export of NE
configuration 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 Data

The M2000 enables you to manually export configuration data of physical NEs. You can save
the configuration in relevant path.
3-4
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.

Issue 02 (2008-09-05)
M2000
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
In the current version, only BSC6000, RNC, and NodeB supports the flat export. For functions
supported by other NEs, see3 Introduction to Configuration Data Export File .
The differences between flat export and the original configuration export are as follows: configuring
the saving days of export files, compressing export files, and flattening objects of MO instances in
export files.
Path of Configuration Export Files

l
Path of configuration data that is manually exported

The configuration data files that are manually exported are saved to a client directory
specified by users,and it also automatically saves the export data to the/export/home/omc/
var/fileint/cm/manualExport directory.
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
Naming rule
For automatic export, the files are named in the following format: CMExport_NE
name_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.
Issue 02 (2008-09-05)

4-1
M2000
For manual export, files are named by the user. Three export formats are available, that is,
xml, csv, and txt.
l
Example
If the NE name is test1, the NE IP address is 10.161.85.204, and the Export time is 15:00
at 2008-05-17,
the file name is CMExport_test1_10.161.85.204_2008051715.xml.
Format of Configuration Export Files

The formats of manual export and automatic export of configuration files are the same. The
formats 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 tree
An exported configuration file corresponds to one NE, and thus only one
pair 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 this
model 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="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-2

Issue 02 (2008-09-05)
M2000
<attr name="className">BSC6000CPU</attr>
<attr name="name">CPU No.=0, Slot No.=4, Subrack No.=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="name">Cabinet No.=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 large
contents. 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 no
hierachical relation in the .csv file.
Each MOI contains a row of attribute name and a row of attribute value. The attribute name and
value correspond to each other. Each MOI also contains the classname and fdn fields. The
classname 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
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
neID
NOTE
In this example, some portions of the export file are displayed in multiple rows because the export file has
large 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 one
configuration file for the same NE each day. By default, the system saves the files exported by
the 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 NE
mentioned here refers to the NE whose name is the same with the IP address.
Issue 02 (2008-09-05)

4-3
M2000
Description of Configuration Files

You 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.
NOTE
If 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 of
ExpFileReservedDays to set the saving days of export files.
2.
Modify parameters of SupportGzip.

Set whether to compress the result file.
3.
If you set SupportGzip to false, the system does not compress the result file.
If you set SupportGzip to true, the system compress the result file using the UNIX
standard and generates a compressed file with the extension name of gz.
Restart the CMServer service to validate the parameters.

Switch to the installation directory of the M2000 (/opt/OMC by default) and run the
following command:
# cd /opt/OMC
# svc_adm -cmd restartsvc CMServer
NOTE
The 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 Data

You can configure the automatic export function in the M2000 client.
1.
Choose Maintenance > Task Management. The Task Management window is

displayed.
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 Data

The M2000 enables you to manually export configuration data of physical NEs. You can save
the configuration in relevant path.
1.
4-4
Choose Configuration > MIT Browsing to view the MIT Browsing window.
Issue 02 (2008-09-05)
M2000
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.
Issue 02 (2008-09-05)

4-5
M2000
Introduction to Performance Data Export

Tool and File
About This Chapter

This describes the performance data export tool and file.
5.1 Performance Data Export Tool
The performance export tool automatically exports performance results.
5.2 Configuration file of the Performance Data Export Tool
The 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 export
function. You can modify the configuration file to set the performance export.
5.3 Performance Data Export File
This 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 Tool
Starting the performance export tool and stopping the performance export tool.
5.5 Troubleshooting for the Performance Export Tool
This describes the procedure for performance export file when an performance export task fails.
Issue 02 (2008-09-05)

5-1
M2000
5.1 Performance Data Export Tool

The performance export tool automatically exports performance results.
After the performance export tool starts, it automatically exports specified performance results
to a file when the preset period ends. The exported performance results still exist in the
performance database.
5.2 Configuration file of the Performance Data Export Tool

The 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 export
function. 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
BeginTime
This item sets the start time for exporting results.
EndTime
This item sets the end time for exporting results.
5-2

Issue 02 (2008-09-05)
M2000
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
several times. For example, if you plan to collect the performance data from 2006-01-01 to
2006-01-10, you can collect 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 is exported, you can collect the perform data from 2006-01-05
to 2006-01-10 by setting the BeginTime=2006-01-05 00:05, EndTime=2006-01-10 00:00 in the
configuration file.
l
GeneralSet
GeneralSet contains common configuration items, which can be modified as required.
CounterSortMode
This 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.
arranged in ascending order based on counter IDs.
arranged in ascending order based on the character string ASCII codes of counter names.
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 quotation
marks in the exported result file. The counter values of the measurement unit that
contains character-string counters, however, are marked with quotation marks.
If the value of CounterValueFormat is set to 1, all the counter values in the exported
result file are marked with quotation marks.
If the value of CounterValueFormat is set to 2, none of the counter values in the

exported result file are marked with quotation marks.
QueryTimeMode
This 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 and
the start time in the file is NE time.
If the value of QueryTimeMode is set to 1, the result is queried according to server

time and displayed according to server time. The name of the result file is server time
and the start time in the file is server time.
DisplayTimeZone
This 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.
DisplayDstOffSet
This item sets whether to display the DST offset information.
Issue 02 (2008-09-05)

5-3
M2000
If the value of DisplayDstOffSet is set to 0, the system does not display the DST offset
information.
If the value of DisplayDstOffSet is set to 1, the system displays the DST offset
information.
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.
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
the set time range once the timer is triggered.
For example, if the value of QueryHours is set to 5, the system checks whether there is
the recollected data available within the time range 10:00 to 15:00 when the timer is
triggered at 15:00. If the recollected data is available, the data is exported to the
corresponding file.
QueryExportFormat
This 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_measurement
period_start time_end time_recover_current system time.csv or
pmresult_measurement unit ID_measurement period_start time_end
time_recover_current system time.xml. The existing exported files do not have any
change.
FileExportMode
This 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 a
host_Name of the NE Type_150999067_5_200710121535_200710121540.xml, such
as pmresult_M2000svrCDMA_HLR_150999067_5_200710121535_200710121540.xml.
OMCServerName
This 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. For
example, if the value of OMCServerName is set to MyServer, the name of an exported
file is MyServer_pmresult_function subset_measurement period_start time_end
time.csv.
If the value of OMCServerName is null, the name of the exported file is

pmresult_function subset_measurement period_start time_end time.csv.
RANShared
This item sets whether the RAN sharing mode is used. The value is common mode by
default.
5-4

Issue 02 (2008-09-05)
M2000
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 the
mode to forward non-cell data. TransmitMode = 0 indicates that the data is forwarded
to all operators. 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.
GZip
This 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 UNIX
standard. The extension of the compressed file is gz.
TemplateMode
This 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 not
allowed to modify the parameter because each configuration item is closely related to other
configuration items.
l
PMDBConnNum
This item sets the number of connections allowable for the database.
MethodThreadNum
This item sets the number of threads for initializing the active thread mode.
TableThreadNum
This item sets the number of threads used by the timer for triggering the result processing
table.
BulkReaderNum
This item sets the number of results read in batches at a time when the system queries results
in 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 of
integrated task management.
In the version of M2000V200R005, the following parameters are added to the integrated task
management. These parameters can be set directly on M2000 client.
NOTE
The export function is controlled by the administration console and cannot be modified.
The parameters such as saving days, measurement unit, measurement period, and delay can be
directly set on M2000 client.
File export path: /export/home/omc/var/fileint/pm/
Issue 02 (2008-09-05)

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

client.
l
Saving days: 90
You can modify the saving days. After this parameter is set, the system regularly deletes
the overdue exported result files.
The system deletes the overdue exported result files once each day.
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 must be integer multiples of five. The default delay is used if you do not
set 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 are
exported to the specified files after the preset delay ends. The time range is divided based
on 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
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, the
performance export tool exports the performance results of the time range 0:00-1:00 at
1:30, and of the 1:00-2:00 at 2:30.
5.3 Performance Data Export File

This 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 performance
export tool starts, it creates a folder in the directory automatically on a daily basis. The folders
5-6

Issue 02 (2008-09-05)
M2000
are named in the pmexport_Date of the day format. The files that are generated on the same
day are saved in the same folder.
For example, the pmexport_20060215 folder saves all the performance files exported on
February 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 export
files.
Categories and Quantities of Performance Export Files

When 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.
If templates are configured in performance files, save the result of each template to a file.
Rules for Naming Performance Export Files

l
Exporting files not by template

The name of the file for saving performance results can be pmresult_Function subset
ID_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 file

pmresult_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.
Exporting files by template

A 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

ID_Measurement period_Start time_End time_Template ID.csv or pmresult_Function
subset ID_Measurement period_Start time_End time_Template ID.xml.
pmresult_67109445_30_200507041030_200507041100_10001.csv indicates:
Issue 02 (2008-09-05)
The ID of the function subset is 67109445.
The template ID is 10001.

5-7
M2000
If a template contains only one function subset and a template name is configured
ID_Measurement period_Start time_End time_Template Name.csv or
pmresult_Function subset ID_Measurement period_Start time_End time_Template
Name.xml.
pmresult_67109445_30_200507041030_200507041100_TCPState.csv indicates:
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 configured

The name of the file for saving performance results can be pmresult_Measurement
period_Start time_End time_Template ID.csv or pmresult_Function subset
ID_Measurement period_Start time_End time_Template ID.xml.
pmresult_30_200507041030_200507041100_10001.csv indicates:
The template ID is 10001.
If a template contains multiple function subsets and a template name is configured

The name of the file for saving performance results can be pmresult_Measurement
period_Start time_End time_Template Name.csv or pmresult_Measurement
period_Start time_End time_Template Name.xml.
pmresult_30_200507041030_200507041100_ TCPState.csv indicates:
The template name is TCPState.
Examples of Performance Export Files

l
An example of the performance export file in .csv format

In 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 counter
name.
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 is
shown as follows:
5-8

Issue 02 (2008-09-05)
M2000
Null | Minutes | Null | Null | Unit of Counter 1 | Unit of Counter 2 |

......
From the third row, the information about the performance results is displayed according
to 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,times
2005-12-6 4:30,30,
"softx_test/Office:OFFICEDIR=2/
subRouteNo:SRC=2/Group:TG=22",Reliable,11063,9071,24817,5903,5248
2005-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.

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 is
displayed. 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 according
to 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,,,ti
mes,times,
times,times,times,times,times,times
2006-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 format

In this example, the performance export file is set in .xml format.
which is set to 0 or 2, determines that the exported result file is displayed by the counter
name. 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>
Issue 02 (2008-09-05)

5-9
M2000
<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 of
suspect 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 CounterSortMode
which 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 (the
second level):value of object name (the second level)/identifier of object name (the third
level):value of object name (the third level)/identifier of object name (the fourth
level):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 object
at 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 Tool

Starting the performance export tool and stopping the performance export tool.
5.4.1 Modifying the Configuration File of the Performance Data Export Tool
Modifying parameters of the configuration file of the performance data export tool, such as
BeginTime, EndTime, CounterSortMode, CounterValueFormat, QueryTimeMode,
DisplayTimeZone, and so on.
5.4.2 Setting Export Tasks on the M2000 Client
You can set performance export tasks on the M2000 client.
5.4.3 Starting the Performance Data Export Tool
This describes the procedure for starting the performance data export tool.
5.4.4 Stopping the Performance Data Export Tool
This describes the procedure for stopping the performance data export tool.
5-10

Issue 02 (2008-09-05)
M2000
5.4.1 Modifying the Configuration File of the Performance Data

Export Tool
Modifying parameters of the configuration file of the performance data export tool, such as
BeginTime, EndTime, CounterSortMode, CounterValueFormat, QueryTimeMode,
DisplayTimeZone, and so on.
Context
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.
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 several
times. For example, if you plan to collect the performance data from 2006-01-01 to 2006-01-10, you can
collect 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 is
exported, you can collect the perform data from 2006-01-05 to 2006-01-10 by setting the
BeginTime=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.
in ascending order based on counter IDs.
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
Issue 02 (2008-09-05)
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 the
exported result file. The counter values of the measurement unit that contains character-string
counters, however, are marked with quotation marks.
5-11
M2000
If the value of CounterValueFormat is set to 1, all the counter values in the exported result
file are marked with quotation marks.
If the value of CounterValueFormat is set to 2, none of the counter values in the exported
result 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.
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.
If the value of DisplayTimeZone is set to 0, the system does not display the time zone
information.
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.
If the value of DisplayDstOffSet is set to 0, the system does not display the DST offset
information.
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 the
set time range once the timer is triggered.
For example, if the value of QueryHours is set to 5, the system checks whether there is the
recollected data available within the time range 10:00 to 15:00 when the timer is triggered at
15: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 mutually
dependent. The configuration of this item cannot be modified.
Step 11 Modify QueryExportFormat.
This item sets the implementation mode for exporting the recollected results.
5-12
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_measurement
period_start time_end time_recover_current system time.csv or pmresult_measurement
Issue 02 (2008-09-05)
M2000
unit ID_measurement period_start time_end time_recover_current system time.xml. The

existing 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.
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 the
NE Type_150999067_5_200710121535_200710121540.xml, such as
pmresult_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 server
name_pmresult_function subset_measurement period_start time_end time.csv. For
example, if the value of OMCServerName is set to MyServer, the name of an exported file
is MyServer_pmresult_function subset_measurement period_start time_end time.csv.
If the value of OMCServerName is null, the name of the exported file is pmresult_function
subset_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.
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 mode
to forward non-cell data. TransmitMode = 0 indicates that the data is forwarded to all
operators. 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.
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 the
result file.
If the value of TemplateMode is set to 1, the template ID is contained in the name of the
result file.
Step 17 Modify PMDBConnNum.

This item sets the number of connections allowable for the database
Step 18 Modify MethodThreadNum.
Issue 02 (2008-09-05)

5-13
M2000
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 in
the database result table.
In the version of M2000V200R005, the following parameters are added to the integrated task
management. These parameters can be set directly on M2000 client.
NOTE
The export function is controlled by the administration console and cannot be modified.
The parameters such as saving days, measurement unit, measurement period, and delay can be directly
set on M2000 client.
Step 21 Modify the saving days.

You can modify the saving days. After this parameter is set, the system regularly deletes the
overdue 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 must
be integer multiples of five. The default delay is used if you do not set 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 are exported
to the specified files after the preset delay ends. The time range is divided based on the export
period. Table 5-1 lists the common export periods and time ranges.
----End
5.4.2 Setting Export Tasks on the M2000 Client

You can set performance export tasks on the M2000 client.
Prerequisite
Procedure
Step 2 Choose File Interface > Performance Data Export in the navigation tree to view a
performance data export task.
Step 3 Use either of the following methods to view the Attribute dialog box:
5-14

Issue 02 (2008-09-05)
M2000
Double-click a performance data export task in the task list.
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
.xml
.txt
Hold Days
Sets the hold days of an exported file. For example, if this parameter
is valued 90, you can infer that the file can be saved for 90 days after
the 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
Function Subsets
The following five measure periods are available:

l
5 minutes
15 minutes
30 minutes
60 minutes
24 hours
1. Select the measure period from the Measure Period drop-down

tab.
2. Select the export period from the Export Period drop-down list.
The export period must be equal to or greater than the measure
period.
3. Input the delay period to the Delay Period textbox. The export
tool 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 to

select 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.

Issue 02 (2008-09-05)

5-15
M2000
Then the system saves the export task, according to which the export tool exports files at the
scheduled time.
----End
5.4.3 Starting the Performance Data Export Tool

This describes the procedure for starting the performance data export tool.
Prerequisite
Log in to the M2000 server as root.
Context
The performance export tool is a service, PMExport, provided by the M2000. It starts and stops
after the M2000 starts and stops. You can start the performance export tool manually during the
operation 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 Tool

This describes the procedure for stopping the performance data export tool.
Prerequisite
Context
The performance export tool is a service, PMExport, provided by the M2000. It starts and stops
after the M2000 starts and stops. You can stop the performance export tool manually during the
operation of the M2000.
5-16

Issue 02 (2008-09-05)
M2000
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 Tool

This describes the procedure for performance export file when an performance export task fails.
Operation Log of the Performance Export Tool

All information displayed during the operation of the performance export tool is recorded into
the <M2000 server installation folder>/var/logs/pmexport.trace file. Check the tool operation
status in this file.
NOTE
If some performance export files are missing while others exist, the M2000 automatically conducts
supplementary collection to obtain the lost data.
No Performance Results Are Exported to Files as Expected

The performance export tool starts and has been running for a while, however no performance
results are exported as expected.
To correct the fault, perform the following steps:
1.
2.
Go to the M2000 installation folder.

# cd /opt/OMC
3.
Check that the service PMExport is running.

# svc_adm -cmd status | grep PMExport
The performance export tool is not running if the following prompt is displayed:
Issue 02 (2008-09-05)

5-17
M2000

PMExport
[not running ]
In such a situation, start the performance export tool manually. For details, see 5.4.3
Starting the Performance Data Export Tool.
The performance export tool is running properly if the following prompt is displayed:
PMExport
4.
[running
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 DST
1.
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 located
in 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 the
result file are displayed according to NE time.
In this situation, set QueryTimeMode to 1 and export the result according to the server
time.
3.
Take the NM is in GMT-5 for example. The DST rule of 2006 specifies that you should
set the time one hour earlier from 02:00 on April 2nd to 02:00 on October 29th. That is, set
the 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 of
this 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 October
29th to the time 01:00 DST on October 29th are exported with one hour delay. The
results generated in the period from 01:00 DST on October 29th to 02:00 DST on
October 29th and in the period from 01:00 on October 29th to 02:00 on October 29th
are exported in the same file. The DST identifies the period to which the data belong.
When you set QueryExportFormat to 1 and QueryTimeMode to 0 or 1, the NM is

in DST. The last one or two results generated in the period from 01:00 DST on October
29th to 01:00 on October 29th are exported in an hour delay. The data generated in the
period 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 and
QueryTimeMode to 1. The results are exported based on the server time.
5-18

Issue 02 (2008-09-05)
M2000
6 Introduction to NE-Based Performance Data Export Tool

and File
Introduction to NE-Based Performance Data

Export 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 Tool
The performance data export tool implements the automatic export function by NE. Using this
tool shortens the time for exporting the performance data file, and thus accelerate the
transmission of the file to the upper-layer NMS.
6.2 Introduction to Configuration Files of NE-Based Performance Data Export Tool
This describes the configuration files of the performance data export tool and the meaning of
each parameter in the configuration files.
6.3 Introduction to NE-Based Performance Data Export File
This 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 Tool
This describes how to start and stop the performance data export tool.
6.5 Troubleshooting for NE-Based Performance Data Export Tool
This describes the troubleshooting for the performance data export tool if an export task fails to
be performed.
Issue 02 (2008-09-05)

6-1

and File
M2000
6.1 Introduction to NE-Based Performance Data Export Tool

The performance data export tool implements the automatic export function by NE. Using this
tool shortens the time for exporting the performance data file, and thus accelerate the
transmission of the file to the upper-layer NMS.
After the tool runs, the Mediation Service of the performance mediation layer receives the
performance result file of an NE every time and then forwards the parsed data to the tool. After
handling the data, the tool exports the data to an .xml file by NE. Exporting the handled data
occurs concurrently with archiving the performance results performed by the mediation layer.
NOTE
Exporting data by NE reduces the export delay.
6.2 Introduction to Configuration Files of NE-Based

Performance Data Export Tool
This describes the configuration files of the performance data export tool and the meaning of
each parameter in the configuration files.
The performance data export tool contains two configuration files:
PMMedExportParam.xml and PMMedExportView.xml. The PMMedExportParam.xml
file is used to set the functional items such as the format of the exported performance data and
exported file management. The PMMedExportView.xml file is used to set the data view to be
exported. 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 the
following default directories: /opt/OMC/etc/PMMedExport/PMMedExportParam.xml
and /opt/OMC/etc/PMMedExport/PMMedExportView.xml. The following part describes
the 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
6-2
CounterSortMode: Indicates the display and sort modes of the counters in the performance
data export file.
Issue 02 (2008-09-05)
M2000

and File
If this parameter is set to 0, the performance data in the exported file is displayed and
sorted by counter name.
If this parameter is set to 1, the performance data in the exported file is displayed and
sorted by counter ID.
By default, this parameter is set to 1, which is recommended for use.
Counterseparator: Indicates the separator, namely, string format, between the counters in
the performance data export file.
By default, Value is set to " ", which indicates that a space is used. If a counter name contains
a space, you are advised to set the space to ";". If a counter ID contains a space, however,
the space can be reserved.
DeleteFileTime: Indicates the time for deleting the performance data export file. The format
is hour : minute, for example, Value = "1:30".
ResultSaveDays: Indicates the time for saving the performance data export file, for
example, Value = "7". This value varies with actual situations.
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.
NastarExport: Indicates whether the NodeB results need to be exported for use by the
Nastar.
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 whose
format is supported by the Nastar.
By default, IsSupport is set to 0.
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. A
compression file with the extension .gz is generated.
FtpPushSet 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.
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 the
information about the northbound exported counters can be set. The following part describes
how 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. Any
modification 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 data
only when the M2000 performance management system performs relevant measurement on NEs.
PMMedExportView.xml configuration file:

Issue 02 (2008-09-05)

6-3

and File
M2000
<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"
<Counter id="117454515" name="Gb mode GPRS attach reject times(illegal MS)"
<Counter id="117454545" name="Gb mode GPRS attach reject(GPRS not allowed in PLMN)"
</Mu>
<Mu id="117440551" name="Gb mode attach" exportMode="2" 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, and
counter in sequence. The description of the parameters in the configuration file is listed in Table
6-1.
Table 6-1 Description of the parameters in the configuration file
6-4
Parameter
Type
Value
Description
ExportSetting
Sets the export of the northbound

performance data.
FileVersion
Unsigned int
0-232-1
Identifies the file version. After

the exported information is
modified, this parameter value
also should be changed so that the
export service can determine
whether to load the data again.
FormatVersion
string
String of any
type
Identifies the file format version.

This parameter value should be
changed if the format of the
configuration file varies.

Issue 02 (2008-09-05)
M2000

and File
Parameter
Type
Value
Description
enableMedExp
bool
true/false
Whether to activate the mediation

layer to export data The export
service obtains the data from the
mediation layer, and therefore,
the prerequisite for enabling the
export function is to set this
parameter to true.
NOTE
If the parameter value is changed,
you must restart all the mediation
service to make effective, For details,
see example 4.
NEType
Sets the type of an NE.
id
Unsigned int
0-1000
Identification of the type of a

performance NE
NodeB: 3
RNC: 4
SGSN: 7
GGSN: 8
BSC6000:76
name
String
String of any
type
Name of an NE type, which is

optional
exportMode
int
0, 1, and 2
0: Shields all the relevant

counters.
1: Activates all the relevant
counters.
2: Only the counters listed in a
sub-item are exported.
Issue 02 (2008-09-05)
supportPeriods
String
Comprising 5,
15, 30, 60, and
1440
The exported measurement

period, for example, if the 5minute period and 30-min period
need to be exported, you can type
5 30.
Mu
Setting of a measurement unit
id
Unsigned int
0-232-1
Identification of a measurement
unit
name
String
String of any
type
Name of a measurement unit

6-5

and File
M2000
Parameter
Type
Value
Description
exportMode
int
0, 1, and 2
0: Shields all the relevant

counters.
1: Activates all the relevant
counters.
2: Only the counters listed in a
sub-item are exported.
supportPeriods
String
Comprising 5,
15, 30, 60, and
1440

5 30. If this parameter is left
empty, use the setting for
NEType.
Counter
Export setting of a counter
id
Unsigned int
0-232 -1
Counter identification
name
String
String of any
type
Counter name
exportMode
int
0-1
0: Data is not exported.

1: Data is exported.
supportPeriods
String
Comprising 5,
15, 30, 60, and
1440

5 30. If this parameter is left
empty, 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 set
the 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 and
the 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.
Provide the information about the functional sub-items to be exported and set
exportMode to 1.
The configuration is as follows:

<Mu id="117440550" name="Gb mode L3 MM" exportMode="1" supportPeriods="15">
</Mu>
</NEType>
Other measurement units to be exported can be changed likewise.

6-6

Issue 02 (2008-09-05)
M2000
3.

and File
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 listed

measurement sub-items are exported.
Change exportMode of Mu to 2, indicating that only the definitely listed counters are
exported.
List the information about the counters to be exported and set exportMode to 1.
The configuration is as follows:

<Mu id="117440551" name="Gb mode attach" exportMode="2" supportPeriods="15">
</Mu>
</NEType>
According to the preceding configuration, If the M2000 obtains the data whose counter IDs
are respectively 117454513, 117454514, and 117454515 from the SGSN, the data is
exported to the performance result file within the 15-min period. The data whose counter
ID 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 of
enableMedExpto true. Restart all the Mediation services to validate the setting. The
procedure 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 Service1
and MediationService2, run commands as svc_adm -cmd restartsvc
MediationService1 and svc_adm -cmd restartsvc MediationService2
.
6.3 Introduction to NE-Based Performance Data Export File

This 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
yyyymmdd: date of saving the performance data
neName: Generally, indicates the name of an NE. For the NodeB, however, this parameter
refers to the corresponding RNC name. If the RNC is not found, the default directory name
is adopted.
Issue 02 (2008-09-05)

6-7

and File
M2000
Type of Performance Data Export File

Currently, the .xml format of the performance data export file is supported by the M2000.
Rule for Naming Performance Data Export File

The 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 are
obtained from a single NE or multiple NEs.
l
A refers to a single NE and a single measurement period.
B refers to multiple NEs and a single measurement period. This scenario is not used at
present.
NOTE
At present, the performance data export file supports only the measurement performed in a single
period.
2.
3.
Startdate: Indicates the start date of a performance measurement period. The format is
YYYYMMDD, which is explained as follows:
l
YYYY refers to year, comprised by four digits, such as 2008.
MM refers to month, comprised by two digits, such as 0112.
DD refers to day, comprised by two digits, such as 0131.
Starttime: Indicates the start time of a performance measurement period. The format is
HHMMshhmm, 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 24hour basis.
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.
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 "-".
++hh refers to the differential hour between the local time and the UTC time zone,
comprised by two digits, such as 00-23.
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 performed
within 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 to
the 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 a

domain. For a single NodeB, RNCName.NodeBName can be used. For multiple NodeBs,
RNCName.NodeB can be used.
NOTE
Currently, multiple NodeBs cannot be written to the same file. The letter B in the suffix of the performance
data export file indicates that the file containing the data exported by multiple NEs.
6-8

Issue 02 (2008-09-05)
M2000
7.

and File
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 RXTB
on 2006-06-26. In addition, the measurement starts from 23:15 to 23:30, lasting 15 minutes. The
delay compared with the UTC time zone is two hours.
Example of Performance Data Export File

The 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

<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 Data

Export Tool
This describes how to start and stop the performance data export tool.
6.4.1 Starting NE-Based Performance Data Export Tool
This describes how to start the performance data export tool.
6.4.2 Stopping NE-Based Performance Data Export Tool
This describes how to stop the performance data export tool.
6.4.1 Starting NE-Based Performance Data Export Tool

This describes how to start the performance data export tool.
Prerequisite
You have logged in to the M2000 server as user root.
Context
The 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
Issue 02 (2008-09-05)

6-9

and File
M2000
manually start the performance data export tool when the M2000 system runs. In the distributed
mode, PMMedExportX is distributed with Mediation. That is, each slave device distributed with
the Mediation service possesses a PMMedExportX service, for example, PMMedExport1 or
PMMedExport2.
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

PMMedExport1
[running
You can infer that the performance data export tool already runs.
----End
6.4.2 Stopping NE-Based Performance Data Export Tool

This describes how to stop the performance data export tool.
Prerequisite
You have logged in to the M2000 server as user root.
Context
The performance export tool serves as a service, PMMedExportX, provided by the M2000. It
starts and stops after the M2000 starts and stops. If required, you can manually stop the
performance 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.
6-10

Issue 02 (2008-09-05)
M2000

and File
# svc_adm -cmd stopsvc PMMedExport1

PMMedExport1
[stopped
You can infer that the performance data export tool is stopped successfully.
----End
6.5 Troubleshooting for NE-Based Performance Data Export

Tool
This describes the troubleshooting for the performance data export tool if an export task fails to
be performed.
Operation Log of Performance Data Export Tool

The operation information about the performance export tool is recorded in the
M2000 server installation directory/var/logs/iMAP.pmmedexp[X]_agent.trace file. You can
know the operating status of the tool by viewing this file, and thus perform troubleshooting on
existing faults.
NOTE
In the distribution mode, the relevant operation information is recorded on each master device.
Configuration File Not Effective After Being Modified

Modify the PMMedExportParam.xml file:
1.
The PMMedExportX service reads the PMMedExportParam.xml file from the the local
server when being initialized. Therefore, if the PMMedExportX file needs to be modified,
you must simultaneously modify the PMMedExportParam.xml file on all the servers
running the PMMedExportX service.
2.
After modifying the configuration file, you must restart the relevant PMMedExportX
service. 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 and

PMMedExportX services on the local server. Therefore, if the modification is required to
take effect on all the servers, you must simultaneously modify the configuration file on all
the servers.
2.
MediationServiceX reads the PMMedExportView.xml file from the local server when
being initialized and obtains the enableMedExp field. Therefore, if this field needs to be
modified, you must restart all the MediationServiceX services.
3.
The PMMedExportX service checks the PMMedExportView.xml file on the local server
every five minutes to obtain the FileVersion field. If the field value is modified, the file
must be reloaded. Therefore, if you modify the exported counters and period information,
you must simultaneously modify the FileVersion field. The performance data export task
by NE automatically scans and loads the field. If the FileVersion field is not simultaneously
modified, you need to restart all the PMMedExportX services. For details, see 6.4.1
Starting NE-Based Performance Data Export Tool.
Issue 02 (2008-09-05)

6-11
M2000
Introduction to Export File of Inventory

Management
About This Chapter

This introduces the export file of inventory management.
7.1 Export File of Inventory Management
This describes the NE types that the export file of inventory management supports, and also the
types, save path, naming rule, and format description of the export file.
7.2 Related Operations on Inventory Management Exporting
The related operations on inventory management exporting involves exporting inventory
management files, stopping automatically exporting inventory management files, and manually
exporting inventory management files.
7.3 The Inventory Types of Each NE
This introduces the thirteen supported inventory types of the RNC, NodeB, BSC6000,
BSC6000 Site, MSC Server, MGW, SGSN, GGSN80, HLR, PCU, BSC, ICS, and UAG. This
also describes each inventory type and its attribute.
Issue 02 (2008-09-05)

7-1
M2000
7.1 Export File of Inventory Management

This describes the NE types that the export file of inventory management supports, and also the
types, save path, naming rule, and format description of the export file.
7.1.1 NE Types of Inventory Management
This describes the NE types of inventory management.
7.1.2 The Types of Export File of Inventory Management
This describes the types of export files of inventory management.
7.1.3 The Default Path of Export File of Inventory Management
This describes the default path of the export file of inventory management in the manual or
scheduled manner.
7.1.4 The Naming Way of Export File of Inventory Management
This describes the naming way of the export file of inventory management.
7.1.5 The Format of Export File of Inventory Management
This describes the format of the export file of inventory management.
7.1.1 NE Types of Inventory Management

This 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 the
following table.
Table 7-1 List of supported NE Types
NE Type
Whether Supported
RNC
Yes
NodeB
7-2
DBS3800
Yes
NodeB3802C
Yes
NodeB3806
Yes
NodeB3806A
Yes
NodeB3812
Yes
NodeB3812A
Yes
NodeB3812AE
Yes
NodeB3812E
Yes
BSC6000
Yes
BSC6000 Site
Yes
Issue 02 (2008-09-05)
M2000
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 Management

This describes the types of export files of inventory management.
The export file of inventory management supports manual export and scheduled export. The
export file of inventory management can be in .xml, .csv, or .txt format.
7.1.3 The Default Path of Export File of Inventory Management

This describes the default path of the export file of inventory management in the manual or
scheduled manner.
Default Path of Export File of Inventory Management

l
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 specified
client directory. Meanwhile, the backup data files are saved in the /export/home/omc/var/
fileint/cm/InvtManualExport/ directory on the M2000 server.
Default path of the export file of inventory management in the scheduled manner
The inventory management data files that are exported at the scheduled time are saved in
the /export/home/omc/var/fileint/cm/InvtTimerExport directory.
7.1.4 The Naming Way of Export File of Inventory Management

This describes the naming way of the export file of inventory management.
Naming Way of Export File of Inventory Management

Currently, the export file of inventory management supports manual export and scheduled
export. In manual export, you can specify the rules for naming the export file of inventory
management on a client. In automatic scheduled export, the rules for naming the export file of
inventory management are as follows:
Issue 02 (2008-09-05)

7-3

l
M2000
Naming rule
In automatic export, the export file of inventory management is named W_M2000_NE
type_NE fdn_NE name.file format.
The NE type refers to the actual type of a current NE, such as the RNC and the
BSC6000.
The NE fdn, such as .3221229568.3221233664.3221282816, uniquely identifies an NE in
the 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.
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 Management

This 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 can
be in .xml, .csv, or .txt format. This section takes the export file in .xml format as an example
because 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 .xml
format.
Table 7-2 Format of the export file of inventory management
7-4
Format
Description
<DATAPAC
KET>
Is a permanent flag and not changed.
<NE>
Is used to record the basic information about existing NEs and supports three
attributes, 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 the
attrname attribute that is used to indicate the inventory type.
ROWDATA
Contains one or more records of the existing inventory type. The records are
separated by the ROW flag.
ROW
Corresponds to an actual record. The attribute of the flag is the attribute name
and value of each record. For the meaning of each attribute name, see 7.3
The Inventory Types of Each NE.

Issue 02 (2008-09-05)
M2000
The following part takes the export file of inventory management pertaining to the BSC6000 as
an 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"
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"
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=""/>
Issue 02 (2008-09-05)

7-5
M2000
</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 Management

Exporting
The related operations on inventory management exporting involves exporting inventory
management files, stopping automatically exporting inventory management files, and manually
exporting inventory management files.
7.2.1 Automatically Exporting Inventory Management Files
After you enable the function of automatically exporting inventory management files, the system
automatically exports inventory management files to files in specific format at predefined time.
7.2.2 Stopping Automatically Exporting Inventory Management Files
This describes how to set the termination of automatically exporting inventory management
files.
7.2.3 Manually Exporting Inventory Management Files
Besides automatic export, you can also manually export inventory management files.
7.2.1 Automatically Exporting Inventory Management Files

After you enable the function of automatically exporting inventory management files, the system
automatically exports inventory management files to files in specific format at predefined time.
Prerequisite
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 and
Extended Parameters.
7-6

Issue 02 (2008-09-05)
M2000
Step 4 Click OK to finish the automatic export configuration.

----End
7.2.2 Stopping Automatically Exporting Inventory Management

Files
This describes how to set the termination of automatically exporting inventory management
files.
Prerequisite
l
The conditions for the automatic inventory management data export are met.
Context
After the export of automatic inventory management files is enabled, you can stop it manually
at any time.
For details on setting the automatic export of inventory management files, see 7.2.1
Automatically 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 automatic
exporting of inventory management files.
----End
7.2.3 Manually Exporting Inventory Management Files

Besides automatic export, you can also manually export inventory management files.
Prerequisite
l
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.
Issue 02 (2008-09-05)

7-7
M2000
Step 5 Click OK to close the Message dialog box.

----End
7.3 The Inventory Types of Each NE

This introduces the thirteen supported inventory types of the RNC, NodeB, BSC6000,
BSC6000 Site, MSC Server, MGW, SGSN, GGSN80, HLR, PCU, BSC, ICS, and UAG. This
also describes each inventory type and its attribute.
7.3.1 RNC Inventory Types
This describes the RNC inventory types and their attributes.
7.3.2 NodeB Inventory Types
This describes the NodeB inventory types and their attributes.
7.3.3 BSC6000 Inventory Types
This describes the BSC6000 inventory types and their attributes.
7.3.4 BSC6000Site Inventory Types
This describes the BSC6000 site inventory types and their attributes.
7.3.5 MSC Server Inventory Types
This describes the MSC Server inventory types and their attributes.
7.3.6 MGW Inventory Types
This describes the MGW inventory types and their attributes.
7.3.7 SGSN Inventory Types
This describes the SGSN inventory types and their attributes.
7.3.8 GGSN80 Inventory Types
This describes the GGSN80 inventory types and their attributes.
7.3.9 HLR Inventory Types
This describes the HLR inventory types and their attributes.
7.3.10 PCU Inventory Types
This describes the PCU inventory types and their attributes.
7.3.11 BSC Inventory Types
This describes the BSC inventory types and their attributes.
7.3.12 ICS Inventory Types
This describes the ICS inventory types and their attributes.
7.3.13 UAG Inventory Types
This describes the UAG inventory types and their attributes.
7.3.1 RNC Inventory Types

This describes the RNC inventory types and their attributes.
7-8

Issue 02 (2008-09-05)
M2000
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
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
FrameNo
Indicates the frame number.
FrameType
Indicates the frame type.
InventoryUnitId
InventoryUnitType
ManufacturerData
RackFrameNo
Indicates the number of the frame in the rack.
RackNo
SerialNumber

7-9
M2000
Meaning
UnitPosition
VendorName
HardwareVersion
Slot
Table 7-5 Slot and its attributes
7-10
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
Indicates the slot number.
SlotPos
Indicates the slot position.
UnitPosition
VendorName
HardwareVersion

Issue 02 (2008-09-05)
M2000
Board
Table 7-6 Board and its attributes
Issue 02 (2008-09-05)
Meaning
BiosVer
Indicates the BIOS version.
BiosVerEx
Indicates the extended BIOS version.
BoardName
Indicates the board name.
BoardType
Indicates the board type.
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
Indicates the BOM code.
LANVer
Indicates the LAN version.
LogicVer
Indicates the logic version.
MBUSVer
Indicates the MBU version.
ManufacturerData
ModuleNo
Indicates the module number.
RackNo
SerialNumber
SlotNo
SlotPos
Indicates the slot position of the board.
SoftVer
Indicates the software version of the board.
SubSlotNo
Indicates the subslot number.
UnitPosition
VendorName
IssueNumber
Indicates the issue number.
HardwareVersion

7-11
M2000
Port
Table 7-7 Port and its attributes
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Table 7-8 HostVer and its attributes
7-12
Meaning
HostVer
Indicates the version number.
HostVerType
Indicates the version type.
sDesc
Indicates the description of the software

version.

Issue 02 (2008-09-05)
M2000
RNCCell
Table 7-9 RNCCell and its attributes
Meaning
CellId
Indicates the cell ID.
CellName
Indicates the cell name.
Lac
Indicates the location area code (LAC).
Locell
Indicates the local cell ID.
ManufacturerData
MaxTxPower
Indicates the maximum transimit power of

the 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 Types

This describes the NodeB inventory types and their attributes.
Rack
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType

7-13
M2000
Meaning
SerialNumber
UnitPosition
VendorName
VersionNumber
HardwareVersion
Frame
7-14
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo
SerialNumber
UnitPosition
VendorName
HardwareVersion

Issue 02 (2008-09-05)
M2000
Slot
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion
Board
Issue 02 (2008-09-05)
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId

7-15
M2000
Meaning
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion
Port
7-16
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData

Issue 02 (2008-09-05)
M2000
Meaning
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
Antenna
Table 7-15 Antenna and its attributes
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
SerialNumber
UnitPosition
VendorName
VersionNumber

7-17
M2000
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
NodeBCell
Table 7-17 NodeBCell and its attributes
7-18
Meaning
BbPoolType
Indicates the type of a baseband resource

pool.
CabinetNo1
Indicates the cabinet number of power

amplifier 2.
CabinetNo2
Indicates the cabinet number of power

amplifier 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.1

dBm) 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 amplifier

1.
SlotNo2
Indicates the slot number of power amplifier

2.
SpeedRate
Indicates the speed rate (km/h).

Issue 02 (2008-09-05)
M2000
Meaning
SubRackNo1
Indicates the subrack number of power

amplifier 1.
SubRackNo2
Indicates the subrack number of power

amplifier 2.
UlFreq
Indicates the uplink frequency.
UlgroupNo
Indicates the number of the uplink resource

group.
UserLabel
Indicates the user label.
7.3.3 BSC6000 Inventory Types

This describes the BSC6000 inventory types and their attributes.
Rack
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion

7-19
M2000
Frame
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo
SerialNumber
UnitPosition
VendorName
HardwareVersion
Slot
7-20
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo

Issue 02 (2008-09-05)
M2000
Meaning
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion
Board
Issue 02 (2008-09-05)
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber

7-21
M2000
Meaning
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion
Port
7-22
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName

Issue 02 (2008-09-05)
M2000
Meaning
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
BTS
Table 7-24 BTS and its attributes
Meaning
SiteIndex
Indicates the site index.
SiteName
Indicates the site name.
SiteType
Indicates the site type.
7.3.4 BSC6000Site Inventory Types

This describes the BSC6000 site inventory types and their attributes.
Rack
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData

7-23
M2000
Meaning
RackNo
RackType
SerialNumber
SiteIndex
UnitPosition
VendorName
HardwareVersion
Frame
7-24
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo
SerialNumber
SiteIndex
UnitPosition
VendorName

Issue 02 (2008-09-05)
M2000
Meaning
HardwareVersion
Slot
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SiteIndex
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion
Board
Issue 02 (2008-09-05)
Meaning
BiosVer
BiosVerEx
BoardName

7-25
7-26
M2000
Meaning
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SiteIndex
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion

Issue 02 (2008-09-05)
M2000
Port
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SiteIndex
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Issue 02 (2008-09-05)
Meaning
HostVer
HostVerType
sDesc

version.
SiteIndex

7-27
M2000
7.3.5 MSC Server Inventory Types

This describes the MSC Server inventory types and their attributes.
Rack
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-28
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData

Issue 02 (2008-09-05)
M2000
Meaning
ModuleNo
RackFrameNo
RackNo
SerialNumber
UnitPosition
VendorName
HardwareVersion
Slot
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion

7-29
M2000
Board
7-30
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion

Issue 02 (2008-09-05)
M2000
Port
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
7.3.6 MGW Inventory Types

This describes the MGW inventory types and their attributes.
Issue 02 (2008-09-05)

7-31
M2000
Rack
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-32
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo

Issue 02 (2008-09-05)
M2000
Meaning
SerialNumber
UnitPosition
VendorName
HardwareVersion
Slot
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion

7-33
M2000
Board
7-34
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
Indicates the issue version number.
HardwareVersion

Issue 02 (2008-09-05)
M2000
Port
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
7.3.7 SGSN Inventory Types

This describes the SGSN inventory types and their attributes.
Issue 02 (2008-09-05)

7-35
M2000
Rack
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-36
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo

Issue 02 (2008-09-05)
M2000
Meaning
SerialNumber
UnitPosition
VendorName
HardwareVersion
Slot
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion

7-37
M2000
Board
7-38
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion

Issue 02 (2008-09-05)
M2000
Port
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
7.3.8 GGSN80 Inventory Types

This describes the GGSN80 inventory types and their attributes.
Issue 02 (2008-09-05)

7-39
M2000
Rack
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-40
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo

Issue 02 (2008-09-05)
M2000
Meaning
SerialNumber
UnitPosition
VendorName
HardwareVersion
Slot
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion

7-41
M2000
Board
7-42
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion

Issue 02 (2008-09-05)
M2000
Port
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
7.3.9 HLR Inventory Types

This describes the HLR inventory types and their attributes.
Issue 02 (2008-09-05)

7-43
M2000
Rack
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-44
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo

Issue 02 (2008-09-05)
M2000
Meaning
SerialNumber
UnitPosition
VendorName
HardwareVersion
Slot
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion

7-45
M2000
Board
7-46
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion

Issue 02 (2008-09-05)
M2000
Port
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
7.3.10 PCU Inventory Types

This describes the PCU inventory types and their attributes.
Issue 02 (2008-09-05)

7-47
M2000
Rack
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-48
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo

Issue 02 (2008-09-05)
M2000
Meaning
SerialNumber
UnitPosition
VendorName
HardwareVersion
Slot
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion

7-49
M2000
Board
7-50
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion

Issue 02 (2008-09-05)
M2000
Port
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
7.3.11 BSC Inventory Types

This describes the BSC inventory types and their attributes.
Issue 02 (2008-09-05)

7-51
M2000
BSCModule
Table 7-67 BSCModule and its attributes
Meaning
ModuleNo
ModuleType
Indicates the module type.
BSCFrame
Table 7-68 BSCFrame and its attributes
Meaning
FrameNo
ModuleNo
BSCBoard
Table 7-69 BSCBoard and its attributes
Meaning
BoardNo
Indicates the board number.
BoardType
FrameNo
LogicalNo
Indicates the logical number.
ModuleNo
BSCBTSEquipment
Table 7-70 BSCBTSEquipment and its attributes
7-52
Meaning
BTSType
Indicates the site type.
ModuleNo
SiteNo

Issue 02 (2008-09-05)
M2000
BSCBTSFrame
Table 7-71 BSCBTSFrame and its attributes
Meaning
FrameNo
ModuleNo
SiteNo
BSCBTSBoard
Table 7-72 BSCBTSBoard and its attributes
Meaning
FrameNo
ModuleNo
SiteNo
SlotNo
BoardNo
Indicates the board number.
BoardType
SerialNumber
SoftVer
7.3.12 ICS Inventory Types

This describes the ICS inventory types and their attributes.
Rack
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType

7-53
M2000
Meaning
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-54
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo
SerialNumber
UnitPosition
VendorName
HardwareVersion

Issue 02 (2008-09-05)
M2000
Slot
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion
Board
Issue 02 (2008-09-05)
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId

7-55
M2000
Meaning
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion
Port
7-56
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData

Issue 02 (2008-09-05)
M2000
Meaning
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Meaning
HostVer
HostVerType
sDesc

version.
7.3.13 UAG Inventory Types

This describes the UAG inventory types and their attributes.
Rack
Issue 02 (2008-09-05)
Meaning
DateOfLastService
DateOfManufacture
InventoryUnitId
InventoryUnitType

7-57
M2000
Meaning
ManufacturerData
RackNo
RackType
SerialNumber
UnitPosition
VendorName
HardwareVersion
Frame
7-58
Meaning
DateOfLastService
DateOfManufacture
FrameNo
FrameType
InventoryUnitId
InventoryUnitType
ManufacturerData
ModuleNo
RackFrameNo
RackNo
SerialNumber
UnitPosition
VendorName
HardwareVersion

Issue 02 (2008-09-05)
M2000
Slot
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData
RackNo
SerialNumber
SlotNo
SlotPos
UnitPosition
VendorName
HardwareVersion
Board
Issue 02 (2008-09-05)
Meaning
BiosVer
BiosVerEx
BoardName
BoardType
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId

7-59
M2000
Meaning
InventoryUnitType
BOMCode
LANVer
LogicVer
MBUSVer
ManufacturerData
ModuleNo
RackNo
SerialNumber
SlotNo
SlotPos
SoftVer
SubSlotNo
UnitPosition
VendorName
IssueNumber
HardwareVersion
Port
7-60
Meaning
DateOfLastService
DateOfManufacture
FrameNo
InventoryUnitId
InventoryUnitType
ManufacturerData

Issue 02 (2008-09-05)
M2000
Meaning
RackNo
SerialNumber
SlotNo
SlotPos
SubSlotNo
UnitPosition
VendorName
HardwareVersion
HostVer
Issue 02 (2008-09-05)
Meaning
HostVer
HostVerType
sDesc

version.

7-61
M2000
Index
Index
A
alarm export
automatic, 2-2
file
category and quantity, 2-2
format, 2-2
naming rule, 2-2
path, 2-2
modifying
configuration file of the alarm export tool, 2-5
configuration file of the performance data export
tool, 5-11
MOI, 3-1
N
NMS, 1-2, 1-2
configuration export file

deletion, 3-1
format, 3-1
mode, 3-1
naming rule, 3-1
path, 3-1
CSV, 2-2
parameter
password, 1-2
user name, 1-2
performance export
file
naming rule, 5-6
path, 5-6
operation
start, 5-16
stop, 5-16
tool, 5-2
configuration file, 5-2
operation log, 5-17
D
DST, 5-11, 5-17
E
EMS, 1-2
F
FDN, 3-1
FTP, 1-2, 1-2
setting
automatic alarm export, 2-6
termination of automatically exporting alarm file,
2-6
interface
Northbound file interface, 1-2
Northbound interface, 1-2
Time Zone, 5-17

troubleshooting
no performance result, 5-17
M2000, 1-2
MIT, 3-1
MO, 3-1
XML, 2-2, 2-2
Issue 02 (2008-09-05)

i-1

Huawei Guide M2000

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Huawei Guide M2000

Загружено:

Авторское право:

Доступные форматы

M2000

Northbound File Interface Developer Guide

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Copyright Huawei Technologies Co., Ltd. 2008. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

2 Introduction to Alarm Export Tool and File.........................................................................2-1

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

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

Huawei Proprietary and Confidential

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

7 Introduction to Export File of Inventory Management...................................................... 7-1

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Table 7-71 BSCBTSFrame and its attributes.....................................................................................................7-53

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

3 Introduction to Configuration Data Export File

Indicates a hazard with a high level of risk that, if not avoided,

Provides additional information to emphasize or supplement

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files,directories,folders,and users are in boldface. For

About This Document

Book titles are in italics.

Terminal display is in Courier New.

The keywords of a command line are in boldface.

Command arguments are in italic.

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

Alternative items are grouped in braces and separated by vertical

Optional alternative items are grouped in square brackets and

Alternative items are grouped in braces and separated by vertical

Alternative items are grouped in braces and separated by vertical

Buttons,menus,parameters,tabs,window,and dialog titles are in

Multi-level menus are in boldface and separated by the ">" signs.

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

Press the keys concurrently.For example,pressing Ctrl+Alt+A

Press the keys in turn.For example,pressing Alt,A means the two

Huawei Proprietary and Confidential

About This Document

Press the primary mouse button twice continuously and quickly

Huawei Proprietary and Confidential

1 Introduction to Northbound File Interface

Introduction to Northbound File Interface

About This Chapter

Huawei Proprietary and Confidential

1 Introduction to Northbound File Interface

1.1 Definition of Northbound Interface

1.2 Definition of Northbound File Interface

The alarm export tool is running on the M2000 server.

The performance export tool is running on the M2000 server.

Data export tasks are configured on the M2000 server.

1.3 Parameters for Connecting the Northbound File

Huawei Proprietary and Confidential

1 Introduction to Northbound File Interface

Huawei Proprietary and Confidential

2 Introduction to Alarm Export Tool and File