Emulex LP1150-F4 User Manual

Solaris SFS Driver

User Manual

Last Updated June 14, 2007

Copyright© 2007 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. No license is granted by implication or otherwise under any patent or patent rights of Emulex Corporation.

Emulex, AutoPilot Installer, BlockGuard, cLAN, FabricStream, FibreSpy, Giganet, HBAnyware, InSpeed, IntraLink, LightPulse, MultiPulse, SAN Insite, SBOD and Vixel are registered trademarks, and AutoPilot Manager, EZPilot, SLI and VMPilot are trademarks, of Emulex Corporation. All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations.

Emulex provides this manual "as is" without any warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Emulex Corporation may make improvements and changes to the product described in this manual at any time and without any notice. Emulex Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties that may result. Periodic changes are made to information contained herein; although these changes will be incorporated into new editions of this manual, Emulex Corporation disclaims any undertaking to give notice of such changes.

Last Updated June 14, 2007

Solaris SFS Driver User Manual Page ii

Installation ..............................................................................................1

Introduction .............................................................................................................................. 1

Compatibility............................................................................................................ 1

Known Issues .......................................................................................................... 2

Minimum Driver for Firmware Installation on LPe11000 and LPe11002 HBAs... 2 Special Circumstances for Installing Solaris SFS Driver Version 2.12 or later ... 2

Installing the Solaris SFS Driver............................................................................................. 3

Downloading and Installing the Driver for Solaris 8 or 9 .......................................... 3

Method 1: Using the Install_it Script (recommended) ....................................... 3

Method 2: Using Individual Patches .................................................................. 3

Downloading and Installing the Driver for Solaris 10 (Sparc, X64 and x86) ............. 4

Installing the FCA Utilities and the HBAnyware Utility.......................................................... 5

Unpacking the Utility Files ....................................................................................... 5

Installing the FCA Utilities........................................................................................ 5

Installing or Updating the FCA Utilities Using the emlxu_install Script............... 5

Installing the HBAnyware Utility, Web Launch and Security Configurator ................ 7

Installing the HBAnyware Utility......................................................................... 7

Installing the HBAnyware Utility with Web Launch............................................. 8

Installing the HBAnyware Utility Security Configurator ...................................... 9

Installing or Updating the Utilities Package Manually ........................................ 9

Removing the Utilities Using the emlxu_remove Script ................................... 10

Removing the Utilities Package Manually........................................................ 11

Configuration .......................................................................................12

Introduction ............................................................................................................................ 12

Driver Parameters ................................................................................................. 13

Solaris SFS and lpfc Driver Parameter Cross-Reference Table............................. 14

Using the HBAnyware Utility ................................................................................................. 18

Starting the HBAnyware Utility............................................................................... 18

Starting HBAnyware with Web Launch .................................................................. 18

Starting the HBAnyware Security Configurator ...................................................... 18

Prerequisites ................................................................................................... 18

Procedure........................................................................................................ 18

Starting the HBAnyware Utility from the Command Line.................................. 19

Changing Management Mode................................................................................ 19

The HBAnyware Utility Window Element Definitions.............................................. 20

The Menu Bar.................................................................................................. 20

The Toolbar ..................................................................................................... 20

The Toolbar Buttons ........................................................................................ 21

The Discovery-Tree......................................................................................... 21

Property Tabs .................................................................................................. 22

Status Bar........................................................................................................ 22

Using the HBAnyware Utility Command-Line Interface .......................................... 22

Using the CLI Client ........................................................................................ 23

Discovering HBAs.................................................................................................. 38

Configuring Discovery Settings ....................................................................... 39

Sorting HBAs ......................................................................................................... 40

Sorting by Host Name ..................................................................................... 40

Sorting by Fabric Address ............................................................................... 40

Sorting Local HBAs Only ....................................................................................... 40

Solaris SFS Driver User Manual Page iii

Viewing HBA Information....................................................................................... 41

Viewing Discovery Information ........................................................................ 41

Viewing Host Information................................................................................. 42

The Host Information Tab ................................................................................ 42

The Host Driver Parameters Tab ..................................................................... 43

Viewing General HBA Attributes ............................................................................ 44

Adapter Summary Field Definitions ................................................................. 44

Adapter Status Area Field Definitions.............................................................. 45

Viewing Detailed HBA Information......................................................................... 46

Adapter Details Field Definitions ..................................................................... 46

Port Attributes Field Definitions ....................................................................... 46

Loop Map Table Definitions ............................................................................. 47

Viewing Fabric Information .................................................................................... 47

Discovery Information Field Definitions ........................................................... 48

Viewing Target Information .................................................................................... 48

Viewing LUN Information................................................................................. 49

LUN Information Field Definitions.................................................................... 49

Viewing Port Statistics ........................................................................................... 50

Port Statistics Field Definitions........................................................................ 51

Viewing Firmware Information ............................................................................... 52

Firmware Field Definitions ............................................................................... 52

Viewing Target Mapping ........................................................................................ 53

Target Mapping Field Definitions ..................................................................... 53

Resetting HBAs ..................................................................................................... 54

Updating Firmware ................................................................................................ 55

Prerequisites ................................................................................................... 55

Procedure........................................................................................................ 55

Updating Firmware (Batch Mode) .......................................................................... 58

Prerequisites ................................................................................................... 58

Procedure........................................................................................................ 58

Enabling or Disabling the BIOS ............................................................................. 59

Prerequisites ................................................................................................... 59

Procedure........................................................................................................ 59

Setting Driver Parameters ..................................................................................... 60

Setting Driver Parameters for an HBA............................................................. 61

Setting Driver Parameters for a Host............................................................... 62

Creating the Batch Mode Driver Parameters File ............................................ 64

Assigning Batch Mode Parameters to HBAs ................................................... 64

Setting Up Persistent Binding ................................................................................ 65

Adding New Targets Using sd.conf for Solaris 8, 9 and 10.............................. 68

Changing Parameters or Bindings for Solaris 8, 9 and 10 ............................... 68

Setting Up Target/LUN Blocking Using sd.conf................................................ 69

No-Reboot Firmware Updates ......................................................................... 69

Loading or Unloading the Driver Without Rebooting........................................ 69

Performing Diagnostic Tests .................................................................................. 70

Running a Quick Test ...................................................................................... 70

Running a POST Test...................................................................................... 71

Using Beaconing ............................................................................................. 71

Creating Diagnostic Dumps............................................................................. 72

Displaying PCI Registers and Wakeup Information ......................................... 72

Running Advanced Diagnostic Tests ............................................................... 73

Running Loopback Tests ................................................................................. 74

Running End-to-End (ECHO) Tests ................................................................. 75

Saving the Log File.......................................................................................... 76

Solaris SFS Driver User Manual Page iv

Out-of-Band SAN Management ............................................................................. 77

Adding a Single Host....................................................................................... 78

Adding a Range of Hosts................................................................................. 79

Removing Hosts .............................................................................................. 80

HBAnyware Security.............................................................................................. 80

Introduction ..................................................................................................... 80

Starting the Security Configurator for the First Time: Creating the First ACG,

Designating the MSC and Selecting Systems in the FC Network .......................... 82

Prerequisites ................................................................................................... 82

Procedure........................................................................................................ 82

Access Control Groups.......................................................................................... 84

Introduction ..................................................................................................... 84

Adding a Server to the ACG ............................................................................ 86

Deleting a Server from the ACG ...................................................................... 87

Removing Security from all Servers in the ACG .............................................. 88

Generating New Security Keys........................................................................ 89

Restoring the ACG to Its Last Saved Configuration......................................... 90

Accessing a Switch ......................................................................................... 91

Access Sub-Groups............................................................................................... 92

Introduction ..................................................................................................... 92

Creating an ASG ............................................................................................. 93

Adding a Server to an ASG ............................................................................. 95

Deleting an ASG.............................................................................................. 95

Restoring an ASG to Its Last Saved Configuration.......................................... 96

Editing an ASG................................................................................................ 97

About Offline ASGs ......................................................................................... 98

Backup Masters..................................................................................................... 99

Introduction ..................................................................................................... 99

Creating a Backup Master ............................................................................. 100

Reassigning a Backup Master as the New MSC from the Old MSC .............. 101

Reassigning a Backup Master as the New MSC from the Backup Master..... 103

Using the emlxadm Utility ................................................................................................... 104

Modes of Operation (emlxadm) ........................................................................... 104

Interactive Mode (emlxadm) .......................................................................... 104

CLI Mode (emlxadm) ..................................................................................... 105

Command Descriptions (emlxadm)...................................................................... 107

get_num_devs............................................................................................... 107

get_dev_list ................................................................................................... 107

get_logi_params <wwpn>.............................................................................. 108

get_host_params........................................................................................... 108

get_sym_pname............................................................................................ 109

set_sym_pname <"string">............................................................................ 109

get_sym_nname............................................................................................ 109

set_sym_nname <"string">............................................................................ 109

dev_login <wwpn>......................................................................................... 109

dev_logout <wwpn> ...................................................................................... 110

get_state <wwpn> ......................................................................................... 110

dev_remove <wwpn> .................................................................................... 110

link_status <d_id> ......................................................................................... 110

get_fcode_rev ............................................................................................... 110

download_fcode <filename>...........................................................................111

get_fw_rev......................................................................................................111

download_fw <filename>................................................................................111

Solaris SFS Driver User Manual Page v

get_boot_rev ................................................................................................. 112

download_boot <filename> ........................................................................... 112

get_dump_size .............................................................................................. 112

force_dump ................................................................................................... 112

get_dump <-t filename.txt or -b filename.bin> ............................................... 112

get_topology.................................................................................................. 113

reset_link <wwpn or zero for local link>......................................................... 113

reset_hard ..................................................................................................... 113

reset_hard_core ............................................................................................ 114

diag <test [parameters]> or diag code <cmd_code (hex)> ............................ 114

ns .................................................................................................................. 115

parm_get_num .............................................................................................. 115

parm_get_list................................................................................................. 116

parm_get <label> .......................................................................................... 118

parm_set <label> <value> ............................................................................. 118

msgbuf all or <number> [-i interval] ............................................................... 119

get_host_attrs ............................................................................................... 119

get_port_attrs <index>, <wwn> or all............................................................. 120

get_path <index>........................................................................................... 121

get_vpd ......................................................................................................... 122

boot_code [enable or disable] ....................................................................... 122

q .................................................................................................................... 122

h .................................................................................................................... 122

hba ................................................................................................................ 123

p .................................................................................................................... 123

Using the emlxdrv Utility ..................................................................................................... 124

Modes of Operation (emlxdrv) ............................................................................. 124

Interactive Mode (emlxdrv) ............................................................................ 124

CLI Mode (emlxdrv)....................................................................................... 125

Command Descriptions (emlxdrv)........................................................................ 126

set_emlxs <alias>.......................................................................................... 126

set_emlxs_sun .............................................................................................. 126

set_emlxs_all ................................................................................................ 126

set_lpfc <alias> ............................................................................................. 127

set_lpfc_nonsun ............................................................................................ 127

clear_dev <alias> .......................................................................................... 127

clear_lpfc....................................................................................................... 128

clear_emlxs ................................................................................................... 128

clear_sun....................................................................................................... 129

clear_nonsun................................................................................................. 129

clear_all......................................................................................................... 130

q .................................................................................................................... 130

Troubleshooting .................................................................................131

Introduction .......................................................................................................................... 131

Situations That Involve HBAnyware ................................................................................... 131

General Situations......................................................................................... 131

Security Configurator Situations - Access Control Groups (ACG) ................. 133

Security Configuration Situations - Access Sub-Groups (ASG) ..................... 134

HBAnyware Security Configurator Situations - Backup Masters.................... 135

Error Message Situations .............................................................................. 136

Master Security Client Situations................................................................... 137

Solaris SFS Driver User Manual Page vi

Console and Log Messages ................................................................................................ 139

Introduction.......................................................................................................... 139

Severity Levels.............................................................................................. 140

Message Log Example .................................................................................. 140

Miscellaneous Events .......................................................................................... 141

Driver Events ....................................................................................................... 142

HBA Initialization Events...................................................................................... 143

Memory Management Events .............................................................................. 145

Service Level Interface (SLI) Events.................................................................... 146

Mailbox Events .................................................................................................... 148

Node Events ........................................................................................................ 148

Link Events.......................................................................................................... 150

ELS Events.......................................................................................................... 151

General I/O Packet Events .................................................................................. 152

FCP Traffic Events............................................................................................... 154

IP Traffic Events .................................................................................................. 154

Solaris SFS Events.............................................................................................. 155

IOCTL Events ...................................................................................................... 157

Firmware Download Events ................................................................................. 158

Common Transport Events .................................................................................. 159

Appendix .............................................................................................161

Introduction .......................................................................................................................... 161

Use Cases ........................................................................................................... 161

Migrating from the Solaris lpfc Driver to the Solaris SFS Driver...................................... 162

Operational Differences Between lpfc and SFS................................................... 162

Sample Script File Details.................................................................................... 162

start_emlxs_migration.sh .............................................................................. 162

finish_emlxs_migration.sh ............................................................................. 163

Migrating a Configuration without FC Boot .......................................................... 164

Migrating Automatically ................................................................................. 164

Prerequisites ................................................................................................. 164

Procedure...................................................................................................... 164

Migrating Manually ........................................................................................ 165

Migrating a Configuration with FC Boot ............................................................... 166

Migrating Non-emlxs HBAs to emlxs HBAs ................................................... 166

Migrating an lpfc Configuration to emlxs – Adding Sun-Branded HBAs......... 168

Solaris SFS Driver User Manual Page vii

Installation

Introduction

Compatibility

The StorEdge SAN Foundation Software (SFS) driver and utilities support the following operating systems:

• Solaris 8 SPARC

• Solaris 9 SPARC

• Solaris 10 SPARC

• Solaris 10 x64 and x86

The following table specifies the host bus adapters (HBAs) supported by the Solaris SFS driver and the Emulex Fibre Channel Adapter Utilities (FCA Utilities).

Table 1: HBA Compatibility

FCA Utilities

HBA Solaris SFS Driver HBAnyware Utility emlxadm emlxdrv

SG-XPCI1FC-EM4-Z**

SG-XPCI2FC-EM4-Z**

SG-XPCIE1FC-EM4**

SG-XPCIE2FC-EM4**

SG-XPCI1FC-EM2**

SG-XPCI2FC-EM2**

LP11002

LP11000

LPe11002*

LPe11000*

LP10000ExDC

LP10000DC

LP10000

LP9802

LP9002DC

LP9002L

LP9002S

XXXN/A

XXXX

* Special driver and firmware installation considerations may apply. See the Known Issues sec-

tion of this manual for more information.

** Special firmware installation considerations apply. See

Updating Firmware on page 55 for more

information.

Solaris SFS Driver User Manual Page 1

Known Issues

Minimum Driver for Firmware Installation on LPe11000 and LPe11002 HBAs

You cannot install firmware version 2.70 or later on an LPe11000 or an LPe11002 HBA that is running a driver version earlier than 2.11i (Sun patch revision -12). (If you are installing driver version 2.12 [Sun patch revision -15] or later, continue reading the next section.)

Special Circumstances for Installing Solaris SFS Driver Version 2.12 or later

If you want to update the driver to version 2.12 (Sun patch revision -15) through 2.20h (Sun patch revision -18) and both of the following conditions are true, follow one of the sets of special installation procedures in this section.

• An LPe11000 or an LPe11002 HBA is installed

• A firmware version earlier than 2.70 is installed

If the above conditions are true and you do not want to enable support for multiple interrupt MSI mode, follow the instructions in Procedure 1 to install the driver and, optionally, to update the firmware.

If the above conditions are true and you do want to enable support for multiple interrupt MSI, follow the instructions in Procedure 2 to install the driver and update the firmware (you must update the firmware to version 2.70 or later for multiple interrupt MSI support).

Procedure 1

1. Download and install the driver version 2.12 or later patch from the Sun Web site. Do not reboot the server after the installation is finished.

2. Add "msi-mode=1;" to the /kernel/drv/emlxs.conf file. This step enables single interrupt MSI mode.

3. Perform a reconfiguration reboot of the server.

4. If desired, download firmware version 2.70 or later from the Emulex Web site and install it on each HBA port. No reboot is required. (Installing firmware version 2.70 or later is not mandatory.)

Procedure 2

1. Download and install the driver version 2.12 or later patch from the Sun Web site. Do not reboot the server after the installation is finished.

2. Add "msi-mode=1;" to the /kernel/drv/emlxs.conf file. This step enables single interrupt MSI mode. (You will enable multiple interrupt MSI support later.)

3. Perform a reconfiguration reboot of the server.

4. Download firmware version 2.70 or later from the Emulex Web site and install it on each HBA port (this step is not optional for multiple interrupt MSI support). No reboot is required.

5. Remove the "msi-mode=1;" entry from the /kernel/drv/emlxs.conf file to enable multiple interrupt MSI support.

6. Perform a reconfiguration reboot of the server.

Solaris SFS Driver User Manual Page 2

Installing the Solaris SFS Driver

Caution: Before installing the Emulex utilities package, you must first install the Sun StorEdge SAN

Foundation Software package and all the recommended patches as described in the Sun StorEdge SAN Foundation Software Installation Guide provided by Sun.

Downloading and Installing the Driver for Solaris 8 or 9

The Emulex FCA driver and the Solaris SFS prerequisites can be acquired in two ways. Method 1, Using the Install_it Script (the recommended method) or method 2, Using Individual Patches.

Method 1: Using the Install_it Script (recommended)

Note: Install_scripts may be available a few days after the individual patches are available.

To obtain and install the Install_it script:

1. Go to http://www.sun.com/download/index.jsp?tab=2, scroll down and click StorageTek SAN 4.4.

