Integration Architecture

Changes in Integration Architecture 
From CA Spectrum 10.2.3 release, the CA Spectrum and CA UIM integration has undergone major changes. You can now configure integration between CA Spectrum and CA UIM through either CA Spectrum or CA UIM's spectrumgtw probe (v8.65) Admin Console. 
You can see the following options in the UIM Configuration page:
    • No Integration
    • Legacy Integration
    • SpectrumGateway
      - If you are using the spectrumgtw probe v8.65, select this option to configure the integration through spectrumgtw probe.
No Integration
 - Select this option button and click Save to disable the integration.
Disable the integration.png
Legacy Integration
 - Select this option to configure the integration through CA Spectrum.
The Legacy Integration option is used when you are using the spectrumgtw 8.64 for the integration. If the integration is already enabled before upgrading CA Spectrum, after the upgrade the 'Legacy Integration' appears as selected by default.
Legacy Integration.png
SpectrumGateway Integration
 - Select this option to configure the integration through UIM spectrumgtw probe v8.65. For instructions, see the Deploy and Configure the Probe section the the spectrumgtw probe documentation.
SpectrumGateway Integration.png
The architecture for the CA Spectrum and CA UIM integration has undergone major changes from CA Spectrum r10.1.2. We recommend you to go through the CA Spectrum-CA UIM Integration using spectrumgtw probe - FACT SHEET to understand the changes to the integration if you are new to this integration or an existing user.
Here are some key changes to the integration architecture:
  • Alarms sent from CA UIM to CA Spectrum will no longer leverage the SNMP Gateway or Spectrum Southbound gateway. Instead, they will be routed through the new Spectrum Gateway Probe.
  • Nisapi-service-host is replaced by nisapi-wasp for inventory sync from CA UIM to CA Spectrum
  • Server Management
    • Has removed dependency on dedicated role
    • Added ability to monitor VM as a server without dependency on Vmware probe
    • Pulls inventory with one of the role in database as DatabaseServer, Host, VirtualMachine, VirtualMachineHost, WebServer, vCenter.
  • Vmware Management
    • Handle Flapping inventory/relationships from UIM
    • Unreported inventory by UIM will be kept in a separate container in Spectrum and can be deleted by user when no more needed
Here's an overview of the updated integration architecture:
  Integration Architecture.png
Architectural Overview - using SBGW component /snmpgtw probes (till CA Spectrum r10.1.1)
When an issue occurs in the infrastructure, alert data is sent from CA UIM to the SpectroSERVER of CA Spectrum through the Southbound Gateway component. SpectroSERVER is a primary server for CA Spectrum. For more information, see the SpectroSERVER and CA Spectrum Databases section.
Using the Southbound Gateway, you can centralize network management, allowing CA Spectrum to capture and display data. Alert data is organized into CA Spectrum event and alarm data as appropriate and is displayed within OneClick.
The Southbound Gateway can be used with any incoming alert data stream format. The Southbound Gateway provides a simple, non-programmatic integration point for systems that can generate SNMP traps. It is also useful for managing non-SNMP environments. Southbound Gateway supplies an import tool that accepts XML-formatted alert data in case the system with which you are integrating cannot generate SNMP traps. For more information, see the section.
Once the Southbound Gateway receives the alert data, the data is mapped to a CA Spectrum event in an AlertMap file. The Southbound Gateway determines the appropriate EventAdmin model to receive the alert data based on the IP address of the host computer that is sending the data. The IP address of the host computer should match the IP address that is used to create the EventAdmin model.
The CA Spectrum EventAdmin model receives the trap and translates it into a CA Spectrum event. If the event corresponds to a critical, major, or minor condition, the corresponding alarm is raised on a CA Spectrum model. The model where the alarm is raised depends on a few factors. We recommend having a previously modeled device in CA Spectrum. If the device model is present in CA Spectrum, the alarm is asserted against the existing device model. If the device model does not exist in CA Spectrum the alarm is asserted against an auto-created EventModel of the Nimsoft Robot that is reporting the condition.
The following diagram illustrates an overview of the CA UIM - CA Spectrum Integration Architecture, till CA Spectrum 10.1.1:
SPEC--Nimsoft Solution Architecture
The integration between CA Spectrum and CA UIM through Web Server is designed to support server management. The HostServer models resulting from the integration provides traditional Spectrum capabilities such as layer2 connectivity and fault isolation with the features supported by CA UIM. You can use the Launch-in-Context feature to launch the CA Unified Management Portal (UMP) view from the server models in CA Spectrum to view the server information.
When the CA UIM and CA Spectrum integration is enabled from the OneClick Administration page, CA Spectrum receives the data from CA UIM through the Rest API. Once we get the data from the Rest API, CA UIM hosts are modeled in CA Spectrum. The alert data is sent from CA UIM to the SpectroSERVER of CA Spectrum through the Southbound Gateway component. The received data is mapped to a CA Spectrum event. The Southbound Gateway determines the appropriate EventAdmin model to forward the event. Metric violation traps that are coming from CA UIM are asserted on the respective Nimsoft host models in CA Spectrum.
The following diagram illustrates the architecture of the CA UIM - CA Spectrum Integration for Server Management through the Web Server (till CA Spectrum v10.1.1):
Server management_WebServer.png
  • CA UIM Probes
    Provide the intelligence to manage specific components on a managed device. For example, the cdm processes probe is responsible for monitoring CPU, disk, and memory usage on target hosts. Over 135 CA CA UIM probes are available, to let you manage the entire IT infrastructure, including servers, network devices, applications, and databases.
  • Nimsoft Alarm Server (NAS)
    Receives and manages incoming alarm messages. The Nimsoft Alarm Server supports message suppression and provides clients with services such as event updates, message filtering, automated actions, and mirroring capabilities.
  • SNMP Gateway Probe (snmpgtw)
    Sends out the traps from CA UIM to CA Spectrum. This probe converts alarms to SNMP-Trap messages which are readable by any SNMP-based management system. It subscribes to CA UIM internal alarms and processes these alarms into SNMP traps with all the information about the alarm that is encoded in the trap varbinds.