how to backup ilo configuration hp ilo 4

How to backup ilo configuration hp ilo 4 code#

Redfish is an OData-derived protocol and data model with resources linking to other resources using '/redfish/v1/link_to_some_other_resource'} Note that the URI of the POST matches the 'target' property in 'Actions'.

How to backup ilo configuration hp ilo 4 code#

The pre-Redfish property HealthRollUp is removed in iLO 5 and HealthRollup is retained.Ĭlient code should make sure any dependencies upon the pre-Redfish 'HealthRollUp' property is replaced by Redfish-standard 'HealthRollup' ILO 'ComputerSystem.v1_1_0.ComputerSystem' ILO 'ComputerSystem.1.0.0.ComputerSystem' To determine the version of a resource, do not split the type/version by the ‘.’ delimiter. Also, the type name cannot be parsed programmatically and should be considered opaque. The type.type format has changed to type.v_.type. To preserve OData conformance, Redfish transitioned the format of properties, and iLO 5 follows this change. 'Hpe': '#HpeiLOServiceExt.v2_0_0.HpeiLOServiceExt 'Ĭlient code should look for dependencies upon the 'Hp' property and also handle 'Hpe' Oem/Hp Sections Renamed to Oem/HpeĪs part of the transition from HP to HPE, and due to the Redfish requirement that the Oem section name reflect an owned IANA name, all Oem section names are changed from Hp to Hpe. The only required header for a GET operation is the authorization ( X-Auth-Token or Authorization) header, except for the root resource at /redfish/v1/ which requires no headers. This is a change from iLO 4 where the presence of the OData-Version header caused iLO 4 to remove pre-Redfish properties from GET responses. Unlike iLO 4, the service does not behave differently based upon the presence or absence of the OData-Version header. ILO 5 assumes all requests are to Redfish REST resources are Redfish requests. Additionally, access of /redfish/v1/x redirects to /redfish/v1/x/.Ĭlient code should access the iLO RESTful API starting at /redfish/v1/ and should handle for HTTP 308 redirect. URI Remapping from /rest to /redfishįor iLO 5 all accesses of the /rest/v1/x URI pattern result in HTTP 308 redirect to /redfish/v1/x/. This enables features like $expand that require very large responses. Unlike iLO 4, iLO 5 responds to all HTTP operations using Chunked Transfer Encoding.

iLO 5 Certificate based authentication configuration.

Redfish Telemetry service for CPU metrics.

Redfish TaskService for long running operations.

Redfish Storage/Drive/Volume model for NVMe and other direct attached storage.

Redfish Role based local user administration.

Redfish Firmware Inventory and UpdateService.

Redfish Directory Authentication configuration.

Redfish Advanced Communication Device (NetworkAdapter) model for certain network adapters.

Redfish 1.6 OpenAPI 3.0 support (URIs conform to Redfish 1.6 templates).HPE Smart Storage and Logical drive configuration.iLO 5 has the following additions not implemented in iLO 4: HPE continues to extend the Redfish data model to enable value for the customer.

Any remaining support for the pre-Redfish iLO RESTful API has been removed and is replaced by the Redfish equivalents. The iLO 5 RESTful API is fully conformant with Redfish. This section is a guide to help client code adapt from the iLO 4 RESTful API to the iLO 5 RESTful API.