2. Log in with your user name and password, and accept the license agreement.

3. Select and download "Install_it Script SAN 4.4.12, English".

4. Select and download "Install_it Script SAN 4.4.x Readme, English", and follow the instructions.

Method 2: Using Individual Patches

To obtain and install individual patches:

1. Go to http://www.sun.com/download/index.jsp?tab=2, scroll down and click StorEdge SAN 4.4.

2. Log in with your user name and password, and accept the license agreement.

3. For Solaris 8:

a. Select "Solaris 8 SFS Base Packages, English" and follow the instructions.

b. Go to http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage. Enter and download the fol-

lowing required patches:

• 111095

• 119913

• 111413

c. Follow the instructions to install each patch.

d. For additional functionality, install the following optional patches:

• 111096 (FCIP)

• 111412 (mpxio)

• 113767 and 113766 (Common HBA API)

• 114475 (FCSM)

For Solaris 9: a. Select "Solaris 9 SFS Base Packages, English" and follow the instructions.

Solaris SFS Driver User Manual Page 3

b. Go to http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage. Enter and download the fol-

lowing required patches:

• 113040

• 119914

• 113043

c. Follow the instructions to install each patch.

d. For additional functionality, install the following optional patches:

• 113041 (FCIP)

• 113039 (mpxio)

• 114478 and 114477 (Common HBA API)

• 114476 (FCSM)

Downloading and Installing the Driver for Solaris 10 (Sparc, X64 and x86)

If the Solaris SFS driver is not already installed, obtain and install the Solaris 10 packages.

To obtain and install the Solaris 10 packages:

1. Go to http://www.sun.com/download/products.xml?id=42c4317d and click Download.

2. Log in with your user name and password, and accept the license agreement.

3. Select and download the driver package.

4. Select and download the readme file, and follow its instructions.

To finish the installation (or if the Solaris SFS driver was already installed), install the driver by obtaining and installing individual patches:

1. Go to http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage. Enter and download the

following required patches:

• For SPARC systems:

• 119130

• 120222

• For x64 and x86 systems:

• 119131

• 120223

2. Follow the instructions to install each patch.

3. For additional functionality, install the following optional patches:

• For SPARC systems

• 119470 (Sun Enterprise Network Array firmware and utilities)

• 119715 (scsi_vhci patch)

• For x64 and x86 systems:

• 119471 (Sun Enterprise Network Array firmware and utilities)

• 119715 (scsi_vhci patch)

Solaris SFS Driver User Manual Page 4

Installing the FCA Utilities and the HBAnyware Utility

Unpacking the Utility Files

The FCA Utilities and the HBAnyware utility are packaged together in one application kit tar file.

To unpack the tar file:

1. Log in as root, or su to root.

2. Copy the application kit tar file from your distribution medium into a directory, referred to here as

<directory>. The .tar file is named something similar to Solaris-3.2a13-1.01c-1a.tar.

3. Change to the directory where you put the kit tar file by typing:

cd <directory>

4. Extract and unpack the FCA Utilities and the HBAnyware utility files from the tar by typing:

tar xf Solaris-3.2a13-1.01c-1a.tar

Both of the following tar kits will be placed in the specified directory:

• Solaris-3.2a13-1.01c-1a-i386.tar

• Solaris-3.2a13-1.01c-1a-sparc.tar

Each of these .tar files contains the following:

• readme.first.txt

• emlxu_kit-1.01c-<platform>.tar - The emlxu_kit files contain the FCA Utilities.

• EmlxApps300b-12-Solaris.tar - This file contains the HBAnyware utility.

5. Untar the Solaris-3.2a13-1.01c-1a-<platform>.tar:

tar xvf Solaris-3.2a13-1.01c-1a-<platform>.tar

Installing the FCA Utilities

The FCA Utilities are comprised of the emlxadm utility and the emlxdrv utility.

• The emlxadm utility provides an interface to the Fibre Channel input/output (FCIO) interface provided by the Sun StorEdge SFS.

• The emlxdrv utility temporarily associates or binds the Emulex emlxs Solaris SFS driver and the Solaris lpfc driver to the various models of Emulex FC HBAs during migration from the Solaris lpfc driver to the Solaris SFS driver.

Installing or Updating the FCA Utilities Using the emlxu_install Script

Although it is possible to install emlxu onto one or more clients from a server, that procedure is not covered in this document; refer to the Solaris documentation.

Note: If an earlier version of the emlxu utilities package is already installed on the system,

the emlxu_install script will remove the old version before installing the new version.

Solaris SFS Driver User Manual Page 5

Prerequisites

• Before installing the Emulex emlxu utilities package, you must completely install:

• The Sun StorEdge SAN Foundation Software package.

• All the recommended patches as described in the Sun StorEdge SAN Foundation Software

Installation Guide provided by Sun.

• The Emulex-Sun Fibre Channel adapter SUNWemlxs driver package.

Procedure

To install the utilities kit using the emlxu_install script:

1. Untar the emlxu_kit-1.01c-<platform>.tar file.

tar xvf emlxu_kit-1.01c-<platform>.tar

The emlxu_install script is available.

2. Install the FCA Utilities by typing:

emlxu_install

3. The script removes any earlier version of the emlxu utilities package. (If an earlier package is not found, this fact is indicated; skip to step 9.) The following text is displayed:

4. If an old package is installed, you are prompted to remove it:

Do you want to remove this package? [y,n,?,q]

5. Enter y. The following message is displayed:

Removal of <EMLXemlxu> was successful.

6. The script expands the utilities kit .tar file and begins installing the new package. A message similar to the following message will be displayed:

7. The script installs the emlxu utilities package. The package is prepared for installation and you are prompted for confirmation by the following message:

Do you want to continue with the installation of <EMLXemlxu> [y,n,?]:

8. Enter y. The installation package provides running commentary on the installation process.

9. Examine the output for any errors or warnings. If the installation is successful, the following message is displayed near the end of the process:

Installation of <EMLXemlxu> was successful.

10. The script performs some cleanup and displays the following messages:

<emlxu_install complete>

11. The script leaves a copy of the emlxu_remove script in your working directory with the original utilities kit tar file. You can remove this script, or leave it in the directory if you may want to uninstall the emlxu utilities from your system in the future. See

Package Manually

on page 9 for more details.

Installing or Updating the Utilities

The emlxu utilities installation is complete. The utility package's programs are located in the /opt/EMLXemlxu/bin directory.

Solaris SFS Driver User Manual Page 6

You do not need to reboot your system to run a utility program, but you must either enter the program’s full path name, or add the package's bin directory (/opt/EMLXemlxu/bin) to your environment’s search path. To use the man pages provided by the package, you must also add the package's man directory (opt/EMLXemlxu/man) to your environment's man path.

For further information on installing and removing packages, consult the Solaris system administration documentation and the pkgadd(1M) and pkgrm(1M) manual pages.

Installing the HBAnyware Utility, Web Launch and Security Configurator

Known Issues

• Starting with the HBAnyware utility version 3.2, Emulex provides support for LightPulse adapters that are reprogrammed with WWPNs outside the typical Emulex range, such as HewlettPackard’s upcoming Virtual Connect for Fibre Channel on the BladeSystem c-Class platform. In such environments, the HBAnyware utility version 3.2, must be deployed across all servers on the SAN, as well as any other management console used for out-of-band management, so that all adapters appear in the Discovery Tree.

Installing the HBAnyware Utility

Prerequisites

• The FCA Utilities must be installed prior to installing the HBAnyware utility.

• Java Runtime Environment:

Version 5 of the Java Runtime Environment (JRE) must be installed. The HBAnyware utility will not run under earlier versions of the JRE.

Caution: The utilities require the java runtime binaries and libraries, so their path must be

included at the beginning of the PATH environment variable to avoid conflicts with possible earlier versions of java that may still be installed on the system. For example, if the java runtime binaries are in /usr/java/bin, then include this path in the PATH environment variable.

For example: (bash> export PATH="/usr/java/bin:$PATH")

The JRE and instructions for installation can be found at http://java.sun.com/downloads/index.html.

Procedure

To install the HBAnyware utility from the tar file:

1. Untar the EmlxApps tar file:

tar xvf EmlxApps-300b12-Solaris.tar

2. Run the unpack script to obtain the correct package version. Type:

./unpack_apps

3. Unzip the HBAnyware package file. Type:

gunzip HBAnyware-<version>-<platform>.tar.gz

4. Untar the HBAnyware package file. Type:

tar -xvf HBAnyware-<version>-<platform>.tar

5. Run the pkgadd utility. Type:

pkgadd -d .

Solaris SFS Driver User Manual Page 7

6. When prompted by pkgadd, choose to install the HBAnyware utility.

7. When prompted by pkgadd, answer the HBAnyware installation questions.

Installing the HBAnyware Utility with Web Launch

Prerequisites

Before installing the HBAnyware utility with Web Launch, ensure your systems meet the following requirements.

• The system on which you are installing the Web Launch services package (the server) requires that the HTTP Web server be configured to handle the JNLP MIME file type. Follow these steps:

a. Change your working directory to the directory containing the Apache configuration files for

example: /etc/apache or /etc/apache2).

b. Edit the file “mime.types”.

c. Add the following line to the file:

application/x-java-jnlp-file jnlp JNLP

d. Save the file.

e. Stop and restart the HTTP Web server (to enable the Web server to detect this change).

• The system on which you are running the browser (the client) requires the Java Runtime Environment (JRE) 5.0 or later must be installed on the browser host. Below are the specific requirements:

• Sun 32-bit JRE 5.0 or later for Intel based systems (x86 and IA64)

• Sun 32-bit JRE 5.0 or later x86-64

Refer to the appropriate vendor documentation for detailed instructions about configuring and starting the HTTP server and installing the JRE.

• The HBAnyware utility must be installed before installing HBAnyware with Web Launch.

Procedure

To install HBAnyware with Web Launch:

1. Log on as ‘root’.

2. Navigate to the HBAnyware directory. Type:

cd /usr/sbin/hbanyware

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 listening on the normal default HTTP port (80)? Answer Y or N as appropriate. If you answer N, you are prompted for the port you wish to use.

You are notified the installation of the HBAnyware Web Launch package has completed.

Solaris SFS Driver User Manual Page 8

Installing the HBAnyware Utility Security Configurator

Follow these instructions to install the Security Configurator on your system.

Prerequisites

• The HBAnyware utility must be installed on the system.

• Java Runtime Environment:

Version 5 of the Java Runtime Environment (JRE) must be installed. The lputil and HBAnyware utilities will not run under earlier versions of the JRE.

The JRE and instructions for installation can be found at: http://java.sun.com/downloads/index.html.

Procedure

To install the HBAnyware utility Security Configurator from a tar file:

1. If you have not already done so, untar the EmlxApps tar file and run the unpack script to obtain the correct package version:

tar xvf EmlxApps-300b12-Solaris.tar

./unpack_apps

2. Unzip the HBAnywareSSC package file:

gunzip HBAnywareSSC-<version>-<platform>.tar.gz

3. Untar the HBAnywareSSC package file. Type:

tar xvf HBAnywareSSC-<version>-<platform>.tar

4. Run the pkgadd utility. su to ‘root’.

pkgadd -d

5. When prompted by pkgadd, choose to install HBAnywareSSC.

6. If prompted by pkgadd, answer the HBAnywareSSC installation questions.

Installing or Updating the Utilities Package Manually

Compatibility

• The HBAnyware utility can be used with Solaris 10 Update 4 or later, or with SFS driver version

2.20i (Sun patch revision -19) or later

Prerequisites

• Before installing the Emulex utilities package, you must completely install:

• The Sun StorEdge SAN Foundation Software package.

• All the recommended patches as described in the Sun StorEdge SAN Foundation Software

Installation Guide provided by Sun.

• If an earlier version of the emlxu utilities package is already installed on the system and you want to install a different version, follow the instructions in on page 11, then return to this section to install the new utilities package.

Solaris SFS Driver User Manual Page 9

Removing the Utilities Package Manually

Procedure

To install the emlxu utilities package manually:

1. Log in as root, or su to root.

2. Copy the utilities kit from your distribution medium into a directory, referred to here as <directory>. The utilities kit is a .tar file named something similar to emlxu_kit-1.01c-sparc.tar.

3. Change to the directory where you put the kit tar file by typing:

cd <directory>

4. Extract the installation images from the tar file by typing:

tar xvf emlxu_kit-1.01c-sparc.tar

5. Install the EMLXemlxu utilities package by typing:

pkgadd -d . EMLXemlxu

6. The package is prepared for installation, and you are prompted to confirm the installation with the following message:

Do you want to continue with the installation of <EMLXemlxu> [y,n,?]

7. Enter y. The installation package provides running commentary on the installation process.

8. Examine the output for any errors or warnings. If the installation is successful, the following message is displayed near the end of the process:

Installation of <EMLXemlxu> was successful.

The emlxu utilities installation is complete. The utility package's programs are located in the /opt/EMLXemlxu/bin directory.

Removing the Utilities Using the emlxu_remove Script

You can uninstall the utilities kit using the emlxu_remove script. If you do not have the emlxu_remove script and you do not have the original emlxu utilities kit tar file, you must uninstall the emlxu package manually; follow the instructions in the emlxu utilities to a newer version and you have the new utilities kit tar file, you do not need to use the emlxu_remove script; the emlxu_install script removes any old version as it installs the newer version; see

Installing or Updating the FCA Utilities Using the emlxu_install Script on page 5 for more details.

To uninstall the utilities package (without updating them):

Note: All emlxu files are removed.

1. Go to the directory where the emlxu_remove script is located, or to the directory where the original utilities kit tar file is located, by typing:

cd <directory>

2. If you have the emlxu_remove script, skip to step 4. If you do not have the emlxu_remove script but you do have the original emlxu utilities kit tar file, extract the emlxu_remove script from the tar file by typing:

tar xf emlxu_kit-1.01c-sparc.tar emlxu_remove

Removing the Utilities Package Manually on page 11. If you are updating

Solaris SFS Driver User Manual Page 10

3. Remove the emlxu utilities package by typing:

emlxu_remove

4. The script locates the EMLXemlxu utilities package, and the following message is displayed:

Note: If no package is installed, the following message is displayed:

pkgrm: ERROR: no package associated with <EMLXemlxu>

5. You are prompted to remove the package with the following message:

Do you want to remove this package? [y,n,?,q]

6. Enter y. The following message is displayed:

Removal of <EMLXemlxu> was successful.

7. The script performs some cleanup and displays the following message:

<emlxu_remove complete>

The utilities package has been removed. If you want to install another version of the emlxu utilities package, do so now by following the instructions in one of the following sections:

•

Installing or Updating the FCA Utilities Using the emlxu_install Script on page 5

•

Installing or Updating the Utilities Package Manually on page 9

For additional information on installing and removing packages, see the Solaris system administration documentation and the pkgadd(1M) and pkgrm(1M) manual pages.

Removing the Utilities Package Manually

To remove the emlxu utilities package:

1. Remove the EMLXemlxu utilities package by typing:

pkgrm EMLXemlxu

2. You are prompted to confirm the removal by the following message:

Do you want to remove this package? [y,n,?,q]

3. Enter y. The package is prepared for removal, and you are prompted again for confirmation:

Do you want to remove this package? [y,n,?,q]

4. Enter y. The following message is displayed:

Removal of <EMLXemlxu> was successful.

The utilities package has been removed.

For additional information on installing and removing packages, see the Solaris system administration documentation and the pkgadd(1M) and pkgrm(1M) manual pages.

Solaris SFS Driver User Manual Page 11

Configuration

Introduction

The HBAnyware utility is launched directly from your Web browser. The utility is client/server based and allows you to perform configuration, update and management tasks locally and remotely (inband - host systems on the same FC SAN or out-of-band - from IP addresses of remote machines). The HBAnyware Web Launch feature enables you to download and launch the HBAnyware user interface by specifying the URL of a server that is hosting the HBAnyware Web Launch software. You only need a standard web

browser, or some other application capable of making HTTP requests.

Note: Only the HBAnyware Web Launch GUI is being exported to the requesting client. All

HBA discovery and remote management operations are performed by resources running on the remote host that served up the GUI component. Therefore, the SAN "view" displayed by the GUI is not from the perspective of the client running the GUI, but rather from the perspective of the host from which this GUI was retrieved.

Use the HBAnyware utility to do any of the following:

• Discover local and remote hosts, HBAs, targets and LUNs

• Reset HBAs

• Set HBA driver parameters locally, simultaneously to multiple HBAs (using Batch Update) and globally

• Update firmware on a single HBA or multiple HBAs using Batch Update

• Update FC boot code (BootBIOS, OpenBoot or EFIBoot) on the local HBA or on remote HBAs

• Enable or disable the system BIOS

• Run diagnostic tests on HBAs

• Manage local, in-band remote and out-of-band remote HBAs

Note: Remote in-band capabilities of the HBAnyware utility are subject to fabric zoning

configuration. Remote hosts you want to discover and manage using the HBAnyware utility must be in the same zone or discovered and managed out-of-band through an Ethernet connection.

• Locate HBAs using beaconing

• The Solaris SFS utility allows you to make changes to the driver initialization.

• The Emulex FCA utilities consist of the emlxadm utility and the emlxdrv utility:

• The emlxadm utility provides an interface to the FCIO interface provided by the Sun StorEdge SFS.

Solaris SFS Driver User Manual Page 12

Driver Parameters

• The emlxs.conf file contains all the parameters necessary to initialize the Solaris SFS driver.

In the emlx.conf file, all adapter-specific parameters have emlxsX-prefix (where X is the driver instance number); e.g.setting emlxs0-link-speed=4 makes 4 the default link speed setting for the zero instance of the driver. Changes to the emlxs.conf file require you to unload and reload the driver.

