™ OneCommand Manager Application Version 5.2 User Manual P006979-01A Rev.
Copyright © 2003-2011 Emulex. All rights reserved worldwide. No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex. Information furnished by Emulex is believed to be accurate and reliable. However, no responsibility is assumed by Emulex for its use; or for any infringements of patents or other rights of third parties which may result from its use.
Introduction.............................................................................................................. 1 Supported Features by Operating System......................................................... 2 Known Issues .................................................................................................... 4 Printing Help Information ...................................................................................
The OneCommand Manager Application Window Element Definitions ........... 24 The Menu Bar ........................................................................................... 25 The Toolbar ............................................................................................... 25 The Toolbar Buttons .................................................................................. 25 The Discovery-Tree...................................................................................
Viewing NIC Port Information .................................................................... 65 Viewing Physical Port Information (OneConnect Adapters Only) .................... 67 Viewing Port Statistics ..................................................................................... 68 Viewing FC/FCoE Port Statistics ............................................................... 68 Viewing iSCSI Statistics ............................................................................
Configuring DCB Parameters for iSCSI Adapter Ports ............................ 115 Configuring DCB Parameters for NIC-Only Adapter Ports ...................... 119 Configuring FCoE Initialization Protocol (FIP) for FCoE Adapters ................. 123 Managing Ports ................................................................................................... 124 Changing Adapter Port Names (FC Ports Only) ............................................ 124 Resetting Adapter Ports (FC/FCoE Ports Only)....
Running a Quick Test .............................................................................. 170 Running a Power On Self Test (POST) ................................................... 171 Using Beaconing ..................................................................................... 171 Creating Diagnostic Dumps..................................................................... 171 Running Advanced Diagnostic Tests .......................................................
InitiateAuth .............................................................................................. 197 SetAuthConfig ......................................................................................... 198 SetPassword ........................................................................................... 198 Boot Commands............................................................................................ 199 EnableBootCode ...........................................................
AddRouteTableEntry ............................................................................... 223 AddTarget................................................................................................ 223 AddTargetPortal ...................................................................................... 224 CleariSNSServer..................................................................................... 226 DelARPTableEntry ......................................................................
PersistentBinding .................................................................................... 247 RemoveAllPersistentBinding ................................................................... 247 RemovePersistentBinding ....................................................................... 247 SetBindingSupport .................................................................................. 248 SetPersistentBinding...............................................................................
Introduction The Emulex® OneCommandTM Manager application is a comprehensive management utility for Emulex LightPulse® host bus adapters (HBAs) and OneConnectTM universal converged network adapters (UCNAs) that provides a powerful, centralized adapter management suite. Adapter management includes discovery, reporting and management of local and remote adapters from a single console anywhere in the Storage Area Network (SAN) and across operating system platforms.
• Mask and unmask FC LUNs • Perform authentication using the Fibre Channel Security Protocol Diffie-Hellman Challenge Handshake Authentication Protocol (FC-SP DHCHAP) • Create and delete FC virtual ports through N_Port_ID virtualization [NPIV] • View FC virtual ports and virtual machine mapping information • Configure FC boot from SAN • Modify an IP port number of the remote management agent • View vital product data (VPD) for the selected adapter port • View transceiver information for the s
Table 1: Supported Features by Operating System Cross-Reference (Continued) Windows Solaris Linux VMware ESX Server FC/FCoE Boot from SAN X X X X iSCSI configuration X X X Update firmware and FC boot code on a single adapter or multiple adapters using batch update Enable or disable the x86 BootBIOS, EFI or OpenBoot, PXE Boot Run diagnostic tests on adapters Manage local adapters X X X X* X X X X* X X X X X X X X* Manage FC remote and TCP/IP accessed adapters Locate adapters usi
Known Issues See the product release notes for the latest information. Printing Help Information To print help information: 1. Select the help information you want to print. 2. From the browser menu select File>Print. 3. From the Print dialog box check Selection. 4. Click OK.
Installing and Uninstalling OneCommand Manager Application Components Installing the OneCommand Manager Application In Windows There are two ways to install the OneCommand Manager application in Windows: • Attended installation using the GUI. • Unattended installation using the command line. Note: If you are running the OneCommand Vision application, you must stop the OneCommand Vision sensor before installing the OneCommand Manager application. To stop the sensor: 1.
3. Double click the elxocm.exe. The Emulex OCManager Enterprise window appears. Figure 1: OCManager Enterprise window 4. Click Next. The Installation Options window appears.
5. Click Install. The Management Mode dialog box appears. Chooose the management mode you want and click OK. See “Changing Management and Read-Only Mode” on page 28 for more information. Figure 3: Management Mode dialog box 6. The Installation Completed window appears when the installation is finished. Figure 4: OCManager Enterprise Installation completed window 7. Click Finish. A shortcut is added to the Start menu. You do not need to reboot the system.
Unattended Installation in Windows To install the OneCommand Manager application in Windows: 1. From the Emulex website, download the x64 or x86 OneCommand Manager Enterprise Kit installation file to your system. The kit is activated with the optional switch /q or /q2. The /q switch displays progress reports. The /q2 switch does not display progress reports.
5. When prompted, enter the type of management you want to use: 1 Local Mode : HBA's on this Platform can be managed by OneCommand clients on this Platform Only. 2 Managed Mode: HBA's on this Platform can be managed by local or remote OneCommand clients. 3 Remote Mode : Same as '2' plus OneCommand clients on this Platform can manage local and remote HBA's. 6. If you answered <2> or <3> in step 5, you must decide if you want the OneCommand Manager application to operate in read-only mode.
• For SLES 10 and SLES 11 type: cd elxocm-sles10-sles11-- 8. Run the install script. Type: ./install.sh 9. Enter the type of management you want to use: 1 Local Mode : HBA's on this Platform can be managed by OneCommand clients on this Platform Only. 2 Managed Mode: HBA's on this Platform can be managed by local or remote OneCommand clients. 3 Remote Mode : Same as '2' plus OneCommand clients on this Platform can manage local and remote HBA's. 10.
Installing the OneCommand Manager Application Web Launch Interface Prerequisites In addition to the driver and OneCommand Manager application, the following prerequisites must be met before you install the Web Launch feature: Note: The OneCommand Manager application Web Launch Interface is not supported on VMware ESX Server. In Windows: • Microsoft Internet Information Services (IIS) Server must be installed. See the Microsoft website for information on downloads and installation.
To add the MIME type: 1. Launch Server Manager. 2. Expand Roles. 3. Under Roles, expand Web Server (IIS). 4. Under Web Server (IIS), Click Internet Information Services (IIS) Manager. 5. In the right pane, find your server name under "Start Page" and click on it. 6. Double-click MIME Types listed under IIS group. 7. A MIME Types page appears. Under "Actions", click Add... A popup dialog box appears. 8. Add "jnlp" (without quotes) to the File name extension field. 9.
• Linux: cd /usr/sbin/ocmanager 3. Run the install script. Type: ./wsinstall 4. When prompted, enter the web server's document root directory. For example: • Solaris: • Linux: /var/apache/htdocs /srv/www/htdocs or /var/www/html 5. Confirm that the IP address of the host is the IP address that the web server uses. Answer or as appropriate. If you answer , you are prompted for the IP address you want to use. 6.
In Windows There are two ways to install the OneCommand Manager application CLI in Windows: • Attended installation using the GUI. • Unattended installation using the command line. Attended Installation in Windows To install the OneCommand Manager application CLI: 1. From the Emulex website, download the x64 or x86 OneCommand Manager Core Kit installation file. Note: For IA64 systems, use the x86 OneCommand Manager Core Kit installation file. 2.
4. Click Next. The Installation options window appears. Figure 6: OCManager CLI Installation options window 5. Click Install. The Operation in Progress window appears. The Installation completed window appears when the installation is finished. Figure 7: OCManager CLI Installation completed window 6. Click Finish. A shortcut is added to the Start menu. You do not need to reboot the system.
Unattended Installation in Windows To install the OneCommand Manager CLI application in Windows: 1. From the Emulex website, download the x64 or x86 OneCommand Manager Core Kit installation file to your system. 2. At the command prompt, set the optional switch to /q or /q2. The kit is activated with this optional switch. The /q switch displays some progress reports. The /q2 switch does not display progress reports. For example: elxocmcore-windows-x64-5.01.00.10-4.
Or elxocmcore-esxNN- Where NN is 40 for an ESX 4.0 system or 41 for an ESX 4.1 system. 3. Type: rpm -e elxvmwarecorekit- Or rpm -e elxocmcore-esxNN- Where NN is 40 for an ESX 4.0 system or 41 for an ESX 4.1 system. In Linux Prerequisites For existing systems install the following drivers before installing the OneCommand Manager application CLI: On LP21000 series adapters and OneConnect FCoE adapters: • Linux driver version 8.2.0.33.
3. Untar the file. tar zxvf elxocmcore---.tgz 4. Change (use cd command) to the core kit directory created in step 3. cd elxocmcore--- 5. Run the install.sh script. ./install.sh Note: The core kit consists of 2 rpm files for each supported architecture and each supported version of Linux: 1. elxocmlibhbaapi-*.rpm 2. elxocmcore-*.
Or Run the uninstall script located in the tar file to remove the enterprise kit. If the HBAnyware Security Configurator is installed, it must be uninstalled before uninstalling the HBAnyware utility. You must run the uninstall script that shipped with the version of HBAnyware Security Configurator that you want to remove. Proceed to step 2. If the Security Configurator is not installed, proceed to step 3. 2. If the HBAnyware Security Configurator is installed, follow these steps: a. Log on as ‘root’. b. c.
Upgrading from the OneCommand Manager Application CLI to the FullFeatured OneCommand Manager Application Enterprise Kit Note: An upgrade can be performed only if the version of the OneCommand Manager application enterprise kit is the same or later than the OneCommand Manager application CLI version. You cannot downgrade a OneCommand Manager application CLI with a previous version of the OneCommand Manager application enterprise kit.
Uninstalling the OneCommand Manager Application Note: Do not uninstall the OneCommand Manager application if you are running, or intend to run, OneCommand Vision. To uninstall the OneCommand Manager application and OneCommand Manager application Web Launch Interface: In Windows 1. (Windows 2003) Select Start>Control Panel>Add/Remove Programs. or (Windows 2008 & Windows 2008 R2) Select Start>Control Panel>Programs>Uninstall a Program. 2.
Uninstalling the OneCommand Manager Application Web Launch Interface Only To uninstall the OneCommand Manager application Web Launch, but leave the OneCommand Manager application installed: In Windows: 1. Select Start>Programs>Emulex>OCManager WebLaunch Uninstall. The following screen appears: Figure 8: OneCommand Manager Web Launch Uninstallation screen 2. The OneCommand Manager application Web Launch Interface is removed. Press any key to continue. In Solaris and Linux: 1. Log on as ‘root’.
In Linux and Solaris: On Linux and Solaris machines, you can stop and start the OneCommand Manager daemon processes using the "stop_ocmanager" and "start_ocmanager" scripts respectively. These are found in the following OneCommand Manager installation directory: Linux - /usr/sbin/ocmanager Solaris - /opt/ELXocm There are three basic daemon processes, included with OneCommand Manager installations, that are affected by these scripts.
Using the OneCommand Manager Application Note: To properly view the OneCommand Manager application, ensure your system meets the following display requirements: For Windows systems, the display resolution must be set to 800 by 600 or better. For Linux and Solaris systems, the display resolution must be set to 1024 by 768 or better. The display must run in 256-color mode or higher. OneCommand Manager application icons use 256 colors.
Note: In some instances, the type of information displayed and available functionality is determined by the operating system in use. The Menu Bar The menu bar contains commands that enable you to perform a variety of tasks such as exiting the OneCommand Manager application, resetting adapters and sorting items in the discovery-tree view. Many of the menu bar commands are also available from the toolbar.
Fabric View button • Displays the FC/FCoE fabrics in the SAN with their fabric IDs. • Displays the ports under each switch. • If targets are present, displays each WWPN. Multiple adapters can refer to the same target. • If LUNs are present, displays each LUN number. • If the fabric ID is all zeros, no fabric is attached. Note: iSCSI and NIC ports are not displayed in Fabric View. Virtual Ports View button • Displays virtual ports in the SAN.
Figure 11: Discovery-tree Discovery-Tree Icons Discovery-tree icons represent the following: The local host. Other hosts connected to the system. A green adapter icon with black descriptive text represents an online adapter. Blue text represents an adapter port that had previously been discovered, but currently is not being seen by the discovery engine (service).
The NIC icon represents a NIC-Only PCI function instance. A green icon indicates this function instance is on-line, black indicates it is disabled, and red indicates a link down instance. The Virtual Port icon represents a virtual port. The COMSTAR icon represents COMSTAR target mode ports. COMSTAR ports are unique in that a single port can be shown simultaneously as both a manageable adapter port and a regular target.
• Local Management Plus - This setting only allows management of adapters on this host, but management of adapters on this host from another host is possible. • Full Management - This setting enables you to manage adapters on this host and other hosts that allow it. If Management Mode was enabled during installation, you can also set read-only mode.
2. Run the following script: /usr/sbin/ocmanager/set_operating_mode 3. Choose the management type and read-only mode you want. Enter for yes to allow the user to perform these operations, enter for no if read-only mode is desired.
Configuring Discovery Automatic FC Discovery Adapters that have a physical FC connection to the same SAN are discovered automatically when the OneCommand Manager application is launched. Adapters that do not have a physical FC connection to the SAN, where the OneCommand Manager application is launched, can be discovered by sending management requests to the remote host using TCP/IP.
Note: In Windows, if you are running a firewall you may need to add the OneCommand Manager application remote server to the firewall’s exception list. This remote server’s path is: \Program Files\Emulex\Util\Common\rmserver.exe On an Itanium 64 host the path is: \Program Files (x86)\Emulex\Util\Common\rmserver.exe The principle differences between FC and TCP/IP access are: • A TCP/IP host with or without an adapter installed does not need to connect to a fabric to manage other hosts.
Windows: The file is located on the system drive in the directory "\Program Files\Emulex\Util" or "\Program Files (x86)\Emulex\Util" for Itanium 64 hosts. Solaris: The file is located in the directory "/opt/ELXocm". Linux: The file is located in the directory "/usr/sbin/ocmanager". 2. Edit the file. Guidelines for editing the file are as follows: • Each line of the file starts with an IPv4 or IPv6 address. Following the IP address can be any number of tabs or spaces.
Procedure To add a single host: 1. From the Discovery menu, select TCP/IP>Add Host. The Add Remote TCP/IP Host dialog box appears. Figure 14: Add Remote TCP/IP Host dialog box 2. Enter the name or the IPv4 or IPv6 address of the host to be added. Note: Entering the IP address to identify the host avoids possible name resolution issues. Note: IPv6 address tuples are delimited by colons and can be entered in a shortened form (i.e. supressing 0's) as defined by the IPv6 address specification. 3.
Figure 15: Add Remote TCP/IP Host dialog box with CIM Credentials 4. Edit the default CIM settings if necessary and click Add Host. You will receive a message indicating the new host was successfully added. Adding a Range of Hosts You find the TCP/IP-accessed manageable hosts by searching a range of IP addresses. The Add Range of TCP/IP Hosts dialog box enables you to build the initial list of TCP/IP accessed manageable hosts. (Not available in read-only mode.
Figure 16: Add Range of TCP/IP Hosts dialog box Prerequisites • The OneCommand Manager application must be installed on all remote hosts. Procedure To add a range of remote hosts: 1. From the Discovery menu, select TCP/IP>Add Range of Hosts. The Add Range of TCP/IP Hosts dialog box appears. 2. Enter the complete start and end address range (IPv4 only) and click Add. The added address range appears in the dialog box. Add any additional ranges you want to search.
3. Click Start Discovery. If an address is remotely manageable, it is added to the list of addresses that the discovery server will attempt to discover. The utility creates a host file if necessary, and checks each address in the range to determine if the host is available and remotely manageable. The number of addresses (of manageable hosts) discovered is periodically updated on the dialog box. Note: The number of addresses does not correspond directly to the number of hosts added to the discovery-tree.
discovered during the search, the host will be added to the discovery-tree only once. If the same host name appears for more than one host, the adapters of all these hosts will be displayed by the OneCommand Manager appliccation as a single host entry. Figure 17: Discovery Settings dialog box To configure discovery settings: 1. From the Discovery menu, select Modify Settings. The Discovery Settings dialog box appears. 2. Define the discovery properties you want. 3.
• Protocol: The http or https protocol can be used to connect to the ESX hosts. The default port numbers used for http and https are 5988 and 5989 respectively. The port number will change automatically according to the protocol selected. The user can also manually change the port number. Since, by default, the HTTP is disabled on sfcb in ESXi host, user should use HTTPS to communicate to the ESXi host. • User name: The user name field contains the username with which to connect to the ESX hosts.
Configuring iSCSI Target Discovery The iSCSI Target Discovery tab allows you to configure iSCSI target discovery related parameters. Figure 18: iSCSI Target Discovery tab To display the iSCSI Target Discovery tab: 1. From the discovery-tree, select the iSCSI port whose discovery settings you want to configure. 2. Select the iSCSI Target Discovery tab. Target Discovery Field Definitions • Target Portals - The Target Portals table contains all target portals that are queried for targets.
Target Discovery Buttons • Add Portal - Click to add a target portal. See “Adding Target Portals” on page 41 for more information. • Remove Portal - Click to remove a portal. See “Removing a Target Portal” on page 41 for more information. • Target Login - Click to log in to a selected target. See “Logging into Targets” on page 41 for more information. • Target Sessions - Click to view active sessions for the selected target. See “Viewing Target Sessions” on page 43 for more information.
Figure 19: Target Login dialog box To log into a target: 1. From the iSCSI Target Discovery tab, select the target from the Targets table. 2. Click Target Login. The Target Login dialog box appears. The dialog box displays the Target Name and Target Alias of the target. When you log into a target and reboot the system, the OneConnect adapter automatically logs in to that target after the reboot is complete. 3. Specify the Target Login Options and Authentication type you want to use. 4.
Manually Adding an iSCSI Target The iSCSI Target Discovery tab enables you to manually add and log into iSCSI targets. To manually add an iSCSI target: 1. From the iSCSI Target Discovery tab, click Manually Add Target. The Add iSCSI Target dialog box appears. 2. Enter the target iSCSI name, target IP address and TCP port number. 3. Specify the Target Login Options and Authentication type you want to use. 4. Click OK.
Figure 20: Target Sessions dialog box Target Sessions Field Definitions • Initiator Name - The initiator named used to log into the session. • Status - The session status (logged in, login in progress, login failed, recovery, unknown). • ISID - The initiator session identifier (unique for each session). • ISID Qualifier - The first two bytes of the ISID (unique for each session). • TSIH - The target session identifier handle.
Session Negotiated Login Options Area • InitialR2T - The initial request to transmit. When set to Yes, the initiator has to wait for the target to solicit SCSI data before sending it. When set to No, it allows the initiator to send a burst of unsolicited FirstBurstLength bytes. • Immediate Data - When set to Yes, it allows the initiator to append unsolicited data to a command. • MaxConnections - The maximum number of connections to targets that are allowed within a single session.
• Destination IP Address - The destination IP address for the connection. • Destination Port - The destination TCP port number for the connection. • Redirected Destination - The redirected IP address for the target. • Redirected Destination Port - The redirected port number for the target. Connection Negotiated Login Options • Authentication Method - The authentication method used for connection. Valid values are None, Mutual CHAP and One-Way CHAP.
Figure 21: iSCSI SNS tab To add a server: 1. Click Update iSNS Server. The Update iSNS Server dialog box appears. 2. Enter the server address and port and click OK. The new iSNS server is also queried for iSCSI targets and any discovered targets are added to the Target's table on the main Target Discovery tab. To remove a server: 1. Click Clear iSNS. The iSNS server is removed and no longer queried during a target refresh. Note: The targets discovered using iSNS are not removed by clearing the iSNS server.
Viewing Discovery Information The Discovery Information page contains a general summary of the discovered elements. The Host, Fabric or Virtual Port icon, depending upon which view you select, is the root of the discovery-tree, but it does not represent a specific network element. Expanding it reveals all hosts, LUNs, targets, adapter ports and virtual ports that are visible on the SAN. To view discovery information: 1. Click the Hosts, Fabrics or Virtual Port icon at the root of the discovery-tree.
Viewing Host Grouping Information The Host Group Information tab displays information about the selected host group, such as the group name, the total number of hosts and so on. See “Grouping Hosts” on page 51 to learn about creating host groups. Note: Host grouping is not supported for VMware. To view host grouping information: 1. From the discovery-tree, select the host group whose information you want to view.
The Host Information tab displays information for the selected host including the number of adapters installed in the selected host, the number of fabrics to which it is connected and so on. Figure 24: Host Information tab Host Information Field Definitions • Operating System - The operating system and version installed on the selected host. • Management IP Address - If the host is discovered with FC, the Management IP Address field displays “Host discovered over Fibre Channel”.
Function Summary Area • NIC Functions - The number of NIC functions running on the discovered adapters on this host. • FC Functions - The number of FC functions running on the discovered adapters on this host. • FCoE Functions - The number of FCoE functions running on the discovered adapters on this host. • FC Targets - The number of FC targets discovered on the FC/FCoE functions on this host. • VPorts - The number of discovered virtual ports that can be managed by this host.
2. From the Available Host Group list choose the group whose hosts you want to view. Managing Host Groups Use the Host Group Management dialog box to create and delete host groups, add and remove hosts and restore host groups. Note: Managing host groups is not supported on VMware. Figure 25: Host Group Management dialog box Host Group Management Field Definitions • Available Hosts -The list of hosts that can be added to a host group. You can select a host and right-click to see its group assignments.
• Create New Group - Enables you to create a new host group. • Delete Group - Removes the currently selected host group. • Restore Group - Returns the selected group's configuration to its original state. • Restore All Groups - Returns all groups to to their original state. • OK - Saves the current configuration changes and closes the dialog box. • Cancel - Discards changes and closes the dialog box.
Adding a Host to a Host Group To add a host to a group: 1. From the View menu, select Manage Groups. The Host Group Management dialog box appears. 2. From the Groups list, select the group to which you want to add the host. 3. From the Available Hosts list, select the host you want to add (or select multiple hosts by using Ctrl-Click or Shift-Click), and click Add Host. The selected host is removed from the Available Hosts list and is added to the Hosts in Selected Group list. 4.
Note: The host group configuration files are completely interchangeable between different operating systems. For example, the host group configuration files created on a Solaris hosts can be copied directly to a Linux or Windows host, with no conversion required. Searching for Hosts The OneCommand Manager application enables you to search the discovery-tree for a particular host by the host’s name.
2. Select an FC adapter in the discovery-tree. Figure 28: FC Adapter Information tab FC Adapter Information Field Definitions • Model - The complete model name of the adapter. • Serial Number - The manufacturer's serial number for the selected adapter. • Hardware Version - For LightPulse adapters it displays the JEDEC ID. For OneConnect adapters it displays the board type and revision code. • Device ID - The default device ID for the selected adapter.
After the system overheating issue is resolved and the adapter has cooled down, reboot the system or, if the system supports hot swapping, cycle the power of the adapter slot. Note: If you are running the OneCommand Vision application, you must stop the OneCommand Vision sensor before hot-swapping an adapter or the hot-swap will fail. To stop the sensor: 1. Select Start > Programs > Administrative Tools > Services. 2. Stop the EmulexSensor service. 3. Stop the EmulexWMIAgent service. 4.
2. Select a OneConnect adapter in the discovery-tree. Figure 29: iSCSI Adapter Information tab OneConnect Adapter Information Field Definitions • Model - The model of the selected adapter. • Serial Number - The serial number of the selected adapter. • Active Firmware Version - The version of the firmware running on the selected adapter. • Firmware State - The condition of the firmware. • BIOS Version - The version of the BIOS in use. • HW Version - The hardware version of the selected adapter.
• NIC Only - Check to choose the NIC only personality. Note: Some of the personalities may be disabled if the personality is not available on the adapter. • Apply button - Click to apply the personality you choose. The system must be rebooted for your selection to take affect. License Features Area • Show License Features button - Click to show availble licenses. • Install License Features button - Click to install licenses.
3. Select the Port Information tab. Figure 30: FC Port Information tab FC Port Information Field Definitions Port Attributes Area Field Definitions • Port WWN - The Port World Wide Name of the adapter. • Node WWN - The Node World Wide Name of the selected adapter. • Fabric Name or Host Name - The Fabric Name field is displayed in Host view. This is a 64-bit worldwide unique identifier assigned to the fabric. The Host Name is displayed in Fabric view.
• OS Device Name - The platform-specific name by which the selected adapter is known to the operating system. (Not supported on VMware ESX servers being managed through the CIM interface.) • Symbolic Node Name - The FC name used to register the driver with the name server. • Supported Class of Service - A frame delivery scheme exhibiting a set of delivery characteristics and attributes. There are three classes of service.
3. Select the Port Information tab. Figure 31: FCoE Port Information tab FCoE Port Information Field Definitions Port Attributes Area Field Definitions • Port WWN - The Port World Wide Name of the adapter. • Node WWN - The Node World Wide Name of the selected adapter. • Fabric Name or Host Name - The Fabric Name field is displayed in Host view. This is a 64-bit worldwide unique identifier assigned to the fabric. The Host Name is displayed in Fabric view.
• Port Type - The current operational mode of the selected adapter’s port. • Enable PFC Throttle checkbox - PFC throttle is enabled by default to prevent the loss of FCoE packets. Uncheck the box to disable PFC throttle. Note: The checkbox does not appear if the adapter does not support PFC throttle. • OS Device Name - The platform-specific name by which the selected adapter is known to the operating system. (Not supported on VMware ESX servers being managed through the CIM interface.
3. Select the iSCSI Port Info tab. Figure 32: iSCSI Port Information tab iSCSI Port Info Field Definitions • Driver Name - The iSCSI driver file name. • Driver Version - The iSCSI driver version. • MAC Address - The iSCSI MAC address currently assigned to the port. • Perm MAC Address - The original factory-assigned iSCSI MAC address. • Device ID - The PCI device ID assigned to the iSCSI function. • Vendor ID - The PCI vendor ID assigned to the iSCSI function.
• IP Address - The iSCSI initiator IP address. • Subnet Mask - The iSCSI initiator subnet mask. • Gateway Address - The iSCSI initiator gateway address. • VLAN Enabled - The VLAN enabled state for the iSCSI interface. • VLAN ID - The VLAN identifier to use 0-4094 (only valid when VLAN is enabled). 0 indicates the VLAN is disabled. • VLAN Priority - The VLAN priority for the iSCSI interface. Network Info Area • Link Status - The status of the link on the selected adapter port.
3. Select the NIC Port Info tab. Figure 33: NIC Port Info tab NIC Port Info Field Definitions • Driver Name - The NIC driver file name. • Driver Version - The NIC driver version. • MAC Address - The NIC MAC address currently assigned to the port. • Perm MAC Address - The original factory assigned NIC MAC address. • IPv4 Address - The IPv4 address for the NIC port. • Subnet Mask - The subnet mask for the NIC port. • IP Address Origin - The origin of the IP address (DHCP or Static).
• Bandwidth Limit - The QoS bandwidth restriction on the port. (Non vNIC adapters only) vNIC Info Area (If supported) • Name - The name assigned to the vNIC by an administrator during switch configuration. • Outer VLAN ID - The VLAN identifier used between the NIC port and the switch. The switch maps this value into the VLAN ID used on the network. • Min. Bandwidth - The minimum bandwidth (i.e. speed) at which the port is guaranteed to run. • Max. Bandwidth - The maximum bandwidth (i.e.
3. Select the Physical Port Info tab. Figure 34: Physical Port Info tab Viewing Port Statistics The Statistics tab provides cumulative totals for various error events and statistics on the port. Some statistics are cleared when the adapter is reset. The Port Statistics information that is displayed depends upon the type of adapter you select, FC, iSCSI or NIC-Only. Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i.
3. Click the Statistics tab. Figure 35: Statistics tab Port Statistics Field Definitions • Tx Frames - FC frames transmitted by this adapter port. • Tx Words - FC words transmitted by this adapter port. • Tx KB Count - FC kilobytes transmitted by this adapter port. • Tx Sequences - FC sequences transmitted by this adapter port. • LIP count - The number of loop initialization primitive (LIP) events that have occurred for the port. This field is not supported if the topology is not arbitrated loop.
• Ex Count Orig - The number of FC exchanges originating on this port. (Not supported on VMware ESX servers being managed through the CIM interface.) • Active XRIs - The number of active exchange resource indicators. (Not supported on VMware based ESX platforms using the CIM interface.) • Received P_BSY - The number of FC port-busy link response frames received. • Link Transitions - The number of times the SLI port sent a link attention condition.
• SCSI Read KB Count - The total number of kilobytes read. • SCSI Status Errors - The number of SCSI status errors sent to the initiator. • SCSI Queue Full Errors - The number of QFULL errors sent to the initiator. • SCSI Sense Errors - The number of times sense data was sent to the initiator. • SCSI Residual Over - The number of residual overruns returned to the initiator. • SCSI Residual Under - The number of residual underruns returned to the initiator.
• Portal Count - The number of rows in the iscsiPortaltypeTable which are currently associated with this iSCSI instance. • Node Count - The number of rows in the iscsiNodetypeTable which are currently associated with this iSCSI instance. • Session Count -The number of rows in the iscsiSessiontypeTable which are currently associated with this iSCSI instance. • Session Failure Count - The number of times a session belonging to this port has failed.
Viewing FC Virtual Port Information (FC and FCoE Adapters Only) Use the Virtual Ports tab to view information about FC virtual ports and their associated targets and LUNs. To view virtual port information: 1. Do one of the following: • From the View menu, select Group Adapters by Virtual Port. • From the toolbar, click Group Adapters by Virtual Port. Figure 37: Virtual Ports Information Virtual Port Information Field Definitions • Number of Hosts - The total number of hosts discovered in the SAN.
The Discovery Information tab shows information about the fabric. Figure 38: Fabric Discovery Information Discovery Information Field Definitions • Number of Hosts - The number of hosts discovered or seen by this host on the selected fabric. • Number of Fabrics - The number fabrics identified during discovery. • Number of Adapters - The number of adapters discovered by this host on the selected fabric.
3. Select the Transceiver Data tab. Figure 39: FC Transceiver Data tab Transceiver Data Field Definitions Module Attributes Area • 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.
• TX Bias Current - The internally measured TX bias current. • TX Output Power - The measured TX output power • RX Input Power - The measured RX input power. Viewing OneConnect Adapter Transceiver Information When you select an OneConnect adapter port from the discovery-tree, the Transceiver Data tab contains information associated with the selected port. To view OneConnect transceiver information: 1. Select Host or Fabric view. Note: iSCSI and NIC-Only adapters do not appear in Fabric view. 2.
• Connector - The external optical or electrical cable connector provided as the media interface. • Wavelength - The nominal transmitter output wavelength at room temperature. • OUI - The vendor’s Organizationally Unique Identifier. It is also known as the IEEE Company Identifier for the vendor. • Date - The vendor’s date code in the MM/DD/YY format. • Serial Number - The serial number provided by the vendor. • Part Number - The part number provided by the SFP vendor.
3. Select the PHY Data tab. Figure 41: PHY Data tab PHY Data Field Definitions Operational Attributes Area • Pair A/B/C/D Signal-to-Noise (SNR) Margin - Displays the CNA's MDI interface average SNR margin for twisted pairs A, B, C & D. Error Rates Area • Low Density Parity Check (LDPC) Frame Errors - The LDPC counter tracks the number of LDPC frames received by CNA's MDI interface that can not be corrected. This counter self-clears at MDI link down.
Viewing Vital Product Data (VPD) Viewing VPD (FC adapters) The VPD tab displays vital product data (if available) for the selected FC adapter port such as the product name, part number, serial number and so on. Note: Not supported on systems using CIM provider v1.2.1 on ESX 3i. To view VPD information: 1. Select Host or Fabric view. 2. In the discovery tree, select the FC port whose VPD information you want to view. 3. Select the VPD tab.
3. Select the VPD tab. Figure 43: OneConnect VPD tab VPD Table Definitions • Product Name - Product information about the selected adapter port. • PN (Part Number) - The adapter's part number. • SN (Serial Number) - The adapter's serial number. • VO - Vendor unique data. “V” indicates a vendor-specific field. An adapter may have none, one or more of these fields defined. Valid values for this field are “VO” (the letter “O”, not the number zero) and “Vx” (where “x” is a number).
3. Select the Maintenance tab. Figure 44: FC Maintenance tab Maintenance Tab Field Definitions Firmware Area • Current Version - The Emulex firmware version number for this model of adapter. • Initial Load - The firmware version stub responsible for installing SLI code into its proper slot. (Not available on VMware ESX servers being managed through the CIM interface.) • SLI-2 Name - The name of the SLI-2 firmware overlay. (Not available on VMware ESX servers being managed through the CIM interface.
• • “Not Present” if boot code is not loaded. If boot code is not loaded, the Enable Adapter boot checkbox is not visible and you cannot configure the selected port to boot from SAN. Enable adapter boot checkbox - Check this box if you want the adapter to load and execute boot code during system startup. Click Configure Boot to configure boot from SAN. See “Configuring Boot from SAN” on page 159 for more information. (Not available in read-only mode.
3. Select the Maintenance tab. Figure 45: FCoE Maintenance tab Maintenance Tab Field Definitions Firmware Area • Firmware Version on Flash - Specifies the firmware version stored on the adapter’s non-volatile storage. When the system restarts, this version becomes the active firmware version. • Service Processor FW Version - Specifies the firmware version that is currently operational on the adapter. • Active Firmware Version - The version of firmware running on the selected adapter.
Pending Changes • WWPN - Works in conjunction with the Change WWN button. Displays the World Wide Port Name you assigned for the selected adapter port, but the system must be rebooted for these changes to take effect and appear under the “Current” listing. See “Configuring Boot from SAN” on page 159 for more information. • WWNN - Works in conjunction with the Change WWN button.
Firmware Tab Field Definitions • Active Firmware Version - The firmware version currently being used by the adapter. • Flash Firmware Version - The flash firmware version currently being used by the adapter. • BIOS Version - The version of the BIOS currently being used by the adapter. Boot Code Versions Area • Startup-up Boot Code - The boot code version currently being used by the adapter. Note: This is the version of the code that boots the adapter.
Viewing FC/FCoE Target Information When you select a target associated with an FC/FCoE adapter from the discovery-tree, the Target Information tab displays information associated with that target. To view FC/FCoE target information: 1. Select Host, Fabric or Virtual Port view. 2. In the discovery-tree, select the FC/FCoE target whose information you want to view. The Target Information tab appears.
2. In the discovery-tree, select the iSCSI target whose information you want to view. The Target Information tab appears. Figure 48: iSCSI Target Information tab Target Information Field Definitions • Target iSCSI Name - The iSCSI name assigned to the target. • Target Alias - The iSCSI alias assigned to the target. This is assigned at the target portal, not by the OneCommand Manager application. • ETO - (Extended Timeout Value) The ETO for the target.
Viewing LUN Information The LUN Information tab contains information about the selected logical unit number (LUN). The type of information that is displayed depends on the type of adapter you select, FC or iSCSI. Note: LUNs that are associated with a manageable COMSTAR port do not appear in the discovery-tree and cannot be configured using the OneCommand Manager application or hbacmd utilities. To view the LUNs using the OneCommand Manager application, you must view the COMSTAR port as a target.
3. Select the LUN whose information you want to view. The LUN Information tab appears. Figure 49: FC/FCoE LUN Information tab FC/FCoE LUN Information Field Definitions Vendor Product Information Area • Vendor Name - The name of the vendor of the LUN. • Product ID - The vendor-specific ID for the LUN. • Revision - The vendor-specific revision number for the LUN. Mapping Information Area • FCP LUN - The FC identifier used by the adapter to map to the SCSI OS LUN.
LUN Masking Area • Current Mask Status - Possible states are masked or unmasked. Note: See “Masking and Unmasking LUNs (Windows)” on page 154 for more information on LUN Masking. Viewing iSCSI LUN Information When you select a LUN associated with an iSCSI adapter from the discovery-tree, the LUN Information tab displays information associated with that LUN. To view the LUN information: 1. Select Host view. 2. From the discovery-tree, select the iSCSI LUN whose information you want to view.
Viewing FC/FCoE Target Mapping (Windows and Solaris) The Target Mapping tab enables you to view current target mapping and to set up persistent binding. Note: Persistent binding is not supported on Solaris systems. Note: The Target Mapping tab is not available on COMSTAR ports. To view target mapping: 1. Select Host or Fabric view. 2. In the discovery-tree, select the FC/FCoE adapter port whose target mapping information you want to view. 3. Select the Target Mapping tab.
Persistent Binding Configuration Area • This table lists persistent binding information for the selected adapter port. (Not available on VMware ESX servers being managed through the CIM interface.) Display Mode Radio Buttons • Show WWPN, Show WWNN or Show D_ID options enable you to choose how to display information in the Persistent Binding Configuration table. Target Mapping Buttons • Refresh - Click to refresh the Target Mapping tab.
Viewing iSCSI and NIC PCI Registers The PCI Registers tab contains PCI information about the selected NIC or iSCSI function. The type of information that is displayed depends on the type of function you select, FC, iSCSI, or NIC -only. See “Viewing the PCI Registers” on page 170 for FC PCI register information. Viewing iSCSI PCI Registers The iSCSI PCI Registers tab displays base PCI registers. Figure 52: iSCSI PCI Registers tab To view iSCSI PCI registers: 1.
Viewing NIC PCI Registers The NIC PCI Registers tab displays base PCI registers. Figure 53: NIC PCI Registers tab To view NIC PCI registers: 1. From the discovery-tree, select the NIC function whose PCI information you want to view. 2. Select the NIC PCI Registers tab.
Managing Adapters This section describes the various adapter management functions you can perform using the OneCommand Manager application. Managing Devices using CIM VMware on the Visor-based ESX platforms uses the Common Interface Model (CIM) as the only standard management mechanism for device management. OneCommand Manager uses the standard CIM interfaces to manage the adapters in the ESX COS and Visor environments and supports CIMbased device and HBA management.
Using the Adapter Information tab, you can view what licenses are available and install licenses for a OneConnect adapter. Figure 54: OneConnect Adapter Information tab Showing Licenses To view the available licenses for a OneConnect adapter: 1. From the discovery-tree, select the OneConnect adapter whose licenses you want to view. The Adapter Information tab is displayed. 2. On the Adapter Information tab click Show License Features. The License Features window appears.
Figure 55: Licensed Features window Installing Licenses To install licenses for a OneConnect adapter: 1. From the discovery-tree, select the OneConnect adapter whose licenses you want to install. The Adapter Information tab is displayed. 2. From the Adapter Information tab, click Install Feature Licenses. The Install Feature Licenses dialog box appears displaying the AdapterID.
3. Following the instructions you received with the Entitlement Code, go to the License website and enter the AdapterID and Entitlement Code. Note: The Copy to Clipboard button enables you to copy the AdapterID to the clipboard so you can paste it into a file or in the AdapterID field at the License website. 4. When the AdapterID and Entitlement Code are successfully validated, download a License Key File containing one or more activation keys. 5.
Figure 57: OneConnect Adapter Information tab To change the personality of a OneConnect adapter: 1. From the discovery-tree, select the OneConnect adapter whose personality you want to change. The Adapter Information tab is displayed. 2. From the Personality area of the Adapter Information tab, select the personality type you want and click Apply. Note: If the adapter does not support personalities, personality controls are not displayed.
Note: In Solaris and Linux, you can also specify parameters when loading the driver manually. (Not available in read-only mode.) Refer to the appropriate driver manual for instructions. Activation Requirements A parameter has one of the following activation requirements: • Dynamic - The change takes effect while the system is running. • Reset - Requires an adapter reset from the utility before the change takes effect. • Reboot - Requires reboot of the entire machine before the change takes effect.
Figure 58: Host Driver Parameters tab Host Driver Parameters Tab Field Definitions • Installed Driver Type - The current driver installed on this host. If there is more than one driver type installed, the Installed Driver Types menu shows a list of all driver types and driver versions that are installed on the adapters in the host. • Adapter Parameter table - A list of adapter driver parameters and their current values.
Setting Driver Parameters The Driver Parameters tab for adapters and hosts enable you to modify driver parameters for a specific adapter or all adapters in a host. For example, if you select a host in the discovery-tree, you can globally change the parameters for all adapters in that host. If you select an adapter port in the discovery-tree, you can change the lpfc_use_adisc, lpfc_log_verbose and the lpfc_nodev_tmo parameters for only that adapter.
Figure 59: Driver Parameters tab - Adapter Selected 4. In the Driver Parameters tab, click the parameter that you want to change. A description of the parameter appears on the right side of the tab. 5. Enter a new value in the Value field in the same hexadecimal or decimal format as the current value or select a value from the drop-down menu. If you enter a value and the current value is in hexadecimal format, it is prefaced by “0x” (for example, 0x2d).
Setting an Adapter Parameter Value to the Host Adapter Parameter Value To set an adapter parameter value to the corresponding host parameter value: 1. Select Host or Fabric view. 2. In the discovery-tree, select the adapter port. 3. Select the Driver Parameters tab. 4. Click Globals. All parameter values are now the same as the global, or host, values. 5. To apply the global values, click Apply. Saving Adapter Driver Parameters to a File To save a desired adapter parameter configuration click Save.
Figure 60: 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 to revert to its last permanent setting when the system is rebooted), check Make changes temporary. This option is available only for dynamic parameters. 7.
5. If DHCHAP authentication is currently employed on this machine, start up the Emulex FC authentication service. Type: /etc/init.d/fcauthd start 6. Start the elxhbamgr service (remote service). Type: ./start_ocmanager The OneCommand Manager application discovery service starts automatically when you launch the application. Note: If DHCHAP authentication is currently employed on Emulex adapters on this machine, you must type "/etc/init.d/fcauthd start" to restart the authentication daemon.
6. Click Save. The Save Driver Parameters dialog box appears. You can save the file to a different directory or change its name. Figure 61: Save Driver Parameters dialog box 7. Use the two radio buttons to choose the type of parameters to save. You can save all parameters or only those parameters whose current values differ from their corresponding default values. A list of the saved parameters and their current values show in the Saved Parameters box. 8. Click Save.
Figure 62: Batch Driver Parameters Update dialog box 4. Make your selections and click Start Update. The OneCommand Manager application Batch Driver Parameter Update dialog box shows the current status of the update. When the update completes, a final summary shows the number of adapters that were successfully processed, and the number of adapters for which one or more parameter updates failed. 5. If you want, click Save Log File to save a report of the update.
Configuring DCB (Data Center Bridging) Parameters Configuring CEE/FCoE-Specific Parameters (LP21000 Series Adapters Only) The CEE tab allows you to view and configure the CEE-specific parameters for the selected port. The CEE tab only appears if you select an LP21000 series adapter from the discovery-tree. • When DCBX is present, the Current Values are received from the switch and can only be changed by configuring the switch.
down values are Standard and Per Priority. The DCBX Sync column indicates if the feature parameter exchange with the switch was successful. “Yes” means it was successful. “No” means it was not successful. The Current Value column indicates the current setting for the value. • PFC Priority Map - A series of eight checkboxes that can only be selected if the Pause Type is set to “Per Priority”. Selected values correspond to the flow control priorities being used by the board.
2. Select the DCB tab. Figure 64: DCB tab (FCoE adapter port selected) DCB Tab Field Definitions • DCBX State - The current DCBX (Data Center discovery and Capability exchange protocol) state (enabled or disabled). • DCBX Mode - The DCBX mode can be either DCB or CIN. Note: DCBX mode also configures FIP mode. If DCBX mode is DCB, FIP is enabled. If it is CIN, FIP is disabled. • LLDP Transmit State - DCBX uses Link Layer Discovery Protocol (LLDP) to exchange parameters between two link peers.
• Error - The state of Error feature. The error feature indicates whether an error has occurred during the configuration exchange with the peer. Error is also set to YES when the Compatible method for the feature fails. FCoE Properties Area (FCoE ports only) • State - The FCoE state. It can be Enabled or Disabled. • Active Priorites - The current active priority assigned for FCoE. • Sync’d - If yes, the FCoE priority has been set by the peer. This parameter cannot be set.
Figure 65: Configure DCB dialog box for FCoE adapter ports (DCBX enabled) Configure DCB Dialog Box Field Definitions DCBX Settings Area • Enabled - DCBX can be enabled or disabled. With DCBX enabled, the configured values are used only if the switch does not provide them. With DCBX disabled, the configured values are used. • DCBX Mode - The DCBX mode can be set to CEE or Cisco-Intel-Nuova (CIN). Changes to the DCBX mode require a reboot of the host.
• Transmit System Description Enabled - Provides a description of the network entity in an alphanumeric format. This includes system's name and versions of hardware, operating system and networking software supported by the device. The value equals the sysDescr object, if the LAN device supports RFC 3418. • Transmit System Capabilities Enabled - Indicates the primary function(s) of the device and whether or not these functions are enabled on the device. The capabilities are indicated by two octets.
1 One and only one priority is configured for the FCoE priority. 2. A maximum of two PFC priorities can be selected and one of them must match the FCoE priority. Note: Not all adapters support two PFC priorities. Adapters that do not support two PFC priorities display an error message if you try to configure more than one PFC priority. 3. The priority group to which the FCoE priority is assigned must contain no other priorities. 4.
DCB Tab Field Definitions • DCBX State -The current DCBX (Data Center discovery and Capability exchange protocol) state (enabled or disabled). • DCBX Mode - The DCBX mode can be either CEE or CIN. • LLDP Transmit State - DCBX uses Link Layer Discovery Protocol (LLDP) to exchange parameters between two link peers. For the DCBX protocol to operate correctly, both LLDP Rx and Tx must be enabled. If either Rx or Tx is disabled, DCBX is disabled.
To configure DCB for iSCSI adapter ports: 1. From the discovery-tree, select the iSCSI adapter port whose CEE properties you want to configure. 2. Select the DCB tab. 3. Click Configure DCB. The Configure DCB dialog box appears. 4. Configure the settings you want and click OK. Note: An error message is displayed if you try to configure more priority groups than the adapter supports. The “Max Configurable PGs” field shows the number of priority groups supported by the adapter.
• Maximum Version - The highest DCBX protocol version supported by the system. Version numbers start at zero. The DCBX protocol must be backward compatible with all previous versions. This setting cannot be changed. LLDP Settings Area • Transmit Enabled - LLDP Transmit can be enabled or disabled. • Transmit Port Description Enabled - Provides a description of the port in an alpha-numeric format. The value equals the ifDescr object, if the LAN device supports RFC 2863.
• Configuration Rules - Click to display the iSCSI Priority window that lists the rules for configuring iSCSI priorities. You must observe the following rules when configuring priority groups for iSCSI adapter ports: 1 Only one priority can be configured as the iSCSI priority. 2. A maximum of two PFC priorities can be selected and one of them must match the iSCSI priority. Note: Not all adapters support two PFC priorities.
DCB Tab Field Definitions • DCBX State -The current DCBX (Data Center discovery and Capability exchange protocol) state (enabled or disabled). • DCBX Mode - The DCBX mode can be either CEE or CIN. • LLDP Transmit State - DCBX uses Link Layer Discovery Protocol (LLDP) to exchange parameters between two link peers. For the DCBX protocol to operate correctly, both LLDP Rx and Tx must be enabled. If either Rx or Tx is disabled, DCBX is disabled.
To configure DCB for NIC adapter ports: 1. From the discovery-tree, select the NIC adapter port whose CEE properties you want to configure. 2. Select the DCB tab. 3. Click Configure DCB. The Configure DCB dialog box appears. 4. Configure the settings you want and click OK. Note: An error message is displayed if you try to configure more priority groups than the adapter supports. The “Max Configurable PGs” field shows the number of priority groups supported by the adapter.
• Maximum Version - The highest DCBX protocol version supported by the system. Version numbers start at zero. The DCBX protocol must be backward compatible with all previous versions. This setting cannot be changed. LLDP Settings Area • Transmit Enabled - LLDP Transmit can be enabled or disabled. • Transmit Port Description Enabled - Provides a description of the port in an alpha-numeric format. The value equals the ifDescr object, if the LAN device supports RFC 2863.
1 Only one PFC priority can be configured. 2. The PFC Priority must be assigned to a priority group which has no other priorities. 3. Bandwidths of all the priority groups must add up to 100%. • OK - Click to apply and save your changes. • Cancel - Click to discard any changes you made. Configuring FCoE Initialization Protocol (FIP) for FCoE Adapters The FIP tab enables you to configure FIP for FCoE adapters. To configure FIP: 1.
Note: In the illustration, the "DCB (FIP) Settings" group box also has "Active" its title. This means that DCB (FIP) is the current DCBX mode (DCBX mode is set from the DCB tab). If CIN (Non-FIP) was the current DCBX mode, "Active" would be in the "CIN (Non-FIP) Settings" group box title. • Primary Fabric Name - Indicates the FC Fabric's WWN to which to connect. If the Primary Fabric Name is wild, i.e. all 0xFFs, then connection to any fabric name is allowed.
• From the discovery-tree, right-click the port whose name you want to change and select Restore Default Name. Resetting Adapter Ports (FC/FCoE Ports Only) You can reset remote and local adapter ports. (Not available in read-only mode or on NIC or iSCSI adapter ports.) Caution: Do not reset your adapter port while copying or writing files. This could result in data loss or corruption. Note: For OneConnect FCoE ports, a reset is only necessary to activate updated driver parameters or FIP settings.
Modifying TCP/IP iSCSI Port Configuration The Modify TCP/IP Configuration dialog box allows you to enable or disable VLANs, assign VLAN IDs and priorities, enable or disable DHCP and change the IP address and subnet mask and gateway address for the selected iSCSI port. Note: Checking DHCP Enabled to automatically obtain an IP address disables the IP address and subnet mask fields. Figure 72: Modify TCP/IP Configuration dialog box To modify TCP/IP configurations for iSCSI ports: 1.
Advanced TCP/IP Configuration The Advanced TCP/IP Configuration dialog box enables you to add and remove Route and Address Resolution Procotol (ARP) Table entries for the selected iSCSI port. Figure 73: Advanced TCP/IP Configuration dialog box To add table entries: 1. From the discovery-tree, select the iSCSI port whose configuration you want to modify. 2. Select the iSCSI Port Info tab and click Modify. The Modify TCP/IP Configuration dialog box appears. 3. Click Advanced.
Enabling and Disabling FC Ports Using the Port Information tab you can enable or disable FC ports. When you disable an FC port, you disable all functions for the port. Disabled ports appear in the discovery-tree with a red X. Note: Ensure there is no I/O traffic on the port before disabling it and never disable a boot port. To enable or disable an FC port: 1. In the discovery-tree, select the FC port you want to enable or disable. 2. Select the Port Information tab. 3. Click Enable Port or Disable Port.
Figure 74: iSCSI Initiator Login Options tab Initiator Login Options Tab Field Definitions iSCSI Names Area • Initiator iSCSI Name - The iSCSI qualifier name of the initiator. • Initiator Alias - An optional non-unique string used to identify the initiator. Initiator Login Options Area • ImmediateData - Defines whether the initiator may append unsolicited data to a SCSI command. Possible values are “Yes” and “No”.
Authentication Area • Authentication Method - Three options are available for the Authentication method: “None”, “One-Way CHAP” and “Mutual CHAP”. One-Way CHAP requires only that the authenticator (iSCSI target) authenticate the iSCSI initiator. Mutual CHAP requires that both the iSCSI target and iSCSI initiator authenticate each other. When “None” is selected, no authentication is performed. • Target CHAP Name - The iSCSI login name sent by the initiator to the target for authentication.
2. Select the iSCSI Initiator Login Options tab and click View Default Login Options. The Initiator Default Login Options window appears. Figure 75: Initiator Default Login Options window Initiator Default Login Options Field Definitions • Immediate Data - If set to Yes, allows the initiator to append unsolicited data to a command. • MaxOutstandingR2T - The maximum number of outstanding request to transmit's (R2T's) per task within a session, each up to MaxBurstLength bytes.
Changing World Wide Name Configuration (FC/FCoE Ports Only) The Maintenance tab enables you to change the World Wide Port Name (WWPN) and the World Wide Node Name (WWNN) of a selected adapter port. For example, you might want to 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 (e.g. driver parameters, persistent binding settings, etc.) of the failed adapter.
• From the toolbar, click Group Adapters by Host Name. • From the Host Grouping menu, select Group Adapter by Fabric Names. 2. In the discovery-tree, select the port whose information you want to change. 3. Select the Maintenance tab. Figure 76: Maintenance tab 4. Click Change WWN.
5. Click Yes. The Change World Wide Name Configuration dialog box appears. Figure 78: Change World Wide Name Configuration dialog box 6. Do one of the following: • Enter a new WWPN and/or WWNN. • Click Get Factory Default WWNs to load the settings that were assigned when the adapter was manufactured to the New WWPN and WWNN settings. These values can then be modified if desired and saved as Volatile or Non-Volatile WWNs.
8. Click OK. 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. 9. Reboot the system for the changes to take effect. The new WWPN and WWNN will appear in the Pending Changes section of the Maintenance dialog box until the system is rebooted. After rebooting, the changes are applied and appear in the Current section of the Maintenance dialog box.
Figure 79: Virtual Ports tab 3. Do one of the following: • Check Auto-generate world wide port name. The OneCommand Manager application creates the unique WWPN for the new virtual port based on the WWPN of the physical port. This option allows you to automatically create up to 255 unique virtual ports for each physical port. It also has the advantage that the new WWPN is unique.
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 dialog box appears notifying you that the virtual port was created. The dialog box 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.
Figure 80: Virtual Port tab 3. Click Remove Virtual Port. The Delete Virtual Port Warning dialog box appears.
Figure 81: Delete Virtual Port Warning 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. Check 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. 5. Click OK. Using FC-SP DHCHAP Authentication (Windows, Linux 8.
Authentication must be enabled at the driver level. Authentication is disabled by default. To enable DHCHAP using the Driver Parameters tab, enable one of the following parameters: enable-auth (in Windows), enable-auth (Solaris) or enable-auth (in Linux 8.2). Note: The authentication driver parameters are only available on local hosts. The OneCommand Manager application GUI does not display this driver parameter for any remote hosts.
• stop - To stop the fcauthd daemon pass the stop command to the fcauthd script. This command takes down the netlink connection between the fcauthd daemon and the LPFC driver and stops the fcauthd daemon. • reload - The reload command reloads the authentication configuration database into memory. This is done whenever the database is changed by another application (the OneCommand Manager application) or by you.
Configuration Area • Mode - The mode of operation. There are three modes: Enabled, Passive and Disabled. • Enabled - The adapter initiates authentication after issuing an FLOGI to the switch. If the connecting device does not support DHCHAP authentication, the software still continues with the rest of the initialization sequence. • Passive - The adapter does not initiate authentication, but participates in the authentication process if the connecting device initiates an authentication request.
Changing Your Password To change your password: 1. From the discovery-tree, select the adapter whose password you wish to change. 2. Select the DHCHAP tab and click Set Password. The Password dialog box is displayed. 3. Choose Set Local Password or Set Remote Password. • Local password is used by the adapter driver when the adapter initiates authentication to the switch (typical use). • Remote password is used by the adapter driver when the switch authenticates with the adapter.
Updating Adapter Firmware The OneCommand Manager application enables you to update firmware for a single adapter or simultaneously for multiple adapters. Updating Firmware for a Single Adapter Using the Maintenance or Firmware tab, you can update firmware on local and remote adapters. The firmware file must be downloaded from the Emulex website and extracted to a local drive before you can perform this procedure. (Not available in read-only mode.) • The Emulex driver must be installed.
3. Select the Maintenance or Firmware tab and click Update Firmware. If the warning screen appears, click Yes. The Firmware Download dialog box appears. Figure 83: Firmware Download dialog box 4. Using the Firmware Download dialog box, navigate to the unzipped, extracted image file you want to download. The firmware image may be specified either by entering the image file's full pathname in the “Firmware File” field or by clicking the Browse button.
Note: VMware ESX hosts managed through the CIM interface will list all the adapters regardless of whether the selected firmware can update the adapter. You must manually deselect the non-matching adapters. Before you can perform a batch update, the firmware file must be downloaded from the Emulex website and extracted to a directory on your local drive. To update firmware for multiple adapters: 1. From the Batch menu, select Download Firmware.
Figure 84: Batch Firmware Download dialog box, selecting adapters to update 4. Make your selections and click Start Download. When downloading begins, the tree-view displays the progress. As firmware for a selected adapter is being downloaded, it appears orange in the tree-view. Once successful downloading is complete, the entry changes to green. If the download fails, the entry changes to red.
Figure 85: Batch Firmware Download dialog box, download complete 5. When downloading is finished, you can click Save Log File to save copy of the activity log. Updating CEE Firmware for a Single Adapter (LP21000 Series Adapters Only) To support configuration of LP21000 and LP21002 adapters, the OneCommand Manager application includes a CEE/FCoE tab. This tab is only shown when an LP21000 or LP21002 adapter is selected in the discovery-tree.
To update CEE firmware on a single LP21000 or LP21002 port: 1. Select Host or Fabric view. 2. In the discovery-tree, select the LP21000 or LP21002 port whose firmware you want to update. 3. Select the CEE/FCoE tab. Figure 86: CEE/FCoE tab 4. Click Update Firmware. The CEE Firmware Download dialog box is displayed.
5. Specify the desired firmware image. Do one of the following in the CEE Firmware Download dialog box: • Type the firmware file name. There are two ways to enter the file name in the Firmware File field: • If the file is not located in the OneCommand Manager application repository, type the full path and filename of the firmware image file. • If the firmware file is located in the OneCommand Manager application repository, type only the filename.
1. From the Batch menu, select Download CEE Firmware. The Batch CEE Firmware Download dialog box appears. Note: You do not need to select a particular tree element for this operation. 2. Click Browse. The Firmware File Selection dialog box appears. 3. Navigate to the firmware file you want to use and click OK. A tree-view appears showing all adapters and their corresponding hosts for which the selected firmware file is compatible.
Figure 89: Batch CEE Firmware Download dialog box, selecting adapters to update 4. Make your selections and click Start Download.
When downloading begins, the tree-view displays the progress. As firmware for a selected adapter is being downloaded, it appears orange in the tree-view. Once successful downloading is complete, the entry changes to green. If the download fails, the entry is changed to red. Figure 90: Batch CEE Firmware Download dialog box, download complete 5. When downloading is finished, you can click Save Log File to save a copy of the activity log.
To automap SCSI devices: 1. Display driver parameters for the host or adapter - select the Driver Parameters tab or the Host Driver Parameters tab. 2. Select the AutoMap parameter. Several fields about the parameter appear on the right side of the tab. 3. Select Enabled. 4. To apply your changes, click Apply. 5. Reboot the system for this change to take effect.
Figure 91: LUN Masking tab LUN Masking Conventions and Guidelines LUN icons in the discovery-tree reflect the live mask state currently in use 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). LUN Masking Column Definitions • LUN – The FC LUN number.
3. Select the LUN Masking tab. This tab contains a list of the same set of LUNs that appear below the SCSI target in the discovery-tree. 4. In the LUN list of the LUN Masking tab, select one or more LUNs. The Mask Selected LUNs, Unmask Selected LUNs, Unmask All LUNs, Restore and Apply buttons become active as appropriate. For example, if the LUN is currently unmasked, only the Mask Selected LUNs button is active. 5.
Figure 92: Target Mapping tab 4. Target mappings are displayed by WWPN, WWNN, or D_ID. “PB”, indicates mapping from persistent binding, while “Auto”, indicates an automapped target. In the Display Mode section, choose the display mode you want to use. 5. If you want click Change Settings. The Mapped Target Settings dialog box appears. You can enable or disable auto-mapping and change the active bind type. Click OK. 6. Reboot the system for changes to take effect.
Figure 93: Add Persistent Binding dialog box 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. Note: Automapped targets have entries only in the second column of the Targets Table. Persistently bound targets have entries in the second and third columns. In this case, the third column contains the SCSI Bus and target numbers you specified in the Add Persistent Binding dialog box.
5. Click the type of binding you want to use, and type the WWPN, WWNN or D_ID 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. Adding New Targets Using sd.conf (Solaris 8, 9 and 10) You can perform on-the-fly configuration changes, without rebooting, using the OneCommand Manager application.
The configuration regions on the adapter store the configuration data for each of these boot types. Note: x86 and OpenBoot share the same configuration memory space. You cannot configure an adapter for both x86 and OpenBoot at the same time. If you try, a message appears that the existing boot type configuration will be overwritten by the new configuration. Note: Boot from SAN configuration does not affect current system operation.
3. Select the Maintenance tab, check enable adapter boot (if available) and click Configure Boot. The Boot from SAN Configuration dialog box appears. Note: The Configure Boot button is disabled if the Enable Adapter Boot checkbox is not checked. If boot code is not present on the adapter, the Enable Adapter Boot checkbox and Configure Boot button are not displayed on the Maintenance tab. Note: For OneConnect adapters, boot is always enabled and cannot be disabled.
6. Check Enable Boot from SAN and for FC ports, set the Topology and Link Speed. Note: Topology and link speed are not available for OneConnect adapters. • • Topology options are : • Auto, Loop First (default) • Auto, Point to Point First • Loop • Point to Point Link speed options are: • Auto (default) • 1 Gb/s (if available) • 2 Gb/s (if available) • 4 Gb/s (if available) • 8 Gb/s (if available) 7. If you want, click Advanced Settings to configure autoscan, spinup delay and so on.
Figure 96: Select Boot Device window (for x86 or EFIBoot) 10. On the Boot from SAN Configuration dialog box, click Apply to save your changes, but leave the dialog box open or click OK to apply the changes and close the dialog box. Note: Click Close to close the Boot from SAN Configuration dialog box without saving your changes. A message appears to discard your changes. 11. Reboot the system for your changes to take effect.
If you make changes you must click OK to save the changes and close the dialog box. You can click Cancel and close the dialog box 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 dialog boxes in the following sections.
• If a boot device is not ready, the BIOS waits for the spinup delay and, for up to three additional minutes, continues the boot scanning algorithm to find another multi-boot device. Note: The default topology is auto topology with loop first. Change this topology setting, if necessary, before configuring boot devices. • If no boot devices have been defined and auto scan is enabled, then the BIOS waits for five minutes before scanning for devices.
EFIBoot Advanced Adapter Settings dialog box Use the EFIBoot Advanced Adapter Settings dialog box to configure the advanced settings for the selected EFIBoot adapter. Figure 98: EFIBoot Advanced Adapter Settings dialog box EFIBoot Advanced Adapter Settings Field Definitions • • Device Path - Makes the Fibre driver appear as a SCSI driver. • Fibre (default) • SCSI Boot Target Scan - This option is available only if none of the eight boot entries are configured to boot via DID or WWPN.
• • 200 ms Default AL_PA number - The range is 0x 00-EF. The default is 0x00. This option changes the AL_PA (Arbitrated Loop Physical Address) of the selected adapter. (Not available for OneConnect adapters.) OpenBoot Advanced Adapter Settings dialog box Use this dialog box to configure the Advanced Adapter Settings for the selected OpenBoot adapter. Figure 99: OpenBoot Advanced Settings dialog box OpenBoot Advanced Adapter Field Definitions • PLOGI Retry Timer - Sets the PLOGI Retry timer value.
Diagnostics Note: Diagnostic tests can only be performed on a local adapter or on a remote adapter connected via TCP/IP. Diagnostic tests cannot be performed on remote adapters connected via FC. Note: Diagnostic dumps can only be generated for local LightPulse adapters or for remote LightPulse adapters connected via TCP/IP. Diagnostic dumps cannot be generated for remote adapters connected via FC. Note: Not supported on systems using CIM provider v1.2.1 on ESX 3i.
Viewing Flash Contents, PCI Registers and Wakeup Information The Diagnostics tab shows PCI register dump information and flash memory contents. The information is read-only and is depicted below. Figure 100: PCI Registers and Flash Contents of the Diagnostics tab Viewing Flash Contents If you check the Show Wakeup Image Only checkbox, the flash overlays that are not loaded when the system is booted no longer display. This checkbox defaults to unchecked.
Viewing Overlay Details If you double-click on a flash overlay, another window appears with details about that overlay. Figure 101: Overlay Detail window To see the details of a different flash overlay image, you can either close the details window and doubleclick on another overlay name, or choose a different overlay name from the Flash overlay menu. Viewing the PCI Registers The PCI Registers appear directly on the Diagnostics tab.
Running a Power On Self Test (POST) The POST is a firmware test normally performed on an adapter after a reset or restart. The POST does not require any configuration to run. (Not available in read-only mode or on LightPulse adapters in ESXi hosts.) To run the POST: 1. From the discovery-tree, select the adapter port on which you want to run the POST. 2. Select the Diagnostics tab and click Power-on Self Test (POST). A warning dialog box appears. 3. Click OK.
Figure 103: Diagnostic Dump dialog box 3. Click Start Dump. A warning message appears about taking the adapter offline. Note: For VMware systems you must set a dump directory before initiating a dump. The dump directory must be a "Storage" partition (a datastore) under the directory /vmfs/volumes. 4. Click OK. Dump files are created.
Figure 104: Diagnostic Dump File Transfer dialog box 6. Select the files you want to copy (multiple selections are available) and click Start Copy. The remote dump files will be copied to your local Dump folder. The local dump folder locations are described in step 4. Running Advanced Diagnostic Tests The Advanced Diagnostics feature gives you greater control than the Quick Test over the type of diagnostics tests that run.
Test results and the status of running tests are time stamped and appear in the Test Log area. Figure 105: Diagnostic Test Setup Running Loopback Tests To run a loopback test, use the Loopback Test section of the Advanced Diagnostics dialog box.
Error Action Enables you to define what is to be done in the event of a test failure. There are two error action options: • Stop Test - Do not log the error and abort the test. No further tests are run. • Ignore - Log the error and proceed with the next test cycle. Test Cycles Enables you to specify test cycles three ways: • Select an established cycle count by clicking on the corresponding radio button. • Enter a custom cycle count in the blank field in the Test Cycles area.
Figure 107: Advanced Diagnostic Tests Warning window for External Loopback 5. Click OK. The progress bar indicates that the test is running. Periodic test feedback, consisting of the current loopback test/cycle plus the completion status of each type of test, is displayed in the Test Log section of the dialog box. Click Clear to erase the contents of the log display or click Save to File to save the log file.
Figure 108: Select Echo Test Target window 3. Define the other parameters you want to use and click Start Test. The following warning window appears: Figure 109: Advanced Diagnostic Tests Warning window 4. Click OK. A result screen appears and the test results appear in the Test Log. Click Clear to erase the contents of the log display or click Save to File to save the log file. Saving the Log File You can save the test log to a log file for later viewing or printing.
After writing an entry into the log, you are prompted to clear the display. The default name of the saved file is DiagTest.log. An example of a saved log file appears below: Figure 110: Example of a DiagTest.log window To save the log file: 1. After running a test from the Diagnostic Test Setup dialog box, click Save to File. The Select Diagnostic Log file Name dialog box appears. The default name of a saved file is DiagTest.log. 2.
All functions are supported locally and remotely on hosts managed with TCP/IP access. Test results and the status of running tests are time stamped and appear in the Test Status area. Figure 111: NIC Diagnostics tab OneConnect Loopback Test Combinations Run the following loopback test combinations using the appropriate checkboxes: • DMA Loopback Test - The DMA loopback test sends data from the host to the adapter, then back to the host, where it is checked for data miscompute errors.
FCoE End to End Echo Test The end-to-end test enables you send an ECHO command/response sequence between an adapter port and a target port. (Not available on ESXi systems.) Note: Not all remote devices respond to an echo command. You cannot run the ECHO test and the External Loopback test concurrently. If you select the ECHO Test the External Loopback test is disabled. Error Action Enables you to define what is to be done in the event of a test failure.
4. Click OK. If you choose to run an External Loopback test the following window appears: Figure 113: Advanced Diagnostic Tests Warning window for External Loopback 5. Click OK. The progress bar indicates that the test is running. Periodic test feedback, consisting of the current loopback test/cycle plus the completion status of each type of test, is displayed in the Test Status section of the dialog box. Click Show Test Log to view and save the log file.
• In VMware Server: There is no default directory for VMware. After writing an entry into the log, you are prompted to clear the display. The default name of the saved file is DiagTest.log. An example of a saved log file appears below: Figure 114: Example of a DiagTest.log window To save the log file: 1. After running a test from the Diagnostic tab, click Save Test Log. The Diagnostic Test Log dialog box appears. The default name of a saved file is DiagTest.log. 2.
Figure 115: Diagnostic Dump dialog box 3. Click Start Dump. Dump files are created. Where these files are created depends upon your operating system: Note: For VMware systems you must set a dump directory before initiating a dump. The dump directory must be a "Storage" partition (a datastore) under the directory /vmfs/volumes. • Windows - %ProgramFiles%Util\Dump\ • Solaris - /opt/ocmanager/Dump • Linux - /usr/sbin/ocmanager/Dump • VMware - a dump directory you create under /vmfs/volumes.
Figure 116: Diagnostic Dump File Transfer dialog box 5. Select the files you want to copy (multiple selections are available) and click Start Copy. The remote dump files are copied to your local Dump folder. The local dump folder locations are described in step 4.
Using the OneCommand Manager Application Command Line Interface The Command Line Interface (CLI) Client component of the OneCommand Manager application provides access to the capabilities of the Remote Management library from a console command prompt. This component is intended for use in scripted operations from within shell scripts or batch files. The CLI Client is a console application named HbaCmd. Each time you run this application from the command line, a single operation is performed.
In the preceding example, this requests the port attributes of port 10:00:00:00:c9:11:22:33 which is present in the host with the IP address 10.11.12.13. The default credentials set will be used. Commands Using the User-Provided CIM Credentials If the credentials differ from the set default values, or if the credentials are not set at all, the user can provide them, along with the command, like this: >hbacmd h=10.19.20.
The CLI Client Command Reference Using the CLI Client Syntax Rules The syntax rules for HbaCmd are as follows: • All commands must start with ‘hbacmd’ in lowercase in Linux, Solaris, and VMware which are case sensitive. • The requested operation must contain at least three characters, or as many as needed to distinguish it from any other operation. • Whenever a WWPN is specified, individual fields are separated by colons (:) or spaces ( ).
• GetQosInfo • GetRetentionCount • GetVPD • GetWWNCap • GetXcvrData • HbaAttributes • InstallAdapterLicense • ListHbas • LoadList • LoopBackTest • PciData • PortAttributes • PortStatistics • ReadWWN • RemoveHost • Reset • RestoreWWN • ServerAttributes • SetBeacon • SetCableNVP • SetCnaPGBW • SetDCBParam • SetDCBPriority • SetDriverParam • SetDriverParamDefaults • SetDumpDirectory • SetFIPParam • SetRetentionCount • ShowAdapterLicenseFeatures • ShowL
The Command Reference CLI Client commands are supported for Windows, Solaris, Linux and VMware ESX. Commands Not Supported in Linux and Solaris Note: The following commands are not supported in Linux and Solaris: PersistentBinding SetPersistentBinding RemovePersistentBinding RemoveAllPersistentBinding BindingCapabilities BindingSupport SetBindingSupport SetPfcThrottle * *SetPfcThrottle is supported in Linux but not in Solaris.
Commands Supported in CIM Provider 3.1 Note: In addition to the commands supported by the CIM Provider 3.0, the following commands are supported by the CIM Provider 3.1: Dump GetDCBParams GetDumpDierctory GetDumpFile GetDumpFileNames GetFCFInfo GetFipParams GetRetentionCount GetPGInfo SetDCBParam SetCnaPgBw SetDCBPriority SetDumpDirectory SetFIPParam SetRetentionCount Commands Supported in CIM Provider 3.2 Note: In addition to the commands supported by the CIM Provider 3.0 and 3.
Commands Supported in Target-mode Ports Note: The following HbaCmd commands are supported for managing target-mode ports: DeleteDumpFiles Download DriverConfig ExportSanInfo GetDCBParams GetDriverParams GetDriverParamsGlobal GetDumpDirectory GetFCFInfo GetFIPParams GetPGInfo GetPortStatistics GetRetentionCount GetVPD GetXcvrData HbaAttributes ListHBAs PortAttributes Reset SaveConfig ServerAttributes SetDCBPGBW SetDCBParam SetDriverParam SetDriverParamDefaults SetFIPParam SetPortEnabled SetRetentionCount All
Help Command The HbaCmd help command lists help for the HbaCmd console application. Help Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd Help [GroupName][CmdName] Description: Help is displayed at three levels. The command hbacmd help lists (by groups) all the commands. The command hbacmd groupname, lists all the commands in the group. The command help commandname shows the help for the specific command. Parameters: [GroupName] - All commands in the group. [CmdName] - Any CLI command.
Example: For non-ESXi hosts hbacmd InstallAdapterLicense 00-12-34-56-78-9A K:\lf1324.lic For ESXi hosts hbacmd h= m=cim u=root p= n= InstallAdapterLicense 00-12-34-56-78-9A K:\lf1324.lic ShowAdapterLicenseFeatures Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd ShowAdapterLicenseFeatures Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command.
Parameters: WWPN - Adapter’s FCoE port WWPN MAC - Adapter’s NIC or iSCSI port address Example: For non-ESXi hosts >hbacmd ShowLicenseAdapterID 00-12-34-56-78-9A For ESXi hosts >hbacmd h= m=cim u=root p= n= ShowLicenseAdapterID 00-12-34-56-78-9A Attributes Commands HbaAttributes Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=] hbaattributes Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command.
PortStatistics Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd PortStatistics Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command shows all port statistics for the adapter.
SetPortEnabled Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd SetPortEnabled Description: This command enables or disables the FC or CNA port. Parameters: WWPN - Adapter’s WWPN MAC - MAC address of the NIC or iSCSI port PortEnable 0 for Disable 1 for Enable Note: Ensure all I/O on the port is stopped, before disabling the port. Note: When the SetPortEnabled command disables an FC port, the adapter must be reset to activate the new setting.
Parameters: WWPN1 - Adapter’s WWPN WWPN2 - Must be "ff:ff:ff:ff:ff:ff:ff:ff" for a switch or the actual WWPN for a target PasswordType 1 = ASCII 2 = Hex (binary) 3 = Password not yet defined Password - Current password value GetAuthConfig Supported by: Windows, Solaris and Linux Syntax: hbacmd GetAuthConfig Description: This command retrieves the authentication configuration for the adapter.
SetAuthConfig Supported by: Windows, Solaris and Linux Syntax: hbacmd SetAuthConfig Description: This command sets the authentication configuration for the adapter.
Cpt - Current password type: 1 = ASCII 2 = Hex (binary) 3 = Password not yet defined Cpw - Current password value Npt - New password type: 1 = ASCII 2 = Hex (binary) Npw - New password value Boot Commands Note: Boot commands are supported on FC/FCoE adapter ports only. EnableBootCode Note: This command is not supported for OneConnect adapters. The boot code is always enabled on OneConnect adapters.
GetBootParams Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd GetBootParams Description: This command shows the boot parameters. If any arguments are missing or invalid, a suitable error is reported. If all arguments are correct, the data is displayed in tabular form.
CEE Commands Note: Converged Enhanced Ethernet (CEE) commands are for CEE management of LP21000 series adapters only. CEEDownload Note: Supported for LP21000 series adapters only. Not supported for OneConnect adapters. Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd CEEDownload Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244.
Pausetype - 1 = Standard, 2 = Per Pause Priority pfcflag - 0 = Clear, 1= Set pfcpriority - (0-0xff) fcoepriority - (0-7) fcoeformat - (0 or 0x10000) Uifporttype - 1 = Access, 2 = Trunk Value - Parameter Value Where multiple values are possible, they should be specified using comma separated values. Data Center Bridging Commands Note: Data Center Bridging (DCB) commands are for DCB management of OneConnect adapters only.
Parameters: WWPN - The WWPN address of the FCoE port MAC - MAC address of the NIC or iSCSI port Example: hbacmd h=10.192.203.154 getpginfo 00-00-c9-93-2f-d8 SetCnaPGBW Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd SetCnaPGBW Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244.
OneConnect adapter parameters: (1= enabled 0 = disabled) Note: The OneConnect adapter parameters doe not apply to LP21xxx adapters. DCBXState - The current DCBX (Data Center discovery and Capability exchange protocol) state DCBXMode - The DCBX mode can be either DCB or CIN. Note: DCBX mode also configures FIP mode. If DCBX mode is DCB, FIP is enabled. If it is CIN, FIP is disabled. PFCEnable - Enabled means that flow control in both directions (Tx and Rx) is enabled.
SetDCBPriority Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd SetDCBPriority < Priorities of PGID1>... Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command sets the priorities for a priority group.
Parameters: WWPN - Adapter’s WWPN MAC - MAC address of the NIC or iSCSI port PFCPriorities - PFC priority that is a comma separated list of up to 7 values ranging from 0-7. Priorities of PGID - Priority group membership that is a comma separated list of priorities ranging in value for 0-7. Example: hbacmd h=10.192.203.151 m=cim setdcbpriority 10:00:00:00:c9:3c:f7:88 3 0,1,2,4,5,6,7 3 0 0 0 0 0 0 Diagnostic Commands EchoTest Note: This command is not supported for OneConnect adapters.
Parameters: WWPN - WWPN of the FC port MAC - MAC address of the NIC or iSCSI port GetXcvrData Note: GetXcrvData is not supported for OneConnect OCe11100 series adapters. Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd GetXcvrData Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244.
LoopBackTest Note: The external loopback test is not supported for OneConnect OCe11100 series adapters. Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd LoopBackTest [Pattern] Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244.
LoopMap Note: Supported for FC ports only. Supported by: Windows, Solaris and Linux Syntax: hbacmd LoopMap Description: This command shows the arbitrated loop map data. Parameters: WWPN - Adapter’s WWPN PciData Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd PciData Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244.
Output: Vendor ID: 0x19A2 Device ID: 0x0700 Command: 0x0406 Status: 0x0010 Revision ID: 0x02 Prog If: 0x00 Subclass: 0x00 Base Class: 0x02 Cache Line Size: 0x10 Latency Timer: 0x00 Header Type: 0x80 Built In Self Test: 0x00 Base Address 0: 0x00000000 Base Address 1: 0xDF478000 Base Address 2: 0xDF480004 Base Address 3: 0x00000000 Base Address 4: 0xDF4A0004 Base Address 5: 0x00000000 CIS: 0x00000000 SubVendor ID: 0x10DF SubSystem ID: 0xE622 ROM Base Address: 0x00000
BeaconState - New state of the beacon: 0 = Off 1= On SetCableNVP Note: This command supports only OneConnect OCe11100 series adapters. Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd SetCableNVP Description: This command sets the nominal velocity of propagation (N-V-P), required for the TDR test, for the cable that connects to the phyical port associated with the WWPN or MAC.
Driver Parameter Commands Note: Supported for FC and FCoE ports only. Note: Driver parameters that are set temporarily and globally (using the "G" and "T" flags) must be read using the "GetDriverParams" hbacmd command to view the current value of the parameter. The "GetDriverParamsGlobal" hbacmd command returns only permanently set driver parameter values.
GetDriverParamsGlobal Supported by: Windows, Solaris, Linux and VMware ESX 4.0. Syntax: hbacmd GetDriverParamsGlobal Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command shows the name and the global value of each driver parameter.
SetDriverParam Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd SetDriverParam Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command changes a driver parameter and designates the scope of the change.
Dump Commands The diagnostic dump feature enables you to create a “dump” file for a selected adapter. Dump files contain information such as firmware version, driver version, and so on. This information is particularly useful when troubleshooting an adapter. (Unavailable in read-only mode.) Caution: Disruption of service can occur if a diagnostic dump is run during I/O activity.
GetDumpDirectory Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd h=ipaddress[:port] m=cim [u=username] [p=password] [n=root/emulex] GetDumpDirectory Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command shows the dump file directory for the adapters in the host.
Parameters: - The directory under /vmfs/volumes that you created to store the dump files. h - Host’s IP address m - cim u - root p - n - Example: hbacmd h=10.192.203.173 m=cim u=root p=Swamiji001 n=root/emulex setdumpdirectory 10:00:00:00:c9:61:f2:64 ocm-datastore This example shows the dump directory set to /vmfs/volumes/ocm-datastore.
GetDumpFileNames Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd GetDumpFileNames Or hbacmd GetDumpFileNames Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command gets the names of the files in the remote host's dump directory.
SetRetentionCount Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd SetRetentionCount Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command specifies the maximum number of diagnostic dump files for the adapter. When the count reaches the limit, the next dump operation deletes the oldest file.
FCoE Commands Note: These commands are supported only on OneConnect FCoE ports. GetFCFInfo Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd GetFCFInfo Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command shows the FCF information of the OneConnect adapter in FCoE mode.
SetFIPParam Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd SetFIPParam Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command sets the FIP parameters of the OneConnect adapter in FCoE mode.
iSCSI Commands Note: iSCSI commands are supported only on OneConnect iSCSI ports. Note: VMware ESX 4.0 does not support iSCSI. The following commands support the iSCSI interface in the OneCommand Manager CLI. The commands and their syntax are listed here. <…> = Required, […] = Optional The MAC address of the CNA port must be passed to each command as the first argument. Some commands require values to be set in a format similar to: "option_name=value".
AddRouteTableEntry Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] AddRouteTableEntry Description: This command adds a new route table entry to the route table of the specified port.
Target_IP - IP address of the target portal ImmediateData 0 = No 1 = Yes (default: 1) HeaderDigest 0 = None 1= CRC32C (default: 0) DataDigest 0 = None 1= CRC32C (default: 0) Auth 0 = None 1= One-Way CHAP 2 = Mutual CHAP (default: 0) TgtCHAPName - Target CHAP name enclosed in quotes (string length: 1-256) TgtSecret - Target Secret enclosed in quotes (string length: 12-16) InitCHAPName - Initiator CHAP name enclosed in quotes (string length: 1-256) InitSecret - Initiator Secret enclosed in quotes (string leng
Example: hbacmd AddTargetPortal 00-11-22-33-44-55 10.0.0.1 8000 Auth=1 "TgtCHAPName" "TargetSecret1" If you set the authentication method to "Mutual CHAP (value of 2)", You must specify all 4 values. Example: hbacmd AddTargetPortal 00-11-22-33-44-55 10.0.0.
CleariSNSServer Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] CleariSNSServer Description: This command clears the configured iSNS server and disables iSNS target discovery. If there is no iSNS server currently configured, this command does nothing.
DiscoveriSNSServer Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] DiscoveriSNSServer Description: This command discovers an iSNS server address through DHCP. If the DHCP server returns an iSNS server address, it replaces the configured iSNS server and can be viewed using the ShowiSNSServer command.
GetiSCSIPortStats Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] GetiSCSIPortStats Description: This command shows all the port statistics for a specified port.
ListSessions Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] ListSessions Description: This command lists all the sessions on a specified target. The iSCSI target name instructs the command to gather the information from the listed iSCSI target name.
SetInitiatorProperties Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] SetInitiatorProperties [Initiator_Name="initiator_name"] [Initiator_Alias="initiator_alias"] [ImmediateData=<0|1>] [HeaderDigest=<0|1>] [DataDigest=<0|1>] [Auth=<0|1|2> "TgtCHAPName" "TgtSecret" "InitCHAPName" "InitSecret"] Description: This command sets the initiator properties for the specified port.
Auth 0 = None 1= One-Way CHAP 2 = Mutual CHAP (default: 0) TgtCHAPName - Target CHAP name enclosed in quotes (string length: 1-256) TgtSecret - Target Secret enclosed in quotes (string length: 12-16) InitCHAPName - Initiator CHAP name enclosed in quotes (string length: 1-256) InitSecret - Initiator Secret enclosed in quotes (string length: 12-16) Note: If you set Auth to 1, you must also specify the TgtCHAPName and TgtSecret.
SetTargetLoginProperties Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] SetTargetLoginProperties [ImmediateData=<0|1>] [HeaderDigest=<0|1>] [DataDigest=<0|1>] [Auth=<0|1|2> "TgtCHAPName" "TgtSecret" "InitCHAPName" "InitSecret"] Description: This command sets the login and authentication properties associated with a specific target. This command requires that you specify a valid iSCSI target name .
TgtSecret - Target Secret enclosed in quotes (string length: 12-16) InitCHAPName - Initiator CHAP name enclosed in quotes (string length: 1-255) InitSecret - Initiator Secret enclosed in quotes (string length: 12-16) Note: If you set Auth is set to 1, you must specify the TgtCHAPName and TgtSecret. If you set Auth to a value of 2, you must specify the TgtCHAPName, TgtSecret, InitCHAPName, and InitSecret.
Example: hbacmd SetTPLoginProperties 00-11-22-33-44-55 10.192.1.1 5050 Auth=1 "TgtChapName" "TargetSecret1" If you set the authentication method to "Mutual CHAP (value of 2)", you must specify all 4 values. Example: hbacmd SetTPLoginProperties 00-11-22-33-44-55 10.192.1.
Parameters: MAC_Address - MAC address of the CNA port ShowRouteTable Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] ShowRouteTable Description: This command shows the route table for a specific port. Parameters: MAC_Address - MAC address of the CNA port Example: hbacmd h=10.192.203.
Parameters: MAC_Address - MAC address of the CNA port Target_IP - IP address of the target portal Port - Port number of the target portal TargetLogin Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd [h=host_IP[:port] | hostname[:port]] TargetLogin [target_portal_ip ] [ImmediateData=<0|1>] [HeaderDigest=<0|1>] [DataDigest=<0|1>] [Auth=<0|1|2> "TgtCHAPName" "TgtSecret" "InitCHAPName" "InitSecret"] Description: This command logs in to a target.
1= CRC32C (default: 0) Auth 0 = None 1= One-Way CHAP 2 = Mutual CHAP (default: 0) TgtCHAPName - Target CHAP name enclosed in quotes (string length: 1-255) TgtSecret - Target Secret enclosed in quotes (string length: 12-16) InitCHAPName - Initiator CHAP name enclosed in quotes (string length: 1-255 InitSecret - Initiator Secret enclosed in quotes (string length: 12-16) Note: If you set Auth to 1, you must specify the TgtCHAPName and TgtSecret.
LUN Masking Commands Note: Supported for FC/FCoE ports only. Note: LUN masking commands are not supported by Linux. Note: The GetLunMaskbyHBA, GetLunMaskbyTarget, RescanLuns, and SetLunMask commands are not supported for VMware ESX and Solaris. GetLunList Supported by: Windows and Solaris Syntax: hbacmd GetLunList
GetLunUnMaskByTarget Supported by: Windows and Solaris Syntax: hbacmd GetLunUnMaskByTarget
MaskOp A = Mask LUN B = Clear unmask target level C = Clear unmask HBA level D = Unmask LUN E = Unmask target level F = Unmask HBA level Miscellaneous Commands <…> = Required, […] = Optional AddHost Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd AddHost host_address Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244.
CnaGetEventLog Note: Supported for OneConnect adapters only. Supported by: Windows, Linux and VMware ESX Syntax: hbacmd CnaGetEventLog Description: This command shows the CNA event log specified by the WWPN or MAC address.
Note: [format] is optional. If the format parameter is specified as csv, adapter information is shown in csv format. If the format parameter is specified as xml, adapter information is shown in xml format. Leaving the format parameter blank shows the data in xml format. Description: For reporting purposes, this command captures the SAN information in xml or csv format. As large amount of information is output from this command Emulex recommends that you re-direct the output to a file.
Parameters: h - Host’s IP address or hostname WWPN - Adapter’s WWPN port MAC - MAC address of the NIC or iSCSI port Example: C:\Program Files\emulex\Util\OCManager>hbacmd h=10.192.203.154 m=cim u=root p=Swamiji001 n=root/emulex getqosinfo 00-00-c9-93-2f-d6 GetVPD Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd GetVPD Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command.
RemoveHost Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd RemoveHost host_address Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command removes a host from the hosts file use for TCP/IP management in the OneCommand Manager application GUI.
Description: This command sets the default CIM credentials. You must specify all four credentials: username, password, namespace and portnumber. Default credentials are used if any credential is not in the hbacmd command argument. Once the default credentials for a host are set, any other command can be issued by specifying m=cim.
Persistent Binding Commands Note: Supported for FC/FCoE ports only. Note: Not supported on Linux, Solaris or VMware ESX; PersistentBinding, SetPersistentBinding, RemovePersistentBinding, Remove All Persistent Binding, BindingCapabilities, BindingSupport and SetBindingSupport. Note: In order for a binding to take effect immediately (SetPersistentBinding parameter, Scope = I or B), the SCSIBus and SCSITarget must match the SCSI bus and SCSI target to which the FC target is already automapped.
BindingSupport Supported by: Windows and Solaris Syntax: hbacmd BindingSupport Description: This command shows the binding support for the adapter. Parameters: WWPN - Adapter’s WWPN Source C = Configuration support L = Live support PersistentBinding Supported by: Windows and Solaris Syntax: hbacmd PersistentBinding Description: This command specifies which set of persistent binding information (configured or live state) is requested.
Parameters: WWPN - Adapter’s WWPN BindType: P = Remove binding by WWPN N = Remove binding by WWNN D = Remove binding by D_ID ID: Target WWPN if BindType = P Target WWNN if BindType = N Target D_ID if BindType = D SCSIBus - Bus number of the SCSI device SCSITarget - Target number of the SCSI device SetBindingSupport Supported by: Windows and Solaris Syntax: hbacmd SetBindingSupport Description: This command enables and sets the binding support(s) for the adapter.
Parameters: WWPN - Adapter’s WWPN Scope: P = Permanent binding (survives reboot) I = Immediate binding B = Binding is both permanent and immediate BindType: P = Enable binding by WWPN N = Enable binding by WWNN D = Enable binding by D_ID TargetId: Target WWPN if BindType = P Target WWNN if BindType = N Target D_ID if BindType = D SCSIBus: Bus number of the SCSI device SCSITarget: Target number of the SCSI device The OneCommand Manager User Manual Page 249
Personality Change Commands TheOneCommand Manager application enables you to change the personality or protocol running on OneConnect adapters. When you change the personality of the adapter and reboot the host, the adapter starts running the new personality or protocol. The personalities that OneConnect adapters currently run are NIC-only, NIC + FCoE, and NIC + iSCSI. In some cases the adapters are pre-configured to support multiple personalities.
ShowPersonalities Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd ShowPersonalities Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command displays the list of personalities available on the adapter. The personality type is displayed as either NIC, iSCSI, or FCoE.
Virtual Port (VPort) Commands Note: Supported by FC and FCoE adapter ports only. <…> = Required, […] = Optional CreateVPort Supported by: Windows, Solaris and Linux Syntax: hbacmd CreateVPort auto [vname] Or hbacmd CreateVPort [vname] Description: This command creates a virtual port with an automatically generated WWPN or a user specified virtual WWPN on the specified physical port.
ListVMs Note: This command lists information for VMware ESX only. Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd ListVMs Description: This command lists all virtual machines and their information for all manageable ports. If you specify the host with the “h=” option or just give the physical WWPN, only the virtual machines for that host return.
WWN Management Commands Note: Supported for FC/FCoE adapter ports only. Note: WWN Management validates WWNs carefully to avoid name duplication. Therefore, you may see error and warning messages if a name duplication is detected. Emulex strongly recommends that the activation requirement be fulfilled after each WWN change or restore. When running with “pending changes”, some diagnostic and maintenance features are not allowed.
GetWWNCap Supported by: Windows, Solaris, Linux and VMware ESX Syntax: hbacmd GetWWNCap Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to the command. The default CIM credentials must be set using the SetCimCred command. See “SetCimCred” on page 244. Description: This command shows if volatile change is supported for the WWPN.
Description: This command changes the WWNs to the factory default or non-volatile values. (Change is non-volatile). Note: A reboot is required to activate the new setting. Note: For VMware ESX: After changing the WWN of an adapter, you must reboot the ESX system before trying to access the adapter on that system. For information on rebooting the ESX system, refer to VMware documentation.
Troubleshooting There are several circumstances in which your system may operate in an unexpected manner. The Troubleshooting section explains many of these circumstances and offers one or more workarounds for each situation. General Situations Table 6: General Situations Situation Resolution After installing and starting the OneCommand Manager application, the status bar says "Initializing discovery engine...", but after waiting for awhile, nothing is displayed in the discovery-tree.
Table 6: General Situations (Continued) Situation Resolution In the OneCommand Manager application discovery-tree, multiple UCNA FCoE or iSCSI ports are grouped under a single physical port. Ensure the Emulex NIC driver is loaded and that the operating system sees ALL NIC ports. They do not need to be plumbed or configured; just visible to the OS. Operating error occurs when attempting to run the OneCommand Manager application. When you attempt to run the utility, an operating system error may occur.
Table 6: General Situations (Continued) Situation Resolution Unwanted remote servers appear in the OneCommand Manager application. To prevent remote servers from appearing in the OneCommand Manager application, do one of the following on the remote systems: • In Windows, disable the OneCommand Manager application service. • In Linux, stop the elxhbamgr daemon by running the /usr/sbin/ocmanager/stop_ocmanager script.
Table 7: Emulex Driver for Linux and OneCommand Manager Application Situations (Continued) Situation Resolution rmmod fails to unload LPFC driver module due to ERROR: Module LPFC is in use. This message can appear when you attempt to remove the driver and there is a Logical Volume Group dependent on the driver. Make the Logical Volume Group unavailable. Type: lvchange -a n xxxxxxx where xxxxxx is the Volume Group Name.
Table 7: Emulex Driver for Linux and OneCommand Manager Application Situations (Continued) Situation Resolution “No module lpfc found for kernel” error message. When upgrading the kernel, rpm generates the following error: “No module lpfc found for kernel KERNELVERSION”. These three situations may be resolved by upgrading the kernel. There are two ways to install the driver into an upgraded kernel. The method you use depends on whether or not you are upgrading the driver.
Table 7: Emulex Driver for Linux and OneCommand Manager Application Situations (Continued) Situation Resolution The Linux SCSI subsystem only sees 8 LUNs when more are present. Some SCSI drivers will not scan past 8 LUNs when the target reports as a SCSI-2 device. Force a SCSI bus scan with /usr/sbin/lpfc/lun_scan. SuSE supplies /bin/rescan-scsi-bus.sh which can be changed to scan everything. Cannot see any adapters. Try the following solutions: 1.
Table 7: Emulex Driver for Linux and OneCommand Manager Application Situations (Continued) Situation Resolution Unwanted remote servers appear in the OneCommand Manager application. To remove out-of-band (TCP/IP) managed systems: 1. From the main menu, select Discovery-->TCP/IP->Remove Host(s)... 2. Select all hosts that you would like to stop discovering. 3. Select Remove. 4. Click Done to exit. To remove in-band (FC) managed systems: 1.
Emulex Driver for Solaris and OneCommand Manager Application Situations Table 8: Emulex Driver for Solaris and OneCommand Manager Application Situations Situation Resolution NIC Link fails to come up. For Emulex OneConnect OCe1010X adapters, you may need to properly configure the network interface using system administration utilities. VPorts and OneCommand Manager Application Situations Table 9: VPorts and OneCommand Manager Application Situations Situation Resolution VPort creation failure.
