Pillar Axiom 600 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 

In this Document

Goal

Solution

References

Applies to:

Goal

This document explains how to interpret the information about date and time contained in the log bundle filename, and how to select and send log bundles to Oracle using either the GUI or the CLI.

Solution

When an array has an internal condition, one or several 'event' logset files are created and stored on the Pilot. The information contained in each logset is confined to the date&time range of that file. For complex issues it can be necessary for Oracle support to require the logs for a specific date&time or all logsets generated on a given day.

The date&time range is identified within the logset name. For example:

A001365BFM-150221003140-150221004307-BRICK_CRU_STATE_CHANGE-e-02-02.tar

Indicates that the logset is for array SN A001365BFM and has a date&time range FROM 150221003140 (2015/02/21 00:31:40) TO 150221004307 (2015/02/21 00:43:07)


The GUI or the CLI can be used to both list and download or send a logset to Oracle.


Note: Call-Home is the most effective and automated method of sending event based log collections to Oracle support. If the array is configured for callhome, most or all of the event logset should automatically be sent to Oracle support.

For Support engineer.

If you have a manual logset taken 'after' the event it should be possible to identify all the previous logsets stored on the pilot.

The customer can then be directed to upload those date&time specific files to Oracle.

Within the scanlog'd logset,
grep PackageName log/axiomsrvr-csi.log*

There may be many. Sometimes its worth reducing with a further date based grep.  For example searching for logsets produced on 150313
grep PackageName log/axiomsrvr-csi.log* | grep "\-150313"

Then you can request the customer upload these for review.

Using the GUI with the release R5

1: If you already have an open SR, skip to step 2. Otherwise, create a new SR in My Oracle Support (MOS) and describe the technical issue (refer to Document 1544005.1 My Oracle Support 'How-to' Series: How to validate your access and create, manage, and escalate Hardware, Software or Cloud Service Requests).

If the array is configured for callhome, the event logs should already be with Oracle support. Collecting an additional 'manual logset' would be recommended next step per Document 1906876.1 Pillar Axiom: How to Collect a System Information Log and Transfer it to Oracle

2: Log into the Axiom GUI.

3: Select the "Support" tab at the top of the screen, then select "System Logs".

4: Select the desired logset filename based on the date&time information in the filename. You can use the shift or control keys when making multiple selections.

5: Select "Actions -> Send to -> Callhome   or Download (to your workstation) as appropriate.
Alternatively , right click after highlighting the required files for the same outcome.

6: A summary screen is displayed , selected 'OK'

Note: The logsets will not be attached/associated with a MOS SR if sent to callhome but Oracle technical support will be able to use them. To associate the files with the MOS SR, the download method to local workstation is required then upload the files to MOS in a browser.



Using the CLI with the release R5 (example)

1: Login as administrator or an administrator level account.

2: List the available logsets (there may be many).

 

3: send the logset to callhome. (repeat for each required logset)

Alternatively, download the logset to your workstation for uploading to MOS. (repeat for each required logset)

References

This solution has no attachment