8
user login on the console. The install instructions in the readme.txt file assume this. If
using Remote Desktop, the “Add Hardware” wizard manually will have to be run
manually. When it prompts for which device was recently installed, select “Ethernet
Device” from the list of devices. Installation can proceed following the instructions in
the readme file. Upon completion, the “Found New Hardware” wizard should start up
again. Otherwise it can be started manually again, this time to setup the “Network
Controller” from the list of devices. The instructions in the readme file are sufficient to
complete the installation. The “SANsurfer iSCSI HBA Manager” previously installed on
the Linux machine can be used to manage the Windows HBA as well. In this case,
during install of “SANsurfer iSCSI HBA Manager” on Windows, select only “Windows
Agent”. Regardless of where the SANsurfer client is running from, it is needed to assign
an ip address and iscsi-alias to the HBA and add the ip addresses of the router’s gigE
ports.
One strange finding is that the iscsi-alias and ip address assigned to the HBA now show
up on the router under the existing entry that was previously associated with the software
initiator. It seems that the Windows iSCSI control panel automatically disabled the
software initiator and transferred the targets and luns to the HBA. This can be rather
disconcerting because it is not immediately clear which initiator is in use. According to
the information on the router as to which ip address and iscsi-alias is logged in, it is
assumed that the HBA is being used now. The Windows iSCSI control panel now shows
the iscsi-alias, targets and luns as paths through the HBA.
