The iLO License service is an OEM Redfish data type composed of the collection service and the service itself.
Refer to the iLO Licensing Guide for more information on iLO licenses.
This section provides examples for managing the iLO license featuring cURL and iLOrest with its built-in ilolicense macro command.
By default (i.e. factory defaults), iLO contains a license with empty properties. Hence the number of members in the HpeiLOLicenseCollection is one. This number never increments.
The following example retrieves the license properties of an iLO 6 based server.
The iLO license collection can have only one license. Hence, you can use the ?only query parameter to expand the only member of the collection
GET {{iloURI}}/redfish/v1/Managers/1/LicenseService/?onlyiLOrest features the macro ilolicense command for managing the iLO license.
ilorest login <ilo-ip> -u <ilo-user> -p password
ilorest ilolicense
ilorest logoutTo install a license for the first time or to renew/upgrade/downgrade a license, use a POST request to the HpeiLOLicense service URI . This operation overrides the currently installed license.
A successful iLO license installation returns a 201 HTTP code as well as the OpenData error object containing the successful Base.*.Created Message Id. Although receiving the error object may be confusing for a successful operation, it is fully compliant with the Redfish specification.
POST /redfish/v1/Managers/1/LicenseService/
Body:
{"LicenseKey": "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"}A Python example using the HPE Python Redfish library is available in the HPE GitHub repository.
When you uninstall the iLO license, the HpeiLOLicenseCollection data type still contains one member, but this only member has mostly empty fields.
DELETE /redfish/v1/Managers/1/LicenseService/1/