Working with Event Rules

Contents
casp1032
Event Rules
Event Rules let you specify the evaluation logic determining how 
DX NetOps Spectrum
 processes those events to which you are applying the rules. You can also specify what actions to perform in response to the events.
An event rule stipulates the conditions under which an event condition, a pattern of events, a combination of events in a particular order, or over a specific period, sets the generation of another event.
You can create multiple rules for a single event.
The Event rules are stored in event configuration files referred to as event disposition files.
Event Condition Rules
An 
event condition rule
 creates an event when specific conditions are satisfied. The input to the rule is a list of conditions and associated events. Each condition is evaluated until one condition evaluates to TRUE, and then the corresponding event is created.
The following parameters are applicable:
  • The event that starts the evaluation of the rule
  • A conditional expression to evaluate
  • If the conditional expression is true, the event to generate
An event condition rule can include multiple conditional expressions and corresponding output events.
Event Pair Rules
In some cases, you expect events to happen in pairs, and if the second event does not occur, it could indicate a problem in the computing infrastructure. Based on such a scenario the 
event pair rule
 creates an event. If one of two expected events are generated but the second event does not follow the first, a new event is generated in response. You can specify the amount of wait time that can elapse before the new event is generated.
 Other unrelated events can be generated between the first and the second event. They do not affect the execution of this rule.
Event Rate Rules
Some types of events do not indicate a problem unless the frequency at which they are generated reaches a specific threshold within a specific amount of time. An 
event rate rule
 creates an event based on this scenario. When a number of events of the same type that is, with the same event code are created within a given time period, a new event is created in response.
 Other, unrelated events do not affect rule execution.
Event rate rules never terminate. Once the conditions of the rule are met and a new event is created in response, the rule remains active. However, no additional event is created as long as the frequency at which the evaluated events remains at or above the specified rate in the rule. If the frequency drops below the specified rate, and then subsequently exceeds that rate again, a new event is generated.
An event rate rule can use either of the following methods to define the window of time in which the events must occur:
 
Sliding Window:
 With this type of time window, if the specified number of events (or more) ever occurs in any window of the specified time period, the output event is created in response. This type of time window is best suited for accurately detecting a short burst of events.
For example, the following illustration shows the sliding time windows that are active for a rule that watches for five instances of a given event (e) within a specified time period.
 spec--ec--slidingwindow--OTH 
When a sliding time window is used for a rule, if the rule generates a rule output event, all active time windows are terminated, and a new time window automatically begins.
 
Sequential Window: 
When the rule uses this type of time window, non-overlapping time windows are examined, one after another, to determine if the requisite number of events has occurred within the time window. This type of time window is best suited for detecting a long, sustained train of events.
For example, the following illustration shows the sequential time windows that are opened and closed for a rule that watches for five instances of a given event (e) within a specified time period.
 spec--ec_sequentialwindow_OTH 
If the current time window closes due to time period expiration, or if the rule creates an output event in response, the window is not opened next time until a new event occurrence is detected.
Event Series Rules
An 
event series rule
 creates an event when a specific event. triggers one or more other events in an ordered or unordered sequence. The combination of events which must occur include any number and type of event. You can specify also the amount of wait time to elapse during which the sequence of events must occur.
 
Note:
 Other, unrelated events can be generated during the wait time. They do not affect the execution of a rule.
Event Counter Rules
An 
Event Counter rule
 counts events. The rule watches for two events, one increasing the count, the other one decreasing it again. An event is generated whenever the count is higher than a threshold, and also once it falls below the set threshold. The Event Counter rule remains instantiated and counts events and does not terminate.
Heartbeat Rules
The 
Heartbeat rule
 watches for a periodic heartbeat event, and generates a new event when the heartbeat event is missing. You can stop the rule instance using a separate event. 
Single Event Rules
The 
Single Event rule
 watches for a single occurrence of a target event. The Single Event rule reduces an event stream where one event ('up' event) occurs multiple times, before a reset ('down') event is observed. Instead of the multiple 'up' events, a single event which can be reused in other rules, denoting the condition ('up' or 'down')is set. An event is generated the first time the target event is seen. The rule triggers only when the clearing event is seen again. The rule then resets the behavior to the initial state. If needed, a separate event can be generated when the clearing event is seen.
Solo Event Rules
The 
Solo Event rule
 finds an instance of target event which does not follow or precede any other user-defined event in a defined period. 
