spectrumgtw AC Configuration

spectrumAC_config
uimpga-ga
spectrumgtw_AC
The following diagram outlines the process to configure the probe to retrieve inventory and synchronize alarms:
spectrumAC_config
spectrumAC_config
From spectrumgtw 8.65, there are considerable changes to the Admin Console GUI. If you are using an earlier version of the probe, the configurable fields in the probe Admin Console vary!
Contents
Overview
You can enable bidirectional integration between CA Spectrum and CA UIM using the
spectrumgtw
probe. This bidirectional integration enables the following functionalities:
CA UIM to CA Spectrum
CA Spectrum receives all CA UIM alarms. CA Spectrum users can view UIM alarms and update (assign/ unassign troubleshooter and clear) CA UIM alarms in OneClick.
CA UIM receives updates when its alarms are updated in CA Spectrum OneClick console.
CA UIM inventory information is synchronized to CA Spectrum (starting from spectrumgtw probe 8.65).
CA Spectrum to CA UIM
CA UIM receives all CA Spectrum alarms and inventory information. Once imported, inventory information is maintained in CA UIM. CA UIM users can update (assign/ unassign troubleshooter, acknowledge) CA Spectrum alarms. CA Spectrum receives updates when its alarms are updated in CA UIM.
The Bidirectional Integration (CA UIM to CA Spectrum and CA Spectrum to CA UIM) has both capabilities that are stated above.
  • Inventory from CA Spectrum is a list of devices from a single or multiple landscapes.
  • Even if you have enabled the existing integration for Server Management and VMware Management, you can enable this bidirectional integration if you deploy and configure the spectrumgtw probe. In this case, integration for Server and VMware Management, and the bidirectional integration work without any conflict.
Configure multi-tenant CA UIM origins for each CA Spectrum landscape
The Multi-tenancy model in CA UIM is based on the Origin tag (Ownership). CA Spectrum-CA UIM integration uses this origin information. The spectrumgtw probe allows you to map Origin with Landscape. To configure origin to landscape-mapping, see Configure multi-tenant Mapping section in spectrumgtw Configure Multi-Tenancy.
Synchronize specific alarms using filters
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. To configure filters for alarm synchronization, see Synchronize Specific Alarms section in spectrumgtw Advanced Configuration.
Verify Prerequisites
Verify that required hardware and software are available and any installation consideration is met before you configure the probe.
Before deploying the required software, refer to the CA Spectrum - CA UIM Integration Compatibility Matrix.
  • CA Spectrum 10.3 and 10.3.1 and CA UIM 9.0.2 or r8.51 SP1 or 8.51 are deployed.
  • webservices_rest package version v8.51 or later on the same robot where UMP is deployed
  • The CA Unified Infrastructure Management is active.
  • The ems (Event Management Services) probe v10.2.0 and higher is deployed.
  • The vmware (VMware Monitoring) probe v6.87 and higher is deployed. (if you are managing virtualized devices with CA UIM and CA Spectrum)
  • The Spectrum UIM Services package must be deployed on the primary robot where the trellis (Application Controller) probe (v8.4.3.0) is installed.
  • To enable the Spectrum Gateway bi-directional integration, navigate to
    CA Spectrum OneClick Administration page
    >
    UIM Configuration,
    enable the CA Spectrum-UIM Bidirectional Management check box, and  select Save. Starting from CA Spectrum 10.2.3, the integration can be configured through either CA Spectrum or spectrumgtw probe Admin Console (from v8.65).
    To configure the integration in CA Spectrum, select the integration option as
    Legacy Integration,
    configure, and select the
    CA Spectrum-UIM Bidirectional Management
    checkbox then select Save.
    To configure the integration in spectrumgtw probe, select the integration option as
    SpectrumGateway Integration
    and select Save. Configure the integration in the
    spectrumgtw
    probe
    configuration page.
  • You must create a Global Collection of the devices that you want to share with CA UIM. Once the global collection is created in CA Spectrum with all the required devices, CA UIM receives that inventory information.
    If you do not want to synchronize Spectrum devices to UIM, keep the Global Collection empty. The Global Collection name must be entered in the 'spectrumgtw' probe configuration page.
  • If you were using the uni-directional integration, you should turn off the associated profile in the snmpgtw probe before you start using the spectrumgtw probe for bidirectional integration.
  • The nas probe is deployed automatically when you install CA UIM. You must ensure that the probe is active.
  • 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.
  • CA Spectrum inventory information is synchronized in CA UIM when new devices are included / deleted or updated from that global collection. The Global Collection (which is synchronized) includes only network devices. Users should not add physical interfaces by themselves, the bidirectional integration handles physical interfaces for the devices.
  • CA Spectrum inventory information is synchronized in CA UIM when new devices are included/deleted or updated from that global collection.
  • Only Physical interfaces of the devices in the configured Global Collection are synchronized to CA UIM. Users should not add physical interfaces by themselves, the bidirectional integration handles physical interfaces for the devices.
  • When a synced node is removed from the Global Collection, the CA UMP device hierarchy (tree structure) might still show that node if CA UIM manages any other perspective of that device, (if the probe is being managed by any other probe of CA UIM).
