Sun StorageTek VSM System
 
Sun StorageTek VSM4 System
 
Sun StorageTek VSM5 System
 
Sun StorageTek V2X SVA Disk System
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
 

In this Document

Goal

Fix

Oracle Confidential INTERNAL - Do not distribute to customer (OracleConfidential).
Reason: Process is for Oracle FSEs only

Applies to:

Goal

How to Perform a Manual State Save on VSM/SVA

Fix

DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE ENGINEER NEED: VSM/SVA, including DOP
- TIME ESTIMATE: 60 minutes
- TASK COMPLEXITY: 4

FIELD ENGINEER INSTRUCTIONS:
- PROBLEM OVERVIEW: A Manual State Save  needs to be performed
- WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE
RESOLUTION ACTIVITY?: The VSM/SVA can remain online
- WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
Check with the customer and verify the customer is aware a statesave of the VSM/SVA will be taken at this time.
From the LOP (local operator panel) or CSRC:
1. From the main screen (SS01) select Log in
2. From the Log in screen (SS16) enter the CSE password (default b0022222)
3. Select option F4 Subsystem Debug Menu
4. Select F5 Controller Debug
5. Select F7 State Save Controls Menu
6. Select F7 IUP/IFF Check-0 State Save
7. Wait for the subsystem to complete the statesave (approximately 4 minutes) before continuing.
8. Review machine status of the VSM/SVA to verify it restarted correctly.
9. From PS02
10 Select F6-Configuration/Drain
11 Select F5-Confuration Subsystem Menu
12 Select F10-Fru Config
13.Verify none of the pars have a fence against them.
    Use page down, page up to review all FRUs in the VSM/SVA.

From DOP/SDP:
1. Log in at the Log in screen using the CSE password
2. Select "Subsystem DeBug"
3. Select "IUP + IFF check-0 State Save"
4. Wait for the VSM/SVA to complete the statesave (approximately 4 minutes) before continuing.
5. Review machine status of the VSM/SVA to verify it restarted correctly.
6. Go to CSE Main Menu
7. Go to Configuration
8. Go to Subsystem Availability
9. Ensure all areas of the VSM/SVA are at 100%

For DOP and LOP
Contact SR owner for further instructions if files need to be uploaded

OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO
AN OPERATIONAL STATE:
VSM: Query the VSM and verify the subsystem, VTD and RTDs are online and functioning
SVA:  Display the volumes on the subsystem and vary the devices and paths back online

PARTS NOTE:

REFERENCE INFORMATION: CAUTION:  if this is a VSM5 or VSM5C, microcode is D/H02.14.xx.xx or lower and has the IFF IP feature enabled and in use, then it is possible they may experience the following issues:

1. IFF IP links maybe lost due to code bug and require resetting - Bug CR 7153871  Lost IFF IP connect after warmstart which is fixed in D02.15.20.00 with SCN 51251
2. FSC 8FEE maybe encountered on subsystems connected via the IFF IP links and induce unnecessary SIM/MIM alerts and SR's.

This solution has no attachment