The time periods are configurable, and there is a separate event to stop the rule.
User-Defined Event Rules
Most of the CA-shipped event rules are supported on the Event Configuration User Interface. However, in some cases, CA can create a special rule or can customize a rule for an individual customer. A customer can also create a rule. 
The Event Configuration Editor does not support Event disposition entries using such rules. The displayed event rule is read-only. The rule entry must be edited in a text editor and reloaded in the event disposition files. Such custom event rule entries must have the correct vendor code and rule name, depending on which vendor supplied the rule. For example, a custom rule entry for a rule that is named MyOwnRule' from vendor 'MyOwnVendor' has the following syntax:
0xfff00002 E50 R MyOwnVendor.MyOwnRule, <rule parameters>
 The xml rule definition file is at $SPECROOT/SS/CsVendor/<Vendor Name>/EventRules/<RuleName>.xml.
Create Event Rules
We recommend that you start the application and examine the rules that CA provides for various events, before creating an event rule. 
You can create an event rule in two ways:
  • From scratch.
  • By copying an existing event rule and modifying the copy. This method is only useful in case the same event triggers the new rule that you want to copy.
 Event rule definitions are stored in event configuration files referred to as event disposition files.
 
To create an event rule:
 
  1. In the Navigation panel, select the event that activates (triggers) the event rule.
  2. In the Details panel, click the Event Rules tab.
    The list of event rules for the selected event appears.
  3. Click the list icon spec--schedule_a_policy_button.
  4. Select the type of event to create from the drop-down list.
     
    The configuration dialog for the selected type of event rule opens.
  5. Configure the event rule as required.
  6. Click OK to save the event rule to the event.
 
To create an event rule from a copy:
 
  1. In the Navigation panel, select the event that has the event rule that you want to copy.
  2. In the Details panel, click the Event Rules tab.
    The list of event rules for the selected event appears.
  3. To copy an event rule, select the desired rule and click the copy icon SPEC--copy.
    The event rule configuration dialog opens.
  4. Modify the configuration of the event rule as required.
  5. Click OK to save the event rule to the event.
Configuring Event Condition Rule Settings
To create an event condition rule, create one or more conditions to evaluate the event for which you are creating the rule. For each condition, define an event that 
DX NetOps Spectrum
 generates if the given condition is met. Optionally, you can also specify that one or more values of the event that triggered the rule is copied to the rule output event.
As an example, assume you want to create the following event condition rule (expressed in pseudo code) for event 0x210c0e:
If event 0x210c0e occurs, evaluate the following: if event variable 2 = 2 or event variable 2 = 2, then generate 0x0021001c, else if event variable 2 = 3 or event variable 2 = 4, then generate 0x0021001b, else if event variable 2 = 5, then generate 0x0021001a, else, generate 0x00210017.
This rule requires the four conditional expressions that are shown in the following rule configuration dialog.
 spec--ec--configeventconditionrule1--SCR 
In the dialog, use the buttons above the list of conditions to add new conditions and to modify, copy, and delete a selected condition. To change the sequence in which the conditions are evaluated, use the up and down arrows below the list of conditions.
The rule output event (generated event <Z>) that corresponds to the first condition that evaluates to TRUE is generated.
Event variable discriminators are a general feature available for all types of rules. However, while you can specify discriminators for an event condition rule, a rule of this type currently does not use them during rule processing.
When you add or modify a condition, you define the conditional expression using the following dialog.
 spec--ec--configeventconditionrule2--SCR 
The settings in the dialog include the following options:
  •  
    Condition ©
    The condition to evaluate. To create the expression, use the controls in the top section of the dialog.
    For information about conditional expression syntax, see Event Condition Rule.
  •  
    Generated Event <Z>- Generate Event
    If the associated condition evaluates to TRUE, the event code of the event to create in response.
    To specify the event code, click Browse, select the event in the Select Event dialog, and then click OK.
  •  
    Generated Event <Z> - Copy Event Variables
    To copy the values of any event variables in that event which activated the rule to the generated event <Z>, select Copy Event Variables and then do any of the following steps:
    • Select Copy All to copy the values of all of the event variables into the generated event <Z>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values must be copied. Ranges of IDs are also supported, for example, “1-4”.
     For information about using the proper syntax when specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Event.
