Q Simplify SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters FS0054601-00 E Page i
Q SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice.
Q SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters SANsurfer desktop icon changed appearance. Added adapter/device enable/disable diagnostic feature. About SANblade Manager window changed. 6.1.1 6.2, 10.1.2 6.4.3 Configuration Change Alarm section default changed. 6.7 Polling Settings dialog box default changed. 6.8 Policy Settings dialog box defaults changed. 6.11 Added target persistent binding for Windows NT/2000, Red Hat Linux, and Solaris SPARC. 7.
Q SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters The NVRAM file is no longer available on QLogic web site. 11.2 Updating flash BIOS from a file now available on Red Hat Linux. 11.3 Updating the FCode now available on Solaris SPARC. 11.4 Changed name of SANsurfer service to QLogic Management Suite Java agent service. 12 Added NIC to glossary. B © 2001–2003 QLogic Corporation. All rights reserved worldwide. First Printed: March 2001 Printed in U.S.A.
Table of Contents Section 1 Introduction 1.1 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 2 System Overview 2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.3 2.3.1 2.3.1.1 2.3.1.2 2.3.2 2.3.3 2.3.4 2.3.5 2.3.6 2.3.7 2.3.8 2.4 2.4.1 2.4.1.1 2.4.1.2 2.4.1.3 2.4.1.4 2.4.2 2.4.3 2.4.3.1 2.4.3.2 2.4.4 2.5 2.5.1 2.5.1.1 2.5.1.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configurations. . . . .
SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters 2.5.2 2.5.2.1 2.5.2.2 Q Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failover of JBOD Dual-Port Writes . . . . . . . . . . . . . . . . . . . . . . . . . ConfigRequired Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section 3 SANblade Manager Overview 3.1 3.2 What is SANblade Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Q SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters SANblade Manager User’s Section 7 Setting Up Connections 7.1 7.1.1 7.1.2 7.1.3 7.1.3.1 7.1.3.2 7.1.4 Connecting to Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually Connecting to a Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auto Connecting to All Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Q SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters 7.5 7.6 7.7 7.7.1 7.7.2 7.8 7.9 7.9.1 7.9.2 7.10 7.11 Viewing and Setting a LUN Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bind Target Devices Attached to the Adapter. . . . . . . . . . . . . . . . . . . . . . Deleting Persistent Configuration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Adapter Persistent Configuration Data . . . . . . . . . . . . . . . . .
Q SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters SANblade Manager User’s 9.2.2.2.2 9.2.2.2.3 9.2.2.3 9.2.3 9.2.4 9.3 9.3.1 9.3.2 9.4 Updating Adapter Statistics Automatically . . . . . . . . . . . . . . . . . . Resetting Adapter Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Adapter Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing the Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters Appendix A Frequently Asked Questions Appendix B Glossary Appendix C Contacting QLogic Q Figures Figure 2-1 2-2 2-3 2-4 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-15 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-8 6-9 6-10 6-11 6-12 Page x Page Single-Ported Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simple Failover Configuration . . . . . . . . . . . .
Q 6-13 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-15 7-16 7-17 7-18 7-19 7-20 7-21 7-22 8-1 8-2 8-3 8-4 8-5 8-6 8-7 8-8 8-9 9-1 9-2 9-3 9-4 9-5 9-6 9-7 SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters SANblade Manager User’s Policy Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connect to Host Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SANblade Manager User’s Guide Management Application for SANblade Host Bus Adapters 9-8 9-9 9-10 9-11 9-12 9-13 9-14 9-15 9-16 9-17 9-18 10-1 10-2 10-3 10-4 10-5 11-1 11-2 11-3 11-4 11-5 11-6 12-1 12-2 12-3 Q Adapter Information Tabbed Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adapter Statistics Tabbed Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistics Sampling Rate Dialog Box . . . . . . . . . . . . . . . . . . . . . . .
Section 1 Introduction This user’s guide contains an overview of the SANsurfer application with emphasis on SANblade Manager, the part of SANsurfer that allows you to configure and manage devices in a storage area network (SAN) environment that uses QLogic Fibre Channel host bus adapters (HBAs). The contents of this user’s guide are described in the following paragraphs: ■ Section 1—Introduction. This section summarizes the contents of this user’s guide. ■ Section 2—System Overview.
Q 1 – Introduction Related Documents ■ Section 12—Troubleshooting. This section presents common troubleshooting questions and answers. It also provides the procedures for tracing SANblade Manager GUI and agent activity, if directed to do so by technical support. ■ Appendix A—Frequently Asked Questions. This appendix lists and provides the answers to frequently asked questions about SANblade Manager. ■ Appendix B—Glossary.
Section 2 System Overview 2.1 Introduction SANblade Manager is a collection of device drivers and management software for controlling, configuring, and managing devices in a storage area network (SAN) environment that uses QLogic Fibre Channel host bus adapters (HBAs). This section summarizes information from various products and contains an installation checklist. The contents of this section are summarized in the following paragraphs: ■ Section 2.1—Introduction ■ Section 2.2—Configurations.
Q 2 – System Overview Configurations Figure 2-1. Single-Ported Configuration Note that figure 2-1 simplifies hardware connections: target devices can be connected through a local loop, Fibre Channel hub, Fibre Channel switch, or any combination of those. Fibre Channel topology is useful in troubleshooting situations; however, a basic configuration requires only this basic diagram showing which hosts and HBAs are connected to which target devices.
Q 2 – System Overview Configurations In this configuration, connections marked P are preferred paths to a device, and connections marked A are alternate paths. Alternate paths to devices are typically hidden from the operating system and file system layers to keep them from being interpreted as two distinct devices. 2.2.3 SAN or Cluster Configuration Figure 2-3 shows a simple storage area network (SAN) configuration consisting of two hosts (X and Y).
Q 2 – System Overview Configurations 2.2.4 RAID Configuration and LUN Masking Figure 2-4 illustrates the interaction of a host adapter alternate with a LUN alternate in a RAID subsystem. Two hosts (X and Y) are connected to a fabric, which is simplified for this diagram. Also on the fabric is a RAID subsystem with dual controllers (left and right) containing eight LUNs. Figure 2-4. RAID Configuration and LUN Masking This is a generic example of a RAID configuration.
Q 2 – System Overview Installation Checklist ■ Both hosts X and Y can recognize both targets on both HBAs. In SANblade Manager, each target device is configured with one HBA as its preferred path and (optionally) one HBA as its alternate path. Be sure that both controllers are configured as enabled and not masked on a target level. ■ On host X, the LUN mask for both controllers is set to enable LUNs 0–3 and disable all other LUNs.
Q 2 – System Overview Installation Checklist 2.3.1.2 Required Software Collect the required software. Table 2-1 specifies QLogic software products that are required for the features you want to enable. Table 2-1.
Q 2 – System Overview Installation Checklist 2.3.3 Step 3: Install the Enhanced Driver Refer to the appropriate software installation guide (see section 1.1) and readme.txt file to install an enhanced device driver on host systems. NOTE: Some operating systems, for example, Windows NT®, come from the operating system manufacturer with a QLogic miniport device driver. This device driver is a standard driver and does not contain the extended features required to run with SANblade Manager.
Q 2 – System Overview Installation Checklist 2.3.4 Step 4: Install any RAID Filter Drivers Some RAID subsystems (including some CLARiiON, EMC, and LSI subsystems) provide redundancy by using the subsystem to provide the same LUNs through two separate controllers in the subsystem. These controllers appear as unrelated target devices to HBAs and miniport drivers.
Q 2 – System Overview Installation Checklist 2.3.6 Step 6: Install the QLdirect Failover Driver The QLdirect driver provides two main features with the enhanced miniport driver under Windows NT and Windows 2000: ■ ■ ■ Failover of a target device between two HBAs Optimization of the I/O path Improved performance and CPU usage If you are not using Windows NT or Windows 2000, or if you are not using QLdirect features, skip to section 2.3.7.
Q 2 – System Overview Configuration Parameters 2.4 Configuration Parameters 2.4.1 Windows Miniport Driver Parameters 2.4.1.1 Basic Parameters QLogic miniport drivers for Windows NT and Windows 2000 read parameters from the following registry keys, depending on the type of miniport driver: HKLM\System\CurrentControlSet\Services\ql2200 HKLM\System\CurrentControlSet\Services\ql2300 Values of parameters in these keys are found in the readme.txt file associated with the miniport driver. 2.4.1.
Q 2 – System Overview Configuration Parameters 2.4.1.4 Miniport Driver Configuration QLogic miniport drivers for Windows NT and Windows 2000 read configuration information from subkeys in the QL2200/2300 keys described in section 2.4.1.1. For each HBA that has configuration information stored in the registry, there is a key created in the QL2200/2300 key that corresponds to the HBA’s worldwide name.
Q 2 – System Overview Troubleshooting 2.5 Troubleshooting This section lists troubleshooting tools to help identify the source of a problem in hardware or software. This section also contains a list of known issues related to certain configurations. 2.5.1 Troubleshooting Tools The following sections explain how to use the Windows event log and SANblade Manager to solve hardware problems. 2.5.1.
Q 2 – System Overview Troubleshooting 2.5.1.2 SANblade Manager SANblade Manager displays target devices on an HBA, loop topology information, loop error count information, etc. SANblade Manager displays target devices on an HBA and is useful for analyzing system configurations. SANblade Manager uses a feature of the enhanced miniport driver to find and display information about devices that are not configured on the local host.
2 – System Overview Troubleshooting Q Notes 2-14 FS0054601-00 E
Section 3 SANblade Manager Overview 3.1 What is SANblade Manager? The QLogic SANblade Manager is a GUI-based application that configures and manages QLogic Fibre Channel host bus adapters ((HBAs) and attached devices within a storage area network (SAN) environment. Note the following: ■ SANblade Manager works with the Windows NT®, Windows® 2000, Red Hat Linux, Solaris SPARC®, and Novell NetWare® operating systems. Support of multiple operating systems allows control of heterogeneous environments.
Q 3 – SANblade Manager Overview Features ❑ Configure LUN path failover. See the support matrix on the SANsurfer Took Kit CD-ROM for a list of adapters that support LUN path failover. Support for additional operating systems and HBAs will be added in future versions of SANblade Manager. Persistently bind targets ❑ Replace devices ❑ Update the NVRAM and flash BIOS ■ Statistics. SANblade Manager provides statistics for each host and adapter.
Section 4 System Requirements The SANblade Manager application requires the hardware and software listed in this section for optimum performance. 4.1 Hardware Requirements The minimum hardware requirements are as follows: ■ QLogic QLA2xxx PCI to Fibre Channel adapters (see section 4.
4 – System Requirements Software Requirements Q 4.2 Software Requirements The minimum software requirements are as follows: ■ One of the following operating systems: ❑ Microsoft Windows NT 4.0 Server, Enterprise Server, or Workstation with Service Pack 6 ❑ Windows 2000 Server, Advanced Server, or Professional with SP1, SP2, or SP3 ❑ Red Hat Linux 7.2 (kernel 2.4.18-19.7.x #1), 7.3 (kernel 2.4.18-19.7.x #1), or Red Hat Advanced Server 2.1 (kernel 2.4.9-e.8) ❑ Solaris SPARC v2.6, 2.7, 2.8, or 2.
Section 5 Installing SANblade Manager Installing the SANblade Manager application consists of installing the SANblade Manager GUI, platform-specific agent, and help components, as appropriate. NOTE: Before installing SANblade Manager, read and follow the instructions in the documents listed in section 1.1, as applicable. This section discusses: ■ ■ Initial installation (see section 5.1) Uninstalling the SANsurfer application (see section 5.2) 5.
Q 5 – Installing SANblade Manager Initial Installation 5.1.1 Installation Options SANblade Manager supports both stand-alone and networked configurations. Install the software appropriate for your configuration (see table 5-1). Table 5-1. Configuration Option Installation Requirements Configuration Software Requirements Stand-alone system This system monitors QLA2xxx adapters locally.
Q 5 – Installing SANblade Manager Initial Installation 5.1.2 Installation Instructions SANsurfer installer is a self-extracting program that installs the SANblade Manager application and related software. NOTE: ■ If a previous version of SANblade Manager exists, uninstall it before proceeding (see section 5.2). ■ You cannot install the SANblade Manager agent directly on a NetWare server; you must install the agent on a Windows NT/2000 system connected to the NetWare server.
Q 5 – Installing SANblade Manager Initial Installation ❑ Click the appropriate operating system under the Drivers and Management Software heading. ❑ In the SANblade/SANsurfer row of the table, click Download. ❑ The File Download dialog box displays. Click Download. Select a directory on your system and download the file. b.
Q 5 – Installing SANblade Manager Initial Installation 3. The Choose Product Features dialog box displays. The dialog box differs, depending on whether you are installing on a Windows NT/2000, Red Hat Linux, or Solaris SPARC system. See figure 5-2 for a sample dialog box. Figure 5-2. Choose Product Features Dialog Box (Sample) SANblade Manager supports both stand-alone and network configurations.
5 – Installing SANblade Manager Initial Installation Q For Red Hat Linux systems: ❑ Select Both GUIs (Blade/Box) and Agent if you have QLA2xxx adapters and SANbox2 switches on your system that will be locally or remotely monitored from other systems on the same network. ❑ Select SANblade Manager GUI if the system will monitor QLA2xxx adapters only on remote systems on the same network. ❑ Select SANbox Manager GUI to install the switch application.
Q 5 – Installing SANblade Manager Initial Installation ❑ Select Customize to create an installation set. The Choose Product Components dialog box displays (see figure 5-3). The dialog box differs, depending on whether you are installing on a Windows NT/2000, Red Hat Linux, or Solaris SPARC system. Figure 5-3. Choose Product Components Dialog Box (Sample) Perform the following steps to create a custom set: a. In the Feature Set box, select Custom Set. b.
Q 5 – Installing SANblade Manager Initial Installation 4. The Important Information dialog box displays (see figure 5-4). Read the information, then click Next. Figure 5-4. Important Information Dialog Box You can find this information in the readme.txt file in the following locations: ❑ ❑ Windows NT/2000: Program Files\QLogic Corporation\SANsurfer Red Hat Linux/Solaris SPARC: opt/qlogic/sansufer 5. The Choose Install Folder dialog box displays (see figure 5-5). Figure 5-5.
Q 5 – Installing SANblade Manager Initial Installation Do one of the following: NOTE: ❑ For NetWare, select the drive mapped to the NetWare server (always select a location other than the default). To select the destination location displayed in the dialog box, click Next (recommended).
5 – Installing SANblade Manager Initial Installation Q Application shortcuts consist of the following: ❑ The SANsurfer icon on the desktop (if selected in step 7) ❑ QLogic Management Suite (SANblade Manager and SANblade Manager Uninstaller), which is accessible when you click the Start button and point to Programs Perform the following steps: a. Do one of the following: ❑ Click All Users Profile if you want the application shortcuts available to all users.
Q 5 – Installing SANblade Manager Initial Installation NOTE: If you select the Create Desktop Icon check box, the SANsurfer icon displays for the current user profile or all user profiles, depending upon your selection in step 6. 8. The Installing SANsurfer dialog box displays (see figure 5-8). Various screens inform you that the installation is progressing. Figure 5-8.
5 – Installing SANblade Manager Initial Installation Q 9. If you are installing NetWare, the Novell NetWare Disk Selection dialog box displays (see figure 5-9). Figure 5-9. Novell NetWare Disk Selection Dialog Box A list of the autodetected Windows NT/2000 drives mapped to NetWare server system volumes (sys:\) displays. The format for a Novell NetWare 5.
Q 5 – Installing SANblade Manager Uninstalling the SANsurfer Application 10. The Install Complete dialog box displays (see figure 5-10). Click Done. Figure 5-10. Install Complete Dialog Box 11. Customize the SANblade Manager application and set your security parameters (see section 6). 5.2 Uninstalling the SANsurfer Application Perform the following steps to uninstall the SANsurfer application (including SANblade Manager) from this system.
Q 5 – Installing SANblade Manager Uninstalling the SANsurfer Application 1. Do one of the following to start the SANsurfer Uninstaller: From a Windows NT system, do one of the following: ❑ Click the Start button, point to Programs, point to QLogic Management Suite, then click SANsurfer Uninstaller. ❑ Perform the following steps to use Add/Remove Programs: a. Click the Start button, point to Settings, and then click Control Panel. b. Double-click the Add/Remove Programs icon. c.
Q 5 – Installing SANblade Manager Uninstalling the SANsurfer Application From a Windows 2000 system, do one of the following: ❑ Click the Start button, point to Programs, point to QLogic Management Suite, and then click SANsurfer Uninstaller. ❑ Perform the following steps to use Add/Remove Programs: a. Click the Start button, point to Settings, and then click Control Panel. b. Double-click the Add/Remove Programs icon. c. The Add/Remove Programs dialog box displays (see figure 5-12).
Q 5 – Installing SANblade Manager Uninstalling the SANsurfer Application 2. The Uninstall SANsurfer—About to Uninstall dialog box displays with SANsurfer Vx.x.xx as the program to be uninstalled (see figure 5-13). Click Uninstall. Figure 5-13. Uninstall SANsurfer—About to Uninstall Dialog Box 3. The Uninstall SANsurfer—Component List dialog box lists the components to be uninstalled (see figure 5-14). Figure 5-14.
Q 5 – Installing SANblade Manager Uninstalling the SANsurfer Application A message displays informing you that the uninstaller is waiting 30 seconds for the agent to shut down. Wait while the uninstaller removes the components. 4. The Uninstall SANsurfer—Uninstall Complete dialog box informs you that the uninstall is complete (see figure 5-15). Click Quit. Figure 5-15. Uninstall SANsurfer—Uninstall Complete Dialog Box 5. If any items were not successfully uninstalled, remove them.
5 – Installing SANblade Manager Uninstalling the SANsurfer Application Q Notes 5-18 FS0054601-00 E
Section 6 Getting Started This section includes the procedures for starting the SANblade Manager GUI, exiting the SANblade Manager GUI, and customizing the application options and policies. This section discusses: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Starting the SANblade Manager GUI (see section 6.1) SANblade Manager main window (see section 6.2) Exiting the SANblade Manager GUI (see section 6.3) Getting help (see section 6.4) Setting SANblade Manager security (see section 6.
Q 6 – Getting Started Starting the SANblade Manager GUI 6.1.1 Starting SANblade Manager on Windows NT/2000 On a Windows NT/2000 system, do one of the following to start the SANsurfer application, which includes the SANblade Manager GUI. When done, the SANblade Manager main window displays (see section 6.2). ■ Double-click the SANsurfer icon on your desktop (if the icon was created during installation) (see figure 6-1).
Q 6 – Getting Started SANblade Manager Main Window 6.2 SANblade Manager Main Window The SANblade Manager main window (displays below (see figure 6-2). HBA Tree Menu Bar Toolbar Tabbed Pages Figure 6-2. SANblade Manager Main Window The window consists of the following sections: ■ ■ ■ ■ Menu bar Toolbar HBA tree Tabbed pages The HBA tree displays the hosts with their connected adapters, devices, and LUNs.
Q 6 – Getting Started Exiting the SANblade Manager GUI A device icon with a circled red X indicates one of the following: ❑ ❑ ❑ ❑ ■ The device is down. The port to the device is down or offline. The device is not responding properly to SCSI commands. The adapter icon displays alarm status. The most severe alarm status for the adapter displays (see section 8.2 for details about alarms): ❑ ❑ ❑ ❑ ❑ ❑ A green adapter icon indicates no alarm. A gray adapter icon indicates an informational alarm.
Q 6 – Getting Started Getting Help with the SANblade Manager GUI 6.4.2 Specifying the Browser Location Perform the following steps to specify the location of the browser SANblade Manager launches when you select to view the online help (see section 6.4.1): 1. On the SANblade Manager main window Help menu, click Set Browser Location. The Browser Location dialog box displays (see figure 6-3). Figure 6-3. Browser Location Dialog Box 2. In the Browser Location box, enter the location.
Q 6 – Getting Started Setting SANblade Manager Security 6.4.3 Viewing SANblade Manager Software Information To view information about the SANblade Manager application software, on the SANblade Manager main window Help menu, click About. The About SANblade Manager window displays (see figure 6-4). Figure 6-4.
Q 6 – Getting Started Setting SANblade Manager Security You can change the SANblade Manager application access password for any host connected to your system for which you have administrator or root privileges. NOTE: The default SANblade Manager application access password is config. Change this password after installation to ensure that security is not compromised. Perform the following steps to set the application access password for a host: 1.
6 – Getting Started Setting the Warning Display Option Q 4. In the Application Access section, do the following to modify the SANblade Manager application access password: a. In the Old Password box, type the current password. b. In the New Password box, type the new password. c. In the Verify Password box, type the new password again to confirm the new password. 5. Do one of the following: ❑ ❑ Click Apply to update the application access password.
Q 6 – Getting Started Setting the Configuration Change Alarm Option 6.7 Setting the Configuration Change Alarm Option SANblade Manager tries to keep the devices and the LUNs that the adapter displays current. When cables are pulled, devices hot plugged into the SAN, or devices are removed, SANblade Manager generates a configuration alarm in the Alarm Log. Perform the following steps to set how the SANblade Manager GUI handles configuration changes: 1.
Q 6 – Getting Started Specifying the Polling Interval ❑ Select Ignore Configuration Changes if you want to ignore the configuration change alarm. The old configuration continues to display. To update to the current configuration, manually connect and disconnect the host (see section 7). 3. Click OK to return to the SANblade Manager main window. 6.8 Specifying the Polling Interval The polling interval is set on a host basis.
Q 6 – Getting Started Setting the Event Log Options 4. In the Interval box, type the polling interval. The range is 1 second to 3600 seconds (1 hour). The default is 30 seconds. NOTE: The faster the polling rate, the more quickly the SANblade Manager GUI receives indications from the connected host. However, faster polling rates consume more of your system’s CPU and network resources and slow the system. 5. Click OK to set the interval. Click Cancel to not change the interval setting. 6.
6 – Getting Started Setting the Alarm Log Option Q 6.10 Setting the Alarm Log Option Perform the following steps to set the number of alarms the Alarm Log can list: NOTE: See section 8.2 for information about viewing the Alarm Log. 1. On the SANblade Manager main window View menu, select Options. The Options dialog box displays (see figure 6-10). Figure 6-10. Options Dialog Box—Alarm Log Section 2. In the Alarm Log section Log Size box, type the number of alarms the Alarm Log can list.
Q 6 – Getting Started Setting the Configuration Policies From this dialog box, you can click More to view the shared components, as in figure 6-12. Highlight the shared device or LUN on the left, the shared hosts display on the right. Click OK to return to the message. Figure 6-12. Shared Components Window ■ When SANblade Manager updates the configuration to reflect configuration changes made by another host, the configuration change—reloading message displays. Click OK.
6 – Getting Started Setting the Configuration Policies Q 2. Device sharing checking occurs each time a configuration change is made to a device. Do one of the following to select the options for sharing devices among hosts: ❑ Clear the Check for shared devices (targets) among host(s) check box to disable device sharing checking.
Q 6 – Getting Started Setting the Configuration Policies ❑ Ask these options when a device is configured and sharing is detected. If you select this policy and sharing is detected, the Shared Device Found dialog box displays. Do the following: a. Select one of the following: ❑ ❑ ❑ Do not configure device. Configure and disable access from other hosts. Proceed with device configuration. b. Click OK to accept your selection. Click Cancel to not configure the device. 3.
Q 6 – Getting Started Updating the HBA Tree ❑ Enable the selected LUN and display a message if the LUN is already enabled on another host(s). If you select this policy and this type of sharing is detected, a warning displays. Do one of the following: ❑ ❑ Click OK to disable access to these LUNs from other hosts. ❑ Click Cancel to disable this policy for this instance. ❑ Click More to view which LUNs are being shared with what hosts that are conflicting with this policy.
Section 7 Setting Up Connections You can connect to and configure local and remote systems. This section discusses: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Connecting to hosts (see section 7.1) Configuring Fibre Channel devices (see section 7.2) Configuring LUNs for a device (see section 7.3) Viewing adapter, device, and path information (see section 7.4) Viewing the current LUN path (see section 7.5) Viewing and setting a LUN path (see section 7.5) Bind target devices attached to the adapter (see section 7.
Q 7 – Setting Up Connections Connecting to Hosts 7.1.1 Manually Connecting to a Host Perform the following steps to manually connect to a host: 1. Do one of the following: ❑ ❑ ❑ Click the Connect button on the SANblade Manager main window toolbar. On the SANblade Manager main window Host menu, click Connect. Press INSERT. The Connect to Host dialog box displays (see figure 7-1). Figure 7-1. Connect to Host Dialog Box 2.
Q 7 – Setting Up Connections Connecting to Hosts 7.1.2 Auto Connecting to All Hosts The auto-connect feature dynamically connects your machine to all the hosts in the network that meet the following conditions: ■ ■ The SANblade Manager agent on the host is running. The host is on the same class C IP address subnet as your machine. The hosts display in the HBA tree and in the Connect to Host dialog box Enter Host Name or IP Address box drop-down list.
7 – Setting Up Connections Connecting to Hosts Q 7.1.3.1 Creating a Host Group File Perform the following steps to save the group of hosts that display in the HBA tree to a host group file: 1. Do one of the following: On the SANblade Manager main window Host menu, click Save Group. Right-click the HBA tree. From the pop-up menu, click Save Group. ❑ ❑ 2. The Save dialog box displays. Save the host group file (.hst) in an appropriate directory. Click Save.
Q 7 – Setting Up Connections Connecting to Hosts 7.1.4 Connecting to Hosts Automatically when Starting the SANblade Manager GUI from the Command Line NOTE: For information about starting SANblade Manager without automatically connecting to hosts, see section 6.1. You can connect to specified hosts automatically when starting the SANblade Manager GUI from the command line. You can connect to a single host or a group of hosts listed in a host group file.
Q 7 – Setting Up Connections Connecting to Hosts 3. Do one of the following: ❑ Type the following and then press ENTER to connect to a single host. hostname is the host name or IP address: SANsurfer -h hostname For example: SANsurfer -h adsw2ksys2 ❑ Type the following and then press ENTER to connect to a group of hosts listed in a host group file (.hst). path is the path of the host group file. SANsurfer -g path For example: SANsurfer -g c:\Program Files\QLogic Corporation\ SANsurfer\hostfiles\group1.
Q 7 – Setting Up Connections Configuring Fibre Channel Devices 7.1.5 Disconnecting from a Host Perform the following steps to disconnect from a host: 1. In the SANblade Manager main window HBA tree, select the host (or adapter, device, or LUN connected to the host) that you want to disconnect. 2. Do one of the following: ❑ On the Host menu, select Disconnect. ❑ Right-click the host in the HBA tree. From the pop-up menu, select Disconnect. ❑ Press DELETE.
7 – Setting Up Connections Configuring Fibre Channel Devices Q The Fibre Channel Port Configuration dialog box displays (see figure 7-3). Figure 7-3. Fibre Channel Port Configuration Dialog Box The host name displays in the title bar. The table is a two-dimensional view of the adapters and devices in the machine. The following information displays: ❑ Node Name. World wide device node name ❑ Port Name. World wide device port name ❑ Adapter n (State/Topo/Bind/ID).
Q 7 – Setting Up Connections Configuring Fibre Channel Devices In addition, the cell is color-coded as follows to represent path information: ❑ White with Open Eye icon. Path visible to the operating system ❑ Black with no icon. Path hidden from the operating system ❑ Gray with Stop icon. Unconfigured device ❑ White with no icon. No path 2. Select the following, as appropriate, from the Fibre Channel Port Configuration dialog box: ❑ Configure device paths for this host (see section 7.2.
7 – Setting Up Connections Configuring Fibre Channel Devices Q 3. The modified configuration set up by SANblade Manager can be either applied to the live system for dynamic updates or saved to the system's persistent configuration data. If the configuration is saved, the adapter's driver retrieves the data from the persistent configuration data at the next system bootup and configures the system accordingly.
Q 7 – Setting Up Connections Configuring Fibre Channel Devices From the Fibre Channel Configuration dialog box Device menu, select Auto Configure to configure the device paths on this host to their default values. Perform the following steps to configure the device paths, and optionally the LUN paths, on this host to their default values: 1. From the Fibre Channel Configuration dialog box Device menu, select Auto Configure. 2. The configure LUN paths to their default values message displays.
7 – Setting Up Connections Configuring Fibre Channel Devices Q 7.2.1.3 Forcing Separation of Device Ports Failover and currently active paths are usually configured based on a device basis (as represented by the device node name). This allows for adapter level and port failover. You can, however, separate a device into two devices on a port basis (by device port name), where each has a subset of paths. This allows only for adapter level failover.
Q 7 – Setting Up Connections Configuring Fibre Channel Devices 3. The confirm forced separation of device message displays. Do one of the following: ❑ Click No to not separate the device. ❑ Click Yes to force device separation. The new configuration displays, as in the example in figure 7-5; there are two listings for device node name 34-34-34-34-34-34-34-34. Figure 7-5. Force Separated Device Configuration 7.2.1.3.
Q 7 – Setting Up Connections Configuring Fibre Channel Devices 3. The confirm combining of separated devices message displays. Do one of the following: ❑ Click No to not combine the separated device. ❑ Click Yes to combine the separated device. The new configuration displays, as in figure 7-6 for device node name 34-34-34-34-34-34-34-34. Figure 7-6. Combine Separated Device Configuration 7.2.
Q 7 – Setting Up Connections Configuring Fibre Channel Devices 7.2.2.1 Enable or Disable Failover Configuration This feature is available only on Windows NT/2000. If you are using third-party software for failover, disable failover in SANblade Manager by performing the following steps: 1. From the Fibre Configuration dialog box, click the File menu. 2. Clear the Enable Failover Configuration check box. All the target paths become visible, and all the LUN paths become preferred.
Q 7 – Setting Up Connections Configuring LUNs for a Device 7.2.2.3 Enabling and Disabling All LUNs on this Host You can configure LUN masking—setting LUNs masked or unmasked from the operating system. Enabling a LUN sets the LUN as unmasked; disabling a LUN sets the LUN as masked. Perform the following steps to enable or disable all LUNs on this host: 1. From the Fibre Channel Configuration dialog box LUNs menu, select Enable LUNs. 2.
Q 7 – Setting Up Connections Configuring LUNs for a Device The following messages can display: ❑ If SANblade Manager detects an invalid LUN configuration, the detected invalid LUN configuration message displays. Invalid LUN configurations include: ❑ A LUN with contradictory enabled paths. All paths must be enabled or disabled. ❑ Too many or too few preferred paths in the system. Only one path can be preferred at a time. Click OK; auto configure runs automatically.
Q 7 – Setting Up Connections Configuring LUNs for a Device Adapter cell information consists of the following: ❑ State. The state of the LUN, which can be Visible, Hidden, or Unconfigured. ❑ Topo. Short for topology, either Fabric (the device is in the fabric) or Local (the device is on the local loop). ❑ Current. The state of the path, which is either Current, Alternate, or Unconfigured. The cell and bull’s eye are color-coded to represent path information: ❑ Blue cell.
Q 7 – Setting Up Connections Configuring LUNs for a Device ❑ View information (see section 7.4): ❑ ❑ ❑ ❑ Adapter information (see section 7.4.1) Device information (see section 7.4.2) Path information (see section 7.4.3) Get help. From the Help menu, click Browse Contents. The help text for the LUN Configuration dialog box displays. 3.
7 – Setting Up Connections Configuring LUNs for a Device Q NOTE: ■ You can set only the LUN path of an enabled LUN. A LUN path can be set as preferred or alternate if the device path is configured as hidden or visible, but not as unconfigured. ■ You can use the Current Path option from the Host menu to view the failover settings for a selected host and set preferred or alternate LUN path as the currently active path (see section 7.5). 7.3.2.
Q 7 – Setting Up Connections Configuring LUNs for a Device NOTE: This option is available only when the LUN is enabled and there are at least two available paths. 7.3.2.3.1 Configure Adapter LUN Paths to the Default Perform the following steps to configure all LUN paths for an adapter to the default values: 1. For the adapter for which you want to configure the LUNs, right-click in the Adapter n heading. 2. From the pop-up menu, select Configure Adapter Using Default. 7.3.2.3.
Q 7 – Setting Up Connections Viewing Adapter, Device, and Path Information 7.3.3 Configure LUN Masking for this Device You can configure LUN masking—set LUNs as masked or unmasked from the operating system. Enabling a LUN sets the LUN as unmasked; disabling a LUN sets the LUN as masked. Use the following options as appropriate: ■ ■ Enabling and disabling all LUNs (see section 7.3.3.1) Enabling and disabling individual LUNs (see section 7.3.3.2) 7.3.3.
Q 7 – Setting Up Connections Viewing Adapter, Device, and Path Information 7.4.1 Viewing Adapter Information Perform the following steps to view adapter information from the Fibre Channel Configuration dialog box and LUN Configuration dialog box: 1. Right-click in the Adapter n column heading. From the pop-up menu, select Adapter Information. The Adapter Information dialog box displays (see figure 7-8). Figure 7-8. Adapter Information Dialog Box The following information displays: ❑ Number.
Q 7 – Setting Up Connections Viewing Adapter, Device, and Path Information 7.4.2 Viewing Device Information Perform the following steps to view device information from the Fibre Channel Configuration dialog box and LUN Configuration dialog box: 1. To display information about a device, do one of the following: ❑ From the Fibre Channel Configuration dialog box, right-click in a cell in the Device Node Name or Device Port Name column. From the pop-up menu, select Device Information.
Q 7 – Setting Up Connections Viewing Adapter, Device, and Path Information 7.4.3 Viewing Path Information Perform the following steps to view path information from the LUN Configuration dialog box: 1. Right-click in the cell in the Adapter n column. From the pop-up menu, select Path Information. The Path Information dialog box displays for the path (see figure 7-10). Figure 7-10. Path Information Dialog Box The following information displays: ❑ Device Node Name.
Q 7 – Setting Up Connections Viewing and Setting a LUN Path 7.5 Viewing and Setting a LUN Path The Current Path option from the Host menu enables you to do the following: ■ ■ View the failover settings for a selected host Set a preferred or alternate LUN path as the currently active path NOTE: See sections 7.2.2 and 7.3.2 for information about setting LUN paths as the preferred or alternate path in a failover condition, and selecting the preferred or alternate path as the currently active path.
Q 7 – Setting Up Connections Bind Target Devices Attached to the Adapter The current path failover information displays: ❑ ❑ Node Name. Listing of the devices and LUNs. ❑ Devices. World wide device node name ❑ LUNs. LUNs are listed under the devices to which they are connected. The LUN number and world wide device port name are included. Adapter n. The adapter cell in the table represents a path from the adapter to the LUN.
7 – Setting Up Connections Bind Target Devices Attached to the Adapter Q Bind target devices to the attached HBAs using the Fibre Channel Port Configuration dialog box, as described in the following steps: 1. To access the Fibre Channel Port Configuration dialog box, perform the following steps: ❑ In the HBA tree, select the host (or adapter, device, or LUN connected to the host). Click the Configure button on the toolbar. ❑ Right-click the host, adapter, device, or LUN in the HBA tree.
Q 7 – Setting Up Connections Deleting Persistent Configuration Data 3. Select an ID from the ID drop-down box. In Solaris SPARC and Red Hat Linux, target IDs can be assigned to configured ports. Valid target ID values are in the range 0–254 (Red Hat Linux) or 0–255 (Solaris SPARC). The IDs are validated before they are saved. Duplicate target IDs are not allowed. When you set a target ID for a visible path in Red Hat Linux, the same target ID is set for both hidden and configured paths.
Q 7 – Setting Up Connections Deleting Persistent Configuration Data 7.7.1 Deleting Adapter Persistent Configuration Data Perform the following steps to delete the persistent configuration data for an adapter and its devices and LUNs: 1. Do one of the following: ❑ From the SANblade Manager main window HBA tree, right-click the adapter (or its host). From the pop-up menu, select Adapter Persistent Configuration Data.
Q 7 – Setting Up Connections Deleting Persistent Configuration Data 7.7.2 Deleting Device Persistent Configuration Data Perform the following steps to delete the persistent configuration data for a device and its LUNs: 1. Do one of the following: ❑ From the SANblade Manager main window HBA tree, right-click the device (or LUN connected to the device). From the pop-up menu, select Device Persistent Configuration Data.
Q 7 – Setting Up Connections Replacing Devices 7.8 Replacing Devices The QLA2xxx adapter’s driver does not automatically purge a device that has been physically removed nor delete a device that is no longer accessible because of errors or failure. The driver keeps the device in its database and marks it as invisible. The driver adds a new device to the database, even if the device is inserted in the same slot as a removed device.
Q 7 – Setting Up Connections Replacing Devices 3. The Warning on Device Replacement dialog box displays (see figure 7-16). Figure 7-16. Warning on Device Replacement Dialog Box The dialog box provides: ❑ Information about the device replacement process ❑ The number, type, and world wide adapter node name of the adapter you selected in step 1 Do the following: a. Read the information. b. Do one of the following: FS0054601-00 E ❑ Click Next to proceed.
Q 7 – Setting Up Connections Replacing Devices 4. If you clicked Next, the Select Inactive Device dialog box displays (see figure 7-17). Figure 7-17. Select Inactive Device Dialog Box The Select Inactive Device dialog box displays the following information: ❑ Adapter. Adapter number, type, and world wide adapter node name. ❑ Old Device. World wide device node name of the device that you want to replace. ❑ Table listing the inactive devices attached to the adapter.
Q 7 – Setting Up Connections Replacing Devices 5. If you clicked Next, the Select Active Device dialog box displays (see figure 7-18). Figure 7-18. Select Active Device Dialog Box The Select Active Device dialog box displays the following information: ❑ Adapter. Adapter number, type, and world wide adapter node name. ❑ Old Device. Device node name of the inactive device that you want to replace. ❑ New Device. Device node name of the active device to replace the inactive device.
7 – Setting Up Connections Replacing Devices Q 6. If you clicked Next, the Confirm Device Replacement dialog box displays (see figure 7-19). Figure 7-19. Confirm Device Replacement Dialog Box The Confirm Device Replacement dialog box displays the following information: ❑ Adapter. Adapter number, type, and world wide adapter node name. ❑ Old Device. World wide device node name of the inactive device that you want to replace. ❑ New Device.
Q 7 – Setting Up Connections Viewing a Saved Host Configuration from a File 7.9 Viewing a Saved Host Configuration from a File When a host is offline, you can view a virtual image of its host configuration that you saved to an external file in your working directory. This section discusses: ■ ■ Saving the host configuration to a file (see section 7.9.1) Viewing the host configuration from a file (see section 7.9.2) 7.9.
7 – Setting Up Connections Viewing a Saved Host Configuration from a File Q 7.9.2 Viewing the Host Configuration from a File Perform the following steps to view the saved virtual host configuration from a file: NOTE: You cannot view a virtual host configuration for a host that is currently connected. 1. Do one of the following: ❑ ❑ ❑ From the Host menu, select Load from File. Right-click in the HBA tree. From the pop-up menu, select Load from File. Press CTRL+O. 2. The Open dialog box displays.
Q 7 – Setting Up Connections Comparing Host Configurations 7.10 Printing a Host Configuration Perform the following steps to print a host configuration: 1. From the SANblade Manager main window, do the following: a. In the HBA tree, select the host (or adapter, device, or LUN connected to the host). b. Do one of the following: ❑ Click the Configure button on the toolbar. ❑ Right-click the host (or adapter, device, or LUN connected to the host) in the HBA tree. From the pop-up menu, select Configure.
7 – Setting Up Connections Comparing Host Configurations Q 2. The Open dialog box displays. Select a .qlc file from the local working directory. Click Open. The Differences Between Online Host and Offline Host dialog box displays (see figure 7-21). Figure 7-21. Differences Between Offline Host and Online Host Dialog Box The Online Host and Offline Host tabbed pages are synchronized: the scroll bar moves both pages. If one host tree is expanded or collapsed, the other tree is also expanded or collapsed.
Q 7 – Setting Up Connections Comparing Host Configurations Use the buttons on the tool bar to navigate through the Offline Host and Online Host tabbed pages: ■ Click the binoculars button to search the host configuration for a requested name. If the search is found, the two tabbed pages are synchronized and the found text is displayed with the selection color of the operating system (the selection color supersedes the change colors).
7 – Setting Up Connections Comparing Host Configurations Q Notes 7-42 FS0054601-00 E
Section 8 Monitoring the Connections SANblade Manager continuously monitors connected hosts and informs you of various conditions and problems through the Alarm Log and Event Log. This section discusses: ■ ■ Viewing and managing the Event Log (see section 8.1) Viewing and managing the Alarm Log (see section 8.2) 8.1 Viewing and Managing the Event Log The Event Log displays events relating to SANblade Manager application operations for any host connected to your system.
8 – Monitoring the Connections Viewing and Managing the Event Log Q The Event Log dialog box displays (see figure 8-1). Figure 8-1. Event Log Dialog Box The Event Log dialog box includes the following information about each event: ❑ Type. The severity of the event. ❑ ❑ ❑ Informative event. An informative or general information event Warning event. A noncritical application event Error event. A critical application event ❑ Time Stamp. The date and time the event was reported ❑ Message.
Q 8 – Monitoring the Connections Viewing and Managing the Event Log 3. To view an individual event, double-click the event. The Event Details dialog box displays (see figure 8-2). Figure 8-2. Event Details Dialog Box The Event Details dialog box displays the time stamp and message. Do the following as appropriate: ❑ ❑ ❑ Click Next to view the details of the next event. Click Previous to view the details of the previous event. Click Close to return to the Event Log dialog box. 4.
8 – Monitoring the Connections Viewing and Managing the Event Log Q 8.1.3 Exporting the Event Log Perform the following steps to export the current events to a CSV (comma delimited) list, which can be exported to another application. 1. From the Event Log dialog box, click Export. See section 8.1.1 for information on accessing the Event Log dialog box. 2. You are prompted to select a location and a file name (see figure 8-3).
Q 8 – Monitoring the Connections Viewing and Managing the Event Log Figure 8-4 shows an example output file, which contains the following event information: ■ ■ ■ Event status (unknown, bad, good, or warning) Date Message Figure 8-4.
8 – Monitoring the Connections Viewing and Managing the Alarm Log Q 8.1.4 Printing the Event Log Perform the following steps to print the Event Log. NOTE: See section 8.1.1 for information on accessing the Event Log dialog box. 1. From the Event Log dialog box, click Print. 2. Print the Event Log. 8.2 Viewing and Managing the Alarm Log SANblade Manager continuously monitors the connected hosts for alarms. The adapter icon on the HBA tree displays alarm status.
Q 8 – Monitoring the Connections Viewing and Managing the Alarm Log This section discusses: ■ ■ ■ Viewing the Alarm Log (see section 8.2.1) Clearing the Alarm Log (see section 8.2.2) Printing the Alarm Log (see section 8.2.2) NOTE: See section 6.10 for information about setting the Alarm Log options. 8.2.1 Viewing the Alarm Log Perform the following steps from the SANblade Manager main menu to view the Alarm Log. 1.
Q 8 – Monitoring the Connections Viewing and Managing the Alarm Log The Alarm Log dialog box displays (see figure 8-6). Figure 8-6. Alarm Log Dialog Box The Alarm Log dialog box includes the following information about each alarm: ❑ Time Stamp. Date and time the alarm was reported ❑ Host Name. Name of the host where the alarm originated ❑ Adapter ID. Name of the adapter where the alarm occurred ❑ Application. Type of management application running when the alarm occurred ❑ Description.
Q 8 – Monitoring the Connections Viewing and Managing the Alarm Log 2. If you want to sort the alarm entries, click the column heading. A triangle displays in the heading, indicating an ascending sort (default). Click the triangle for an descending sort. 3. To view an individual alarm, double-click the alarm. The Alarm Details dialog box displays (see figure 8-7). Figure 8-7. Alarm Details Dialog Box The Alarm Details dialog box displays the time stamp, host name, device ID, and description.
8 – Monitoring the Connections Viewing and Managing the Alarm Log ❑ Q ❑ If you are viewing the alarms for one host, SANblade Manager clears the alarms only for that host. ❑ If you are viewing the alarms for one adapter, SANblade Manager clears the alarms only for that adapter. Click Cancel to not clear the alarms. 3. From the Alarm Log dialog box, click OK to return to the SANblade Manager main window. 8.2.
Q 8 – Monitoring the Connections Viewing and Managing the Alarm Log Figure 8-9 shows an example output file, which contains the following alarm information: ■ ■ ■ ■ ■ Date Host Adapter Status Message Figure 8-9. Export Alarm Log—Sample Output File 8.2.4 Printing the Alarm Log Perform the following steps to print the Alarm Log: NOTE: See section 8.2.1 for information on accessing the Alarm Log dialog box. 1. From the Alarm Log dialog box, click Print. 2. Print the Alarm Log.
8 – Monitoring the Connections Viewing and Managing the Alarm Log Q Notes 8-12 FS0054601-00 E
Section 9 Displaying Host, Adapter, Device, and LUN Information You can display information about hosts, adapters, devices, and LUNs. This section discusses viewing information about the following: ■ Hosts —general information, topology, and statistics (see section 9.1) ■ Adapters—general information, statistics, device list, and link status (see section 9.2) ■ Devices—general information and LUN list (see section 9.3) ■ LUNs—general information (see section 9.4) NOTE: See section 7.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Host Information 9.1.1 Viewing General Host Information Perform the following steps to view general information about a host: 1. In the SANblade Manager main window HBA tree, select the host. 2. Select the Information tab. The Host Information tabbed page displays (see figure 9-1). Figure 9-1. Host Information Tabbed Page The following information displays: ❑ ❑ ❑ ❑ 9-2 Host. Host name OS Type.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Host Information 9.1.2 Viewing Topology Information Perform the following steps to view the topology for a host: 1. In the SANblade Manager main window HBA tree, select the host. 2. Select the Topology tab. The Topology tabbed page displays (see figure 9-2). Figure 9-2. Topology Tabbed Page The following information displays: ❑ Host.
9 – Displaying Host, Adapter, Device, and LUN Information Displaying Host Information Q 9.1.3 Viewing and Updating Host Statistics This section discusses: ■ ■ ■ Viewing host statistics (see section 9.1.3.1) Updating host statistics (see section 9.1.3.2) Exporting host statistics (see section 9.1.3.3) NOTE: Host statistics are available only for Windows NT and Windows 2000 systems and only when the QLdirect driver is installed. The Statistics tab does not display if these criteria are not met. 9.1.3.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Host Information The identifying information displays: ❑ Host. Host name For each adapter, the following information displays. IOPS stands for I/Os per second; KBPS stands for kilobytes per second. ❑ Adapter. Adapter’s number, adapter type (2200 indicates a QLA22xx adapter; 2300 indicates a QLA23xx adapter), and world wide adapter port name ❑ Requested. Number of IOPS or KBPS of data requested ❑ Executed.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Host Information 9.1.3.2.2 Updating Host Statistics Automatically Perform the following steps to automatically update the host statistics at a specified interval: 1. Select the Auto Poll check box. 2. Click Set Rate. The Statistics Sampling Rate dialog box displays (see figure 9-4). Figure 9-4. Statistics Sampling Rate Dialog Box 3. In the Sampling Rate box, type the sampling rate interval. The range is 1 second to 30 seconds.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Host Information 9.1.3.3 Exporting Host Statistics Perform the following steps to export the host statistics to a CSV (comma delimited) file, which can be exported to another application: 1. From the Host Statistics tabbed page (see figure 9-3), select the Log to File check box. See section 9.1.3.1 for information on accessing the Host Statistics tabbed page. 2. You are prompted to select a location and a file name (see figure 9-5).
9 – Displaying Host, Adapter, Device, and LUN Information Displaying Host Information Q Figure 9-7 shows an example output file, which contains the following host statistics information: ■ ■ ■ ■ ■ ■ Adapter number and type I/O or KB Requested Executed Scale Time since last poll Figure 9-7.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information 9.2 Displaying Adapter Information You can view the following adapter information: ■ ■ ■ ■ General adapter information (see section 9.2.1) Adapter statistics (see section 9.2.2) Device list (see section 9.2.3) Link status (see section 9.2.4) 9.2.1 Viewing General Adapter Information Perform the following steps to view general information about an adapter connected to a host: 1.
9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information Q The identifying information displays: ❑ Host. Name of the host connected to the adapter ❑ Adapter. Adapter number and type (2200 indicates a QLA22xx adapter; 2300 indicates a QLA23xx adapter) ❑ Node Name. World wide adapter node name ❑ Port Name. World wide adapter port name ❑ Port ID. Port ID of the adapter The general information displays: ❑ Serial Number. Serial number of the adapter ❑ BIOS Version.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information 9.2.2.1 Viewing Adapter Statistics Perform the following steps to view statistical information about an adapter connected to a host: 1. In the SANblade Manager main window HBA tree, select the adapter. 2. Select the Statistics tab. The Adapter Statistics tabbed page displays (see figure 9-9). Figure 9-9. Adapter Statistics Tabbed Page The identifying information displays: ❑ ❑ ❑ ❑ ❑ Host.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information ❑ ❑ ❑ I/O Count. Total number of I/Os reported by the adapter's driver I/O per Second. Number of I/Os processed by the adapter per second Bytes per Second. Number of bytes processed by the adapter per second You can update statistics manually or have them automatically update at a specified interval (see section 9.2.2.2). You can also export the statistics to a CSV (comma delimiter) file (see section 9.2.2.3). 9.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information 9.2.2.2.3 Resetting Adapter Statistics Click Reset to reset the statistics to their initial value of zero. 9.2.2.3 Exporting Adapter Statistics Perform the following steps to export the adapter statistics to a comma delimited (CSV) file, which can be exported to another application. 1. From the Adapter Statistics tabbed page (see figure 9-9), select the Log to File check box. See section 9.2.2.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information Figure 9-13 shows an example output file, which contains the following host statistics information: ■ ■ ■ ■ ■ ■ Adapter errors Device errors Resets Recount IOPS bytes per second (bps) Figure 9-13.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information 9.2.3 Viewing the Device List Perform the following steps to display information about devices attached to an adapter connected to a host: 1. In the SANblade Manager main window HBA tree, select the adapter. 2. Select the Device List tab. The Device List tabbed page displays (see figure 9-14). Figure 9-14. Device List Tabbed Page The identifying information displays: ❑ ❑ ❑ ❑ ❑ Host.
9 – Displaying Host, Adapter, Device, and LUN Information Displaying Adapter Information ❑ ❑ Q Product ID. Product ID of the device Product Revision. Product revision level of the device To sort the device list information, click in the desired column heading. In figure 9-14, the information is sorted by the loop ID. 9.2.4 Viewing Link Status Perform the following steps to view the link information for devices attached to an adapter connected to a host: 1.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Device Information The link status information displays: ❑ Port Name. For the adapter, the world wide adapter port name displays. For each device, the world wide device port name displays. ❑ Diagnostic information. For the adapter and each device, the number of link failures, loss of sync failures, signal failures, and number of invalid CRCs display. 3.
9 – Displaying Host, Adapter, Device, and LUN Information Displaying Device Information Q 9.3.1 Viewing General Device Information Perform the following steps to view general information about a device: 1. In the SANblade Manager main window HBA tree, select the device. 2. Select the Information tab. The Device Information tabbed page displays (see figure 9-16). Figure 9-16. Device Information Tabbed Page The following information displays: ❑ ❑ ❑ ❑ ❑ ❑ 9-18 Product Vendor.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying Device Information 9.3.2 Viewing the LUN List Perform the following steps to display information about LUNs: 1. In the SANblade Manager main window HBA tree, select the device. 2. Select the LUN List tab. The LUN List tabbed page displays (see figure 9-17). Figure 9-17. LUN List Tabbed Page The identifying information displays: ❑ ❑ ❑ ❑ ❑ ❑ Device Vendor. Device manufacturer Device Product ID.
Q 9 – Displaying Host, Adapter, Device, and LUN Information Displaying LUN Information 9.4 Displaying LUN Information Perform the following steps to view general information about a LUN: 1. In the SANblade Manager main window HBA tree, select the LUN. 2. Select the Information tab. The LUN Information tabbed page displays (see figure 9-18). Figure 9-18. LUN Information Tabbed Page The following information displays: ❑ ❑ ❑ ❑ ❑ ❑ 9-20 Product Vendor. Manufacturer of the LUN Product ID.
Section 10 Performing Diagnostics Diagnostic tests interrupt normal adapter operations. The adapter’s state before the tests are restored at the completion of the testing. Note the following: ■ Run these tests when no other activities are required of the adapter. ■ Tests read and write to sensitive areas on the adapter. ■ Disruption of some diagnostic tests may require a complete update of the adapter’s critical memory areas.
Q 10 – Performing Diagnostics Preparing for Diagnostic Testing NOTE: The loopback test must be run with the loopback connector; the read/write buffer test must be run without the loopback connector on a device that supports the SCSI Read Buffer and SCSI Write Buffer commands. 10.1 Preparing for Diagnostic Testing Preparation for the loopback and read/write buffer tests differs. See the following, as appropriate: ■ ■ Loopback test (see section 10.1.1) Read/write buffer test (see section 10.1.2) 10.1.
Q 10 – Performing Diagnostics Preparing for Diagnostic Testing 10.1.1.2 Installing a Loopback Connector Before running the loopback test, you must install a loopback connector on the adapter. Note the following about the loopback connector: ■ The loopback connector must be appropriate for the type of Fibre Channel adapter connector. ■ Be sure to select the appropriate adapter connector for testing. Each adapter connector displays in the SANblade Manager main window HBA tree as an adapter.
10 – Performing Diagnostics Setting the Diagnostic Test Parameters Q To run the read/write test on specific devices attached to an adapter, perform the following steps from the SANblade Manager main window: 1. Right-click on a device in the HBA tree. 2. Select Enable Diagnostics on Device. A check mark displays next to the device icon. 3. Repeat steps 1 and 2 for each device you want to test. 10.
Q 10 – Performing Diagnostics Running Diagnostic Tests 4. The data size sets the number of bytes transferred when the test is run. In the Data Size box, select the number of bytes to transfer. Valid values are 8, 16, 32, and 64. NOTE: Novell NetWare does not support the values 16, 32, or 64. 5. Do one of the following to set the test frequency: ❑ In the Number of Tests box, type or select the number of passes you want to run. Testing stops when the passes complete.
Q 10 – Performing Diagnostics Viewing the Diagnostic Test Results 10.4 Viewing the Diagnostic Test Results The test results section of the Diagnostics tabbed page displays the results of a test run (see figure 10-2). The Test Status column indicates whether the test passed or failed. The remaining information pertains to error counters. Figure 10-2. Diagnostic Test Results Section This section discusses: ■ ■ Loopback test results (see section 10.4.1) Read/write buffer test results (see section 10.4.
Q 10 – Performing Diagnostics Viewing the Diagnostic Test Results Figure 10-2 shows a successful test. The Test Status column in figure 10-3 shows that the loopback test failed. Figure 10-3.
Q 10 – Performing Diagnostics Viewing the Diagnostic Test Results 10.4.2 Read/Write Buffer Test Results The Read/Write Buffer Test Results section provides the following information, as shown in figure 10-4. Figure 10-4. Diagnostic Test Results—Read/Write Buffer Test ■ ■ Loop ID/Status ❑ The loop ID of the adapter when operating in loop mode. ❑ The status of the test—whether the test passed or failed. The possible values: Success. The test passed. ❑ Error.
Q 10 – Performing Diagnostics Viewing the Diagnostic Test Results ❑ ❑ ❑ R/W buffer not supported Write buffer failed Device not present ■ Link Failure. Number of link failures ■ Sync Loss. Number of sync loss errors ■ Signal Loss. Number of signal loss errors ■ Invalid CRC. Number of invalid CRCs If the value in the Data Miscompare column is nonzero, you can view the miscompare information by double-clicking any column. The Diagnostic Details dialog box displays (see figure 10-5). Figure 10-5.
Q 10 – Performing Diagnostics Preparing for Normal Adapter Operations 10.5 Preparing for Normal Adapter Operations When loopback testing is complete, do the following to resume normal adapter operations: 1. Do the following to remove the loopback connector: a. Remove the loopback connector from the adapter connector. b. Reconnect the cable that you disconnected in section 10.1.1.2. 2. Modify the adapter settings Connection Options back to its previous setting (see section 10.1.1.1).
Section 11 Updating the Adapter You can update an adapter’s nonvolatile RAM (NVRAM) settings and flash BIOS. This section discusses: ■ ■ ■ ■ Updating adapter settings (see section 11.1) Restoring default NVRAM settings from a file (see section 11.2) Updating the flash BIOS from a file (see section 11.3) Updating the FCode (see section 11.4) NOTE: Flash BIOS applies only to Windows NT and Windows 2000 systems. FCode applies only to Solaris SPARC systems.
11 – Updating the Adapter Updating Adapter Settings Q The Settings tabbed page displays parameters that are saved in NVRAM. These settings configure Fibre Channel devices and the QLA2xxx adapter to which they are attached (see figure 11-1). Figure 11-1. Settings Tabbed Page (Adapter Settings) The identifying information displays: ■ ■ ■ ■ ■ Host. Name of the host connected to the adapter Adapter. Adapter number and type Node Name. World wide adapter node name Port Name.
Q 11 – Updating the Adapter Updating Adapter Settings Perform the following steps to modify the settings for the selected adapter: 1. In the SANblade Manager main window HBA tree, select the adapter. 2. Select the Settings tab. 3. In the Select Settings section box, select the type of settings that you want to modify. ❑ ❑ Adapter Settings. See section 11.1.1 for details. Advanced Adapter Settings. See section 11.1.2 for details. 4. As appropriate, modify the settings.
11 – Updating the Adapter Updating Adapter Settings Q 11.1.1 Adapter Settings To view or modify the host adapter NVRAM settings, on the Settings tabbed page Select Settings section box, select Adapter Settings. The Adapter Settings section displays the current settings (see figure 11-2). Figure 11-2.
Q 11 – Updating the Adapter Updating Adapter Settings The default settings for the QLA2xxx adapter are listed in table 11-1 and described in the following paragraphs. Table 11-1.
Q 11 – Updating the Adapter Updating Adapter Settings ■ Hard Loop ID. If the Enable Adapter Hard Loop ID setting is enabled, the adapter attempts to use the ID specified in this setting. The default ID is 0. ■ Loop Reset Delay. After resetting the loop, the firmware refrains from initiating any loop activity for the number of seconds specified in this setting. The default is 5 seconds. ■ Enable Adapter Hard Loop ID.
Q 11 – Updating the Adapter Updating Adapter Settings The default settings for the QLA2xxx adapter are listed in table 11-2 and described in the following paragraphs. Table 11-2.
11 – Updating the Adapter Updating Adapter Settings 11-8 Q ■ Enable Extended Error Logging. This setting provides additional error and debug information to the operating system. When enabled, events are logged into the Windows NT/2000 Event Viewer. The default is disabled. ■ Login Retry Count. This setting specifies the number of times the software tries to log in to a device. The default is 8 retries. ■ Enable LIP Reset.
Q 11 – Updating the Adapter Restoring Default NVRAM Settings from a File 11.2 Restoring Default NVRAM Settings from a File WARNING!! Changing NVRAM incorrectly can cause serious damage to your system. Perform the following steps to restore the default NVRAM settings from a file: 1. In the SANblade Manager main window HBA tree, select the adapter. 2. Click the Utilities tab. The Utilities tabbed page displays (see figure 11-4). Figure 11-4.
11 – Updating the Adapter Updating the Flash BIOS from a File Q 5. The Security Check dialog box displays. In the Enter Password box, type the password. Click OK. 6. The tabbed page appears dimmed during the update. When complete, the NVRAM save complete message displays. 7. Reboot the system. 11.3 Updating the Flash BIOS from a File NOTE: The SANblade Manager flash BIOS update feature is available only on Windows NT, Windows 2000, and Red Hat Linux systems.
Q 11 – Updating the Adapter Updating the Flash BIOS from a File The identifying information displays: ❑ ❑ ❑ ❑ ❑ Host. Name of the host connected to the adapter Adapter. Adapter number and type Node Name. World wide adapter node name Port Name. World wide adapter port name Port ID. Port ID of the adapter 3. Click the Update Flash button. 4. Select the file that contains the flash BIOS. You can obtain this file from the QLogic Web site or service personnel. The file typically ends with .
Q 11 – Updating the Adapter Updating the FCode 11.4 Updating the FCode NOTE: The SANblade Manager update FCode feature is available only on Solaris SPARC systems. It is not available on Windows NT, Windows 2000, NetWare, or Red Hat Linux (the Update FCode button does not display on the Utilities tabbed page). Perform the following steps to update the FCode: 1. In the SANblade Manager main menu HBA tree, select the adapter. 2. Click the Utilities tab.
Section 12 Troubleshooting Problems can occur when installing and using the SANblade Manager application. This section discusses: ■ Troubleshooting problems and solutions (see section 12.1) ■ Tracing SANblade Manager GUI and agent activity (debug), as directed by technical support (see section 12.2) 12.1 Troubleshooting Problems and Solutions Table 12-1 lists problems that can occur when using the SANblade Manager application, including their causes and solutions. Table 12-1.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem Cause and Solution Installation reports that there is no space available Cause: There is insufficient disk space or not enough available memory. Solution: The installation detects when there is insufficient disk space. Once sufficient disk space is available, continue the installation. For disk space requirements, see section 4.1 or the readme.txt file.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem Cause and Solution SANblade Manager GUI cannot disconnect from the local host Cause: The qlremote agent or the SANblade Manager GUI is not responding. Solution: Verify that the qlremote agent is installed and running: ■ For Windows NT/2000, open the Services window and verify that the QLogic Management Suite Java agent service is running.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem Cause and Solution SANblade Manager cannot disconnect from a remote host Cause: The qlremote agent service has stopped or is unable to establish a network link. Solution: ■ Verify that the remote host is running the qlremote agent: ■ For Windows NT/2000, open the Services window and verify that the QLogic Management Suite Java agent service is running.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem Cause and Solution Unable to find SANblade Manager GUI online help Cause: The path to the browser is not correctly specified. SANblade Manager GUI does not automatically refresh Cause: There is a disconnect with the qlremote agent or network communication has stopped.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem SANblade Manager GUI loses the connection to an adapter or a device Cause and Solution Cause: There is a disconnect with the qlremote agent or the operating system driver has lost communication with the adapter or device.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem SANblade Manager GUI crashes Cause and Solution Cause: SANblade Manager GUI lost communication with the qlremote agent, another application caused a conflict with SANblade Manager, or an operating system driver lost communication with the adapter or device.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem Cause and Solution Unable to create load balance configuration Cause: SANblade Manager detected an invalid configuration. Unable to mask LUNs Cause: The LUN path is unconfigured. Solution: In order to enable load balancing, each storage subsystem must report multiple LUNs.
Q 12 – Troubleshooting Troubleshooting Problems and Solutions Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem Unable to display Adapter Information, Adapter Statistics, Device List, or Link Status Cause and Solution Cause: The qlremote agent is not running or is not installed. Solution: Verify that the qlremote agent is installed and running: ■ For Windows NT/2000, open the Services window and verify that the QLogic Management Suite Java agent service is running.
Q 12 – Troubleshooting Tracing SANblade Manager GUI and Agent Activity (Debug) Table 12-1. Troubleshooting Problems and Solutions (Continued) Problem Unable to run the read/write buffer test Cause and Solution Cause: The device does not support SCSI Read/Write Buffer commands. Solution: Not all devices support the SCSI Read/Write Buffer commands. The read/write buffer test reports Unsupported if the device does not support these commands.
Q 12 – Troubleshooting Tracing SANblade Manager GUI and Agent Activity (Debug) This section discusses: ■ ■ Tracing SANblade Manager GUI activity (see section 12.2.1) Exporting or saving agent activity logs (see section 12.2.2) 12.2.1 Tracing SANblade Manager GUI Activity To trace SANblade Manager GUI activity, do the following: 1. Edit the local.properties file, which is located where SANsurfer is installed. Change the following two properties: node.trace.level=900 node.trace.output.
12 – Troubleshooting Tracing SANblade Manager GUI and Agent Activity (Debug) Q For a Red Hat Linux or Solaris SPARC system, the location could be: lax.stderr.redirect=/trace.txt lax.stdout.redirect=/trace.txt lax.stdin.redirect=/trace.txt See figure 12-2 for an example. Figure 12-2. SANsurfer.
Q 12 – Troubleshooting Tracing SANblade Manager GUI and Agent Activity (Debug) 3. If you are using a Windows NT/2000 system, do the following to change the height of the screen buffer: a. Do one of the following: ❑ From a Windows NT system, click the Start button, point to Programs, and select Command Prompt. ❑ From a Windows 2000 system, click the Start button, point to Programs, point to Accessories, and select Command Prompt. b. The Command Prompt window displays.
12 – Troubleshooting Tracing SANblade Manager GUI and Agent Activity (Debug) Q g. The Apply Properties to Shortcut dialog box displays. Do one of the following: ❑ For a Windows NT system, select Modify shortcut which started this window. Click OK. ❑ For a Windows 2000 system, select Modify shortcut that started this window. Click OK. 4. Start the SANblade Manager application; a new console window that displays SANblade Manager GUI activity opens. 12.2.
Q 12 – Troubleshooting Tracing SANblade Manager GUI and Agent Activity (Debug) 3. Start the agent, again, without forking into the background. Redirect the stdout and stderr properties to a file (see section 12.2.1, step 2). Send the file to technical support. # /usr/local/bin/qlremote > /AgentOutput.txt 2>&1 4. Open a second terminal to start the SANblade Manager GUI. Connect to the host with the SANblade Manager GUI. 5. From the terminal you opened in step 1, press CTRL+C to stop the qlremote agent.
12 – Troubleshooting Tracing SANblade Manager GUI and Agent Activity (Debug) Q Notes 12-16 FS0054601-00 E
Appendix A Frequently Asked Questions Table A-1 lists some frequently asked questions (FAQs) about the SANblade Manager application. Table A-1. Frequently Asked Questions Question Answer On what platforms does SANblade Manager run? The SANblade Manager GUI runs on any platform that supports the Java JVM 1.3 specification. The agent runs only on Windows NT/2000, Solaris SPARC, Red Hat Linux, and NetWare.
A – Frequently Asked Questions Q Notes A-2 FS0054601-00 E
Appendix B Glossary This section describes common hardware, software, and Fibre Channel terms that are used in the SANblade Manager documentation. Adapter An adapter is the board that interfaces between the host system and disk. Adapter is synonymous with host adapter, adapter board, and HBA. In SANblade Manager documentation, the term QLA2xxx adapter is used. AL_PA AL_PA stands for arbitrated loop_physical address. This is a low-level address on the Fibre Channel loop.
Q B – Glossary Driver (continued) In NetWare, the required drivers include: ■ Host Adapter Module (HAM). HAM is the driver component associated with the host adapter hardware. It provides the functionality to route requests to the bus where a specified device is attached. ■ Custom Device Module (CDM). CDM is the drive component associated with storage devices. It provides the functionality to build device-specific commands from I/O messages received from NetWare’s Media Manager.
Q B – Glossary Failover path The failover path software feature ensures data availability and system reliability by assigning alternate path and automatic adapter failover for device resources. This feature is available only in Windows NT/2000, Novell NetWare, and Red Hat Linux. Flash BIOS A QLA2xxx adapter’s flash PROM contains the code that allows booting from the adapter at startup. HBA Host bus adapter. See Adapter. IOCB IOCB stands for I/O control block.
Q B – Glossary B-4 Media Media are carriers of information. Fibre Channel supports several different physical media: copper, multimode optical, and single-mode optical, which differ mainly in the maximum cable length. All Fibre Channel protocols are supported on all media. NIC NIC stands for network interface controller. NVRAM NVRAM stands for nonvolatile random access memory. NVRAM configuration settings are stored in NVRAM. You can configure NVRAM settings or restore them from a file.
Q B – Glossary Port Ports are access points in a device where a link attaches. There are four types of ports, as follows: N_Port is a Fibre Channel device port that supports point-to-point topology. NL_Port is a Fibre Channel device port that supports loop topology. F_Port is a port in a fabric where an N_Port can attach. FL_Port is a port in a fabric where an NL_Port can attach.
Q B – Glossary Notes B-6 FS0054601-00 E
Appendix C Contacting QLogic For product information, our latest drivers, and links for technical assistance, please visit QLogic’s Web site at: www.qlogic.com. If you are using the SANblade Manager GUI and have Internet access, you can connect to QLogic’s Web site by clicking the QLogic logo on the right side of the SANblade Manager main window toolbar.
C – Contacting QLogic Q Notes C-2 FS0054601-00 E