The Host Context Agent (HCA) attempted to register an iSCSI initiator associated with a host that already has storage partition mappings. The iSCSI initiator was consequently marked inactive and can be activated through the storage management software or CLI.
The storage subsystem associated a new host port identifier with a known host. This is probably the result of a new host port identifier being physically installed into the host. However, because this host already has access to logical drives, the host port identifier has been marked inactive to prevent any unauthorized access to the logical drives.
The Recovery Guru Details area provides specific information you will need as you follow the Recovery Steps.
Important Notes
If the affected host port identifier is a physical Host Bus Adapter (i.e NOT an iSCSI Initiator), then ensure that the HBA was physically installed into the host by an authorized person. If the HBA installation was authorized, use the following Recovery Steps to activate the host port and allow it to gain access to the logical drives. If you are not aware of any authorization to install a new HBA into the host, check the host hardware and your system administrator before taking any action.
If a physical HBA was installed and had more than a single port, then each port identifier will be marked inactive.
Recovery Steps
1 | From the Subsystem Management Window (AMW), select the Mappings >> Manage Host Port Identifiers menu option. Result: The Manage Host Port Identifiers dialog is displayed. |
2 | Select the affected Host Port Identifier from the Host Port Identifier Information area. Note: The affected host port identifier is listed in the Recovery Guru Details area, and should also have an Inactive status in the Manage Host Port Identifiers dialog. |
3 | Click the Activate button. Result: The Activate Host Port Identifier dialog is displayed. |
4 | Click the Yes button. Result: The host port identifier is now active and has gained access to the logical drives associated with the host. |
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. |
| 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 |
Home<UnitMonitor ID="IBMStorageSubsystem.FailureID_0339_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_INACTIVE_INITIATOR_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.StateIdC6BAE4DF73FFF7A587455FC48A0B7F90" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="IBMStorageSubsystem.StateIdF786B0BFE549B9FFE99A4DE4AD956D28" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>339</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>