StorageTek Virtual Storage Manager System 6 (VSM6)
 

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

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: KB to document workflow on common ASR
Created from <SR 3-15294811977>

Applies to:

Symptoms

 ASR received:

Product Type: STORAGETEK VSM6
Summary:Cluster has restarted a node after a failure.

Fault event description:The VSM6 VTSS has successfully restarted after a failure condition was encountered.
Jul 08 15:49:49 vsmpriv1_vsm vsmpriv1_vsm: [ID 100004] CRITICAL: FSC00100004_CL
Jul 08 15:49:49 vsmpriv1_vsm vsmpriv1_vsm: [ID 100004] CRITICAL: FSC00100004_CLUSTER_FINISHED_STARTING_NODE:
This FSC indicates that Cluster has finished bringing the node online after a reboot. This will be sent out in an ASR.

No other ASR's or errors reported.

Changes

Maintenance; such as code updates, DR testing, relocation, or power rerouting.

Cause

There is scheduled maintenance and/or code upgrades on the VSM in question.

Solution

If there is a confirmed known maintenance item being performed, the /opt/vsm/bin/asr_sfb_cfg.pl ASR_DISABLE script is usually run to prevent ASR requests from opening.  However, on final reboot an ASR may be initiated that reports the system is now online.

Confirmation can also be obtained by checking additional SR's for the same serial number and/or:

-Contacting the customer

-Contacting the assigned FE

-Checking the SFB for a new version of the VSM code being booted in the Major Events Log.

Note - It is possible for the node to panic and generate the same symptoms FSC00100004 in this solution without any other errors reported.  It is advisable to check the SFB var_adm_messages.txt log to verify there was no kernel panics.  Review the linked document.

References

This solution has no attachment