Table of Contents
This is a list of the subcommands for the AutoSupport command.
Displays a summary of the current AutoSupport destinations.
Displays and retransmits recent AutoSupport messages.
Displays AutoSupport content manifest.
Displays and modifies AutoSupport trigger configuration.
The AutoSupport mechanism will use SMTP if there are any (user configured) destination email addresses set in the autosupport.to option. If autosupport.support.enable is on, AutoSupport will also be sent to support personnel. AutoSupport messages sent to support personnel may be transmitted by SMTP, HTTP or HTTPS as specified in the autosupport.support.transport option.
If SMTP is used, then the AutoSupport mechanism contacts a mail host that is listening on the SMTP port (25) to send email. A list of up to 5 mailhosts can be specified by using the autosupport.mailhosts option, and they will be accessed in the order specified until one of them answers as a mailhost. It will then send email through the successful mailhost connection to the destination email address specified in the autosupport.to option. Note that the autosupport.to option allows only 5 email addresses. To send to more than 5 recipients, create a local alias, or distribution list, and add that as the recipient.
If autosupport.support.enable is on then a copy of the AutoSupport message is also sent to support personnel as follows:
If autosupport.support.transport is smtp then the copy of the AutoSupport is emailed to the destination specified in autosupport.support.to and the same mailhost picking algorithm is used as above.
If autosupport.support.transport is http or https then a direct connection to the location specified in autosupport.support.put_url or autosupport.support.url is made and the AutoSupport message is transmitted to support personnel by using HTTP PUT/POST. If a proxy is required to use HTTP or HTTPS, configure proxy settings with the autosupport.support.proxy option.
The AutoSupport mechanism is automatically triggered periodically by the kernel to send information. It can also be invoked on-demand by the System Administrator. AutoSupport messages will also be sent on events that require corrective action from the System Administrator or support personnel.
To accommodate multiple delivery methods and destinations and to preserve time dependent values, the outgoing AutoSupport messages are spooled in /etc/log/autosupport. AutoSupport processing will attempt to deliver all (currently undelivered) messages until the autosupport.retry.count has been reached or until subsequent AutoSupport messages "fill the spool" such that the oldest (undelivered) messages are forced to be dropped. The spool size is currently 50 messages.
The subject line of the mail sent by the AutoSupport mechanism contains a text string to identify the reason for the notification. The subject also contains a relative prioritization of the message, using syslog severity levels from DEBUG to EMERGENCY (see na_syslog.conf(5)). The messages and other information in the notification should be used to check on the problem being reported.
The setup command tries to configure AutoSupport as follows:
If a mailhost is specified, it adds an entry for mailhost to the /etc/hosts file.
Setup also queries for autosupport.from information.
The AutoSupport messages from a node in an HA pair contains information about its partner, such as the partner system ID and the partner host name.
In takeover mode, if you reboot the live node, two AutoSupport messages notify the email recipients of the reboot: one is from the live node, and one is from the failed node.
The live node sends an AutoSupport message after it finishes the takeover process.
The following examples show how to modify AutoSupport URLs when using IPv6 address literals: node-1> options autosupport.mailhost [2620:10a:4002:6004::bbbb]:25 node-1> options autosupport.support.proxy username:password@[2620:10a:4002:6004::bbbb]:8080
Table of Contents