Troubleshooting CA Performance Management Integration

Contents
casp1032
 
 
After 
DX NetOps Spectrum
 Upgrade, Integration Breaks with CA Performance Management in SSL Environment
Symptom:
 
DX NetOps Spectrum
 and CA PM integration breaks after 
DX NetOps Spectrum
 upgrade. This happens when SSL is enabled and 
DX NetOps Spectrum
 is connected to CA PM using 
https
.
Solution (for 10.2.2 and previous versions):
 
Verify whether SSL is enabled on the OneClick web server host in the 
DX NetOps Spectrum
 environment. If so, verify that the "axis2.xml" file is updated with HTTPS protocol and appropriate port number.
Follow these steps:
 
  1. Open the "axis2.xml" file in an editor from "$SPECROOT/tomcat/webapps/axis2/WEB-INF/conf".
  2. Add the following section in axis2.xml after 'http' transportReceiver:
    <transportReceiver name="https" class="org.apache.axis2.transport.http.AxisServletListener"> <parameter name="port">8443</parameter> </transportReceiver>
  3. Restart the Webserver for these changes to take affect.
Solution (for 10.2.3)
 
The "axis2.xml" file contains the following section in commented format. After 
DX NetOps Spectrum
 upgrade, you can uncomment this code and update the port number to integrate 
DX NetOps Spectrum
 with CA PM using 
https
. You must restart the Webserver for these changes to take affect.
<transportReceiver name="https" class="org.apache.axis2.transport.http.AxisServletListener"> <parameter name="port">8443</parameter> </transportReceiver>
 
Unable to Add Spectrum Data as Source to CA Performance Management
Symptom:
 
I am unable to add 
DX NetOps Spectrum
 as a data source in 
CA Performance Center
 when I select 
https
 as the protocol.
Solution:
 
Verify whether SSL is enabled on the OneClick web server host in the 
DX NetOps Spectrum
 environment. If so, verify that the "axis2.xml" file is updated with HTTPS protocol and appropriate port number.
Follow these steps:
 
  1. Open the "axis2.xml" file in an editor from "$SPECROOT/tomcat/webapps/axis2/WEB-INF/conf".
  2. Locate the following section in axis2.xml:
    <transportReceiver name="http" class="org.apache.axis2.transport.http.AxisServletListener"> <parameter name="port">8080</parameter> </transportReceiver>
  3. Change the section as follows:
    <transportReceiver name="https" class="org.apache.axis2.transport.http.AxisServletListener"> <parameter name="port">8443</parameter> </transportReceiver>
Error When Adding Device to IP Domain
Symptom:
 
I tried to add a device to a 
CA Performance Center
 IP domain in OneClick. I received an error message that stated, "The following models could not be added to the Global Collection 
Domain Name
." An additional statement claimed that the models did not exist. But I have verified that the models do exist in the landscape.
Solution:
 
You see this message if you attempt to add a device that is already associated with an existing IP domain to another IP domain. This error can occur if, for example, the device was added to the IP domain either manually or dynamically, using a Global Collection rule. The portion of the error message stating that "The model does not exist" is inaccurate. We plan to address this issue in a future version of the 
DX NetOps Spectrum
 software.
Pingable Devices in 
CA Performance Center
 Have Little Data
Symptom:
 
After synchronization, some devices that 
DX NetOps Spectrum
 contributed to 
CA Performance Center
 appear to have a Subtype of Pingable in the Inventory view. They should be classified as Router or Switch. They are legitimate devices that should be reporting lots of performance data.
Solution:
 
pingable device
 refers to a device that does not allow SNMP polling and is therefore contacted using ICMP ping tests for status and reachability statistics. Devices that are sent over from 
DX NetOps Spectrum
 can appear to be Pingable and have only status and availability data because of configuration issues. Take the following steps:
  • Make sure that 
    CA Performance Center
     has an SNMP profile with the appropriate credentials to collect SNNP data from the device. For more information, see Add an SNMP Profile to Gather Performance Data.
  • Make sure that the correct SNMP profiles are specified in the discovery profile that corresponds to the device.
  • Check firewall configuration. If the SNMP and discovery configurations are correct, a network ACL or firewall adjustment can be required to enable the Data Collector to collect SNMP data for the device.
Make sure that the Data Collectors that are assigned to the IP domain of each pingable device have network access to the devices. The level of access must be comparable to that of the 
SpectroSERVER
 or Secure Domain Connector that monitors the device in 
DX NetOps Spectrum
.
CA PM alarms are missing in 
DX NetOps Spectrum
Symptom:
CAPM alarms are missing in 
DX NetOps Spectrum
 due to CA PM and 
DX NetOps Spectrum
 machines are not in time sync.
Solution:
CA PM and 
DX NetOps Spectrum
 machines need to be in time sync, contact the network administrator.