HP LeftHand SAN Solutions Support Document - Service Notes - VSA 7.0 for VMware ESX

33
An Extra Microsoft iSCSI Session Is Created In The Console After Rebooting
The Host (5023)
Scenario
An extra iSCSI session is created in the Console after rebooting the host for
the volume which is mounted with “Automatically restore this connection
when the system boots” selected.
Explanation
This is a Microsoft issue in which different session IDs (iSCSI ISIDs) are used
for the same hostvolume pair, depending on how the session was established.
After an ungraceful host shutdown, you might see duplicate iSCSI sessions in
the Console, one with a Status of Failed and one a Status of Connected.
Workaround
Log off the automatically logged on persistent session and manually log back
on to get rid of the spurious session.
Microsoft iSCSI Initiator Stops With Error (5552)
Scenario
In rare cases, the Microsoft iSCSI Initiator version 2.02 and 2.03 may stop
after a storage module reboots.
Workaround
Manually restart the Microsoft iSCSI Initiator Service.
Using 1-Way CHAP To Mount Volume In QLogic HBA Fails To Detect
Volume (5289)
Scenario
Using the Centralized Management Console, configure an Authentication
Group with a CHAP name, target secret, and initiator secret. After adding the
volume list, you then attempt to mount a volume in the QLogic HBA using the
target secret and initiator secret you set in the Authentication Group. The
volume is not detected.