How to take an ILOM snapshot on an Oracle Sun Fire Server
search cancel

How to take an ILOM snapshot on an Oracle Sun Fire Server

book

Article ID: 42859

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

When an Oracle Sun Fire server/hardware appliance suffers from a firmware or hardware issue, we must get Oracle involved for part replacement or guidance on installing any firmware patches or updates as needed. Nearly all the cases to Oracle require a customer's ILOM snapshot from the appliance.

Environment

All supported versions of the API Gateway

Resolution

How to take an ILOM snapshot

Oracle maintains documentation regarding the ILOM Snapshot process. This documentation for the ILOM Snapshot process is included inside of a larger document for Maintenance & Diagnostics of the ILOM 3.x which may also be very beneficial to review.

Please click one of the following links for the most current ILOM Snapshot processes, depending on whether you have access to the ILOM web interface or the command-line utility (CLI).

For quick reference, the steps are also noted below.

Using the Oracle ILOM snapshot utility (web)

Before You Begin:

  • To collect SP data using the Service Snapshot utility, you need the Admin (a) role enabled.

To override the BIOS boot device setting from Oracle ILOM by using the Host Control features, perform the following steps:

  1. Log in to the Oracle ILOM SP web interface.
  2. Click Maintenance --> Snapshot. The Service Snapshot Utility page appears.
  3. Select the data set: Normal, FRUID, Full, or Custom.
  • Normal : Specifies that Oracle ILOM, operating system, and hardware information is to be collected.
  • FRUID : Available as of Oracle ILOM 3.0.3, specifies that information about FRUs currently configured on your server in addition to the data collected by the Normal set option is to be collected.
  • Full : Specifies that all data is to be collected. Selecting Full might reset the system.
  • Custom : Allows you to choose one or more of the following data sets:
    • Oracle ILOM data
    • Hardware data
    • Basic OS data
    • Diagnostic data
    • FRUID data
  1. If you want to collect only log files from the data set, click the Enabled check box.
  2. If you want to encrypt the output file, click the Enabled check box.
  3. Select one of the following methods to transfer the output file:
  • Browser
  • SFTP
  • FTP
  1. Click Run. A Save As dialog box appears.
  2. In the dialog box, specify the directory to which to save the file and the file name.
  3. Click OK. The file is saved to the specified directory.

Using the Oracle ILOM snapshot utility (CLI)

Before You Begin:

  • To collect SP data using the Service Snapshot utility, you need the Admin (a) role enabled.

To run the Service Snapshot utility, perform the following steps:

  1. Log in to the Oracle ILOM CLI server SP.
  2. Type the following commands where <data> and <URI> are one of the options noted below the commands:
  • set /SP/diag/snapshot dataset=<data>
  • set /SP/diag/snapshot dump_uri=<URI>
CLI command options
Variable Option Description
data
normal Specifies that Oracle ILOM, operating system, and hardware information is to be collected.
FRUID Available as of Oracle ILOM 3.0.3, requests Oracle ILOM to collect information about FRUs currently configured on your server in addition to the data collected by the normal option.
full Specifies that all data is to be collected (?full? collection). Note - Using this option might reset the running host.
* normal-logonly Specifies that only log files are to be collected.
* fruid-logonly
* full-logonly
URI Any valid target directory location Specifies the URI of the target directory. The URI format is as follows:
protocol://username:password@host/directory
where protocol can be one of these transfer methods: SFTP or FTP.
For example, to store the snapshot information in the directory named data on the host, define the URI as follows:
ftp://joe: mypasswd@host_ip_address /data
The directory data is relative to the user?s login, so the directory would probably be /home/joe/data .