Sun ZFS Storage 7420
 
Sun Storage 7110 Unified Storage System
 
Oracle ZFS Storage ZS3-2
 
Sun Storage 7210 Unified Storage System
 
Oracle ZFS Storage ZS4-4
 
Sun Storage 7410 Unified Storage System
 
Sun Storage 7310 Unified Storage System
 
Sun ZFS Storage 7120
 
Oracle ZFS Storage ZS3-4
 
Sun ZFS Storage 7320
 
Oracle ZFS Storage Appliance Racked System ZS4-4
 
Oracle ZFS Storage ZS3-BA
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
 
_Old GCS Categories>Sun Microsystems>Storage - Disk>Unified Storage
 

SNMP traps reporting events FMD-8000-4M & FMD-8000-6U can trigger alerts on third party monitoring software.

In this Document

Symptoms

Changes

Cause

Solution

Applies to:

Symptoms

SNMP traps received by third party monitoring agents with the following event types -

FMD-8000-4M +
FMD-8000-6U +

Please note the format of these events may be different depending on the trap and the monitoring software.

Changes

Hardware replacements that occurred within 30 days of the first fault event on the hardware.

Cause

FMD will continue to track this fault event for 30 days from the initial fault event even after the hardware has been replaced.

If the hardware were to be reintroduced to the system during this 30 day window, the active problem would show up again.

After 30 days, fmd will flush the persistent state for this hardware resource.

Solution

If you receive the FMA event codes above without any other corresponding FMA faults and the uuid's match for both FMD-8000-4M & FMD-8000-6U events please check the following from the BUI:

1. Look for any current 'Active Problems'

a) If there are no 'Active Problems' listed continue to step 2.

b) If there are 'Active Problems' listed and a Service Request (SR) has not already been raised with Oracle Support, then you should raise a new SR to have these investigated.

2. If confirmed there are no 'Active Problems', then check

for a hardware failure event that occurred 30 days before the FMD-8000-4M / FMD-8000-6U SNMP events.

If there is an event within 30 days before the listed SNMP trap, that has an 'EVENT ID' matching that from the SNMP traps, then confirm that the hardware has been replaced inside the 30 day window from the original fault by:

Also check that all hardware currently reports as healthy.

If so the FMD-8000-4M / FMD-8000-6U events can be safely ignored.

These events in this case are the results of fmd flushing the persistent state of this hardware device and the events themselves are acknowledgments that the hardware is no longer present in the system (as it was replaced) so the events are being marked repaired and removed from fmd.

No further action is required from the user if this is the case.

This solution has no attachment