For more information, see the
spectrumgtw Release Notes.
Deploy and Configure the Probe
You must deploy the probe on a machine on the same network where DX NetOps Spectrum OneClick server is installed.
Follow these steps:
  1. Deploy the
    Spectrum UIM Services
    package. For more information, see Add Services to the trellis probe.
    The Spectrum UIM Services package has to be deployed on the primary robot where the trellis probe is installed.
  2. Ensure that the spectrumgtw probe is deployed in the same network where the CA Spectrum OneClick server is installed.
  3. Select the robot under the hub from the Admin Console.
  4. Select the
    spectrumgtw
    probe from the Probes tab and select
    Configure
    .
  5. In the
    Spectrum Configuration
    section, enter the following configuration details:
    • Hostname/IP:
      Hostname/IP of the computer where the CA Spectrum OneClick Server is deployed.
    • Protocol:
      select from the following network protocol to connect to the CA Spectrum OneClick server.
    • Port:
      Port number to access CA Spectrum OneClick.
    • User Name:
      User name to access CA Spectrum OneClick.
    • Password:
      Password to access CA Spectrum OneClick.
    • Global Collection Name:
      Specify the Global Collection Name in Spectrum for which you want to retrieve the inventory (set of selected devices)
  6. In the
    Inventory Configuration
    section, configure the inventory synchronization settings.
  7. In the
    Alarm Configuration
    section, perfom the following steps:
    1. Select the
      Alarm Integration
      checkbox to enable alarm integration.
  8. In the
    UIM Configuration
    section (as shown in the screenshot here), enter the following configuration details: Select
    Validate Connections
    from the
    Actions
    drop-down.
UIM Config page.JPG
    • UMP Hostname/IP:
      Hostname/ IP address of the system where CA UMP (Unified Management Portal) is deployed.
    • Port:
      Port number to access CA UMP (Unified Management Portal).
    • Protocol:
      select network protocol to connect to CA UMP.
      • http
      • https (from spectrumgtw 8.66)
        In 'https' mode, to access the QoS metrics information of UMP in OneClick, you must import SSL Certificate of UIM UMP Server into Spectrum OneClick Server. To import the certificate, from the OneClick home page select
        Administration
        ,
        SSL Certificates
        , upload the certificate file then select
        Save
        . Restart the OneClick web server for the changes to take effect.
    • User Name:
      Specify a CA UIM username to access UMP.
    • Password:
      Enter the password to the username specified in the previous field.
    • Spectrum Selected Landscape:
      Specify the SpectroSERVER under which UIM-managed device hierarchy is created/displayed in the OneClick view.
      When spectrumgtw probe is upgraded to 8.65 or later, provide the landscape name (not the landscape handle, ex 0x10000000) in the Spectrum
      Selected Landscape
      field.
      From spectrumgtw 8.67 onwards, the
      UIM Group Name
      field in the UIM configuration section, has been changed to
      Group Name for Hosts.
    • UIM Group Name for Hosts
      : Specify the UIM group name in this field for selective inventory synchronization of hosts (of the UIM group specified) from CA UIM to CA Spectrum. This is applicable for Server Management entities only.
    1. UIM Group Name for VMware
      : Specify the UIM group name in this field for selective inventory synchronization of VMware entities (of the UIM group specified) from CA UIM to CA Spectrum. To address the challenges in providing filtering of VMware data from UIM to Spectrum, a 'UIM Group Name for VMware' field is introduced from spectrumgtw v.8.67.
      1. Ensure that you add vCenter and ESX hosts and the corresponding virtual machines to be synced to Spectrum.
      2. If the vCenter is not part of the group, ESX and VMs are not modeled in Spectrum even though they are part of the group.
      3. If vCenter and VMs are part of the group and ESX is not, then the VMs are created without any relationship with the vCenter in Spectrum.