To create a default condition in the condition configuration dialog evaluating to TRUE; select DEFAULT for Operator and click Insert Criterion.
Configuring Event Pair Rule Settings
The Event Pair dialog provides the following settings:
 spec--ec--configeventpairrule--SCR 
The settings in the dialog include the following:
  •  
    Event Variable Discriminators
    A comma-separated list of the IDs of the event variables in the event to evaluate as a part of the rule.
    Enter each ID separately; ranges of IDs are not supported.
  •  
    Event <Y> - Event Code
    The event code of the event that, within the specified time period, follows the event that activates (triggers) the rule. Event <Y> is the second event in the pair of events.
    To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events that are loaded into Event Configuration), and click OK.
  •  
    Time <T> - Time Interval
    The period that begins when the first event is created and during which the second event (event <Y>) occurs.
  •  
    Get Time From Attribute
    Select this option to use the value of any time attribute whose value is a quantity of time, such as like the polling _interval attribute (0x1134e). The value of the selected time attribute becomes the value of Time <T>. The time unit is seconds.
    The format would resemble the following:
    if Event X occurs and is not followed by Event Y within the time specified in the time- specific Attribute Y, then generate Event Z.
  •  
    Generated Event <Z> - Generate Event
    The event code of the event to create in response if the second event (event <Y>) does not follow the first event within the specified time interval.
    To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events that are loaded into Event Configuration), and click OK.
  •  
    Generated Event <Z> - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <Z>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into generated event <Z>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
    For information about the proper syntax to use when specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Event.
 
Event Variable Discriminators in Event Pair Rules
 
The use of discriminators not only lets multiple instances of the rule to be generated due to the same event, but also affects rule processing and termination. More specifically, if discriminators are used, the following occurs:
When the event is generated, if there are active instances of the rule, another instance of the rule is created only if the values of the specified variables are different in the new event when compared to the events that activated the existing rule instances. (If you do not specify any discriminators for a rule and if a single instance of the rule is active, then the subsequent instances of the rule are not generated when subsequent instances of the event occur.)
To terminate the rule without generating the rule output event, the values of all of the specified event variables must be the same in both the first event (that triggered the rule) and the second event (for which the rule is watching) in the pair.
As an example, assume you create an event pair rule that watches for a port down event followed by a port up event, and you specify the event variable that stores the interface ID of the port as an event variable discriminator. As a result, if device A has ports 1 and 2, and port 1 goes down, a rule instance for the event is generated. If port 2 subsequently goes down, another rule instance is also generated due to the same event because the interface ID in the second instance of the event is different. There are now two active instances of the rule due to port down events that are related to two different ports.
To continue the example, if port 2 goes up within the specified time period, the associated rule will immediately terminate without generating the rule output event if the port up event that is generated stores the interface ID of port 2 in the same event variable (that is, the IDs of the event variables in the first event and second event in the pair that store the interface ID are the same). If a similar event is not generated for port 1 within the specified time period, the associated rule terminates by generating the rule output event.
To use event variable discriminators effectively in an event pair rule, the IDs of the event variables in the contributing events must match. That is, the same event variables must store the same variable binding data. If not, you can create an event condition rule that is activated by the first event and copies the data to event variables having the appropriate IDs in the rule output event; you can then use the rule output event as the second event in the pair.
Configuring Event Rate Rule Settings
To configure an event rate rule use the following dialog: 
 Event Rate Rule dialog in OneClick 
