HP Systems Insight Manager 7.2 Technical Reference Guide

must support SSH and you must provide the required credentials. An SSH based solution uses CLP.
All management processor firmware releases include support for SSH/CLP. ProLiant SSH/CLP
support is included in v1.70 or later of the management processor firmware. Integrity SSH/CLP
support is included in management processor firmware. All management processors can be updated
to this version or later. The license collection uses an HTTP based mechanism and operates without
credentials. Management processor firmware in many instances allows the user to define if license
information is available on demand using this mechanism.
Table 1 Supported hardware for Integrity management processor license collections
Firmware supportServer typeProduct nameHardware
F.02.19 or greaterRackMerlionrx2660
F.02.19 or greaterRackRubyrx3600
F.02.19 or greaterRackSapphirerx6600
T.03.07 or greaterBladeTahitiBL860c
T.03.07 or greaterBladeBoraboraBL870c
NOTE: The new management processor license collection is supported on management processor
and management processor devices. Deployment is supported on management processor and
management processors with newer firmware versions.
In some instances, licenses are managed and controlled by the licensed system (remote licensing).
In this case, License Manager provides the facility to collect and deploy licenses to those systems.
For non-management processor systems, communication used is a Microsoft DCOM mechanism.
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. If specific credentials have not
been provided, each set of WBEM credentials provided as global credentials are used in turn. 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.
NOTE: Management processors have used two key formats (key format v0 and the current v1).
The original v0 license key has limited support in License Manager. License input using a v0 key
fails. However, it is rare that you will encounter a v0 key license. All v1 key licenses work. Both
v0 and v1 keys can be collected, but only v1 keys can be deployed.
NOTE: Automatic collection of management processor licenses is not supported.
NOTE: You do not have support or upgrade options by default. After July 9, 2007, all license
keys are included in one year of 24 x 7 Software Technical Support and Update Service. The
License Manager informs you which license keys are "support and update enabled" and which
license keys require the purchase of future updates and upgrades.
CLI mxlmkeyconfig
The CLI mxlmkeyconfig allows you to combine all the License Manager key files into one file instead
of having to execute multiple files. Combining these files into a single file makes it easier when
adding keys from a file through the License Manager graphical user interface (GUI).
The mxlmkeyconfig command takes all the keys and related information and places it in the resulting
key file. The CLI program will not allow duplicates. If there are duplicate <keystring> values, a
License Manager 27