Sun StorageTek VSM System
 
Sun StorageTek VSM4 System
 
Sun StorageTek VSM5 System
 

PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM
 

In this Document

Symptoms

Cause

Solution

Applies to:

Symptoms

--The VSM reported an FSC7596 through ASR.

--The VSM reported a SIM msg SLS6659I as a result of an FSC7596 (sense bytes 22 and 23)

      Example:
      SLS6659I VTSS VTSS01 SIM:0010100000008FE0115000039E002E1041030E1A0000 7596 05104201F100 3A0C

      The SLS6659I SIM error has a string of 32 sense bytes (00-31). Sense bytes 22 and 23 contain the fault that triggered the SIM.
      In the case of an FSC7596 only, sense bytes 30 and 31 (the last 4 digits) will indicate the fault code that triggered the FSC 7596. 

      Note: the Fault code that triggered the FSC7596 is in sense bytes 30 and 31. In this case it is 3A0C.

                A fault code 3A0C indicates that a Support Engineer triggered a manual statesave for diagnostic purposes. 

Cause

FSC7596 indicates the box completed a full box warm boot.

A warmboot is the VSM attempt to logically recover from what it perceives to be a failure situation. The condition could be internal to the VSM or an event external that the VSM detected and determined that it should reset itself.

A warmboot is a microcode initiated recovery mechanism.  A manual statesave can be initiated by a Support Engineer to force a recovery action in certain situations. 

In some cases the VSM could first fence hardware that it believes could be at fault. It may then automatically force a warmboot in order to run diagnostics on the control regions.  If it successfully tests and recovers, it will unfence the hardware. If not, the hardware will stay fenced and service will be required.

Solution

 If an ASR event occurred to report the FSC7596, Automation will check the recovery status of the warmboot.
--If the FSC7596 recovered successfully, no further action is required and the SR will be closed.

A check0/warmboot that completes and recovers all Unit Processors (IUP) successfully will show all eight IUPs (IUP0-7) with a return status of OK.  Anything other than OK is an indication that that IUP did not recover and is still halted.  And IPX card (IPX0-IPX3) will likely be fenced.

FIML: IUP 0,1 645 OK 0 640 OK 0
FIML: IUP 2,3 645 OK 0 641 OK 0
FIML: IUP 4,5 645 OK 0 642 OK 0
FIML: IUP 6,7 645 OK 0 643 OK 0

--If the FSC7596 did not recover successfully, a task will be opened to the Field Engineer to resolve the failure. Typically this will require replacing a hardware component.

If the FSC7596 was detected by the customer due to a SIM message, it will be necessary to open a support ticket at Oracle Support to have the files reviewed to determine recovery status.

Note: If the VSM is not at current microcode (D/H02.21.01.00), it is recommended to schedule a code upgrade to this level of code.

This solution has no attachment