Troubleshooting CA UIM and CA Spectrum Integration

Contents
casp1032
Contents
CA Spectrum not receiving alerts from CA UIM
Symptom:
The Spectrumgtw's alarm syncing functionality is not working and it was working previously. No changes to spectrumgtw configuration were made.
Cause:
Check if the state of the Trellis probe in a failed state. Trellis probe is used in the integration with Spectrumgtw probe. If it is in a failed state then the Spectrumgtw-service will not work.
Solution:
To resolve the issues, 'cold start' (Deactivate-Activate) the Trellis probe.
 
spectrumgtw probe configuration is not being saved on Spectrum 10.2 integration with CA UIM 8.47 and 8.51
Symptom:
An error message is displayed when saving the spectrumgtw probe configuration through the Admin Console.
Cause:
The Spectrum OneClick web server machine is not responding to heartbeat restful post.
http://<OneClick_hostname>:<port>/spectrum/restful/heartbeat
This issue is resolved from Spectrum 10.2.1 (and above) integration with UIM 8.5.1.
Solution:
There are missing entries in the $SPECROOT/tomcat/webapps/spectrum/WEB-INF/web.xml file on the CA Spectrum OneClick web server machine.
 
com.ca.spectrum.restful.servlet.OneClickServlet
com.ca.spectrum.restful.servlet.HeartbeatServlet
com.ca.spectrum.restful.servlet.EventAlarmServlet
com.ca.spectrum.restful.servlet.HeartbeatAlarmResponseServlet
com.ca.spectrum.restful.servlet.UniversemhServlet
Alarm Forwarding Not Working for CA UIM
Symptom:
On a Distributed
SpectroSERVER
(DSS) setup, when the CA UIM managed hosts are modeled in Spectrum on landscapes other than Main Location Server (MLS), the CA UIM alarms that are raised on hosts may not get forwarded to the host models in non-MLS landscapes.
Solution:
To fix this issue, create the EventAdmin models manually for CA UIM Integration on all the landscapes in DSS when the integration is enabled. Review the following scenarios before creating the EventAdmin model manually:
Scenario 1:
For fresh integration or if the CA UIM models (existing models or CA UIM host models) are on landscapes other than MLS, create the EventAdmin models manually on other landscapes so that the alarms are forwarded to hosts. 
 Use the default options while creating the EventAdmin model and do not enable the Alert_Forwarding_Enabled attribute.
Follow these steps:
  1. To launch the OneClick Console, select Start Console at the top of the OneClick page, and log in as a
    CA Spectrum
    administrator.
  2. Select the
    SpectroSERVER
    and Universe on the Explorer tab of the OneClick Navigation panel.
  3. Select the Topology tab on the Contents panel and click the Create a New Model by Type icon.
    The Select Model Type dialog appears.
  4. Click the All Model Types tab.
  5. Select EventAdmin and click OK.
    The Create Model of Type dialog appears.
  6. Enter the name and IP address of the CA UIM server and click OK.
    The CA UIM server is added to the topology as the selected model type.
    For more information about creating a model in OneClick, see the Modeling and Managing Your IT Infrastructure
     
    section.
Scenario 2:
If CA UIM Integration is enabled through the Southbound Gateway and an EventAdmin model already exists on a landscape, the attribute SBG_AlertForwardingEnabled must be enabled for the existing EventAdmin. The EventAdmin models must be created manually on other landscapes.
Follow these steps:
  1. To create an EventAdmin model manually, follow the instructions that are documented for Scenario 1.
  2. To enable the SBG_AlertForwardingEnabled attribute, select the EventAdmin in the OneClick Topology.
  3. Select the Attributes tab in the Component Detail panel.
  4. Select SBG_AlertForwardingEnabled in the left window of the Attributes panel.
    The attribute is added to the right window of the Attributes panel.
  5. Double-click SBG_AlertForwardingEnabled in the right window, and select Yes. Click OK.
    The SBG_AlertForwardingEnabled attribute is enabled.
