SANsurfer Application Notes
7/28/04
SANsurfer iSCSI HBA Manager
Application Notes (iSCSI HBA QLA4xxx)
1. For information on application
instructions and options make sure to
review the "SANsurfer iSCSI HBA Application
User’s Guide". The latest and updated version
of this guide is available on the QLogic web
site under resources for the QLA4010 HBA.
2. A PDF Viewer must be installed and selected
with "Set Browser Location" to use help
feature for the SANsurfer iSCSI HBA Manager
client GUI.
3. On the Target Settings Tab if targets were
discovered by having a "SendTargets" host
configured, the "SendTargets" host must be
deleted if any of the targets are deleted to
prevent them from reappearing on the next
reset of the adapter.
4. If any targets have been configured prior to
a Restore of the Factory Defaults, those
targets will need to be manually deleted, the
adapter reset and then reconfigured in order
for them to use the new defaults.
5. DHCP option on GUI may need a reset of
QLA4010 to acquire new lease. If the DHCP
Server has a long lease time then no new
lease will be acquired in a reasonable amount
of time. To resolve this issue, the user can
Reset the 4010 by typing a new or changing
existing HBA Alias Name and pressing Save
button. This will reset the board and a new
IP address will be issued.
6. For Windows 2000, Service Pack 4 or greater
must be installed on the system where the
iSCSI HBA and iSCSI agent are located in
order for QLA4xxx driver to work properly.
7. The default SANsurfer iSCSI HBA Manager
operation password is "config". Make
sure to change this password after
install to ensure security is not
compromised. In order to change the password
the following is required for each platform:
Windows: username specified must be for a
account the agent is running on and
be in the administrator group
Linux: username specified must be for a
account the agent is running on and
be in the adm or root groups
Solaris: username specified must be for a
account the agent is running on and
be in the adm or root groups
8. The SANsurfer iSCSI HBA Manager application
tries to help in not allowing the user to
connect to the same host more than once
(causes issues with policies and wasted
system resources). This adds the requirement
that all host IP address MUST resolve to
a host name to allow connection to complete.
If DNS is not used you must edit the local
host file on the system where you are running
the SANblade Manager GUI and add the host
name to IP mapping manually.
Windows:
<SystemRoot>\\system32\\drivers
\\etc\\hosts
Linux:
/etc/hosts
Solaris:
/etc/hosts
9. The File Choosers in SANsurfer HBA Manager
at times do not respond to double click
traversal of the file system. The work
around for now is select the directory and
click the Open button to the right to
traverse the directory or open a specific
file.
10. When running SANsurfer iSCSI HBA Manager and
connecting to a remote Linux
machine the /etc/hosts files on the two
machines will have to be modified to
allow async notifications from the agent
to the GUI to operate properly. To
resolve this issue, create a new entry
with the host IP address assigned to
ethx. Modify the existing entry by
moving the hostname from the localhost
line to the newly created line.
Example
Initial:
127.0.0.1 localhost runner.domain.com
Modified:
127.0.0.1 localhost
10.0.0.1 runner.domain.com
11. With Red Hat Linux Advanced Server 2.1
a new secure portmapper has been
included. Add the statement
"portmap:ALL" to the /etc/hosts.allow
file in order for remote communication
to work properly between GUIs and
agents.
12. To be able to change the current SANblade
Manager password you need the shadow
password option installed on your Linux
machine (see below steps on how to
install).
For example with Red Hat Linux the
steps to create /etc/shadow file:
1) Install shadow-utils rpm package from
<Linux CD-1>
/RedHat/RPMS/shadow-utils-20000902-4.i386.rpm
2) Go to /etc and type "pwconv" command
to convert the passwords to shadow
password format.
13. The message 'Warning: Cannot convert string
"x" to type VirtualBinding' seen on Linux
when either running the GUI or the uninstall
is a Java issue. The specified key
mapping is already defined by the window
manager. These warnings can be ignored since
they do not affect the operation of the
application.
14. The administrator account password must not
be blank when changing the SANblade Manager
application password. This is a Windows
2003 security restriction.
15. On systems where DNS is not setup properly
and where there are no entries in the system
hosts file for the hosts where SANsurfer
iSCSI HBA Manager iQAgent is installed, host
status alarms will not update the client GUI
properly.
16. Running SANsurfer Control iX and iqlremote
(SANsurfer iSCSI HBA Manager agent)
simultaneously on the same system is not
supported. But, running SANsurfer Control iX
and the SANsurfer iSCSI HBA Manager client
GUI on the same system is supported.
17. Only one operation (Save HBA, Ping, Reset
Statistics Counter, Refresh Statistics
Counter, ...) at a time can be performed in
the SANsurfer HBA iSCSI Manager Application.
18. To manage the iSCSI HBAs on a local host the
SANsurfer iSCSI HBA Manager server agent must
be installed.
19. On Windows, after the driver has been
updated. The version of the driver displayed
will not always be updated. To confirm the
version of the driver currently installed
must go to the system device manager screen
and check the current installed version.
20. The iSCSI HBAs and iSCSI HBA Driver must be
correctly installed before the SANsurfer
iSCSI HBA Manager agent (iqlremote) will
successfully start.
21. If BIOS Boot Targets have CHAP, it is
recommended that these boot targets be added
and configured first before adding other
Targets that have CHAP.
22. To delete or modify settings for BIOS Boot
Targets, the targets must first be
unconfigured as Boot Targets with
Fast!UTIL (CTRL-Q prompt during boot).
23. If a system has multiple HBAs, and BIOS is
desired, it is important to insure that ALL
HBAs have firmware that supports BIOS.
Fast!UTIL does not restrict configuration of
HBAs that do not have current firmware.
24. If multiple targets with an active session
are deleted or lose that session (for example
by entering invalid CHAP entries), saving the
HBA settings may fail. It is recommended to
delete or logout targets one at a time if
this occurs.
25. On Solaris, before using the Hot Swap feature
on the QLogic QLA4XXX adapters, the iqlremote
agent must first be stopped.
26. On Solaris, the maximum number of LUNs per
target displayed in the GUI is 128,
additional LUNs for Solaris hosts will not be
shown in the GUI.
27. If the DHCP server is unavailable, it is
recommended that the HBA be set to a fixed IP
address. On Windows, if the above process
does not work, then the HBA nework link must
first be disconnected prior to updating to
the fixed IP address, and then reconnected
after the HBA has been reconfigured with the
new IP Address.
28. The next save command after a restore factory
default save will always include HBA reset
(even if it is a target only operation).
WORKAROUND: Do a second save after the first
save for restore factory defaults if
concerned about an HBA reset for next save
command.
29. Saving a target with IP address 0.0.0.0 will
result in a message indicating RPC command
error.
30. On Solaris if connecting to more than
64 targets, then the SANsurfer iSCSI HBA
Manager agent (iqlremote) requires that
the operating system minimum stack size per
process be (16384 or 0x4000) KBytes.
31. Prior to application exit, recommend all
target modifications be saved. A prompt to
save them, if not previously saved, will be
displayed at application exit. But if only
target modifications and no HBA options have
been made, and there are several target
modifications, then in rare cases not all
target changes are saved prior to application
exit.
32. When a Send Targets entry in the
HBA Target Settings tab is disabled,
invalid error messages are displayed
("RPC Error" or "Save Target Settings
Failed") when a save operation is performed.
The save operation actually completes
successfully. WORKAROUND: These invalid error
messages can be elminated if the Send
Targets entry is re-enabled and saved or if
the Send Targets entry is removed.
33. HBAs installed on Windows systems use
a global Keep Alive Time Out per HBA.
Individual target Keep Alive Time Out
settings of targets on each HBA are
ignored. The HBA Global Keep Alive Time Out
can be configured under HBA Options tab,
Firmware sub tab, Configured Firmware Values.
34. In rare cases a Re-Fresh operation may need
to be issued more than once for the display
to be updated correctly.
35. The value displayed for MACEncodingErrorCount
in the Statistics tab is not correct.
36. Selection of multiple HBAs in SANsurfer
iSCSI HBA Manager is not currently supported.
The first HBA selected will be used for
display and all operations.
37. Targets that do not have their bind flag set
will not persist across save operations. All
Targets that you wish to persist across save
operations must have have the bind flag set.
38. In rare cases when setting SLP options the
obtain SLP DA via DHCP option will not
stick and the discover SLP DA option will be
selected instead.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.