VSM/SVA - Changes in MIM and SIM reporting format for a defective HDA with latest microcode

Asset ID:	1-79-1450114.1
Update Date:	2016-02-02
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1450114.1 : VSM/SVA - Changes in MIM and SIM reporting format for a defective HDA with latest microcode

Applies to:

Sun StorageTek V2X SVA Disk System - Version Not Applicable to Not Applicable [Release N/A]
Sun StorageTek VSM System - Version 4 to 5C [Release 4.0 to 5.0]
Information in this document applies to any platform.

Purpose

This document explains the differences between SVA and VSM handling of MIM and SIM reporting for a defective HDA.

Details

VTSS products manage back-end drive failures differently than SVA products with respect to SIM (Service Information Messages) and MIM (Machine Initiated Maintenance) offloads.

Differences:

VTSS microcode was changed such that with just two exceptions* drive failure SIM messages are not sent to the host console. This change was made in response to customer complaints that the subsystem was sending too many SIMs to the host console.
In the VSM product line the original drive failure will present a MIM (call home) but does not send a SIM to the host. Additionally, FSC3E01 (drive reconstruction started), FSC3E02 (drive reconstruction completed), FSC3E61 to FSC3E6F (number of spares remaining available) and FSC734X (number of broken drives within the subsystem) also do not report a SIM to the console.
FSC3E02 (drive reconstruction completed) will present a MIM (not a SIM).

*The two exceptions mentioned are:

FSC3E5F – Spare needed (meaning a drive has failed and a spare drive is needed for reconstruction)

FSC3E60 – No spares remaining (meaning all spares have been used)

PLEASE NOTE: The VTSS SIM report (SNS.DAT file) and the HIC_STAT.DIA will report that a SIM was presented, but in fact the bit to send the SIM to the customer console has been turned off for these fault codes so the customer will not be presented with the SIM. The HIC_STAT.DIA lines showing the SIMs were sent simply indicate that the SIM microcode module believes the SIM has been sent. In fact the drive failure related SIMs are not sent.

EXAMPLEs:
10/06/07 04:44:21 SIM send start - ID: 77/3E61 10/06/07 04:44:25 SIM send complete - ID: 77/3e61 10/06/07 04:44:25 SIM send start - ID: 78/3E02 10/06/07 04:44:29 SIM send complete - ID: 78/3e02
The SIM messages shown above were NOT sent to the host console.

Summary: Drive failures in the VTSS do not generate SIMs regardless of the ‘SIM Display Level’ setting in the VTSS. MIMs are sent for only the original drive failure and when drive reconstruction completes.

Attachments

This solution has no attachment