• The lpfc.conf file contains all the parameters necessary to initialize the Solaris lpfc driver.

In the lpfc.conf file, all adapter-specific parameters have lpfcX-prefix (where X is the driver instance number); e.g., setting lpfc0-lun-queue-depth= 20 makes 20 the default number of maximum commands which can be sent to a single logical unit (disk) for the zero instance of the lpfc driver. Changes to the lpfc.conf file require you to unload and reload the driver.

Note: If you want to override a driver parameter for a single driver-loading session, you can specify it as a parameter to the lpfc automap=0 (for 32-bit platforms) or modload/kernel/drv/sparcv9/lpfc automap=0 (for 64bit platforms). This will load Emulex's SCSI support driver with automap set to 0 for this session.

• The HBAnyware utility reflects the Solaris SFS driver parameters.

The following table is a cross-reference of the Solaris SFS driver parameters and the corresponding or related lpfc driver parameters. The values for the lpfc driver parameters and the Solaris SFS driver parameters default to enable migration from the Solaris lpfc driver to the Solaris SFS driver.

modload command. For example: # modload /kernel/drv/

Note: If any of the default parameter values were changed, verify that this change will not

impact the migration before you migrate.

Solaris SFS Driver User Manual Page 13

Solaris SFS and lpfc Driver Parameter Cross-Reference Table

Table 1: Solaris SFS and lpfc Driver Parameter Cross-Reference

Solaris SFS/ HBAnyware Parameter

ack0 0 = Off

adiscsupport

Solaris SFS/HBAnyware Min/Max, Defaults and Description

1 = On Default: 0 Description: Use ACK0 for class 2. If ACK0 is 1, the HBA tries to use ACK0 when running Class 2 traffic to a device. If the device doesn’t support ACK0, then the HBA uses ACK1. If ACK0 is 0, only ACK1 is used when running Class 2 traffic.

0 = No support. Flush active I/O's for all FCP target devices at link down. 1 = Partial support. Flush I/O's for non-FCP2 target devices at link down. 2 = Full support. Hold active I/O's for all devices at link down. Default: 1 Description: Sets the level of driver support for the FC ADISC login I/O recovery method.

Related lpfc Parameter

ack0 0 = Off

use-adisc 0 = Off

lpfc Min/Max, Default and Description

1 = On Default: 0 Description: Controls the ELS command used for address authentication during rediscovery upon linkup. The driver will always use ADISC for FCP-2 devices and re-discovery due to an registered state change notification (RSCN).

Comments

If there are tape devices on the SAN that support FCP2, set the use-adisc parameter to 1 and the adiscsupport parameter to 1 (partial support) or 2 (full support).

assign-alpa Min:0x00

