Monitor Description for (105)
What Caused the Problem?
The host switch card in one of the controllers is not functioning properly. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.
Important Notes
If it is determined in this procedure that the host switch card has failed, you must replace the controller canister containing the faulty switch card.
Recovery Steps
1 | Select the View Event Log option to determine the initial cause of the problem. The host switch card either:
Note: Event 2844 indicates a problem that could be temporary or intermittent. Therefore, it could recover on its own. However, it is best to use the SAN Switch Management application described in step 2 to obtain more details. | ||||||
2 | To further diagnose and possibly fix the problem, start the separate SAN Switch Management application for the host switch card. Note: Make sure that the SAN Switch Management application is connected to the IP address of the host switch card associated with the affected controller and storage subsystem.
| ||||||
3 | Place the affected controller offline using the following steps. The affected controller is listed in the Details area.
| ||||||
4 | Select Recheck to rerun the Recovery Guru. An Offline Controller problem should be reported in the Summary area. Follow that procedure to remove and replace the controller and then go to step 5. | ||||||
5 | Select Recheck 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. |
Target | IBMStorageSubsystem.StorageSubsystem | ||
Parent Monitor | IBMStorageSubsystem.StorageSubsystemAvailability | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | IBMStorageSubsystem.FailureUnitMonitorType | ||
Remotable | True | ||
Accessibility | Internal | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | Machine generated entity |
<UnitMonitor ID="IBMStorageSubsystem.FailureID_0105_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_HOST_BOARD_FAULT_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.StateId7B0996D051F17BCC99AFE9086E6849FE" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="IBMStorageSubsystem.StateId869D21EA3B8C6594C0AB935585D97DBC" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>105</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>