![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 1369953.1 : How to Collect a 99x0 Auto Dump:ATR:1369953.1:3
In this Document
Oracle Confidential (INTERNAL). Do not distribute to customers. Applies to:Sun Storage 9985 System - Version Not Applicable to Not Applicable [Release N/A]Sun Storage 9985V System - Version Not Applicable to Not Applicable [Release N/A] Sun Storage 9990 System - Version Not Applicable to Not Applicable [Release N/A] Sun Storage 9990V System - Version Not Applicable to Not Applicable [Release N/A] Sun Storage 9910 System - Version Not Applicable to Not Applicable [Release N/A] Information in this document applies to any platform. DISPATCH INSTRUCTIONS - WHAT SKILLS DOES THE ENGINEER NEED: SE9910/9960/9970/9980/990/9985/9990V/9985V Overview and training on SVP operations. TIME ESTIMATE: 120 minutes Dependent on size of configuration TASK COMPLEXITY: 3 FIELD ENGINEER INSTRUCTIONS: PROBLEM OVERVIEW An autodump needs to be collected to diagnose a difficult hardware issue or investigate performance relate issues which has not been solved by following the action codes listed in the applicable SIM or TROUBLESHOOTING SECTION of the Maintenance Manuals. WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? Current state as the autodump is transparent to the host WHAT ACTION DOES THE ENGINEER NEED TO TAKE: In order to ensure the SVP has all the current information from the SE99x0 subsystem, you will need to refresh the SVP with the data from the subsystem. In order to achieve this, from the SVP main menu open the "Maintenance" window by selecting the Maintenance Icon on the SVP screen. When the SVP opens the "Maintenance" window it will refresh all the data on the SVP. Once the "Maintenance" window is open and the array subsystem frame view screen is visible, it can then be closed. On the main SVP window, select the "Auto Dump" Icon. * If the subsystem is in an unknown state, generate an Auto Dump type 'Normal' * For a performance related issue, generate an Auto Dump type 'Detail' * If the subsystem is reporting errors, but is in a known state, generate an Auto Dump type 'Rapid' * If you are unsure of which type of Auto Dump to generate, always generate an Auto Dump type 'Normal' Click OK The Auto Dump file will now be generated. This process can take several minutes to complete. When finished a message will appear indicating the dump has completed. Click OK. The Auto Dump "file" has now been generated. For the SE9910, SE9960, SE9970, and SE9980 units the Auto Dump file (HDD) will be stored in the following location / filename on the SVP. - C:\DKC200\tmp\HDCP.LZH For a SE9985 or SE9990 unit the Auto Dump file will be stored in the following location / filename on the SVP. - C:\DKC200\tmp\HDCP.TGZ PLEASE NOTE: A common mistake is that the file(s) named DUMP.LZH or DUMP.TGZ which are file(s) available in the C:\DKC200\DUMP folder are presented for analysis. These "dump.xxx" file(s) are NOT the Auto Dump file(s) required. The file required is ALWAYS the HDCP.xxx file located in the C:\DKC200\tmp\ folder. Returning The Auto Dump File. The Auto Dump file should be uploaded to the Cores2 infrastructure or attached to the service request. The Auto Dump file can be anywhere from 20 to 200 MB in size, therefore cannot be directly copied onto a floppy disk. Please ensure that you have a USB flash drive available to copy the Auto Dump from the SVP or some other type of network based file transfer utility. OBTAIN CUSTOMER ACCEPTANCE - WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE: No action required PARTS NOTE: N/A ADDITIONAL COMMENTS: The Auto Dump function is described in the SVP SECTION of the Maintenance Manual, which can be found on the microcode CD. GoalAutodump collection FixCollect an auto dump and provide it to L2 for analysis. Attachments This solution has no attachment |
||||||||||||||
|