Max:0xef Default:0x00 (valid ALPA's only) Description: This is only valid if topology is loop. A zero setting means no preference. If multiple adapter instances on the same host are on the same loop, you should set this value differently for each adapter.

N/A N/A

Solaris SFS Driver User Manual Page 14

Table 1: Solaris SFS and lpfc Driver Parameter Cross-Reference (Continued)

Solaris SFS/ HBAnyware Parameter

cr-delay Min:0

cr-count Min:1

Solaris SFS/HBAnyware Min/Max, Defaults and Description

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.

Max:255 Default:1 Description: Specifies a count of I/O completions after which an interrupt response is generated. This feature is disabled if crdelay is set to 0.

Related lpfc Parameter

cr-delay Min:0

cr-count Min:1

lpfc Min/Max, Default and Description

Max:255 Default:1 Description: 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.

Comments

Setting this value can minimize CPU utilization by reducing the number of interrupts that the driver generates to the operating system.

The parameter setting is often determined by your OEM. This parameter sets the number of I/Os to be queued in the operating system’s driver before an interrupt is initiated. The driver default settings are roughly a 1:1 I/O to interrupt ratio. If you change this parameter, performance varies per application.

link-speed 0 = auto select

1 = 1 Gigabaud 2 = 2 Gigabaud 4 = 4 Gigabaud Default: 0 Description: Sets the link speed setting for initializing the FC connection.

link-speed 0 = auto select

1 = 1 Gigabaud 2 = 2 Gigabaud 4 = 4 Gigabaud Default: 0 Description: Sets link speed.

This variable can be changed to a specific link speed to optimize the link initialization process for a specific environment.

Solaris SFS Driver User Manual Page 15

Table 1: Solaris SFS and lpfc Driver Parameter Cross-Reference (Continued)

Solaris SFS/ HBAnyware Parameter

network-on Min:0 (Disables)

num-iocbs Min:128

Solaris SFS/HBAnyware Min/Max, Defaults and Description

Max:1 (Enables) Default:1 Description: Enables or disables IP networking support in the driver.

Max:1024 Default = 1024 Description: Sets the number of iocb buffers to allocate.

Related lpfc Parameter

network-on Min:0 (Disables)

num-bufs Min:64

lpfc Min/Max, Default and Description

Max:1 (Enables) Default:1 Description: Controls whether lpfc provides IP networking functionality over FC. This variable is Boolean: when zero, IP networking is disabled: when non-zero, IP networking is enabled.

Max:128 Default = 128 Description: Specifies the number of command buffers to allocate. These buffers are used for Fibre Channel Extended Link Services (ELS) and one for each FCP command issued in SLI-2 mode. If you want to queue lots of FCP commands to the adapter, then you should increase num-bufs for better performance. These buffers consume physical memory and are also used by the device driver to process loop initialization and rediscovery activities. Important: The driver must always be configured with at least several dozen ELS command buffers; Emulex recommends at least 128.

Comments

The lpfc parameter enables or disables FCIP on the Emulex HBA.

num-nodes Min:2

Max:512 Default:512 Description: Number of FC nodes (NPorts) the driver will support.

N/A N/A

Solaris SFS Driver User Manual Page 16

Table 1: Solaris SFS and lpfc Driver Parameter Cross-Reference (Continued)

Solaris SFS/ HBAnyware Parameter

pm-support 0 = Disables power

topology 0 = loop, if it fails attempt pt-

Solaris SFS/HBAnyware Min/Max, Defaults and Description

management support in the driver. 1 = Enables power management support in the driver. Default: 0 Description: Enable/Disable power management support in the driver

to-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 Fibre Channel connection. Set ptto-pt if you want to run as an N_Port. Set loop if you want to run as an NL_Port.

Related lpfc Parameter

N/A N/A

topology 0x0 = loop, if it fails attempt

lpfc Min/Max, Default and Description

pt-to-pt 0x2 = pt-to-pt only 0x4 = loop only 0x6 = pt-to-pt, if it fails attempt loop Default: 0 Description: Controls the FC topology expected by lpfc at boot time. FC offers pt-to-pt, fabric and arbitrated loop topologies. To make the adapter operate as an N_Port, select pt-to-pt mode (used for N_Port to F_Port and N_Port to N_Port connections). To make the adapter operate as an NL_Port, select loop mode (used for private loop and public loop topologies). The driver will reject an attempt to set the topology to a value not in the above list. The auto-topology settings 0 and 6 will not work unless the adapter is using firmware version 3.20 or higher.

Comments

The topology parameter controls the protocol (not physical) topology attempted by the driver.

ub-bufs Min:40

Max:16320 Default:1000 Description: Sets the number of unsolicited buffers to be allocated.

N/A N/A

Solaris SFS Driver User Manual Page 17

Using the HBAnyware Utility

Starting the HBAnyware Utility

Note: The HBAnyware utility can only discover and manage remote HBAs on hosts running

the HBAnyware utility’s elxhbamgr daemon.

Note: Remote in-band capabilities of the HBAnyware utility are subject to fabric zoning

configuration. Remote hosts you want to discover and manage using the HBAnyware utility must be in the same zone or discovered and managed out-of-band through an Ethernet connection.

To start the HBAnyware utility:

1. Login as or su to ‘root’.

2. Run the script:

/usr/sbin/hbanyware/hbanyware

Starting HBAnyware with Web Launch

After the HBAnyware Web Launch software has been installed and the Web Launch server has been initialized, you can launch the HBAnyware utility directly with your Web browser.

To launch the HBAnyware utility with your Web browser:

1. Open your Web browser.

2. Enter the URL of an HBAnyware.jnlp file. Make sure that the URL specifies a remote server which has the HBAnyware Web Launch software installed and running. For example:

http://138.239.20.30/hbanyware.jnlp

Note: If the browser window displays “Emulex Corporation HBAnyware Demo of

HBAnyware WebStart web n.n.n.n ...” when attempting to start HBAnyware with Web Launch, refer to the “Troubleshooting” section on page 131.

Starting the HBAnyware Security Configurator

Prerequisites

• Make sure that all of the systems that are part of, or will be part of, the security configuration are online on the network so that they receive updates or changes made to the security configuration.

• Before running the security configurator out-of-band, you must set up the OOB hosts so they will be seen by the security configurator. For more information, see page 77

Procedure

If this is the first time you are starting the configurator, see Starting the Security Configurator for the First

Time: Creating the First ACG, Designating the MSC and Selecting Systems in the FC Network

To start the HBAnyware Security Configurator for Solaris:

1. Login as or su to ‘root’.

2. Run the script:

/usr/sbin/hbanyware/ssc

Solaris SFS Driver User Manual Page 18

Out-of-Band SAN Management on

on page 82.

Starting the HBAnyware Utility from the Command Line

To launch the HBAnyware utility from the command line:

1. Type /usr/sbin/hbanyware/hbanyware. This starts the HBAnyware utility running in in-band access. You can also start the HBAnyware utility running in out-of-band access by adding an argument in the form “h=<host>”. The <host> argument may be either the IP address of the host or its system name. The call will use a default IP port of 23333, but you can override this by optionally appending a colon (:) and the IP port number.

Note: Remember that not all HBAs for a specific host may be running in-band.

Therefore, running that host out-of-band may display HBAs that do not appear when the host is running in-band.

Examples of Modifications

• HBAnyware h=138.239.82.2

The HBAnyware utility will show HBAs in the host with the IP address 138.239.82.2.

• HBAnyware h=Util01

The HBAnyware utility will show HBAs in the host named Util01.

• HBAnyware h=138.239.82.2:4295

The HBAnyware utility will show HBAs in the host with the IP address 138.239.82.2 using IP Port

4295.

• HBAnyware h=Util01:4295

The HBAnyware utility will show HBAs in the host named Util01 using IP port 4295.

Run this modified command line to launch the HBAnyware utility for a single, remote host in local mode.

Changing Management Mode

During installation a management mode was selected, however you can change it if the “Allow users to change management mode from the utility" box was checked. HBAnyware enables you to choose from three types of host/HBA management.

To change HBAnyware management mode:

1. Run the set_operating_mode script:

/usr/sbin/hbanyware/set_operating_mode

The following appears:

1 Local Mode - HBAs on this Platform can be managed by HBAnyware clients on this Platform Only.

2 Managed Mode - HBAs on this Platform can be managed by local or remote HBAnyware clients.

3 Remote Mode - Same as “2” plus HBAnyware clients on this Platform can manage local and remote HBAs.

Enter the number ‘1’, ‘2’ or ‘3’.

2. Enter desired management mode.

3. Press <Enter>.

4. Click OK.

Solaris SFS Driver User Manual Page 19

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 1: HBAnyware Utility Window with Element Call Outs

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 Reset Adapter toolbar button is unavailable as well.

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 host bus adapters and sorting items in the discovery-tree view. Many of the menu bar commands are also available from the toolbar.

The Toolbar

The toolbar contains buttons that enable you to refresh the discovery-tree, reset the selected HBA and sort the discovery-tree. Many of the toolbar functions are also available from the menu bar.

Figure 2: The HBAnyware Toolbar

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.

Solaris SFS Driver User Manual Page 20

The Toolbar Buttons

The toolbar buttons perform the following tasks:

Click the Rediscover button to refresh the discovery-tree display.

Click the Reset button to reset the selected HBA.

Sort Toolbar Buttons

You can sort discovered adapters by host name or fabric addresses. You can also choose to display only local or remote HBAs. See page 40 for details on sort buttons.

Sort by Host Name button (default)

Sort by Fabric ID button

Local HBAs Only button

Help button

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, when present, are also displayed.

Figure 3: HBAnyware Utility, Discovery-tree

Solaris SFS Driver User Manual Page 21

Discovery-Tree Icons

Discover- 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.

A red HBA icon with red descriptive text represents an offline or otherwise temporarily inaccessible HBA. Several situations could cause the HBA to be offline or inaccessible:

• The HBA on a local host is not connected to the network, but is still available for local

access.

• The HBA on a local host is malfunctioning and is inaccessible to the local host as well as to

the network.

• The HBA on a local host is busy performing a local download and is temporarily inaccessible

to the local host as well as to the network.

The Target icon represents connections to individual storage devices.

The LUN icon represents connections to individual LUNs.

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.

Status Bar

As you navigate through the menu bar or the toolbar, help messages appear on the status bar near the bottom of the HBAnyware window.

The status bar is visible by default. Use the Status Bar item in the View menu to hide the status bar. If checked, the status bar is visible.

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, batch files, or the specific platform equivalent.

Note: The HBAnyware utility can only discover and manage remote HBAs on hosts running

the HBAnyware utility’s elxhbamgr daemon.

Remote in-band capabilities of the HBAnyware utility are subject to fabric zoning configuration. Remote hosts you want to discover and manage using the HBAnyware utility must be in the same zone or discovered and managed out-of-band through an Ethernet connection.

Solaris SFS Driver User Manual Page 22

Using the CLI Client

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 first parameter of this command is the requested operation. When the specified operation is completed, the command prompt is displayed. Most operations retrieve information about an entity on the SAN and display that information on the console.

Most of the CLI Client commands require one or more additional parameters that specify the nature of the command. A parameter used by many hbacmd commands specifies the World Wide Port Name (WWPN) of the HBA that is the target of the command. For example, the following command shows the port attributes for the HBA with the specified WWPN:

/usr/sbin/hbanyware/hbacmd portattrib 10:00:00:00:c9:20:20:20

hbacmd can be run in out-of-band mode by making the first argument h=<host>. For example:

/usr/sbin/hbanyware/hbacmd h=cp-hp5670 listhbas /usr/sbin/hbanyware/hbacmd h=138.239.91.121 listhbas

Syntax Rules

The syntax rules for the HBAnyware utility Command-Line Interface (hbacmd) are as follows:

• All commands and their arguments are NOT case sensitive.

• The requested operation must contain at least three characters, or as many as needed to distinguish it from any other operation.

• Whenever a WWPN is specified, individual fields are separated by colons (:) or spaces ( ). When using space separators, the entire WWPN must be enclosed in quotes (").

• All hbacmd inputs must be in hexadecimal format. The only exceptions are the cycle-counts used in some of the diagnostic commands.

Out-of-Band Access

Out-of-band (OOB) access enables you to access HBAs via their IP-address or by the name of the host on which they reside. Since HBAs may exist on a host but not be a part of a FC network, they will not appear during normal in-band discovery. Thus, OOB access enlarges the number of HBAs that can be queried or modified.

Note: A local host cannot be accessed out-of-band.

OOB access via hbacmd uses an additional parameter on the command line. The parameter must be the first parameter in the list, coming immediately after hbacmd. The remaining parameters are those documented for each operation.

Note: You can also access an in-band HBA via its OOB address.

The format of the OOB parameter is:

h={<IPAddress> | <host-name>}

Some examples are:

h=128.239.91.88 h=cp-compaq8000

The following lists all HBAs running on the host with a specified IP address:

hbacmd h=128.239.91.88 listHBAs

Solaris SFS Driver User Manual Page 23

If you don’t know the IP address, but you know the host name, type:

hbacmd h=cp-compaq8000 listHBAs

If the host is unreachable, the command will return an error.

CLI Client Command Reference

Version

Syntax: HBACMD Version

Description: Shows the current version of the HBAnyware CLI client application. To view the version, type:

hbacmd version

Sample response:

HBAnyware Command Line Interface: Version 3.0

Parameters: None.

ListHBAs

Syntax: HBACMD ListHBAs

Description: Shows a list of the discovered manageable Emulex HBAs and some of their attributes. The list will contain one 6-attribute group for each discovered HBA. Example of an attribute group list:

Manageable HBA List Port WWN: 10:00:00:00:c9:20:08:cc Node WWN: 20:00:00:00:c9:20:08:cc Fabric Name:10:00:00:60:69:90:0b:f6 Flags: 0000f900 Host Name: CP-EMULEX-DECPC Mfg: Emulex Corporation

Parameters: None.

SaveConfig

Syntax: HBACMD SaveConfig <wwpn> <filename> <ctrlword>

Description: Saves the contents of the driver parameter list to a file for the specified HBA. The ASCII file lists parameter definitions, delimited by a comma. Each definition is of the form:

<parameter-name>=<parameter-value>

Save either the values of the global set or those specific to the referenced HBA. The file created by this command stores itself in the Emulex Repository directory.

Example:

hbacmd SaveConfig elxstor-5-1.20A0.dpv 10:00:00:00:c9:2e:51:2e N

Sample response:

HBACMD_SaveConfig: Success writing driver parameters to file C:\Program Files\HBAnyware\Emulex Repository\elxstor-5-1.20A.dpv

Parameters:

WWPN - The World Wide Port Name of the HBA. This HBA can be either local or remote.

filename - The file name that will contain the driver parameter list upon successful completion of this command.

ctrlword - G = save the global parameter set. N = save the local (HBA-specific) parameter set.

Solaris SFS Driver User Manual Page 24

HBAAttrib

Syntax: HBACMD HBAAttrib <wwpn>

Description: Shows a list of all attributes for the HBA with the specified WWPN. To view attributes, type:

hbacmd hbaattrib 10:00:00:00:c9:20:08:cc

Sample response:

HBA Attributes for 10:00:00:00:c9:4a:c5:90

Host Name : localhost.localdomain Manufacturer : Emulex Corporation Serial Number : BG53059073 Model : LP1150-F4 Model Desc : Emulex LP1150-F4 4Gb 1port FC: PCI-X2 SFF HBA Node WWN : 20 00 00 00 c9 4a c5 90 Node Symname : Emulex LP1150-F4 FV2.10A5 DV8.0.16.25 HW Version : 1036406d Opt ROM Version: FW Version : 2.10A5 (J2F2.10A5) Vender Spec ID : 10DF Number of Ports: 1 Driver Name : lpfc Device ID : F0D5 HBA Type : LP1150-F4 Operational FW : SLI-2 Overlay SLI1 FW : SLI-1 Overlay 2.10a5 SLI2 FW : SLI-2 Overlay 2.10a5 IEEE Address : 00 00 c9 4a c5 90 Boot BIOS : Disabled Driver Version : 8.0.16.25; HBAAPI(I) v2.1.c, 02-02-06 Kernel Version : 1.11a5

Parameters:

WWPN - The World Wide Port Name of the HBA. This HBA can be either local or remote.

PortAttrib

Syntax: HBACMD PortAttrib <wwpn>

Description: Shows a list of all attributes for the port with the specified WWPN. To view attributes, type:

hbacmd portattrib 10:00:00:00:c9:20:08:cc

Sample response:

Port Attributes for 10:00:00:00:c9:4a:c5:90

Node WWN : 20 00 00 00 c9 4a c5 90 Port WWN : 10 00 00 00 c9 4a c5 90 Port Symname : Port FCID : 11400 Port Type : Fabric Port State : Operational Port Service Type : 12 Port Supported FC4 : 00 00 01 20 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Port Active FC4 : 00 00 01 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Port Supported Speed: Unknown Port Speed : 2 GBit/sec. Max Frame Size : 2048 OS Device Name : /sys/class/scsi_host/host10 Num Discovered Ports: 3

Solaris SFS Driver User Manual Page 25

Fabric Name : 10 00 00 60 69 50 15 25

Parameters:

WWPN - The World Wide Port Name of the port. This port can be either local or remote.

PortStat

Syntax: HBACMD PortStat <wwpn>

Description: Shows all port statistics for the HBA with the specified WWPN. To view port statistics for the HBA, type:

hbacmd portstat 10:00:00:00:c9:20:08:cc

Sample response:

Port Statistics for 10:00:00:00:c9:20:08:cc

Exchange Count : 1496534 Responder Exchange Count: 37505 TX Seq Count : 1588007 RX Seq Count : 1561255 TX Frame Count : 1588695 RX Frame Count : 1561892 TX Word Count : 19821312 RX Word Count : 66368000 TX KB Count : 77427 RX KB Count : 259250 LIP Count : 1 NOS Count : n/a Error Frame Count : 0 Dumped Frame Count : n/a Link Failure Count : 0 Loss of Sync Count : 9 Loss of Signal Count : 0 Prim Seq Prot Err Count : 0 Invalid TX Word Count : 0 nvalid RX Frame CRC Cnt : 0 Link Transition Count : 0 Active RPI Count : 0 Active XRI Count : 0 Rx Port Busy Count : 0 Rx Fabric Busy Count : 0 Primary Sequence Timeout: 0 Elastic Buffer Overrun : 0 Arbitration Timout : 0

Parameters:

WWPN - The World Wide Port Name of the port. This port can be either local or remote.

ServerAttrib

Syntax: HBACMD ServerAttrib <WWPN>

Description: Shows a list of attributes of the server running locally to the specified HBA. To view the server attributes for the HBA, type:

hbacmd serverattrib 10:00:00:00:c9:20:08:cc

Sample response:

Server Attributes for 10:00:00:00:c9:4a:c5:90

Host Name : localhost.localdomain FW Resource Path: /usr/sbin/hbanyware/RMRepository/ DR Resource Path: /usr/sbin/hbanyware/RMRepository/ HBAnyware Server Version: 3.0

Parameters:

Solaris SFS Driver User Manual Page 26

WWPN - The World Wide Port Name of any HBA local to the designated server. The HBA itself can be either local or remote.

Target Ma pping

Syntax: HBACMD TargetMapping <wwpn>

Description: Shows a list of mapped targets and the LUNs attached to each for the port with the specified WWPN. To view the target mapping for 10:00:00:00:c9:20:08:0c, type:

hbacmd targetmapping 10:00:00:00:c9:20:08:0c

Sample response:

Target Mapping for 10:00:00:00:c9:4a:c5:90

FCP ID : 115E2 SCSI Bus Number: 0 SCSI Target Num: 0 Node WWN : 50:00:60:E8:02:78:6E:03 Port WWN : 50:00:60:E8:02:78:6E:03 Tgt Device Name: /dev/sdb

FCP LUN 00 : 0000 0000 0000 0000 SCSI OS Lun : 0 Lun Device Name: /dev/sdb Vendor ID : HITACHI Product ID : OPEN-3 Product Version: 0118 SCSI Capacity : 2347 MB Block Size : 512 Bytes

FCP LUN 01 : 0001 0000 0000 0000 SCSI OS Lun : 1 Lun Device Name: /dev/sdb Vendor ID : HITACHI Product ID : OPEN-3 Product Version: 0118 SCSI Capacity : 2347 MB Block Size : 512 Bytes

FCP LUN 02 : 0002 0000 0000 0000 SCSI OS Lun : 2 Lun Device Name: /dev/sdb Vendor ID : HITACHI Product ID : OPEN-3 Product Version: 0118 SCSI Capacity : 2347 MB Block Size : 512 Bytes

Parameters:

WWPN - The World Wide Port Name of the port. This port can be either local or remote.

Reset

Syntax: HBACMD Reset <wwpn>

Description: Resets the HBA with the specified WWPN. Resetting an HBA may require several seconds to complete, especially for remote devices. This command will return for additional input only after the reset has finished. To reset an HBA whose WWPN is 10:00:00:00:c9:e:51:2e, type:

hbacmd reset 10:00:00:00:c9:2e:51:2e

Sample response:

Reset HBA 10:00:00:00:c9:2e:51:2e

Solaris SFS Driver User Manual Page 27

Parameters:

WWPN - The World Wide Port Name of the port. This port can be either local or remote.

Download

Syntax: HBACMD Download <wwpn> <filename>

Description: Loads the specified firmware image to the HBA with the specified WWPN. To load the firmware image located in hdc190a4.dwc to an HBA with WWPN 10:00:00:00:c9:2e:51:2e, type:

hbacmd download 10:00:00:00:c9:2e:51:2e hdc190a4.dwc

Sample response for a successful download:

Downloading hdc190a4.dwc to hba 10:00:00:00:c9:2e:51:2e Download Complete.

Parameters:

WWPN - The World Wide Port Name of the HBA that is the target of the firmware download. This HBA can be either local or remote.

FileName - The file name of the firmware image you want to load. This can be any file accessible to the CLI client application.

AllNodeInfo

Syntax: HBACMD AllNodeInfo <wwpn>

Description: Shows target node information for each target accessible from the specified HBA. To view the target node data for 10:00:00:00:c9:20:0d:36, type:

Hbacmd allnodeinfo 10:00:00:00:c9:20:0d:36

Sample response:

All Node Info for 10:00:00:00:c9:4a:c5:90

Node Type : EXIST FCP ID : 115E2 SCSI Bus Number: 0 SCSI Target Num: 0 Node WWN : 50:00:60:E8:02:78:6E:03 Port WWN : 50:00:60:E8:02:78:6E:03 OS Device Name : /sys/class/scsi_host/host10/device/target10:0:0

Parameters:

WWPN - The World Wide Port Name of the HBA whose target node information you want to query. This HBA can be either local or remote.

DriverConfig

Syntax: HBACMD driverconfig <wwpn> elxconfig.dpv <ctrlword>

Description: Sets all driver parameters for the HBA specified by WWPN to the driver parameter values contained in the driver parameter file (elxconfig.dpv in the above example). These files can be easily generated via the HBAnyware Driver Parameter tab. Driver types must match between .dpv file type and host platform HBA.

For example, type:

hbacmd driverconfig 10:00:00:00:c9:2e:51:2e elxconfig G

Below is a sample response:

hbacmd: Success setting driver configuration parameters to values in .dpv file.

Solaris SFS Driver User Manual Page 28

Parameters:

WWPN - The World Wide Port Name of the HBA on which to set driver parameters.

ctrlword - G = save the global parameter set.

DriverParams

Syntax: HBACMD DriverParams <wwpn>

Description: Shows the name and values of each driver parameter for the selected HBA. To view the driver parameters for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd driverparams 10:00:00:00:c9:2e:51:2e

Sample (abbreviated) response:

Driver Params for 10:00:00:00:c9:4a:c5:90. Values in HEX format.

DX string Low High Def Cur Exp Dyn 00 log-verbose 0 ffff 0 20 1 1 01 lun-queue-depth 1 80 1e 1e 1 4 02 scan-down 0 1 1 1 1 4 03 nodev-tmo 0 ff 1e 3c 1 1 04 topology 0 6 0 0 1 4 05 link-speed 0 4 0 0 1 4 06 fcp-class 2 3 3 3 1 4 07 use-adisc 0 1 0 1 1 1 08 ack0 0 1 0 0 1 4 09 fcp-bind-method 1 4 2 2 1 4 0a cr-delay 0 3f 0 0 1 4 0b cr-count 1 ff 1 1 1 4 0c fdmi-on 0 2 0 0 1 4 0d discovery-threads 1 40 20 20 1 4 0e max-luns 1 8000 100 100 1 4

Parameters:

WWPN - The World Wide Port Name of the HBA whose driver parameters you want to view. This HBA can be either local or remote.

DriverParamsGlobal

Syntax: HBACMD DriverParamsGlobal <wwpn>

Description: Shows the name and the global value of each driver parameter for the selected HBA. To view the global driver parameters for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd driverparamsglobal 10:00:00:00:c9:2e:51:2e

Sample (abbreviated) response:

Driver Params (Global) for 10:00:00:00:c9:2e:51:2e. Values in HEX.

DX string Low High Def Cur Exp Dyn 00 AbortStatus 0 ff e e 1 1 01 ARBTOV 1f4 4e20 5dc 5dc 1 5 02 BlinkTimeOut 1 1E 8 8 1 0 03 Class 1 2 2 2 1 1

Solaris SFS Driver User Manual Page 29

04 CrfIntrpt 0 1 0 0 1 5 05 CrfMsCnt 0 3f 0 0 1 5 06 CrfRspCnt 0 ff 0 0 1 5 07 DebugMask 0 efffffff 0 0 0 5 08 DisableAck0 0 1 0 0 1 5 09 DiscMethod 0 1 1 0 1 1 0a DiscoveryDelay 0 7 0 0 1 1 0b ElsRetryCount 1 ff 1 1 1 1 0c ElsRjtCount 0 ff 2d 2d 1 1 0d ElsTimeOut 0 1 0 0 1 1 0e EmulexOption 0 7fffffff d200 da00 1 0 0f EnableDPC 0 1 0 1 1 1 10 ErrRetryMax 0 fffffffe 1 1 1 1 11 FrameSizeMSB 0 8 0 0 1 5 12 HardAddress 0 1 0 0 1 0 13 HlinkTimeOut 0 ff 1e 1e 1 1 14 InitialDelay 0 1 1 1 1 0 15 LinkSpeed 0 10 0 0 1 1 16 LinkTimeOut 1f4 3c 3c 1 1 17 LipFFrecovery 0 1 0 0 1 1 18 LogErrors 0 1 0 0 1 1 19 MapNodeName 0 1 0 0 1 0 1a NodeTimeOut 0 ff 14 14 1 1 1b QueueAction 0 2 0 0 1 1 1c QueueDepth 1 ff 20 20 1 1 1d QueueTarget 0 1 0 0 1 5 1e QueueIncStep 0 100 2 2 1 1 1f RegFcpType 0 1 1 1 1 1 20 ResetFF 0 1 0 0 1 1 21 ResetTPRLO 0 2 0 0 1 1 22 RetryNodePurge 0 1 1 1 1 1 23 RTTOV a ff 64 64 1 5

Parameters:

WWPN - The World Wide Port Name of the HBA whose driver parameters you want to view. This HBA can be either local or remote.

SetDriverParam

Note: This command may only be used with the lpfc_log_verbose, lpfc_use_adisc and

lpfc_nodev_tmo parameters.

Syntax: HBACMD SetDriverParam <wwpn> <ctrlword> <param> <value>

Description: Changes the value of the specified driver parameter that is operating the referenced HBA, and designates the scope of that change. For example, to change the value of the log_verbose parameter for 10:00:00:00:c9:2e:51:2e and make it global, type:

hbacmd SetDriverParam 10:00:00:00:c9:2e:51:2e g log_verbose 3

Solaris SFS Driver User Manual Page 30

Sample response:

Set Driver Parameter log_verbose=3(g) for 10:00:00:00:c9:2e:51:2e

Parameters:

WWPN - The World Wide Port Name of the HBA whose Boot BIOS you want to modify. This HBA can be either local or remote.

ctrlword - G = make change global, B = make change both permanent and global, N = make change neither permanent nor global

param - The name of the parameter whose value you want to modify. You can only use the log_verbose, use_adisc and _nodev_tmo parameters. Do not precede these commands with lpfc_. For example use log_verbose not lpfc_log_verbose.

Value - The new value you want to assign to the parameter.

SetBootBios

Syntax: HBACMD SetBootBios <wwpn> <ctrlword>

Description: Enables or disables the Boot BIOS on the referenced HBA. To enable the Boot BIOS for 10:00:00:00:c9:2e:51:2e, type:

hbacmd setbootbios 10:00:00:00:c9:2e:51:2e E

Parameters:

WWPN - The World Wide Port Name of the HBA whose Boot BIOS you want to modify. This HBA can be either local or remote.

ctrlword - E = enable the Boot BIOS, D = disable the Boot BIOS.

PciData

Syntax: HBACMD PciData <wwpn>

Description: Shows PCI configuration data for the HBA specified by the WWPN. To show PCI configuration data for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd pcidata 10:00:00:00:c9:2e:51:2e

Sample response:

Vendor ID: 0x10DF Device ID: 0xF0D5 Command: 0x0157 Status: 0x0230 Revision ID: 0x01 Prog If: 0x00 Subclass: 0x04 Base Class: 0x0C Cache Line Size: 0x20 Latency Timer: 0xF8 Header Type: 0x00 Built In Self Test: 0x00 Base Address 0: 0xE0001004 Base Address 1: 0x00000000 Base Address 2: 0xE0000004 Base Address 3: 0x00000000 Base Address 4: 0x0000C001 Base Address 5: 0x00000000 CIS: 0x00000000 SubVendor ID: 0x10DF SubSystem ID: 0xF0D5 ROM Base Address: 0x00000000 Interrupt Line: 0xFF Interrupt Pin: 0x01 Minimum Grant: 0xFF Maximum Latency: 0x00 Capabilities Ptr: 0x5C

Parameters:

WWPN - The World Wide Port Name of the HBA whose PCI configuration data you want to show.

Solaris SFS Driver User Manual Page 31

Wakeup

Syntax: HBACMD wakeup <wwpn>

Description: Shows wakeup parameter data for the HBA specified by the WWPN. To show wakeup parameter data for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd wakeup 10:00:00:00:c9:2e:51:2e

Sample response:

Wakeup Parameters: Initial Load: 0x02C03992 0x00103411 Flags: 0x00000000 Boot BIOS 0x03433290 0x00101303 SLI-1: 0x06433992 0x00103411 SLI-2: 0x07433992 0x00103411 Has Expansion ROM 0

Parameters:

WWPN - The World Wide Port Name of the HBA whose wakeup parameter data you want to show.

LoopMap

Syntax: HBACMD loopmap <wwpn>

Description: Shows the arbitrated loop map data for the HBA specified by the WWPN. To show the arbitrated loop map data for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd loopmap 10:00:00:00:c9:2e:51:2e

Below is a sample response:

AL_PA: 01 Local Adapter E8 SCSI Device E4 SCSI Device CA SCSI Device

Parameters:

WWPN - The World Wide Port Name of the HBA whose loopmap you want to show.

GetBeacon

Syntax: HBACMD getbeacon <wwpn>

Description: Shows the current beacon status for the HBA specified by the WWPN. To show the current beacon status for HBA 10:00:00:00:c9:2e:51:2e, type:

For example, type:

hbacmd getbeacon 10:00:00:00:c9:2e:51:2e

Possible responses are:

Beacon State = On Beacon State = Off Unable to get Beacon state, error 1 Beaconing not supported on host or adapter

Parameters:

WWPN - The World Wide Port Name of the HBA whose beacon status you want to show.

Solaris SFS Driver User Manual Page 32

SetBeacon

Syntax: HBACMD setbeacon <wwpn> <state>

Description: Sets the current beacon status for the HBA specified by the WWPN. To set the current beacon status for HBA 10:00:00:00:c9:2e:51:2e to off, type:

hbacmd setbeacon 10:00:00:00:c9:2e:51:2e 0

To set the current beacon status for HBA 10:00:00:00:c9:2e:51:2e to on, type:

hbacmd setbeacon 10:00:00:00:c9:2e:51:2e 1

Possible responses are:

Beacon State successfully set to On Beacons State successfully set to Off Unable to get Beacon state, error 1 Beaconing not supported on host or adapter

Parameters:

WWPN -The World Wide Port Name of the HBA whose beacon status you want to set. This HBA can be either local or remote.

State - The new state of the beacon: 0 = beacon OFF, 1= beacon ON

PostTest

Syntax: HBACMD posttest <wwpn>

Description: Runs the POST test on the HBA specified by the WWPN. Support for remote HBA is out-ofband (Ethernet) only. To run the POST test for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd posttest 10:00:00:00:c9:2e:51:2e

Sample response:

Running POST, polling for results.....

Power On Self Test Succeeded;time to execute = 8928 ms

Parameters:

WWPN - The World Wide Port Name of the HBA on which to run the POST test.

EchoTest

Syntax: HBACMD echotest <wwpn1> <wwpn2> <count> <StopOnError>

Description: Runs the echo test on the HBAs specified by the WWPN1 and WWPN2.

Note: Support for remote HBA is out-of-band (Ethernet) only. The EchoTest command will

fail if the target WWPN does not support the ECHO ELS command.

To run the echo test for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd echotest 10:00:00:00:c9:2e:51:2e 10:00:00:00:c9:2e:51:45 10 1

Sample response:

Echo test: polling for results......

Echo test succeeded; time to execute = 53 ms.

Parameters:

WWPN1 - The World Wide Port Name of the originating HBA.

WWPN2 - The World Wide Port Name of the destination (echoing) HBA.

Solaris SFS Driver User Manual Page 33

Count - The number of times to run the test.

StopOnError - Should the test be halted on Error? 0 = no halt, 1 = halt

Loopback

Syntax: HBACMD loopback <wwpn> <type> <count> <StopOnError>

Description: Runs the loop test on the HBA specified by the WWPN.

Note: Only external Loopback tests must be run out-of-band.

To run the loop test for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd loopback 10:00:00:00:c9:2e:51:2e 1 10 0

Sample response:

Running Loopback: polling for results......

Loopback Test Failed; xmit errors = 3; rcv errors = 2; time to execute = 1015 ms.

Parameters:

WWPN - The World Wide Port Name of the HBA on which to run the loopback test(s).

Type -Type of loopback test where: 0 = PCI LoopBack Test, 1 = Internal LoopBack Test, 2 = External LoopBack Test

Count - The number of times to run the test (Range = 1,...10000)

StopOnError - Should the test be halted on Error? 0 = no halt, 1 = halt

Dump

Syntax: HBACMD dump <wwpn>

Description: Runs the dump diagnostic retrieval command on the HBA specified by the WWPN. This command is supported for local HBAs only. The file by default is located in: /usr/sbin/hbanyware/Dump

To run the dump diagnostic retrieval command for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd dump 10:00:00:00:c9:2e:51:2e

Parameters:

WWPN - The World Wide Port Name of the HBA on which to you want to run the dump.

DeleteDumpFiles

Syntax: HBACMD deletedumpfiles <wwpn>

Description: Deletes all dump files associated with the HBA specified by the WWPN. To delete all dump files for HBA 10:00:00:00:c9:2e:51:2e, type:

hbacmd deletedumpfiles 10:00:00:00:c9:2e:51:2e

Sample response:

HBACMD: Dump file deletion complete.

Parameters:

WWPN - The World Wide Port Name of the HBA whose dump files you want to delete.

Solaris SFS Driver User Manual Page 34

PersistentBinding

Syntax: HBACMD PersistentBinding <wwpn> <source>

Description: Queries the presence of any persistent binding that may exist for the specified WWPN. The <source> is used to query either the configured or live state of any binding that may be present. To view the configured persistent binding for an adapter whose WWPN is 10:00:00:00:c9:20:0d:36, enter:

hbacmd persistentbinding 10:00:00:00:c9:20:0d:36 C

Sample response:

Persistent Binding for 10:00:00:00:c9:20:0d:36 Bind Type : WWPN FCP ID : 10101SCSI Bus Number: 0SCSI Target Num: 0Node WWN : 20:00:00:D0:B2:00:30:40 Port WWN : 20:00:00:D0:B2:00:30:40 OS Device Name : \\.\Scsi:4:0

Bind Type : WWPN FCP ID : 10FEFSCSI Bus Number: 0SCSI Target Num: 1Node WWN : 50:06:04:8A:CC:C8:99:00 Port WWN : 50:06:04:8A:CC:C8:99:00 OS Device Name : \\.\Scsi:4:1

If the binding does not exist, only the first line is returned.

Parameters:

WWPN - The World Wide Port Name of the HBA whose dump files you want to delete.

source - C if the configured state is being queried. L if the live state is being queried.

SetPersistentBinding

Syntax: HBACMD SetPersistentBinding <wwpn> <scope> <bindtype> <ID> \ <scsibus> <scsitarget>

Description: Sets a persistent binding between a Fibre Channel target and a Scsi bus and target. The binding can be to a target WWPN, target WWNN, or target D_ID. To bind permanently, on behalf of HBA 10:00:00:00:c9:2e:51:2e, target WWPN 20:00:00:d0:b2:00:30:40 to Scsi bus 1, target 3, enter:

hbacmd setpersistentbinding 10:00:00:00:c9:2e:51:2e P P \ 20:00:00:d0:b2:00:30:40 1 3

To bind immediately, on behalf of HBA 10:00:00:00:c9:2e:51:2e, target D_ID 10101 to Scsi bus 1, target 3, enter:

hbacmd setpersistentbinding 10:00:00:00:c9:2e:51:2e I D \ 10101 1 3

If there are no errors, a response to the last example would be:

Set Persistent Binding for 10:00:00:00:c9:2e:51:2e I D \ 10101 1 3

Parameters:

WWPN - The World Wide Port Name of the HBA for which a persistent binding is to be set. This HBA can be either local or remote.

scope - P = binding is permanent (survives across reboot). I = binding is immediate. B = binding is both permanent and immediate.

bindtype - P = enable binding by WWPN. N = enable binding by WWNN. D = enable binding by D_ID.

Solaris SFS Driver User Manual Page 35

ID - Target WWPN if bindtype = P. Target WWNN if bindtype = N. Target D_ID if bindtype = D

scsibus - Bus number of SCSI device.

scsitarget - Target number of SCSI device.

RemoveAllPersistentBinding

Syntax: HBACMD RemoveAllPersistentBinding <wwpn>

Description: Removes all persisting bindings associated with the referenced HBA. To remove all persistent bindings for 10:00:00:00:c9:21:5e:21, enter:

hbacmd removeallpersistentbinding 10:00:00:00:c9:21:5e:21

A sample response would be:

Remove All Persistent Binding for 10:00:00:00:c9:2e:51:2e

Parameters:

WWPN - The World Wide Port Name of the HBA for which all persistent bindings are to be removed. This HBA can be either local or remote.

RemovePersistentBinding

Syntax: HBACMD RemovePersistentBinding <wwpn> <bindtype> <ID> \ <scsibus> <scsitarget>

Description: Removes a persistent binding between a Fibre Channel target and a SCSI bus and target. The binding to be removed can be to a target WWPN, target WWNN, or target D_ID. To remove, on behalf of HBA 10:00:00:00:c9:2e:51:2e, the binding between target WWPN=20:00:00:d0:b2:00:30:40 and SCSI bus 1, target 3, enter:

hbacmd removepersistentbinding 10:00:00:00:c9:2e:51:2e P \ 20:00:00:d0:b2:00:30:40 1 3

To remove, on behalf of HBA 10:00:00:00:c9:2e:51:2e, the binding between target D_ID=10101 and SCSI bus 1, target 3, enter:

hbacmd removepersistentbinding 10:00:00:00:c9:2e:51:2e D \ 10101 1 3

If there are no errors a response to the last example would be:

Remove Persistent Binding for 10:00:00:00:c9:2e:51:2e D \ 10101 1 3

Parameters:

WWPN - The World Wide Port Name of the HBA for which a persistent binding is to be removed. This HBA can be either local or remote.

bindtype - P = enable binding by WWPN. N = enable binding by WWNN. D = enable binding by D_ID.

ID - Target WWPN if bindtype = P. Target WWNN if bindtype = N. Target D_ID if bindtype = D.

scsibus - Bus number of SCSI device.

scsitarget - Target number of SCSI device.

Solaris SFS Driver User Manual Page 36

BindingCapabilities

Syntax: HBACMD BindingCapabilities <wwpn>

Description: Displays the binding capabilities present at the referenced HBA. To view the binding capabilities at 10:00:00:00:c9:21:5e:21, enter:

hbacmd bindingcapabilities 10:00:00:00:c9:21:5e:21

Sample response:

Binding Capability for 10:00:00:00:c9:2e:51:2e Can bind to D_IDCan bind to WWPN Can bind to WWNN Can bind AUTOMAP Can bind CONFIGURED

Parameters:

WWPN - The World Wide Port Name of the HBA whose binding capabilities are being queried. This HBA can be either local or remote.

BindingSupport

Syntax: HBACMD BindingSupport <wwpn> <source>

Description: Displays the binding support available at the reference HBA. The view the configured binding support for 10:00:00:00:c9:21:5e:21, enter:

hbacmd bindingsupport 10:00:00:00:c9:21:5e:21 C

Sample response:

Binding Support for 10:00:00:00:c9:2e:51:2e Can bind to WWPN Can bind AUTOMAP

Parameters:

WWPN - The World Wide Port Name of the HBA whose binding support is being queried. This HBA can be either local or remote.

source - C if the configured support is being queried. L if the live support is being queried.

SetBindingSupport

Syntax: HBACMD SetBindingSupport <wwpn> <bindflag>

Description: Sets the binding support(s) for the reference HBA. To enable binding support for WWPN and Automap on HBA 10:00:00:00:c9:21:5e:21, enter:

hbacmd setbindingsupport 10:00:00:00:c9:21:5e:21 P1

Sample response:

Set Binding Support for 10:00:00:00:c9:21:5e:21 P1

Parameters:

WWPN - The World Wide Port Name of the HBA for which binding support is being set. This HBA can be either local or remote.

bindflag - 1 = enable support for Automap binding. 0 = disable support for Automap binding. P1 = enable support for WWPN binding and Automap. N1 = enable support for WWNN binding and Automap. D1 = enable support for D_ID binding and Automap. P0 = enable support for P, disable Automap. N0 = enable support for N, disable Automap. D0 = enable support for D, disable Automap.

Solaris SFS Driver User Manual Page 37

Discovering HBAs

Local and remote HBAs are discovered automatically when you launch the HBAnyware utility. Initially, both local and remote HBAs are displayed.

You can also discover HBAs on out-of-band (OOB) hosts. For more information, see on page 23.

Note: The HBAnyware utility must be installed and the elxhbamgr process(es) must be

running on all remote hosts that you want to discover and manage.

Out-of-Band Access

Figure 4: HBAnyware Utility, Discovery Information

Note: Emulex recommends setting the monitor display resolution to 1024x768 as a

minimum to properly view the HBAnyware utility.

Solaris SFS Driver User Manual Page 38

Configuring Discovery Settings

Use the HBAnyware Discovery Settings dialog box to configure several discovery server parameters. You can define when to start the discovery server, when to refresh in-band and out-of-band discoveries and when to remove previously discovered HBAs that are no longer being discovered.

Figure 5: HBAnyware Utility, HBA Discovery Settings Dialog Box

To configure discovery settings:

1. Start the HBAnyware utility.

2. From the menu bar, select Discovery/Modify Settings. The Discovery Settings dialog box appears.

3. Define the discovery properties you wish and click OK. Click Defaults to return the discovery properties to their default settings.

Solaris SFS Driver User Manual Page 39

Sorting HBAs

Sort discovered HBAs by host name, fabric name, HBA name, target name and LUN number. You can also choose to view local HBAs or remote HBAs. By default, both local and remote HBAs are sorted by host name/fabric name.

To sort HBAs:

1. Start the HBAnyware utility.

2. 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. The current adapter display mode is checked.

• From the toolbar, click one of the following buttons:

Sort HBAs by Host Name (default).

Sort HBAs by Fabric ID.

3. The HBAnyware utility sorts in ascending order. The sort recognizes letters, numbers, spaces and punctuation marks.

Sorting by Host Name

• Initially sorts by host name. You cannot change host names using the HBAnyware utility; names must be changed locally on that system.

• Within each host system, sorts by HBA model.

• If multiple HBAs have the same model number, sorts models by World Wide Node Name (WWNN).

• If targets are present, sorts by World Wide Port Name (WWPN). Multiple HBAs may refer to the same target.

• If LUNs are present, sorts by LUN number.

Sorting by Fabric Address

• Initially sorts by fabric ID.

• Within each fabric ID, sorts by HBA model.

• If multiple HBAs have the same model number, sorts models by WWNN.

• If targets are present, sorts by WWPN. Multiple HBAs may refer to the same target.

• If LUNs are present, sorts by LUN number.

• If the fabric ID is all zeros, no fabric is attached.

Sorting Local HBAs Only

Displays local HBA's only. Works in conjunction with the Sort by Host Name and Sort by Fabric ID buttons.

To display local HBAs only, do one of the following:

• From the menu bar: click View, then click Local HBAs Only. The current adapter display mode is checked.

• From the toolbar, click the Local HBAs Only

Solaris SFS Driver User Manual Page 40

button.

Viewing HBA Information

Viewing Discovery Information

The Discovery Information area 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 will reveal all hosts, LUNs, targets and HBAs that are visible on the storage area network (SAN).

To view the discovery information:

1. Start the HBAnyware utility.

2. Click the Host or Fabric icon at the root of the discovery-tree. Discovered SAN elements appear in the discovery-tree. Select an element from the discovery-tree to learn more about it.

Figure 6: HBAnyware Utility, Discovery Information

Discovery Information Field Definitions

• Number of Hosts - The total number of discovered host computers. This includes servers, workstations, personal computers, multiprocessors and clustered computer complexes.

• Number of Fabrics - The total number of discovered fabrics.

• Number of Adapters - The total number of discovered HBAs.

• Number of Targets - The total number of unique discovered targets on the SAN. In the discovery-tree, the same target can appear under more than one HBA.

Solaris SFS Driver User Manual Page 41

Viewing Host Information

There are two tabs that show host information: the Host Information tab and the host Driver Parameters tab. The Host Information tab is read-only. The host 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. Start the HBAnyware utility.

2. 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.

3. Select a host in the discovery-tree.

4. Select the Host Information tab (see Figure 7) or the Host Driver Parameters tab (Figure 8).

The Host Information Tab

Figure 7: HBAnyware Utility, Host Information Tab

Host Information Field Definitions

• Number of Adapters - The number of HBAs installed in the host.

• Number of Fabrics - The number of fabrics to which this host is attached.

• Number of Targets - The number of storage devices seen by the host.

• Remote Manager Server Version - The version of the HBAnyware utility server that is running on the host. If different versions of the HBAnyware utility are installed on different hosts in the SAN, those differences appear in this field.

• Host IP Address - If the host is discovered in-band, the dialog box displays "Host discovered inband." If the host is discovered out-of-band, the dialog box displays the host's IP address, e.g.,

138.239.82.131.

Solaris SFS Driver User Manual Page 42

The Host Driver Parameters Tab

The Host Driver Parameters tab (Figure 8) 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. For each parameter, the tab shows the current value, the range of acceptable values, the default value, and whether the parameter is dynamic (a dynamic parameter allows the change to take effect without resetting the HBA or rebooting the system).

For more information on changing the parameters for a single HBA, see

HBA

on page 61.For more information changing the parameters for the host, see Setting Driver Parameters

for a Host

on page 62.

Setting Driver Parameters for an

Figure 8: HBAnyware Utility, Driver Parameters Tab - Host Selected

Note: If there is more than one driver type installed, the Installed Driver Types menu shows a list of all driver types and driver versions that are installed on the HBAs in the host.

Driver Parameter Tab Field Definitions

• Installed Driver Type - The current driver and version installed.

• Adapter Parameter table - A list of HBA driver parameters and their current values.

• Parameter-specific information - The details about the parameter appears on the right side of the tab.

Driver Parameter Tab Buttons

• Restore - Click to save and restore parameters to this last saved value, if you have made changes to parameters and have not saved them by clicking Apply.

• Defaults - Click to reset all parameter values to their default (out-of-box) values.

• Apply - Click to apply any driver parameter changes. If you changed a parameter that is not dynamic, you must unload the driver and reload it.

Solaris SFS Driver User Manual Page 43

Viewing General HBA Attributes

The General tab contains general attributes associated with the selected HBA.

To view general attributes:

1. Start the HBAnyware utility.

2. Select Host or Fabric sort.

3. Click an HBA in the discovery-tree.

Figure 9: HBAnyware Utility, General Tab

Adapter Summary Field Definitions

• 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.

• Fabric Name or Host Name - The Fabric Name field shows if you selected, “Sort by Host Name”. The fabric name is a 64-bit worldwide unique identifier assigned to the fabric. The Host Name field shows if you selected “Sort by Fabric ID”. The host name is the name of the host containing the HBA.

• Driver Version - The version of the driver installed for the HBA.

• Firmware Version - The version of Emulex firmware currently active on the HBA.

• Driver Name - The executable file image name for the driver as it appears in the Emulex driver download package.

• Boot Bios - Indicates if the boot code is enabled or disabled.

Solaris SFS Driver User Manual Page 44

Adapter Status Area Field Definitions

State - The current operational state of the HBA: “Up” or “Down”.

Link Status - The current link status between the HBA and the fabric. There are several possible states:

• The “Operational” state indicates that the HBA is connected to the network and operating normally.

• All other states indicate that the HBA is not connected to the network. Green HBA icons with red descriptive text indicate that the HBA is offline. These offline states are:

• “User offline” - The HBA is down or not connected to the network.

• “Bypassed” - the HBA is in Fibre Channel discovery mode.

• “Diagnostic Mode” - The HBA is controlled by a diagnostic program.

• “Link Down” - There is no access to the network.

• “Port Error” - The HBA is in an unknown state; try resetting it.

• “Loopback” -an FC-1 mode in which information passed to the FC-1 transmitter is shunted directly to the FC-1 Receiver. When a FC interface is in loopback mode, the loopback signal overrides any external signal detected by the receiver.

• “Unknown” -The HBA is offline for an unknown reason.

• Link Speed - The link speed of the HBA in gigabits per second.

Solaris SFS Driver User Manual Page 45

Viewing Detailed HBA Information

The Adapter Details tab in the HBAnyware utility contains detailed information associated with the selected HBA.

To view the detailed attributes:

1. Start the HBAnyware utility.

2. Select Host or Fabric sort.

3. Select an HBA in the discovery-tree.

4. Select the Adapter Details tab.

Figure 10: HBAnyware Utility, Adapter Details Tab

Adapter Details Field Definitions

• Node Symbolic Name - The Fibre Channel 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 - The number of other HBAs visible to the selected HBA.

• Device ID - The HBA's default device ID.

Port Attributes Field Definitions

• Port FC ID - The Fibre Channel ID for the port of the selected HBA.

• Port Type - The current operational mode of the selected HBA’s port.

• OS Device Name - The platform-specific name by which the selected HBA is known to the operating system.

• Supported Class of Service - A frame delivery scheme exhibiting a set of delivery characteristics and attributes. There are three classes of service.

Solaris SFS Driver User Manual Page 46

• Class-1 provides a dedicated connection between a pair of ports confirmed with delivery or notification of nondelivery.

• Class-2 provides a frame switched service with confirmed delivery or notification of nondelivery.

• Class-3 provides a frame switched service similar to Class-2 but without notification of frame delivery or non-delivery.

• Supported FC4 Types - a 256-bit (8-word) map of the FC-4 protocol types supported by the port containing the selected HBA.

Loop Map Table Definitions

• 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

The Discovery Information area contains information about the selected fabric.

To view the fabric information:

1. Start the HBAnyware utility.

2. Do one of the following:

• From the menu bar, click View, then click Sort by Fabric ID.

• From the toolbar, click the Sort by Fabric ID button.

3. Click on a fabric address in the discovery-tree. The Discovery Information tab shows information about the selected fabric.

Figure 11: HBAnyware Utility, Discovery Information

Solaris SFS Driver User Manual Page 47

Discovery Information Field Definitions

• Number of Hosts - The number of hosts discovered or seen by this host on the selected fabric.

• Number of Fabrics - The number fabrics identified during discovery.

• Number of Adapters - The number of HBAs discovered by this host on the selected fabric.

• Number of Targets - The number of storage devices seen by this host on the selected fabric.

Viewing Target Information

The Target Information area contains information specific to the selected storage device.

To view target information:

1. Start the HBAnyware utility.

2. 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.

3. Click a target in the discovery-tree. The Target Information tab appears.

Figure 12: HBAnyware Utility, Target Information

Target Information Field Definitions

• Mapping Information Area

• FC ID - The Fibre Channel ID for the target; assigned automatically in the firmware.

• SCSI Bus Number - Defines the SCSI bus to which the target is mapped.

• SCSI Target Number - The target's identifier on the SCSI bus.

Solaris SFS Driver User Manual Page 48

• Node WWN - A unique 64-bit number, in hexadecimal, for the target (N_PORT or NL_PORT).

• Port WWN - A unique 64-bit number, in hexadecimal, for the fabric (F_PORT or FL_PORT).

• OS Device Name - The operating system device name.

Viewing LUN Information

The LUN Information area contains information about the selected logical unit number (LUN).

To view the LUN information:

1. Start the HBAnyware utility.

2. 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.

3. Click on a LUN in the discovery-tree.

Figure 13: HBAnyware Utility, LUN Information

LUN Information Field Definitions

• Vendor Product Information Area

• Vendor ID - The name of the vendor of the LUN.

• Product ID - The vendor-specific ID for the LUN.

• Revision - The vendor-specific revision number for the LUN.

• Mapping Information Area

• FCP LUN - The Fibre Channel identifier used by the HBA to map to the SCSI OS LUN.

Solaris SFS Driver User Manual Page 49

• SCSI OS LUN - The SCSI identifier used by the operating system to map to the specific LUN.

• OS Device Name - The name assigned by the operating system to the selected LUN.

• LUN Capacity

Note: LUN capacity information is only provided when the LUN is a mass-storage (disk)

device. Other devices like tapes and scanners, etc. do not display capacity.

• Capacity - The capacity of the LUN, in megabytes.

• Block Length - The length of a logical unit block in bytes.Capacity - the capacity of the logical unit, in megabytes.

• Block Length - the length of a logical unit block in bytes.

Viewing Port Statistics

The Statistics tab provides cumulative totals for various error events and statistics on the port. Some statistics are cleared when the HBA is reset.

To view port statistics:

1. Start the HBAnyware utility.

2. Select Host or Fabric sort.

3. Click an HBA in the discovery-tree.

4. Click the Statistics tab.

Figure 14: HBAnyware Utility, Statistics Tab

Solaris SFS Driver User Manual Page 50

Port Statistics Field Definitions

• Tx Frames - Fibre Channel frames transmitted by this HBA port.

• Tx Words - Fibre Channel words transmitted by this HBA port.

• Tx KB Count - Fibre Channel kilobytes transmitted by this HBA port.

• Tx Sequences - Fibre Channel 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. Loop initialization consists of the following:

• Temporarily suspend loop operations.

• Determine whether loop capable ports are connected to the loop.

• Assign AL_PA IDs.

• Provide notification of configuration changes and loop failures.

• Place loop ports in the "monitoring" state.

• Error Frames - The number of frames received with cyclic redundancy check (CRC) errors.

• Link Failures - The number of times the link failed. A link failure is a possible cause of a time-out.

• Loss of Signal - The number of times the signal was lost.

• Invalid Tx Words - The total number of invalid words transmitted by this HBA port.

• Ex Count Orig - The number of Fibre Channel exchanges originating on this port.

• Active XRIs - The number of active exchange resource indicators.

• Received P_BSY - The number of FC port-busy link response frames received.

• Link Transitions - The number of times the SLI port sent a link attention condition.

• Elastic Buf Overruns - The number of times the link interface has had its elastic buffer overrun.

• Rx Frames - The number of Fibre Channel frames received by this HBA port.

• Rx Words - The number of Fibre Channel words received by this HBA port.

• Rx KB Count - The received kilobyte count by this HBA port.

• Rx Sequences - The number of Fibre Channel 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.

• Loss of Sync - The number of times loss of synchronization has occurred.

• Prim Seq Prot Errs - The primitive sequence protocol error count. This counter increments whenever there is any type of protocol error.

• Invalid CRCs - The number of frames received that contain CRC failures.

• Ex Count Resp - The number of Fibre Channel exchange responses made by this port.

• Active RPIs - The number of remote port indicators.

• Receive F_BSY - The number of Fibre Channel port-busy link response frames received.

• Primitive Seq Timeouts - The number of times a primitive sequence event timed out.

• Arbitration Timeouts - The number of times the arbitration loop has timed out. Large counts could indicate a malfunction somewhere in the loop or heavy usage of the loop.

Solaris SFS Driver User Manual Page 51

Viewing Firmware Information

Use the Firmware tab to view current firmware versions, enable system BIOS and update firmware on remote and local HBAs. The update procedure is on page 55.

To view the firmware information:

1. Start the HBAnyware utility.

2. Select Host or Fabric sort.

3. Select an HBA in the discovery-tree.

4. Select the Firmware tab.

Figure 15: HBAnyware Utility, Firmware Tab

Firmware Field Definitions

Firmware Area

• 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 the SLI code into its proper 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.

• Kernel Version - The version of the firmware responsible for starting the driver.

Firmware Tab Buttons

• Enable/Disable - Click to enable or disable the boot code.

Solaris SFS Driver User Manual Page 52

• Update Firmware - Click to this button to display the HBAnyware Firmware Download dialog box. Using the HBAnyware Firmware Download dialog box, browse to the file you wish to download and download the file. See the “Update Firmware” topic on page 55 for more information.

Viewing Target Mapping

The Target Mapping tab in the HBAnyware utility enables you to view current target mapping and to set up persistent binding. You can also set up persistent binding using lputil.

To view target mapping:

1. Start the HBAnyware utility.

2. Select Host or Fabric sort.

3. Select an HBA in the discovery-tree.

4. Select the Target Mapping tab.

Figure 16: HBAnyware Utility, Target Mapping Tab

Target Mapping Field Definitions

Current Settings Area

• Active Bind Type -N/A

• Automapping - N/A

Current Mappings Table

• This table lists all currently mapped targets for the selected HBA.

Persistent Binding Configuration Table

• This table lists persistent binding information for the selected HBA.

Solaris SFS Driver User Manual Page 53

Display Mode Radio Buttons

•Show WWPN

• Show WWNN

• Show D_ID

Target Mapping Buttons

• Change Settings - Click to change the Bind Type, the mode used to persistently bind target mappings. The Mapped Target Settings window is displayed. Select the Bind Type (WWPN, WWNN, or D_ID) or set Automapping to Enabled to Disabled.

• Add Binding - Click to add a persistent binding.

• Bind New Target - Click to add a target that does not appear in the Persistent Binding table.

• Remove - Click to remove the selected binding.

• Remove All Bindings - Click to remove all persistent bindings that are currently defined for the selected HBA.

• PCI Configuration Parameters - Parameters from the PCI configuration space on the HBA. Information includes vendor ID, device ID, base addresses, ROM address, header type, subclass and base class.

• Adapter Revision Levels - Firmware revision levels, including kernel and overlay version information.

• Wakeup Parameters - BIOS status and version, as well as SLI (service level interface).

• IEEE Address - The HBA board address.

• Loop Map - If you are using arbitrated loop topology, this option shows information about your connected devices, such as AL_PA and D_ID.

• Status and Counters - Byte, frame, sequence and busy counts.

• Link Status - Tracks activities such as link failure, loss of sync, and elastic overlay.

• Configuration Parameters - D_ID topology, and time-out values for link failures and loss of sync.

Resetting HBAs

The HBAnyware utility allows you to reset remote and local HBAs.

Caution: Do not reset an HBA while copying or writing files. This could

result in data loss or corruption.

To reset the HBA using the HBAnyware utility:

1. Start the HBAnyware utility.

2. In the discovery-tree, select the HBA you want to reset.

3. Do one of the following:

• From the menu bar, click Adapter, and then click Reset HBA.

• Click the Reset HBA button.

Solaris SFS Driver User Manual Page 54

4. The following warning screen appears:

Figure 17: HBAnyware Utility, Reset Warning Screen

5. Click Yes. The HBA resets.

The reset may require several seconds to complete. While the HBA is resetting, the status bar shows “Reset in progress.” When the reset is finished, the status bar shows “Ready”.

Updating Firmware

The HBAnyware utility allows you to update firmware on remote and local HBAs.

Prerequisites

• The Solaris SFS driver is installed properly.

• The HBAnyware utility is installed properly.

• The firmware file has been downloaded from the Emulex Web site and extracted.

Note: The HBAnyware utility will update firmware on all HBAs including Sun-branded

HBAs, but the Solaris SFS driver will immediately perform a firmware check and download afterwards on the Sun-branded HBAs only, cancelling the HBAnywaregenerated update for these Sun-branded HBAs. See the Sun Web site or contact the OEM’s customer service department or technical support department for the firmware files.

Procedure

To update firmware using the HBAnyware utility:

1. Start the HBAnyware utility.

2. In the discovery-tree, select the HBA onto which you want to update firmware.

Solaris SFS Driver User Manual Page 55

3. Select the Firmware tab.

Figure 18: HBAnyware Utility, Firmware Tab

4. Click Update Firmware. The Firmware Download dialog box appears.

Figure 19: HBAnyware Utility, Firmware Download Dialog Box

Solaris SFS Driver User Manual Page 56

5. Click Browse. The Firmware File Selection dialog box appears.

Figure 20: HBAnyware Utility, Firmware File Selection Dialog Box

6. Navigate to the extracted firmware file you wish to download. Select the file and click OK. A status bar shows the progress of the download and indicates when the download is complete.

7. Click Start Download.

If you are updating the firmware on a dual-channel HBA, repeat steps 2 through 7 to update the firmware on the second port or see

Updating Firmware (Batch Mode) on page 58.

Solaris SFS Driver User Manual Page 57

Updating Firmware (Batch Mode)

Loading firmware in batch mode differs from its non-batch counterpart in that it enables you to install firmware on multiple HBAs in a single step. Batch firmware loading is restricted to a single firmware file and to all accessible HBAs for which that file is compatible.

Note: Stop other HBAnyware utility functions while batch loading is in progress.

Prerequisites

• The firmware file has been downloaded from the Emulex Web site and extracted to the Emulex Repository folder (RMRepository). This folder is in /usr/sbin/HBAnyware/RMRepository.

Procedure

To batch load firmware using the HBAnyware utility:

1. Start the HBAnyware utility.

2. From the menu bar, select Batch and click Download Firmware.

Note: You do not need to select a particular tree element for this operation.

3. When the Batch Firmware File dialog box appears, browse to locate and select the firmware file to download. Click Open.

Figure 21: HBAnyware Utility, Batch Firmware Download Dialog Box

4. A tree-view appears showing all HBAs and their corresponding hosts for which the selected firmware file is compatible.

5. Check boxes next to the host and HBA entries are used to select or deselect an entry. Checking an HBA selects or removes that HBA; checking a host removes or selects all eligible HBAs for that host.

Solaris SFS Driver User Manual Page 58

6. When selection/deselection is complete, click Start Download.

7. Once downloading begins, the tree-view displays the progress. As firmware for a selected HBA is being downloaded, it appears orange in the tree-view. Once successful downloading is complete, the entry changes to green. If the download failed, the entry is changed to red.

Figure 22: HBAnyware Utility, Firmware Download Dialog Box with Completed Download

8. When downloading is complete, you can click Print Log to get a hard copy of the activity log.

9. Click Close to exit the batch procedure.

Enabling or Disabling the BIOS

Enabling the BIOS is a two-step process:

1. Enable the system BIOS (x86 BootBIOS, FCode or EFIBoot) to read the Emulex boot code on the HBA (using the HBAnyware utility).

2. Enable the HBA to boot from SAN (using the BIOS utility).see the documentation that accompanies the boot code for more information.

Prerequisites

• The Solaris SFS driver is installed properly.

Procedure

To enable or disable the HBA BIOS:

1. Start the HBAnyware utility.

2. In the discovery-tree, select the HBA whose BIOS you wish to enable/disable.

Solaris SFS Driver User Manual Page 59

3. Select the Firmware tab.

Figure 23: HBAnyware Utility, Firmware Tab with BIOS Disabled

4. To enable or disable the BIOS, click Enable. The button title changes from Enable to Disable.

If you are updating x86 BootBIOS, you must also enable the HBA to boot from SAN using the BIOS utility; see the documentation that accompanies the boot code for more information.

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.

For example, if you select a host in the discovery-tree, you can globally change the parameters for all HBAs in that host. If you select an HBA in the discovery-tree, you can change the lpfc_use_adisc, lpfc_log_verbose and the lpfc_nodev_tmo parameters for only that HBA.

For each parameter, the Driver Parameters tab and Host Driver Parameters tab shows the current value, the range of acceptable values, the default value, and whether the parameter is dynamic (a dynamic parameter allows the change to take effect without restarting the HBA or rebooting the system). You can make parameter changes persistent after a reboot of the system. You can also restore parameters to their default settings.

You can also 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 the parameters for that HBA. After you create the .dpv file, the HBAnyware utility enables you to apply the .dpv file parameters to multiple HBAs in the system, thereby simplifying multiple HBA configuration.

See

Creating the Batch Mode Driver Parameters File on page 64 for more information.

Note: The HBAnyware utility enables you to make dynamic parameter changes with any

version of Solaris. However, changes made by editing the lpfc.conf file and issuing an update_drv command are only dynamic for Solaris 9 and later.

Solaris SFS Driver User Manual Page 60

Setting Driver Parameters for an HBA

To change the driver parameters for an HBA:

1. Start the HBAnyware utility.

2. 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.

3. In the discovery-tree, select the HBA whose parameters you wish to change.

4. Select the Driver Parameters tab (see Figure 24). The parameter values for the selected HBA are displayed.

Figure 24: HBAnyware Utility, HBA Selected - Driver Parameters Tab

5. 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 dialog box.

6. 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). You may enter a new hexadecimal value without the "0x". For example, if you enter ff10, this value is interpreted and displayed as "0xff10".

7. If you want the change to be temporary (causing the parameter to revert to its last permanent setting when the system is rebooted), check the "Make change temporary" box. This option is available only for dynamic parameters.

8. If you are making changes to multiple parameters, and you want all the changes to be temporary, check the "Make all changes temporary" box. This setting overrides the setting of the "Make change temporary" box. Only dynamic parameters can be made temporary.

9. Click Apply.

Solaris SFS Driver User Manual Page 61

Restoring All Parameters to Their Earlier Values

If you changed parameters, but did not click Apply and you want to restore the parameters to their last saved values, click Restore.

Resetting All Default Values

If you want to reset all parameter values to their default (factory) values, click Defaults.

Setting Driver Parameters for a Host

To change the driver parameters for HBAs installed in a host:

1. Start the HBAnyware utility.

2. 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.

3. In the discovery-tree, click the host whose HBA driver parameters you wish to change.

4. Click the Host Driver Parameters tab. If there are HBAs with different driver types installed, the installed Driver Types menu shows a list of all driver types and driver versions that are installed on the HBAs in the host. Select the driver whose parameters you wish to change. This menu does not appear if all the HBAs are using the same driver.

5. In the Host Driver Parameters tab, click the parameter that you want to change. A description of the parameter appears on the right side of the dialog box.

Figure 25: HBAnyware Utility, Host Selected - Driver Parameters Tab

6. Enter a new value in the Value field. You must enter values 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).

