SolutionPack for Huawei iManager M2000 Summary Sheet – Service Assurance Suite 9.4

Table of Contents


Learn how to install and configure the SolutionPack for Huawei iManager M2000. This SolutionPack monitors the performance of the mobile network managed by Huawei iManager M2000.

Back to Top

Technical specifications

SolutionPack version


Compatible EMC M&R versions

6.5u1 and later

Data collection method

Stream collector

Main reports

Topology Map:
Topology Map for 3G By Cell
Topology Map for 3G By Station
Accessibility Success Rate
SDCCH Congestion by Cell
Call Drop Rate by Cell
Handover Success Rate
Traffic Integrity:
2G Data Avg Throughput Downlink
2G Data Avg Throughput Uplink
3G Data Avg Throughput Downlink
3G Data Avg Throughput Uplink
2G Cell Downtime
3G Cell Downtime
2G Site Utilization
3G Site Utilization
CE Utilization
Simultaneous Data Users
Situations to Watch:
Call Drop Rate
Cell Down Time
Handover Success Rate
SDDCH Congestion

Back to Top

Where to find the latest SolutionPack software

Install the latest core software update for your product suite. SolutionPacks distributed with core software have a 30-day free evaluation period. If you plan to use the software longer than 30 days, you must install a SolutionPack license before the trial period ends.

This 30-day free evaluation only applies to new installations and is not available for upgraded installations. If you upgrade the core software and want to try a new SolutionPack, you must request a license for that SolutionPack by completing a Support Request (SR) form, which is available on the EMC Online Support website at

Back to Top

Performing prerequisite installation tasks

This SolutionPack requires that the performance management (PM) data from Huawei iManager M2000 be locally available on the EMC M&R server hosting the Stream collector. You must ensure Huawei iManager M2000 can push the PM data files to the EMC M&R server.

This procedure includes a task for sending the PM files from Huawei iManager M2000 to the EMC M&R server. Contact the Huawei iManager M2000 administrator about where the PM files are stored and how they are processed.


  1. Verify the SFTP or FTP server is running on the EMC M&R server where the Stream collector resides.
  2. Verify that connectivity exists between the EMC M&R server and Huawei iManager M2000.
  3. Configure Huawei iManager M2000 to push the raw PM data files on a regular time interval to this default directory on the EMC M&R server: <install directory>/Collecting/Stream-Collector/<collector instance name>/data/
    Here is an example of a raw PM file name: pmresult_67109379_*.csv.
    You can override the default directory during the SolutionPack installation.
  4. Verify that the required counters are enabled on Huawei iManager M2000 EMS (Element Management System). These counters are listed in the SolutionPack for Huawei iManager M2000 Counter Prerequisites.
Back to Top

Determining the format of the performance data

The Huawei iManager M2000 formats the data in the performance management files based on the counter ID (numerical representation), the counter name or the counter description. For the Stream collector to correctly parse the metrics in these files, you must indicate the format of these PM files during the SolutionPack installation.

The Huawei iManager M2000 creates one performance management CSV file for each counter group ID. This table shows the performance properties for Counter Group ID:-67109381.


  1. Using a text editor, open one of the performance management CSV files.
  2. In the column header after Reliability, check for these formats. The italicized text shows the actual format example.
    Format Example
    Counter ID Result Time,Granularity Period,Object Name,Reliability,"67202488"
    Counter name Result Time,Granularity Period,Object Name,Reliability,"VS.HSUPA.16QAM.UtilizeTimePermillage"
    Counter description Result Time,Granularity Period,Object Name,Reliability,"AR3010A:Mean Number of Dynamically Configured Channels(SDCCH)(900/850/810 band)"
    You are asked for this format when you install the SolutionPack.
Back to Top

Installing a SolutionPack

After you log in as an administrator, you can install a SolutionPack from Centralized Management.

