CA Spectrum and CA UIM
From the Spectrum v10.1.2 release, the SNMP Gateway probe and SBGW / Southbound gateway are no longer recommended for alarms synchronization from CA UIM to CA Spectrum. CA recommends to use the Spectrum Gateway (spectrumgtw) probe for alarm synchronization from this release.
We recommend that you go through the CA Spectrum-CA UIM Integration using spectrumgtw probe - FACT SHEET to understand the changes to the integration whether you are new to this integration or an existing user.
For more information refer to the CA Spectrum - CA UIM Integration Compatibility Matrix below:
Inventory sync using nis API /NIS Restful API (Wasp Edition)
From CA UIM 8.47 onwards, you no longer have to deploy nisapi separately.
The wasp probe which is a core component in CA UIM contains the nisapi_service_host probe functionality.
By default, the nisapi package is deployed in wasp as part of the CA UIM installation or upgrade.
10.1.2 / 10.2
8.6, 8.61 and 8.64 (Multi-tenancy feature is not supported)
8.51, and 8.51 SP1
8.51, and 8.51 SP1
8.51, 8.51 SP1 and 9.0.1
In previous releases of CA UIM, the nisapi_service_host package was deployed to the service_host probe. As of CA UIM release 8.47, the service_host probe was deprecated and its functionality was moved to the wasp probe. This change has the following implications for your CA Spectrum integration: You no longer have to deploy nisapi separately. By default, your CA Spectrum integration uses the nisapi package deployed in wasp as part of a CA UIM installation or upgrade.
- By default,the wasp probe uses port 80. However, because the wasp probe is a core component in CA UIM, this port should already be open in a properly functioning CA UIM environment. For more information, refer to the wasp probe documentation.
The CA Spectrum - CA Unified Infrastructure Management (CA UIM) (formerly known as CA Nimsoft or CA Nimsoft Monitor) Integration expands the CA Spectrum monitoring capabilities of the infrastructure with information and alarms from CA UIM and provides the following benefits:
- Provides holistic view of availability of host servers and VMware environment across the network and their performance data for fault management in a single pane of application. It also provides end to end root cause and impact analysis across network and server elements, extending CA Spectrum core capabilities to other infrastructure domains.
- Advance condition correlation between CA UIM and CA Spectrum helps in building the robust fault management.
- Leverage CA UIM capabilities for server management and use the CA Spectrum network management capabilities for an end to end infrastructure management.
The following video describes how you can integrate CA Spectrum and CA UIM to monitor your infrastructure and to use CA Spectrum’s root cause analysis feature to rapidly troubleshoot and resolve issues:
CA Spectrum and CA UIM bidirectional Integration
You can enable bidirectional integration between CA Spectrum r10.3 and CA UIM r8.5.1 using the
This integration enables reception of all CA UIM alarms by CA Spectrum and reception of CA Spectrum inventory information and all CA Spectrum alarms by CA UIM.
For more on the bidirectional integration see CA Spectrum and CA UIM bidirectional Integration.
Please see the following video to understand more about the bidirectional integration and its capabilities:
Enhancements and Improvements to the CA Spectrum and CA UIM Integration:
GUI Changes to the UIM Configuration page in CA Spectrum
From CA Spectrum 10.2.3 release, major GUI changes are done to the UIM configuration section in CA Spectrum Administrations page. You can choose the integration option to configure it from CA Spectrum or CA UIM's spectrumgtw probe. For more details, see the Changes in Integration Architecture section in the Integration Architecture page.
Following are the available configuration options:
- No Integration- Select this option to disable the Spectrum-UIM integration.
- Legacy Integration- Select this option if you are using the spectrumgtw probe v8.64 with CA Spectrum 10.2.3
- SpectrumGateway Integration- Select this option if you are using the spectrumgtw probe v8.65. The Spectrum-UIM integration is configured through UIM's spectrumgtw probe.
Configuring Integration through UIM’s spectrumgtw Probe v8.65
If you are using CA UIM's spectrumgtw probe (v8.65) and CA Spectrum r10.2.3, the integration between CA Spectrum and CA UIM is configured through CA UIM's spectrumgtw probe (v8.65) Admin Console. Select the 'SpectrumGateway Integration' option in the CA Spectrum OneClick Admin pages > UIM Configuration page. Click 'Save' then go to CA UIM's spectrumgtw probe (v8.65) Admin Console to complete the configuration. For configuration instructions, see the Deploy and Configure the Probe section the the spectrumgtw probe documentation..
Before switching the existing integration from
SpectrumGateway Integration, ensure that you have installed the patch
10.02.03.PTF_10.2.303on top of CA Spectrum 10.2.3. This patch is a solution to retain the UIMEventAdmin Models after moving integration from Legacy Integration to SpectrumGateway Integration.
From CA Spectrum 10.2.3, CA Spectrum can monitor both UIM models and SystemEdge models when CA Spectrum-CA UIM Integration is enabled with Multi-tenancy.
When the integration is enabled with Multi-tenancy, CA UIM origins are mapped to CA Spectrum landscapes. In this scenario, CA Spectrum monitors UIM models on the landscapes which are part of Multi-tenancy mapping and can monitor SystemEdge AIM based models on the landscapes which are not part of Multi-tenancy mapping.
When the CA Spectrum-CA UIM Integration is enabled without Multi-tenancy, CA Spectrum monitors UIM models only. All the SystemEdge AIM based models are deleted on all the landscapes.
vMotion Support Enhancments
From r10.2.3, when a VM is migrated (vMotion) in VMware, then the spectrumgtw probe picks the changes and sends to CA Spectrum. The changes are shown in the CA Spectrum hierarchy. The reflection time for the changes in CA Spectrum hierarchy is based on the frequency at which UIM vmware probe publishes the changes to CA UIM. This functionality is supported for both legacy integration and integration through spectrumgtw probe 8.65 version.
After deploying and starting the spectrumgtw 8.6.5, you must restart the UIM vmware probe.
In earlier releases, when CA Spectrum models UIM host Server if the network devices such as routers or switches have the same IP address then CA Spectrum reconciles based on IP address and network devices are displayed as part of UIM Manager Hierarchy.
Starting from CA Spectrum 10.2.3, for the same scenario, CA Spectrum will create UIM Host Server/UIM VM models in the UIM Manager Hierarchy and stop reconciling with the network devices with IP Address.
Support for Customized Alarms
From r10.2.3, you can manage customization (changing the severity) for UIM alarms in CA Spectrum. The spectrumgtw probe 8.65 version is enhanced to allow the Spectrum users for this customization. For more information, see the Support for Customized Alarms section in the spectrumgtw AC Configuration documentation.
Maintenance Schedule Synchronization
From r10.2.3, the Maintenance Mode schedules on devices from CA Spectrum will be synchronized to CA UIM and from CA UIM to CA Spectrum, using the integration via spectrumgtw probe v8.65. For more information, see the Schedule Maintenance Mode section.
Multi-Tenant support in CA Spectrum
From r10.2.2, CA Spectrum supports multi-tenancy by leveraging the multi-tenant capability of CA UIM through the bidirectional CA Spectrum-CA UIM integration enabled by the Spectrum Gateway (spectrumgtw) probe. The Multi-tenancy model in CA UIM is based on the Origin tag (Ownership). Using REST calls provided by CA Spectrum the spectrumgtw probe leverages this origin information. The spectrumgtw probe allows CA Spectrum to map Origin with Landscape. For more information on multi-tenancy in CA Spectrum see Multi-Tenant support in CA Spectrum.
Filter and Synchronize Specific Alarms
The CA Spectrum and CA UIM integration supports filtering and synchronizing specific alarms from Spectrum to UIM or UIM to Spectrum. The alarm filter solution reduces clutter and eliminates the sync of alarms that you do not want to monitor. After applying the alarm filters you can see only the filtered alarms in Spectrum or UIM. You can configure the alarm filtering in the Spectrum Gateway (spectrumgtw) probe. For more information, see Synchronize Specific Alarms section in the Spectrum Gateway (spectrumgtw) probe documentation.
Selective Inventory Synchronization
From r10.2.1, the CA Spectrum and CA UIM integration supports selective synchronization of Server Management entities only. This functionality allows you to avoid full inventory synchronization of and select only the server inventory which you want to get synced from UIM to Spectrum. For more information, see 'Selective Inventory Synchronization' section in the Integrating CA Spectrum and CA UIM through the Web Server for Server Management page.
Custom Attributes Synchronization
You can synchronize custom attributes from CA UIM to CA Spectrum. When you enable the CA Spectrum-UIM Bidirectional Management integration, the following custom attributes are synced from UIM to CA Spectrum. For more information see, custom attributes section.
Supporting AWS (Amazon Web Services) Cloud Monitoring
AWS Cloud (Amazon Web Services) Monitoring is supported by CA Spectrum using the CA UIM and CA Spectrum integration. The aws (Amazon Web Services) Monitoring probe deployed in CA UIM enables the metric data collection from the AWS instances. This data is then synchronized from CA UIM to CA Spectrum. For more information, see Supporting AWS (Amazon Web Services) Monitoring.
Supporting azure (Microsoft Azure Monitoring)
Microsoft Azure Monitoring is supported by CA Spectrum using the CA UIM and CA Spectrum integration. The azure (Microsoft Azure Monitoring) probe deployed in CA UIM enables the metric data collection from the AWS instances. This data is then synchronized from CA UIM to CA Spectrum. For more information, see Supporting Microsoft Azure Monitoring.
ESX Host Server Maintenance Mode enhancement
From CA Spectrum 10.2.1, you can now choose whether to retain the default correlation between the ESX host and the VMs during Maintenance mode. By default, all the VMs under the ESX Host are automatically placed in maintenance mode. You can now choose to set only the parent ESX host server in maintenance mode and not the child virtual machines that are hosted on the ESX server. For more information see, Place ESX Host in Maintenance Mode or Hibernation.
SNMP profile Synchronization
From this release, SNMP profiles for CA Spectrum inventory in a Global Collection are synchronized by the Spectrum gateway (spectrumgtw) probe to SNMP Collector so that it can monitor those without re-entering SNMP credentials.
When inventory data is synchronized from CA Spectrum to CA UIM via spectrumgtw probe, the SNMP credentials are also synchronized and stored in the CA UIM database. The SNMP profiles synchronized from CA Spectrum are shared with the Discovery server, and once the SNMP Collector probe provides the IP range relevant to the profiles synchronized, you no longer need to re-enter the SNMP credentials while logging in to the CA UIM interface.
The configuration of integration parameters is done in the Spectrum gateway configuration. This capability is only available for the integration between CA Spectrum 10.2.1 and CA UIM 8.5.1 using the spectrumgtw probe 8.6 versions.
SSL communication between Spectrum Gateway (spectrumgtw) probe and CA Spectrum
The CA Spectrum- CA UIM integration between CA Spectrum 10.2.1 and CA UIM 8.5.1 using Spectrum Gateway (spectrumgtw) probe 8.6, supports secure (https) communication the gateway probe and CA Spectrum. You need to ensure that the CA Spectrum OneClick Server is configured for SSL (HTTPs) and that https is selected as the communication protocol in the Spectrum Gateway (spectrumgtw) probe configuration.
For more information see:
Configure OneClick for Secure Sockets Layer
Spectrum Fault Tolerant Scenarios
Back-end changes have been made to CA Spectrum to prevent modeling new entities, reported by CA UIM, in a particular SpectroSERVER if it is a Secondary SpectroSERVER. However updating the models and their relationships will still be done in secondary SpectroSERVER.
Improved the OneClick Server logging for CA Spectrum-CA UIM integration to give insights into what has been modeled an what was not, movement of VMs across different ESX hosts, relationship additions and deletions etc.
Till now CA Spectrum used to reconcile entities like Vcenters, VMs and Hosts. CA Spectrum is able to reconcile logical entities like Datacenters, Clusters and Resource Pools with existing models of corresponding entity types if they were modeled previously to prevent duplication in error scenarios.
CA Spectrum will now reconcile ESX hosts with existing ESX hosts or UIMHostServer models only. If ESX host is reconciled with a UIM Host Server model then the existing UIMHostServer model will be deleted and a new ESX model will be created for that ESX host. This newly created model will be part of both Virtualization and Server hierarchies.
If an ESX server is already modeled in CA Spectrum with a model type other than UIMVirtualMachineHost or UIMHostServer, the ESX Server is not reconciled as part of the CA Spectrum-CA UIM integration.
Out of box solution for managing VM as a server
You no longer need to deploy the
vmwareprobe to synchronize VMware inventory. If VMs are being monitored as a server in CA UIM it can be pulled into CA Spectrum for Server management.
: The vmware probe allows you to monitor standalone ESX Host Servers and it's corresponding hierarchy in a CA UIM context. CA Spectrum does not support this. This is only supported if you are monitoring ESX Servers through VCenter using vmware probe.
Delete Unreported Entities in CA Spectrum (Virtualization Management)
In previous versions of the CA Spectrum-CA UIM integration, the virtual entities/ models that were not reported during a synchronization cycle were auto-deleted. From this release, these models will be placed in the Unreported Entities/ Models container, instead of being deleted.
See Delete Unreported Entities.