Solaris SFS Driver User Manual Page 62

9. Click Apply.

Restoring All Parameters to Their Earlier Values

If you changed parameters, but not click Apply and you want to restore the parameters to their last saved values, click Restore.

Resetting All Default Values

If you want to reset all parameter values to their default (factory) values, click Defaults.

Solaris SFS Driver User Manual Page 63

Creating the 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 the parameters for that HBA. After you create the .dpv file, the HBAnyware utility enables you to apply the .dpv file parameters to multiple HBAs in the system, thereby simplifying multiple HBA configuration.

To create the .dpv file:

1. Start the HBAnyware utility.

2. Select the HBA whose parameters you want to apply to other HBAs from the discovery-tree.

3. Select the Driver Parameters tab. Set driver parameters (see Figure 24 on page 61).

4. After you define the parameters for the selected HBA, click Save Settings. The Select Driver Parameter File dialog box appears. Use the dialog box to select where to save the file or to rename the file. Click Save. The Save Driver Parameters dialog box appears.

Figure 26: HBAnyware Utility, Save Driver Parameters Dialog Box

5. 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.

6. A list of the saved parameters and their current values show in the Saved Parameters box.

7. Click Save.

Assigning Batch Mode Parameters to HBAs

After you create the batch mode parameters (.dpv) file, you can assign its parameters to multiple HBAs. Assigning batch mode parameters make it easy to configure multiple HBAs. See

