Skip to main content
A newer release of this product is available.

system node autosupport invoke-splog

Contributors
Suggest changes
PDFs

Generate and send an AutoSupport message with collected service-processor log files

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The system node autosupport invoke-splog command sends an AutoSupport message with the Service Processor (SP) or baseboard management controller (BMC) log files from a specified node in the cluster.

Parameters

-remote-node {<nodename>|local} - Node

Use this parameter to specify the node from which Service Processor log files are to be collected.

[-log-sequence <integer>] - Log File Sequence Number

Use this parameter to specify the sequence number of the Service Processor log files to be collected. If this parameter is omitted, the latest Service Procesor log files are collected.

[-uri <text>] - Alternate Destination for This AutoSupport

Use this parameter to send the AutoSupport message to an alternate destination. Only "file," "http," and "https" protocols are supported. If this parameter is omitted, the message is sent to the all of the recipients defined by the system node autosupport modify command.

[-force <true>] - Generate and Send Even if Disabled

Use this parameter to generate and send the AutoSupport message even if AutoSupport is disabled on the node.

[-full <true>] - Full Log Collection

Use this parameter to collect full logs from the SP or BMC.

[-show-full-progress <true>] - Full Log Collection Progress Status

Use this parameter to find the status of a full log collection from a SP or BMC.

Examples

Use this command to invoke an AutoSupport message to include the Service Processor log files collected from node cluster1-02.

cluster1::> system node autosupport invoke-splog -remote-node cluster1-02
[Job 777] Job succeeded: Log files from the service processor have been
transferred to "/mroot/etc/log/sp/ondemand" on node cluster1-01, and
AutoSupport message has been triggered.

cluster1::>