Table of ContentsView in Frames

How event-triggered AutoSupport messages work

AutoSupport creates event-triggered AutoSupport messages when the EMS processes a trigger event. An event-triggered AutoSupport message alerts recipients of problems that require corrective action, and messages contain only information that is relevant to the problem. You can customize what content to include and who receives the messages.

AutoSupport uses the following process to create and send event-triggered AutoSupport messages:

  1. When the EMS processes a trigger event, EMS sends AutoSupport a request.
    Note: A trigger event is an EMS event with an AutoSupport destination and a name that begins with a callhome. prefix.
  2. AutoSupport creates an event-triggered AutoSupport message.

    AutoSupport collects basic and troubleshooting information from subsystems that are associated with the trigger to create a message that only includes information that is relevant to the trigger event.

    A default set of subsystems are associated with each trigger. However, you can choose to associate additional subsystems with a trigger by using the autosupport trigger modify command.

  3. AutoSupport sends the event-triggered AutoSupport message to the recipients defined by the options, options autosupport.noteto, options, and options commands.

    You can enable and disable delivery of AutoSupport messages for specific triggers by using the autosupport trigger modify command with the -to and -noteto parameters.

Example of data sent for a specific event

The storage shelf PSU failed EMS event triggers a message that contains basic data from the Mandatory, Log Files, Storage, RAID, HA, Platform, and Networking subsystems and troubleshooting data from the Mandatory, Log Files, and Storage subsystems.

You decide that you want to include data about NFS in any AutoSupport messages sent in response to a future storage shelf PSU failed event. You enter the following command to enable troubleshooting-level data for NFS for the event:

system> autosupport trigger modify -autosupport-message -troubleshooting-additional nfs
Note: The callhome. prefix is omitted from the storage shelf PSU failed event when you use the autosupport trigger commands.