9. In the
Host Server Configuration
section, do the following:
From 8.68 VMware probe managed VMs are not synchronized as part of the host server sync.
    1. Select the
      Host Server Integration
      checkbox, to enable the Host Server Integration.
      When you disable the
      Host Server Integration
      , the sync stops and deletes the existing entities from Spectrum. You can change the retaining of the models in the Spectrum, using the
      RetainModelsAndRelations
      attribute in the UIM Manager model.
      The following are the supported the integration mode and the resulting action in Spectrum:
      • DELETE_MODELS: Delete models from Spectrum
        Default value
      • DELETE_RELATIONS: Retain the models and delete the relationships of models.
      • RETAIN_ALL: Keep both relations and models in Spectrum.
    2. Select the
      Include Virtual Machines
      checkbox, to syncs the virtual machines that are not managed by the VMWare probe.
    3. In the
      Full Synchronization
      field, specify the time (
      in DD:HH:MM format
      ) to run the full synchronization job.
    4. In the
      Incremental Synchronization
      field, specify the time interval (in minutes) to run the incremental synchronization from CA Spectrum.
10. In the VMware Management Configuration section, do the following:
    1. Select the
      VMware Integration
      checkbox to enable VMware integration.
      When you disable the
      VMWare  Integration
      , the sync stops and deletes the existing VMWare entities from Spectrum. You can change the retaining of the models in the Spectrum, using the
      RetainModelsAndRelations
      attribute in the UIM Manager model.
      The following are the supported the integration mode and the resulting action in Spectrum:
      • DELETE_MODELS: Delete models from Spectrum
        Default value.
      • DELETE_RELATIONS: Retain the models and delete the relationships of models.
      • RETAIN_ALL: Keep both relations and models in Spectrum.
    2. In the
      Synchronization
      filed, specify the time interval (in minutes) to run the synchronization job (for VM servers from CA Spectrum). Default: 120 min.
      From spectrumgtw, a new check is added to verify whether any UIM VMs are deleted or missed from nisapi response, and deleted from unreported inventory.
11. Close the
Validate Connections
dialog that appears with a relevant success/ error message.
12. Make the required configuration changes, based on the error message (if any).
13.
Save
the configuration changes.
14. Select
Reload
on the success message to refresh the configuration.
The probe restarts and the full synchronization job runs for inventory and alarm synchronization. Whenever the probe is restarted, by default, parallel full synchronization jobs for alarms and inventory are initiated.
Import CA Spectrum SSL (https) Certificate into Spectrum Gateway Probe
If you want to use encrypted communication (https protocol) between CA Spectrum and spectrumgtw probe, you must import the ssl/https certificate from CA Spectrum to spectrumgtw probe.
Ensure that the 'https' certificate is exported and copied to the server where the spectrumgtw probe is installed. To export the ssl/https certificate, run the following command:
keytool -export -keystore /usr/<PATH> -alias <certificate_alias> -file <FILENAME.cer>
For example:
keytool -export -keystore /usr/Spectrum/custom/keystore/cacerts -alias tomcatssl -file OCServer.cer
Copy the exported .cer file to the computer where the spectrumgtw probe is installed.
Follow these steps to import the certificate:
  1. Run the following command to import the certificate to the cacerts keystore in Security folder of spectrumgtw probe install folder.
    keytool -importcert -alias <certificate_alias> -file /<PATH>/<FILENAME.cer> -keystore /<PATH>
    For example:
    keytool -importcert -alias tomcatssl -file C:\Program Files (x86)\Nimsoft\probes\gateway\spectrumgtw\OCServer.cer -keystore C:\Program Files (x86)\Nimsoft\probes\gateway\spectrumgtw\security\cacerts
  2. When prompts, provide the keystore password as 'changeit'.
  3. After the certificate is imported, stop the spectrumgtw probe service.
  4. Start the spectrumgtw probe.
