Citrix

Produktdokumentation



Ganzes Dokument herunterladen

Configuring Event and Alarm Triggers

Dec. 18, 2015

You can filter a set of events or alarms by configuring filters with specific conditions and assigning actions to the filters. When the events or alarms generated meet the filter criteria, the action associated to the filter is executed.

Event triggers enable an administrator to filter the events generated by Command Center and take actions on the filtered list of events. Alarm triggers enable an administrator to filter the alarms generated by Command Center and take actions on the filtered list of alarms. You can also set the time interval to trigger an alarm (in seconds) and priority on a list of filters. The conditions on which you can create the filters are: status, device type, severity, source, failure object, category, and message.

You can assign the following actions to event and alarm triggers:

  • Send e-mail Action: Sends an email for the events and alarms that match the filter criteria you specified.
  • Suppress Action: Suppresses or drops the events and alarms for a specific time period.
  • Run Command Action: Executes a command or a script on the Command Center server for events matching a particular filter criterion. By default, to search for the executable, Command Center looks in the paths defined in the environment variable PATH of the device operating system.
    Table 1. Parameters for Run Command Action Script
    Parameter Description

    $severity

    This parameter corresponds to the state of the event, which corresponds to the severity of the Event.

    $text

    This parameter corresponds to the "description" field of the events received.

    $message

    This parameter corresponds to the "description" field of the alarms received.

    $entity

    The failure object is the key of the Event object. This field affects how the event is processed. Appropriate processing by the trap parser ensures that the failure object reflects the exact problem as notified. This can be used for tracking down the problems quickly and to identify the objects, instead of simply reporting raw events.

    $category

    This parameter corresponds to the type of traps defined under category of the filter.

    $source

    This parameter corresponds to the source IP of the managed device.
  • Send Trap Action: Sends or forwards SNMP traps to an external trap destination. The values that you configure in Trap Forward Settings (Administration > Trap Forward Settings) are displayed by default. You can configure new values, if required.
  • Execute Task Action: Executes a built-in task or a custom task (both NetScaler and CloudBridge), for the events and alarms that match the filer criteria you specified. You can specify the below parameters as task variable values for a chosen task. During task execution, these parameters will be replaced with actual values.
    Table 2. Parameters for Execute Task Action Script
    Parameter Description

    $source

    This parameter corresponds to the source IP of the managed device.

    $failureobject

    This parameter corresponds to the entity instances or counters for which an event has been generated. It can include the counter names for all threshold-related events, entity names for all entity-related events and certificate names for all certificate-related events.

To configure event and alarm triggers

  1. On the Fault tab, in the left pane, under SNMP, click Events or Alarms.
  2. In the right pane, under Events or Alarms, click Triggers.
  3. Under Event Triggers or Alarm Triggers, click Add Filter.
  4. Under Add Filter, in Name, type a filter name. The filter name is unique and user-defined.
  5. In Status, select either Enable or Disable.
  6. In Device Type, select the type of device, such as NetScaler and CloudBridge.
  7. In Severity, select the severity level of the events for which you want to add the filter.
  8. In Devices, click the icon next to the text box to select the IP address(es) of the discovered NetScaler or WANScaler devices for which you want to define a filter.
  9. In Categories, click the icon next to the text box to select the categories of events generated by the managed devices.
  10. In Failure Objects, either type the entity instances or counters for which an event has been generated, or enter a part of the entity instance along with a wildcard character, or click the icon next to the text box to select the entity instances. Note: This list can contain counter names for all threshold-related events, entity names for all entity-related events, certificate names for certificate-related events. For threshold-related events, the instances should match the incoming traps, as described in the table.
  11. In Filter based on event description, type a message that lets you further narrow the filter to events or alarms that meet specific criteria. The message should match the incoming trap. For example, if you want to view all events that are generated when a feature or entity is enabled, type Command: enable*. And, if you want to view all events generated by a particular user for the selected category, type *User: UserName Note: If you are not sure of the format of the message to type, you can copy the format of a similar category from the Message field in the Events or Alarms pane.
  12. Under Filter Action, click Add Action.
  13. Under Filter Actions, in Action Type, select the type of action you want to associate with a filter, such as Send e-mail Action, Suppress Action, Run Command Action Send Trap Action and Execute Task Action.
    Note: Click Test Mail to check if the mail server credentials provided are accurate and if the mail server is accessible from command center server. If the connection to the mail server is successful, a test mail is sent to the specified email and the settings are saved.
  14. In Action Name, type the name of the action, and fill values for various options depending on the action type that you select, and then click OK.
Back to Top