Dell Emulex Family of Adapters - Manual (Page 315)

OneCommand Manager Command Line Interface Version 10.2 User Manual P010067-01A Rev. A
4. CLI Client Command Usage
CIM Interface
315
CIM Interface
Note: In Linux and Solaris, you cannot use HbaCmd as a CIM client.
Device Management Using the CIM Interface
VMware on the hypervisor-based ESXi platforms use the CIM as the only standard
management mechanism for device management.
For VMware ESXi hosts, you can manage adapters using the OneCommand Manager
application on Windows, but you must install and use the appropriate Emulex CIM
Provider. For installation, see “Installing the CIM Provider for VMware ESXi Hosts” on
page 305.
Note: For VMware ESXi hosts, when advanced adapter management capabilities are
required, such as iSCSI management, use the OneCommand Manager for
VMware vCenter software plug-in. For more details, see the OneCommand
Manager for VMware vCenter User Manual.
Syntax Rules for the CIM Interface
For the CIM interface, all the syntax rules in section “HbaCmd Syntax Usage” on
page 313 apply, except that the “h” option is required. Additionally, the “m=cim”
parameter is required in the command line for getting the data from the ESXi host. For
example:
hbacmd 192.168.1.110 m=cim u=root p=password n=root/emulex listhbas
Syntax Options and Setting CIM Credentials
For issuing CIM-based commands, two main syntax options are available.
Option A
hbacmd <h=IP_Address[:port]> m=cim [u=userid] [p=password]
[n=root/emulex] <command> <WWPN>
Option B
hbacmd <h=IP_Address[:port]> <m=cim> <command>
Before using the option B syntax, you must set the CIM credentials by doing one of
the following:

Set the default CIM credentials using the SetCimCred command (see
page 404). This command sets only the CIM credentials. Once you have set
them, subsequent HbaCmd commands do not require you specify the CIM
credentials on the command line.
For example:
hbacmd SetCimCred <username> <password> <namespace>
<portnum>