DB Insight traps no longer generate alarms in Spectrum

Document ID : KB000020965
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

After upgrading DB Insight from 11.3 to 11.5, the traps sent to Spectrum are no longer raising alarms.

Solution:

This issue is specific to the use of Spectrum release 9.1 and the Field/Services developed DB Insight Integration.

This integration provides alarming in Spectrum when traps from DB Insight are received in Spectrum. This integration configures Spectrum so that:

  • The alarms are raised with the correct severity and information.

  • The alarms are routed to the correct device model in Spectrum the trap is related to via the South Bound Gateway (SBGW) functionality in Spectrum.

  • The integration relies on specially configured Event files provided by CA Services or Field representatives.

The standard custom integration provided is based on Spectrum release 9.1 and DB Insight release 11.3.

As of the DB Insight release 11.4 and newer releases, there were changes to the traps and their contents that will break this custom integration.

If the DB Insight is upgraded a common symptom is that the expected alarms will no longer be seen. Instead you may see no alarms at all, or unknown trap events raised in Spectrum when these traps are received.

There are two possible solutions to execute to resolve this problem.

1 - Upgrade to Spectrum 9.2 to receive out of the box support for the DB Insight traps and their alarming.

2 - Change DB Insight so that it behaves like the 11.3 release in terms of the traps it sends to Spectrum. To accomplish this:

2a - On the DB Insight system, open the $DB__INSIGHT_HOME\*idd\bin\alarm.map file.

2b - Find this section, and change the 'CONSTANTVALUE' setting from the default of 3 to 2.

So this section starts like this:

 	# -------------------INDIVIDUAL ALARMS TRAP SETTING --------------------- 
 	# 1 : noTrap(1), # 2 : withoutObjInfo(2) # 3 : withObjInfo(3) # 4 : BothTraps(4) 
 	iddmodAlarmDetailTrapTypeSetting 0 INTEGER RONLY CONSTANTVALUE 3 

And ends up looking like this:

 	# -------------------INDIVIDUAL ALARMS TRAP SETTING --------------------- 
 	# 1 : noTrap(1), # 2 : withoutObjInfo(2) # 3 : withObjInfo(3) # 4 : BothTraps(4) 
 	iddmodAlarmDetailTrapTypeSetting 0 INTEGER RONLY CONSTANTVALUE 2 

2c - Save the changes to that file, and restart the SystemEDGE agent in control of DB Insight to make this change take affect.

3 - Test the send of some traps and since the traps will now be sent in a format that Spectrum 9.1 with the custom integration will understand, the alarms should begin to function as designed again.

Do note that when a upgrade to Spectrum 9.2 does occur eventually, this change to the alarm.map file will need to be reset back to the default for proper functionality with the 9.2 Spectrum release.

This custom integration is not required in the Spectrum 9.2 release as it supports these DB Insight traps and their alarming out of the box by default.

If you still use Spectrum 9.1, you can either upgrade to Spectrum release 9.2 for out of the box support of these traps, or engage your CA Sales Representative to inquire about this custom integration for the Spectrum 9.1 release.