You must delete EventAdmin and the associated event models when the integration is disabled.
Unnecessary minor alarms are noticed on VMware models
Symptom:
You may notice unnecessary minor alarms on VMware models
Solution:
To fix this issue, configure the SNMP gateway probe to avoid unnecessary minor alarms. For more information, see Deploy and Configure Probes.
If CA Spectrum and CA Unified Infrastructure Management Integration is disabled on second SpectroSERVER, you may notice Stale Nimsoft models on primary SpectroSERVER.
Stale Nimsoft Models on Primary SpectroSERVER
Symptom:
If CA Spectrum and CA UIM Integration is disabled on second SpectroSERVER, you may notice Stale Nimsoft models on primary SpectroSERVER.
Solution:
To fix this issue, you can delete the VMs and the rest of the entities in CA Spectrum OneClick console. To delete the entities, follow these steps:
  1. In the CA Spectrum OneClick console, select the corresponding model, click the attribute tab, and search
    “EditModelMask”.
  2. Change the value of
    “EditModelMask”
    from 255 to 0 and click
    Save.
  3. Right-click that entity and select the
    Delete
    option.
Traps sent from snmpgtw are not being processed in CA Spectrum after enabling the CA Spectrum-CA UIM integration.
Symptom analysis:
  
This behavior is observed mainly in environments where the snmpgtw (snmp gateway) probe is deployed on a different server, i.e. other than the integrated UIM server (as mentioned in UIM Configuration page).
Solution
You have to manually create an 
EventAdmin
 with the IP address of server/machine where the snmpgtw probe is deployed, and the traps will be handled properly using the SBGW probe (South Bound gateway) functionality.
 You also need to set the 
SBGW_AlertForwarding
 attribute to 
Yes
.
Unknown alerts received for the NimsoftHost model
Symptom analysis:
Unknown alert received trap mainly occurs on 
NimsoftHostServer
 models. The machine on which snmpgtw probe is deployed is also reported as 
NimsoftHostServer
 model in CA Spectrum, hence the models are found with the same IP address; as 
EventAdmin
 and as 
NimsoftHostServer
 model types.
When a trap is received, CA Spectrum forwards the trap to both the models with same IP Address. 
As SBGW functionality works with EventAdmin model it processes the trap and 
NimsoftHostServer
 model fails to recognize it. Hence these unknown alerts are generated.
Solution:
 
Navigate to 
NimsoftHost 
model > 
CA Spectrum Modeling Information 
sub view > Select 
Yes
 for the 
Disable Trap-Based Events
 drop-down option.
The default value is 
No
.
No unknown alert events will be observed, after you disable this option.
Missing Inventory due to Vcenter being hosted on a VM
Scenario 1:
UIM reports two entities with different CS_ID for the same host which is a VM and has a vcenter deployed on it (Vcenter hosted on VMs managed by other vcenters), which causes the hierarchy in CA Spectrum to be deleted during the subsequent syncs with UIM.
Solution
: Model the Vcenters first, consequently the VM which is acting as a vcenter will not be modeled, thus preserving the hierarchy in Spectrum
Scenario 2:
 
