SANsurfer iSCSI HBA Manager Application

This software license applies only to QLogic customers.
QLogic Corporation.
All rights reserved.

Table of Contents

OS Support
  5.1. Hardware Requirements
  5.2. Software Requirements
Installing SANsurfer iSCSI HBA Manager
Executing SANsurfer iSCSI HBA Manager
Removing SANsurfer iSCSI HBA Manager
Known Issues and WorkArounds
Contacting QLogic

1. OS Support

This application has been tested with the following operating systems:

  • Windows 2000/SP4+(IA32)
  • Windows XP, 2003 (IA32,x64)
  • SunOS (Sparc) 5.8, 5.9, 5.10
  • SunOS (IA32,x64) 5.10
  • Red Hat Linux AS 2.1(IA32), 3.0, 4.0(IA32,x64)
  • SuSE Linux ES 8.0(IA32), 9.0(IA32,x64,PPC)

2. Features

QLogic SANsurfer iSCSI HBA Manager supports QLogic QLA4xxx adapters. Some of the features include:

  • Asset Management
    • Connect to and disconnect from local and remote hosts
    • Provides information about connected hosts and attached iSCSI HBAs
    • Provides information about iSCSI devices and LUNs connected to the iSCSI HBAs
    • Ability to save Host configuration to text file
    • Ability to save and load detailed Host configuration of iSCSI HBAs and connected targets to and from a binary file for later offline viewing
    • Ability to display Vender Private Data
  • Configuration Management
    • Configure QLogic iSCSI HBAs network and iSCSI parameters
    • Configure connections to iSCSI targets
    • View target negotiated parameters
    • Ability to specify ASCII or hex CHAP secrets
    • Display LUN properties
    • Update firmware
    • Update BIOS, FCODE, and ROM
    • Update driver (Windows only)
    • Restore factory defaults
  • Statistics
    • Statistics available for each iSCSI HBA
    • Statistics collected automatically or on request
    • Statistics can be reset at any time
  • Advanced Diagnostics
    • Ping a target to verify connectivity between HBA port and a target
    • View ARP cache
    • View Connection Error Log, which displays the 100 latest entries of connection errors or connection status entries for target connections to the HBA port
    • Ability to perform read/write buffer tests
    • Ability to perform internal loop back tests
    • Ability to perform external loop back tests
  • HBA State and Target Session Connection State Monitoring
    • Monitors QLogic iSCSI HBAs and displays their state
    • Monitors target connections and displays their state

3. Components

SANsurfer iSCSI HBA Manager includes the SANblade Manager iX, which consists of the following components:

  • SANsurfer iSCSI HBA Manager GUI/Client Application: The GUI application provides the necessary user interface configuring QLogic QLA4xxx adapters. The application doesn't need to be installed on the system where the QLogic QLA4xxx adapter resides. A single client can manage several server agents.
  • iQAgent Server: This server allows clients to connect remotely to configure adapters. The application must be installed on the system where the QLogic QLA4xxx adapter resides.
  • iSDMAPI: QLogic proprietary application programming interface to manage QLA4xxx adapters.

4. Configuration

SANblade Manager iX is designed to be configured as client server application.

5. Requirements

See the following topics for product requirements:

5.1 Hardware Requirements

  • QLogic QLA4xxx iSCSI adapter
  • Single or Multi-processor Server or Workstation
  • Pentium II class 300 MHz, 64 MB RAM, minimum 20 MB disk space
  • 1024 x 768 Video Display settings
  • TCP/IP Ethernet Adapter (to access to remote agents)

5.2 Software Requirements

  • Windows 2000 (SP4+) server, Advanced Server, Professional, or 2003 Server
  • SunOS 5.8, 5.9, 5.10 (requires graphical user interface [GUI] such as XWindows)
  • Red Hat Linux Advanced server 2.1, 3.0, 4.0 (requires GUI such as XWindows)
  • Linux SuSE Enterprise 8.0 and 9.0 (requires GUI such as XWindows)
  • Linux Red Hat x64 systems require that 32-bit X11 libraries are installed, for example:
    xorg-x11-libs-<version>.i386.EL rpm
  • QLogic QL4xxx Drivers
  • HTML Web browser installed with Set Browser Location specified to use help feature
  • TCP/IP

6. Installing SANsurfer iSCSI HBA Manager

SANsurfer iSCSI HBA Manager is included in an Install Anywhere installation executable file (Windows: iSCSI_SANsurfer_*_windows.exe and Linux/SunOS: iSCSI_SANsurfer_*.bin). Use this file to install the available components. Be sure to remove any existing installations before installing.

To install the SANsurfer iSCSI HBA Manager Application, follow the steps for your operating system.

