Monitor REC_METADATA_OFFLINE (50)

IBMStorageSubsystem.FailureID_0050_Monitor (UnitMonitor)

Monitor Description for (50)

Knowledge Base article:

Missing Mirror Repository Logical Drive

What Caused the Problem?

The storage subsystem has detected that the drives associated with the mirror repository logical drive are no longer accessible. This can be the result of removing all drives associated with an array or a loss of power to one or more drive enclosures. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Recovery Steps

1

If...

Then...

The drives associated with the mirror repository logical drive have been removed

Re-insert the drives back into the drive enclosure. When all drives have been inserted, wait until they are displayed in the Subsystem Management Window.

Go to step 5.

The drives associated with the mirror repository logical drive have not been removed

Go to step 2.

2

If...

Then...

The drive enclosure associated with the missing repository logical drive does not have power

Check to see that the drive enclosure's power supplies are properly connected to an operating power source, have the power switch in the on position, and have an optimal status (a separate recovery guru entry will be displayed for a power supply that is not optimal).

Go to step 3.

The drive enclosure associated with the missing mirror repository logical drive has power

Go to step 4.

3

If...

Then...

You find a power supply problem

Correct the problem and go to step 5.

You cannot find a power or power supply problem

Contact your technical support representative.

4

You will need to re-create the mirror repository logical drives using the following steps:

a

Create a record of all existing mirror relationships associated with this storage subsystem by selecting the

Storage Subsystem >> View >> Profile

menu option, selecting the Logical Drives tab, and selecting the Save As button.

b

Delete all mirroring relationships by highlighting any mirrored logical drive that is not listed as missing, selecting the

Logical Drive >> Remote Logical Drive Mirroring >> Remove Mirror Relationship

menu option, and selecting the Select All button.

c

Deactivate the Remote Logical Drive Mirroring feature by selecting the

Storage Subsystem >> Remote Logical Drive Mirroring >> Deactivate

menu option.

d

Activate the Remote Logical Drive Mirroring feature by selecting the

Storage Subsystem >> Remote Logical Drive Mirroring >> Activate

menu option.

e

Use the information saved in step a to re-establish your previous mirror configuration by highlighting the previously designated primary logical drives from the appropriate Subsystem Management Window and selecting the

Logical Drive >> Remote Logical Drive Mirroring >> Create

menu option.

Go to step 5.

5

Click the

Recheck

button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

Element properties:

TargetIBMStorageSubsystem.StorageSubsystem
Parent MonitorIBMStorageSubsystem.StorageSubsystemAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeIBMStorageSubsystem.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_METADATA_OFFLINE
Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="IBMStorageSubsystem.FailureID_0050_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="IBMStorageSubsystem.REC_METADATA_OFFLINE_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="IBMStorageSubsystem.StateId279D7D5F3B73593E12A70473DCFB05DC" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="IBMStorageSubsystem.StateId92AE45F2E7D0EDA0D053DBC4C39EA320" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>50</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>