The dialog offers the following settings:
  •  
    Event Variable Discriminators
    A comma-separated list of the IDs of the event variables that are included in the event. Events in the list are evaluated as a part of the rule.
    Enter individual IDs; ranges of IDs are not supported.
    The use of discriminators not only lets multiple instances of the rule to be generated due to the same event, but also affects rule processing. More specifically, if discriminators are used, the following occurs:
    • When the event is generated, if there are active instances of the rule, another instance of the rule is created only if the values of the specified variables are different in the new event when compared to the events that activated the existing rule instances. (If you do not specify any discriminators for a rule and if a single instance of the rule is active, subsequent instances of the rule are not generated when subsequent instances of the event occur.)
    • To generate the rule output event, the values of the variables must be the same in all instances of the same event (and all other rule conditions must be met).
  •  
    Event Rate - Occurrences <N>
    The number of instances of the same event that must be created within the specified time period for the rule to generate the output event.
  •  
    Event Rate - Time <T>
    The period during which <N> occurrences of the same event are required for the rule to generate the output event.
  •  
    Event Rate - Sliding Window
    The type of time window to use. Select a Sliding Window, or clear Sliding Window to use a 
    sequential window
     of time. For a description of both, see Event Rate Rules.
  •  
    Generated Event <Z> - Generate Event
    The event code of the event to create if <N> occurrences of the same event occur within the specified period.
    To specify the event code, click Browse, select the event in the Select Event dialog, and click OK.
  •  
    Generated Event - Copy Event Variables
    To copy the values of any event variables of the event that activated the rule into the generated event <Z>, select Copy Event Variables and do one of the following:
    • Select Copy All to copy the values of all of the event variables into generated event <Z>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values are being copied. Ranges of IDs are also supported, for example, “1-4”.
    For information about the proper syntax for specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Event.
  •  
    Low Rate Event
    (Optional) Generates a low rate event <L> if the frequency drops below the threshold. The rule generates the high rate event again only when the frequency threshold is crossed again.
  •  
    Stop Event
    (Optional) Stops the rule with an event. The rule runs continuously unless you set the stop event. In many cases, letting it run continuously is the desired behavior.
An event rate rule can also generate a different rule output event when the rate of the trigger event drops below the specified threshold. Manually modify the rule in the event disposition file and specify that rule output event. For more information, see EventRateWindow Rule.
Configuring Event Series Rule Settings
You can configure an event series rule using the following dialog.
 spec--ec--configeventseriesrule--SCR 
The settings in the dialog include the following options:
  •  
    Event Variable Discriminators
    A comma-separated list of IDs of event variables in the event to evaluate as a part of the rule. Enter each ID manually, ranges of IDs are not supported.
    To allow multiple instances of the rule to be generated due to the same event, use discriminators. The use of discriminators also affects processing and termination of rules. The following conditions apply occur if discriminators are used:
    • In case, there are active instances of the rule during event generation, another instance of the rule is created only if the values of the specified variables are different in the new event as compared to the events activating the existing rule instances. The subsequent instances of the rule are generated when a single instance of the rule is active, only when you specify any discriminators for a rule.
    • To generate the rule output event, the values of the variables must be the same in all contributing events (that is, both, in the event that activated the rule, and in all events that are specified in the series).
    To use event variable discriminators effectively in an event series rule, the IDs of the event variables in the contributing events must match. That is, the same event variables must store the same variable binding data. Alternately, you can create an event condition rule that a given event triggers and copies the data to event variables having the appropriate IDs in the rule output event. You can then use the rule output event in the series.
  •  
    Events <S> - Event List
    Select Ordered if the list (series) of events must occur in a specific sequence to trigger creation of the response event. Select Not Ordered if the events in the series can occur in any order.
  •  
    Events <S> - Event Code
    The series of events that must follow the event that activated the rule for the rule to generate the output event. If the events in the series must occur in a specific order, list them in that order.
    To add, modify, copy, and remove events from the list use the buttons above the table.
    To move an event up or down in the list, select the event, and click the up or down arrow.
    You can add an event to the series, and can specify that one or more of the values in its event variables be copied to the rule output event (generated event <Z>). To select the event in the dialog to add to the series, do any of the following actions:
    • Select Copy All to copy the values of all of the event variables to the rule output event.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values you want to copy. Ranges of IDs are also supported, for example, “1-4”.
  •  
    Time <T> - Time Interval
    The period during which the series of events must occur for the rule to generate the output event.
  •  
    Generated Event <Z> - Generate Event
    The event code of the event to create, in response to a series of events occurring within the specified period and in the specified order.
    To specify the event code, click Browse, select the event in the Select Event dialog (displaying all events that are loaded into Event Configuration), and click OK.
  •  
    Generated Event <Z> - Copy Event Variables
     
To copy the values of any event variables in that event which first activated the rule to the generated event <Z>, select Copy Event Variables, and perform any of the following steps:
Select Copy All to copy the values of all of the event variables into the generated event <Z>.
  • Select Copy, and specify a comma-separated list of specific variable IDs whose values are copied. Ranges of IDs are also supported, for example, “1-4”.
 For information about the proper syntax to use when specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Event.