Driver Parameters File

To assign batch mode parameters to HBAs:

1. Start the HBAnyware utility.

2. From the HBAnyware utility menu, click Batch and select Update Driver Parameters. (You do not need to select any discovery-tree elements at this time.) The Select Driver Parameter File dialog box appears.

on page 64 to learn how to create the .dpv file.

Creating the Batch Mode

Solaris SFS Driver User Manual Page 64

3. Select the file whose parameters you wish to apply and click Open. The Batch Driver Parameter Update dialog box shows all the batch file compatible HBAs with a check mark beside them.

Figure 27: HBAnyware Utility, Batch Driver Parameters Update Dialog Box

4. Click Start Updates. The HBAnyware utility Batch Driver Update dialog box shows the current status of the update. When the update completes, a final summary shows the number of HBAs that were successfully processed, and the number of HBAs for which one or more parameter updates failed.

If you wish, click Print Log to print a report of the update.

Setting Up Persistent Binding

When you create a persistent binding, the HBAnyware utility tries to make that binding dynamic. However, the binding must meet all of the following criteria to be dynamic:

• The SCSI ID (target/bus combination) specified in the binding request must not be mapped to another target. For example, the SCSI ID must not already appear in the 'Current Mappings' table under 'SCSI ID'. If the SCSI ID is already in use, then the binding cannot be made dynamic, and a reboot is required.

