How to prevent CA Spectrum OneClick from seeing specific alarm types

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

Description:

In certain instances, it may be necessary to prevent certain alarms from being received by OneClick. For example, in one customer scenario, they generate an alarm for a specific trap. They only need the alarm to exist long enough for an automated trouble ticket to be created and then clear the alarm. They have attached an event pair rule to the event associated with the alarm looking for an event ID that will never be generated which then logs a clear event for that alarm. Since there is no need for the user to take action, instead of trying to filter out these alarms, they needed a way to prevent OneClick from seeing these alarms in the first place which in turn frees up OneClick from having to process these alarms.

Solution:

The "preempttypelist" parameter functionality has be added to the $SPECROOT/tomcat/webapps/spectrum/WEB-INF/web.xml file which tells OneClick which alarm types to "ignore".

The following is the format of the "preempttypelist" parameter:

<context-param>
     <param-name>alarm.web.model.preempttypelist</param-name>
     <param-value>0x4248588,0x424856d,0x4249401,0x4248410,0x4245708,0x5090d7e,0x479cd81,0x4249965,0x4245709,0x4245751,0x4246f04,0x4248699</param-value>
</context-param>

The <param-value> tag is a comma separated list of alarm type ID's you wish OneClick to ignore.

After making the above change, you will need to restart tomcat.

The "preempttypelist" parameter may have to be re-implemented after a patch or upgrade install.