To generate an event in response to a specific series of events, where one of several events triggers that same series first. To satisfy this scenario, create the same event series rule for all events that triggers the series.
Alternatively, you want to watch for any combination of a series of events and in any order, inclusive of the event that triggers the series. To satisfy this scenario, we recommend that you create the following rules:
 
Event that triggers the rule (event to which rule is applied)
 
 
Events in the series (not ordered)
 
 
Rule output event (generated event <Z>)
 
0x0001002a
0x0001002b, 0x0001002c
0x0001002f
0x0001002b
0x0001002a, 0x0001002c
0x0001002f
0x0001002c
0x0001002a, 0x0001002b
0x0001002f
Using this set of rules, any combination of events 0x0001002a, 0x0001002b, and 0x0001002c occurring in any order generates event 0x0001002f.
Configuring Event Counter Rule Settings
You configure an event counter rule using the following dialog:
 EventCounter 
The settings in the dialog include the following:
The event for which the rule is defined is the one that counts up the event. The first event initiates a new rule instance and counts (count is 1).
  •  
    Event Variable Discriminators
    A comma-separated list of the IDs of the event variables in the event to evaluate as a part of the rule.
    Enter each ID separately; ranges of IDs are not supported. Event variable discriminators are a general feature available for all types of rules. 
  •  
    Count down event <D> - Event Code
    Sets the event code that counts down by one. To specify the event code, click Browse, select the event in the Select Event dialog which displays all of the events that are loaded into Event Configuration, and click OK.
  •  
    Count down event <D> - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <D>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Count down event <D>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
     For information about the proper syntax to use when specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Event.
  •  
    Counter Event Threshold <N>
    Sets a certain threshold that when reached, generates a new event. The rule also generates another event when the count is lower then the threshold again.
  •  
    Threshold violated event <V> - Event Code
    Is generated when the count threshold is reached. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events that are loaded into Event Configuration), and click OK.
  •  
    Threshold violated event <V> - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <V>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Threshold violated event <V>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values you wish to copy. Ranges of IDs are also supported, for example, “1-4”.
  •  
    Threshold reset event Reason: - Event Code
    Generates when the count is below the threshold again. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events that are loaded into Event Configuration), and click OK.
  •  
    Threshold reset event Reason: - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event Reason:, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Threshold reset event Reason:.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values you wish to copy. Ranges of IDs are also supported, for example, “1-4”.
Configuring Heartbeat Rule Settings
You can configure heartbeat rule using the following dialog.
 Heartbeat 
The settings in the dialog include the following:
  •  
    Event Variable Discriminators
    A comma-separated list of the IDs of the event variables in the event to evaluate as a part of the rule.
    You must enter each ID; ranges of IDs are not supported. Event variable discriminators are a general feature available for all types of rules. 
  •  
    Heartbeat Event <H> - Event Code
    Sets the Heartbeat Event code. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
  •  
    Heartbeat Event <H> - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <H>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Heartbeat Event <H>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
     For information on the proper syntax to use when specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Event.
  •  
    Heartbeat Period <P>
    Sets the time gap between individual heartbeats.
  •  
    Generate event on missing heartbeat <Z> - Event Code
    Generates an event when the heartbeat event is missed. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
  •  
    Generate event on missing heartbeat <Z> - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <Z>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables to Generate event on missing heartbeat <Z>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
  •  
    (Optional) Heartbeat Rule Stop Event <S> - Event Code
    The Heartbeat Rule Stop Event stops the Heartbeat event rule.To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
Configuring Single Event Rule Settings
You can configure a single event rule using the following dialog.
 SingleEvent 
The settings in the dialog include the following:
  •  
    Event Variable Discriminators
    A comma-separated list of the IDs of the event variables in the event to evaluate as a part of the rule.
    You must enter each ID; ranges of IDs are not supported. Event variable discriminators are a general feature available for all types of rules.
  •  
    Generate single event <S> - Event Code
    It is generated the first time the trigger event is seen either when the rule is instantiated, or the first time the trigger event occurs after the reset event is seen. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
  •  
    Generate single event <S> - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <D>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Count down event <D>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
    For information on the proper syntax to use when specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Event.
  •  
    Reset rule event Reason: - Event Code
    Sets the reset event. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
  •  
    Reset rule event Reason: - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <D>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Count down event <D>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
  •  
    (Optional) Reset rule notify event <N> - Event Code
    It is generated when the reset event is seen. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
  •  
    Reset rule notify event <N>- Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <D>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Count down event <D>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
