Chapter 7: Managing Adapters and Ports
This chapter describes the various adapter and port management functions you can perform using the Emulex HBA Manager application.
7.1 Viewing Adapter Information
When you select an adapter from the discovery-tree (Figure 4), the Adapter Information tab (Figure 16) contains general attributes associated with the selected adapter.
To view adapter information, perform the following steps:
1. Select the Host, Fabric, or Virtual Ports view.
2. Select an adapter in the discovery-tree. The Adapter Information tab appears (Figure 16).
Figure 16: Adapter Information Tab (Two-Lane Trunking Supported)
The following Adapter Information tab fields are displayed:
n Model – The complete model name of the adapter.
n Serial Number – The manufacturer's serial number for the adapter.
n Hardware Version – The version of the adapter.
n Device ID – The PCIe device ID for the selected adapter.
n IPL File Name – The IPL file name for the selected adapter.
n Adapter Temperature – If the adapter's temperature is not available, Not Supported is displayed. If supported by the adapter, this field displays the following adapter temperature-related status messages:
– Normal: The adapter’s temperature is within the normal operational range.
– Warning: The adapter’s temperature is beyond the normal operational range. If the temperature continues to increase, the adapter shuts down. You must determine the cause of the temperature issue and fix it immediately. Check for system cooling issues. Common causes of system cooling issues include clogged air filters, inoperative fans, and air conditioning issues that cause high ambient air temperatures.
– Exceeds operational range – Adapter stopped: The temperature has reached a critical limit, forcing the adapter to shut down. You must determine the cause of the temperature issue and fix it before resuming operation. Check for system cooling issues. Common causes of system cooling issues include clogged air filters, inoperative fans, and air conditioning issues that cause high ambient air temperatures.
After the system overheating issue is resolved and the adapter has cooled down, reboot the system, or if the system supports hot swapping, power-cycle the adapter slot.
n Trunking (FC Port Aggregation) area:
– When supported by the adapter, you can combine multiple physical FC links to form a single logical link. After the logical link is created, you can view its speed and physical link status. See Section 7.1.1, Configuring Trunking, for additional information.
The following information applies to trunking:
n Trunking is supported only on LPe35000-series and LPe36000-series adapters.
n Dynamic D_Port cannot coexist with the trunking feature on LPe35000-series and LPe36000-series adapters. If trunking is enabled, the firmware automatically disables Dynamic D_Port.
n Trunking is not supported at 8Gb/s, and the link will not come up at this speed.
n Before you configure trunking on an Emulex adapter, follow the Brocade® instructions for configuring trunking on the switch.
The Adapter Information tab enables you to configure trunking (also called FC port aggregation), which combines multiple physical FC links to form a single logical link (aggregated port). The aggregated port’s maximum link speed is the sum of the maximum link speeds of the individual physical links comprising the aggregated port. For example, an aggregated port comprised of two physical links running at 64Gb/s each will have a potential logical (aggregate) link speed of 128Gb/s. The actual link speed of the aggregated port depends on the states (active or nonactive) of the individual physical links comprising the aggregated port.
The physical links comprising an aggregated port are referred to as lanes. Both 2-lane and 4-lane aggregated ports are supported. For dual-port adapters, only 2-lane port aggregation is possible. If 2-lane port aggregation is configured on a dual-port adapter, the two physical links are combined to form a single 2-lane aggregated port whose aggregate speed is potentially 128Gb/s assuming that both physical links are active, each at 64Gb/s link speed.
LPe35004 adapters support both 2-lane port aggregation and 4-lane port aggregation. If 2-lane port aggregation is configured on an LPe35004 adapter, the four physical links on the adapter are divided among two separate aggregated ports. The two lowest numbered physical links form the first aggregated port, and the two highest numbered physical links form the second aggregated port. If 4-lane port aggregation is configured on an LPe35004 adapter, all four physical links are combined to form a single 4-lane trunk whose aggregate speed is potentially 128Gb/s, assuming that all four links are active, each at 32Gb/s link speed.
Figure 17: Adapter Information Tab (Two-Port Adapter with Two-Lane Trunking Enabled)
To set trunking, perform the following steps:
1. In the discovery-tree (Figure 4), select the supported adapter port whose trunking you want to set.
2. Select the Adapter Information tab (Figure 17).
3. Select Disabled, 2-lane, or 4-lane.
NOTE: On an LPe35004 adapter, if 2-lane port aggregation is selected, the four physical links on the adapter are divided among two separate aggregated ports (Port 0 and Port 1). The two lowest numbered physical links form the first aggregated port (Port 0), and the two highest numbered physical links form the second aggregated port (Port 1).
4. Click Apply. The Trunking Configuration dialog notifies you that your changes require a system reboot.
Figure 18: Trunking Configuration Dialog
5. Click OK and reboot the system.
When you select a port from the discovery-tree, the Port Information tab (Figure 19) contains general attributes associated with the selected adapter.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
To view port information, perform the following steps:
1. Select the Host or Fabric view.
2. Select a port in the discovery-tree.
3. Select the Port Information tab (Figure 19).
Figure 19: Port Information Tab
The following Port Information tab fields are displayed:
– Port WWN – The WWPN of the adapter.
– Node WWN – The WWNN of the adapter.
– Fabric Name or Host Name – The Fabric Name field is displayed in the Host view. The fabric name is a 64-bit worldwide unique identifier assigned to the fabric. The Host Name field is displayed in the Fabric view and is the name of the host that contains the adapter.
– Boot Version – The boot version is no longer displayed in this field. See the Firmware tab for the adapter (Section 7.4, Viewing Firmware Information) to view the boot version.
– PCI Function – The PCI function number assigned by the system.
– PCI Bus Number – The PCI bus number assigned to the FC function.
– Driver Version – The version of the driver installed for the adapter.
– Driver Name – The executable file image name for the driver as it appears in the Emulex driver download package.
– Firmware Version – The version of Emulex firmware currently active on the adapter port.
– Port FC ID – The FC ID for the selected adapter port.
– Discovered Ports – The number of ports found during discovery by the Emulex adapter driver.
– Port Type – The FC type of the selected adapter’s port (not available if the port link is down).
– OS Device Name – The platform-specific name by which the selected adapter is known to the operating system.
– Symbolic Node Name – The FC name used to register the driver with the name server.
– Supported Class of Service – A frame delivery scheme that exhibits a set of delivery characteristics and attributes. Two classes of service can be displayed:
l Class 2 – Provides a frame-switched service with confirmed delivery or notification of nondelivery.
l Class 3 – Provides a frame-switched service similar to Class 2 but without notification of frame delivery or nondelivery.
– Supported FC4 Types – A 256-bit (8-word) map of the FC-4 protocol types supported by the port that contains the selected adapter.
– Link Status – The status of the link on the selected adapter port.
– Port Speed – The current port speed of the selected adapter port. For trunked ports, the maximum speed that the trunked port is capable of (if all ports in the trunk are up) is displayed.
7.2.1 Enabling and Disabling a Port
You can enable or disable a port from the Port Information tab. When you disable a port, you disable all functions for the port.
CAUTION! Do not disable a boot port; doing so could result in data loss or corruption.
The following information applies to enabling or disabling a port:
n Ensure that there is no I/O traffic on the port before disabling it.
n You must reset the adapter to activate the new value.
n The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
1. Select the Host or Fabric view.
2. Select a port in the discovery-tree.
3. From the Port Information tab, click Enable Port or Disable Port. The following popup appears.
4. Click Yes to enable or disable the port.
7.3 Viewing Firmware Parameters
To view firmware parameters, select the Firmware Parameters tab (Figure 20).
Figure 20: Firmware Parameters Tab
The following Firmware Parameters tab fields are displayed:
n Configured Link Speed – This field displays the link speeds that are supported on the port. The list varies depending on the adapter type. The list also includes an Auto Detect option, which indicates that the link speed should be auto-negotiated. See Section 7.3.1, Configuring Link Speed, for more information.
NOTE: If an installed adapter does not support forced link speeds, the Configured Link Speed settings and the Apply button are not shown.
n FA-PWWN – This field displays the FA-PWWN status of the port. FA-PWWN allows a switch to assign a virtual WWPN to the initiator. Disabled is the default setting. See Section 7.3.2, Enabling and Disabling FA-PWWN, for more information.
n Dynamic D_Port – This field displays the Dynamic D_Port status of the port. Dynamic D_Port allows D_Port tests to be initiated from the switch side. Enabled is the default setting. See Section 7.3.3, Enabling and Disabling Dynamic D_Port, for more information.
n FEC – This field displays the 16G FEC status of the port. Enabled is the default setting.
n Topology – This field displays the topology in use (available only when supported by the adapter). The following topology options are available:
To configure a link speed, perform the following steps:
1. Select the Firmware Parameters tab (Figure 20).
2. Select a link speed from the Configured Link Speed list (Figure 21).
Figure 21: Configured Link Speed List
3. Click Apply to set the new link speed. The Apply button is enabled only if the currently selected link speed does not match the current speed.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
If the speed has been set successfully, the following message states that the port must be reset to activate the new speed setting.
5. From the toolbar, click the
Reset Port button.
In some situations, the currently configured link speed is not in the supported speed list for the port. This situation can occur if a new SFP is installed that supports a different set of link speeds than the previously installed SFP. If the currently configured link speed is not in the supported speed list, the following message is displayed:
Warning: The currently configured port speed is not a valid supported speed.
Please select a link speed and click Apply.
The Apply button remains enabled until you select a valid port speed.
If the installed SFP is not supported by the adapter, you cannot configure a link speed. In this situation, the following message is displayed:
If an adapter does not support forced link speeds, the Firmware Parameters tab does not show a Configured Link Speed list.
7.3.2 Enabling and Disabling FA-PWWN
The following information applies to FA-PWNN:
n The switch must support FA-PWWN. Refer to the documentation that accompanied the switch for instructions on configuring FA-PWWN on the switch.
n The link is toggled if FA-PWWN is enabled, but the switch does not support FA-PWWN.
n After enabling or disabling FA-PWWN, the port must be reset for changes to take effect.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or an offline port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
n When a new WWPN is assigned using FA-PWWN, persistently stored configuration information associated with the original WWPN, such as driver parameters and LUN frame priority settings, is not applied to the newly assigned WWPN. The configuration information associated with the original WWPN must be reconfigured for the new WWPN.
n Dynamic D_Port and FA-PWWN cannot be enabled simultaneously. If Dynamic D_Port is enabled and you want to enable FA-PWWN, you must first disable Dynamic D_Port. If FA-PWWN is enabled and you want to enable Dynamic D_Port, you must first disable FA-PWWN.
To enable or disable FA-PWWN, perform the following steps:
1. Select the Firmware Parameters tab (Figure 20).
2. Select Enabled or Disabled from the FA-PWWN list.
3. Click Apply. The following popup appears.
5. From the toolbar, click the 
Reset Port button.
6. Restart the Emulex HBA Manager application.
NOTE: The following popup appears if the FA-PWWN change was unsuccessful.
Figure 22: Change Firmware Parameter Popup
7.3.3 Enabling and Disabling Dynamic D_Port
To run D_Port tests from the switch, Dynamic D_Port must be enabled on the adapter. When Dynamic D_Port is enabled, the adapter port passes I/O normally until a D_Port command is received from the switch, at which time the adapter port runs the diagnostic tests before returning to normal service. Dynamic D_Port is enabled by default.
The following information applies to Dynamic D_Port:
n The Emulex HBA Manager application D_Port diagnostics are run from the adapter, and the switch port must have Dynamic D_Port mode enabled. You must disable Dynamic D_Port on the adapter to run D_Port diagnostic tests using the Emulex HBA Manager application. See Section 10.4, Running D_Port Tests, for more information about D_Port.
n Dynamic D_Port cannot be enabled simultaneously with DH-CHAP or FA-PWWN. If Dynamic D_Port is enabled and you want to enable DH-CHAP or FA-PWWN, you must first disable Dynamic D_Port.
n Dynamic D_Port does not appear on the Firmware Parameters tab if it is not supported.
n Dynamic D_Port must be enabled on the HBA port when D_Port testing is initiated from the switch. Dynamic D_Port must be disabled on the HBA port when D_Port testing is initiated from the HBA.
n Dynamic D_Port testing is not available when trunking is enabled.
n If Dynamic D_Port is enabled on an HBA, the tests are not supported in a direct-connect point-to-point environment. The HBA must be connected to a Brocade switch to run D_Port tests.
n When using Dynamic D_Port in a BFS configuration, the configuration must have redundant paths to the boot LUN, and only one of the redundant adapter ports should be set to Dynamic D_Port.
n Revision A of the FOIT AFCT-57F3TMZ-ELX (16GFC longwave optic transceiver) does not support D_Port for MDS Diagnostic for Cisco switches.
n Neither Revision A nor Revision B of the FOIT AFCT-57F3TMZ-ELX (16GFC longwave optic transceiver) supports D_Port for Brocade switches.
n For more information about D_Port, refer to the Brocade section of the Broadcom website at www.broadcom.com.
To enable or disable Dynamic D_Port on the adapter, perform the following steps:
1. From the discovery-tree (Figure 4), select the port on which you want to enable or disable Dynamic D_Port.
2. Select the Firmware Parameters tab (Figure 20) and choose Enabled or Disabled from the Dynamic D_Port list.
7.3.4 Enabling and Disabling 16G FEC
To enable or disable 16G FEC, perform the following steps:
1. Select the Firmware Parameters tab (Figure 20).
2. Select Enabled or Disabled from the FEC list.
3. Click Apply. The Change Firmware Parameter popup (Figure 22) appears.
5. From the toolbar, click the 
Reset Port button.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
6. Restart the Emulex HBA Manager application.
7.4 Viewing Firmware Information
Use the Firmware tab (Figure 23) to download firmware and create diagnostic dumps.
To view firmware information, perform the following steps:
2. Select an adapter in the discovery-tree (Figure 4).
3. Select the Firmware tab (Figure 23).
The following Firmware tab fields are displayed:
n Active Firmware Version – Displays the firmware version currently being used by the adapter.
n Flash Firmware Version – Displays the firmware version stored in the flash on the adapter.
n Boot Code Versions – Displays the versions of the adapter boot code. It has no relation to the FC boot code versions.
n Secure Firmware – Displays the Enabled or Disabled status of the adapter’s secure firmware feature.
NOTE: A secure jumper must be installed on LPe31000-series and LPe32000-series adapters to enable secure firmware. Refer to the adapter’s installation guide for more information about enabling secure firmware.
n Firmware Status – Displays any activation requirements necessary to use the new firmware. This field does not appear if no activation requirements are necessary.
NOTE: The buttons on the Firmware tab are not available in read-only mode.
n Download Firmware – Click this button to update the adapter’s firmware. See Chapter 8, Updating Adapter Firmware, for information on updating firmware.
n Diagnostic Dump – Click this button to perform a diagnostic dump on the adapter. See Section 10.7, Creating Diagnostic Dumps, for information about performing a diagnostic dump.
7.5 Viewing and Clearing Statistics
When you select a port from the discovery-tree, the Statistics tab (Figure 24) provides cumulative totals for various error events and statistics on the port. If supported by the adapter, you can also clear all the values displayed in the tab.
NOTE: Some statistics are cleared when the adapter is reset.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
To view statistics, perform the following steps:
1. Select the Host or Fabric view.
2. Select a port in the discovery-tree.
The following Statistics tab fields are displayed:
n Tx Frames – FC frames transmitted by this FC function.
n Tx Words – FC words transmitted by this FC function.
n Tx KB Count – FC kilobytes transmitted by this FC function.
n Tx Sequences – FC sequences transmitted by this FC function.
n LIP Count – The number of LIP events that have occurred for the FC function. This field is not supported if the topology is not arbitrated loop. Loop initialization consists of the following:
– Temporarily suspending loop operations.
– Determining whether loop-capable ports are connected to the loop.
– Providing notification of configuration changes and loop failures.
– Placing loop ports in the monitoring state.
n Error Frames – The number of frames received with CRC errors.
n Link Failures – The number of times the link has failed. A link failure is a possible cause of a timeout.
n Loss of Signal – The number of times the received FC signal was lost.
n Invalid Tx Words – The total number of invalid words transmitted by this FC function.
n Ex Count Orig – The number of FC exchanges originating on this FC function. (This option is not supported on VMware ESXi servers being managed through the CIM interface.)
n Active Exchanges – The number of active FC exchanges. (This option is not supported on VMware-based ESXi platforms using the CIM interface).
n Received P_BSY – The number of FC port-busy link response frames received.
n Link Transitions – The number of times the SLI® port sent a link attention condition.
n Elastic Buf Overruns – The number of times the link interface has had its elastic buffer overrun.
n Rx Frames – The number of FC frames received by this FC function.
n Rx Words – The number of FC words received by this FC function.
n Rx KB Count – The received kilobyte count by this FC function.
n Rx Sequences – The number of FC sequences received by this FC function. (This option is not supported on VMware ESXi servers being managed through the CIM interface.)
n NOS Count – The number of NOS events that have occurred on the switched fabric. (This option is not supported for the Emulex drivers for Windows or for arbitrated loop.)
n Dumped Frames – The number of frames that were lost because of a lack of host buffers available. (This option is not supported for the Emulex drivers for Windows.)
n Loss of Sync – The number of times loss of synchronization has occurred.
n Prim Seq Prot Errs – The Primitive Sequence Protocol error count. This counter is incremented whenever there is any type of protocol error.
n Invalid CRCs – The number of frames received that contain CRC failures.
n Ex Count Resp – The number of FC exchange responses made by this FC function. (This option is not supported on VMware ESXi servers being managed through the CIM interface.)
n Active RPIs – The number of active logins. (This option is not supported on VMware ESXi servers being managed through the CIM interface).
n Receive F_BSY – The number of FC fabric-busy link response frames received.
n Prim Seq Timeouts – The number of times a primitive sequence event timed out. (This option is not supported on VMware ESXi servers being managed through the CIM interface.)
n Arbitration Timeouts – The number of times that the arbitrated loop has timed out. Large counts could indicate a malfunction somewhere in the loop or heavy usage of the loop. (This option is not supported on VMware ESXi servers being managed through the CIM interface.)
To clear all the values displayed on the tab, click Clear Counters if it is available.
7.6 Viewing Virtual Port Information
The Discovery Information tab (Figure 25) displays information about virtual ports and their associated targets and LUNs.
To view virtual port information, perform the following steps:
1. Perform one of the following tasks:
– From the View menu, select Group Adapters by Virtual Port.
– From the toolbar, click the 
Group Adapters by Virtual Port button.
The Discovery Information tab appears (Figure 25).
Figure 25: Discovery Information Tab
The following Discovery Information tab fields are displayed:
n Hosts – The total number of hosts discovered in the SAN.
n Adapters – The total number of adapters discovered in the SAN.
n Physical Ports – The total number of physical ports discovered in the SAN.
– FC Functions – The total number of FC functions discovered in the SAN.
– FC Targets – The total number of FC targets discovered in the SAN.
– VPorts – The total number of virtual ports discovered in the SAN.
7.7 Creating and Deleting Virtual Ports
This section describes how to create and delete virtual ports.
Use the Virtual Ports tab (Figure 26) to create the virtual port WWPN.
NOTE: The Emulex HBA Manager application cannot create or delete virtual ports on VMware ESXi server systems. Although the VMware ESXi server supports NPIV, only VMware management tools can create or delete virtual ports.
NOTE: In Linux, virtual ports do not persist across system reboots.
The NPIV driver parameter must be enabled before you attempt to create a virtual port, and the SLI mode driver parameter must be set to 0 or 3. The driver parameter names vary slightly depending upon your operating system.
n For Windows: The NPIV parameter name is enableNPIV, and the SLI mode parameter name is SLIMode.
n For Linux: The NPIV parameter name is lpfc_enable_npiv, and the SLI mode parameter name is lpfc_sli_mode.
See Section 7.17, Configuring the Driver Parameters, for more information on enabling driver parameters.
To create a virtual port, perform the following steps:
1. Perform one of the following tasks:
– From the View menu, select Group Adapters by Virtual Ports.
– From the toolbar, click the 
Group Adapters by Virtual Ports button.
2. From the discovery-tree, select the FC function on which you want to create a virtual port. The Virtual Ports tab appears (Figure 26).
3. Enter a unique WWPN for the new virtual port. You can create as many virtual ports as you want. A valid port name must have one of the following formats:
10:00:xx:xx:xx:xx:xx:xx
2x:xx:xx:xx:xx:xx:xx:xx
3x:xx:xx:xx:xx:xx:xx:xx
5x:xx:xx:xx:xx:xx:xx:xx
where x is a hexadecimal value.
CAUTION! Make sure that the entered WWPN is unique to your particular SAN. Otherwise, a nonfunctioning SAN and data loss could occur.
4. Enter an optional name for the virtual port if you want. You can give the new virtual port any name you want up to 99 characters in length. This name is used as part of the symbolic node name for the vPort.
5. Click Create Virtual Port. A popup notifies you that the virtual port was created. The popup also displays the new virtual port's WWPN. Each virtual port has its own WWPN, but its WWNN is the same as the physical port's WWNN.
NOTE: If you entered a WWPN that is already in use, you are prompted to enter another WWPN.
6. Click OK. The new virtual port is added to the discovery-tree (Figure 4) under the physical port where it was created, and the Number of Virtual Ports field is updated.
NOTE: The Emulex HBA Manager application automatically refreshes its discovery after a virtual port is created. However, targets for a new virtual port might not be discovered during the refresh. Therefore, you must refresh the discovery until the targets appear under the virtual port in the discovery-tree (Figure 4).
NOTE: The Emulex HBA Manager application cannot create or delete virtual ports on VMware ESXi server systems. Although the VMware ESXi server supports NPIV, only VMware management tools can create or delete virtual ports.
To delete a virtual port, perform the following steps:
1. Perform one of the following tasks:
– From the View menu, select Group Adapters by Virtual Ports.
– From the toolbar, click the 
Group Adapters by Virtual Ports button.
2. From the discovery-tree, select the virtual port that you want to delete. The Virtual Port tab appears (Figure 27).
3. Click Remove Virtual Port. The Delete Virtual Port Warning popup appears (Figure 28).
Figure 28: Delete Virtual Port Warning Popup
NOTE: The link on the physical port must be up to delete a virtual port. The Remove Virtual Port button on the Virtual Port tab is disabled if the link is down.
4. Select It is OK to delete the virtual port. and click OK. You are notified that the virtual port is no longer available and that it was removed from the discovery-tree (Figure 4).
7.8 Viewing Fabric Information
The Discovery Information tab (Figure 29) contains information about the selected fabric.
To view fabric discovery information, perform one of the following tasks:
– From the View menu, select Group Adapters by Fabric Address.
– From the toolbar, click the
Group Adapters by Fabric Address button.
The Discovery Information tab is displayed (Figure 29).
Figure 29: Fabric Discovery Information
The following Discovery Information tab fields are displayed:
n Fabrics – The number fabrics identified during discovery.
n FC Functions – The number of FC functions running on the discovered adapters on this host.
n FC Targets – The number of targets discovered on the FC functions on this host.
7.9 Viewing Port Transceiver Information
When you select a port from the discovery-tree (Figure 4), the Transceiver Data tab (Figure 30) enables you to view transceiver information, such as vendor name, serial number, and part number. If the adapter does not support some or all of the transceiver data, the fields display N/A.
To view transceiver information, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree (Figure 4), select the port whose transceiver information you want to view.
3. Select the Transceiver Data tab (Figure 30).
Figure 30: Transceiver Data Tab
The following Transceiver Data tab fields are displayed:
– Vendor – The name of the vendor.
– Identifier/Type – The identifier value that specifies the physical device described by the serial information.
– Ext. Identifier – Additional information about the transceiver.
– Connector – The external optical or electrical cable connector provided as the media interface.
– Wavelength – The nominal transmitter output wavelength at room temperature.
– Speed – The speed, or speeds, at which the selected port can run.
– OUI – The vendor’s OUI, also known as the IEEE Company Identifier for the vendor.
– Date – The vendor’s date code in MM/DD/YY format.
– Serial Number – The serial number provided by the vendor.
– Part Number – The part number provided by the SFP vendor.
– Revision – The vendor revision level.
– Temperature – The internally measured module temperature.
– Supply Voltage – The internally measured supply voltage in the transceiver.
– TX Bias Current – The internally measured transmitted bias current.
– TX Output Power – The measured transmitted output power.
– RX Input Power – The measured received input power.
The VPD tab (Figure 31) displays vital product data (if available) for the selected adapter port, such as the product name, part number, and serial number.
To view VPD information, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree, select the FC function whose VPD information you want to view.
The following VPD tab fields are displayed:
n Product Name – Product information about the selected FC function.
n PN (Part Number) – The adapter's part number.
n SN (Serial Number) – The adapter's serial number.
n Vx – Vendor unique data. V indicates a vendor-specific field. An adapter can have none, one, or more of these fields defined.
NOTE: Some adapters might show additional VPD information, such as EC (EC level), MN (Manufacturer ID), and XY data. Data in the XY field is a vendor-specific hexadecimal dump.
7.11 Viewing Maintenance Information
NOTE: This option is not available in read-only mode.
Use the Maintenance tab (Figure 32) to view firmware information and update adapter firmware. You can also configure BFS and change WWPN and WWNN information for the selected adapter port.
To view firmware information, perform the following steps:
1. Select the Host or Fabric view.
2. Select a port in the discovery-tree.
3. Select the Maintenance tab (Figure 32).
The following Maintenance tab fields are displayed:
– Active Firmware Version – The overall Emulex firmware version for this port.
– Service Processor FW Name – The Emulex firmware name for this port.
– Firmware Version on Flash – The firmware version currently residing in flash on the adapter.
– ULP FW Name – The firmware version running on the ULP processors within the ASIC.
– Adapter Boot Version – Displays one of the following:
l The selected adapter port's boot code version if the boot code is present.
l Disabled if the boot code is disabled.
l Not Present if the boot code is not loaded. If the boot code is not loaded, Enable adapter boot is not visible, and you cannot configure the selected port to boot from SAN.
– Enable adapter boot – Select this option if you want the port to load and execute boot code during system startup.
– Click Configure Boot to configure BFS (not available in read-only mode).
NOTE: Enabling adapter boot only causes the port to load the boot code and run it during system startup. It does not mean that the port boots from SAN. To boot from SAN, the boot type must be enabled. Enable this in the Boot from SAN configuration window for each boot type. (See Section 7.18, Configuring BFS.)
NOTE: The WWN Management area is disabled when FA-PWWN is enabled on an adapter port.
l WWPN – The World Wide Port Name for the selected port.
l WWNN – The World Wide Node Name for the selected port.
l WWPN – Works with the Change WWN button. It displays the WWPN that you assigned for the selected port, but the system must be rebooted for these changes to take effect and appear under the Current listing. See Section 7.16, Changing the WWPN and WWNN, for more information.
l WWNN – Works with the Change WWN button. It displays the WWNN that you assigned for the selected port, but the system must be rebooted for these changes to take effect and appear under the Current listing. See Section 7.16, Changing the WWPN and WWNN, for more information.
7.12 Viewing Target Information
When you select a target associated with an adapter from the discovery-tree (Figure 4), the Target Information tab (Figure 33) displays information associated with that target.
To view target information, perform the following steps:
1. Select the Host, Fabric, or Virtual Port view.
2. In the discovery-tree (Figure 4), select the target whose information you want to view. The Target Information tab appears (Figure 33).
Figure 33: Target Information Tab
The following Target Information tab fields are displayed:
– FC ID – The FC ID for the target; typically assigned by the fabric.
– SCSI Bus Number – The SCSI bus number to which the target is mapped.
– SCSI Target Number – The target's identifier on the SCSI bus.
– Node WWN – A unique 64-bit number, in hexadecimal, for the target node (N_Port or NL_Port).
– Port WWN – A unique 64-bit number, in hexadecimal, for the target port (N_Port or NL_Port).
– OS Device Name – The operating system device name.
When you select a LUN associated with a target from the discovery-tree (Figure 34), the LUN Information tab displays information associated with that LUN.
NOTE: The Refresh LUNs button on the toolbar refreshes only the LUN list for the currently selected target.
On Linux systems, to make LUNs that are newly added to a storage array appear on the host, the following script must be run from the command shell:
This script prevents you from having to reboot. If the host machine is rebooted after the LUN is added to the target array, you do not need to run the script.
To view the LUN information, perform the following steps:
1. Select the Host, Fabric, or Virtual Port view.
2. From the discovery-tree, select a LUN. The LUN Information tab appears (Figure 34).
Figure 34: LUN Information Tab
The following LUN Information tab fields are displayed:
n Vendor/Product Information area:
– Vendor Name – The name of the vendor of the LUN.
– Product ID – The vendor-specific product ID for the LUN.
– Revision – The vendor-specific revision number for the LUN.
– FCP LUN – The FC LUN identifier used by the adapter to communicate with the SCSI FCP LUN.
– SCSI OS LUN – The SCSI identifier used by the operating system to communicate with the SCSI FCP LUN.
– OS Device Name – The name assigned by the operating system to the LUN.
NOTE: LUN capacity information is provided only if the LUN is a mass-storage (disk) device. Other devices, such as tape devices and scanners, do not display capacity.
– Capacity – The capacity of the LUN, in MB.
– Block Size – The length of a logical unit block, in bytes.
n LUN Masking Information area:
– Current Mask Status – Possible states are Masked or Unmasked. See Section 7.15, Masking and Unmasking LUNs (Windows), for more information on LUN masking.
– Enable ExpressLane – See Section 7.15.2, Managing ExpressLane LUNs, for information about the ExpressLane feature.
The Target Mapping tab (Figure 35) enables you to view current target mapping and to set up persistent binding.
To view target mapping, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree, select the FC function whose target mapping information you want to view.
3. Select the Target Mapping tab (Figure 35).
The following Target Mapping tab fields are displayed:
NOTE: For Linux and VMware ESXi, this area is N/A.
– Active Bind Type – WWPN, WWNN, or a D_ID.
– Automapping – The current state of SCSI device automapping: Enabled (default) or Disabled.
– Lists current mapping information for the selected FC function. Shows the WWPN, WWNN, D_ID, and SCSI ID of the currently mapped device. The type can be Auto (automapped target) or PB (mapped from persistent binding).
n Persistent Binding Configuration area:
This table lists persistent binding information for the selected FC function. (This option is not available on VMware ESXi servers being managed through the CIM interface.)
NOTE: For Linux, this area is N/A.
For information on changing settings, see Section 7.14.1.1, Changing Automapping Settings.
– Select how you want to display information in the Persistent Binding Configuration table.
For information on adding a binding, see Section 7.14.1.2, Adding a Persistent Binding.
For information on binding a new target, see Section 7.14.1.3, Binding a Target That Does Not Appear in the Persistent Binding Table.
To remove a single binding, select the binding and click Remove.
To remove all bindings, click Remove All Bindings.
7.14.1 Using Automapping and Persistent Binding (Windows Only)
NOTE: This option is not available in read-only mode.
You can set up persistent binding on remote and local adapters. Global automapping assigns a binding type, target ID, SCSI bus, and SCSI ID to the device. The binding type, SCSI bus, and SCSI ID can 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 during system boot. When you create a persistent binding, the Emulex HBA Manager application tries to make that binding dynamic. However, the binding must meet all of the following criteria to be dynamic:
n 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, the binding cannot be made dynamic, and a reboot is required.
n The target (WWPN, WWNN, or D_ID) specified in the binding request must not be mapped to a SCSI ID. If the desired target is already mapped, a reboot is required.
n The bind type (WWPN, WWNN, or D_ID) specified in the binding request must match the currently active bind type shown in the Current Settings area of the Target Mapping tab. If they do not match, the binding cannot be made active.
7.14.1.1 Changing Automapping Settings
To change automapping settings, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree, select the FC function that you want to set up with persistent binding.
3. Select the Target Mapping tab (Figure 35). All targets are displayed.
4. If you want to make changes, click Change Settings. The Target/LUN Settings dialog appears. You can enable or disable automapping and change the active bind type. Click OK.
NOTE: If NVMe over FC is enabled on the adapter, automapping is automatically set to Enabled, and the bind type is automatically set to WWPN. You cannot change the settings.
5. Click Refresh to see the changes.
6. Reboot the system for the changes to take effect.
7.14.1.2 Adding a Persistent Binding
To add a persistent binding, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree (Figure 4), select the FC function that you want to set up with persistent binding.
3. Select the Target Mapping tab (Figure 35). All targets are displayed. In the Persistent Binding Configuration table, click the target that you want to bind.
4. Click Add Binding. The Add Persistent Binding dialog (Figure 36) is displayed.
Figure 36: Add Persistent Binding Dialog
5. Select the bind type that you want to use (WWPN, WWNN, or D_ID).
6. Select the bus ID and target ID that you want to bind, and click OK.
For targets that are persistently bound, the SCSI_ID column contains the SCSI bus and target numbers that you specified in the Add Persistent Binding dialog. This binding takes effect only after the local machine is rebooted.
For targets that are not persistently bound (in other words, targets that are automapped), the SCI_ID column contains the automapped SCSI bus and target number.
The Type column displays PB for a persistent binding or Auto for an automapped binding.
7.14.1.3 Binding a Target That Does Not Appear in the Persistent Binding Table
NOTE: It is possible to specify a SCSI bus and target that have already been bound to a different FC target. Attempting to bind a target already in the Persistent Binding Configuration table on the Target Mapping tab results in the following error message:
Target already in target list.
To bind a target that does not appear in the Persistent Binding Configuration table on the Target Mapping tab, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree (Figure 4), select the FC function that you want to set up with persistent binding.
3. Select the Target Mapping tab (Figure 35). All targets are displayed.
4. Click Bind New Target. The Bind New Target dialog is displayed (Figure 37).
Figure 37: Bind New Target Dialog
5. Select the type of binding that you want to use, and type the WWPN, WWNN, or D_ID that you want to bind to the target.
6. Select the bus ID and target ID that you want to bind, and click OK.
NOTE: A target does not appear on the target list if automapping is disabled and the target is not already persistently bound.
7.15 Masking and Unmasking LUNs (Windows)
LUN masking refers to whether a LUN is visible to the operating system. A masked LUN is not available and is not visible to the operating system. You can use the LUN Masking tab (Figure 38) to mask or unmask LUNs at the host level.
NOTE: The LUN Masking tab is not shown in the Virtual Port view because LUN masking is not available for virtual ports.
7.15.1 LUN Masking Conventions and Guidelines
LUN icons in the discovery-tree (Figure 4) reflect the live mask state used by the driver. Green LUN icons indicate unmasked LUNs. Gray LUN icons indicate masked LUNs. Red text indicates that a LUN mask has been changed, but not applied (saved).
The following LUN Masking tab information is displayed:
n On Reboot – The On Reboot column shows the mask configuration currently saved to the configuration file on disk (Linux) or to the registry (Windows). Usually, for a specific LUN, the states reported in the On Reboot and Current columns are identical. However, there are times when they do not match. For example, the hbacmd utility can be used to change only the current mask state for a LUN and not change the On Reboot mask state contained in the configuration file.
n Current – The Current column displays the live mask state currently in use by the driver. When you first see the LUN Masking tab, the mask states displayed in the Current column are identical to the mask states for the corresponding LUNs in the discovery-tree (Figure 4).
To change the mask status of a LUN, perform the following steps:
2. From the discovery-tree (Figure 4), select the target whose LUN masking state you want to change. A set of LUNs appears below the selected target.
3. Select the LUN Masking tab (Figure 38). This tab contains a list of the same set of LUNs that appear below the FC target in the discovery-tree (Figure 4).
4. In the LUN list of the LUN Masking tab, select one or more LUNs. The Mask Selected LUN(s), Unmask Selected LUN(s), Unmask All LUNs, Restore, and Apply buttons become active as appropriate. For example, if the LUN is currently unmasked, only the Mask Selected LUN(s) button is active.
5. Change the mask status by clicking Mask Selected LUN(s), Unmask Selected LUN(s), or Unmask All LUNs as appropriate. Mask status changes appear in red text.
NOTE: To return all mask settings to their status before you started this procedure, click Restore before you click Apply. If you click Apply, changes cannot be cancelled by clicking Restore. To unmask all LUNs, click Unmask All LUNs. This button is always active.
6. Click Apply to commit the changes. An informational message confirms that the mask status has changed and the red text changes to black.
7.15.2 Managing ExpressLane LUNs
The Emulex HBA Manager application allows you to set special priority queuing for selected LUNs by making them ExpressLane LUNs (Figure 39). ExpressLane LUN performance is superior to that of regular LUNs. You can enable ExpressLane LUNs attached to both physical and virtual ports.
It is best practice to assign a frame priority to an ExpressLane LUN if the adapter and the switch support it.
ExpressLane LUN assignments persist across reboots.
The following information applies to ExpressLane functionality:
n Masked LUNs cannot be ExpressLane enabled because they are not presented to the host. Conversely, ExpressLane LUNs cannot be masked.
n For Linux operating systems, if ExpressLane LUNs are created, the vPort must be re-created after a system boot because vPorts do not persist across system reboots. If the vPort is re-created with the same WWPN to which the ExpressLane LUN was previously assigned, and the same LUN is then detected, it becomes an ExpressLane LUN again.
Figure 39: LUN Information Tab (ExpressLane LUN with Frame Priority Selection Supported)
To enable an ExpressLane LUN, perform the following steps:
NOTE: ExpressLane must be enabled on the Driver Parameters tab to create an ExpressLane LUN. See Section 7.17, Configuring the Driver Parameters, for more information.
1. Select the Host, Fabric, or Virtual Port view.
2. From the discovery-tree, select a LUN under the adapter on which you want to enable ExpressLane. The LUN Information tab appears (Figure 39).
3. Select the Enable ExpressLane check box.
4. Click Apply. The LUN icon in the discovery-tree changes to the ExpressLane LUN icon.
To disable an ExpressLane LUN, perform the following steps:
1. Select the Host, Fabric, or Virtual Port view.
2. From the discovery-tree, select a LUN under the adapter on which you want to disable ExpressLane. The LUN Information tab appears (Figure 39).
3. Clear the Enable ExpressLane check box to disable the selected LUN.
To disable all ExpressLane LUNs, perform the following steps:
1. Select the Host, Fabric, or Virtual Port view.
2. From the discovery-tree, select a LUN under the adapter on which you want to disable ExpressLane. The LUN Information tab appears (Figure 39).
3. Click Disable ExpressLane on all LUNs.
4. A dialog appears warning you that you are about to disable all ExpressLane LUNS on this target. Click OK.
All ExpressLane LUN icons in the discovery-tree (for the selected adapter port) will change to the regular LUN icon, and any assigned frame priority is set to 0. No data is deleted from these LUNs.
7.15.2.1 Selecting a Frame Priority
If the adapter and switch support it, you can assign a frame priority to the ExpressLane LUN. Switches can provide up to three priority levels; Low, Medium, and High, but they might provide fewer options.
To select a frame priority, perform the following steps:
NOTE: The EnableXLane driver parameter must be enabled on the Driver Parameters tab to set frame priorities. See Section 7.17, Configuring the Driver Parameters, for more information.
1. Select the Host, Fabric, or Virtual Port view.
2. From the discovery-tree, select a LUN under the adapter on which you want to enable ExpressLane. The LUN Information tab appears (Figure 39).
3. Select the Enable ExpressLane check box if it is not already selected. The LUN icon in the discovery-tree changes to the ExpressLane LUN icon.
4. Select a frame priority from the Priority Level drop-down list.
NOTE: If the switch connected to the FC initiator does not support LUN-specific frame priority levels using the Get Fabric Object (GFO) command, you must manually enter the frame priority values in the range of 0 to 127 for all ExpressLane-enabled LUNs as depicted in Figure 40.
Figure 40: LUN Information Tab (Frame Priority Not Supported by the Switch)
If problems occurred when assigning the frame priority, the LUN Information tab displays a message with a suggested solution.
7.16 Changing the WWPN and WWNN
The Maintenance tab (Figure 41) enables you to change the WWPN and the WWNN of a selected FC function. For example, you can use an installed adapter as a standby in case another installed adapter fails. By changing the standby adapter's WWPN or WWNN, it can assume the identity and configuration (for example, driver parameters, and persistent binding settings) of the failed adapter.
Three options exist for referencing WWNs:
n Factory Default WWN – The value that shipped from the factory. This value cannot be changed.
n Non-volatile WWN – A value that is saved in the adapter’s non-volatile flash memory and that survives a reboot or a power cycle.
n Volatile WWN – A temporary value that is saved in volatile memory on the adapter. If volatile WWNs are set, they are used instead of the nonvolatile WWNs.
NOTE: Volatile WWN changes require a warm system reboot to take effect. Volatile WWN changes are lost on systems that power-cycle the adapters during reboot.
NOTE: To avoid address conflicts, do not assign a WWPN with the same WWPN as another FC device on your SAN. The Emulex HBA Manager application checks the WWPN that you specify against all the other detected WWPNs and, if a duplicate is found, an error is displayed and the WWPN is not changed.
ATTENTION: Changing volatile WWNs takes the selected adapter offline. Make sure that this adapter is not controlling a boot device and that all I/O activity on this adapter is stopped before proceeding; otherwise, unexpected behavior or data loss can result.
Considerations When Changing the WWN Configuration
n To avoid address conflicts, do not assign a WWNN or WWPN with the Emulex HBA Manager application if you also use another address management tool.
n The WWPN and WWNN in the Pending Changes list can display n/a instead of None. This display occurs when the remote host is busy processing some critical task and WWN management cannot obtain the current state of WWN management.
n In an environment where preboot management exists, a WWPN or WWNN modified by the Emulex HBA Manager application can be overridden by preboot management, such as industry-standard CLP.
In an environment with CLP, the Emulex HBA Manager application modifies the WWNN or WWPN. The Emulex HBA Manager application requires a reboot to complete the change. After a reboot, the CLP string is sent during the system boot and rewrites the WWNN or WWPN.
In an environment without CLP, the Emulex HBA Manager application modifies the WWNN or WWPN. The Emulex HBA Manager application requires a reboot to complete the change. The system boots, and the WWNN or WWPN modified by the Emulex HBA Manager application is used.
n On a system where the Emulex HBA Manager application is installed, make sure that the port numbers configured during the installation are open and dedicated to the application only. No other service should be listening on this port.
n The FA-PWWN firmware parameter must be disabled to change the WWN. See Section 7.3.2, Enabling and Disabling FA-PWWN, for information about disabling FA-PWWN.
To change an FC function’s WWPN or WWNN, perform the following steps:
1. Perform one of the following tasks:
– From the View menu, select Group Adapters by Host Name.
– From the toolbar, click the 
Group Adapters by Host Name button.
– From the Host Grouping menu, select Group Adapter by Fabric Names.
2. In the discovery-tree, select the FC function that you want to change.
3. Select the Maintenance tab (Figure 41).
4. Click Change WWN. The popup in Figure 42 appears.
Figure 42: Warning About Changing the WWN
5. Click Yes. The Emulex HBA Manager Change WWN Configuration dialog appears (Figure 43).
Figure 43: Emulex HBA Manager Change WWN Configuration Dialog
6. Perform one of the following tasks:
– Click Get Factory Default WWNs to load the settings that were assigned to the FC function when the adapter was manufactured to the New WWPN and New WWNN fields. These values can then be modified if desired and saved as volatile or non-volatile WWNs.
– Click Get Non-volatile WWNs to load the current non-volatile WWN settings to the New WWPN and New WWNN fields. These values can then be modified and saved to volatile or non-volatile memory, and then they can then be modified and saved as volatile or non-volatile WWNs.
7. Select Write changes to volatile memory for temporary use to save the new WWPN and new WWNN settings as volatile WWNs. If Write changes to volatile memory for temporary use is cleared, the new WWPN and new WWNN settings are saved as non-volatile WWNs.
NOTE: If the adapter or firmware does not support volatile WWNs, the Write changes to volatile memory for temporary use check box is dimmed.
8. Click OK. After checking for a duplicate WWPN, the new WWPN and new WWNN values are saved for volatile or
non-volatile use. The new WWPN and WWNN appear in the Pending Changes section in the WWN Management area of the Maintenance tab until the system is rebooted.
9. Reboot the system for the changes to take effect. After rebooting, the changes are applied and appear in the Current area of the Maintenance dialog.
NOTE: This option is not available in read-only mode.
The Emulex HBA Manager application allows you to change the adapter port representation in the discovery-tree.
For example, you might want to identify a particular FC port with the role it supports, such as accounting or engineering. Use any characters that you want for names, and names can be up to 255 characters in length. You can also revert to the adapter's default name.
NOTE: Although you can change the FC port’s displayed name from the default WWPN, the change occurs in the discovery-tree (Figure 4) only. The port’s WWPN is still active; it is replaced for display purposes with the name that you enter. For example, the Port WWN field of the Port Information tab is not changed. Also, any changes you make to the names in your discovery-tree are seen only by you; users running the Emulex HBA Manager application on another host do not see your name changes.
To change the name of an FC port, perform the following steps:
1. From the discovery-tree (Figure 4), select the port whose name you want to change by performing one of the following tasks:
– Select Edit Name from the Port menu.
– From the discovery-tree, right-click the port whose name you want to change and select Change Name.
2. Edit the name in the discovery-tree.
To use the FC port’s default name, perform the following steps:
1. From the discovery-tree (Figure 4), select the FC port whose name you want to change.
2. Perform one of the following tasks:
– Select Use Default Name from the Port menu.
– From the discovery-tree, right-click the port whose name you want to change and select Restore Default Name.
7.16.2 Resetting the FC Functions
You can reset remote and local functions.
CAUTION! Do not reset functions while copying or writing files. This action could result in data loss.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
To reset the FC function, perform the following steps:
1. In the discovery-tree (Figure 4), select the FC function that you want to reset.
2. Perform one of the following tasks:
– From the Port menu, select Reset Port.
– From the toolbar, click the 
Reset button.
The Reset FC Port popup appears (Figure 44).
Figure 44: Reset FC Port Popup
3. Click Yes to perform the reset.
The reset can require several seconds to complete. During the reset, the status bar shows Reset in progress. When the reset is finished, the status bar shows Reset Completed.
7.17 Configuring the Driver Parameters
NOTE: This option is not available in read-only mode.
The Emulex HBA Manager application displays available driver parameters along with their defaults and minimum and maximum settings. A description of the selected parameter is also provided. This section contains information that you must be aware of when working with driver parameters. For a more detailed description of specific driver parameters, refer to the appropriate Emulex driver user guide.
NOTE: In Linux, you can also specify parameters when loading the driver manually. Refer to the appropriate driver user guide for instructions.
7.17.1 Activation Requirements
A parameter has one of the following activation requirements:
n Dynamic – Takes effect while the system is running.
n Reset – Requires a reset from the utility before the change takes effect.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
n Reboot – Requires a reboot of the entire machine before the change takes effect. In this case, you are prompted to perform a reboot when you exit the utility.
7.17.2 Host Driver Parameters Tab
The Host Driver Parameters tab (Figure 45) enables you to view and edit the adapter driver parameter settings contained in a specific host. The host driver parameters are global values and apply to all adapters in that host unless they are overridden by parameters assigned to a specific adapter using the adapter Driver Parameters tab. For each parameter, the tab shows the current value, the range of acceptable values, the default value, and the activation requirements.
ATTENTION: The Emulex HBA Manager application cannot retrieve data from an offline adapter or port and will display incorrect information for that adapter or port. Adapters and ports must be online for the application to display accurate information.
For information on changing parameters for a single adapter, see Section 7.17.3, Setting the Driver Parameters. For information on changing parameters for the host, see Section 7.17.3.5, Setting the Driver Parameters for All FC Functions in a Host.
NOTE: Setting a host-level driver parameter for a specific port overrides all port-level driver parameters set for the port.
Figure 45: Host Driver Parameters Tab
The following Host Driver Parameters tab fields are displayed:
n Installed Driver Type – The current drivers installed on this host. If more than one driver type is installed, the Installed Driver Type drop-down list displays all driver types that are installed on the adapters in the host and enables you to select the particular driver type to configure.
n Adapter Parameter table – A list of adapter driver parameters for the selected driver type and their current values.
n Modify Adapter Parameter area:
– Adapter-specific information is displayed in this area, which includes the value, range, default, activation requirements, and description.
n Make all changes temporary (if possible) – If the parameter is dynamic, check this box to make the change temporary. The parameter reverts to its last permanent setting when the system is rebooted.
7.17.3 Setting the Driver Parameters
The Driver Parameters tab for FC functions and hosts enables you to modify driver parameters for a specific FC function or all FC functions in a host.
For example, if you select a host in the discovery-tree (Figure 4), you can globally change the parameters for all FC functions in that host. If you select an FC function in the discovery-tree, you can change the parameters for only that FC function.
For each parameter, the Driver Parameters tab shows the current value, the range of acceptable values, the default value, and the activation requirement. You can also restore parameters to their default settings.
You can apply driver parameters for one FC function to other FC functions in the system using the Driver Parameters tab, thereby simplifying the configuration of multiple adapters. See Section 7.17.4, Creating a Batch Mode Driver Parameters File, for more information.
NOTE: The Linux 2.6 kernel supports setting only some of the driver parameters for individual FC functions. Some driver parameters must be applied to all FC functions contained in the host. Refer to the Emulex Driver for Linux User Guide for more information.
7.17.3.1 Setting the Driver Parameters for a Single FC Function
NOTE: Setting a host-level driver parameter for a specific port overrides all port-level driver settings for that parameter.
To change the driver parameters for a single FC function, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree (Figure 4), select the FC function that you want to change.
3. Select the Driver Parameters tab (Figure 46). The parameter values for the selected FC function are displayed.
NOTE: The LinkSpeed driver parameter (Windows) or link-speed driver parameter (Linux) are not shown if the adapter supports forced link speeds. The link speed is configured using the Firmware Parameters tab. See Section 7.3, Viewing Firmware Parameters, for more information.
Figure 46: Driver Parameters Tab
4. 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/decimal format as the current value or select a value from the list. If the current value is in hexadecimal format, it is prefaced by 0x (for example, 0x2d). You can enter a new hexadecimal value without the 0x. For example, if you enter ff10, this value is interpreted and displayed as 0xff10.
6. If you want the change to be temporary (causing the parameter to revert to its last permanent setting when the system is rebooted), select the Make change temporary check box. This option is available only for dynamic parameters.
7. If you are making changes to multiple parameters, and you want all the changes to be temporary, select Make all changes temporary (if possible). This setting overrides the Make change temporary setting. Only dynamic parameters can be made temporary.
7.17.3.2 Restoring All Parameters to Their Earlier Values
If you changed parameters, but did not click Apply in the Driver Parameters tab (Figure 46) and you want to restore the parameters to their last saved values, click Restore.
7.17.3.3 Resetting All Default Values
To reset all parameter values to their default (factory) values, click Defaults in the Driver Parameters tab (Figure 46).
7.17.3.4 Setting an Adapter Parameter Value to the Host Adapter Parameter Value
To set an adapter parameter value to the corresponding host parameter value, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree (Figure 4), select the adapter port.
3. Select the Driver Parameters tab (Figure 46).
4. Click Globals. All parameter values are now the same as the global, or host, values.
5. To apply the global values, click Apply.
7.17.3.5 Setting the Driver Parameters for All FC Functions in a Host
NOTE: Setting a host-level driver parameter for a specific port overrides all port-level driver parameters set for the port.
To change the driver parameters for all FC functions installed in a host, perform the following steps:
1. Perform one of the following tasks:
– From the View menu, select Group Adapters by Host Name.
– From the toolbar, click the 
Group Adapters by Host Name button.
2. In the discovery-tree, click the host whose adapter driver parameters you want to change.
3. Select the Host Driver Parameters tab (Figure 47). If adapters with different driver types are installed, the Installed Driver Type menu shows a list of all driver types and driver versions that are installed. Select the driver whose parameters you want to change. This menu does not appear if all the adapters are using the same driver.
4. Click the parameter that you want to change. A description of the parameter appears on the right side of the tab.
Figure 47: Host Driver Parameters Tab – Host Selected
5. Enter a new value in the Value field in decimal or hexadecimal format, depending on how the current value is presented. If the value is in hexadecimal format, it is prefaced by 0x (for example, 0x2d).
6. To make a change temporary (the parameter reverts to its last permanent setting when the system is rebooted), select Make change temporary. This option is available only for dynamic parameters.
7. To make changes to multiple parameters, select Make all changes temporary (if possible). Only dynamic parameters can be made temporary.
7.17.3.6 Changing Nondynamic Parameter Values (Linux)
To change nondynamic parameter values for Linux, perform the following steps:
1. Navigate to the /usr/sbin/ocmanager directory, and run the script to stop the Emulex HBA Manager application processes by typing the following command:
2. Stop all I/O to FC-attached devices.
3. Unload the FC driver. Type the following command:
4. Reload the driver. Type the following command:
5. Start the elxhbamgr service (remote service). Type the following command:
The Emulex HBA Manager application discovery service starts automatically when you start the application.
NOTE: For changes to persist after a reboot, you must create a new ramdisk image. Refer to the Emulex Drivers for Linux User Guide for more information.
7.17.4 Creating a Batch Mode Driver Parameters File
NOTE: This option is not available in read-only mode.
You can apply driver parameters for one FC function to other FC functions in the system using the Driver Parameters tab. When you save the driver parameters for an adapter, you create a.dpv file that contains parameters for that adapter. After you create the.dpv file, the Emulex HBA Manager application enables you to assign the .dpv file parameters to multiple adapters in the system.
To create the .dpv file, perform the following steps:
1. Select the Host or Fabric view.
2. Select the FC function whose parameters you want to apply to other FC functions from the discovery-tree (Figure 4).
3. Select the Driver Parameters tab (Figure 46).
5. After you define the parameters for the selected adapter, click Apply.
6. Click Save. The Save Driver Parameters dialog appears (Figure 48). You can save the file to a different directory or change its name.
Each definition is saved in a comma-delimited file with the following format:
<parameter-name>=<parameter-value>
The file is saved in the Emulex repository directory.
– In Windows: \Program Files\Emulex\Util\Emulex Repository
– In Linux: /usr/sbin/ocmanager/RMRepository
– In VMware ESXi: /tmp/RMRepository
NOTE: Host driver parameters and persistent binding settings cannot be saved.
The Emulex HBA Manager application then uses the Batch Driver Parameter Update function to apply these saved settings to all compatible adapters on the SAN.
Figure 48: Save Driver Parameters Dialog
7. Choose whether to save all parameters or only those parameters whose current values differ from their corresponding default values.
A list of the saved parameters and their current values appear in the Saved Parameters list.
7.17.4.1 Assigning Batch Mode Parameters
To assign batch mode parameters to adapters, perform the following steps:
1. From the Batch menu, select Update Driver Parameters. (You do not need to select any discovery-tree [Figure 4] elements at this time.)
2. When the Batch Driver Parameter Update dialog appears (Figure 49), click Browse.
Figure 49: Batch Driver Parameter Update Dialog
3. Select the file that you want to use and click OK. A dialog notifies you that the Emulex HBA Manager application is searching for compatible adapters.
After compatible FC functions are found, the Driver Parameter File field of the Batch Driver Parameter Update dialog displays the selected file's path. The Supported Driver Type field displays the selected driver. The set of compatible adapters is displayed in the dialog’s discovery-tree.
Using the Display Options settings, you can choose how adapters are displayed in the discovery-tree. Select Group by Host to display adapters in a host-centric view. Select Group by Fabric to display hosts in a fabric-centric view with their fabric addresses. The WWPN and host name for each available FC function is displayed under its respective fabric.
You can also display host groups by selecting Show Host Groups. To display a particular host group, select that group from the Host Group list.
You can select or clear the host, adapter, and FC functions entries in the discovery-tree. Selecting an adapter selects or removes all FC functions on that adapter. Selecting a host selects or removes all eligible adapters for that host.
4. Make your selections, and click Start Updates. The Batch Driver Parameter Update dialog (Figure 49) shows the current status of the update. When the update is finished, a final summary shows the number of FC functions that were successfully processed and the number of FC functions for which one or more parameter updates failed.
You can click Save Log File to save a report of the update. If you change any parameter settings, click Reset Display to refresh the dialog.
You can use the Emulex HBA Manager application to configure a system to boot from an attached SCSI FCP LUN. BFS allows servers on a storage network to boot their operating systems directly from a SAN storage device, typically identified by its WWPN and a LUN located on the device. By extending the server system BIOS, BFS functionality is provided by the BootBIOS contained on an Emulex adapter in the server. When properly configured, the adapter then persistently directs the server to boot from a LUN on the SAN as if it were a local disk.
NOTE: BFS is not supported through the CIM interface.
Using the Maintenance tab, you can enable, disable, or configure BFS for x86 BootBIOS and EFIBoot.
The following information applies to boot types:
n x86 BootBIOS works with the existing BIOS on x64 and x86 systems.
n EFIBoot works with x64-based systems and provides 64-bit system boot capability through the use of the EFI shell.
n When x86 settings are changed, the same changes are also made to EFI. Conversely, when EFI settings are changed, the changes are also made to x86.
Broadcom provides Universal Boot code in the firmware image. Universal Boot code contains multiple types of boot code that provide multiplatform support for BFS. Universal Boot code transparently determines your system platform type and automatically runs the proper boot code image in the adapter. This code image resides in the adapter flash memory, allowing easier adapter portability and configuration between servers.
The adapters store the boot configuration data for each of these boot types.
NOTE: BFS configuration does not affect current system operation. The changes take effect only upon reboot if you have configured BFS correctly.
SCSI FCP Boot Device Parameters
The boot LUN for x86 BootBIOS and EFIBoot is in the range of 0 to 255. EFIBoot also supports an 8-byte LUN, which you can use instead of the single-byte LUN. You must select which LUN type to configure.
n You must boot the host to configure BFS with the Emulex HBA Manager application.
n You must work from a running host that supports the Emulex HBA Manager application. Often, this host has booted from a direct-attached drive. With the Emulex HBA Manager application, you can configure a direct boot host to boot from a SAN. You can modify an existing BFS configuration or configure BFS on an adapter for installation in another host so that it can boot from SAN.
n You must know the boot code type that the system supports; the Emulex HBA Manager application cannot detect this information. You can configure any boot type, but if the system does not support that type, it cannot boot from SAN.
n One of the following adapter drivers must be installed:
– Windows: Storport Miniport driver
To configure BFS, perform the following steps:
1. Select the Host or Fabric view.
2. In the discovery-tree (Figure 4), click the FC adapter function on which you want to enable BFS.
3. Select the Maintenance tab (Figure 32), select Enable adapter boot, and click Configure Boot. The Boot from SAN Configuration dialog, which varies for each boot type, appears. Figure 50 displays the Boot from SAN Configuration dialog for the EFIBoot boot type. Figure 51 displays the Boot from SAN Configuration dialog for the x86 BootBIOS boot type.
NOTE: The Configure Boot button is dimmed if Enable adapter boot is not selected.
Figure 50: Boot from SAN Configuration Dialog (EFIBoot)
Figure 51: Boot from SAN Configuration Dialog (x86 BootBIOS)
4. Verify that the Adapter field contains the WWPN of the FC function, and ensure that you configure the correct adapter FC function.
5. From the Boot Type menu, select X86 or EFI.
NOTE: If you modified the settings for the current boot type and then change to a new boot type, a message reminds you to save the current settings before changing to the new boot type.
6. Select Enable Boot from SAN, and select the topology (available only when supported by the adapter).
Possible topology options are:
7. To configure autoscan, spinup delay, and other advanced settings, see Section 7.18.1, Configuring BFS Advanced Settings.
8. For EFIBoot, you can configure NVMe boot parameters. See Section 7.18.2, Configuring NVMe BFS Settings.
9. For EFIBoot, you can select Brocade Fabric Assigned Boot LUN (FABL). You are prompted to reboot after enabling FABL.
NOTE: Switch configuration is required when using FABL. Refer to the Brocade switch manual for configuration details.
NOTE: Boot LUNs allocated using FABL will override the boot device configuration currently defined for the port (Figure 50).
10. Select one or more boot devices.
11. Perform one of the following tasks on the Boot from SAN Configuration dialog (Figure 50 or Figure 51):
– Select Target WWPN, type the desired WWPN, and click OK.
– Select Target D_ID (hex), type the desired D_ID, and click OK (not available for EFIBoot).
– Select Target LUN, type the desired LUN, and click OK.
For EFIBoot, enter the LUN value in big-endian order (most-significant byte, or big endian, first), and enter all 16 characters, including leading zeros, for the target WWPN. Type an 8-byte LUN (hexadecimal) target ID for the LUN.
– Click Select From List, select the target from a list of discovered LUNs (if available), and click OK on the Select Boot Device dialog (Figure 52). You can manually enter the target and LUN from the Boot from SAN Configuration dialog; however, it is easier to select an existing LUN from the Select Boot Device dialog. The Emulex HBA Manager application attempts to update the boot parameters. If the update is successful, a popup displays a confirmation message. Click OK.
Figure 52: Select Boot Device Window
12. On the Boot from SAN Configuration dialog (Figure 50), click Apply to save your changes but leave the dialog open, or click OK to apply the changes and close the dialog.
NOTE: Click Close to close the Boot from SAN Configuration dialog without saving your changes. A message prompts you to discard your changes.
13. If you changed x86 or EFIBoot settings, the following popup appears. Click OK.
14. Reboot the system for your changes to take effect.
7.18.1 Configuring BFS Advanced Settings
The Emulex HBA Manager application provides advanced settings for each boot type. From the Boot from SAN Configuration dialog (Figure 50), click Advanced Settings. A dialog specific to the chosen boot type appears and allows you to enable options, such as spinup delay and autoscan.
If you make changes, you must click OK to save the changes and close the dialog. You can click Cancel and close the dialog without saving the changes.
NOTE: If you do not enter the advanced settings and the configuration for the boot type is new, default values are used. The default settings are given with descriptions of the Advanced Adapter Settings dialogs in the following sections.
7.18.1.1 x86 Boot Advanced Adapter Settings
Use the x86 Boot Advanced Adapter Settings dialog (Figure 53) to configure advanced settings for the selected x86 adapter. All selections are cleared by default. All changes require a reboot to activate.
NOTE: When x86 settings are changed, the same changes are also made to EFI. Conversely, when EFI settings are changed, the changes are also made to x86.
Figure 53: x86 Boot Advanced Adapter Settings Dialog
The following x86 Boot Advanced Adapter Settings fields are displayed:
n Enable start unit command – Issues the SCSI start unit command.
n Enable EDD 3.0 – Enables the EDD option, which shows the path to the boot device. (This option is available on Intel Itanium servers only.)
n Enable spinup delay – If at least one boot device has been defined, and the spinup delay is enabled, the BIOS searches for the first available boot device.
– If a boot device is present, the BIOS boots from it immediately.
– If a boot device is not ready, the BIOS waits for the spinup delay and, for up to 3 additional minutes, continues the boot scanning algorithm to find another multiboot device.
– If no boot devices have been defined and autoscan is enabled, the BIOS waits for 5 minutes before scanning for devices.
– In a private loop, the BIOS attempts to boot from the lowest target AL_PA that it finds.
– In an attached fabric, the BIOS attempts to boot from the first target found in the NameServer data.
NOTE: The default topology is auto topology with loop first. Change this topology setting, if necessary, before configuring boot devices.
n Enable environment variable – Sets the boot controller order if the system supports the environment variable.
n Enable auto boot sector – Automatically defines the boot sector of the target disk for the migration boot process, which applies only to HPE MSA1000 arrays. If no partition exists on the target, the default boot sector format is
63 sectors.
n Auto Scan – With autoscan enabled, the first device issues a name server inquiry. The boot device is the first D_ID, LUN 0, or non-LUN 0 device returned, depending on the option that you select. Only this device is the boot device, and it is the only device exported to the multiboot menu, which appears at boot time. Autoscan is available only if none of the eight boot entries is configured to boot through D_ID or WWPN. Select one of the following options:
n PLOGI Retry Timer (ms) – Sets the interval for the PLOGI retry timer. This option is especially useful for
Tachyon-based RAID arrays. On very rare occasions, a Tachyon-based RAID array resets itself, and the port goes offline temporarily in the loop. When the port comes back online, the PLOGI retry interval scans the loop to discover this device. Select one of the following values:
7.18.1.2 EFIBoot Advanced Adapter Settings
Use the EFIBoot Advanced Adapter Settings dialog (Figure 54) to configure the advanced settings for the selected EFIBoot adapter.
NOTE: When x86 settings are changed, the same changes are also made to EFI. Conversely, when EFI settings are changed, the changes are also made to x86.
Figure 54: EFIBoot Advanced Adapter Settings Dialog
EFIBoot Advanced Adapter Settings field definitions follow:
n Boot Target Scan – This option is available only if none of the eight boot entries are configured to boot by using D_ID or WWPN.
– NVRAM Targets (default) – Discovers only LUNs that are saved to the adapter’s NVRAM.
– Discovered Targets – Discovers all devices that are attached to the port. Discovery can take a long time on large SANs.
– EFIBootFCScanLevel: NVRAM Targets and EFIBootFCScanLevel: Discovered Targets – Allows third-party software to toggle between a boot path from NVRAM and a boot path from discovered targets by manipulating an EFI system NVRAM variable.
n Maximum LUNs per Target – Sets the maximum number of LUNs that are polled during device discovery. The range is 1 to 4096. The default is 256.
n PLOGI Retry Timer – Sets the interval for the PLOGI retry timer. This option is especially useful for Tachyon-based RAID arrays. Under rare occasions, a Tachyon-based RAID array resets itself and the port goes offline temporarily in the loop. When the port comes online again, the PLOGI retry interval scans the loop to discover this device.
7.18.2 Configuring NVMe BFS Settings
You can configure NVMe settings for EFIBoot adapters. From the Boot from SAN Configuration dialog (Figure 50), click NVMe Boot Parameters. The NVMe Boot Device Parameters dialog (Figure 55) allows you to define the Namespace ID, Subsystem NQN, NVMe WWPN, and the NVMe WWNN.
The following information applies to NVMe:
n NVMe configuration is supported only on Windows, Linux, and VMware operating systems.
n NVMe BFS configuration is supported only on EFIBoot.
Figure 55: NVMe Boot Device Parameters Dialog
NVMe Boot Device Parameter field definitions follow:
n Namespace ID – The NVMe controller's unique identifier for the namespace.
n Subsystem NQN – This parameter sets the NVMe SubsystemNQN.
n NVMe WWPN – This parameter sets the WWPN of the NVMe target.
n NVMe WWNN – This parameter sets the WWNN of the NVMe target.
7.19 Using FC-SP-2 DH-CHAP Authentication
Use the DH-CHAP tab to view and configure FC-SP-2 DH-CHAP authentication between an adapter and a switch. FC-SP-2 DH-CHAP authentication is disabled by default.
The following information applies to DH_CHAP authentication:
n BFS is not supported when DH-CHAP authentication is enabled.
n DH-CHAP is available only for physical ports, not for virtual ports.
n The authentication driver parameters are available only on local hosts. This parameter is not displayed for any remote hosts.
n DH-CHAP is not supported on FA-PWWN ports.
n DH-CHAP cannot be enabled simultaneously with Dynamic D_Port. You must first disable Dynamic D_Port to enable DH-CHAP.
NOTE: Authentication must be enabled at the driver level. Enable the lpfc_enable_auth parameter for Linux, the EnableAuth parameter for Windows, or the lpfc_enable_auth parameter for VMware before attempting to configure DH-CHAP. See Section 7.17, Configuring the Driver Parameters, for instructions on changing driver parameters. Authentication is disabled by default.
To enable DH-CHAP on Linux systems, the lpfc_enable_auth parameter must be passed to the driver by typing the following command:
insmod lpfc.ko lpfc_enable_auth=1
For a permanent configuration on Linux systems that will persist across system reboots, create the /etc/modprobe.d/lpfc.conf file, and place the following line into it:
options lpfc lpfc_enable_auth=1
The DH-CHAP tab (Figure 56) enables you to configure authentication.
The following DH-CHAP tab fields and buttons are displayed:
n Adapter-Level Configuration area:
– Click Delete Authentication For All Ports to permanently delete the entire authentication configuration for all the ports on the adapter.
n Port-Level Configuration area:
– Click Entity List to see the list of entity pairs with a saved authentication configuration.
– Mode – The mode of operation. Three modes are available:
l Enabled – The FC function initiates authentication after issuing a FLOGI to the switch. If the connecting device does not support DH-CHAP authentication, the software still continues with the rest of the initialization sequence.
l Passive – The FC function does not initiate authentication but participates in the authentication process if the connecting device initiates an authentication request.
l Disabled – The FC function does not initiate authentication or participate in the authentication process if it is initiated by a connecting device. This is the default mode.
– Timeout – During the DH-CHAP protocol exchange, if the switch does not receive the expected DH-CHAP message within the specified time interval, authentication failure is assumed (no authentication is performed). The time value ranges from 20 to 999 seconds, and the default is 45 seconds.
– Bi-directional – If this setting is enabled, the FC driver supports authentication initiated by either the switch or the FC function. If this setting is disabled, the driver supports only FC-function-initiated authentication. The remote password must be configured to enable this setting. See Section 7.19.3, Setting or Changing Secrets, for instructions.
– Re-authenticate – If this setting is enabled, the FC driver can periodically initiate authentication.
– Re-auth Interval – The value, in minutes, that the FC driver uses to periodically re-initiate authentication. Valid interval ranges are 10 to 3600 minutes. The default is 300 minutes.
– DH Priority – The priority of the five supported DH groups (the Null group and groups 1, 2, 3, and 4) that the FC driver presents during the DH-CHAP authentication negotiation with the switch.
– Hash Priority – The priority of the supported hash algorithms (MD5 and SHA1) that the FC driver presents during the DH-CHAP authentication negotiation with the switch (the default is MD5 first, then SHA1).
n Restore – Click this button to return parameters to their previous settings.
n Defaults – Click this button to return parameters to their default settings.
n Apply – Click this button to apply the new parameter settings before initiating authentication.
NOTE: Clicking Defaults removes all current configuration settings, including port secrets and this switch/target connection.
n Parameter Description / General Help area:
– This area contains a brief description of the selected parameter and the options available for the parameter.
– This area displays the current authentication state. Possible states are Not Authenticated, Authentication In Progress, Authentication Success, Authentication Active, and Authentication Failed.
n Initiate Authentication – To perform immediate authentication, click this button after configuring parameters in the Configuration area and clicking the Apply button.
n Set Secret – Click this button to set a new local or remote secret in ASCII or hexadecimal (binary). See Section 7.19.3, Setting or Changing Secrets, for instructions.
After DH-CHAP has been activated and configured, manually initiate authentication per adapter by clicking Initiate Authentication. A FLOGI can also be caused by bringing the link between the switch and the adapter down and then up (not available in read-only mode).
7.19.1 Deleting Authentication for All Ports
This section describes how to delete the authentication configuration, including secrets, from the adapter flash memory. You must reload the driver or reboot the system to activate the new driver settings.
NOTE: The driver authentication parameter lpfc_enable_auth (Linux), lpfc_enable_auth (VMware), or EnableAuth (Windows) must be disabled before deleting authentication for all ports. See Section 7.17, Configuring the Driver Parameters, for instructions on changing driver parameters.
To delete authentication for all ports, perform the following steps:
1. In the discovery-tree (Figure 4), select the adapter port whose authentication you want to delete.
2. Select the DH-CHAP tab (Figure 56).
3. Click Delete Authentication For All Ports.
7.19.2 Viewing Saved Authentication Configuration Entities
The Entity List displays a list of entity pairs that have a saved authentication configuration. The list might include entity pairs for authentication configurations that are no longer valid or configurable. For example, the list would contain an entity pair whose configuration becomes obsolete and invalid after a port WWN change.
To view saved authentication configuration entities, perform the following steps:
1. In the discovery-tree (Figure 4), select the adapter port whose authentication configuration entities you want to view.
2. Select the DH-CHAP tab (Figure 56).
3. Click Entity List. The Authentication Entity List dialog appears (Figure 57).
Figure 57: Authentication Entity List Dialog
7.19.2.1 Deleting Authentication Configuration Entities
You can delete all invalid entities or particular entities.
To delete saved authentication configuration entities, perform the following steps:
1. In the discovery-tree (Figure 4), select the adapter port whose authentication configuration entities you want to delete.
2. Select the DH-CHAP tab (Figure 56).
3. Click Entity List. The Authentication Entity List dialog appears (Figure 57).
4. Click Delete Invalid Entries to remove all invalid entities (red), or select the entities that you want to delete and click Delete.
7.19.3 Setting or Changing Secrets
You can change or set the local or remote secret (password). The local secret is typically used by the driver when the adapter initiates authentication to the switch. The remote secret is used by the driver if the switch attempts to authenticate with the adapter. Bi-directional authentication requires the remote secret.
To set or change secrets, perform the following steps:
1. In the discovery-tree (Figure 4), select the adapter port whose secrets you want to set or change.
2. Select the DH-CHAP tab (Figure 56).
3. Click Set Secret. The Set Secret dialog appears (Figure 58).
4. Choose Set Local Secret or Set Remote Secret.
– The FC driver uses the local password if the adapter initiates authentication to the switch (typical use).
– The FC driver uses the remote password if the switch authenticates with the adapter. This situation is possible only when Bi-Directional is enabled on the DH-CHAP tab (Figure 56).
5. To see the password characters entered in the dialog, select the Show Characters check box.
6. Enter the new secret. Secrets must contain at least 12 bytes, and local and remote secrets must be different.
8. Select Alphanumeric or Hex (binary) format.
CAUTION! Do not forget the secret after one has been assigned. After a secret is assigned to an adapter, subsequent DH-CHAP configuration settings for that adapter, including the default configuration or new secrets, require you to enter the existing secret to validate your request. No further changes can be made without the secret.
NOTE: Click Help on the Set Secret dialog for assistance with secrets.
7.19.4 Changing the Authentication Configuration
NOTE: You can configure DH-CHAP only on the local host.
To view or change the authentication configuration, perform the following steps:
1. In the discovery-tree (Figure 4), select the adapter port whose configuration you want to view or change.
2. Select the DH-CHAP tab (Figure 56).
If the fields on this tab are dimmed, either authentication has not been enabled at the driver level, or the local secret has not been set.
– For instructions on enabling the driver authentication parameter lpfc_enable_auth (Linux), lpfc_enable_auth (VMware), or EnableAuth (Windows), see Section 7.17, Configuring the Driver Parameters.
– For instructions on setting the local secret, see Section 7.19.3, Setting or Changing Secrets.
3. Change the configuration values that you want.
NOTE: If you click Apply, changes cannot be canceled.
To return settings to the status before you started this procedure, click Restore before you click Apply.
To return all settings to the default configuration, click Defaults.
CAUTION! Returning all settings to the default configuration also resets any passwords to NULL.
7.20 Guest Operating System Discovery and Management from the Base Host Operating System
When the Emulex HBA Manager application is installed on a guest operating system, the guest operating system is discovered by the Emulex HBA Manager application running on the host operating system. The guest operating system host appears as a remote host in the discovery-tree (Figure 59).
Figure 59: Emulex HBA Manager Application Running on the Base Host after Discovering the Guest Host