Set Log Levels
In the
Probe Setup
section, the
Log Level
drop-down list enables you to set the level of details that are written to the log file for the spectrumgtw probe.
You can define the maximum size of the log file in kilobytes in the
Maximum Log File Size(KB)
field.
The maximum value that you can enter in the field is 100000 (kb).
Configure Inventory Synchronization
You can select the synchronization frequency in the
Full Synchronization Mode
list to configure the job to run at an
(Hourly or Daily)
basis. Based on your selection in
Full Alarm Synchronization Mode
list (
Hourly
or
Daily)
, the subsequent
Full Synchronization (Hourly) list, or
Daily Specific Time (HH:MM)
field appears.You can specify the time in the
Daily
Specific Time (HH:MM)
field (in HH:MM format) to specify the time for the full synchronization. The full synchronization job runs daily at the specified time in the probe configuration. By default, the time is set to 00:00 (HH: MM).If you have selected the
Hourly
option from the
Full Alarm Synchronization Mode
list, you can select one of the following options (all values in Hours) from the
Full Synchronization (Hourly)
list:
  • 3
  • 6
  • 9
  • 12
After every full synchronization, the incremental synchronization job is scheduled to retrieve the changes (addition or deletion of devices or modifications of device attributes) from the specified Global Collection during the interval (configured time that is specified in the
Incremental
Synchronization (Mins)
field). By default, the time interval for the incremental synchronization job is set to 30 minutes. For example, if you specify 30, then the job is run after every 30 minutes and the job retrieves the changes from Global Collection in the 30-minute interval. You can also modify the value in the
Incremental
Synchronization (Mins)
field to configure the job to run at your specified intervals. Moreover, you can run the full synchronization and incremental synchronization job manually using the
Synchronize All
Inventory Now
and
Update Inventory Now
options, respectively, from the
Actions
menu.
If you are managing virtualized devices with CA UIM and CA Spectrum, ensure that the spectrum-uim-service (Spectrum-UIM-Services probe) is deployed and active.
Configure Alarm Synchronization
Full Synchronization Mode
You can select the synchronization frequency in the
Full Synchronization Mode
list to configure the job to run at an
(Hourly or Daily)
basis.
Based on your selection in
Full Synchronization Mode
list (
Hourly
or
Daily)
, the subsequent
Full Synchronization (Hourly) list, or
Daily Specific Time (HH:MM)
field appears.
You can specify the time in the
Daily Specific Time (HH:MM)
field (in HH:MM format) to specify the time for the full synchronization.
The full synchronization job runs daily at the specified time in the probe configuration. By default, the time is set to 00:00 (HH: MM).
If you have selected the
Hourly
option from the
Full Synchronization Mode
list, you can select one of the following options (all values in Hours) from the
Full Synchronization (Hourly)
list:
  • 1
  • 6
  • 12
Incremental Synchronization (Secs)
After every full synchronization, the incremental synchronization job is scheduled to retrieve the changes (addition or deletion of alarms or modifications of alarm attributes) from the specified Global Collection during the interval (configured time that is specified in the
Incremental Synchronization (Secs)
field). By default, the time interval for the incremental synchronization job is set to 30 seconds. For example, if you specify 30, then the job is run after every 30 seconds and the job retrieves the changes from Global Collection in the 30-second interval. You can also modify the value in the
Incremental
Synchronization (Secs)
field and configure the job to run at specific time intervals. Moreover, you can run the full synchronization and incremental synchronization job manually using the
Synchronize All Alarms Now
and
Update
Alarms Now
options from the
Actions
menu.
Synchronize Alarms
By default, the bidirectional alarm synchronization between CA Spectrum and CA UIM is enabled for all alarms. However, you can select unidirectional synchronization of alarms, for example, you can synchronize alarms only from CA Spectrum to CA UIM or exclusively from CA UIM to CA Spectrum. You can specify the direction in which the alarms are synchronized from the
Synchronize Alarms
drop-down list. If you opt for either unidirectional synchronization of alarms option, all alarms are synced based on the direction you select from the drop-down list.
  • You should have Administrator privileges to synchronize alarms in a context.
  • Any actions that are performed on the synchronized alarms (Clear, Acknowledge, Update) reflect on both front-ends (CA Spectrum and CA UIM / UMP).
Ticket ID Custom Field
The Ticket ID Custom Field is a mandatory field. You cannot save your configuration unless you select an appropriate custom field.
To configure the Ticket ID Custom Field, follow this step
:
  1. From the list that is populated in
    Ticket ID Custom Field
    drop-down list, select an appropriate custom ID field.Based on the Custom ID field you select, the Ticket ID mapping is performed.
