Professional Documents
Culture Documents
Huawei Guide m2000 PDF
Huawei Guide m2000 PDF
Huawei Guide m2000 PDF
V200R008C01
Issue 02
Date 2008-09-05
Part Number
Website: http://www.huawei.com
Email: support@huawei.com
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.
Contents
Index.................................................................................................................................................i-1
Figures
Tables
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.
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.
This describes the configuration data export files: their detailed formats, deletion strategy, and
file types.
This describes the file path, categories, quantities, rules for naming files, format description,
deletion strategy, and modification description of configuration export files.
This describes the NE-based performance data export tool and file.
Conventions
1. Symbol Conventions
The following symbols may be found in this document. They are defined as follows
Symbol Description
TIP Indicates a tip that may help you solve a problem or save your
time.
2. General Conventions
Convention Description
Convention Description
3. Command Conventions
Convention Description
4. GUI Conventions
Convention Description
> Multi-level menus are in boldface and separated by the ">" signs.
For example,choose File > Create > Folder .
5. Keyboard Operation
Convention Description
Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the two
keys should be pressed in turn.
6. Mouse Operation
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.
This describes the definition of the Northbound interface, and the definition and parameters of
the Northbound file 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.
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.
This describes the alarm export tool, the formats of alarm export files, alarm export operations,
and troubleshooting.
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 current-
alarm, 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.
l 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>
<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>
Prerequisite
You have logged in to the M2000 server as root.
Procedure
Step 1 Go to the M2000 installation folder.
# cd /opt/OMC
# vi etc/conf/english/fmexportsvc_field.xml
NOTE
Step 3 To make the modified configuration file effective, run the following commands:
# . ./svc_profile.sh
----End
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.
----End
Prerequisite
l The conditions for the automatic alarm export are met.
l You have logged in to the M2000 client.
Context
After the automatic alarm export is enabled, you can stop it manually at any time.
For details on setting the automatic alarm export, see 2.3.2 Setting Automatic Export of Alarm
Files.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
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
This describes the configuration data export files: their detailed formats, deletion strategy, and
file types.
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.
<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.
<className> The name of the MOC that the MOI belongs to.
<attr name="className">MSCServerFunction</attr>
<attr name="fdn">.3221229568.3221233664.3221282816.3221491712</attr>
<attr name="name">MSCServerFunction</attr>
<attr name="neID">0</attr>
<MO className="SRVNODE" fdn=".3221229568.3221233664.3221282816.3221491712.
3221663744">
<attr name="MOIndex">0_LOCAL</attr>
<attr name="SN">LOCAL</attr>
<attr name="SN_IDX">0</attr>
<attr name="className">SRVNODE</attr>
<attr name="fdn">.3221229568.3221233664.3221282816.3221491712.
3221663744</attr>
<attr name="name">Server name=LOCAL</attr>
</MO>
<MO className="MSCServerTimeZone" fdn=".3221229568.3221233664.
3221282816.3221491712.3221352448">
<attr name="MOIndex">.3221229568.3221233664.3221282816</attr>
<attr name="className">MSCServerTimeZone</attr>
<attr name="fdn">.3221229568.3221233664.3221282816.3221491712.
3221352448</attr>
<attr name="name">EMSTZ</attr>
<attr name="neID">0</attr>
</MO>
</MO>
</MO>
</MOTree>
NOTE
In the example, some information is displayed in two lines because of the large quantity of the information.
In actual configuration data files, the information occupies only one line.
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.
This describes the file path, categories, quantities, rules for naming files, format description,
deletion strategy, and modification description of configuration export files.
NOTE
l In the current version, only BSC6000, RNC, and NodeB supports the flat export. For functions
supported by other NEs, see3 Introduction to Configuration Data Export File .
l 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.
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.
<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="className">BSC6000CPU</attr>
<attr name="fdn">.3221229568.3221233664.3221282816.3221512192</attr>
<attr name="name">CPU No.=0, Slot No.=4, Subrack No.=0</attr>
<attr name="neID">0</attr>
</MO>
<MO className="BSC6000Cabinet" fdn=".3221229568.3221233664.3221282816.3221364736">
<attr name="CabinetNo">0</attr>
<attr name="CabinetType">False</attr>
<attr name="MOIndex">0_0</attr>
<attr name="className">BSC6000Cabinet</attr>
<attr name="fdn">.3221229568.3221233664.3221282816.3221364736</attr>
<attr name="name">Cabinet No.=0</attr>
<attr name="neID">0</attr>
</MO>
</MO>
</MOTree>
NOTE
In this example, some portions of the export file are displayed in two rows because the export file has large
contents. In the export file, these portions are actually displayed in one row.
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.
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.
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.
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.
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.
l 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.
– If the value of CounterSortMode is set to 1, the counters in the exported file are
arranged in ascending order based on counter IDs.
– If the value of CounterSortMode is set to 2, the counters in the exported file are
arranged in ascending order based on the character string ASCII codes of counter names.
l CounterValueFormat
This item sets a display mode for counter values in the result file.
– If the value of CounterValueFormat is set to 0, the counter values of the measurement
unit that contains only non-character-string counters are not marked with 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.
l 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.
l 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.
l DisplayDstOffSet
This item sets whether to display the DST offset information.
– 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.
l 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.
l 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.
l 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.
l 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_M2000svr-
CDMA_HLR_150999067_5_200710121535_200710121540.xml.
l 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.
l RANShared
This item sets whether the RAN sharing mode is used. The value is common mode by
default.
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
l The export function is controlled by the administration console and cannot be modified.
l The parameters such as saving days, measurement unit, measurement period, and delay can be
directly set on M2000 client.
l File export path: /export/home/omc/var/fileint/pm/
Export Period
Time Ranges
(minute)
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.
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.
– If a template contains only one function subset and a template name is configured
The name of the file for saving performance results can be pmresult_Function subset
ID_Measurement period_Start time_End time_Template Name.csv or
pmresult_Function subset ID_Measurement period_Start time_End time_Template
Name.xml.
For example, the name of the performance export file
pmresult_67109445_30_200507041030_200507041100_TCPState.csv indicates:
– The time range is from 10:30 to 11:00 on July 4, 2005.
– The ID of the function subset is 67109445.
– The measurement period is 30 minutes.
– 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.
For example, the name of the performance export file
pmresult_30_200507041030_200507041100_10001.csv indicates:
– The time range is from 10:30 to 11:00 on July 4, 2005.
– The measurement period is 30 minutes.
– 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.
For example, the name of the performance export file
pmresult_30_200507041030_200507041100_ TCPState.csv indicates:
– The time range is from 10:30 to 11:00 on July 4, 2005.
– The measurement period is 30 minutes.
– The template name is TCPState.
– 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
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
<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
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.
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.
l If the value of CounterValueFormat is set to 1, all the counter values in the exported result
file are marked with quotation marks.
l If the value of CounterValueFormat is set to 2, none of the counter values in the exported
result file are marked with quotation marks.
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.
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.
This item sets the implementation mode for exporting the recollected results.
l If the value of QueryExportFormat is set to 0, export all the results and re-write the existing
exported files if the recollected data is available.
l If the value of QueryExportFormat is set to 1, export the recollected data to another file.
The file name is different, which is pmresult_measurement unit ID_measurement
period_start time_end time_recover_current system time.csv or pmresult_measurement
This item sets the number of threads for initializing the active thread mode.
This item sets the number of threads used by the timer for triggering the result processing table.
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
l The export function is controlled by the administration console and cannot be modified.
l The parameters such as saving days, measurement unit, measurement period, and delay can be directly
set on M2000 client.
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
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
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:
Parameter Description
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.
Function Subsets 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.
NOTE
For measurement subsets with the same measurement period, you can configure only one export period.
Then the system saves the export task, according to which the export tool exports files at the
scheduled time.
----End
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
Step 1 Go to the M2000 installation folder.
# cd /opt/OMC
# . ./svc_profile.sh
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
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 stop the performance export tool manually during the
operation of the M2000.
Procedure
Step 1 Go to the M2000 installation folder.
The default M2000 installation path is /opt/OMC.
# cd /opt/OMC
The performance export tool is not running if the following prompt is displayed:
svc_adm:error:service is not running
----End
NOTE
If some performance export files are missing while others exist, the M2000 automatically conducts
supplementary collection to obtain the lost data.
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 [running ]
4. Check the log file <M2000 server installation folder>/var/logs/pmexport.trace for errors.
Proceed accordingly based on the error information.
NOTE
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.
l 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.
This describes the NE-based performance data export tool and file.
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.
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.
l CounterSortMode: Indicates the display and sort modes of the counters in the performance
data export 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.
l 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.
l DeleteFileTime: Indicates the time for deleting the performance data export file. The format
is hour : minute, for example, Value = "1:30".
l ResultSaveDays: Indicates the time for saving the performance data export file, for
example, Value = "7". This value varies with actual situations.
l RANShared: Indicates the setting of functional items related to RAN sharing.
– If IsShared is set to 1, it indicates that the RAN sharing function is enabled.
– TransmitMode: Indicates the mode of non-cell data shared between operators.
– 0: All the data is written.
– 1: No data is written.
– 2: The data is written for only primary operators.
l NastarExport: Indicates whether the NodeB results need to be exported for use by 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.
l GZip: Set whether to compress the result file
– If the value is 0, do not compress the result file.
– If the value is 1, compress the result file complying with the UNIX standard. A
compression file with the extension .gz is generated.
l FtpPush:Set whether to enable the FTP initial upload
– If the value is 0, disable the FTP initial upload.
– If the value is 1, enable the FTP initial upload.
l Other parameters are reserved and not used temporarily.
Not all the counters being measured on the M2000 are not all provided for the northbound.
Therefore, the M2000 should provide an independent control view for the NMS and thus 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.
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.
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.
l Provide the information about the functional sub-items to be exported and set
exportMode to 1.
The configuration is as follows:
<NEType id="7" name="SGSN" exportMode="2" supportPeriods="15">
<Mu id="117440550" name="Gb mode L3 MM" exportMode="1" supportPeriods="15">
</Mu>
</NEType>
3. If only the specified counters are to be exported, you can set in the following way:
l Change exportMode of NEType to 2, indicating that only the definitely listed
measurement sub-items are exported.
l Change exportMode of Mu to 2, indicating that only the definitely listed counters are
exported.
l List the information about the counters to be exported and set exportMode to 1.
The configuration is as follows:
<NEType id="7" name="SGSN" exportMode="2" supportPeriods="15">
<Mu id="117440551" name="Gb mode attach" exportMode="2" supportPeriods="15">
<Counter id="117454513" name="Gb mode GPRS attach request times"
exportMode="1" supportPeriods="15"/>
<Counter id="117454514" name="Gb mode GPRS attach accept timest"
exportMode="1" supportPeriods="15"/>
<Counter id="117454515" name="Gb mode GPRS attach reject times(illegal MS)"
exportMode="1" supportPeriods="15"/>
<Counter id="117454545" name="Gb mode GPRS attach reject(GPRS not allowed in PLMN)"
exportMode="0" supportPeriods="15"/>
</Mu>
</NEType>
According to the preceding configuration, If the M2000 obtains the data whose counter 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
.
7. RC: Refers to the running statistical parameter starting from 1. If the file name is not unique,
this field is added after the file name. For the measurement performed within a single period,
this field is not required.
For example, file name: A20060626.2315+0200-2330+0200_RXTB
The file name indicates that the performance data is measured on an RNC type NE named 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.
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
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.
By default, run the following command:
# cd /opt/OMC
You can infer that the performance data export tool is started successfully.
l If the following message is displayed,
PMMedExport1 [running ]
You can infer that the performance data export tool already runs.
----End
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.
By default, run the following command:
# cd /opt/OMC
You can infer that the performance data export tool is stopped successfully.
----End
Supported NE Types
The NE types that are supported by the export file of inventory management are listed in the
following table.
RNC Yes
NodeB3802C Yes
NodeB3806 Yes
NodeB3806A Yes
NodeB3812 Yes
NodeB3812A Yes
NodeB3812AE Yes
NodeB3812E Yes
BSC6000 Yes
MGW Yes
SGSN Yes
GGSN80 Yes
HLR Yes
PCU Yes
ICS Yes
UAG Yes
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.
l 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.
l Example
For example, if the NE type is BSC6000, NE fdn is .3221229568.3221233664.3221282816,
NE name is 211, NE format is in .csv format, then the name of the export file is as follows:
W_M2000_BSC6000_.3221229568.3221233664.3221282816_211.csv.
Table 7-2 describes the purposes of flags in the export file of inventory management in .xml
format.
Format Description
<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.
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"
InventoryUnitType="Hardware" ManufacturerData=""
ModuleNo="-1" RackFrameNo="1" RackNo="0"
SerialNumber="" UnitPosition="RackNo = 0,
FrameNo=1" VendorName="Huawei"
VendorUnitFamilyType="Frame" VendorUnitTypeNumber="0"
VersionNumber=""/>
</ROWDATA>
</TABLE>
<TABLE attrname="Slot">
<ROWDATA>
<ROW DateOfLastService="" DateOfManufacture="" FrameNo="1"
InventoryUnitId="14" InventoryUnitType="Hardware"
ManufacturerData="" RackNo="0" SerialNumber=""
SlotNo="14" SlotPos="1" UnitPosition="RackNo = 0,
FrameNo=1,SlotNo=14,SlotPos=1"
VendorName="Huawei"
VendorUnitFamilyType="Slot"
VendorUnitTypeNumber="0" VersionNumber=""/>
</ROWDATA>
</TABLE>
<TABLE attrname="Board">
<ROWDATA>
<ROW BiosVer="" BiosVerEx="" BoardName="GXPUM"
BoardType="" DateOfLastService=""
DateOfManufacture="" FrameNo="3" InventoryUnitId="0"
InventoryUnitType="Hardware" Item="" LANVer=""
LogicVer="" MBUSVer="" ManufacturerData=""
ModuleNo="-1" RackNo="1" SerialNumber=""
SlotNo="0" SlotPos="0" SoftVer="" SubSlotNo="-1"
UnitPosition="RackNo= 1,FrameNo=3,SlotNo=0,
SlotPos=0, SubSlotNo=0" VendorName=""
VendorUnitFamilyType="Board" VendorUnitTypeNumber="0"
VersionNumber=""/>
</ROWDATA>
</TABLE>
<TABLE attrname="Port">
<ROWDATA>
<ROW DateOfLastService="" DateOfManufacture=""
FrameNo="0" InventoryUnitId="14"
InventoryUnitType="Hardware" ManufacturerData=""
RackNo="0" SerialNumber=""
SlotNo="14" SlotPos="0" SubSlotNo="-1"
UnitPosition="RackNo= 0, FrameNo=0,
SlotNo=14, SlotPos=0, SubSlotNo=-1,
PortNo=14" VendorName="Huawei"
VendorUnitFamilyType="E1Port" VendorUnitTypeNumber="0"
VersionNumber=""/>
</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>
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform inventory management.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
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.
----End
Prerequisite
l The conditions for the automatic inventory management data export are met.
l You have logged in to the M2000 client.
l You are authorized to perform inventory management.
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 1 Choose Maintenance > Task Management. The Task Management window is displayed.
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
Prerequisite
l You have logged in to the M2000 client.
l You are authorized to perform inventory management.
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.
----End
Rack
Frame
Slot
Board
Port
HostVer
RNCCell
Rack
Frame
Slot
Board
Port
Antenna
HostVer
NodeBCell
Rack
Frame
Slot
Board
Port
HostVer
BTS
Rack
Frame
Slot
Board
Port
HostVer
Rack
Frame
Slot
Board
Port
HostVer
Rack
Frame
Slot
Board
Port
HostVer
Rack
Frame
Slot
Board
Port
HostVer
Rack
Frame
Slot
Board
Port
HostVer
Rack
Frame
Slot
Board
Port
HostVer
Rack
Frame
Slot
Board
Port
HostVer
BSCModule
BSCFrame
BSCBoard
BSCBTSEquipment
BSCBTSFrame
BSCBTSBoard
Rack
Frame
Slot
Board
Port
HostVer
Rack
Frame
Slot
Board
Port
HostVer
Index
A modifying
configuration file of the alarm export tool, 2-5
alarm export configuration file of the performance data export
automatic, 2-2 tool, 5-11
file MOI, 3-1
category and quantity, 2-2
format, 2-2 N
naming rule, 2-2
path, 2-2 NMS, 1-2, 1-2
C P
configuration export file parameter
category and quantity, 3-1 password, 1-2
deletion, 3-1 user name, 1-2
format, 3-1 performance export
mode, 3-1 file
naming rule, 3-1 category and quantity, 5-6
path, 3-1 naming rule, 5-6
CSV, 2-2 path, 5-6
operation
D start, 5-16
stop, 5-16
DST, 5-11, 5-17 tool, 5-2
configuration file, 5-2
E operation log, 5-17
EMS, 1-2
S
F setting
automatic alarm export, 2-6
FDN, 3-1 termination of automatically exporting alarm file,
FTP, 1-2, 1-2 2-6
I T
interface Time Zone, 5-17
Northbound file interface, 1-2 troubleshooting
Northbound interface, 1-2 no performance result, 5-17
M X
M2000, 1-2 XML, 2-2, 2-2
MIT, 3-1
MO, 3-1