HBAnyware® Utility Version 3.
Copyright© 2008 Emulex Corporation. All rights reserved worldwide. No part of this document may be reproduced by any means nor translated to any electronic medium without the written consent of Emulex Corporation. Information furnished by Emulex Corporation is believed to be accurate and reliable. However, no responsibility is assumed by Emulex Corporation for its use; or for any infringements of patents or other rights of third parties which may result from its use.
Introduction.............................................................................................................. 1 Known Issues .................................................................................................... 3 Installing HBAnyware Components.......................................................................... 4 Installing the HBAnyware Utility......................................................................... 4 Installing the HBAnyware Utility with Web Launch.......
Viewing Target Mapping (Linux) ................................................................ 39 Viewing and Setting Up Authentication (Windows, Linux 8.2, Solaris LPFC and Solaris emlxs (SFS)) .............................................. 40 Viewing or Changing Authentication Configuration ............................. 42 Changing Your Password.................................................................... 42 Updating Firmware ........................................................................
Restoring the ACG to Its Last Saved Configuration ................................ 105 Accessing a Switch ................................................................................. 105 Access Sub-Groups....................................................................................... 105 Introduction ............................................................................................. 105 ASG Icons ..........................................................................................
Introduction Emulex® drivers have many properties that you can modify using the HBAnyware® configuration utility. The utility is client/server based and provides 'remote' configuration capability to other host platforms running the utility. This remote configuration capability can be provided by either Fibre Channel (FC) access (host systems on the same FC Storage Area Network (SAN) or by Transmission Control Protocol/Internet Protocol (TCP/IP) access (from IP addresses of remote machines).
Table 1: HBAnyware Features and Tasks Cross-Reference Feature/Task Windows Solaris LPFC Solaris (emlxs) SFS Linux VMware ESX Server HBAnyware Graphical User Interface (GUI) HBAnyware Command Line Interface (CLI) HBAnyware with Web Launch utility HBAnyware Security Configurator Discover local hosts, HBAs, targets and LUNs Discover remote hosts, HBAs, targets and LUNs Enable local discovery of Emulex and OEM branded Emulex HBAs Enable FC discovery of Emulex and OEM branded Emulex HBAs Reset HBAs X X
Known Issues The following issues have been reported at the time of publication. These issues may not have been verified or confirmed and may apply to another product, such as hardware. • Emulex provides support for LightPulse® HBAs that are reprogrammed with World Wide Port Names (WWPNs) outside the typical Emulex range, such as Hewlett-Packard’s upcoming Virtual Connect for FC on the BladeSystem c-Class platform. In these environments, HBAnyware utility version 3.
Installing HBAnyware Components Installing the HBAnyware Utility In Windows: The AutoPilot Installer® software streamlines the Emulex driver and HBAnyware utility installation. See the Quick Installation Manual for more information. This manual is available on the Emulex Web site for your driver version.
To install the HBAnyware utilities in Linux: Note: This procedure also installs the application helper module on your system.The application helper module allows HBAnyware to communicate with the Emulex driver for Linux. The 'elxlpfc' init script is also installed and configured to start and stop the 'lpfcdfc' driver during system startup and shutdown. 1. Log on as ‘root’. 2. Download the utilities from the Emulex web site or copy them to the system from the installation CD. 3.
Installing the HBAnyware Utility with Web Launch In addition to the driver and HBAnyware utilities, the following must be installed before you can install the Web Launch feature: Note: The HBAnyware utility with Web Launch is not supported on the VMWare ESX Server. • • In Windows: • Microsoft Internet Information Services (IIS) Server must be installed. See the Microsoft Web site for information on downloads and installation. • JRE must be installed. See the www.java.
3. Run the install script. Type: ./wsinstall 4. When prompted, enter the Web server's document root directory. For example: /srv/www/htdocs 5. You are provided with the IP address of the host and asked if that is the IP address that is being used by your Web server. Answer Y or N as appropriate. If you answer N, you are prompted for the IP address you wish to use. 6. You are asked if your Web server is listening on the normal default HTTP port (80)? Answer Y or N as appropriate.
6. When prompted by pkadd, choose to install HBAnywareSSC. 7. When prompted by pkadd, answer the HBAnyware installation option questions. In Linux: 1. Log on as ‘root’. 2. Change (use the cd command) to the directory to which you copied the tar file. (See “Installing the Utilities and the application helper module” on page 7 step 2 for reference.) 3. Run the install script with the ssc parameter specified. Type: .
Uninstalling HBAnyware Web Launch Only To uninstall HBAnyware Web Launch, but leave the HBAnyware utility installed: In Windows: 1. Select Start> Programs>Emulex>HBAnyware WebLaunch Uninstall. The following screen appears: Figure 2: HBAnyware Web Launch, Uninstallation screen 2. HBAnyware Web Launch is removed. Press any key to continue. In Solaris LPFC, Solaris emlxs (SFS) and Linux: 1. Log on as ‘root’.
In Linux (also uninstalls the application helper module): 1. Log on as ‘root’. 2. Change (use the cd command) to the directory to which you copied the tar file during installation. 3. Uninstall any previously installed versions. Type: ./uninstall In VMware ESX Server (uninstalls the HBAnyware Agent): 1. Log in as ‘root’. 2. Type: rpm -qa | grep elx 3. Locate the .rpm file. The .rpm contents are installed in /usr/sbin/hbanyware. The hbacmd utility is also located in this directory. 4.
Using the HBAnyware Components Note: To properly view the HBAnyware utility, ensure your system meets the following display requirements: For Windows systems the display resolution must be set to 800 by 600 or better. For UNIX systems the display resolution must be set to 1024 by 768 or better. The display must run in 256-color mode or higher. HBAnyware icons use 256 colors. If the display is set for 16 color mode, HBAnyware icons will not be displayed.
• If you are running the HBAnyware Security Configurator with TCP/IP access, TCP/IP hosts must be added to the discovery-tree or they will not be seen by the Security Configurator. Note: When you install the HBAnyware utility security software on a system and run the HBAnyware utility Security Configurator for the first time, that system becomes the Master Security Client (MSC). For more information, see “Creating the Access Control Group” on page 100.
The HBAnyware Utility Window Element Definitions The HBAnyware utility window contains five basic components: the menu bar, the toolbar, the discoverytree, the property tabs and the status bar. Figure 3: HBAnyware Utility window Note: The element you select in the discovery-tree determines whether a menu item or toolbar icon is active. For example, if you select the local host or other system host, the Reset Adapter item on the Adapter menu is unavailable.
The Menu Bar The menu bar contains command menus that enable you to perform a variety of tasks such as exiting the HBAnyware utility, resetting HBAs and sorting items in the discovery-tree view. Many of the menu bar commands are also available from the toolbar. The Toolbar Many of the toolbar functions are also available from the menu bar. The toolbar is visible by default. Use the Toolbar item in the View menu to hide the toolbar. If the item is checked, the toolbar is visible.
The Discovery-Tree The discovery-tree (left pane) has icons that represent discovered network (SAN) elements (local host name, system host names and all HBAs active on each host). Targets and LUNs are also displayed. Figure 5: Discovery-tree Discovery-Tree Icons Discovery-tree icons represent the following: This icon represents the local host. This icon represents other hosts connected to the system. A green HBA icon with black descriptive text represents an online HBA.
The Tape LUN icon represents LUNs that are tape devices. The Target Controller LUN icon represents LUNs that are storage controllers. The Switch icon represents connections to the switch. Property Tabs The property tabs display configuration, statistical and status information for network elements. The set of available tabs is context-sensitive, depending on the type of network element or HBA currently selected in the discovery-tree.
Changing Management Mode During installation you selected a management mode, however you can change it if you enabled that option during installation. The HBAnyware utility enables you to choose three types of host/HBA management: • Strictly Local Management - This setting only allows management of HBAs on this host. Management of HBAs on this host from other hosts is not allowed.
Resetting HBAs You can reset remote and local HBAs. Caution: Do not reset your HBA while copying or writing files. This could result in data loss or corruption. To reset the HBA: 1. In the discovery-tree, select the HBA you want to reset. 2. Do one of the following: • From the menu bar, click Adapter, and then click Reset Adapter. • Click the Reset HBA button: . The following warning appears: Figure 7: Reset Warning 3. Click Yes. The HBA resets. The reset may require several seconds to complete.
Changing HBA Names The HBAnyware utility enables you to change HBA names. For example, you may want to identify a particular HBA with the function it supports, such as a tape drive, scanner, or some other device. Use any characters you want for names, and names can be up to 255 characters in length. You may also revert to the HBA's default name if you wish. Note: Although you can change the HBA's displayed name from the default WWPN, the change occurs in the discovery-tree only.
Discovering HBAs Automatic Fibre Channel Discovery HBAs that have a physical FC connection to the same SAN are discovered automatically when HBAnyware is launched. HBAs that don't have a physical FC connection to the SAN where HBAnyware is launched can be discovered by sending management requests to a remote host using TCP/IP. Note: The HBAnyware utility can only discover and manage remote HBAs on hosts running the HBAnyware utility’s remote management server.
The principle differences between FC and TCP/IP access are: • A TCP/IP host with an HBA installed does not need to connect to a fabric to manage other hosts. • A TCP/IP management host can manage all of the HBAs in a remote host, not just the ones connected to the same fabric. FC can only manage HBAs connected to the same fabric. • You can manage many more hosts since TCP/IP access is not constrained by the boundaries of a fabric or zoning. • True board status (e.g.
Figure 11: Add Range of IP Hosts dialog box To add a range of hosts: 1. From the Discovery menu, select TCP/IP>Add Range of Hosts. The Add Range of IP Hosts dialog box appears. 2. Enter the complete start and end address range and click Add. The added address range appears in the dialog box. Add any additional ranges you wish to search. 3. Click Start Discovery. The utility checks each address in the range to determine if the host is available and remotely manageable.
Removing Hosts Removing hosts that can no longer be discovered improves the operation of the discovery server. For example, you may want to remove a host when it is removed from the network or detect hosts that are no longer being discovered. To remove hosts: 1. From the Discovery menu, select TCP/IP>Remove Host(s). The Remove TCP/IP Hosts dialog box shows a list of discovered hosts. Any host not currently discovered appears in red.
Sorting HBA Information You can sort discovered HBAs by host name, fabric ID, HBA name, target name and LUN number. You can also view local or remote HBAs. By default, both local and remote HBAs are sorted by host name. To sort HBAs, switch between host name or fabric ID in one of two ways: • From the menu bar: click View, then click Sort by Host Name or Sort by Fabric ID. • From the toolbar, click one of the following buttons: • Sort HBAs by Host Name (default) • Sort HBAs by Fabric ID . .
Viewing HBA Information Viewing Discovery Information Discovery Information contains a general summary of the discovered elements. The Host or Fabric icon, depending upon which view you select, is the root of the discovery-tree, but it does not represent a specific network element. Expanding it reveals all hosts, LUNs, targets and HBAs that are visible on the SAN. To view the discovery information: 1. Click the Host or Fabric icon at the root of the discovery-tree.
Viewing Host Information There are two tabs that show host information: the Host Information tab and the Driver Parameters tab. The Host Information tab is read-only. The Driver Parameters tab enables you to view and define HBA driver settings for a specific host. To view the Host Information and Driver Parameters tabs: 1. Do one of the following: • From the menu bar, click View, then click Sort by Host Name. • From the toolbar, click the Sort by Host Name button: . 2.
The Driver Parameters Tab The Driver Parameters tab enables you to view and edit the HBA driver settings contained in a specific host. The host driver parameters are global values and apply to all HBAs in that host unless they are overridden by parameters assigned to a specific HBA using the HBA Driver Parameters tab.
Viewing General HBA Attributes The General tab contains general attributes associated with the selected HBA. To view general attributes: 1. Select Host or Fabric sort. 2. Select an HBA in the discovery-tree. Figure 16: General tab General Field Definitions Adapter Summary Area • Model - The complete model name of the HBA. • Port WWN - The Port World Wide Name of the HBA. • Node WWN - The Node World Wide Name of the selected HBA.
• HBA Temperature - If supported by the selected HBA, this field displays the HBA's temperature and one of the following temperature-related status messages: • Normal: The HBA temperature is within normal operational range. • Exceeded operational range - Critical: The HBA temperature is beyond normal operational range. If the temperature continues to increase, the HBA will shut down. You must determine the cause of the temperature problem and fix it immediately. Check for system cooling issues.
3. Select the Adapter Details tab. Figure 17: Adapter Details tab Adapter Details Field Definitions Adapter Details Area • Symbolic Node Name - The FC name used to register the driver with the name server. • Hardware Version - The JEDEC ID board version of the selected HBA. • Serial Number - The manufacturer assigned serial number of the selected HBA. • Discovered Ports - Counts the number of mapped and unmapped ports found during discovery by the Emulex HBA driver.
Loop Map Area • The loop map shows the different ports present in the loop, and is present only if the port (HBA) is operating in loop mode. The simplest example would be to connect a JBOD directly to an HBA. When this is done, the port type will be a private loop, and the loop map will have an entry for the HBA, and one entry for each of the disks in the JBOD. Viewing Fabric Information Discovery Information contains information about the selected fabric. To view the fabric information: 1.
Viewing Target Information Target Information contains information specific to the selected storage device. To view target information: 1. Do one of the following: • From the menu bar, click View, then click Sort by Host Name. • From the toolbar, click the Sort by Host Name button: . 2. Click a target in the discovery-tree. The Target Information tab appears.
Viewing LUN Information LUN Information contains details about the selected LUN. To view the LUN information: 1. Do one of the following: • From the menu bar, click View, then click Sort by Host Name. • From the toolbar, click the Sort by Host Name button: . 2. Select a LUN in the discovery-tree. Figure 20: LUN Information LUN Information Field Definitions • • • Vendor Product Information Area • Vendor Name - The name of the vendor of the LUN.
Masking and Unmasking LUNs (Windows, Solaris LPFC and Solaris emlxs (SFS)) LUN masking refers to whether or not a LUN is visible to the operating system. A LUN that has been masked is not available and is not visible to the OS. You can use HBAnyware to mask or unmask LUNs at the host level. Note: In Solaris systems, the Emulex LPFC drivers support both a target level and HBA level LUN unmasking override feature.
To change the mask status of a LUN: 1. From the discovery-tree, click on a SCSI target. A set of LUNs appears below the selected SCSI target. The LUN Masking tab is displayed. This tab contains a list of the same set of LUNs appear below the SCSI target. Figure 22: LUN Masking tab 2. In the LUN list of the LUN Masking tab, select one or more LUNs. The LUN Masking tab buttons become active as is appropriate.
3. Click the Statistics tab. Figure 23: Statistics tab Port Statistics Field Definitions • Tx Frames - FC frames transmitted by this HBA port. • Tx Words - FC words transmitted by this HBA port. • Tx KB Count - FC kilobytes transmitted by this HBA port. • Tx Sequences - FC sequences transmitted by this HBA port. • LIP count - The number of loop initialization primitive (LIP) events that have occurred for the port. This field is not supported if the topology is not arbitrated loop.
• Rx Words - The number of FC words received by this HBA port. • Rx KB Count - The received kilobyte count by this HBA port. • Rx Sequences - The number of FC sequences received by this HBA port. • NOS count - This statistic is currently not supported for the SCSIport Miniport and Storport Miniport drivers, nor is it supported for arbitrated loop. • Dumped Frames - This statistic is not currently supported for the SCSIport Miniport driver, the Storport Miniport driver or the driver for Solaris.
Firmware Field Definitions • • Firmware Area • Current Firmware Version - The Emulex firmware version number for this model of HBA. • Operational Firmware Name - If visible, the name of the firmware that is operational. • Initial Firmware - The firmware version stub responsible for installing SLI code into its slot. • SLI-1 Firmware Name - The name of the SLI-1 firmware overlay. • SLI-2 Firmware Name - The name of the SLI-2 firmware overlay.
Target Mapping Field Definitions Current Settings Area • Active Bind Type - WWPN, WWNN, or a destination identifier (D_ID). • Automapping - The current state of SCSI device automapping: enabled (default) or disabled. Current Mappings Area • This table lists current mapping information for the selected HBA. Persistent Binding Configuration Area • This table lists persistent binding information for the selected HBA. Display Mode Radio Buttons • Show WWPN, Show WWNN or Show D_ID.
3. Select the Target Mapping tab. Figure 26: Target Mapping tab Target Mapping Field Definitions Current Settings Area • Active Bind Type -N/A • Automapping - N/A Current Mappings Area • This table lists current mapping information for the selected HBA. Persistent Binding Configuration Area • N/A Display Mode Radio Buttons • N/A Target Mapping Buttons • N/A Viewing and Setting Up Authentication (Windows, Linux 8.
To enable DH-CHAP using the Drivers Parameters tab, enable the enable-auth parameter (in Windows), the auth-mode parameter (in Solaris LPFC) or lpfc-enable-auth (in Linux 8.2). Figure 27: Authentication tab Authenticate Tab Field Definitions • Source - The HBA identifier WWPN of the HBA port) • Destination - The fabric switch name. Configuration Data Area • Mode - The mode of operation. There are three modes: Enabled, Passive and Disabled.
• Hash Priority - The priority of the two supported hash algorithms (MD5 and SHA1) that the driver (HBA) presents during the DH-CHAP authentication negotiation with the switch (default is MD5 first, then SHA1.) Viewing or Changing Authentication Configuration To view or change authentication configuration: 1. In the discovery tree, click the HBA. 2. Select the Authenticate tab. The Authenticate tab is displayed.
Updating Firmware Prerequisites • The Emulex driver is installed: • The HBAnyware utility is installed. • The firmware zip file is downloaded from the Emulex Web site, unzipped and extracted to a folder on a local drive. • If the HBA is already connected to a boot device, the system is in a state in which this type of maintenance can be performed: • I/O activity on the Bus has been stopped. • Cluster software, or any other software that relies on the HBA to be available, is stopped or paused.
4. In HBAnyware versions 3.0 or later, after you click Update Firmware, the Firmware Download dialog box appears (Figure 29). Figure 29: Firmware Download dialog box for Windows 5. For all versions of HBAnyware, use the Firmware Download dialog box to navigate to the unzipped, extracted image file you want to download. 6. Select the file and click Start Download (version 3.0 or later) or OK (versions earlier than 3.0).
3. Navigate to the extracted boot code image file you want to download. Boot code images have a .prg extension. Select the boot code file and click Open. A tree-view shows all HBAs, and their corresponding hosts, that are compatible with the selected boot code file (Figure 30). Figure 30: Selecting HBAs to Update screen for Windows 4. Click the box next to an HBA to select or remove the HBA from the batch process.
download fails, the entry changes to red and failure information appears at the bottom of the screen. Figure 31: Download Complete screen for Windows 6. When downloading is finished, click Print Log to print a hard copy of the activity log. Note: Printing is not supported in Linux. 7. Click Close to exit the batch procedure. 8. Click Close. 9. Repeat steps 2 through 8 to update boot code on additional HBAs.
Enabling or Disabling an HBA’s BIOS Enabling the BIOS is a two-step process: 1. Enable the HBA BIOS (x86 BootBIOS, FCode or EFIBoot) to read the Emulex boot code on the HBA. 2. Enable the HBA to boot from SAN (using the BIOS utility). The Emulex boot code must be downloaded from the Emulex Web site and extracted to a local drive before you can perform this procedure. To enable or disable the HBA BIOS: 1. In the discovery-tree, select the HBA. 2. Select the Firmware tab.
Configuring the Driver In Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux: Set driver parameters using the HBAnyware utility. In Solaris LPFC, Solaris emlxs (SFS) and Linux:, you can also specify parameters when loading the driver manually. See the appropriate driver manual for instructions. Setting Driver Parameters The Driver Parameters tab and host Driver Parameter tab enable you to modify driver parameters for a specific HBA or all HBAs in a host.
3. Select the Driver Parameters tab. The parameter values for the selected HBA are displayed. Figure 33: Driver Parameters tab - HBA Selected 4. In the Driver Parameters tab, click the parameter that you want to change. A description of the parameter appears on the right side of the tab. 5. Enter a new value in the Value field in the same hexadecimal or decimal format as the current value. If the current value is in hexadecimal format, it is prefaced by "0x" (for example, 0x2d).
Setting an HBA Parameter Value to the Host Parameter Value To set an HBA parameter value(s) to the corresponding host parameter value(s): 1. In the discovery-tree, select the HBA. 2. Select the Driver Parameters tab. 3. Click Globals. All parameter values are now the same as the global, or host, values. 4. To apply the global values, click Apply. Saving HBA Driver Parameters to a File To save HBA driver parameters, click Save (or Save Settings).
Figure 34: Driver Parameters tab - Host Selected 5. Enter a new value in the Value field in decimal or hexadecimal format, depending on how the current value is presented. If the value is in hexadecimal format, it is prefaced by "0x" (for example” 0x2d”). 6. To make a change temporary (the parameter to revert to its last permanent setting when the system is rebooted), check the Make changes temporary box. This option is available only for dynamic parameters. 7.
Creating and Assigning a Batch Mode Driver Parameters File You can apply driver parameters for one HBA to other HBAs in the system using the Driver Parameters tab. When you define parameters for an HBA, you create a .dpv file. The .dpv file contains parameters for that HBA. After you create the .dpv file, the HBAnyware utility enables you to assign the .dpv file parameters to multiple HBAs in the system. To create and assign the .dpv file: 1.
8. The two radio buttons allow you to choose the type of parameters to save. You can save all parameters or only those parameters whose current values differ from their corresponding default values. A list of the saved parameters and their current values show in the Saved Parameters box. 9. Click Save. 10. Assign batch mode parameters to HBAs: From the Batch menu select Update Driver Parameters. (You do not need to select any discovery-tree elements at this time.
Storport Miniport Driver Parameters The parameter values listed in Table 1 are applicable to driver version 2.00 or later. If you are using a version previous to 2.00, see the Storport Miniport Driver User Manual for parameter information. Activation Requirements A parameter has one of the following activation requirements: • Dynamic - The change takes effect while the system is running. • Reset - Requires an HBA reset from the utility before the change takes effect.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definitions CoalesceRspCnt=n CoalesceRspCn specifies the number of response entries that trigger an Interrupt response. Activation Requirement Reset Value: 0 - 255 (decimal) or 0x1 - 0xFF (hex) Default = 8 (0x8) DiscoveryDelay=n DiscoveryDelay controls whether the driver waits for ‘n’ seconds to start port discovery after link up. Dynamic If set to 0 = immediate discovery after link up.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definitions Activation Requirement HardALPA=0xn HardALPA allows the HBA to use a hard assigned loop address. Reset Value: 0x00 - 0xEF (hex) Default = 0x00 (use soft addressing, or flash stored hard address value) Note: Only valid AL_PAs may be used. InitTimeout=n Determines the number of time-out seconds during driver initialization for the link to come up.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definitions LogErrors=n LogErrors determine the minimum severity level required to enable entry of a logged error into the system event log. Errors are classified as severe, malfunction or command level. A severe error requires user intervention to correct a firmware or HBA problem. An invalid link speed selection is an example of a severe error.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definitions PciMaxRead PciMaxRead enables override of default PCI read transfer length. The driver will auto-detect the presence of an AMD PCI bridge and adjust for this bridge. This parameter allows for override of the automatic value. Activation Requirement Reset Value: 512, 1024, 2048 and 4097 Default: 2048 RmaDepth=n RmaDepth sets the remote management buffer queue depth.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definitions TraceBufSiz=n TraceBufSiz sets the size in bytes for the internal driver trace buffer. The internal driver trace buffer acts as an internal log of the driver's activity. Activation Requirement Reboot Value: 250,000 - 2,000,000 or 0x3D090 - 0x1E8480 (hex). Default = 250,000 (0x3D090) Table 2: Storport Miniport Topology Reference Topology Description Value Private Loop Operation Only FC-AL topology is used.
Driver for Solaris LPFC – Configuration File Reference The parameter values listed in Table 3 are applicable to driver version 6.20i or later. If you are using a version previous to 6.20i, see the Emulex Driver for Solaris User Manual for parameter information. Note: The fcp-bind-WWNN, fcp-bind-WWPN and fcp-bind-DID driver properties do not apply to a specific HBA. They are the global properties. These properties specify a list of persistent bindings.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments auth-cfgparms Controller Specific Description and Values: This is the DH-CHAP related driver property for FC-SP support. It is only valid when driver property enable-auth is set to 1. This driver property is ignored when enable-auth is set to 0. The format of this property is: "LWWN|RWWN|atov|amod|dir|tlist|hlist|dhgplist|raintval" LWWN: The WWPN of the local entity, i.e. HBA port.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments auth-keys Controller Specific Description and Values: This is the DH-CHAP authentication key driver property for FC-SP support. It is only valid when driver property enable-auth is set to 1. This driver property is ignored when enable-auth is set to 0. The format of this property is: "LWWN:ktype:klength:key:RWWN:ktype:klength:key" LWWN: The WWPN of the local entity, i.e. HBA port.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments cr-count Controller Specific 1 1 255 No This value specifies a count of I/O completions after which an interrupt response is generated. This feature is disabled if cr-delay is set to 0. cr-delay Controller Specific 0 0 63 No This value specifies a count of milliseconds after which an interrupt response generated if cr-count has not been satisfied.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments dqfull-throttle-upinc Controller Specific 1 0 128 Yes Amount to increment LUN queue depth each time. This driver property causes the LPFC driver to decrement a LUN’s queue depth, if a queue full condition is received from the target. The queue depth will be decremented down to a minimum of 1.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments dqfull-throttle-uptime Controller Specific 1 0 30 Yes Time interval (seconds) to increment LUN queue depth. This driver property causes the LPFC driver to decrement a LUN’s queue depth, if a queue full condition is received from the target. The queue depth will be decremented down to a minimum of 1.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments extra-io-tmo Controller Specific 0 0 255 Yes Extra timeout value, in seconds, to be applied to each FCP command sent. When connecting through a large fabric, certain devices may require a longer timeout value. fcp-bind-DID Global Inactive N/A N/A No Setup persistent FCP bindings based on a target device’s Port ID.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments fcp-bind-WWNN Global Inactive N/A N/A No Setup persistent FCP bindings based on a target device’s WWNN. This binding guarantees that target assignments will be preserved between reboots. The format for a bind entry is “NNNNNNNNNNNNNNNN:lpf cXtY” where NNNNNNNNNNNNNNNN is a 16 digit representation of the targets WorldWide Node Name, X is the driver instance number and Y is the target assignment.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments fdmi-on Global 0 0 2 No This driver property controls the FDMI capability of the LPFC driver. If set to 0 (default), FDMI is disabled. A value of 1 enables FDMI without registration of host name port attribute, while a value of 2 enables FDMI with registration of host name port attribute. ip-class Controller Specific 3 2 2 Yes FC is capable of transmitting IP data in Class2 or Class 3.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments log-verbose Controller Specific 0x0 0x0 0xffff Yes (bit mask) When set to nonzero this variable causes LPFC to generate additional messages concerning the state of the driver and the I/O operations it carries out. These messages may go to the system log file, /var/adm/messages and/or the system console. See Error Messages for detailed information on the bit mask.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments lun-queue-depth Global 30 1 128 No The driver uses this value as the default limit for the number of simultaneous commands to issue to a single logical unit on a single target on the loop. A single logical unit will never be sent more commands than allowed by lun-queue-depth; however, less may be sent when sd-max-throttle or tgt-queue-depth is reached for the entire target.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments nodev-holdio Controller Specific 0 0=Off 1=On Yes This variable controls if I/O errors are held by the driver if a FCP device on the SAN disappears. If set, I/O errors will be held until the device returns back to the SAN (potentially indefinitely). This driver property is ignored, if SCSI commands are issued in polled mode. The upper layer may retry the command once the error is returned.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments num-iocbs Controller Specific 256 128 10240 No This variable indicates the number of Input/Output Control Block (IOCB) buffers to allocate. IOCBs are internal data structures used to send and receive I/O requests to and from the LightPulse hardware. Too few IOCBs can temporarily prevent the driver from communicating with the HBA, thus lowering performance. (This condition is not fatal.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min topology Controller Specific 0x0 use-adisc Controller Specific xmt-que-size Controller Specific Dynamic Comments 0x0=loop , then P2P 0x2=P2P only 0x4=loop only 0x6=P2P, then loop No This variable controls the FC topology expected by LPFC at boot time. FC offers point-topoint, fabric, and arbitrated loop topologies.
Driver For Solaris emlxs (SFS) Driver Parameters • The emlxs.conf file contains all the parameters necessary to initialize the Solaris emlxs (SFS) driver. • The HBAnyware utility reflects the Solaris emlxs (SFS) driver parameters. The parameter values listed in Table 4 are applicable to driver versions 1.30/2.30 or later. If you are using the SFS driver version 1.22/2.22, see the HBAnyware Utility, version 3.3 User Manual.
Table 4: emlxs.conf Parameters (Continued) Property Name auth-cfgs Default Min Max Activation Comments Description and Values: This is the DH-CHAP related driver property for FC-SP support. It is only valid when driver property enable-auth is set to 1. This driver property should be ignored when enable-auth is set to 0. This property represents a table of entries.
Table 4: emlxs.conf Parameters (Continued) Property Name Default auth-cfgs (continued) However, since the parameter represents a table of entries the table can represent all entries across all HBA instances. This allows all HBA instances to share a common table of entries. auth-keys Description and Values: This is the DH-CHAP authentication key driver property for FC-SP support. It is only valid when driver property enable-auth is set to 1.
Table 4: emlxs.conf Parameters (Continued) Property Name Default Min Max Activation Comments cr-count 1 1 255 Requires link reset. This value specifies a count of I/O completions after which an interrupt response is generated. This feature is disabled if cr-delay is set to 0. cr-delay 0 0 63 Requires link reset. This value specifies a count of milliseconds after which an interrupt response generated if cr-count has not been satisfied.
Table 4: emlxs.conf Parameters (Continued) Property Name Default Min Max Activation Comments num-nodes 0 0 4096 Requires HBA reset. Number of FC nodes (NPorts) the driver will support. pci-max-read 2048 512 4096 Requires HBA reset Sets the PCI-X max memory read byte count [512, 1024, 2048 or 4096] pm-support 0. 0 1 Requires reboot. Enable/Disable power management support in the driver. 0 = Disables power management support in the driver.
Solaris emlxs (SFS) and Solaris LPFC Driver Parameter Cross-Reference The cross-reference information listed in Table 5 is applicable to the Driver for Solaris LPFC version 6.20i and the Driver for Solaris emlxs (SFS) version 1.30/2.30. If you are using Solaris emlxs (SFS) version 1.22.2.22 see the HBAnyware Utility version 3.3 User manual. If you are using a Solaris LPFC or Solaris emlxs (SFS) driver version previous to these listed, see the appropriate User Manual for parameter information.
Table 5: Solaris emlxs (SFS) and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris emlxs/ HBAnyware Property Solaris emlxs/HBAnyware Min/Max, Defaults and Description Related LPFC Property This is the DH-CHAP related driver property for FC-SP support. It is only valid when driver property enable-auth is set to 1. This driver property is ignored when enable-auth is set to 0. authcfgparms This is the DH-CHAP authentication key driver property for FC-SP support.
Table 5: Solaris emlxs (SFS) and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris emlxs/ HBAnyware Property Solaris emlxs/HBAnyware Min/Max, Defaults and Description Related LPFC Property cr-delay Min:0 Max:63 Default:0 Description: Specifies a count of milliseconds after which an interrupt response is generated if the cr-count has not been satisfied. This value is set to 0 to disable the Coalesce Response feature as default.
Table 5: Solaris emlxs (SFS) and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris emlxs/ HBAnyware Property Solaris emlxs/HBAnyware Min/Max, Defaults and Description Related LPFC Property log-notices Min: 0x00000000 Max:0xFFFFFFFF Default: 0x0000000 Verbose mask for notice messages to the messages file.
Table 5: Solaris emlxs (SFS) and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris emlxs/ HBAnyware Property Solaris emlxs/HBAnyware Min/Max, Defaults and Description Related LPFC Property num-iocbs Min:128 Max:10240 Default = 1024 Description: Sets the number of iocb buffers to allocate. num-bufs Min:128 Max:10240 Default = 256 Description: Specifies the number of command buffers to allocate.
Table 5: Solaris emlxs (SFS) and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris emlxs/ HBAnyware Property Solaris emlxs/HBAnyware Min/Max, Defaults and Description Related LPFC Property topology 0 = loop, if it fails attempt ptto-pt 2 = pt-to-pt only 4 = loop only 6 = pt-to-pt, if it fails attempt loop Default: 0 Description: Link topology for initializing the FC connection. Set pt-to-pt if you want to run as an N_Port. Set loop if you want to run as an NL_Port.
Driver for Linux Parameter Tables The driver parameter values listed in Table 6, Table 7 and Table 8 are applicable to driver version 8.0.16.34. If you are using a version previous to 8.0.16.34, see the Emulex Driver for Linux User Manual for parameter information The driver parameters listed in Table 9 and Table 10 are applicable to driver version 8.2. Driver for Linux version 8.2 supports DH-CHAP authentication and configuration. Version 8.
Table 6: Driver for Linux, LPFC Static Parameters (Requires a driver reload to change) (Continued) Variable Default Min Max Comments lpfc_discovery_threads 32 1 64 Specifies the maximum number of ELS commands that can be outstanding for a discovery. Visible using sysfs No Note: The discovery_threads parameter will default to a value of 64 for private loop topologies regardless of the configured value.
Table 6: Driver for Linux, LPFC Static Parameters (Requires a driver reload to change) (Continued) Visible using sysfs Variable Default Min Max Comments lpfc_fcp_bind_method 2 1 4 Specifies method of binding each port. Values: 1: WWNN binding 2: WWPN binding 3: D_ID binding 4: ALPA binding Yes lpfc_fdmi_on 0 0 2 False (0) if disabled. (1) or (2) if enabled depending on type of support needed. Yes lpfc_scan_down 1 0=Off 1=On Select method for scanning ALPA to assign a SCSI ID.
Table 8: LPFCDFC Driver for Linux, Static Parameters Variable Default Min Max Comments lpfc_scsi_req_tmo 30 0 255 Time out value (in seconds) for SCSI request sent through lpfcdfc module. (Not available using HBAnyware GUI. Command line only.) Version 8.2 LPFC and LPFCDFC Parameter DH-CHAP Authentication and Configuration The Emulex driver for Linux version 8.2.0.x supports the FC-SP/Authentication DH-CHAP (DiffieHellmann Challenge Handshake Authentication Protocol).
fcauth Daemon Parameters The fcauth daemon supports the following parameters: • start - To start the fcauthd daemon pass the start command to the fcauthd script. This command loads the daemon into memory, opens a netlink for the driver to connect to, and reads the authentication configuration database into memory for use by the LPFC driver. • stop - To stop the fcauthd daemon pass the stop command to the fcauthd script.
Table 9: lpfc Static Parameters (Requires a driver reload to change) (Continued) Variable Default Min Max Comments lpfc_discovery_threads 32 1 64 Specifies the maximum number of ELS commands that can be outstanding for a discovery. Visible using sysfs No NOTE: The discovery_threads parameter will default to a value of 64 for private loop topologies regardless of the configured value.
Table 9: lpfc Static Parameters (Requires a driver reload to change) (Continued) Visible using sysfs Variable Default Min Max Comments lpfc_max_luns 256 1 32768 Specifies the maximum number of LUN IDs per target. A value of 20 means LUN IDs from 0 to 19 are valid. The SCSI layer will scan each target until it reaches the specified LUN ID. Yes lpfc_multi_ring_support 1 1 2 Determines the number of primary SLI rings over which to spread IOCB entries.
Table 10: lpfc Dynamic Parameters (Do not require a driver reload to change) (Continued) Variable Default Min Max Comments lpfc_use_adisc 0 0=Off 1=On Sends ADISC instead of PLOGI for device discovery or RSCN. Driver for VMware ESX Configuration Parameters All HBA-specific parameters have an lpfcX_ prefix (where X is the driver instance number); e.g.
Table 11: Driver for VMware ESX Configuration Parameters (Continued) Variable Default Min Max Dynamic Comments lpfc_fcp_bind_DID inactive N/A N/A No Bind specific SCSI IDs to targets based on FC Port ID. lpfc_fcp_bind_method 2 1 4 No Specifies the bind method (WWWN/WWPN/DID/ALPA map) to be used. lpfc_fcp_bind_WWNN inactive N/A N/A No Bind specific SCSI IDs to targets based on FC WWNN. lpfc_fcp_bind_WWPN inactive N/A N/A No Bind specific SCSI IDs to targets based on FC WWPN.
Table 11: Driver for VMware ESX Configuration Parameters (Continued) Variable Default Min Max Dynamic Comments lpfc_max_vpi 0xffff 0 0xffff No NPIV: Maximum number of vpis available per physical port. lpfc_nodev_holdio 0 0=Off 1=On Yes If the device disappears, hold I/O until it comes back. lpfc_no_device_delay 1 0 30 Yes Delay to fail back an I/O in seconds. lpfc_nodev_tmo 30 0 255 Yes Seconds to hold I/O err if device disappears.
Server Performance (Windows) I/O Coalescing I/O Coalescing is enabled and controlled by two driver parameters: CoalesceMsCnt and CoalesceRspCnt. The effect of I/O Coalescing will depend on the CPU resources available on the server. With I/O Coalescing turned on, interrupts are batched, reducing the number of interrupts and maximizing the number of commands processed with each interrupt. For heavily loaded systems, this will provide better throughput.
NumFcpContext If the number of outstanding I/Os per HBA is expected to exceed 512, increase this parameter to a value greater than the number of expected I/Os per HBA. Increase this value in stages: from 128 to 256 to 512 to 1024 to a maximum of 2048i. NumFcpContext limits the number of outstanding I/Os per HBA, regardless of how QueueDepth is set. The NumFcpContext defaults to 512.
5. If you need to make changes to multiple parameters, and you want all the changes temporary, check Make all changes temporary box. Only dynamic parameters can be temporary. 6. To apply your changes, click Apply. 7. Reboot the system for this change to take effect. Mapping and Masking Defaults (Windows) Table 13 describes LUN mapping and masking global defaults.
2. Select the Target Mapping tab. All targets are displayed. Figure 38: Target Mapping tab 3. Target mappings are displayed by WWPN, WWNN, or D_ID. “PB”, indicates mapping from persistent binding, while “Auto”, indicates an automapped target. In the Display Mode section, choose the display mode you want to use. 4. Change Setting - Click to change the active bind type (the mode used to persistently bind target mappings), LUN automapping or LUN unmasking settings.
4. Select the Bus ID and target ID that you want to bind, and click OK. Note: Automapped targets have entries only in the second column of the Targets Table. Persistently bound targets have entries in the second and third columns. In this case, the third column contains the SCSI Bus and target numbers you specified in the Add Persistent Binding dialog box. This binding takes effect only after the local machine is rebooted.
HBAnyware Security Introduction After you install the base HBAnyware software, which includes the HBAnyware utility and remote server, on a group of systems, the HBAnyware utility on any of those systems can remotely access and manage the HBAs on any systems in the group. This may not be a desirable situation, because any system can perform actions such as resetting boards or downloading firmware.
3. Select the unsecured servers that you want to add to the ACG from the Available Servers list. Figure 42: Access Control Group tab with ACG Servers 4. Click the left arrow to add the servers to the Access Control Group Servers list. 5. Click Apply. Designating a Master Security Client The first time you run the HBAnyware Security Configurator on any system in a FC network, that system becomes the MSC (Master Security Client).
Access Control Group Tab on the MSC On the MSC, you select or deselect the systems that are to be part of the security installation in the Access Control Group tab. When you select unsecure systems and move them to the Access Control Group Servers list, these systems updates to secure them and bring them into the MSC's ACG. When you select systems in the ACG and move them to the Available Servers list, the security configuration for those systems update to make them unsecure.
Access Control Group Tab on a Non-MSC On a non-MSC system, the Access Control Group tab shows the systems that are part of the client's ACG. You cannot modify the ACG on a non-MSC. (You can modify the ACG only on the MSC or a client higher in the security topology's hierarchy.) The ACG tab on a non-MSC system looks similar to the following: Figure 44: Access Control Group tab on a Non_MSC System ACG Icons Depending on the configured security topology, a system can be a server in one or more ACGs.
Adding a Server to the ACG After you create the initial Access Control Group (ACG) on the Master Security Client (MSC), you may add unsecured servers to the ACG. To add servers to the ACG: 1. On the Access Control Group tab, from the Available Servers list, select the unsecured servers to add to the ACG (Figure 43). 2. Click the left arrow to add the server to the Access Control Group Servers list. 3. Click Apply. Deleting a Server from the ACG To delete a server from the Access Control Group (ACG): 1.
Restoring the ACG to Its Last Saved Configuration You can restore the ACG to its last saved configuration, if there are unsaved changes to the ACG, only from the Master Security Client (MSC). To restore the ACG to its last saved configuration: From the Access Control Group tab on the MSC, click Restore (Figure 43). Accessing a Switch You can enable switch access only on a Master Security Client (MSC).
ASG Icons The following icons indicate the state of each of the servers in the Access Sub-Group Servers list. The system is a server in the ASG but not in any child ASGs. You can remove it from the ASG. The system is a server in the ASG and at least one child ASG. You cannot remove it from the ASG until you remove it from the child ASGs. The system is a server in the ASG and a client to a child ASG.
2. Click New. The New Access Sub-Group dialog box appears: Figure 47: New Access Sub-Group dialog box 3. Enter the ASG information: • Access Sub-Group Name: Enter the name of the ASG. The ASG name is for identification purposes only. It does not provide any security function. Provide a name that will make it easy to remember the systems that are part of the ASG. The name can contain any alphanumeric characters, symbols or spaces (up to 31).
Adding a Server to an ASG To add a server to an ASG: 1. Click the Access Sub-Group tab (see Figure 46 on page 106). 2. The name of the ASG appears in the Access Sub-Groups tree. From the Available Servers list, select the servers to add to the ASG. Note: TCP/IP accessed servers will appear in the Available Servers list even though the ASG client system may not have discovered them yet. These servers can still be added to the Access Sub-Group Servers list. 3.
3. Click Edit. The Edit Access Sub-Group dialog box appears:. Figure 48: Edit Access Sub Group dialog box 4. Change the ASG information: • Access Sub-Group Name: Change the name of the ASG. The ASG name is for identification purposes only. It does not provide any security function. Provide a name that is easy to remember the systems that are part of the ASG. The name can contain any alphanumeric characters, symbols or spaces (up to 31).
About Offline ASGs Sometimes a client system may not be online when the HBAnyware Security Configurator is running. In this case, the Access Sub-Group (ASG) for the client appears offline in the ASG tree, much like the following: Figure 49: Access Sub-Groups tab - Client System Offline The offline ASG entry serves as a placeholder for where the real ASG would be in the tree. You cannot modify or delete the entry (although it is removed from the display if all of its child ASGs are deleted).
Backup Masters Introduction A Backup Master mirrors the security data of the Master Security Client (MSC) in case it has to take over as the MSC if the MSC is unable to operate or is removed from the security configuration. A Backup master system receives all the updates to the security configuration on the MSC. However, you cannot make modifications to the security configuration on a Backup Master.
Backup Master Tab and Controls The first time you select the Backup Master tab on the MSC, it looks similar to the following: Figure 50: Backup Master tab - First Time Selected Creating a Backup Master To create a Backup Master: 1. On the Master Security Client (MSC), start the HBAnyware Security Configurator. 2. Click the Backup Master tab. Figure 51: Backup Master tab with Backup Masters 3. Select a system from the Available Systems list.
4. Click the left arrow to move the system to the Backup Masters list. 5. Click Apply to save your changes. Reassigning a Backup Master as the New MSC from the Old MSC Because a Backup Master may have to take over as the Master Security Client (MSC), it must be able to physically access all of the HBAs that the MSC can access. If the MSC connects to multiple fabrics, select its Backup Master from the Available Systems list connected to the same fabrics as the MSC.
3. Click Assign This System As The Master Client. A prompt asks if you want to continue. 4. Click Yes. A prompt notifies you that this system is now the new MSC. 5. Click OK. The Configurator closes. 6. Restart the HBAnyware Security Configurator to run the former Backup Master as the MSC.
Diagnostics Performing Diagnostic Tests Note: All diagnostic tests and diagnostic dumps can only be performed on the local system or on remote systems connected with TCP/IP access. Diagnostic tests and diagnostic dumps cannot be performed on remote systems connected with FC access. Note: Diagnostics are not available on VMware ESX Server.
Running a Quick Test The Diagnostics tab enables you to run a quick diagnostics test on a selected HBA. The Quick Test consists of 50 PCI Loopback test cycles and 50 Internal Loopback test cycles. To run a quick test: 1. From the discovery-tree, select the HBA on which you wish to run the Quick Test. 2. Select the Diagnostics tab and click Quick Test. A warning message appears. Figure 54: Quick Test Warning window 3. Click OK to run the test.
Creating Diagnostic Dumps The diagnostic dump feature enables you to create a “dump” file for a selected HBA. Dump files contain various information such as firmware version, driver version and so on, that is particularly useful when troubleshooting an HBA. Caution: Disruption of service may occur if a diagnostic dump is run during I/O activity. To start a diagnostic dump: 1. From the discovery-tree, select an HBA whose diagnostic information you wish to dump. 2.
Displaying PCI Registers and Wakeup Information A PCI Register dump for the selected HBA appears in the lower left panel of the Diagnostics tab. Wakeup information for the selected HBA appears in the lower right panel of the Diagnostics tab.
Test results and the status of running tests, are time stamped and appear in the Test Log area. Figure 57: Advanced Diagnostics Running Loopback Tests To run a loopback test, use the Loopback Test section of the Advanced Diagnostics dialog box.
Test Cycles Enables you to specify test cycles three ways: • Select an established cycle count by clicking on the corresponding radio button. • Enter a custom cycle count in the blank field in the Test Cycles area. • Set the test to run until you manually click Stop, by selecting the Infinite radio button. Test Pattern Enter a custom test pattern to be used in tests that transfer data. The test pattern can be up to 8 hexadecimal bytes.
Running End-to-End (ECHO) Tests Run echo tests using the End-to-End (ECHO) Test section of the Diagnostics tab. The end-to-end test enables you send an ECHO command/response sequence between an HBA port and a target port. Note: Not all remote devices respond to an echo command. You cannot run the ECHO test and the External Loopback test concurrently. If you select the ECHO Test the External Loopback test is disabled. To run end-to-end echo tests: 1.
5. Click OK. A result screen appears and the test results appear in the Test Log. Click Clear to erase the contents of the log display or click Save to File to save the log file. Saving the Log File You can save the test log to a log file for later viewing or printing. When new data is written to a saved file, the data is appended to the end of the file. Each entry has a two-line header that contains the identifier of the HBA being tested and the date and time of the test.
Using the HBAnyware Utility Command-Line Interface The Command Line Interface (CLI) Client component of the HBAnyware utility provides access to the capabilities of the Remote Management library from a console command prompt. This component is intended for use in scripted operations from within shell scripts or batch files. The CLI Client is a console application named hbacmd. Each time you run this application from the command line, a single operation is performed.
The CLI Client Command Reference CLI Client commands are supported for Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Only CLI Client commands that are dynamic are supported for VMware ESX Server. Note: The PersistentBinding, SetPersistentBinding, RemovePersistentBinding, RemoveAllPersistentBinding, BindingCapabilities, BindingSupport and SetBindingSupport commands are not supported for Linux.
SaveConfig Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Syntax: hbacmd SaveConfig Description: Saves the specified HBA’s driver parameters to a file. The resulting file will contain a list of driver parameter definitions in ASCII file format with definitions delimited by a comma. Each definition is of the form: = Saves either the values of the global set or those specific to the HBA.
TargetMapping Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS), Linux and VMware ESX Server. Syntax: hbacmd TargetMapping Description: Shows a list of mapped targets and the LUNs for the port. Parameters: WWPN - World Wide Port Name of the HBA whose target mapping you wish to view. Reset Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS), Linux and VMware ESX Server. Syntax: hbacmd Reset Description: Resets the HBA.
GetLunUnMaskbyTarget Supported by: Windows, Solaris LPFC and Solaris emlxs (SFS). Syntax: hbacmd GetLunUnMaskByTarget
PersistentBinding Supported by: Windows, Solaris LPFC and Solaris emlxs (SFS). Syntax: hbacmd PersistentBinding Description: Specifies which set of persistent binding information is requested: the configured or live state of any present binding. Parameters: WWPN - World Wide Port Name of the HBA whose persistent binding information you wish to specify. Source - C = Configuration, L = Live SetPersistentBinding Supported by: Windows, Solaris LPFC and Solaris emlxs (SFS).
RemovePersistentBinding Supported by: Windows, Solaris LPFC and Solaris emlxs (SFS). Syntax: hbacmd RemovePersistentBinding Description: Removes persistent binding between an FC target and a SCSI Bus and target. The binding to be removed can be to a target WWPN, target WWNN, or target D_ID. Parameters: WWPN - World Wide Port Name of the HBA whose persistent bindings you wish to remove.
DriverConfig Supported by: Windows, Solaris LPFC and Solaris emlxs (SFS). Syntax: hbacmd DriverConfig Description: Sets all driver parameters for the HBA to the driver parameter values contained in the specified .dpv file type. The .dpv file’s driver type must match the driver type of the host platform HBA. Parameters: WWPN - World Wide Port Name of the HBA whose driver parameters you wish to set. FileName - Name of the .
Parameters: WWPN - World Wide Port Name of the HBA whose driver parameters you wish to change. Flag1 - L = Make change local for this HBA only, G = Make change global (all HBAs on this host) Flag2 - P = Make change permanent (persists across reboot), T = Make change temporary Note: For VMware ESX Server, CtrlWord - P = Make change permanent, G = Make change global, B = Both, N = Neither. Because P and B are not supported on VMware ESX Server you can only use G or N. Param - Name of the parameter to modify.
SetAuthConfig Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Syntax: hbacmd SetAuthConfig Description: Sets the authentication configuration for the HBA. Parameters: WWPN1 - World Wide Port Name of the HBA whose authentication configuration you wish to set.
InitiateAuth Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Syntax: hbacmd InitiateAuth Description: Initiates the authentication configuration on the HBA. Parameters: WWPN1 - World Wide Port Name of the HBA whose authentication configuration you wish to initiate. WWPN2 - Must be ff:ff:ff:ff:ff:ff:ff:ff PCIData Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Syntax: hbacmd PCIData Description: Shows PCI configuration data for the HBA.
SetBeacon Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Syntax: hbacmd SetBeacon Description: Sets the current beacon status for the HBA. Parameters: WWPN - World Wide Port Name of the HBA whose beacon you wish to change. BeaconState - New state of the beacon: 0 = Off, 1= On PostTest Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Syntax: hbacmd PostTest Description: Runs the POST on the HBA.
Dump Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux. Syntax: hbacmd dump Description: Displays the maximum number of diagnostic dump files that be can stored for an HBA. Creates a diagnostic dump file in the hbacmd dump file directory. Parameters: WWPN - World Wide Port Name of the HBA whose dump information you wish to view. GetRetentionCount Supported by: Windows, Solaris LPFC, Solaris emlxs (SFS) and Linux.
Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains many of these circumstances and offers one or more workarounds for each situation. General Situations Table 14: General Situations Situation Resolution A Fibre Channel link fails to come up. If a Fibre Channel link fails to come up, verify that an 8-Gb HBA is not attempting to connect to a 1-Gb device. Only 2-Gb, 4-Gb and 8-Gb devices are supported on 8-Gb HBAs.
Table 14: General Situations (Continued) Situation Resolution SAN Management Workstation Does Not Have an FC Connection. The SAN management workstation does not have a physical FC connection into the SAN because the other management tools are all out-of-band. Can HBAnyware be run on this SAN management workstation? HBAnyware can communicate with remote HBAs using out-ofband access as long as the remote host is running HBAnyware. To solve this problem: 1. Start HBAnyware. 2.
Emulex Driver for Windows and HBAnyware Situations Table 15: Emulex Driver for Windows and HBAnyware Situations Situation Resolution lputilnt Installs, but HBAnyware Does Not. When you run setupapps.exe, lputilnt installs but HBAnyware does not. You have attempted to manually install the utilities for the driver before manually installing the driver Perform the installation tasks in the following order: 1. Install the driver (see the Installation section of the Storport User Manual). 2.
Table 17: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution In some cases, after loading an OEM supplied combined firmware/OpenBoot image you will not be able to enable BootBIOS from the lputil Boot BIOS Maintenance menu. If you encounter this problem after loading the OEM combined firmware/OpenBoot image, follow the steps outlined in the resolution. 1. Download the current OpenBoot only image for your adapter from the Emulex web site. 2.
Table 17: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution Loading lpfc or lpfcdfc driver on SLES 9 reports "unsupported module, tainting kernel" in system log. This message is logged by the SLES 9 kernel whenever a module which is not shipped with the kernel is loaded. This message can be ignored. rmmod of lpfc driver hangs and module reference count is 0. Due to a small race condition in the kernel it is possible for an rmmod command to hang.
Table 17: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution The HBAnyware software package will not install. An error message states that: "inserv Service Elxlpfc has to be enabled for service ElxDiscSrvinserv: exiting now/sbin/ inserv failed exit code 1." Reinstall the driver with the lpfc-install script. The Emulex driver for Linux does not load in ramdisk for a custom built kernel. Custom built kernels are not supported by Emulex.
Table 17: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution Cannot See Other HBAs or Hosts. Although HBAnyware is installed, only local host bus adapters (HBAs) are visible. The other HBAs and hosts in the SAN cannot be seen. All the HBAs in the SAN will be visible if: • The other servers have a connection to your zone of the SAN. Check fabric zoning. • The elxhbamgr processes are running on remote hosts (enter ps -ef | grep elxhbamgr).
Security Configurator Situations - Access Control Groups (ACG) Table 18: Access Control Groups Situations Situation Resolution All servers are not displayed. When I run the Security Configurator on the Master Security Client (MSC), I do not see all of the systems in available servers or ACG Servers lists. When I run the Security Configurator on a non-MSC, I do not see all of the systems I should see in the ACG Servers list.
Table 19: HBAnyware Security Configurator - Access Sub-Groups Situations (Continued) Situation Resolution In the ASG tree of the Access Sub-Groups tab, one or more of the names of the ASGs is displayed as "- ASG (Client Offline) -". The client system for the ASG was not discovered when the Configurator was started. This is actually a symptom of two different problems.
HBAnyware Security Configurator Situations - Backup Masters Table 20: HBAnyware Security Configurator - Backup Masters Situations Situation Resolution Cannot create a backup master. Select a system (or group of systems) from the MSC to be the Backup Master. The system must be either an unsecured system (which will be secured by being made a Backup Master), or a system that is not part of any ASG (client or server). These systems will mirror the MSC's security configuration.
Error Message Situations Table 21: Error Message Situations Situation Resolution The Access Sub-Group name already exists. Please use a different name. This message appears when you create an ASG. You entered a duplicate ASG name in the Access SubGroup Name field. At each level of the security topology, each ASG name must be unique. Click OK on the message and enter a unique ASG name. The Access Sub-Group parent’s ASG is offline. You should delete the ASG when the parent ASG is available.
Master Security Client Situations Table 22: Master Security Client Situations Situation Resolution The MSC is no longer bootable or able to connect to the FC network. You must reassign a Backup Master as the new MSC from the Backup Master. Warning: Use this procedure only if the MSC cannot relinquish control to a Backup Master. For example, if the MSC is no longer bootable or able to connect to the FC network.
Non-Hierarchical and Hierarchical ASG It is possible from a higher-level client (such as the MSC) to create an ASG 1 with system A as the client and systems B, C, D, and E as servers. Then create an ASG 2 with system E as the client, but with systems F and G as servers even though F and G are not part of ASG 1. This makes the topology nonhierarchical (see Figure 63).
Figure 64: Hierarchical ASG Scenario The HBAnyware Utility User Manual Page 149
