HP Systems Insight Manager 5.3 Technical Reference Guide

including deploying license keys to iLO and collecting licensing information from iLO. Not all servers can
communicate with iLO at this time.
The License Manager core establishes and maintains a secure communication channel with iLO2 through
two options provided by HP SIM, SSL and SSH. Both, SSL and SSH meet the requirements for a secure
channel. If the target systems are iLOs, the iLO must support SSH and you must provide the required
credentials. An SSH based solution uses CLP. All iLO2 firmware releases include support for SSH/CLP.
Proliant SSH/CLP support is included in v1.70 or later of the iLO firmware. Integrity SSH/CLP support is
included in iLO2 firmware. All iLOs can be updated to this version or later.
Table 13-2 Supported hardware for Integrity management processor license collections
Firmware supportServer typeProduct nameHardware
F.02.19RackMerlionrx2660
F.02.19RackRubyrx3600
F.02.19RackSapphirerx6600
T.03.07BladeTahitiBL860c
T.03.07BladeBoraboraBL870c
NOTE: The new iLO license collection and deployment is only supported on iLO2 devices.
License Manager Manage Licenses, Assign Licenses, Un-Assign Licenses, and Collect Remote
License Info features operate on the License Manager database. Some products manage licenses locally
on the target system in the Windows registry. In these cases, license information is collected directly from
those targets using DCOM and placed in the License Manager database. Collect Remote License Info
collects licensing information from selected target systems, if the target is an iLO using SSH. When using
Collect Remote License Info, License Manager knows the mechanism to use to automatically collect
licensing information.
Apart from early versions of PMP, all license information for HP SIM plug-ins is maintained by License
Manager in the HP SIM database. For some products, the license is stored in a licensing structure in the
Windows registry on the licensed system. License Manager employs Microsoft's remote registry API over the
DCOM protocol to assign licenses to and collect license information from those remote systems. License
information is duplicated in the HP SIM database, but licenses are managed remotely and must be periodically
collected to keep this information current. Authentication credentials for the specified systems are needed
when licenses are sent to the specified system. If WBEM authentication credentials have been provided for
a specific target, these credentials are used. For more information, see “Setting protocols and credentials
for a system or groups of systems”. If specific credentials have not been provided, each set of WBEM
credentials provided as global credentials are used in turn. For more information, see “Setting global
protocols”. If no credentials are provided, the connection is attempted using the default credentials of the
HP SIM server. The remote registry service must be started and run on candidate target systems for key
collection or assignment.
Communication with iLO2 uses the HP SIM provided SSH channel. You must provide the SSH user name
and password for each iLO. If the user name and password are common to a group of iLOs, the user name
and password can be defined for the group. HP SIM also supports sign-in credentials for iLO2 systems.
License Manager does not permanently bind (or apply) a product license to a system. Users can assign and
un-assign licenses as needed.
After a product executes a licensed operation on a system, the license is bound (locked) to that system.
License Manager can no longer move a license that has been applied or locked. Assigning a license to a
system is a way for the user to ensure that a particular type of license (permanent versus trial) is automatically
consumed by the product when it runs on that system. For remote systems, licenses are deployed to those
systems but not applied or locked. Running the product on a target system locks or applies the license.
Assigning and deploying are not the same as binding. For a remote system, a deployed license remains on
the system, but is not consumed until the associated product is used. If multiple keys and corresponding
licenses are deployed to a target, only the required numbers of licenses are consumed. The remaining licenses
are unused.
Generally, when a license is applied as part of the product operation, the license is bound (locked) and
cannot be unassigned and used elsewhere. A license deployed to a remote target cannot be recalled.
License manager 363