SolutionPack for Ericsson eNodeB Summary Sheet – Service Assurance Suite 9.4

Table of Contents

Overview

Learn how to install and configure the SolutionPack for Ericsson eNodeB. This SolutionPack is a mobile network management solution designed to generate reports that show key metrics and key performance indicators (KPIs) for Ericsson eNodeB nodes. It provides real-time and historical performance reports.

Back to Top

Technical specifications

SolutionPack version

1.0

Compatible EMC M&R versions

6.5u1 and later

Data collection method

Stream collector

Main reports

Dashboard
Shows snapshots of key performance indicator (KPI) reports. You can drill down into these individual KPI reports per eNodeB and per cell:
  • Inventory of network elements monitored by this SolutionPack
  • Session Setup Success Rate (KPI)
  • eNodeB Availability (KPI)
  • Throughput (DL/UL KPIs)
  • Intra-Freq Handover Success Rate (KPI)
  • Drop Rate (KPI)

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 http://support.emc.com.

Back to Top

Performing prerequisite installation tasks

This SolutionPack requires that the performance management (PM) data from eNodeB nodes be locally available on the EMC M&R server hosting the Stream collector. You must ensure the Operations Support System-Radio and Core (OSS-RC) can push the PM data files to the EMC M&R server.

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

Procedure

  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 the OSS-RC server.
  3. Configure OSS-RC 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/<SP-name>/IncomingData/
    Here is an example of the name of a PM file: A20140710.0545+0300-0600+0300_SubNetworkONRM_RootMo,SubNetworkLTERAN,MeContextABC123_statsfile.xml.
    You can override the default directory during the SolutionPack installation.
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 http://support.emc.com.

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

Procedure

  1. Log in to the EMC M&R platform with your user name and password.
  2. Select Administration.
  3. Select Centralized Management.
  4. Select SOLUTIONPACK CENTER.
  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.

Procedure

  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

Confirming report creation

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

To view the reports:

Procedure

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

Results

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

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

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

Procedure

  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 reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  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.

Procedure

  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.

Procedure

  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