UIM reports one entity for a host which is a VM and has a vcenter hosted on it. Sometimes the relationship for such a VM with its parent ESX host is not reported from UIM in subsequent syncs which causes that VM to be deleted in Spectrum and since it is also a vcenter the hierarchy also gets deleted in Spectrum.
Solution: 
The relationship between such a VM and its parent ESX host will not be modeled thus preserving the hierarchy in Spectrum.
UIM Models in Lost and Found/Cluttered Universe view
Symptom
: Sometimes the relationships between ESX host and child VMs are not reported in some syncs. This causes all such VMs to be moved to the Lost and Found node. Also, All the UIM models are modeled under Universe by default which clutters the topology view of the Universe
Solution: 
A new container called
UIM Inventory
is now introduced where all the UIM entities will be placed upon creation in Spectrum. Also, in case the ESX to VM relation is not reported then such VMs will be moved to the said container thus preventing the models in Lost and Found issue.
Customer can move this UIM Inventory container across the navigation hierarchy and rename it as per his needs.
Not all CA UIM models are modeled in CA Spectrum
Symptom
: In some instances, ESX hosts, Resource Pools and VMs are reported as children of an entity whose type is “COMPUTE_RESOURCE”. This is an entity type which Spectrum doesn’t recognize which causes Spectrum to not process the children of such entities.
Solution
: CA Spectrum has been modified to recognize
“COMPUTE_RESOURCE”
entity type, thus enabling modeling the children of such entities
OneClick Client hangs when metric views of UIM models are expanded
Symptom
: Sometimes OneClick Client becomes unresponsive when the user clicks the metric views of the UIM models.  OneClick Server makes individual REST calls for each metric and till the response is received from the UIM, the OneClick client becomes unresponsive.
Solution
: A single
nisapi
call is made to fetch data of all the metric types for each metric family instead of  multiple calls in order to improve the performance.       
Models found in LostFound container
Symptom
: Models found in LostFound container
Probable Cause
: If there are any Virtual Machines under vApp, after disabling VMware Management integration, those VMs might be found under LostFound container
Solution
: Users should manually delete those models from the LostFound container before integrating CA Spectrum and CA UIM (VMware or Server Management) again.
Multiple JSON exception(s) in Tomcat log
Symptom
: Users might observe multiple JSONException in tomcat log (See below for exception details) during CA Spectrum- CA UIM Integration:
Error in getting the property PrimaryOSNameorg.json.JSONException: JSONObject["PrimaryOSName"] not found. at org.json.JSONObject.get(JSONObject.java:516) at com.ca.nimsoft.integration.nis.nisservice.NimsoftRESTEntity.getProperty(NimsoftRESTEntity.java:37) at com.ca.nimsoft.integration.manager.NimosftHostServerModelTask.call(NimosftHostServerModelTask.java:55) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Probable Cause
: If any inventory from CA UIM does not contain Primary OperatingSystem Name, JSONException is thrown in tomcat log
Solution
: Users can ignore these as they do not impact functionality
Unable to delete CA UIM Inventory container from source landscape
Symptom
: CA UIM Inventory container doesn't delete from source landscape even though there are no datacenters after migration
Solution
: Users should manually delete 'UIM Inventory' container. However, leaving it as is, without deleting, will not affect any functionality
Server Hierarchy under UIM manager is empty in source landscape
Symptom
: Under UIM Manager, Server hierarchy remains empty in source landscape even though there are no datacenters after migration
Probable Cause
: If there are many Virtual machines that were part of a datacenter, migration process will take more time than expected if the 'Incremental Sync Time Interval' and 'VMWare Sync Time Interval' are less than 15 minutes
Solution
: You should set '
Incremental Sync Time Interval
' and '
VMWare Sync Time Interval
' to its default value. You can manually delete
'Server'
hierarchy. However, leaving it as is, without deleting, will not affect any functionality
Servers does not migrate immediately when Datacenter(s) are migrated.
Symptom
: Servers does not migrate immediately when Datacenter is migrated. Server migration happens only after subsequent syncs
Probable Cause
: When there are many host servers that were part of a datacenter, and if the '
Incremental Sync Time Interval
' and '
VMWare Sync Time Interval'
are less than 15 minutes, the migration process will take more time than expected, 
Solution
: You should set '
Incremental Sync Time Interval
' and '
VMWare Sync Time Interval
' to its default value.
Errors in Uni directional alarms synchronization, when the synchronization options are flipped in the spectrumgtw probe Admin Console
Symptom
: Unidirectional alarms sync has problem when the option is flipped between between '
CA Spectrum to CA UIM
' and '
CA UIM to CA Spectrum
' or vice-versa,
Probable Cause
: If users are using any ems version lesser than v8.4.3 this problem is observed
Solution
: Deploy latest version on ems probe version 8.4.3