• The target (WWPN, WWNN or DID) specified in the binding request must not be mapped to a SCSI ID. If the desired target is already mapped, then a reboot is required.

• The 'Bind Type Selection' (WWPN, WWNN or DID) specified in the binding request must match the currently active bind type shown under “Current Settings” section of the Target Mapping tab. If they do not match, then the binding cannot be made active.

To set up persistent binding using the HBAnyware utility:

1. Start the HBAnyware utility.

2. In the directory tree, click the HBA for which you want to set up persistent binding.

Solaris SFS Driver User Manual Page 65

3. Click the Target Mapping tab. All targets are displayed.

Figure 28: HBAnyware Utility, Target Mapping Tab

4. The information for each currently defined mapping includes the world wide port name (WWPN), world wide node name (WWNN), device ID (D_ID), SCSI ID, or Bind Type. The type can be either 'PB', indicating that the mapping was the result of a persistent binding, or 'Auto', indicating that the target was automapped. In the Display Mode section, choose the display mode you want to use.

5. If you want to change the Active Bind Type (the mode used to persistently bind target mappings) or Automapping setting, click Change Settings. Select the Bind Type (WWPN, WWNN or D_ID), and set Automapping to Enabled or Disabled.

Note: All mapped targets, whether automapped or resulting from a persistent binding

configuration, will have entries in the “Current Mappings” table on the Target Mapping dialog box.

If the binding that you defined has been successfully activated, you will see the following message:

“The new binding has been created and is currently active.”

If, however, the binding was successfully created, but could not be made active, you will see the following message:

“The new binding has been created. Note that this binding will not become active until after you have rebooted the system.” Generally, you should ensure that the bind type in the Current Settings section of the Target Mapping dialog box is the same as the type of binding selected in the Persistent Binding Configuration section of the dialog box.

Solaris SFS Driver User Manual Page 66

To add a persistent binding:

1. In the Targets Table, click the target that you want to bind.

2. Click Add Binding. The Add Persistent Binding dialog box is displayed.

Figure 29: HBAnyware Utility, Add Persistent Binding Dialog Box

3. Select the Bind Type that you want to use (WWPN, WWNN or D_ID).

4. Select the Bus ID and Target ID that you want to bind, and click OK.

Note: All mapped targets, whether automapped or resulting from a persistent binding

configuration, will have entries in the “Current Mappings” table on the Target Mapping dialog box.

If the binding that you defined has been successfully activated, you will see the following message:

“The new binding has been created and is currently active.”

If, however, the binding was successfully created, but could not be made active, you will see the following message:

Solaris SFS Driver User Manual Page 67

To bind a target that does not appear in the Persistent Binding Table:

1. Click Bind New Target. The Bind New Target dialog box is displayed.

Figure 30: HBAnyware Utility, Bind New Target Dialog Box

2. Click the type of binding you want to use, and type the WWPN, WWNN or D_ID you want to bind to the target.

3. Select the Bus ID and Target ID that you want to bind, and click OK.

Note: A target will not appear on the target list if automapping has been disabled and the

target is not already persistently bound.

Adding New Targets Using sd.conf for Solaris 8, 9 and 10

You can perform on-the-fly configuration changes, without rebooting, using the HBAnyware utility. For Solaris 8, you must first add the new targets to the sd.conf file.

To add new targets using sd.conf (Solaris 8):

1. Edit the Solaris SCSI configuration file (sd.conf):

#vi /kernel/drv/sd.conf . . . name="sd" parent="lpfc" target=17 lun=1; name="sd" parent="lpfc" target=18 lun=10; name="sd" parent="lpfc" target=19 lun=15; . . .

2. Save the file and exit vi.

Changing Parameters or Bindings for Solaris 8, 9 and 10

To change parameters or bindings in Solaris 9 and 10, edit the sd.conf file as shown above and force a reread of the file with the update_drv -f sd command.

To change parameters or bindings in Solaris 8:

1. Stop all I/O on the device.

2. Unconfigure all ports with open instances to the driver.

3. Unload the driver using the modunload command. (See "Loading or Unloading the Driver without Rebooting" on page 69 for more information.)

4. Reload the driver using the modload command. (See "Loading or Unloading the Driver without Rebooting" on page 69 for more information.)

Solaris SFS Driver User Manual Page 68

Setting Up Target/LUN Blocking Using sd.conf

The class keyword ("scsi") ensures that Solaris specifically probes all adapters controlled by all driver that register themselves as class="scsi". The parent keyword ("lpfc") ensures that Solaris specifically probes all adapters controlled by the lpfc driver for the specified targets and LUNS. The class and parent keywords cause the SCSI layer to probe multiple adapters, even multiple adapters across multiple drivers. This method limits the SCSI layer probing of targets and LUNs on an adapter-by-adapter basis. This gives you control over which targets and LUNs are seen by each initiator (target/LUN blocking).

To set up target/LUN blocking using sd.conf:

1. Reboot the system with the adapter installed.

2. Check the output of dmesg(1M). This message displays in the following format:

NOTICE: Device Path for interface lpfcX:/pci@1f.0/pci@1/fibre-channel@3

Note: Where lpfcX is the interface for a specific adapter and /pci@1f.0/pci@1/fibre-

channel@3 is the device path for the specific adapter.

3. Add entries to the sd.conf file in the following format:

name="sd" parent="lpfc" target=16 lun=0 hba="lpfcX";

Note: This entry does not cancel the effect of any other parent="lpfc" or class="scsi" entries

for target=16 lun=0. If you want the SCSI layer to probe only for target=16 lun=0 on device lpfcX, the parent="lpfc" or class="scsi" entries for target=16 lun=0 need to be deleted. You can cause system problems if certain class="scsi" entries are deleted. These entries are used by the SCSI adapter, so if there is a SCSI boot disk at target=0 lun=0 whose probe entry has been deleted, the system won't boot. Similarly, if any SCSI target's probe entry is deleted, that device won't operate. To guarantee that the Fibre Channel and SCSI probing won't conflict, use persistent binding to assign FC devices target numbers greater then 15. Persistent binding can be used to perform target blocking but not LUN blocking.

No-Reboot Firmware Updates

Emulex is the only vendor providing dynamic adapter firmware updates during operation without stopping I/O traffic. You can dynamically update host bus adapter firmware using the HBAnyware utility. Refer to

Updating Firmware on page 55 for more information.

Loading or Unloading the Driver Without Rebooting

Note: When the Solaris operating system is installed on a Fibre Channel drive, you must

reboot the system because you cannot quiesce all I/O on the OS drive.

Systems must support dynamic reconfiguration.

To load the driver without rebooting:

1. Load the driver using the modload command.

2. Use the cfgadm command to configure Emulex HBAs.

3. Restart I/O.

To unload the driver without rebooting:

1. Stop all I/O on the device.

2. Use the cfgadm command to disconnect Emulex HBAs.

3. Unload the driver using the modunload command.

Solaris SFS Driver User Manual Page 69

Performing Diagnostic Tests

Use the Diagnostics tab to do the following:

• Run these tests on Emulex HBA's installed in the system:

• PCI Loopback (see page 74)

• Internal Loopback (see page 74)

• External Loopback (see page 74)

• Power-On Self Test (POST) (see page 71)

• Echo (End-to-End) (see page 75)

• Quick Test (see page 70)

• Perform a diagnostic dump (see page 72).

• View PCI registers and wakeup parameter (see page 72).

• Control HBA beaconing (see page 71).

Figure 31: HBAnyware Utility, Diagnostics Tab

All functions are supported locally and remotely, except for the dump feature which is only supported locally.

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. Start the HBAnyware utility.

2. From the discovery-tree, select the HBA on which you wish to run the Quick Test.

Solaris SFS Driver User Manual Page 70

3. Select the Diagnostics tab and click Quick Test. The following message appears:

Figure 32: HBAnyware Utility, Quick Test Message

4. Click OK to run the test. The Quick Diagnostics Test message shows the PCI Loopback and Internal Loopback test results.

Running a POST Test

The POST (Power On Self Test) is a firmware test normally performed on an HBA after a reset or restart. The POST does not require any configuration to run.

To run the POST Test:

1. Start the HBAnyware utility.

2. From the discovery-tree, select the HBA on which you wish to run the POST Test.

3. Select the Diagnostics tab and click Power-on Self Test (POST). A warning dialog box appears.

Figure 33: HBAnyware Utility, POST Test Warning Window

4. Click OK. A POST Test window shows POST test information.

Using Beaconing

The beaconing feature enables you to force a specific HBA’s LEDs to blink in a particular sequence. The blinking pattern acts as a beacon, making it easier to locate a specific HBA among racks of other HBAs.

When you enable beaconing, the two LEDs blink rapidly in unison for 24 seconds, after which the LEDs report the HBA health status for 8 seconds. When the 8 seconds are up, the HBA returns to beaconing mode. This cycle repeats indefinitely until you disable this feature or you reset the HBA.

Note: The beaconing buttons are disabled if the selected HBA does not support

beaconing.

To enable or disable beaconing:

1. Start the HBAnyware utility.

2. From the discovery-tree, select the HBA whose LEDs you wish to set.

3. Select the Diagnostics tab and click Beacon On or Beacon Off.

Solaris SFS Driver User Manual Page 71

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.

Note: The Diagnostic Dump feature is only supported for local HBAs. If a remote

HBA is selected from the tree-view, the Initiate Diagnostic Dump is disabled.

To start a diagnostic dump:

1. Start the HBAnyware utility.

2. From the discovery-tree, select a local HBA whose diagnostic information you wish to dump.

3. Select the Diagnostics tab and click Diagnostic Dump. The Diagnostic Dump dialog box appears. You can specify how many files you want to save using the Files Retained counter. Click Delete Existing Dump Files if you wish to remove existing dump files from your system.

Figure 34: HBAnyware Utility, Diagnostic Dump Dialog Box

4. Click Start Dump.

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. The information is read-only and is depicted below:

Figure 35: HBAnyware Utility, PCI Registers and Wakeup Parameters Area of the Diagnostics Tab

Solaris SFS Driver User Manual Page 72

Running Advanced Diagnostic Tests

The Advanced Diagnostics feature gives you greater control than the Quick Test over the type of diagnostics tests that run. Through Advanced Diagnostics, you can specify which tests to run, the number of cycles to run, and what to do in the event of a test failure.

To run advanced diagnostics tests:

1. Start the HBAnyware utility.

2. Click Advanced Diagnostics Test on the Diagnostics tab to view the Advanced Diagnostics dialog box.

You can run four types of tests:

• PCI Loopback

• Internal Loopback

• External Loopback

• End-to-End (ECHO)

Note: You cannot run the External Loopback test and ECHO test concurrently. If you select

External Loopback the ECHO test section is disabled and vice versa.

All test results, plus the status of running tests, are time stamped and appear in the log at bottom of the dialog box.

Figure 36: HBAnyware Utility, Advanced Diagnostics Dialog Box

Solaris SFS Driver User Manual Page 73

Running Loopback Tests

To run a loopback test, use the "Loopback Test" section of the Advanced Diagnostics dialog box.

You can run the following loopback test combinations using the appropriate check boxes:

• PCI Loopback Test - A firmware controlled diagnostic test in which a random data pattern is routed through the PCI bus without being sent to an adapter link port. The returned data is subsequently validated for integrity.

• Internal Loopback Test - A diagnostic test in which a random data pattern is sent down to an adapter link port, then is immediately returned without actually going out on the port. The returned data is subsequently validated for integrity.

• External Loopback Test - A diagnostic test in which a random data pattern is sent down to an adapter link port. The data goes out the port and immediately returns via a loopback connector.

The returned data is subsequently validated for integrity.

Note: You cannot run the External Loopback test and ECHO test concurrently. If you select

External Loopback the ECHO test section is disabled and vice versa.

You can specify the number of test cycles by clicking one of the cycle counts values in the "Test Cycles" section of the dialog box or enter a custom cycle count if you wish. The Test Status section displays how many cycles of each test ran. The "Error Action" section of the dialog box enables you to define what should be done in the event of a test failure.

There are two error action options:

• Stop Test - The error will be logged and the test aborted. No further tests will run.

• Ignore - Log the error and proceed with the next test cycle.

To run loopback tests:

1. Start the HBAnyware utility.

2. From the discovery-tree, select the HBA on which you wish to run the Loopback Test.

3. Select the Diagnostics tab and click Advanced Diagnostics Tests. From the "Loopback Test" section of the dialog box, choose the type of Loopback test you wish to run and define the

loopback test parameters.

Note: You must insert a loopback plug in the selected HBA before running an

External Loopback test.

4. Click Start. The following warning appears:

Figure 37: HBAnyware Utility, Advanced Diagnostic Tests Warning

Solaris SFS Driver User Manual Page 74

5. Click OK. If you choose to run an External Loopback test the following window appears:

Figure 38: HBAnyware Utility, Advanced Diagnostic Tests Warning for External Loopback

6. Click OK. The progress bar indicates that the test is running.

Periodic test feedback, consisting of the current loopback test/cycle plus the completion status of each type of test, is displayed in the "Test Log" section of the dialog box. Click Clear to erase the contents of the log display or click Save to File to save the log file.

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. Start the HBAnyware utility.

2. From the discovery-tree, select the HBA from which you wish to initiate the End-to-End (ECHO) Tes t.

3. Select the Diagnostics tab. Click Advanced Diagnostics Test.

4. Check Echo Test. Enter the World Wide Port Name (WWPN) for the target.

Click Select From List if you do not know the actual WWPN of the test target. The Select Echo Test Target dialog box appears. Select the port you wish to test from the tree-view and click

Select.

Solaris SFS Driver User Manual Page 75

All relevant information for the selected port is automatically added to the Target Identifier section of the Diagnostics dialog box.

Figure 39: HBAnyware Utility, Select Echo Test Target Window

5. Click Start. The following warning window appears:

Figure 40: HBAnyware Utility, Advanced Diagnostic Tests Warning

6. 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. Over time, the data accumulates to form a chronological history of the diagnostics performed on the HBA.

After writing an entry into the log, you are prompted to clear the display.

The default name of the saved file is DiagTestLog.log and by default is located in: /usr/sbin/hbanyware/Dump

Solaris SFS Driver User Manual Page 76

An example of a saved log file appears below:

Figure 41: DiagTestLog Window

To save the log file:

1. After running a test from the Diagnostic Test Setup dialog box, Click Save to File. The Select Diagnostic Log file Name dialog box appears. The default name of a saved file is DiagTestLog.log.

2. Browse to the desired directory, change the log file name if you wish and click Save.

Out-of-Band SAN Management

