BladeSystem Management Software

Detect iLO Advance license through script?

 
chuckk281
Trusted Contributor

Detect iLO Advance license through script?

Richard had a question on how to get iLO license info:

 

******************************

 

Is there a way to detect whether the iLO advance License has been activated through a OS script?

 

******************************

 

Terry provided a great answer:

 

******************************

 

In the “HP BladeSystem ProLiant Firmware Management Best Practices Implementer Guide” there is a section on Validating the iLO Advanced license:

http://h18004.www1.hp.com/products/servers/management/literature.html

 

see page 88 below, I tried this on a DL385 G6 (Linux) output below:

 

# hponcfg -f get_info.xml

Firmware Revision = 1.10 Device type = iLO 3 Driver name = hpilo

<GET_FW_VERSION

   FIRMWARE_VERSION = "1.10"

   FIRMWARE_DATE = "Jul 26 2010"

   MANAGEMENT_PROCESSOR = "iLO3"

   LICENSE_TYPE = "iLO 3 Advanced HP limited-distribution date-restricted test"

    />

Script succeeded

 

Or:

 

# hponcfg -f get_info.xml | grep LICENSE_TYPE

   LICENSE_TYPE = "iLO 3 Advanced HP limited-distribution date-restricted test"

 

Page 88:

Validating the iLO Advanced License is installed on each blade

Now that we have a way to obtain a list of iLO IP addresses as shown above, we need to write several RIBCL XML files that is used later to build our scripts. The XML files contain the same format and data regardless of whether or not we plan to execute the m from a Windows or Linux system.

Note:

The login name and password within the RIBCL XML file is not used. It is there because iLO requires an entry in this field. Set the Password field to DoesNotMatter to show it doesn’t matter what you put in these fields, as long as it is valid XML data.

The XML file below is named Get_ILO_Firmware_Version.xml in the scripts created later. It is the same as the command to retrieve the iLO firmware version information below, but for clarity purposes, a separate XML file is created. <!-- FDT RIBCL Sample Script for HP Lights-Out Products -->

<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to insert a virtual -->

<!-- media image -->

<RIBCL VERSION="2.0">

<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">

<RIB_INFO MODE="read">

<GET_FW_VERSION/>

</RIB_INFO>

</LOGIN>

</RIBCL

 

When we create a script later, the output from issuing this XML file against the iLO is similar to the output example follows. <?xml version="1.0"?>

<RIBCL VERSION="2.22">

<RESPONSE

STATUS="0x0000"

MESSAGE='No error'

/>

<GET_FW_VERSION

FIRMWARE_VERSION = "1.78"

FIRMWARE_DATE = "Jun 10 2009"

MANAGEMENT_PROCESSOR = "iLO2"

LICENSE_TYPE = "iLO 2 Standard Blade Edition"

/>

</RIBCL>

 

This output means the blade does not have an iLO Advanced license. Because of this, the blade is unable to support scriptable virtual media and must use the OA GUI (as described in Scenario 1B: Updating a server using the HP BladeSystem FDT.) to update an enclosure through the OA Virtual Media pass-through feature. Output similar to the following example means the blade is supported for scriptable virtual media. <?xml version="1.0"?>

<RIBCL VERSION="2.22">

<RESPONSE

STATUS="0x0000"

MESSAGE='No error'

/>

<GET_FW_VERSION

FIRMWARE_VERSION = "1.79"

FIRMWARE_DATE = "Aug 26 2009"

MANAGEMENT_PROCESSOR = "iLO2"

LICENSE_TYPE = "iLO 2 Advanced"

/>

</RIBCL>

 

*********************************

 

Comments? Have you tried this script?