VSM - VCF card failed with FSC 3659 followed by FSC 38BE Warm Boot Recovery

Asset ID:	1-72-1310923.1
Update Date:	2011-04-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1310923.1 : VSM - VCF card failed with FSC 3659 followed by FSC 38BE Warm Boot Recovery

Applies to:

Sun StorageTek VSM System - Version: 4 to 5C - Release: 4.0 to 5.0
IBM z/OS on System z

Symptoms

VTSS subsystem fenced a VCF card which failed with FSC3659. It also took a FSC38BE warm boot and fenced the control region.

Cause

The VCF card failed by creating control bus errors. These control bus errors resulted in the fencing of the control region.

The VCF card could then not be GFR'd because the control region was down.

The control region GFR attempts failed because every attempt encountered another control bus error and the fencing of additional FRUs.

Solution

This problem can be addressed via the following special procedure:

If the actions below fail at any point then stop and escalate this problem to support.
Identify the suspect interface card (VCF card). This will likely be the first interface card that the subsystem fenced.
Without using GFR, unplug the suspect VCF card.
Recover the control region by performing a GFR NO-replace of the IPX card in the control region that was taken down.
Verify that there are no FRUs fenced other than the suspect VCF card.
GFR (replace with new from stock during the GFR) the suspect VCF card.
Verify the subsystem is now 100% with no fenced FRUs.
Have the customer vary any CHPIDs or RTDs that previously went offline back online and verify that the subsystem works normally for the customer.

Attachments

This solution has no attachment