Event hardware failure messages without a unique FRU identifier may result in the replacement of the wrong FRU on a Sun StorEdge 3310 SCSI or 3510/3511 FC array.

The serial number in the event messages is always the serial number of the primary controller regardless of which CPU has the fault. As a result, the good FRU that matches the serial number may incorrectly be replaced while the bad FRU remains in the system. If an event occurs on the bad controller at the time the good controller is being replaced, a full array outage is possible.

This issue can occur on the following platforms:

SPARC Platform

• Sun StorEdge 3310 SCSI Array without patch 113722-10
• Sun StorEdge 3510 FC Array without patch 113723-10
• Sun StorEdge 3511 FC Array without patch 113724-04

Example event messages:

    [0123] #298: StorEdge Array SN#26103 Peripheral Device ALERT: CPU high
    temperature threshold exceeded ( 96.00C)

    Mon Feb 14 12:45:31 2005 [01A3] #299: StorEdge Array SN#26103 Peripheral
    Device NOTICE: CPU temperature high temperature now back to non-critical
    level ( 92.00C)

Based upon the serial number, the primary controller was replaced. The above messages are from the primary controller AFTER the replacement, indicating that the wrong FRU was replaced. Aside from the serial number, there is no identifying FRU information contained in the message.

There is no workaround. Please see the "Resolution" section below.

This issue is addressed in the following releases:

SPARC Platform

• Sun StorEdge 3310 SCSI Array with patch 113722-10 or later
• Sun StorEdge 3510 FC Array with patch 113723-10 or later
• Sun StorEdge 3511 FC Array with patch 113724-04 or later

• Updated Contributing Factors and Resolution sections

14-Jun-2005:

• Updated Contributing Factors

• Updated Contributing Factors and Resolution sections

• State: Resolved
• Updated Contributing Factors and Resolution sections

This solution has no attachment