To trigger an AutoSupport message in ONTAP, the following commands are valid:

1. ::> autosupport invoke --node <nodename> --type all

What it does: This command manually triggers a complete AutoSupport message of type 'all.' This includes logs and system information from all subsystems.

How to use:

Run the command: autosupport invoke --node <nodename> --type all

Replace <nodename> with the name of the node for which you want to generate the AutoSupport message.

Why it's relevant: This is the primary method for triggering a full AutoSupport message manually. It is commonly used during troubleshooting to provide comprehensive system data to NetApp Support.

2. ::> autosupport invoke-core-upload --node <nodename>

What it does: This command is specifically used to upload core files (e.g., kernel or user space cores) from a node to NetApp Support for analysis.

How to use:

Run the command: autosupport invoke-core-upload --node <nodename>.

Replace <nodename> with the name of the node for which you want to upload core files.

Why it's relevant: If there is a system panic or other critical issue, this command ensures that core files are included in the AutoSupport message for detailed analysis.

Why Other Options Are Incorrect:

A . ::> autosupport history show-upload-details --node <nodename>:

This command displays the history of AutoSupport uploads but does not trigger a new AutoSupport.

B . ::> system node coredump upload --node <nodename>:

This command uploads coredumps directly to a support server but does not trigger an AutoSupport message.

'ONTAP 9 AutoSupport Configuration Guide' confirms autosupport invoke as a valid command to trigger AutoSupport messages.

'ONTAP CLI Reference Manual' specifies autosupport invoke-core-upload for core file uploads.