On Windows:

  1. In Windows Explorer, double-click iSCSI_SANsurfer_*_windows.exe to execute the SANsurfer iSCSI HBA Manager installation file.
  2. Follow the on-screen instructions.
  3. Continue the installation until complete.

On Linux and SunOS:

  1. Execute the SANsurfer iSCSI HBA Manager installation file (iSCSI_SANsurfer_*.bin).
  2. Follow the on-screen instructions.
  3. Continue the installation until complete.

7. Executing SANsurfer iSCSI HBA Manager

On Windows:

  1. Select Start->Programs->QLogic Management Suite->SANsurfer. The SANsurfer iSCSI HBA Manager application displays its main dialog box.
  2. Select the Connect toolbar icon or menu item to connect to the local machine or a remote machine.

On Linux/SunOS:

  1. Execute the SANsurfer iSCSI HBA Manager executable file:
    /usr/loca/bin/SANsurfer (default) or
    /opt/QLogic_Corporation/SANsurfer/ SANsurfer
  2. Select the Connect toolbar icon or menu item to connect to the local machine or a remote machine.

NOTE: The default security password is config. You should change this password in the Host Security Tab for additional protection. The security password is required to save any configuration changes and access CHAP configuration.

8. Removing SANsurfer iSCSI HBA Manager

On Windows:

1. Run the Control Panel from Start->Settings->Add/Remove Programs.

2. Select SANsurfer iSCSI HBA Manager.

3. Follow the on-screen instructions to remove the installed components.

On Linux/SunOS, execute the SANsurferUninstaller executable file:
/usr/local/bin/SANsurferUninstaller (default) or

9. Application Notes

  • For application instructions and options, review the application help by starting within the application or use a web browser to view the help file located in folders shown for your operating system:
    Windows: <install directory>\help\iscsi_help\iSCSI_Help.htm
    Unix: <install directory>/help/iscsi_help/iSCSI_Help.htm
  • If the Target Settings Tab shows targets discovered by configuring a SendTargets host, you must delete the SendTargets host when deleting any of the targets to prevent them from reappearing on the next reset of the adapter.
  • The default SANsurfer HBA Manager operation password is config.
    NOTE: Make sure to change this password after installation to ensure security.
  • Changing the password requires the following for each platform:
    Username specified must be for an account in the administrator group on the system in which the agent is running.
    Username specified must be an account in both the adm and root groups on the system in which the agent is running. Currently there is a separate password setting in Non-Agent mode and Agent mode per host. Therefore changing one will not change the other.

  • Before you can change the current SANblade Manager password, you need the shadow password option installed on your Linux machine. For example, on a Red Hat Linux, follow these 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 the pwconv command to convert the passwords to shadow password format.
  • The administrator account password must not be blank when changing the SANblade Manager application password. This is a Windows 2003 security restriction.
  • The SANsurfer iSCSI HBA Manager application prevents you from connecting to the same host more than once (to save system resources and address policy issues). This requires that all host IP address MUST resolve to a host name to allow the connection to complete.
  • If your system doesn't use DNS, you must edit the local host file on the system running the SANsurfer HBA Manager GUI and add the host name to IP mapping manually, as defined for your operating system:
  • When running SANsurfer iSCSI HBA Manager and connecting to a remote Linux machine, you must modify the /etc/hosts files on the two machines 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. For example:

    Initial: localhost
    Modified: localhost

  • With Linux a new secure portmapper has been included. Add the statement portmap : ALL to the /etc/hosts.allow file for remote communication to work properly between GUIs and agents.
  • On systems where DNS is not set up 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 may not update the client GUI properly.
  • The iSCSI HBAs and iSCSI HBA Driver must be correctly installed before the SANsurfer iSCSI HBA Manager agent (iqlremote) can start successfully.
  • 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.
  • 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, you must disconnect the HBA network link must prior to updating to the fixed IP address, and then reconnect it after reconfiguring the HBA with the new IP Address.
  • 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. Configure the HBA Global Keep Alive Time Out under HBA Options tab, Firmware sub tab, under the Configured Firmware Values.
  • In rare cases, you must issue a manual Refresh more than once to update the display correctly. If a prompt appears, requesting you to disconnect from host, select no and continue to wait for refresh to complete.
  • 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 the bind flag set.
  • TCP Timestamp should not be disabled in the firmware options to preserve full functionality.
  • Under Linux x64 (EM64T, AMD64), the IA32 SANsurfer Pro installer requires installation of the IA32 X11 libs and either the Compatible Architecture Development or the Compatible Architecture Support package. The IA32 X11 libs are included in the xorg-x11-libs-<version>.i386.EL rpm. If the libs are missing the following exception will be displayed:
    java.lang.UnsatisfiedLinkError: /tmp/install.dir.4191/Linux/resource/jre/lib/ i386/xawt/ cannot open shared object file: No such file or directory
    For example, an installation package with its dependent packages for the 2nd Red Hat install disk includes:
  • On the Solaris 10 operating system, you must set the web browser location for online help needs to a location of an installed web browser. The default for Solaris 10 is: /usr/sfw/bin/mozilla\
  • Silent installation is available with all default options. The following is specific to the SANsurfer iSCSI HBA Manager standalone package only (does not apply to the combined packages with FC and Switch components). The command is as follows:
    <package> -i silent -DSILENT_INSTALL_SET="<ID>"
    <package> is the installation package file
    <ID> is the installation set to install:
    GUI and Windows Agent: SB_iX_WI_A
    GUI and Linux Agent: SB_iX_LX_A
    GUI and Solaris Agent: SB_iX_SL_A
    GUI only: SB_iX
    Windows Agent: SBiX_WINA
    Linux Agent: SBiX_LINA
    Solaris Agent: SBiX_SOLA

    NOTE: If you misspell the ID or install set or if the installer program cannot find the install set, they system installs the default install set, which includes the GUI and the OS agent.
  • In rare cases, when you restart the system in agent mode, the agent starts when the driver is still loading and not all HBAs are discovered initially. Refreshing the host on the GUI discovers any HBAs that the driver has presented since the initial startup of the agent or since the last refresh.
  • SANsurfer iSCSI HBA Manager does not support agent mode on systems that use the iSCSI HBA NDIS (network) driver. For these systems, install only the GUI portion of SANsurfer iSCSI HBA Manager on the local system, not the agent. In this configuration, the GUI communicates directly with the locally installed iSCSI HBAs without an agent.
  • The iSNS and SLP automatic target discovery process is a continuous discovery process. Targets do not always appear immediately after the features are enabled. Refreshing the HBAs on the host checks for currently discovered targets or, if wait 30 seconds to 2 minutes, the SANsurfer iSCSI HBA Manager GUI automatically detects newly discovered targets and requests a refresh to update the information displayed in the GUI.
  • To update the MTU/Jumbo Frames parameter on a 405x HBA and if the iSCSI HBA NDIS (network) driver is installed, you must configure the MTU/Jumbo Frames parameter with SANsurfer iSCSI HBA Manager. Reboot the system to ensure that the operating system uses the updated MTU value for the network and NDIS drivers as well as the iSCSI driver.

