Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2045430.1
Update Date:2015-09-04
Keywords:

Solution Type  Technical Instruction Sure

Solution  2045430.1 :   How to Collect ESM Logs from CSM 200 Trays  


Related Items
  • Sun Storage 6580 Array
  •  
  • Sun Storage 6780 Array
  •  
  • Sun Storage 6140 Array
  •  
  • Sun Storage 6180 Array
  •  
  • Sun Storage 6540 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
  •  




In this Document
Goal
Solution
 Collect ESM logs through serial port:
 
Collect ESM logs through CAM "service" command:


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Need serial access
Created from <SR 3-10946562071>

Applies to:

Sun Storage 6580 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6540 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6140 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6180 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6780 Array - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

This article describes the procedure to manually capture the ESM shell data through ESM serial port and through Common Array Manager CLI.
CAM supportdata donot collect ESM statecapture by default.

Solution

Collect ESM logs through serial port:

Perform the following steps:

  1.    Use a terminal program to break in to the ESM shell.
  2.    Connect to the ESM in the tray (The connection type might vary depending on the type of tray.)
  3.    Enable capture of the output on the terminal program
  4.    The COM Settings are 38400 BAUD, 8 Bits, No Parity, no Flow control.
  5.    Once you break into the shell, you should see output similar to that shown below.
  6.    Enable the ESM output
  7.    Run the commands listed below to get data that you need to troubleshoot the information
  8.    Repeat the process on the other ESM in the enclosure

The most important options for troubleshooting are going to be [d] Dump State Capture Buffer (large), [e] Enclosure Status and Health, and [p] Dump Configuration Profile.

  • ESM State Capture              -- This will provide information similar to a DQ trace, with the history of the ESM logging these files. This is helpful to determine if a particular ESM is getting errors or rebooting more than the others.
  • Enclosure Status and Health -- Gives an overview of the overall enclosure health from the ESM perspective.
  • Dump Configuration Profile  -- Provides detailed information on the firmware versions of the drives, ESM, power supplies, and so on.

   

_________________________________________________________________
                         ESM Applications Menu
_________________________________________________________________

         [a] Enable or Disable (toggle) Audible Alarm
         [c] Command Line Interface (Advanced users only!)
         [d] Dump State Capture Buffer (large)
         [e] Enclosure Status and Health
         [p] Dump Configuration Profile
         [r] Reboot the ESM (Temporary drive path loss will occur!)
         [s] List Seven Segment Display Codes
         [t] Set Enclosure Tray ID


Collect ESM logs through CAM "service" command:

Syntax :

/opt/SUNWsefms/bin/service -d <array-name or IP> -c save -t iom -p <path to save the file> -o <file-name>

Eg :

service -d ST6540 -c save -t iom -p /tmp -o state.zip

Executing the save command on ST6540
Created iomtray10slot1.txt
Created iomtray10slot2.txt
Created iomtray0slot1.txt
Created iomtray0slot2.txt
Zipping to /tmp/state.zip
Completion Status: Success

  

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback