Sun Storage 6580 Array
 
Sun Storage Flexline FLA200 Drive Module
 
Sun Storage 6180 Array
 
Sun Storage Flexline 280 Array
 
Sun Storage 3511 SATA Array
 
Sun Storage 2540 Array
 
Sun Storage 2540-M2 Array
 
Sun Storage 6780 Array
 
Sun Storage 2510 Array
 
Sun Storage 7410 Unified Storage System
 
Sun Storage 6140 Array
 
Sun Storage 3510 FC Array
 
Sun Storage 3120 SCSI Array
 
Sun Storage Flexline 210 Array
 
Sun Storage Flexline FLA300 Drive Module
 
Sun Storage 2530 Array
 
Sun ZFS Storage 7320
 
Sun Storage Flexline 380 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage Flexline FLC200 Drive Module
 
Sun Storage 6540 Array
 
Sun Storage 7210 Unified Storage System
 
Sun Storage 7310 Unified Storage System
 
Sun Storage Flexline 240 Array
 
Sun ZFS Storage 7120
 
Sun Storage 7110 Unified Storage System
 
Sun Storage 3320 SCSI Array
 
Sun Storage 6130 Array
 
Sun ZFS Storage 7420
 

PLA-Support>Sun Systems>DISK>Connected Services>SN-DK: ASR Configuration
 

In this Document

Goal

Solution

References

Applies to:

Goal

This document explains the Automated Diagnosis Service Request creation method. By answering some simple questions and uploading the required data using My Oracle Support, Automated Diagnosis will process the answers and data immediately after the Service Request is created. Using this method will likely result in a quicker time to resolution than "traditional" Service Request creation methods.

Automated Diagnosis relies on having access to the specific data file(s) noted below.  Uploading the exact data requested will expedite your service.  If anything else is provided, e.g. .txt or .jpg files, automation will exit, signalling that the "data provided does not match expectations".  The exact data requested provides automation with all the necessary information to automatically diagnose an issue, and if needed the part information that is required to expedite dispatch or part shipment.  Incorrect data, such as a .txt file, .jpg file, screen snapshot(s) or messages log may provide some information, but can not be used for automated diagnosis.  Only one valid bundle can be uploaded, multiple valid data bundles will cause automation to exit. 

It is recommended to upload the data during SR creation or upload the required data as soon as possible after SR creation utilizing the MOS Upload Files feature:

• Sun Storage 3000 Array series require either a se3kextr file or Explorer Data Collector output.
  
  • See Document: 1012343.1 for details on how to collect the se3kxtr data file.
  • See Document: 1312847.1 for details on how to collect an Explorer Data Collector output.
• Sun Storage 2000, 6000 and FLX arrays require a Common Array Manager  Array supportData file.
  
  • See Document: 1002514.1 for details on how to collect the Array supportData file.
  • NOTE: Uploading supportData collected with the Santricity utility will prevent automated diagnosis and cause the Service Request to be routed to an Oracle Service Engineer.
• Sun Storage 7000 NAS arrays require a Support Bundle.
  • See Document: 1019887.1 for details on how to collect and upload a Support Bundle.
  • NOTE: For 7000NAS systems running 2011.1.1.0 or newer firmware you can create a support-bundle and provide an associated Service Request number in the process. In the CLI you issue "maintenance system sendbundle SR-NUMBER" and in the Browser UI you get a pop-up asking for an SR-number when you create the bundle. For older versions of firmware: In order to use the Support Bundle for automated diagnosis you will need to monitor the support bundle creation progress and once the bundle starts uploading, abort the upload in by clicking the (x) icon to the right of the bundle name. Then use the download icon and download the Support Bundle to your workstation to have it at hand when prompted during the Service Request creation process.

Solution

Summary: The Auto-Diagnostic feature is available for a range of hardware products and known issues. To ensure the success of the auto-diagnostic feature, you are required to enter the correct physical address for the asset, answer the prompted questions and upload the files (supportData from Common Array Manager for example) as specified. Information about the particular file to upload is available in step 4 , the Related Knowledge section of the service request and is based on the array type to be serviced. 

Benefits of Using Auto-Diagnostic feature: Customers using the Auto-Diagnostic feature will experience faster mean time to diagnose and repair than customers who have elected not to take advantage of Auto-Diagnostic. By answering some simple questions and uploading the required support files using My Oracle Support your Service Request (SR) and support files will be processed immediately and in most cases a resolution and next steps will be added to the SR within minutes. In most cases no additional customer engagement will be needed. Once diagnosed the problem will be forwarded to the Oracle Support team to schedule the field service representative and or dispatch a part.

How Services Auto-Diagnostic work?
As with all SRs the serial number will be validated for entitlement and service level prior to proceeding. The Auto-Diagnostic feature analyzes submitted data against a defined problem and rules set. Based on the outcome, a resolution path is triggered. If a defective component is detected, a request will be triggered to replace the part. Alternatively the issue may be escalated to an Oracle support team for further analysis.

Requirements: The Auto-Diagnostic feature requires log files and/or additional content to be uploaded during the Service Request process. It is recommended that the Service Tools Bundle be installed on Oracle Systems and the log files be available prior to service request initiation.

Step by Step details:  The process is built into the existing hardware SR process for systems or storage for known problem types.

Step 1 - The Hardware SR must be raised against the serial number which experienced the failure.
Step 2 – As there is no additional interaction with the support team, it is critical that the system address be validated and entered in the SR. Take time to Change the Address if needed. Please note the address must be the shipping address that the part will need to be shipped to and the contact should be the person who will receive the replacement part.
Step 3 – Select the Problem Category and Sub-Category if available that best describes the type of issue your system is experiencing. As the service develops additional problem categories and sub-categories will be added for additional known issues.
Step 4 – displays this document and information about the particular file to upload.
Step 5 - Upload the requested support files. These are based on the selection of the Problem Category at Step 3.
   
NOTE: Make absolutely sure sure that the correct product name, severity and serial-number as well as correct shipping address and contact person is provided during Service Request Creation.

NOTE: The Auto-Diagnostic feature requires the support file to be uploaded. If you do not have the files ready to upload, it is recommended that you save the Service Request at this stage and gather the files. Either open the saved draft SR or continue with the SR process once you have the required files.  Although it is recommended you wait to open the Service Request until you have the diagnostic data, you may create the Service Request without diagnostic data.  If you do open the Service request without the diagnostic data and do not upload the requested files within 30 minutes of the creation date, then the auto-diagnostic service will not start and you will experience delays in service .

NOTE: Unless absolutely needed, do not manually update the Service Request during the process. Unnecessary updates may cause the automated diagnosis to be aborted and get the Service Request sent to an Oracle Service Engineer. Examples of unnecessary updates: Stating that the required file has been uploaded. Asking for part arrival times(This is better handled by calling your local Oracle Support number and through the menu system request to be connected to the Field Dispatch Team which is responsible for parts orders and Field Service arrangements.) or requesting the SR to be closed or cancelled(This you can do yourself by requesting closure or cancellation in the My Oracle Support portal).  Example of a necessary update is when the proposed solution or received part did not resolve the issue, the Service Request will then need to be sent to an Oracle Support Engineer for further analysis. Uploading diagnostic data after a Service Request is created is not considered to be a manual update.

Figure 1.

References

This solution has no attachment