| Asset ID: |
1-72-2182688.1 |
| Update Date: | 2017-11-12 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2182688.1
:
xDR Builders Not Showing Any Information In IXP Software Menu
| Related Items |
- Oracle Communications Performance Intelligence Center (PIC) Software
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
|
In this Document
Created from <SR 3-13228602531>
Applies to:
Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.3 to 9.0.4 [Release 9.0]
Information in this document applies to any platform.
Symptoms
In NSP CCM, list of xdr builders under Mediation => IXP => Software is empty.
Changes
Cause
NSP is not able to reach one JMX from one IXP server of the subsystem.
/var/log/nsp/weblogic/nsp/application.log:
2016-09-11 14:00:15,627 - ERROR - NSPWL1 - Centralized Configuration - tekelec - SYSTEM - Exception caught inside SubsystemSoftwareModel.getInstalledBuilders()::Unable to connect host - 10.2.3.1. Please contact system administrator. - com.steleus.nsp.config.system.exception.NSPCentConfException: Unable to connect host - 10.2.3.1. Please contact system administrator.
Solution
Gather JMX logs for root cause analyzes
- Connect on IXP as cfguser (IP is mentioned in application.log)
- Change directory:
cd $PROC
- Find jmxlog (usually jmxAgent.log) with ls
- Copy log in cfguser home directory:
cf.cat jmxAgent.log > ~/jmxagent.log
Most common causes are:
- Too many alarms to sent by JMX
- NSP not able to handle the amount of alarms
Restart jmx to recover
- Connect on IXP as cfguser (IP is mentionned in application.log)
- Stop jmx:
pm.set off JmxAgent
- Ensure it is stopped with pm.getprocs. It might take 1 minute to stop
- Start jmx:
pm.set on JmxAgent
Attachments
This solution has no attachment
