How to create a SPECTRUM Event Condition rule to prevent unwanted Live Health alarms on interface models that do not have a connection in the SPECTRUM database. (Legacy KB ID CNC TS29627)

Products

• CA eHealth

Issue/Introduction

The following are the instructions for creating a SPECTRUM Event Condition Rule on the Live Health LiveHealthAlarm 0x11213 event. The Event Condition rule will check for a connection to the associated SPECTRUM interface model using the NetworkLinkType (0x12a79) attribute. If the NetworkLinkType value is equal to 0, that indicates there is no connection in SPECTRUM so only create an event. The default condition is to generate an alarm.

0x00011213 E 50 R { 10 } CA.EventCondition, "{a 0x12a79} == {I 0}", "0x035dffff -:-", "default", "0x035dfffe -:-"

0x035dffff E 50

0x035dfffe E 50 A 3,0x0001120f,10

In the above example, the following work will need to be done:

1. Remove the default alarming on the 0x00011213 event

2. Create a new event (0x035dffff in the above example) to only generate an event

3. Create a new event (0x035dfffe in the above example) to assert a Critical Live Health Alarm.

4. The above EventDisp entry should be created in the $SPECROOT/custom/Events/EventDisp file. Do not change the default Live Health EventDisp

5. Copies of the new Event Format files will need to be added to the $SPECROOT/custom/Events/CsEvFormat directory of all SpectroSERVER and OneClick systems.

Refer to the Event Configuration Editor User Guide (SPECTRUM 8.1), Event Configuration Files Guide (SPECTRUM 8.1) and Event Configuration User Guide (SPECTRUM 9.0) for more information on creating customer events.

Related Issues/Questions:
How to create a SPECTRUM Event Condition rule to prevent unwanted Live Health alarms on interface models that do not have a connection in the SPECTRUM database.

Problem Environment:
SPECTRUM 08.01.00.00
SPECTRUM 09.00.00.00
Live Health
CallT0000221171


(Legacy KB ID CNC TS29627 )

Environment

Release:
Component: EHLH