Out-of-Band (OOB) remote SAN management is achieved by sending the remote management requests over a LAN using the Ethernet TCP/IP protocol to remote hosts.

In-band management is achieved by sending the remote management requests over a SAN to remote hosts.

The principle differences between in-band and out-of-band SAN Management are:

• A management host with an HBA installed does not need to connect to a fabric to manage other hosts.

• An OOB management host can manage all of the HBAs in a remote host, not just the ones connected to the same fabric. In-band can only manage HBAs connected to the same fabric.

• You can manage many more hosts since OOB is not constrained by the boundaries of a fabric or zoning.

• True board status (e.g. link down) is available since the in-band path is not necessary to send a status request to the remote host.

• HBA security in an OOB environment is much more important since many more hosts are available for management and OOB access is not affected by fabrics or zoning.

• Discovery of hosts in an OOB environment is much more difficult than in-band discovery.

Solaris SFS Driver User Manual Page 77

Adding a Single Host

The HBAnyware utility enables you to specify a single OOB host to manage. If the host is successfully discovered as a manageable host, it is added to the static list of hosts and if it has not been discovered in-band, the host and its HBAs are added to the discovery tree.

To add a single host:

1. Start the HBAnyware utility.

2. From the Discovery menu, select Out-of-Band/Add Host. The Add Remote Host dialog box appears.

Figure 42: HBAnyware Utility, Add Remote Host Dialog Box

3. Enter the name or the IP address of the host to be added. Entering the IP address is the best way to add a new host.

Note: Using the IP address to identify the host avoids name resolution issues.

4. Click OK. You will receive a message indicating whether or not the new host was successfully added.

Solaris SFS Driver User Manual Page 78

Adding a Range of Hosts

You can find the OOB manageable hosts by searching a range of IP addresses using the Add Range of IP Hosts dialog box.

Figure 43: HBAnyware Utility, Add Remote Hosts Window

The Add Range of IP Hosts dialog box enables you to build the initial list of OOB manageable hosts.

To add a range of hosts:

1. Start the HBAnyware utility.

2. From the Discovery menu, select Out-of-Band/Add Range of Hosts. The Add Range of IP Hosts dialog box appears.

3. 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.

4. Click Start Discovery. HBAnyware checks each address in the range to determine if the host is available and remotely manageable. The number of addresses discovered (of manageable hosts) is periodically updated on the dialog box.

Note: The number of addresses does not correspond directly to the number of hosts added to the discovery-tree.

For example, some of the addresses discovered may be for hosts that have already been discovered in-band. However, new HBAs may be discovered on those hosts that were not discovered in-band.

Also, a host may have more than one HBA installed and both IP addresses for that host are discovered during the search, but only one host will possibly be added to the discovery-tree.

5. When the search is complete, click Cancel.

Solaris SFS Driver User Manual Page 79

6. A dialog box appears asking to save the IP ranges you searched. Click Yes to save the address ranges. If you save the address ranges, these address ranges will appear the next time you use the Add Range of IP Hosts dialog box. Click No if you do not want to save the address ranges.

The Save Ranges to A File button saves the specified range(s) to a file so that the same ranges can be automatically invoked when the HBAnyware utility is started again.

Removing Hosts

Periodically you may want to remove hosts that are no longer part of the network. You may want to remove a host when it is removed from the network or to detect hosts that are no longer being discovered. Removing hosts that can no longer be discovered improves the operation of the discovery server.

To remove hosts:

1. Start the HBAnyware utility.

2. From the Discovery menu, select Out-of-Band/Remove Host. The Remove Remote Hosts dialog box shows a list of discovered OOB hosts. Any host not currently discovered appears in red. Click Show Undiscovered Hosts Only to only display currently undiscovered hosts.

3. From the Remove Remote Hosts dialog box, select the hosts you wish to remove. You can select all the displayed hosts by clicking Select All.

4. Click OK to remove the selected hosts.

HBAnyware Security

Introduction

Initially, only the HBAnyware software package has been installed on all of the systems of a Fibre Channel network. 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. Figure 44 illustrates a system with no security.

Figure 44: Initial State - No Security

The HBAnyware security software consists of an application programming interface (API) containing a set of security management functions and a user interface (UI). Together these allow you to administer a security system configuration (SSC). HBAnyware security is system-based, not user-based.

SSC provides two main security features:

1. Prevents remote HBA management from systems that you do not want to have this capability.

2. Prevents an accidental operation (such as firmware download) on a remote HBA. In this case, you do not want to have access to HBAs in systems you are not responsible for maintaining.

SSC has several components that enable you to setup your environment in a secure way:

• Security association (SA) - A record consisting of a key and an access control record. Related components are the SA table, SA File and SA Identifier (SA_ID).

• SA table - a group of 256 Security Associations and a flag to enable/disable security.

• SA file - A locally encrypted file on each system that is part of the HBAnyware security

environment that stores the SA table.

Solaris SFS Driver User Manual Page 80

• SA_ID - An index (into the SA table) that is passed in the CT command descriptor to indicate

which Access Control Record (containing the key is being used to encrypt/decrypt the command data) to use in the SA table.

• Master Security Client (MSC) - Upon first discovery, an MSC will configure the first ACG, granting itself client access and all of the systems it wants to manage server access. Once security is enabled on a server system, that server cannot grant itself client access. Only an MSC can grant this access to a server by creating an Access Sub Group (ASG) and making a server the client to the ASG.

• ACG - An ACG consists of a client system and the servers it is allowed access to manage. An MSC creates an initial ACG. All additional ACGs are defined out of this initial ACG.

• ASG - A sub-group of systems created from the systems of a client’s ACG. One system is the designated client and the others are made servers. The updates to the SA files are sent from the client to the appropriate systems to create an ASG. The new client system not only has access to remotely manage the servers in its new ACG, but and can also create additional ASGs from its own systems in its ACG. This gives the ASG a hierarchical nature:

• Backup Master - The system designated by an MSC as the backup MSC. It can take over the MSC if the MSC becomes permanently disabled and can no longer be the MSC.

Solaris SFS Driver User Manual Page 81

Starting the Security Configurator for the First Time: Creating the First ACG, Designating the MSC and Selecting Systems in the FC Network

Prerequisites

• The Solaris SFS Driver is installed.

• The HBAnyware and lputil utilities are installed.

• The HBAnyware Security Configurator is installed.

• All of the systems that are part of, or will be part of, the security configuration are online on the Fibre Channel network. This enables the systems to receive updates and changes made to the security configuration.

Caution: Any system that is part of the security installation, but offline when the Security

Configurator starts for the first time will not be available for security configuration changes even if it is brought online while the Configurator is running. Any system that is already part of the security installation might not run with the proper security attributes if updates to the security configuration are made while it is offline.

Procedure

Start the HBAnyware Security Configurator for the first time in an unsecure environment. The computer from which you run the Security Configurator will become an MSC.

1. Run the /usr/sbin/hbanyware/ssc script. Type:

/usr/sbin/hbanyware/ssc

The” Unsecure System” message is displayed.:

Figure 45: Security Configurator, “Unsecure System” Message

2. Click OK on the Unsecure System message to have the systems with HBAs discovered. The Discovery Window is displayed:

Figure 46: Discovery Window

Solaris SFS Driver User Manual Page 82

All of the available servers are discovered and available to become part of the system Access Control Group (ACG).

3. Select the unsecured servers to be added to the ACG from the Available Servers list.

Figure 47: Security Configurator, Access Group Control Tab with Call Outs

4. Click the left arrow to add the servers to the Access Control Group Servers list.

Note: There can be only one MSC per access control group (ACG). There can be multiple

MSCs (thus multiple ACGs) in a SAN, however the set of ACG servers controlled by each MSC must not overlap (i.e. ACG servers controlled by one MSC cannot be added to another MSC's ACG). For example, if you designate a host in a SAN as an MSC, and assign some, but not all, of the servers in the SAN to that MSC (i.e. move some of the hosts in the 'Available Servers' list on the 'Access Control Group' tab to the 'Access Control Group Servers' list), then any of the servers that still remain in the 'Available Servers' list can be designated as a separate MSC. The servers that appear in the 'Available Servers' list have yet to be claimed by an MSC and are thus in an unsecured state. Any leftover servers that still remain in the 'Available Servers' list can subsequently be added to the ASG controlled by the new MSC.

5. Click OK or Apply. The security configuration is updated on all of the selected servers as well as on the initial system. The following process sets up an MSC (see Figure 48).

Solaris SFS Driver User Manual Page 83

a. The SSC utility runs.

b. SA_ID is selected.

c. SA files are created for systems 2 through 5.

d. SA files are sent to each system and system 1 becomes an ACG and an MSC, the only system which can run the HBAnyware client to remotely access all other system.

Figure 48: Systems 2 through 6 can access and control their local HBAs

Access Control Groups

Introduction

The Access Control Group tab shows the systems that are part of a client's Access Control Group (ACG) and, from an MSC, allows you to select the systems that belong to the ACG.

Access Control Group Tab on the MSC

On an 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 are updated to secure them and bring them into the MSC's ACG.

Solaris SFS Driver User Manual Page 84

When you select systems in the ACG and move them to the Available Servers list, the security configuration for those systems is updated to make them unsecure. After you have configured security from the MSC for the first time, the Access Control Group tab looks similar to the following:

Figure 49: Security Configurator, Access Control Group Tab on a non-MSC system

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 50: Security Configurator, Access Control Group Tab after MSC security is configured

ACG Icons

Depending on the configured security topology, a system can be a server in one or more ACGs. It can also be a client to an ACG. The following icons indicate the state of each of the systems in the Access Control Group Servers list.

Solaris SFS Driver User Manual Page 85

The system is a secure server in the ACG. It does not belong to an Access Sub-Group (ASG). You can remove this system from the ACG.

The system is a secure server in the ACG and belongs to one or more ASGs. You can remove this system from the ACG.

The system is a secure server in the ACG and a client to an ASG. You cannot remove this system from the ACG until you remove it as a client from the ASG.

The system is a secure server in the ACG, a secure server in one or more ASGs and a client to an ASG You cannot remove this system from the ACG until you remove it as a client from the ASGs.

The system is a Backup Master. You cannot remove this system from the ACG until you remove it as a Backup Master.

Adding a Server to the ACG

After you create the initial Access Control Group (ACG) on the Master Security Client (MSC), you may want to add unsecured servers to the ACG.

To add servers to the ACG:

1. Start the HBAnyware Security Configurator.

2. On the Access Control Group tab, from the Available Servers list, select the unsecured servers that you want to add to the ACG.

Figure 51: Security Configurator, The Access Group Control Tab with Call Outs

3. Click the left arrow to add the server to the Access Control Group Servers list.

4. Click OK or Apply.

Solaris SFS Driver User Manual Page 86

Deleting a Server from the ACG

To delete a server from the Access Control Group (ACG):

1. Start the HBAnyware Security Configurator.

2. On the Access Control Group tab, from the Access Control Group Servers list, select the secured systems that you want to delete from the ACG.

Figure 52: Security Configurator, The Access Group Control Tab with Call Outs

3. Click the right arrow to remove the servers from the Access Control Group Servers list.

4. Click OK or Apply.

Solaris SFS Driver User Manual Page 87

Removing Security from all Servers in the ACG

You can remove security from all systems only from the Master Security Client (MSC). Removing the entire security topology on all of the servers in the MSC's ACG puts the servers in an unsecure state. The MSC is also put in an unsecure state; consequently, it is no longer the MSC. Any participating systems that are not online will not receive the 'remove security' configuration update, and as a result will no longer be accessible remotely.

To remove security from all servers in the ACG:

1. Start the HBAnyware Security Configurator. The Access Control Group tab is displayed.

Figure 53: Security Configurator, Access Control Group Tab

2. On the Access Control Group tab, click the Remove Security button. The following message is displayed:

Figure 54: The HBAnyware Security Configurator “Warning” Dialog Box

3. Click Yes. Security is removed from all servers in the ACG.

Solaris SFS Driver User Manual Page 88

Generating New Security Keys

You can generate new security keys only from a Master Security Client (MSC). After the new security keys are generated, they are automatically sent to all of the remote servers in the Access Control Group (ACG).

Note: All the servers that are part of the ACG must be online when this procedure is

performed so that they may receive the new keys. Any servers that do not receive the new keys will no longer be accessible remotely.

To generate new security keys for all servers in the ACG:

1. From the MSC, start the HBAnyware Security Configurator. The Access Control Group tab is displayed.

Figure 55: Security Configurator, Access Control Group Tab

2. On the Access Control Group tab, click the Generate New Keys button. A dialog box warns you that you are about to generate new security keys for all systems.

3. Click Yes. The new keys are generated and sent to all of the remote servers in the ACG.

Solaris SFS Driver User Manual Page 89

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:

1. From the Access Control Group tab on the MSC, click the Restore button.

Figure 56: Security Configurator, Access Control Group Tab

Solaris SFS Driver User Manual Page 90

Accessing a Switch

You can enable switch access only on a Master Security Client (MSC). Switch access grants the client access rights to a switch to remotely access HBAs on servers in the Access Control Group (ACG).

To enable switch access:

1. Start the HBAnyware Security Configurator.

2. From the Access Control Group tab, check Enable Switch Access.

Figure 57: Security Configurator, Access Control Group Tab

Solaris SFS Driver User Manual Page 91

Access Sub-Groups

Introduction

The Access Sub-Group tab allows you to create multiple Access Sub-Groups (ASGs) and multiple levels (tiers) in the security topology hierarchy. The hierarchy can be as many levels deep as desired. However, it is recommended the hierarchy extend no more than three levels deep, as it becomes increasingly difficult to keep track of the topology the deeper it goes. The hierarchy of ASGs is displayed in the Access Sub-Groups tab as a tree. You can create, modify and delete ASGs at each level in this tree

Figure 58: Security Configurator, Access Sub-Groups Tab with Servers

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. You cannot remove it from the ASG until you remove it as a client from the child ASG (by either deleting or editing the child ASG).

The system is a server in the ASG, a server in at least one other child ASG and a client to a child ASG. You cannot remove it from the ASG until you remove it from the child ASGs and as a client from the child ASG (by either deleting or editing the child ASG).

The system is a server in the ASG and a client to a non-child ASG. You can remove it from the ASG.

The system is a server in the ASG, a server in at least one child ASG, and a client to a nonchild ASG. You cannot remove it from the ASG until you remove it from the child ASGs.

Solaris SFS Driver User Manual Page 92

Creating an ASG

You create a new Access Sub-Group (ASG) by selecting one system from the Access Control Group (ACG) to be the client, and some or all of the other systems to be servers to this client, thus defining the new client's ACG. When the HBAnyware Security Configurator is run on the new client, the displayed ACG shows the servers that were configured in the ASG by its parent client.

To create an ASG:

1. Start the HBAnyware Security Configurator.

2. Click the Access Sub-Groups tab.

Figure 59: Security Configurator, Access Control Group Tab (new)

3. Click New. The New Access Sub-Group dialog box is displayed.

Figure 60: Security Configurator, New Access Sub-Group Window

4. 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). At each level of the security topology, each ASG name must be unique. If the name is not unique at its level, an error message informs you of this when you click OK.

• Access Sub-Group Client System: Select the system that is to be the client.

• Number of indices reserved for this Access Sub-Group: Select the number of 'indices' you want to reserve for the client system of the new ASG. This number reflects the number of subsequent 'child' ASGs that can subsequently be created on the new client's system. See the Reserved Indices topic (under Access Sub-Groups in this manual) for examples.

Solaris SFS Driver User Manual Page 93

Emulex LP1150-F4 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Installation

Introduction

Compatibility

Known Issues

Minimum Driver for Firmware Installation on LPe11000 and LPe11002 HBAs

Special Circumstances for Installing Solaris SFS Driver Version 2.12 or later

Procedure 1

Procedure 2

Installing the Solaris SFS Driver

Downloading and Installing the Driver for Solaris 8 or 9

Method 1: Using the Install_it Script (recommended)

Method 2: Using Individual Patches

Downloading and Installing the Driver for Solaris 10 (Sparc, X64 and x86)

Installing the FCA Utilities and the HBAnyware Utility

Unpacking the Utility Files

Installing the FCA Utilities

Installing or Updating the FCA Utilities Using the emlxu_install Script

Prerequisites

Procedure

Installing the HBAnyware Utility, Web Launch and Security Configurator

Known Issues

Installing the HBAnyware Utility

Prerequisites

Procedure

Installing the HBAnyware Utility with Web Launch

Prerequisites

Procedure

Installing the HBAnyware Utility Security Configurator

Prerequisites

Procedure

Installing or Updating the Utilities Package Manually

Compatibility

Prerequisites

Procedure

Removing the Utilities Using the emlxu_remove Script

Removing the Utilities Package Manually

Configuration

Introduction

Driver Parameters

Solaris SFS and lpfc Driver Parameter Cross-Reference Table

Using the HBAnyware Utility

Starting the HBAnyware Utility

Starting HBAnyware with Web Launch

Starting the HBAnyware Security Configurator

Prerequisites

Procedure

Starting the HBAnyware Utility from the Command Line

Examples of Modifications

Changing Management Mode

The HBAnyware Utility Window Element Definitions

The Menu Bar

The Toolbar

The Toolbar Buttons

Sort Toolbar Buttons

The Discovery-Tree

Discovery-Tree Icons

Property Tabs

Status Bar

Using the HBAnyware Utility Command-Line Interface

Using the CLI Client

Syntax Rules

Out-of-Band Access

CLI Client Command Reference

Version

ListHBAs

SaveConfig

HBAAttrib

PortAttrib

PortStat

ServerAttrib

Target Ma pping

Download

AllNodeInfo

DriverConfig

DriverParams

DriverParamsGlobal