HBAnyware® Utility Version 3.
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.
Introduction.............................................................................................................. 1 Known Issues .................................................................................................... 1 Installing HBAnyware Components.......................................................................... 2 Installing the HBAnyware Utility......................................................................... 2 Installing the HBAnyware Utility with Web Launch.......
Viewing and Setting Up Authentication (Windows, Solaris LPFC and Solaris SFS)................................................................................. 36 Viewing or Changing Authentication Configuration ............................. 37 Changing Your Password.................................................................... 37 Updating Firmware .......................................................................................... 38 Updating Firmware (Batch Mode)................................
Editing an ASG ......................................................................................... 93 About Offline ASGs ................................................................................... 94 Backup Masters............................................................................................... 95 Introduction ............................................................................................... 95 Backup Master Eligible Systems ..........................................
Introduction Emulex® drivers have many properties that you can modify using the HBAnyware® configuration utility. The utility is client/server based and provides 'remote' configuration capability to other host platforms running the utility. This remote configuration capability can be provided by either Fibre Channel (FC) access (host systems on the same FC Storage Area Network (SAN) or by Transmission Control Protocol/Internet Protocol (TCP/IP) access (from IP addresses of remote machines).
• If there are multiple versions of the Java Runtime Environment (JRE) installed on your Internet Explorer client, then you may see the following text in the browser's main display window when you attempt to launch the HBAnyware utility via the browser: Emulex Corporation HBAnyware Demo of HBAnyware WebStart web n.n.n.n .....
3. Unzip the file. Type: gunzip HBAnyware--.tar.gz 4. Untar the file. Type: tar -xvf HBAnyware--.tar 5. Run the pkgadd utility. Type: pkgadd -d . 6. When prompted by pkadd, choose to install HBAnyware. 7. When prompted by pkadd, answer the HBAnyware installation option questions. To install the HBAnyware utilities in Linux: Note: This procedure also installs the application helper module on your system.
Installing the HBAnyware Utility with Web Launch In addition to the driver and HBAnyware utilities, the following must be installed before you can install the Web Launch feature: • • In Windows: • Microsoft Internet Information Services (IIS) Server must be installed. See the Microsoft Web site for information on downloads and installation. • JRE must be installed. See the www.java.com Web site for information on downloads and installation.
6. You are asked if your Web server is 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 when the installation of the HBAnyware Web Launch package is complete. Once the necessary information is entered, you are notified when the installation of the HBAnyware Web Launch package is complete. The Web Launch configuration files are created and Web Launch Services automatically starts. 7.
Uninstalling the HBAnyware Security Configurator To uninstall the HBAnyware Security Configurator: In Windows: 1. Select Start>Settings>Control Panel. The Control Panel appears. Click on Add/Remove Programs and the Add or Remove Programs window appears. 2. Select Emulex HBAnyware Security Configurator>Change/Remove. Click Next. The Security Configurator is removed from the system. 3. Click Finish. Uninstallation is complete. In Solaris LPFC and Solaris SFS: 1. Log on as ‘root’.
Uninstalling HBAnyware Web Launch Only To uninstall HBAnyware Web Launch, but leave the HBAnyware utility installed: In Windows: 1. Select Start> Programs>Emulex>HBAnyware WebLaunch Uninstall. The following screen appears: Figure 1: HBAnyware Web Launch, Uninstallation dialog screen 2. HBAnyware Web Launch is removed. Press any key to continue. In Solaris LPFC, Solaris SFS and Linux: 1. Log on as ‘root’. Note: If you installed HBAnyware with Web Launch, you must uninstall it before uninstalling HBAnyware.
3. Uninstall any previously installed versions. Type: ./uninstall Using the HBAnyware Components Note: To properly view the HBAnyware utility, ensure your system meets the following display requirements: For Windows systems the display resolution must be set to 800 by 600 or better. For UNIX systems the display resolution must be set to 1024 by 768 or better. The display must run in 256-color mode or higher. HBAnyware icons use 256 colors.
• If you are running the HBAnyware Security Configurator with TCP/IP access, you must set up any TCP/IP hosts or they will not be seen by the Security Configurator. Note: When you install the HBAnyware utility security software on a system and run the HBAnyware utility Security Configurator for the first time, that system becomes the Master Security Client (MSC). For more information, see “Creating the ACG” on page 86.
The HBAnyware Utility Window Element Definitions The utility window contains five basic components: the menu bar, the toolbar, the discovery-tree, the property tabs and the status bar. Figure 2: HBAnyware Utility window Note: The element you select in the discovery-tree determines whether a menu item or toolbar icon is active. For example, if you select the local host or other system host, the Reset Adapter item on the Adapter menu is unavailable. The 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 HBAs and sorting items in the discovery-tree view. Many of the menu bar commands are also available from the toolbar. The Toolbar Many of the toolbar functions are also available from the menu bar. The toolbar is visible by default. Use the Toolbar item in the View menu to hide the toolbar. If the item is checked, the toolbar is visible.
The Discovery-Tree The discovery-tree (left pane) has icons that represent discovered network (SAN) elements (local host name, system host names and all HBAs active on each host). Targets and LUNs, when present, are also displayed. Figure 4: Discovery-tree Discovery-Tree Icons Discovery-tree icons represent the following: This icon represents the local host. This icon represents other hosts connected to the system. A green HBA icon with black descriptive text represents an online HBA.
The Target Controller LUN icon represents LUNs that are storage controllers. The Switch icon represents connections to the switch. Property Tabs The property tabs display configuration, statistical and status information for network elements. The set of available tabs is context-sensitive, depending on the type of network element or HBA currently selected in the discovery-tree. Status Bar The status bar is located near the bottom of the HBAnyware utility window.
2. Choose the management type you want. 3. Click OK. Note: The HBAnyware utility must be restarted to see the new management mode. In Solaris LPFC, Solaris SFS and Linux: 1. Run the following script: /usr/sbin/hbanyware/set_operating_mode 2. Choose the management type you want. Resetting HBAs You can reset remote and local HBAs. Caution: Do not reset your HBA while copying or writing files. This could result in data loss or corruption. To reset the HBA: 1.
Note: After adding an HBA to a running system (commonly called a hot plug), click the Discovery Refresh icon or restart the HBAnyware utility to display the new HBA in the discovery-tree. Figure 7: Discovery Information Remote SAN Management Using TCP/IP Access Protocol You can also discover HBAs on TCP/IP hosts. Remote SAN management over TCP/IP sends remote management requests on another LAN using TCP/IP access protocol to remote hosts.
1. From the Discovery menu, select TCP/IP>Add Host. The Add Remote Host dialog box appears. Figure 8: Add Remote Host dialog box 2. 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. 3. Click OK. You will receive a message indicating whether or not the new host was successfully added.
3. Click Start Discovery. The utility 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 over FC.
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 FC and TCP/IP accessed discoveries and when to remove previously discovered HBAs that are no longer being discovered. Figure 10: HBA Discovery Properties dialog box To configure discovery settings: 1. From the Menu bar, select Discovery/Modify Settings. The HBA Discovery Properties dialog box appears. 2.
Sorting HBA Information You can sort discovered HBAs by host name, fabric ID, HBA name, target name and LUN number. You can also view local or remote HBAs. By default, both local and remote HBAs are sorted by host name. To sort HBAs: 1. Switch between host name or fabric ID in one of two ways: • From the menu bar: click View, then click Sort by Host Name or Sort by Fabric ID. • From the toolbar, click one of the following buttons: Sort HBAs by Host Name (default) Sort HBAs by Fabric ID . . 2.
Viewing HBA Information Viewing Discovery Information Discovery Information contains a general summary of the discovered elements. The Host or Fabric icon, depending upon which view you select, is the root of the discovery-tree, but it does not represent a specific network element. Expanding it reveals all hosts, LUNs, targets and HBAs that are visible on the SAN. To view the discovery information: 1. Click the Host or Fabric icon at the root of the discovery-tree.
Viewing Host Information There are two tabs that show host information: the Host Information tab and the Driver Parameters tab. The Host Information tab is read-only. The Driver Parameters tab enables you to view and define HBA driver settings for a specific host. To view the Host Information and Driver Parameters tabs: 1. Do one of the following: • From the menu bar, click View, then click Sort by Host Name. • From the toolbar, click the Sort by Host Name button: . 2.
The Driver Parameters Tab The Driver Parameters tab enables you to view and edit the HBA driver settings contained in a specific host. The host driver parameters are global values and apply to all HBAs in that host unless they are overridden by parameters assigned to a specific HBA using the HBA Driver Parameters tab.
Viewing General HBA Attributes The General tab contains general attributes associated with the selected HBA. To view general attributes: 1. Select Host or Fabric sort. 2. Select an HBA in the discovery-tree. Figure 14: General tab General Field Definitions Adapter Summary Area • Model - The complete model name of the HBA. • Port WWN - The Port World Wide Name of the HBA. • Node WWN - The Node World Wide Name of the selected HBA.
• • 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.
• Discovered Ports - Counts the number of mapped and unmapped ports found during discovery by the Emulex HBA driver. The mapped ports are targets and the unmapped ports are non targets such as switches or HBAs. • Device ID - The HBA's default device ID. Port Attributes Area • 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.
Viewing Fabric Information Discovery Information contains information about the selected fabric. To view the fabric information: 1. 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: . 2. Click on a fabric address in the discovery-tree. The Discovery Information tab shows information about the selected fabric.
Viewing Target Information Target Information contains information specific to the selected storage device. To view target information: 1. Do one of the following: • From the menu bar, click View, then click Sort by Host Name. • From the toolbar, click the Sort by Host Name button: . 2. Click a target in the discovery-tree. The Target Information tab appears.
Viewing LUN Information LUN Information contains details about the selected LUN. To view the LUN information: 1. Do one of the following: • From the menu bar, click View, then click Sort by Host Name. • From the toolbar, click the Sort by Host Name button: . 2. Select a LUN in the discovery-tree. Figure 18: LUN Information LUN Information Field Definitions • • • Vendor Product Information Area • Vendor Name - The name of the vendor of the LUN.
Masking and Unmasking LUNs (Windows, Solaris LPFC and Solaris SFS) LUN masking refers to whether or not a LUN is visible to the operating system. A LUN that has been masked is not available and is not visible to the OS. You can use HBAnyware to mask or unmask LUNs at the host level. Note: In Solaris systems, the Emulex LPFC drivers support both a target level and HBA level LUN unmasking override feature.
To change the mask status of a LUN: 1. From the discovery-tree, click on a SCSI target. A set of LUNs appears below the selected SCSI target. The LUN Masking tab is displayed. This tab contains a list of the same set of LUNs appear below the SCSI target. Figure 20: LUN Masking tab 2. In the LUN list of the LUN Masking tab, select one or more LUNs. The LUN Masking tab buttons become active as is appropriate.
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. Select Host or Fabric sort. 2. Select an HBA in the discovery-tree. 3. Click the Statistics tab. Figure 21: Statistics tab Port Statistics Field Definitions • Tx Frames - FC frames transmitted by this HBA port. • Tx Words - FC words transmitted by this HBA port.
• 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 FC frames received by this HBA port. • Rx Words - The number of FC words received by this HBA port. • Rx KB Count - The received kilobyte count by this HBA port. • Rx Sequences - The number of FC sequences received by this HBA port.
Viewing Firmware Information Use the Firmware tab to view current firmware versions, enable system BIOS and update firmware on remote and local HBAs. To view the firmware information: 1. Select Host or Fabric sort. 2. Select an HBA in the discovery-tree. 3. Select the Firmware tab. Figure 22: Firmware tab Firmware Field Definitions Firmware Area • Current Firmware Version - The Emulex firmware version number for this model of HBA.
Viewing Target Mapping (Windows, Solaris LPFC and Solaris SFS) The Target Mapping tab enables you to view current target mapping and to set up persistent binding. To view target mapping: 1. Select Host or Fabric sort. 2. Select the HBA in the discovery-tree whose target mapping information you wish to view. 3. Select the Target Mapping tab. Figure 23: Target Mapping tab Target Mapping Field Definitions Current Settings Area • Active Bind Type - WWPN, WWNN, or a destination identifier (D_ID).
Viewing Target Mapping (Linux) Use this tab to view target mapping. The Target Mapping tab is read-only. Note: Persistent binding is not supported by the Linux 2.6 kernel or by the Emulex version 8 driver for Linux. To view target mapping: 1. Select Host or Fabric sort. 2. Select the HBA in the discovery-tree whose target mapping information you wish to view. 3. Select the Target Mapping tab.
Viewing and Setting Up Authentication (Windows, Solaris LPFC and Solaris SFS) Use the Authenticate tab to view and set up FC-SP DHCHAP configuration. You can initiate authentication asynchronously (at will) per HBA. Otherwise, when authentication is enabled, the HBA will attempt authentication with the switch at fabric login (FLOGI) time per the FC-SP standard. Note: To successfully authenticate with the switch using DHCHAP, you only need to set the configuration mode to enabled and set the local password.
• Bi-Directional - If selected, the driver (HBA) supports authentication initiated by either (both) the switch or the HBA. If this check box is clear, the driver supports HBA initiated authentication only. • Re-authenticate - If selected, the driver can periodically initiate authentication. • Re-authorization interval - The value in minutes that driver (HBA) will use to periodically initiate authentication. Valid interval ranges are between 10 to 3600 minutes. The default is 300.
Updating Firmware You can update firmware on local and remote HBAs. The firmware file must be downloaded from the Emulex Web site and extracted to a local drive before you can perform this procedure. Note: For OEM branded HBAs, see the OEM’s Web site or contact the OEM’s customer service department or technical support department for the firmware files. To update firmware: 1. In the discovery-tree, select the HBA. 2. Select the Firmware tab. Figure 26: Firmware tab 3. Click Update Firmware.
5. Navigate to the extracted firmware file you wish to download. Select the file and click Start Download. A status bar shows the progress of the download and indicates when the download is complete. 6. Click Close. The Firmware tab displays the updated firmware information for the selected HBA.
6. 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 30: Firmware Download dialog box with Download Complete 7. When downloading is complete, you can click Print Log to get a hard copy of the activity log. 8. Click Close to exit the batch procedure.
Enabling or Disabling an HBA’s BIOS Enabling the BIOS is a two-step process: 1. Enable the HBA BIOS (x86 BootBIOS, FCode or EFIBoot) to read the Emulex boot code on the HBA. 2. Enable the HBA to boot from SAN (using the BIOS utility). The Emulex boot code must be downloaded from the Emulex Web site and extracted to a local drive before you can perform this procedure. To enable or disable the HBA BIOS: 1. In the discovery-tree, select the HBA. 2. Select the Firmware tab.
Configuring the Driver In Windows, Solaris LPFC, Solaris SFS and Linux: Set driver parameters using the HBAnyware utility. In Solaris LPFC, Solaris SFS and Linux:, you can also specify parameters when loading the driver manually. 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.
4. In the Driver Parameters tab, click the parameter that you want to change. A description of the parameter appears on the right side of the tab. 5. Enter a new value in the Value field in the same hexadecimal or decimal format as the current value. If the current value is in hexadecimal format, it is prefaced by "0x" (for example, 0x2d). You may enter a new hexadecimal value without the "0x". For example, if you enter ff10, this value is interpreted and displayed as "0xff10". 6.
Setting Driver Parameters for a Host To change the driver parameters for HBAs installed in a host: 1. Do one of the following: • From the menu bar, click View, then click Sort by Host Name. • From the toolbar, click the Sort by Host Name button: . 2. In the discovery-tree, click the host whose HBA driver parameters you wish to change. 3. Select the Driver Parameters tab.
3. Unload the lpfcdfc driver. Type: rmmod lpfcdfc 4. Unload the lpfc driver. Type: rmmod lpfc 5. Reload the driver.Type: modprobe lpfc modprobe lpfcdfc The HBAnyware services will start automatically when you launch the application. For these changes to persist after a reboot you must create a new ramdisk image. Creating and Assigning a Batch Mode Driver Parameters File You can apply driver parameters for one HBA to other HBAs in the system using the Driver Parameters tab.
7. Click Save. The Save Driver Parameters dialog box appears. Figure 35: Save Driver Parameters dialog box 8. The two radio buttons allow you to choose the type of parameters to save. You can save all parameters or only those parameters whose current values differ from their corresponding default values. 9. A list of the saved parameters and their current values show in the Saved Parameters box. 10. Click Save. 11. Assign batch mode parameters to HBAs: From the Batch menu select Update Driver Parameters.
Storport Miniport Driver Parameter Reference Tables The parameter values listed in Table 1 are applicable to driver version 2.00 or later. If you are using a version previous to 2.00, see the Storport Miniport Driver User Manual for parameter information. Activation Requirements A parameter has one of the following activation requirements: • Dynamic - The change takes effect while the system is running. • Reset - Requires an HBA reset from the utility before the change takes effect.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definition s CoalesceRspCnt=n This parameter specifies the number of response entries that trigger an Interrupt response. Activation Requirement Restart Value: 0 - 255 (decimal) or 0x1 - 0xFF (hex) Default = 8 (0x8) DiscoveryDelay=n DiscoveryDelay controls whether the driver waits for ‘n’ seconds to start port discovery after link up. Dynamic If set to 0 = immediate discovery after link up.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definition s FrameSizeMSB=n FrameSizeMSB controls the upper byte of receive FrameSize if issued in PLOGI. This allows the FrameSize to be constrained on 256-byte increments from 256 (1) to 2048 (8). Activation Requirement Restart Value: 0 - 8 Default = 0 HardALPA=0xn HardALPA allows the HBA to use a hard assigned loop address.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definition s LogErrors=n LogErrors determine the minimum severity level required to enable entry of a logged error into the system event log. Errors are classified as severe, malfunction and command level. A severe error requires user intervention to correct a firmware or HBA problem. An invalid link speed selection is an example of a severe error.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definition s PciMaxRead This parameter enables override of default PCI read transfer length. The driver will auto-detect the presence of an AMD PCI bridge and adjust for this bridge. This parameter allows for override of the automatic value. Activation Requirement Restart Value: 512, 1024, 2048 and 4097 Default: 2048 RmaDepth=n This parameter sets the remote management buffer queue depth.
Table 1: Storport Miniport Driver Parameters (Continued) Parameter Definition s TraceBufSiz=n This parameter sets the size in bytes for the internal driver trace buffer. The internal driver trace buffer acts as an internal log of the driver's activity. Activation Requirement Reboot Value: 250,000 - 2,000,000 or 0x3D090 - 0x1E8480 (hex). Default = 250,000 (0x3D090) Table 2: Storport Miniport Topology Reference Table Topology Description Value Private Loop Operation Only FC-AL topology is used.
Driver for Solaris LPFC – The Configuration File Reference Table The parameter values listed in Table 3 are applicable to driver version 6.20i or later. If you are using a version previous to 6.20i, see the Emulex Driver for Solaris User Manual for parameter information. Note: The fcp-bind-WWNN, fcp-bind-WWPN and fcp-bind-DID driver properties do not apply to a specific HBA. They are the global properties. These properties specify a list of persistent bindings.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments auth-cfgparms Controller Specific Description and Values: This is the DH-CHAP related driver property for FC-SP support. It is only valid when driver property enable-auth is set to 1. This driver property should be ignored when enable-auth is set to 0. The format of this property is: "LWWN|RWWN|atov|amod|dir|tlist|hlist|dhgplist|raintval" LWWN: The WWPN of the local entity, i.e. HBA port.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments auth-keys Controller Specific Description and Values: This is the DH-CHAP authentication key driver property for FC-SP support. It is only valid when driver property enable-auth is set to 1. This driver property should be ignored when enable-auth is set to 0. The format of this property is like: "LWWN:ktype:klength:key:RWWN:ktype:klength:key" LWWN: The WWPN of the local entity, i.e. HBA port.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments cr-count Controller Specific 1 1 255 No This value specifies a count of I/O completions after which an interrupt response is generated. This feature is disabled if cr-delay is set to 0. cr-delay Controller Specific 0 0 63 No This value specifies a count of milliseconds after which an interrupt response generated if cr-count has not been satisfied.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments dqfull-throttle-upinc Controller Specific 1 0 128 Yes Amount to increment LUN queue depth each time. This driver property causes the lpfc driver to decrement a LUN’s queue depth, if a queue full condition is received from the target. The queue depth will be decremented down to a minimum of 1.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments dqfull-throttle-uptime Controller Specific 1 0 30 Yes Time interval (seconds) to increment LUN queue depth. Amount to increment LUN queue depth each time. This driver property causes the lpfc driver to decrement a LUN’s queue depth, if a queue full condition is received from the target. The queue depth will be decremented down to a minimum of 1.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments enable-auth Controller Specific 0 0 1 Yes This driver property specifies if the DH-CHAP is enabled or not. When set to 1, the you should also set up two other driver properties such as auth-cfgparms and auth-keys as described above. When set to 0, DH-CHAP support is disabled and auth-cfgparms and auth-keys are ignored.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments fcp-bind-method Controller Specific 2 1 4 No Specifies the method of binding to be used. This binding method is used for persistent binding and automapped binding. A value of 1 will force WWNN binding, value of 2 will force WWPN binding and value of 3 will force DID binding.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments fcp-bind-WWPN Global Inactive N/A N/A No Setup persistent FCP bindings based on a target device’s WWPN. This binding guarantees that target assignments will be preserved between reboots. The format for a bind entry is “NNNNNNNNNNNNNNNN:lpf cXtY” where NNNNNNNNNNNNNNNN is a 16 digit representation of the targets WorldWide Port Name, X is the driver instance number and Y is the target assignment.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments linkdown-tmo Controller Specific 30 0 255 Yes This variable controls how long the driver will hold I/O (0 - 255 seconds) after the link becomes inaccessible. When this timer expires, all I/O waiting to be serviced is aborted. For instance, FCP commands will be returned back to the target driver with a failure. The lower the value, the quicker the driver will fail commands back to the upper levels.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments lpfcNtM-tgt-throttle Controller Specific none 1 10240 No The maximum number of outstanding commands to permit for any target, including all LUNs on that target. This value overrides tgt-queuedepth. lpfcXtYlZ-lun-mask Controller Specific none 0 1 Yes The driver uses this value to determine whether or not to expose discovered LUNs to the OS.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments msi-mode Controller Specific 2 0 2 No This variable controls whether lpfc uses MSI based interrupts or legacy interrupts. If set to 2 (default), the driver will try to use multiple message MSI. If multiple message MSI is not possible due to an OS or hardware limitation, then the driver will attempt single message MSI. If single message MSI fails, then the driver will attempt legacy interrupts.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments nodev-tmo Controller Specific 30 0 255 Yes This variable (0 to 255 seconds) controls how long I/ O will be held by the driver if a device on the SAN disappears. If set, I/O will be held for the specified number of seconds. If the device does not appear on the SAN before nodev-tmo seconds, then the driver will fail all held I/O and mark the device as unavailable.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min Max Dynamic Comments post-ip-buf Controller Specific 128 64 1024 No This variable specifies the number of 4K STREAMS buffers to allocate and post to the fibre channel IP ring. Increase this setting for better IP performance under heavy loading. scan-down Controller Specific 1 0=Off 1=On Yes There are two scanning algorithms used to discover a node in a private loop.
Table 3: LPFC.conf Parameters (Continued) Property Name Scope Default Min topology Controller Specific 0x0 use-adisc Controller Specific xmt-que-size Controller Specific Dynamic Comments 0x0=loop , then P2P 0x2=P2P only 0x4=loop only 0x6=P2P, then loop No This variable controls the Fibre Channel topology expected by lpfc at boot time. Fibre Channel offers point-to-point, fabric, and arbitrated loop topologies.
Driver For Solaris SFS Parameters • The emlxs.conf file contains all the parameters necessary to initialize the Solaris SFS driver. • The HBAnyware utility reflects the Solaris SFS driver parameters. The parameter values listed in Table 4 are applicable to driver versions 1.22/2.22 or later. If you are using a version previous to 1.22/2.22, see the Emulex Driver for Solaris User Manual for parameter information. All parameters are controller-specific.
Table 4: emlxs.conf Parameters (Continued) Property Name Default Min Max Activation Comments console-errors 0x00000000 0x00000000 0xFFFFFFFF Requires reboot. Verbose mask for error messages to the console. cr-count 1 1 255 Requires link reset. This value specifies a count of I/O completions after which an interrupt response is generated. This feature is disabled if cr-delay is set to 0. cr-delay 0 0 63 Requires link reset.
Table 4: emlxs.conf Parameters (Continued) Property Name Default Min Max Activation Comments network-on 0 0 1 Requires reboot. Enables/disables IP networking support in the driver. num-iocbs 1024 128 10240 Requires HBA reset. This variable indicates the number of Input/ Output control block (IOCB) buffers to allocate. num-nodes 0 0 4096 Requires HBA reset. Number of FC nodes (NPorts) the driver will support.
Solaris SFS and Solaris LPFC Driver Parameter Cross-Reference Table The cross-reference information listed in Table 5 is applicable to the Driver for Solaris LPFC version 6.20i and the Driver for Solaris SFS version 1.22.2.223. If you are using a Solaris LPFC or Solaris SFS driver version previous to these listed, see the Driver User Manual for parameter information.
Table 5: Solaris SFS and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris SFS/ HBAnyware Parameter Solaris SFS/HBAnyware Min/Max, Defaults and Description Related LPFC Parameter consolenotices Min: 0x00000000 Max:0xFFFFFFFF Default: 0x0000000 Verbose mask for notice messages to the console.
Table 5: Solaris SFS and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris SFS/ HBAnyware Parameter Solaris SFS/HBAnyware Min/Max, Defaults and Description Related LPFC Parameter cr-count Min:1 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. cr-count Min:1 Max:255 Default:1 Description: Specifies a count of I/O completions after which an interrupt response is generated.
Table 5: Solaris SFS and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris SFS/ HBAnyware Parameter Solaris SFS/HBAnyware Min/Max, Defaults and Description Related LPFC Parameter log-warnings Min: 0x00000000 Max:0xFFFFFFFF Default: 0x0000000 Verbose mask for warning messages to the messages file.
Table 5: Solaris SFS and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris SFS/ HBAnyware Parameter Solaris SFS/HBAnyware Min/Max, Defaults and Description Related LPFC Parameter num-iocbs Min:128 Max:1024 Default = 10240 Description: Sets the number of iocb buffers to allocate. num-bufs Min:128 Max:10240 Default = 256 Description: Specifies the number of command buffers to allocate.
Table 5: Solaris SFS and Solaris LPFC Driver Parameter Cross-Reference (Continued) Solaris SFS/ HBAnyware Parameter Solaris SFS/HBAnyware Min/Max, Defaults and Description Related LPFC Parameter topology 0 = loop, if it fails attempt ptto-pt 2 = pt-to-pt only 4 = loop only 6 = pt-to-pt, if it fails attempt loop Default: 0 Description: Link topology for initializing the 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.
Driver for Linux, LPFC and LPFCDFC Parameter Tables The driver parameter values listed in Table 3 are applicable to driver version 8.0.16.34 or later. If you are using a version previous to 8.0.16.34, see the Emulex Driver for Linux User Manual for parameter information The parameters determine some aspects of the driver behavior. The following tables list the driver parameters.
Table 6: Driver for Linux, LPFC Static Parameters (Requires a driver reload to change) (Continued) Comments Visible using sysfs 0=auto select 1=1G 2=2G 4=4G Sets link speed. Yes 8192 32 8192 Maximum number of FCP commands that can queue to an Emulex HBA. Yes lpfc_lun_queue_depth 30 1 128 Default max commands sent to a single logical unit (disk).
All lpfc dynamic parameters are read/write using sysfs. Table 7: Driver for Linux, LPFC Dynamic Parameters (Do not require a driver reload to change) Variable Default Min Max Comments lpfc_discovery_min_wait* 3 0 60 The minimum number of seconds the driver waits for the discovery to complete. lpfc_discovery_wait_limit* 600 0 600 (special value meaning no limit) The maximum number of seconds the driver waits for the discovery to complete.
Server Performance (Windows) I/O Coalescing I/O Coalescing is enabled and controlled by two driver parameters: CoalesceMsCnt and CoalesceRspCnt. The effect of I/O Coalescing will depend on the CPU resources available on the server. With I/O Coalescing turned on, interrupts are batched, reducing the number of interrupts and maximizing the number of commands processed with each interrupt. For heavily loaded systems, this will provide better throughput.
NumFcpContext If the number of outstanding I/Os per HBA is expected to exceed 512, increase this parameter to a value greater than the number of expected I/Os per HBA. Increase this value in stages: from 128 to 256 to 512 to 1024 to a maximum of 2048i. NumFcpContext limits the number of outstanding I/Os per HBA, regardless of how QueueDepth is set. The NumFcpContext defaults to 512.
Mapping and Masking Automapping SCSI Devices (Windows) The driver defaults to automatically mapping SCSI devices. The procedures in this section apply if the default has been changed. To automap SCSI devices: 1. Display driver parameters for the host or HBA - select the Driver Parameters tab or the host Driver Parameters tab. 2. Select the AutoMap HBA parameter. Several fields about the parameter appear on the right side of the screen. 3. Select Enabled. 4.
Setting Up Persistent Binding (Windows, Solaris LPFC and Solaris SFS) You can set up persistent binding on remote and local HBAs. Global automapping assigns a binding type, target ID, SCSI bus and SCSI ID to the device. The binding type, SCSI bus and SCSI ID may change when the system is rebooted. With persistent binding applied to one of these targets, the WWPN, SCSI bus and SCSI ID remain the same when the system is rebooted. The driver refers to the binding information at bootup.
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 38: 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: Automapped targets have entries only in the second column of the Targets Table. Persistently bound targets have entries in the second and third columns.
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.
Creating the ACG To create the ACG: 1. Start the HBAnyware utility Security Configurator for the first time in an unsecure environment. A warning message appears. 2. Click OK. The Access Control Group tab appears: Figure 40: Access Control Group tab - No ACG Servers 3. Select the unsecured servers that you want to add to the ACG from the Available Servers list. Figure 41: Access Control Group tab with ACG Servers 4. Click the left arrow to add the servers to the Access Control Group Servers list. 5.
Designating a Master Security Client The first time you run the HBAnyware Security Configurator on any system in a Fibre Channel network, that system becomes the MSC (Master Security Client). See “Running the Configurator for the First Time” on page 86 for more information.
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 43: Access Control Group tab on a Non_MSC System ACG Icons Depending on the configured security topology, a system can be a server in one or more ACGs.
Deleting a Server from the ACG To delete a server from the Access Control Group (ACG): 1. On the Access Control Group tab, from the Access Control Group Servers list, select the secured systems to delete from the ACG (Figure 42). 2. Click the right arrow to remove the servers from the Access Control Group Servers list. 3. Click OK (or Apply). Removing Security from all Servers in the ACG You can remove security from all systems only from the Master Security Client (MSC).
Access Sub-Groups Introduction Use the Access Sub-Group tab 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, we recommend 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 shows in the Access Sub-Groups tab as a tree. You can create, modify and delete ASGs at each level in this tree.
Creating an ASG 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 ACG shows the servers that were configured in the ASG by its parent client. To create an ASG: 1. Click the Access Sub-Groups tab. Figure 45: Access Sub-Groups tab with No Sub-Groups Created 2. Click New.
Reserved Indices - Examples A particular security installation can support the creation of several hundred access groups (ACGs and ASGs). When you create each new access group, you allocate some number of 'indices' to the client system of the new ASG. This number reflects the number of subsequent 'child' ASGs that you can subsequently create at the new client's system. • If zero indices are reserved, you cannot create any lower-level ASG under the client of the new ASG.
Restoring an ASG to Its Last Saved Configuration You can restore an Access Sub-Group (ASG) to its last saved configuration if there are unsaved changes to it. To restore an ASG to its last saved configuration: 1. Click the Access Sub-Group tab (see Figure 45 on page 91). 2. Select the ASG whose configuration you want to restore. 3. Click Restore. 4. Click OK (or Apply) to save your changes. Editing an ASG You can change the name, client system or reserved indices of an Access Sub-Group (ASG).
About Offline ASGs Sometimes a client system may not be online when the HBAnyware Security Configurator is running. In this case, the Access Sub-Group (ASG) for the client appears offline in the ASG tree, much like the following: Figure 48: Access Sub-Groups tab - Client System Offline The offline ASG entry serves as a placeholder for where the real ASG would be in the tree. You cannot modify or delete the entry (although it is removed from the display if all of its child ASGs are deleted).
Backup Masters Introduction A Backup Master mirrors the security data of the Master Security Client (MSC) in case it has to take over as the MSC if the MSC is unable to operate or is removed from the security configuration. A Backup master system receives all the updates to the security configuration on the MSC. However, you cannot make modifications to the security configuration on a Backup Master.
Creating a Backup Master To create a Backup Master: 1. On the Master Security Client (MSC), start the HBAnyware Security Configurator. 2. Click the Backup Master tab. Figure 50: Backup Master tab with Backup Masters 3. Select a system from the Available Systems list. 4. Click the left arrow to move the system to the Backup Masters list. 5. Click OK (or Apply) to save your changes.
Reassigning a Backup Master as the New MSC from the Backup Master WARNING: Use this method only if the MSC cannot relinquish control to a Backup Master. For example, if you can no longer boot the MSC or connect to the Fibre Channel network. Under any other circumstances, if the Backup Master takes over as the MSC, and the MSC is still running or comes back online later, there will be two MSCs for the same security configuration. This will eventually lead to corruption of the security configuration.
Diagnostics Performing Diagnostic Tests Note: All diagnostic tests and diagnostic dumps can only be performed on the local system or on remote systems connected with TCP/IP access. Diagnostic tests and diagnostic dumps cannot be performed on remote systems connected with Fibre Channel access.
Running a Quick Test The Diagnostics tab enables you to run a quick diagnostics test on a selected HBA. The Quick Test consists of 50 PCI Loopback test cycles and 50 Internal Loopback test cycles. To run a quick test: 1. From the discovery-tree, select the HBA on which you wish to run the Quick Test. 2. Select the Diagnostics tab and click Quick Test. A warning message appears. Figure 53: Quick Test Warning window 3. Click OK to run the test.
Creating Diagnostic Dumps The diagnostic dump feature enables you to create a “dump” file for a selected HBA. Dump files contain various information such as firmware version, driver version and so on, that is particularly useful when troubleshooting an HBA. Caution: Disruption of service may occur if a diagnostic dump is run during I/O activity. To start a diagnostic dump: 1. From the discovery-tree, select an HBA whose diagnostic information you wish to dump. 2.
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: Click Advanced Diagnostics Test on the Diagnostics tab to view the Advanced Diagnostics dialog box.
Running Loopback Tests To run a loopback test, use the Loopback Test section of the Advanced Diagnostics dialog box. Loopback Test Combinations 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.
3. Click Start. The following warning appears: Figure 57: Advanced Diagnostic Tests Warning window 4. Click OK. If you choose to run an External Loopback test the following window appears: Figure 58: Advanced Diagnostic Tests Warning window for External Loopback 5. 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.
All relevant information for the selected port is automatically added to the Target Identifier section of the Diagnostics dialog box. Figure 59: Select Echo Test Target window 4. Click Start. The following warning window appears: Figure 60: Advanced Diagnostic Tests Warning window 5. Click OK. A result screen appears and the test results appear in the Test Log. Click Clear to erase the contents of the log display or click Save to File to save the log file.
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.
Using the HBAnyware Utility Command-Line Interface The Command Line Interface (CLI) Client component of the HBAnyware utility provides access to the capabilities of the Remote Management library from a console command prompt. This component is intended for use in scripted operations from within shell scripts or batch files. The CLI Client is a console application named hbacmd. Each time you run this application from the command line, a single operation is performed.
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. Parameters: None SaveConfig Syntax: hbacmd SaveConfig Description: Saves the specified HBA’s driver parameters to a file. The resulting file will contain a list of driver parameter definitions in ASCII file format with definitions delimited by a comma.
TargetMapping Syntax: hbacmd TargetMapping Description: Shows a list of mapped targets and the LUNs for the port. Parameters: WWPN - World Wide Port Name of the HBA whose target mapping you wish to view Reset Syntax: hbacmd Reset Description: Resets the HBA. An HBA reset may require several seconds to complete, especially for remote devices. Once the reset command is completed, the system command prompt is displayed.
GetLunUnMaskbyTarget Syntax: hbacmd GetLunUnMaskByTarget
PersistentBinding Syntax: hbacmd PersistentBinding Description: Specifies which set of persistent binding information is requested: the configured or live state of any present binding.
BindingCapabilities Syntax: hbacmd BindingCapabilities Description: Shows the binding capabilities present for the HBA. If a binding is configured, it means the binding is maintained across reboots. Parameters: WWPN - World Wide Port Name of the HBA whose binding capabilities you wish to view BindingSupport Syntax: hbacmd BindingSupport Description: Shows the binding support available for the HBA.
GetDriverParamsGlobal Syntax: hbacmd GetDriverParamsGlobal Description: Shows the name and the global value of each driver parameter for the HBA. Parameters: WWPN - World Wide Port Name of the HBA whose driver parameter global names and values you wish to view SetDriverParam Syntax: hbacmd SetDriverParam Description: Allows you to change the value of a driver parameter and designate the scope of that change.
SetAuthConfig Syntax: hbacmd SetAuthConfig Description: Sets the authentication configuration for the HBA.
InitiateAuth Syntax: hbacmd InitiateAuth Description: Initiates the authentication configuration on the HBA. Parameters: WWPN1 - World Wide Port Name of the HBA whose authentication configuration you wish to initiate WWPN2 - Must be ff:ff:ff:ff:ff:ff:ff:ff PCIData Syntax: hbacmd PCIData Description: Shows PCI configuration data for the HBA.
PostTest Syntax: hbacmd PostTest Description: Runs the POST on the HBA. Support for a remote HBA is TCP/IP access only. Parameters: WWPN - World Wide Port Name of the HBA on which you wish to run a POST EchoTest Syntax: hbacmd EchoTest Description: Runs the echo test on HBAs. Note: Support for remote HBA is TCP/IP access only. The EchoTest command will fail if the target WWPN does not support the ECHO ELS command.
GetRetentionCount Syntax: hbacmd GetRetentionCount Description: Displays the maximum number of diagnostic dump files stored for the HBA. Parameters: WWPN - World Wide Port Name of the HBA on which you wish to get the retention count SetRetentionCount Syntax: hbacmd SetRetentionCount Description: Specifies the maximum number of diagnostic dump files stored for the HBA.
Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains many of these circumstances and offers one or more workarounds for each situation. General Situations Table 11: General Situations Situation Resolution When attempting to start HBAnyware the Web browser displays “Emulex Corporation HBAnyware Demo of HBAnyware WebStart web n.n.n.n...
Table 11: General Situations (Continued) Situation Resolution SAN Management Workstation Does Not Have a Fibre Channel Connection. The SAN management workstation does not have a physical Fibre Channel connection into the SAN because the other management tools are all out-of-band. Can HBAnyware be run on this SAN management workstation? HBAnyware can communicate with remote HBAs using out-ofband access as long as the remote host is running HBAnyware and the remote server. To solve this problem: 1.
Emulex Driver for Windows and HBAnyware Situations Table 12: Emulex Driver for Windows and HBAnyware Situations Situation Resolution lputilnt Installs, but HBAnyware Does Not. When you run setupapps.exe, lputilnt installs but HBAnyware does not. You have attempted to manually install the utilities for the driver before manually installing the driver Perform the installation tasks in the following order: 1. Install the driver (see the Installation section of the Storport User Manual). 2.
Emulex Driver for Linux and HBAnyware Situations Table 14: Emulex Driver for Linux and HBAnyware Situations Situation Resolution If a SAN configuration has 256 targets mapped by the lpfc driver, any additional added targets do not get a target ID mapping by the driver and cause target discovery to fail. Removing targets or reinitializing the link does not solve the problem. Unload and reload the driver to reset available target IDs.
Table 14: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution Under certain conditions of an I/O load, some targets cannot retire an I/O issued by a Linux initiator within the default timeout of 30 seconds given by the scsi midlayer. If the situation is not corrected, the initiator-to-target condition deteriorates into abort/recovery storms leading to I/O failures in the block layer. These types of failures are preceded by a SCSI IO error of hex 6000000.
Table 14: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution "No module lpfc found for kernel" error message. When upgrading the kernel, rpm generates the following error: "No module lpfc found for kernel KERNELVERSION". These three situations may be resolved by upgrading the kernel. There are two ways to install the driver into an upgraded kernel. The method you use depends on whether or not you are upgrading the driver.
Table 14: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution The Linux SCSI subsystem only sees 8 LUNs when more are present. Some SCSI drivers will not scan past 8 LUNs when the target reports as a SCSI-2 device. Force SCSI bus scan with /usr/sbin/ lpfc/lun_scan. SuSE supplies /bin/rescan-scsi-bus.sh which can be changed to scan everything. Cannot See Any HBAs. You launch HBAnyware and no HBAs are visible.
Table 14: Emulex Driver for Linux and HBAnyware Situations (Continued) Situation Resolution Cannot access formerly accessible servers via the Security Configurator or the HBAnyware Utility. This is actually a symptom of two different problems.
Security Configurator Situations - Access Control Groups (ACG) Table 15: Access Control Groups Situations Situation Resolution All servers are not displayed. When I run the Security Configurator on the Master Security Client (MSC), I do not see all of the systems in available servers or ACG Servers lists. When I run the Security Configurator on a non-MSC, I do not see all of the systems I should see in the ACG Servers list.
Table 16: HBAnyware Security Configurator - Access Sub-Groups Situations (Continued) Situation Resolution In the ASG tree of the Access Sub-Groups tab, one or more of the names of the ASGs is displayed as "- ASG (Client Offline) -". The client system for the ASG was not discovered when the Configurator was started. This is actually a symptom of two different problems.
HBAnyware Security Configurator Situations - Backup Masters Table 17: HBAnyware Security Configurator - Backup Masters Situations Situation Resolution Cannot create a backup master. Select a system (or group of systems) from the MSC to be the Backup Master. The system must be either an unsecured system (which will be secured by being made a Backup Master), or a system that is not part of any ASG (client or server). These systems will mirror the MSC's security configuration.
Error Message Situations Table 18: Error Message Situations Situation Resolution The following error message is displayed when creating an ASG: “The Access Sub-Group name already exists. Please use a different name.” You entered a duplicate ASG name in the Access SubGroup Name field. At each level of the security topology, each ASG name must be unique. Click OK on the message and enter a unique ASG name.
Master Security Client Situations Table 19: Master Security Client Situations Situation Resolution The MSC is no longer bootable or able to connect to the FC network. You must reassign a Backup Master as the new MSC from the Backup Master. Warning: Use this procedure only if the MSC cannot relinquish control to a Backup Master. For example, if the MSC is no longer bootable or able to connect to the FC network.
Non-Hierarchical and Hierarchical ASG It is possible from a higher-level client (such as the MSC) to create an ASG 1 with system A as the client and systems B, C, D, and E as servers. Then create an ASG 2 with system E as the client, but with systems F and G as servers even though F and G are not part of ASG 1. This makes the topology nonhierarchical (see Figure 62).
Figure 63: Hierarchical ASG Scenario The HBAnyware Utility User Manual Page 131
