I have created custom events in Spectrum. One to assert and generate an alarm and one to clear the alarm. Is there a way to test asserting and clearing a custom alarm in Spectrum with these events?
Release: Any
The "create event" command can be used in the Command Line Interface (CLI) to create the events that generate and clear the alarms.
The create event command creates an event with type event_type and text event_text for the model that is specified by model_handle. If a landscape_handle is specified, the event is created for the user model that created the event.
Note: In previous versions of the CLI the event was created for the landscape model.
If model_handle or landscape_handle is not specified, then the event is created for the user model that created the event or the current model if one has been specified. Some events in CA Spectrum do not have an associated model. For example, when an application connects to the SpectroSERVER, no model is associated with the event.
If create event is entered with a valid event_type, valid event_text, and a valid model_handle or landscape_handle (if present), the created entry is displayed in the event table. The create time is displayed in hh:mm:ss format.
The event_type command (also named an event code in CA Spectrum) is a 4-byte hexadecimal number: the two most significant bytes specify the developer ID for the event (0001 for CA Spectrum-generated event codes), and the two least significant bytes are a unique identifier for the event. Not all event types include user-entered text. Examples of such event types are those that include the variable {S 0} in their event format files. For those event types that do not include user-entered text, the event_text parameter is ignored but must still be present on the command line.
Note: The create event command only supports one variable: {S 0} There are no other options to pass more variables.
To create event navigate to $SPECROOT:
cd vnmsh
./connect
./create event type=0x1061a text=“fan down” mh=0x40013
Date Time Type MHandle MName MTypeName
05/11/2000 12:39:42 0x1061a 0x400134 <NAME> Bdg_CSI_CNB20
This will create event 0x1061a that can now be seen on model 0x400134 in the OneClick console.
To disconnect from CLI run:
./disconnect
Please reference the "Command Line Interface" section of the documentation for more information.
This can also be used to clear an alarm that is not user clearable by finding the clear event for the alarm cause code and then creating that event in CLI.