The spectrumgtw probe determines whether to read/write and synchronize the Ticket ID/ information from CA Spectrum to CA UIM or CA UIM to Spectrum based on what you select in custom ID field.
The following Ticketing gateway probes are supported by this integration:
  • ServiceNow Gateway (sngtw) probe v2.21
  • CA Service Desk Gateway (casdgtw) probe v2.51
  • CA UIM Service Desk Gateway (nsdgtw) probe v1.34
  • HP Service Manager Gateway (hpsmgtw) probe v1.11
  • The Ticket ID synchronization functionality will only work if the ticketing system is configured on either CA Spectrum or CA UIM. If both have a ticketing system that is configured, the synchronization does not work and it results in unexpected system behavior.
  • When the ticketing system is configured on CA UIM, ensure that the custom property you select from the drill-down option matches the custom property that is configured in the Ticketing gateway probe.
Alarm (Severity, Attribute, and Action) Mapping
CA Spectrum — CA UIM Alarm Severity Mapping
The following tables display the alarm severity mapping between UIM and Spectrum that is based on the alarm severity as raised in the source application:When the alarm is raised in UIM, and the alarm is viewed in Spectrum:
CA UIM Severity Status
CA Spectrum Severity Status
Informational
Event
Warning
Event
Minor
Minor
Major
Major
Critical
Critical
When the alarm is raised in CA Spectrum, and the alarm is viewed in CA UIM:
CA Spectrum Severity Status
CA UIM Severity Status
Minor
Minor
Major
Major
Critical
Critical
Maintenance
Informational
Suppressed
Informational
Initial
Informational
Device Attribute Mapping
CA UIM Attribute
CA Spectrum Attribute
Label
Model_name (0x1006e)
Description
HWComponentDescription (0x129e0) for Ports;
Description (0x230017) May not always present;
sysDescr (0x10052)
PrimaryIPV4Address
Network_Address (0x12d7f)
Primary Address (0x12d80) for devices
Ip_address (0x12dbb) for interfaces
PrimaryIPV6Address
USMPrimaryIPV6Address (0x5b60003) *External
PrimaryMacAddress
MAC_Adress (0x110df)
OtherMacAddresses (comma separated list)
USMOtherMACAddressess (0x5b60002) *External
Primary Role (maps too CM_COMPUTER_SYSTEM.dedicated)
Model_Class (0x11ee8)
PrimaryOSVersion
NRM_runningfirmware (0x12de0)
Vendor
Vendor_name (0x11570)
Model
DeviceType (0x23000e)
PhysSerialNumber
Serial_Number (0x10030) *only for devices
USMDeviceSerialNumber (0x5b60005) for ports *External
sysLocation
Location (0x23000d)
sysContact
ContactPerson (0x23000c)
SysName (sysName from MIB-II System group)
sysName (0x10b5b) *External
sysLocation
Location(0x23000d)
sysContact
ContactPerson (0x23000c)
sysServices
sysServices (0x1102f) *External
sysUpTime
sysUpTime (0x10245) *External
sysObjectID
sysObjectID(0x10053) *External
FirmwareVersion
FirmwareVersion (0x12de0)
SignificantModelHandle
SignificantModelHandle (0x12a56)
Alarm Attribute Mapping
The following table maps the corresponding alarm attributes between alarms that are raised in CA UIM and CA Spectrum:
CA UIM Alarm Attribute
CA Spectrum Alarm Attribute
Alarm ID
Alarm ID (0x11f9c)
Alarm Title
Alarm Title (0x12b4c)
Level
Severity (0x11f56)
createTime
Creation Date (0x11f4e)
userClearable
User Clearable (0x11f9b)
Assigned To
Trouble Shooter (0x11f57)
Interface Attribute Mapping
The following table maps the corresponding interface attributes between interfaces in CA UIM and CA Spectrum:
CA UIM Interface Attribute
CA Spectrum Interface Attribute
IfIndex
IfIndex
Ifdescription
ifDescr
IfType
IfType
IfPhysAddress (custom) and/or PrimaryMacAddress
Physical_Addr
instanceName
ifName
IfAlias (custom) and/or namedAliases
ifAlias
NomSpeedInBitsPerSec
IF_Speed
IfMTU (custom)
ifMtu
IfAdminStatus
ifAdminStatus
IfOperStatus
IfOperStatus
IfPrimaryIPV4Address
ip_address
Alarm Action Mapping
The following table displays the corresponding alarm action mapping between CA Spectrum and CA UIM:
CA Spectrum Alarm Action
CA UIM Alarm Action
Assign
Assign
Unassign
Unassign
Acknowledge
Not Applicable
Clear
Acknowledge
Additional Alarm Considerations
  • DNS Lookup - When the DNS Lookup option is enabled in the Raw Configuration, it finds the IP address of the device using the provided host name. To enable the DNS Lookup option, go to Raw Configuration Interface > setup > alarms section, update the value of the DNS_ENABLED key to
    True
    .
    Default: false
  • Alarm acknowledgements from CA Spectrum are not sent to CA UIM, while alarm acknowledgment from CA UIM is sent as clear alarm in CA Spectrum. In CA UIM acknowledging the alarm clears it in CA Spectrum, while in CA Spectrum acknowledging the alarm recognizes the presence or existence of the alarm.
  • Non-clearable alarms that are raised in CA Spectrum cannot be manually cleared/acknowledged from CA UIM.
  • For alarms on logical entities that are received from CA Spectrum the CA UIM alarm is updated with its parent IP.
  • CA Spectrum alarm raised on those entities which are not synchronized to CA UIM, are displayed in the CA USM > Global Alarm View of CA UIM (UMP) Unified Management Portal.
  • CA UIM alarm raised on an entity, which is not a discovered model in Spectrum, then a new EventModel gets created and that alarm gets asserted on that EventModel.
