Table of Contents
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 only allows 5 email address. 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 Network Appliance 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 then a direct connection to the location specified in autosupport.support.url is made and the autosupport is transmitted to Network Appliance via HTTP POST.
The autosupport mechanism is triggered automatically once a week by the kernel to send information before backing up the messages file. It can also be invoked to send the information through the options command. Autosupport mail will also be sent on events that require corrective action from the System Administrator. And finally, the autosupport mechanism will send notification upon system reboot from disk.
To accommodate multiple delivery methods and destinations and to preserve time dependent values, the outgoing autosupport messages are now 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 40 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.
If on, includes CIFS session and share information in autosupport messages. If off, those sections are omitted. The default is off.
The type of content that the autosupport notification should contain. Allowable values are complete and minimal. The default value is complete. The minimal option allows the delivery of a "sanitized" and smaller version of the autosupport, at the cost of reduced support from Network Appliance. Please contact Network Appliance if you feel you need to use the minimal option. The complete option is the traditional (and default) form of autosupport. If this option is changed from complete to minimal then all previous and pending autosupport messages will be deleted under the assumption that complete messages should not be transmitted.
Triggers the autosupport daemon to send an autosupport notification immediately. A text word entered as the option is sent in the notification subject line and should be used to explain the reason for the notification.
Enables/disables the autosupport notification features (see na_autosupport(8)). The default is on to cause autosupport notifications to be sent. This option will override the autosupport.support.enable option.
Defines the user to be designated as the sender of the notification. The default is [email protected]. Email replies from Network Appliance will be sent to this address.
Enables/disables the NHT data autosupport to be sent to the recipients listed in the autosupport.to option. NHT data is the binary, internal log data from each disk drive, and in general, is not parsable by other than Network Appliance. There is no customer data in the NHT autosupport. The default for this option is off.
Enables/disables performance data autosupport to be sent to the recipients listed in autosupport.to. The performance autosupport contains hourly samples of system performance counters, and in general is only useful to Network Appliance. The default is off.
Defines the list of up to 5 mailhost names. Enter the host names as a comma-separated list with no spaces in between. The default is an empty list.
Defines the type of string that is used in the identification portion of the subject line when autosupport.content is set to minimal. Allowable values are systemid and hostname. The default is systemid.
Defines the list of recipients for the autosupport short note email. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list to disable short note emails.
Enables/disables the generation of the Health Trigger (NHT) data autosupport. Default is off
Enables/disables hourly sampling of system performance data, and weekly creation of a performance data autosupport. The default is on.
Number of times to try resending the mail before giving up and dropping the mail. Minimum is 5; maximum is 4294967295 ; The default is 15 .
Time in minutes to delay before trying to send the autosupport again. Minimum is 30 seconds, maximum is 1 day. Values may end with `s', `m' or `h' to indicate seconds, minutes or hours respectively, if no units are specified than input is
assumed to be in seconds. The default value is 4m.
Enables/disables the autosupport notification to Network Appliance The default is on to cause autosupport notifications to be sent directly to Network Appliance as described by the autosupport.support.transport option. This option is superceded (overridden) by the value of autosupport.enable.
Allows the setting of an http based proxy if autosupport.support.transport is https or http. The default
for this option is the empty string, implying no proxy is necessary.
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is smtp.
Allows setting the type of delivery desired for autosupport notifications that are destined for Network Appliance. Allowed values are https, http (for direct web based posting) or smtp (for traditional email). The default value is https. Note that http and https may (depending on local network configuration) require that the autosupport.support.proxy option be set correctly. Also smtp requires that autosupport.mailhosts be configured correctly before autosupport delivery can be successful.
This option is read only; it shows where autosupport notifications to Network Appliance are sent if autosupport.support.transport is https or http.
Enables autosupport throttling (see na_autosupport(8)). When too many autosupports are sent in too short a time, additional messages of the same type will be dropped. Valid values for this option are on or off. The default value for this option is on.
Defines the list of recipients for the autosupport email notification. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. The default is an empty list. Note that it is no longer necessary to use the standard Network Appliance autosupport email address in this field to direct autosupport messages to Network Appliance. Please use autosupport.support.enable instead.
Defines the list of recipients for the autosupport email notification that will receive all messages that are or will be sent to the standard Network Appliance autosupport email address. Up to 5 mail addresses are allowed. Enter the addresses as a comma-separated list with no spaces in between. To disable, clear this list. The default is an empty list.
Generation date and timestamp
SNMP contact name (if specified)
SNMP location (if specified)
Partner System ID (if clustered)
Partner Hostname (if clustered)
Cluster Node Status (if clustered)
Console language type
sysconfig -a output
sysconfig -c output
sysconfig -d output
System Serial Number
Software Licenses (scrambled prior to transmission)
cf monitor all output (if clustered)
ic stats performance output (if clustered with VIA)
ic stats error -v output (if clustered with VIA)
snet stats -v output (if clustered with SNET)
ifconfig -a output
ifstat -a output
vlan stat output
vif status output
nis info output
nfsstat -c output (if licensed)
cifs stat output (if licensed)
cifs sessions summary (if licensed)
cifs sessions output (if licensed and enabled)
cifs shares summary (if licensed)
cifs shares output (if licensed and enabled)
vol status -l (if cifs is licensed)
vfiler status -a output (if licensed)
df -i output
snap sched output
vol status -v output
vol status output
vol status -c output
vol scrub status -v output
sysconfig -r output
fcstat fcal_stats output
fcstat device_map output
fcstat link_stats output
ECC Memory Scrubber Statistics
ems event status output
ems log status output
perf report -t output
storage show adapter -a output
storage show hub -a output
storage show disk -a output
storage show fabric output
storage show switch output
storage show port output
EMS log file (if enabled)
Parity Inconsistancy information
BMC_EVENT: BUS ERROR
BMC_EVENT: POST ERROR
CPU FAN WARNING - [fan]
DISK_FAIL!!! - Bypassed by ESH
PARTNER DOWN, TAKEOVER IMPOSSIBLE
REBOOT (after WAFL_check)
REBOOT (after entering firmware)
REBOOT (after giveback)
REBOOT (halt command)
REBOOT (internal halt)
REBOOT (internal reboot)
REBOOT (power glitch)
REBOOT (power on)
REBOOT (reboot command)
REBOOT (watchdog reset)
USER_TRIGGERED ([user input from autosupport.doit]) LOG_INFO
[power supply failure]
[power supply] POWER_SUPPLY_DEGRADED!!!
[shelf over temperature critical]
The subject in the autosupport email messages from a filer in a cluster reads, ``Cluster notification,'' instead of ``System notification.''
The autosupport email messages from a filer in a cluster contains information about its partner, such as the partner system ID and the partner host name.
In takeover mode, if you reboot the live filer, two autosupport email messages notify the email recipients of the reboot: one is from the live filer and one is from the failed filer.
The live filer sends an autosupport email message after it finishes the takeover process.
Table of Contents