Pillar Axiom 300 Storage System
 
Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

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

In this Document

Goal

Solution

References

Applies to:

Goal

The intent of this document is to drive you through the procedure to collect logs from your system and either send them automatically or attach them manually to a new or existing Service Request (SR).

This document includes different solutions depending on your system release and whether you want to use the GUI (Graphical User Interface) or CLI (Command Line):

• Using the Graphical User Interface (GUI) with the releases R1-R4.
• Using the Command Lines (CLI) with the releases R1-R4.
• Using the Graphical User Interface (GUI) with the release R5.
• Using the Command Lines (CLI) with the release R5.

Solution

Using the GUI with the releases R1-R4

1. Open the Axiom GUI and go to support. Click on Collect System Information in the left navigation column and again in the pull down menu.
   
   
   
   
   
2. Select "Debugs Logs", "Event Logs" and "Statistics". Select also "Send to configured call-home server immediately after collection" if it is enabled. Then click on "Options".
   
   
   
   
   
3. Select all components and "All logs from each selected component" unless advised differently by the support representative.
   
   
   
   
4. Click on Ok twice. You can follow the collection process by clicking on the background running tasks icon .
5. If the call-home server is not enabled or if you need to manually transfer the logs to Oracle, please continue with the steps below, otherwise you can stop here.
6. Go to support. Click on Collect System Information in the left navigation column and select "Download System Information to Client" in the pull down menu.
   
   
   
   
7. Follow the instructions in <Document 1547088.2> How to Upload Files to Oracle Support to transfer the logs to Oracle.

Using the CLI with the releases R1-R4

To collect logs please follow below steps:

1. The following command will collect all logs and send them to call-home server automatically. If your system cannot send logs to callhome server you should use "SendOff=false" then follow the steps 2 and 3.
   
   
   pdscli.exe submit -u administrator -p pillar -H xx.xx.xx.xx PerformCollectSystemInformation CollectTraceLogParameters.IncludeAllHardwareComponents=true SendOff=[true|false] SystemInformationType=DebugLogs
   
   Example:
   
   
   pdscli.exe submit -u administrator -p pillar -H xx.xx.xx.xx PerformCollectSystemInformation CollectTraceLogParameters.IncludeAllHardwareComponents=true SendOff=true SystemInformationType=DebugLogs
   
     Header
       ProtocolVersion:   0.1
       SessionKey:        731115c1789b177244dffdd4a6a66cf5
       Time:              2013-11-28T07:07:21-05:00
       ClientData:        pdscli.exe
       RequestStatus:     Succeeded
     Error List
     PerformCollectSystemInformationResponse
       TaskID:            ID82b1c810-d21d-b211-8d51-000e0c6d92eb
       TaskFQN:           /PerformCollectSystemInformationTask_17111
   
   
   
2. If your system cannot send logs to callhome server due to some reason, you should manually download logs to your workstation and then upload to Oracle SR.
   
   
   1. Obtain the name of the log file you generated:
      
      
      pdscli.exe submit -u administrator -p <password> -H <Axiom Public IP address> GetSystemInformationFileDetails
      
      
      Example:
      
      
      pdscli.exe submit -u administrator -p pillar -H xx.xx.xx.xx GetSystemInformationFileDetails
      
        Header
          ProtocolVersion:                    0.1
          SessionKey:                         eb082955d71e34f142f96ea9f9995df5
          Time:                               2013-11-28T07:17:08-05:00
          ClientData:                         pdscli.exe
          RequestStatus:                      Succeeded
        Error List
        GetSystemInformationFileDetailsResponse
          CallHomeFileDetails
            Status:                           Available
            Type:                             Manual
            CallHomeFile:                     CH19.tar
            CreationDate:                     2013-11-28T07:05:46-05:00
            SystemInformationSize:            1.4G
            TraceLogDetails
              IncludeOnlyLatestLogs:          false
              IncludeInMemoryLogs:            true
              IncludeBackupLogs:              true
              IncludeAllHardwareComponents:   true
              IncludePilotLogs:               true
              IncludeSANHostLogs:             true
              SlammerList
              BrickList
            CallHomeMatrixDetails
              Format:                         030100-011100
              Version:                        1
              LastUpload:                     2013-09-23T02:54:51-07:00
            SystemInformationType[1]:         DebugLogs
            SystemInformationType[2]:         HardwareInventory
            SystemInformationType[3]:         SoftwareInventory
            SystemInformationType[4]:         ManagementConfiguration
            SystemInformationType[5]:         SystemTopology
            SystemInformationType[6]:         FileServers
            SystemInformationType[7]:         VolumeGroups
            SystemInformationType[8]:         SANInventory
            SystemInformationType[9]:         PDSFS
      
      
      
   2. Now we know name of the file, you can download the log file to your workstation.
      
      
      pdscli.exe submit -u administrator  -p <password> -H <Axiom Public IP address> PerformDownloadSystemInformationFile SystemInformationFile=<CallHome File Name>
      
      Example:
      
      
      pdscli.exe submit -u administrator  -p pillar -H xx.xx.xx.xx PerformDownloadSystemInformationFile SystemInformationFile=CH19.tar
      
        Header
          ProtocolVersion:   0.1
          SessionKey:        28cd809e42c0ac158a35ed1e5e2880d9
          Time:              2013-11-28T07:47:55-05:00
          ClientData:        pdscli.exe
          RequestStatus:     Succeeded
        Error List
        PerformDownloadSystemInformationFileResponse
          FileContents:      &@BINa05864;
          TaskID:            ID820f014d-d21d-b211-8d5b-000e0c6d92eb
          TaskFQN:           /PerformDownloadSystemInformationFileTask_17425
      
      
      The result details give you the name of the file downloaded to your workstation. In this example it is BINa05864. It will be landed to directory that you have executed the pdscli command.
      You can find more details in the R4 CLI Reference Guide.
      
      
      
