If the system does not send the AutoSupport message, you can determine whether that is because AutoSupport cannot generate the message or cannot deliver the message.

Steps

Check delivery status of the messages by using the system node autosupport history show command.

Read the status.

This status Means

This status	Means
initializing	The collection process is starting. If this state is temporary, all is well. However, if this state persists, there is an issue.
collection-failed	AutoSupport cannot create the AutoSupport content in the spool directory. You can view what AutoSupport is trying to collect by entering the `system node autosupport history show -detail` command.
collection-in-progress	AutoSupport is collecting AutoSupport content. You can view what AutoSupport is collecting by entering the `system node autosupport manifest show` command.
queued	AutoSupport messages are queued for delivery, but not yet delivered.
transmitting	AutoSupport is currently delivering messages.
sent-successful	AutoSupport successfully delivered the message. You can find out where AutoSupport delivered the message by entering the `system node autosupport history show -delivery` command.
ignore	AutoSupport has no destinations for the message. You can view the delivery details by entering the `system node autosupport history show -delivery` command.
re-queued	AutoSupport tried to deliver messages, but the attempt failed. As a result, AutoSupport placed the messages back in the delivery queue for another attempt. You can view the error by entering the `system node autosupport history show` command.
transmission-failed	AutoSupport failed to deliver the message the specified number of times and stopped trying to deliver the message. You can view the error by entering the `system node autosupport history show` command.

initializing

The collection process is starting. If this state is temporary, all is well. However, if this state persists, there is an issue.

collection-failed

AutoSupport cannot create the AutoSupport content in the spool directory. You can view what AutoSupport is trying to collect by entering the system node autosupport history show -detail command.

collection-in-progress

AutoSupport is collecting AutoSupport content. You can view what AutoSupport is collecting by entering the system node autosupport manifest show command.

queued

AutoSupport messages are queued for delivery, but not yet delivered.

transmitting

AutoSupport is currently delivering messages.

sent-successful

AutoSupport successfully delivered the message. You can find out where AutoSupport delivered the message by entering the system node autosupport history show -delivery command.

ignore

AutoSupport has no destinations for the message. You can view the delivery details by entering the system node autosupport history show -delivery command.

re-queued

AutoSupport tried to deliver messages, but the attempt failed. As a result, AutoSupport placed the messages back in the delivery queue for another attempt. You can view the error by entering the system node autosupport history show command.

transmission-failed

AutoSupport failed to deliver the message the specified number of times and stopped trying to deliver the message. You can view the error by entering the system node autosupport history show command.

Perform one of the following actions:

For this status	Do this
initializing or collection-failed	Contact Fujitsu Support because AutoSupport cannot generate the message.
ignore, re-queued, or transmission failed	Check that destinations are correctly configured for SMTP, HTTP, or HTTPS because AutoSupport cannot deliver the message.

For this status

Do this

initializing or collection-failed

Contact Fujitsu Support because AutoSupport cannot generate the message.

ignore, re-queued, or transmission failed

Check that destinations are correctly configured for SMTP, HTTP, or HTTPS because AutoSupport cannot deliver the message.