Go to main content

Oracle® x86 Servers Diagnostics and Troubleshooting Guide

Exit Print View

Updated: January 2020

Take a System Snapshot (CLI)


Caution  -  The purpose of the Oracle ILOM Service Snapshot utility is to collect data for use by Oracle Service personnel to diagnose system problems. Customers must not run this utility unless requested to do so by Oracle Service personnel.

  1. Obtain permission from Oracle Service personnel before performing this procedure.
  2. Verity that you have Admin(a) role privileges, which are required to collect SP data using the Snapshot utility.
  3. Issue the following command to specify what kind of data the Snapshot utility should collect:

    -> set /SP/diag/snapshot dataset=value

    Where value can be one of the following:

    • normal – Collect information about Oracle ILOM, host operating system, and hardware configuration.

    • normal-logonly – Collect only log files.

    • FRUID – Collect information about installed FRUs, in addition to the data set collected for Normal.

    • fruid-logonly – Collect only log files.

    • full – Collect the maximum information about the server. This option could cause the server to reset.

    • full-logonly – Collect only log files.

  4. To specify whether the Snapshot data should be encrypted, type:

    -> set /SP/diag/snapshot encrypt_output=[true|false]

    Note -  When the encrypt_output property is set to true, you must type an encryption password at the prompt in order to start the data collection. Later, you must type an encryption password at the prompt in order to decrypt the output file. To decrypt an encrypted output file, see Decrypt an Encrypted Snapshot File.
  5. To start the data collection, type set /SP/diag/snapshot dump_uri=protocol://username:password@host/directory.

    The transfer protocol can be sftp, ftp, ftps, tftp, http, or https.

    For example, to store the Snapshot information through FTP in a directory named data on the host, type set /SP/diag/snapshot dump_uri=ftp://username:mypasswd@host-ip-address/data.

    Note -  The directory is relative to the user's login; therefore, in the previous example, the full path to data is probably /home/username/data.