Before you begin

  • Determine whether you need a SolutionPack license file by checking the feature names and expiration dates listed in Centralized Management > License Management. If not listed, obtain a license by completing a Support Request (SR) form, which is available on the EMC Online Support website at

  • Make sure the core modules, such as the Module-Manager, are up-to-date on all servers since not all module dependencies are validated during the SolutionPack installation. See the EMC M&R (Watch4net) Installation and Configuration Guide for more information.


  1. Log in to the EMC M&R platform with your user name and password.
  2. Select Administration.
  3. Select Centralized Management.
  5. Select the SolutionPack in the Browse and Install SolutionPacks screen.
  6. Read the summary information and click Install.
  7. Select the components to install.
    1. Type the instance name.
    2. Select the server in one or more list boxes. For example, select the server in the Data collection and Reports list boxes.
    3. Click Next.
  8. Complete the wizards screens and click Install on the last screen.
    The installation process begins.
  9. Select the maximize arrow next to each component to view the installation process.
    When the installation successfully completes, green checkmarks appear.
  10. Select Centralized Management > SolutionPack to verify the installed SolutionPack.
Back to Top

Performing post installation tasks

After installing the SolutionPack, you must perform certain tasks.


  1. If you selected Move as the Post processing action during the installation, which keeps all processed performance management XML files, make sure you have a maintenance task running on the server that periodically deletes these files. You can do this manually or by scheduling Cron jobs.
  2. If using the default directory to store the performance management XML files, verify that the apg user has read/write permissions on it.
  3. If not using the default directory, make sure the directory that you are using to store the performance management XML files is on a valid partition and that the apg user has read/write permissions on it. If using another user, make sure that user is in the same UNIX permissions group as the apg user.
Back to Top

Setting up sectorized cell views on geo maps

You can provide views of the individual cells, which are the sectors of a cellsite, on the geo maps in this SolutionPack. To do this, you customize a default property tagging filter and edit an existing sample CSV file according to your specifications. The information you enter into this filter processes the properties that you specify in the CSV file to enrich the views on the geo maps.


  1. Navigate to Centralized Management.
  2. Under Logical Overview, click Collecting.
  3. Select the Property-Tagging-Filter for the Huawei iManager M2000 instance. For example: Property-Tagging-Filter::huawei-m2000 <server>
    You can also modify the property tagging filter using the Data Enrichment functionality in Centralized Management. For more information, see the online help in the EMC M&R platform.
  4. Click Configuration Files in the blue bar.
  5. Select conf/property-tagging-filter_m2000.xml.
  6. Click Edit to add these required key properties and provide processing instructions for the CSV file:
    • device
    • siteid
    • sitename
    • sitetype: indoor or outdoor
    • celltype: 2G, 3G, or 4G
    • location: latitude and longitude of the site location
    • azimuth: orientation of the cell/sector
    • radius: approximate radius of coverage
    • beamwidt: beam width view of the cell/sector
    For instructions on customizing this property tagging filter, click doc/APG-Property-Tagging-Filter.pdf under Documentation.
  7. Under Configuration Files, do one of the following:
    • To add locations based on the cell ID, edit the sample file M2000-cellid-map.csv to meet your requirements, and then click Save.
    • To add locations based on the device, edit the sample file M2000-device-map.csv to meet your requirements, and then click Save.
    The following shows sample entries for this type of CSV file:
    31071,EN107,Enma Mall,Indoor,3G,24.1298 56.5743,90,25000,120
    31074,EN107,Enma Mall,Indoor,3G,33.1298 40.5743,210,25500,120
    31072,EN107,Enma Mall,Indoor,3G,26.1298 50.5743,330,25500,120
    After the next polling cycle, you will see sectorized cell views on the geo maps.
Back to Top

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:


  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.


It may take up to an hour to display all relevant information in these reports.

Back to Top


This SolutionPack generates alerts when specific thresholds are reached in the mobile network. These alerts cover the areas of accessibility, retainability, mobility, and utilization.

Accessibility alerts

Retainability alerts

Mobility alerts

Utilization alerts

Back to Top

Adding new metrics in the collector

The SolutionPack supports some metrics that are not part of the installation. This sample procedure shows you the steps to follow when adding these new metrics to the Stream collector.

