Integration Architecture

casp1032
 
 
Changes in 
DX NetOps Spectrum
 10.4.1
In the current release, 
DX NetOps Spectrum
-CA UIM integration has the following changes:
Customize the HostSsync Payload Size in OneCLick
From 10.4.1, you can customize the maximum size of the payload that you want to receive from the spectrumgtw probe to 
DX NetOps Spectrum
 during the host server sync. Set the org.
apache.cxf.stax.maxInputSizeInMB
 parameter to a desired value in the 
Spectrum_HOME\tomcat\webapps\spectrum\WEB-INF\web.xml
 file.
Default:
 8 MB
Include Virtual Machines
When you select the 
Include Virtual Machines
 checkbox, 
DX NetOps Spectrum
 syncs only the non-VMWare VMs
From the spectrumgtw probe 8.68, the vmware probe-managed VMs are not synchronized as part of the host server sync.
Disable the Host Server Integration
When you disable the 
Host Server Integration
, the sync stops and deletes the existing entities from 
DX NetOps Spectrum
. You can change the retaining of the models in 
DX NetOps Spectrum
 by using the 
RetainModelsAndRelations
 attribute in the CA UIM Manager model.
The following are the supported integration modes and the resulting actions in 
DX NetOps Spectrum
:
  • DELETE_MODELS: Delete models from 
    DX NetOps Spectrum
    Default value
  • DELETE_RELATIONS: Retain the models and delete the relationships of models.
  • RETAIN_ALL: Keep both relations and models in 
    DX NetOps Spectrum
Disable the VMWare Integration
When you disable the 
VMWare Integration
, the sync stops and deletes the existing VMWare entities from 
DX NetOps Spectrum
. You can change the retaining of the models in 
DX NetOps Spectrum
 by using the 
RetainModelsAndRelations
 attribute in the CA UIM Manager model. 
The following are the supported integration modes and the resulting actions in 
DX NetOps Spectrum
:
  • DELETE_MODELS: Delete models from 
    DX NetOps Spectrum
    Default value
  • DELETE_RELATIONS: Retain the models and delete the relationships of models.
  • RETAIN_ALL: Keep both relations and models in 
    DX NetOps Spectrum
    .
Changes in 10.2.3
From the 10.2.3 release, the 
DX NetOps Spectrum
 and CA UIM integration has undergone major changes. You can now configure the integration between 
DX NetOps Spectrum
 and CA UIM through either 
DX NetOps 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
     
    Integration
     - If you are using the spectrumgtw probe v8.65 or higher, 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 
DX NetOps 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 
DX NetOps 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 spectrumgtw probe documentation.
 SpectrumGateway Integration.png 
 
The architecture for the 
DX NetOps Spectrum
 and CA UIM integration has undergone major changes from 10.1.2. We recommend you to go through the 
DX NetOps 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 
    DX NetOps Spectrum
     will no longer leverage the SNMP Gateway or 
    DX NetOps Spectrum
     Southbound gateway. Instead, they will be routed through the new 
    DX NetOps Spectrum
     Gateway Probe.
  • Nisapi-service-host is replaced by nisapi-wasp for inventory sync from CA UIM to 
    DX NetOps 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 roles in the 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 
      DX NetOps Spectrum
       and can be deleted by the 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 r10.1.1)
When an issue occurs in the infrastructure, alert data is sent from CA UIM to the SpectroSERVER of 
DX NetOps Spectrum
 through the Southbound Gateway component. SpectroSERVER is a primary server for 
DX NetOps Spectrum
. For more information, see the SpectroSERVER and 
DX NetOps Spectrum
 Databases
 section.
Using the Southbound Gateway, you can centralize network management, allowing 
DX NetOps Spectrum
 to capture and display data. Alert data is organized into 
DX NetOps 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 
DX NetOps 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 
DX NetOps Spectrum
 EventAdmin model receives the trap and translates it into a 
DX NetOps Spectrum
 event. If the event corresponds to a critical, major, or minor condition, the corresponding alarm is raised on a 
DX NetOps Spectrum
 model. The model where the alarm is raised depends on a few factors. We recommend having a previously modeled device in 
DX NetOps Spectrum
. If the device model is present in 
DX NetOps Spectrum
, the alarm is asserted against the existing device model. If the device model does not exist in 
DX NetOps 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 - 
DX NetOps Spectrum
 Integration Architecture, till 10.1.1:
 SPEC--Nimsoft Solution Architecture 
The integration between 
DX NetOps Spectrum
 and CA UIM through Web Server is designed to support server management. The HostServer models resulting from the integration provides traditional 
DX NetOps 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 
DX NetOps Spectrum
 to view the server information.
When the CA UIM and 
DX NetOps Spectrum
 integration is enabled from the OneClick Administration page, 
DX NetOps 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 
DX NetOps Spectrum
. The alert data is sent from CA UIM to the SpectroSERVER of 
DX NetOps Spectrum
 through the Southbound Gateway component. The received data is mapped to a 
DX NetOps 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 
DX NetOps Spectrum
.
The following diagram illustrates the architecture of the CA UIM - 
DX NetOps Spectrum
 Integration for Server Management through the Web Server (till 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 
    DX NetOps 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.