Ticket Handling
Trouble tickets that are managed by the CA UIM ticketing gateway probes for alarms from CA Spectrum are not annotated with information about root cause and symptomatic conditions of the related alarms. For example, if a trouble ticket is generated by a CA UIM ticket gateway for a CA Spectrum alarm, and it is then determined by CA Spectrum that the alarm is symptomatic to another alarm from CA Spectrum, the ticket for the symptomatic alarm is not annotated to indicate anything about the symptomatic condition.
Support for Customized Alarms
The spectrumgtw 8.65 version is enhanced to allow CA Spectrum users to handle the customization (changing the severity) for UIM alarms in CA Spectrum. For example, alarms with 'Information' severity on UIM can be mapped with different severity in CA Spectrum. The following parameters are introduced in the spectrumgtw.cfg file of spectrumgtw probe:
     <enable_custom_alarms>
      <map_multiple_severities>
The default values for these parameters are 'no'. When the value is 'no' for these two parameters, the event customization is not allowed and the existing alarm mapping is applied. To know the existing alarm-mapping information, see the Alarm (Severity, Attribute, and Action) Mapping section in this page.
By modifying these parameters, CA Spectrum users can modify the severity for UIM alarms. Following examples are two different scenarios, which helps you to understand the alarm severity with customization in CA Spectrum:
Scenario 1:
In the spectrumgtw.cfg file of spectrumgtw probe, if the 'enable_custom_alarms' and 'map_multiple_severities' parameters value is set to 'yes', then the spectrumgtw probe sends the update to CA Spectrum to delete the existing alarm and create an alarm regarding the customization in CA Spectrum with new severity key.
enable_custom_alarms =
yes
map_multiple_severities =
yes
The following table shows both CA UIM Severity and customized severity in CA Spectrum.
CA UIM Alarm Severity Status
CA Spectrum Alarm Severity Status (Customization)
Critical
Minor
Major
Critical
Minor
Major
Informational/Warning
Minor
In this scenario, whenever there is a severity change, the spectrumgtw probe sends request to delete the existing alarms and create an alarm with mapped severity in CA Spectrum.
When an alarm in CA UIM with severity as Critical and it is customized to Minor severity in CA Spectrum, if you update a Critical alarm severity to Minor in CA UIM, then existing Minor alarm in CA Spectrum is deleted and a new alarm is created regarding the customized mapping (that is, Major).
Scenario 2:
In the spectrumgtw.cfg file of spectrumgtw probe, if the 'enable_custom_alarms' parameter values is set to 'yes' and the 'map_multiple_severities' parameter value is set to 'no', then the spectrumgtw probe sends the alarms to CA Spectrum even if the severity is changed in CA UIM.
enable_custom_alarms =
yes
map_multiple_severities =
no
The following table shows both CA UIM Severity and customized severity in CA Spectrum.
CA UIM Alarm Severity Status
CA Spectrum Alarm Severity Status
(Customization)
Critical
Minor
Major
Minor
Minor
Minor
Informational/Warning
Minor
In this scenario, if all alarms in CA UIM are customized as Minor in CA Spectrum, if you update the Critical alarm severity to Major in CA UIM, then it updates the existing Minor alarms in CA Spectrum.