HP LeftHand SAN Solutions Support Document - Application Notes - QLogic HBAs and the LeftHand SAN 20071223

If all steps have been followed correctly the QLogic iSCSI HBA should log into

the new volume. This can be verified in the SAN/iQ CMC by selecting the

volume and then the “iSCSI sessions” tab. If a session is listed with the iqn

name of the QLogic iSCSI HBA initiator(s) then it is logged into the volume

and all remaining configuration will be done from the QLogic iSCSI server. If

a session is not listed then something might be configured incorrectly in the

volume list or authentication group. Verify that the QLogic iSCSI HBA can

ping the Virtual IP address of the SAN/iQ cluster, that all network

configuration is correct, and that all iqn or CHAP Authentication Group and

Volume List information was entered correctly.

For the volume to show up a rescan of storage devices may be necessary. Select

the port of the QLogic iSCSI HBA in SANsurfer, then “refresh” in the lower

right corner of the Target Settings Tab. After the rescan is complete the new

volume should now be visible under the iSCSI adapter.

Discovering additional volumes

Without rebooting, additional volumes can be logged into and discovered by

simply performing another “refresh” in SANsurfer Target Settings tab and

enabling that target and selecting bind to persistently map upon reboot.

Ensure that additional volumes are created and allocated to the Volume List

containing the QLogic iSCSI HBA’s Authentication Group. This is performed

in the LeftHand CMC.

Trouble Shooting Volume Connectivity

If new volumes are not showing up as expected and the steps in this guide

have been followed try these trouble shooting steps

• Ping the virtual IP address from the iSCSI initiator to ensure basic

network connectivity

— The QLogic HBA has a ping utility inside the BIOS Fast!UTIL of the

HBA, the iscli utility or in the SANsurfer GUI.

• Double check all IQN names or CHAP entries. For authentication to work

correctly these must be exact. Simplifying the IQN name to something

shorter than the default can help trouble shoot