3. Follow the instructions in <Document 1547088.2> How to Upload Files to Oracle Support to transfer the logs to Oracle.

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> Discover how to use My Oracle Support - Create and Update Service Requests). Note in the Request that you will be creating manual logs and sending them to the call-home Server.
2. Log into the Axiom GUI.
3. Select the "Support" tab at the top of the screen, then select "System Logs".
   
   
   
   
4. Select "Actions -> Create".  You can also right-click in the logs area of the screen and select "Create".
   
   
   
   
5. Select the desired options using the image below as a guide, including SAN Hosts for host Axiom Path Manager log collection if this issue is related to interaction with SAN Hosts.
   
   
   It is recommended to select all the components unless advised differently by the support representative.
    
   
   
6. Select "Send to Call-Home server".
7. Enter the SR number in the "Notes" field. The SR number must be the first entry in this field, with white space between it and any other notes.  For detailed notes regarding the log set, please enter them in the MOS SR.
   
   
   
   
   
   Older R5.x releases have a "Collection Reason" field (see below), located at the top of the log collection screen. If your GUI has a "Collection Reason" field, enter the SR Number in that field.
   
   
   
   
   
   
8. Then press OK to start the log collection.
9. Select OK on the confirmation screen to confirm the collection.
   
   
   
   
   
10. The Axiom will collect the log set, and automatically transfer the log set to the Call-Home Server. As the log set is received, it will be automatically linked to the MOS Service Request number that was entered in the "Notes" field and notify the SR owner. If for any reasons you need to manually transfer the log set to Oracle, please follow the instructions in <Document 1547088.2> How to Upload Files to Oracle Support.

Using the CLI with the release R5

1. Log into axiomcli:
   
   
   axiomcli login -u <username> -p <password> -axiom <axiom IP>
   
   
   Example:
   
   
   axiomcli login -u administrator -p myadminpassword -axiom xx.xx.xx.xx
   
   
   
2. Collect the system log:
   
   
   • Without collecting logs from SAN hosts:
     
     
     axiomcli system_log -collect -all -sendToCallHome -collectionReason <Oracle SR number>
      
     
     Where:
     
     -all: Requests the collection of all system information.
     -sendToCallHome: Directs the system information and logs to be sent to the Call‐Home server as soon as the collection operation completes.
     -collectionReason: Specifies the reason for performing the log collection. By entering the Oracle SR number, you allow the My Oracle System to automatically attach these new logs to the existing SR.
     
     
     
     Note: If your Axiom is not connected through callhome, you need to remove the option "-sendToCallHome" and then move to step 3. Otherwise you can stop here.
      
     
     
   • With the collection of logs from SAN hosts:
     
     
     axiomcli system_log -collect -all -sanhost <sanhost‐id‐or‐fqn [, sanhost‐id‐or‐fqn]> -sendToCallHome -collectionReason <Oracle SR number>
      
     
     You can include up to 10 SAN hosts. For the latest information about the CLIs, please refer to Pillar Axiom CLI Reference Guide, Release 5.3.
      
     
     
     Note: If your Axiom is not connected through callhome, you need to remove the option "-sendToCallHome" and then move to step 3. Otherwise you can stop here.
      
     
     
3. If your system cannot send logs to callhome server due to some reason, you should manually download logs to your workstation and then upload to Oracle SR:
   
   
   1. Obtain the name of the log file you generated:
      
      
      axiomcli system_log -list
       
      
      Example:
      axiomcli system_log -list

      ...
      ...
      /myAxiomSerialNumber-140709073922-140709075138-MANUAL_COLLECTION-m-01-01.tar
      /myAxiomSerialNumber-140912082205-140913082202-PRIMARY_PERIODIC_COLLECTION-p-02-02.tar
      /myAxiomSerialNumber-150226081859-150304085133-SECONDARY_PERIODIC_COLLECTION-p-02-02.tar
      /myAxiomSerialNumber-150304085150-150305081942-PRIMARY_PERIODIC_COLLECTION-p-02-02.tar
      /myAxiomSerialNumber-141220110121-141220110654-PCP_EVT_FOUND_PILOT_CORE_FILE-e-02-02.tar
      /myAxiomSerialNumber-160103195313-160121041537-BRICK_CRU_STATE_CHANGE-e-02-02.tar
      /myAxiomSerialNumber-140102081940-140105082101-PRIMARY_PERIODIC_COLLECTION-p-02-02.tar
      /myAxiomSerialNumber-150212081943-150218085050-SECONDARY_PERIODIC_COLLECTION-p-02-02.tar
      /myAxiomSerialNumber-140625104800-140627215620-MANUAL_COLLECTION-m-01-01.tar
      /myAxiomSerialNumber-140521085102-140521090619-MANUAL_COLLECTION-m-01-01.tar
      /myAxiomSerialNumber-150408085150-150409082010-PRIMARY_PERIODIC_COLLECTION-p-02-02.tar

        
      
      
   2. Download the log bundle:
      
      
      axiomcli system_log -download -logBundle <logbundle> -file <filename>
        
      
      Example:
      
      
      axiomcli system_log -download -logBundle /myAxiomSerialNumber-150408085150-150409082010-PRIMARY_PERIODIC_COLLECTION-p-02-02.tar -file myAxiomSerialNumber-150408085150-150409082010-PRIMARY_PERIODIC_COLLECTION-p-02-02.tar
       
      
      
   3. Follow the instructions in <Document 1547088.2> How to Upload Files to Oracle Support to transfer the logs to Oracle.

References

This solution has no attachment