Configuring Solo Event Rule Settings
You can configure a solo event rule using the following dialog.
 SoloEvent 
The settings in the dialog include the following:
  •  
    Event Variable Discriminators
    A comma-separated list of the IDs of the event variables in the event to evaluate as a part of the rule.
    You must enter each ID; ranges of IDs are not supported. Event variable discriminators are a general feature available for all types of rules.
  •  
    Prevent period before Solo Event <B>
    Sets the time period before the solo event where none of the 'prevent' events may occur (in seconds).
  •  
    Solo Event <S>- Event Code
    Specifies the Solo event. To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
  •  
    Solo Event <S>- Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <D>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Count down event <D>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”.
    For information on the proper syntax to use when specifying variable IDs or ranges of IDs using Event Configuration, see Copying Variable Values from Contributing Events to the Rule Output Even 
  •  
    Prevent period after Solo Event Action:
    Sets the period after the solo event where none of the 'prevent' events may occur.
  •  
    Generated Event <Z> - Event Code
    Defines the event that will be generated when the rule triggers (when just the 'solo' event is seen). To specify the event code, click Browse, select the event in the Select Event dialog (which displays all of the events loaded into Event Configuration), and click OK.
  •  
    Generated Event <Z> - Copy Event Variables
    If you want to copy the values of any event variables in the first event that activated the rule to generated event <D>, select Copy Event Variables, and do one of the following:
    • Select Copy All to copy the values of all of the variables into Count down event <D>.
    • Select Copy, and specify a comma-separated list of specific variable IDs whose values should be copied. Ranges of IDs are also supported, for example, “1-4”
  •  
    Prevent Events <P>
    Defines a list of 'prevent' events. In the dialog, use the buttons above the list of prevent events to add new events and to modify, copy, and delete a selected event.
  •  
    Stop Event <X> - Event Code
    The Stop Event stops the Solo Event rule. To specify the event code, click Browse, select the event in the Select Event dialog which displays all of the events loaded into Event Configuration, and click OK.
Copy Variable Values from Contributing Events to the Rule Output Event
When you use event rules, the event that is generated is sometimes generated only after multiple contributing events occur or after certain conditions are met.
By default, a rule output event has no event variables. However, you can specify optional processing. The values of the event variables in the events that contribute to the rule processing can be copied to the output event. You can then use event variable discriminators to specify event processing behaviors for the rule output event that is based on those values. And because the values of event variables in events that generate alarms are also stored in those alarms, you can use event discriminators to specify alarm processing (generation or clearing of alarms) based on the values. For an example of this usage, see Event Variable Copying and Event Discriminators.
You can specify that all of the event variables in a contributing event are copied to the rule output event, or you can specify variable IDs. Use the event variable IDs that are mapped (in the AlertMap file) to the OIDs of the variable bindings that are sent with the trap. 
To copy only specific variable binding values from a contributing event to the rule output event, enter a comma-separated list of the IDs or ranges of IDs. This configuration is shown in the following image:
 spec--ec--copyeventvariables--SCR 
Use the first text box to specify the contributing event variables that you want to copy. Use the second text box to specify the event variables in the output event where the values are copied. The first ID in the “source” text box is copied into the first ID in the “target” text box, and so on.
You can copy the value of one source variable into a target variable that has a different ID. For example, the preceding image specifies that source variable 1 is copied into target variable 1, source variable 2 is copied into target variable 3, and source variables 3, 4, and 5 are copied into target variables 4, 5, and 6, respectively.
Modifying Event Rules
You can modify event rules.
 
To modify event rules
 
  1. In the Navigation panel, select the event that activates (triggers) the event rule.
  2. In the Details panel, click the Event Rules tab.
    The list of event rules for the selected event appears.
  3. Select the event rule to modify, and click the edit icon SPEC--editbutton_ICO.
  4. Modify the configuration of the event rule as required.
  5. Click OK.
Delete Event Rules
You can delete event rules.
 
To delete event rules
 
  1. In the Navigation panel, select the event that activates (triggers) the event rule.
  2. In the Details panel, click the Event Rules tab.
    The list of event rules for the selected event appears.
  3. Select the event rule to delete, and click the delete icon SPEC--clearalarms_deleteusers_ICO.
  4. Click OK to confirm the deletion.