SolutionPack for Ericsson IMS MRFP
Table of Contents
Overview
Learn how to install and configure the SolutionPack for Ericsson IMS Media Resource Function Processor (MRFP). The Media Resource Function Processor is a subsystem of the Media Resource System (MRS) in the IP Media Subsystem (IMS). The SolutionPack for Ericsson IMS MRFP reports on the MRFP functionality of MRS.
- Performance of the various MRS resources such as MRFP services, VMRFP (Visited Media Resource Function Processor), MRFP Association, Interactive Messaging, and the IP system.
- Performance of overall MRFP functions such as MRFP audio and multimedia sessions.
- Performance of the related equipments such as plug-in units, IP interfaces, Gigabit Ethernet, Ethernet Switch module ports, and Et Resource.
This article applies to Service Assurance Suite 9.3.
This SolutionPack is one of many provided with Service Assurance Suite.
Back to TopTechnical specifications
SolutionPack version
- 1.0
Compatible EMC M&R (Watch4net) versions
- 6.3u2 and later
Data collection method
All metrics are parsed through 3GPP standard xml files.
- XML collector
Main reports
- Resources
- MRFP Services
- MrfpFunctions
- Vmrfp
- MrfpH248Association
- MS Processing
- Interactive Messaging
- IP Oam
- IP System
- Equipment Related Measurements
- PluginUnit
- EtResource
- IPinterface
- GigabitEthernet
- EthernetSwicthModulePort
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.

Back to Top
Collecting performance parameters
Before installing a SolutionPack, you must perform certain steps to ensure the SolutionPack is able to collect performance parameters from various IMS components. These parameters are transferred in 3GPP-compliant XML files from IMS to the Watch4net host using SFTP.
Before you begin
Review the configuration options for the XML collector in the APG-Text-Parsing-Library.pdf file located in the <Install_Dir>/APG/Doc directory of the Watch4net host.
Procedure
- Create a directory in the Watch4net host for collecting performance data.
For example: /opt/IMS/incoming/mrfp
- On the directory that you just created, change the permissions to
apg.
For example: # chown -R apg:apg /opt/IMS/incoming/mrfp
- Configure the OSS-RC, EMS (Element Management System), mediation node, or other to push the 3GPP-compliant XML files (i.e., Ericsson Report Output Files (ROP)) to the directory created in step 2.
These 3GPP-compliant XML files are listed in the section called Node, Performance category, Default filename pattern and 3GPP format.
- Verify the periodic transfer of the 3GPP-compliant XML files is set accordingly. If your SolutionPack is set to look for updates every five minutes (the default), make sure SFTP is invoked every five minutes as well.
- SFTP the 3GPP-compliant XML files into the directory that you just created.
Node, performance category, default file name pattern and 3GPP format
You can change the default file name pattern.
The Ericsson IMS Metrics File provides a complete listing of the expected counters for the file pattern type. This spreadsheet is available on the EMC support website http://support.emc.com.
Back to TopConfiguring the user process limits for a Linux installation
Increase the user process limits for the user account to a maximum of 65534. This modification enables services to open 65534 files and 65534 processes when needed.
Before you begin
- Make sure you have a login with root privileges.
- The installed on a server running Red Hat Enterprise Linux 6, CentOS Linux 6, or SUSE Linux Enterprise Server (SLES) 11.
- The name specified for the user account during the installation.
Procedure
- Open the /etc/security/limits.conf file.
- Add the following lines for the user.
In this example, the user is apg.
apg hard nofile 65534 apg soft nofile 65534 apg hard nproc 65534 apg soft nproc 65534
- Save the file.
- To restart the services, type the following commands from the
bin directory of the installation:
./manage-modules.sh service stop all./manage-modules.sh service start all
- To verify the changes, type su apg -c 'ulimit -n -u'
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 http://support.emc.com.
. If not listed, obtain a license by completing a Support Request (SR) form, which is available on the EMC support website- 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 Watch4net Installation and Configuration Guide provides for more information.
Procedure
- Log in and select Administration.
- Select Centralized Management in the Administration tree.
- Select SOLUTIONPACK CENTER.
- Select the SolutionPack in the Browse and Install SolutionPacks screen.
- Read the summary information and click Install.
- Select the components to install.
- Type the instance name.
- Select the server in one or more list boxes. For example, select the server in the Data collection and Reports list boxes.
- Click Next.
- For each list box you select, a screen appears.
- Click Next after you complete each screen.
- Click Install after you complete the last screen.
The installation process begins. - Select the maximize arrow next to each component to view the installation process.
When the installation successfully completes, green checkmarks appear.
After you finish
Confirming report creation
After you install a SolutionPack, you can view its reports.
To view the reports:
Procedure
- Go to .
- Click the SolutionPack to view its reports.
Results
Troubleshooting
Report display problems
What to do if data does not appear in any reports
Procedure
- 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.
- Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
- To view the log files for errors, go to Centralized Management and click .
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
- Click Administration.
- Click Centralized Management.
- Expand Scheduled Tasks.
- Click Database.
- Select the import-properties-Default task.
- Click Run Now.
- Confirm success in running the task in the Last Result and Last Result Time columns.
What to do if data does not appear in some reports
Procedure
- Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
- Search for the metric in the database.
- To view the log files for errors, go to Centralized Management and click .
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
- Go to the Administration page.
- Under Modules, click Management of Database Modules.
- 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.
- Click
Query.A list of the metric results appears. If nothing displays, the metric is not being collected.
Viewing collector errors in the Collector-Manager log files
Review the Collector-Manager log files to troubleshoot problems with data collection.
Procedure
- Click Administration.
- Click Centralized Management.
- Expand Collecting.
- Click the Collector-Manager for your collector instance.
Collector-Manager::<Collector-Manager instance> - <physical_host_ID>
- Expand Log Files and click the View File icon to review the configuration error messages.