This sample procedure adds new metrics to the counter names VS.AttCellUpdt.RLFail, VS.FailCellUpdt.RLFail.NoReply and VS.SuccCellUpdt.RLFail, which are in counter group ID 67109382 . These metrics are listed in the SolutionPack for Huawei iManager M2000 Counter Prerequisites spreadsheet.


  1. Back up the original collector and parser files. For example: huawei-collecting-name.xml to huawei-collecting-name.xml.bak and huawei-parsing.xml to huawei-parsing.xml.bak.
  2. Search for the counter name VSAttCellUpdtRLFail (without '.' ) in huawei-collecting-name.xml.
  3. If found in huawei-collecting-name.xml, uncomment the following lines:
    <values required="false"context-key=VS.AttCellUpdt.RLFail;">
  4. If not found in huawei-collecting-name.xml, do the following:
    1. Check the contents of the counter group ID 67109382. For example: cat pmresult_67109382_30_201302201600_201302201630.csv
      Result Time,Granularity Period,Object Name,Reliability,"VS.AttCellUpdt.RLFail","VS.FailCellUpdt.RLFail.NoReply","VS.SuccCellUpdt.RLFail"
      2013-02-20 16:00,30,"RNC/BSC6900UCell:Label=PO230A1, CellID=32301",Reliable,0,0,0
      2013-02-20 16:00,30,"RNC/BSC6900UCell:Label=PO430B2, CellID=32305",Reliable,0,0,0
      2013-02-20 16:00,30,"RNC/BSC6900UCell:Label=PO430B1, CellID=32302",Reliable,0,0,0
      2013-02-20 16:00,30,"RNC/BSC6900UCell:Label=PO230A2, CellID=32304",Reliable,0,0,0
    2. Match one of the above object name patterns with an object name in this table. The Stream collector extracts required performance management data from the object name. The object type is the logical grouping of the counter group IDs.
    3. Since the object name pattern RNC/BSC6900UCell:Label=PO230A1 matches one that is of obj1 type, search for <hardcoded-properties key="hwobjid">obj1</hardcoded-properties>
    4. Add these values to the metrics:
      <values required="false" context-key=VS.AttCellUpdt.RLFail >
      <name> VSAttCellUpdtRLFail </name>
      <values required="false" context-key=VS.FailCellUpdt.RLFail.NoReply >
      <values required="false" context-key=VS.SuccCellUpdt.RLFail >
    5. Save huawei-collecting-name.xml.
      In this example, the performance data is formatted by the counter name. If data is formatted by the counter ID or the counter description, you must add the metric information to huawei-collecting-id.xml or huawei-collecting-desc.xml, respectively, instead of huawei-collecting-name.xml.
  5. Append this directory file-pattern to the huawei-parsing.xml file:
    <directory file-pattern="pmresult_67109379_*.csv|pmresult_67109377_*.csv|pmresult_ 67109382 *.csv" recursive="true">data/</directory>
  6. Save huawei-parsing.xml.
  7. Restart the Stream collector.
Back to Top


Report display problems

Back to Top

What to do if data does not appear in any topology reports


  1. After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. Check these feeds to the topology reports:
    • http://<EMC M&R-Instance>:58083/topology/repository/
    • http://<EMC M&R-Instance>:58083/topology/report/map?device=<STATION_NAME>&devtype=Station&mapType=STATION_MAP
    • http://<EMC M&R-Instance>:58083/topology/resources/mobilepaths/topo:MobileStation:<STATION_NAME>
  4. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Running a scheduled task to import data into reports

After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.


  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some topology reports


  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. In the database, search for these metrics that are used to stretch the topology from controller to station to cell:
    • RRCAttConnEstabReg for cell-specific metric (device ->siteid) inverse connection to station

    • VSIUBDLCongTime for station-specific metric (device ->cntlr) inverse connection to controller

    • VSRRCAttConnEstabRNC for controller-specific metric
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Searching for metrics in the database

You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.


  1. Go to the Administration page.
  2. Under Modules, click Management of Database Modules.
  3. On the Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
    For example, to list up to 100 results of the SignalWait Time metric with the properties of device and IP, type name=='SignalWaitTime' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

Viewing collector errors in the Collector-Manager log files

Review the Collector-Manager log files to troubleshoot problems with data collection.


  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Collecting.
  4. Click the Collector-Manager for your collector instance.
    Collector-Manager::<Collector-Manager instance> - <physical_host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top