10. Known Issues and WorkArounds

Issue / Problem Description Work Around / Solution

When changing the HBA port subnet for systems using DHCP, you need to reset the DHCP option on GUI for to acquire new lease for a QLA4xxx. If the DHCP Server has a long lease time, the system does not acquire a new lease in a reasonable amount of time.

Reset the 40xx using the HBA level Options tab by clicking the Reset button. This resets the board and issues a new IP address.

The File Choosers in SANsurfer HBA Manager at times do not respond to double-click traversal of the file system.

Select the directory and click the Open button to the right to navigate the directory or open a specific file.

If multiple targets with an active session are deleted or a session is lost (for example by entering invalid CHAP entries), saving the HBA settings may fail.

Delete or log out from targets one at a time if this occurs.

Disabling a Send Targets entry in the HBA Target Settings tab, generates invalid error messages: RPC Error or Save Target Settings Failed when performing a save. The save operation actually completes successfully.

To eliminate these invalid error messages, re-enable the Send Targets entry and save it or remove the Send Targets entry.
The value displayed for MACEncodingErrorCount in the Statistics tab is not correct.  

Non-Agent Mode: In rare cases, if you select Refresh at a specific time during HostPolling, the display bar continues to show a refresh.

Disconnect and Re-connect to the host.

During installation, if you select the option to remove a prior installed version of the application, then at times the uninstaller windows hide behind the current installation windows.


When deleting and saving dynamic targets (ID >= 64) to persistent targets (ID < 64) without saving target settings between delete and save operations, any dynamic targets saved before deleting persistent target IDs will not persist across OS reboots.

Under Target Settings tab, select Save Settings first to save all dynamic targets to persistent, then delete targets, and do a final Save Settings.

In rare cases when SANsurfer iSCSI agent is busy, a Possible Loss of Communication popup window appears.

When prompted whether you want to disconnect, select no.
In non-agent mode, SANsurfer iSCSI may frequently request a refresh when none are needed. Change the host polling interval to a larger value or turn off by setting it to zero.
With a selective restore of firmware defaults (even when network parameters are not selected for default), the SLP DA address resets to  

11. Contacting QLogic

Please visit QLogic's website ( On this site you will find product information, our latest drivers, and links for technical assistance if needed.

Go to Top

©Copyright 2005. All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are

trademarks or registered trademarks of their respective owners.