Asset ID: |
1-71-1444021.1 |
Update Date: | 2017-08-03 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1444021.1
:
How to Perform a VSM/SVA Health Check:ATR:1444021.1:4
Related Items |
- Sun StorageTek VSM System
- Sun StorageTek VSM4 System
- Sun StorageTek VSM5 System
- Sun StorageTek V2X SVA Disk System
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Process is for Oracle FSEs only
Applies to:
Sun StorageTek VSM System - Version 4 to 5C [Release 4.0 to 5.0]
Sun StorageTek V2X SVA Disk System - Version Not Applicable to Not Applicable [Release N/A]
Sun StorageTek VSM4 System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek VSM5 System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Goal
How to Perform a VSM/SVA Health Check.
Solution
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
Sun Storagetek VSM or V2X Training, including DOP.
TIME ESTIMATE: 120 minutes
TASK COMPLEXITY: 4
FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
PROBLEM OVERVIEW: VSM requires a routine health check
WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE
RESOLUTION ACTIVITY?: The system can remain online
WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:
Accessing the Detached Operators Panel (DOP)
1. Access the VSM locally.
2. Once the DOP is displayed on the screen, log into the DOP with the known password.
3. Check fru status by clicking on Configuration,then FRU. Note any fenced frus.
4. Click on the hic_stat at the bottom right of the screen.
5. At the pulldown menu, select hic_stat pause.
6. Copy any current FSC messages;check for any CK0's, RTD events, fenced FRUs
7. Click on the Main Menu button.
8. Click on Configuration.
9. Click on GFR, then CFE list and see if there are any CFEs posted (there could be CFEs for 79A5 log wraps or recovered FRU events like IUP or power-delete
as applicable
10. If there are 79A5 log wraps the logs should be offloaded using vshell and checked.
11. Select or click on Subsystem Status and verify the system is not degraded and is optimal.
12. Go back to Configuration again.
13. Click on Drive Status and verfiy no HDAs are failed or unavailable. If any are failed, have an FS task created to order and replace the part
14. Again, go back to Configuration and check the RTD status, FRU status, Interface Status, etc... Note any issues encountered and have an FS task created to
order/replace the part
Connecting to vshell from the laptop to download logs. If you need assistance with vshell, please review DOC ID 2131483.1.
1. Connect to the subsystem via vshell from your laptop.
2. Issue the vshell command lmkdir c:\SR #
3. Issue the vshell command lcd c:\SR #
4. Issue the vshell command allstate -d $
5. Wait for the vshell prompt
6. Disconnect from the subsystem
7. Zip the files in the c:\SR # directory into one
8. Attach the file created to this SR (SR #) or SPLAT
OBTAIN CUSTOMER ACCEPTANCE:
WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO
RETURN THE SYSTEM TO AN OPERATIONAL STATE: Verify the VSM has all components available and verify the customer has all channels and devices still online and fully functional.
PARTS NOTE:
REFERENCE INFORMATION:
Attachments
This solution has no attachment