Find file History
Failed to load latest commit information.
img Small update on python-redfish goal Jun 15, 2016

Redfish Lab Contents

This lab purpose is to explore Redfish and become familiar with the standard as well as the extensions provided by the HPE RESTful API on HPE ProLiant servers via multiple toolsets.

Lab Writers and Trainers

Objectives of the Redfish Lab

At the end of the Lab students should be able to navigate through the various Refish fields, understand the differences between what is in the standard and the possible OEM additions, use the appropriate tools to control servers equiped with such a standard either through a Web Browser, a CLI tool or programmatically.

This Lab is intended to be trial and error so that during the session students should understand really what is behind the environment, instead of blindly following instructions, which never teach people anything IMHO. You've been warned ;-)

This Lab presents five means for retrieving and setting parameters from and to an HPE ProLiant server via the HPE RESTful API. You can work with:

  1. A web browser with the associated extension
  2. The free to use HPE hprest tool
  3. wget / curl tools
  4. PowerShell commands
  5. A python script

The following exercises are proposed for each method:

  1. Get Properties
  2. Set a property and/or perform an action

Expected duration : 120 minutes

Prerequisite knowledge

Attendees must be familiar with the following technologies:

  • HTTP basics
  • Linux commands and utilities
  • The vi or nano editors

Having some knowledge in the following technologies might also help:

  • UEFI in HPE ProLiant Gen9+ servers
  • Linux shells and scripting
  • Python scripting
  • PowerShell scripting

Of course, in case you're less familiar with these technologies, the Lab is still doable, just ask for help to your instructors in order to avoid being stuck on a related topic.

Reference documents

This lab intends to be a complement (not a substitute) to the following public documents:

When dealing with the Redfish standard, the first approach is to look at the reference Web site

Estimated time for the lab is placed in front of each part.

Environment setup

Estimated time: 20 minutes

Client setup

This Lab supposes that your client machine will run a Windows OS. If you're lucky to have a Linux one, don't worry as the instructions also apply to it as well.

Before starting the lab exercises, your client station must be installed with the following:

  1. The Firefox browser with the HttpRequester extension and HttpFox. Add them to your Firefox if it's not already installed. NOTE: Google Chrome with the Postman extension can be used as well. However, screen snapshots in this Lab have been performed with HttpRequester as this extension is easier to install in non-connected environments.
  2. An SSH client (PuTTY on Windows clients is OK)

For the rest of this Lab, each team has received a lab number (X) from the instructor, and we'll refer to your server as labX. It has the following characteristics:

  • iLO IP: (login: demopaq - password: password)
  • Server IP: (login: root - password: password)

Test first your connectivity to the iLO of your server labX with the SSH protocol. If you don't know what it means, ask your instructor. Answer Yes to the Security Alert (if needed). If the login is successful, exit from the iLO:

</>hpilo-> exit

Then test the access to your OS (a preinstalled RHEL 7 Linux distribution). Answer Yes to the confirmation query. If the login is successful, exit from the system:

# exit

Finally test and set your browser: Open the Firefox browser (if not already done). If you don’t see the following double arrow icon in the top right corner, notify the instructor.

HttpRequester Setup

From Firefox, open a session toward the iLO of your server at

If needed, click on Advanced and then on Add Exception... then Confirm Security Exception:

Insecure App

Log into the iLO. Your server should be in the OFF state. If not, warn the instructor.

Server Off

By default, modern browsers block Insecure Contents and packets coming from the iLO via the Remote Console are considered as such. In the main central pane, click on the .Net link:

.Net console

Click on the upper left locker/warning icon and then on the > sign and click on Disable protection for now:

Disable Protection

Click again on the .NET link. Push the RUN button of Security Warning popups if any. The console window should now be appear.

Of course, you don't need to do that on Linux as you'll use the Java plugin and its own security framework ;-)

REST and Redfish introduction

REST definition

Wikipedia says: “Representational State Transfer (REST) is a software architecture style consisting of guidelines [...] for creating scalable web services [...] REST [is] a simpler alternative to SOAP and WSDL-based web services.

RESTful systems typically, but not always communicate over the Hypertext Transfer Protocol with the same verbs (GET, POST, PUT, DELETE...) used by web browsers...”

Redfish definition

“Redfish is an open industry standard specification and schema that specifies a RESTful interface and utilizes JSON and OData to help customers integrate solutions within their existing tool chains.”

Hewlett Packard Enterprise started to implement its own iLO RESTful API before the Redfish 1.0 specification was published. Today iLO 4 based ProLiant servers host both the legacy iLO RESTful API and a Redfish 1.0 compliant implementation.

This hands on lab focuses on the Redfish implementation but mentions how you can switch back to the legacy iLO RESTful API.

Web browser and REST client

Although REST is primarily used via Application Programming Interfaces (APIs), it is possible to test and debug RESTful systems with a web browser and an associated extension. The extension is used to build the correct https packets (headers, payload...) and to display nicely (or not) returned answers in different formats (JSON, XML, raw...).

If you need to use a browser different from Firefox or Chrome, make sure its associated extension supports the PATCH verb/method, in addition to GET and POST. The PATCH method is a proposed standard (RFC 5789) and is required by the redfish specifications.

Now that your setup and some introduction has been done, let's start experimenting with Redfish.

Using Redfish

Estimated time: 80 minutes.

Get properties from the server

The goal of this exercise is to understand the different dialogs and syntaxes used between the client (browser) and the RESTful server.

Open the HttpRequester client:

HttpRequester Open

Redfish and the iLO RESTful API implementation requires the authentication of clients (via SSL) before using GET, POST or PATCH methods.

In these exercises, we use only the Basic Authentication mechanism primarily designed for single requests. Full session states are also supported by the iLO REST Interface, and explained in Managing HPE Servers Using the HPE RESTful API.

HttpRequester Request

  1. Supply as URL where X is your group number. (An URL starting with /rest/v1 will communicate with the legacy iLO RESTful API, not the new Redfish standard based one)

  2. Then click on Authentication and supply the privileged username (demopaq) and password (password)

  3. Submit this GET request.

In return, you get a response with status 200 OK. If not, tell your instructor. Make sure that the Pretty format box is ticked:

HttpRequester Answer

In this case (traditional rack or blade server), the Total number of “Systems” contained in this box is 1. A Moonshot server with multiple cartridges, would typically return a higher number.

The Type (Collection.1.0.0) represents the most important concept in Redfish and the iLO RESTful API. To simplify, we can consider it is the class of an object instance. We will talk again about Types later in this lab.

The link: /rest/v1/Systems/1 can be interpreted as a logical view of the first server contained in the box. It is the entry point for CPU, memory, expansion slots, power management and BIOS version properties.

To view the properties related to item 1 of this System, change the URL to the following:

The exhaustive list of properties is returned, including possible actions like the different Reset possibilities (ResetType):

HttpRequester Reset

Further down, you can see Power state.

Change the URL to /redfish/v1/Systems/1 and compare the output with the /rest/v1/Systems/1 using the bottom History pane.

HttpRequester History

You should notice that the output are nearly identical (paths are adapted).

To trigger a Redfish compliant request and get the corresponding output, you need to specify an Open Data header.

HttpRequester Open Data

  1. Click on the Headers tab of your HttpRequester
  2. Fill up the Name and Value fields as shown upper
  3. Click on the Add button
  4. Click on the Submit button

You should notice that the output is different from previous requests. For example, the Bios Version appears earlier:

HttpRequester BIOS

Note: In addition to the Systems link, the data model proposes others entry points like Chassis and Managers. The description of their content is explained in the Managing HPE Servers Using the HPE RESTful API

A partial view of the data model is:

Redfish Data Model

Using the browser extension, navigate through the Chassis link by sending the following URIs. Make sure that the OData-Version header is still present:


You should notice that the Chassis link contains physical properties of the server(s).

Perform a similar navigation in the Managers location. What is the type of content under Managers? Confirm your findings with the data model picture just above.

Send an action

This exercise sends the Power-On action to start the server. This action is possible via the Systems/1 link.

HttpRequester Action

  1. Select the POST button
  2. click on the "Headers" tab. You need to specify the type of payload you will send (application/json). The type of answers you Accept from the iLO is optional here, but it is good practice to specify: application/JSON as well.
  3. Select the "Content to send" tab and enter the JSON payload of this POST action in the editor. You should be able to cut&paste the following text: {"Action":"Reset","ResetType":"On"}

HttpRequester Content to Send

Hit the Submit button. You should get a successful answer:

HttpRequester Success

Verify in the IRC that the server is booting.

You can then kill the HttpRequester application.

The HPE RESTful Interface tool

Using a Web browser to get and set properties in a server is very useful for learning or troubleshooting. However, browsing the data model becomes quickly complex. Again, RESTful APIs are intended to be used by programs and you may not have the skills or the time to develop your own RESTful executable suitable for managing your systems.

As an intermediate solution between a browser extension and a dedicated RESTful program, HPE proposes an Open Source RESTful Interface tool. This tool hides the complexity of the underlying data model and provides a simple and easy to use mean for managing servers.

This tool can be downloaded for free from Installable packages for both Windows (.msi) and Linux (.rpm) are available. For Linux it is even easier to use the HPE SDR at

NOTE: All servers (including Gen8) featuring an ilO4 firmware equal or greater than 2.0 can be managed with this tool. However, Gen8 servers have only a limited set modifiable properties.

The HPE RESTful Interface tool is the perfect replacement for the following five STK separate tools: reboot, conrep, setbootorder, hponcfg and rbsureset.

The following exercises briefly explains the specific terminology as well as the operational modes of the tool: Interactive, scriptable and file-based.

Tool installation

Although we could use hprest from your Windows station to manage the server in an out-of-band manner, we will use it from the Linux server itself, because we want to test both out-of-band and in-band management and the SDR. Moreover, the pdsh part of this exercise is not possible on Windows.

Open a PuTTY session to the server ( with root / password for credentials and install the hprest package:

# yum install -y lsb

# wget

# chmod 755 ./

# ./ -r 7.1 hprest

# yum install -y hprest

We have to install the lsb package which is used by to determine which distribution we running on. For the moment, RHEL 7.2 is not yet supported so we point to the 7.1 repository which contains the latest packages.

From a general point of view, server resources and their properties belong to a specific “class” or Type. Type names are referenced by a string followed by a version number like in ComputerSystem.1.0.0.

To view or alter a property in a specific Type using hprest, you must:

  1. Log into the iLO4 of the server
  2. Select the Type containing the property to display or alter.

The complete list of types and associated properties are detailed in the HPE RESTful API Data Model Reference for iLO4.

Interactive mode

This mode lets you send interactive RESTful commands to get or set resources and property values:

  1. Launch the hprest tool.
  2. From the hprest > prompt, log into the iLO4 of your server for an out-of-band session.
  3. Issue the help command:

Host# hprest

hprest > login –u demopaq –p password

WARNING: Cache is activated session keys are stored in plaintext

hprest > help

In addition to the "atomic" commands (get set...), hprest provides tools performing several set of commands at once. Review the Tool list at the bottom of the help message:

hprest Help

Next, we'll change the way the server is booting:

  1. Use the bootorder BIOS COMMAND to force the system to stop at UEFI Shell during next reboot.
  2. Send the status command to view the two parameters changed by the bootorder tool.
  3. Commit the changes:

hprest > bootorder --onetimeboot=UefiShell

hprest > status

Current changes found:
ComputerSystem.1.0.0 (Currently selected)

hprest > commit

The commit commands logs you out. Login again using the in-band manner, and list all the Types (classes of objects) available:

hprest > login

WARNING: Cache is activated session keys are stored in plaintext

hprest > types

From there, select ComputerSytem.1.0.0 using the tab command completion key and list all the properties:

hprest > select comp<tab>

hprest > select ComputerSystem.<tab>

hprest > select ComputerSystem.1.0.0

hprest > ls

Modify now the AdminName property, part of type HpBios.1.2.0, with a string containing a white space, all of this in one single command (note the required comas around the property name and its value):

hprest > set "AdminName=Foo Bar" --selector HpBios.1.2.0

Issue the select command and note that the selected type is now HpBios.1.2.0:

hprest > select

Current selection: 'HpBios.1.2.0'
Nothing has yet been changed in the server. Display the status of the changes located in a server cache and commit them to the server.

hprest > status

Current changes found:
HpBios.1.2.0 (Currently selected)
        AdminName=Foo Bar

hprest > commit

Committing changes...
One or more properties were changed and will not take effect until system is reset.
Logging session out.

hprest > exit

By for Now


Script based mode

This mode allows multiple hprest directives bundled in a single shell script. Change directory to /tmp and launch again an in-band session:

Host# hprest login

List all the Types, select the HpBios.1.2.0 type and save its properties in a file:

Host# hprest types

Host# hprest select HpBios.1.2.0

Host# hprest save --filename /tmp/bios.json

File based mode

This last mode allows the load of an entire configuration file into hprest, which will send it to the managed server.

In this exercise, we'll modify the UEFI BIOS settings in order to execute automatically a networked based startup.nsh file during the startup of the UEFI Shell (remember, we previously set the next boot to UefiShell).

Using the nano or vi text editor, open /tmp/bios.json saved in the previous exercise and perform the following modifications:

  1. Assign a static IPv4 configuration to the NIC of the server (the first one found and connected)
  2. Assign a network location for the automatic startup script:.

Host# vi /tmp/bios.json

"Dhcpv4": "Disabled",
"Ipv4Address": ""
"IPv4Gateway": ""
"Ipv4SubnetMask": "",
"UefiShellStartup": "Enabled",
"UefiShellStartupUrl": "",

Save and exit the text editor (:wq for vi).

NOTE: the script name "startup.nsh" is a reserved keyword part the UEFI Shell specification. In other words, only a script called startup.nsh will be launched automatically by the Shell, whether it is located on the Internet or locally on an EFI file system (i.e. FS0: or FS1:). Think of Autoexec.bat as a reserved script name in the MS-DOS days...

Your hprest session should be still active. Hence, you can load the modified bios.json file:

Host# hprest load --filename /tmp/bios.json

To validate these modifications, we need to reset the system. Log into the ilO (demopaq / password) GUI and from the central pane, click on .NET to launch the Integrated Remote Console (if not already started):

Launch iLO

You may need, again, to allow Firefox to load unsecure content:

Firefox Insecure

Note: On the latest Chrome, the same action has to be performed, but on the right side of the URL!

From the Console, Reset the server and don’t touch anything. Just watch:

iLO Reset

Upon restart, the server detects the modifications performed via the iLO RESTful API and notifies the user it will reboot. Don’t touch anything. Just watch. Remember, we modified the Next Boot order to UefiShell, so the system will stop there:

Server Reboot

After the reboot, the UEFI Shell is launched, it fetches the startup.nsh file from the network and executes it:


Using a browser, you should be able to view the content of this startup.nsh file and understand why it generates errors; this file is used in another lab and does not find what it is looking for...

Exit from the shell and boot Linux:


Scripting with wget or curl

wget and curl are non-interactive CLI network downloaders available on Linux and Windows. They can be used to send https requests and perform actions via the iLO RESTful API. Sometimes, it is quicker, easier and more convenient to use them compared to a web-browser extension or the hprest tool.

Reuse PuTTY again to log on your server. As an example, we'll use the following command to send a Reset signal to your iLO. Watch your iLO session after launching the command.

Host# wget --header='OData-Version:4.0' --header='Content-Type:application/json' --no-check-certificate --auth-no-challenge --http-user=demopaq --http-password=password --post-data='{"Action":"Reset"}'

The above command uses a basic authentication (--auth-no-challenge) and does not require any certificate from the iLO (--no-check-certificate) and uses the usual X you need to change.

iLO Reset

A second example shows how you can send a power off signal to multiple systems, in parallel using pdsh and wget.

When the iLO is back again, login as demopaq / password. From your PuTTY session, issue the following command where [X] represents a list of a single number: yours. To really specify a list of multiple targets, you could use: [1-9] or [1,2-4,9]. But DON’T DO THAT today. Otherwise you will kill your neighbor’s server!

Note that in the following %h is a “placeholder” that will be replaced automatically by pdsh with each numbers in the list:

Host# pdsh -R exec -w[X] wget --header='OData-Version:4.0' --header='Content-Type:application/json' --no-check-certificate --auth-no-challenge --http-user=demopaq --http-password=password --post-data='{"Action":"Reset","ResetType":"ForceOff"}' https://%h/redfish/v1/Systems/1/

Of course, you are disconnected from PuTTY. From the iLO4 GUI, power on the server.

Power on Server

Once the server is rebooted, close the iLO Integrated Remote Console (IRC) to stop the UID from blinking:

Server on

Open again open a PuTTY session toward the Linux server.

The following example uses curl to change the hostname of the iLO.

Host# curl --dump-header - --insecure -u demopaq:password --request PATCH -H "OData-Version: 4.0 " -H "Accept: application/json " -H "Content-Type: application/json " --data '{"Oem": { "Hp": { "HostName": "ilo-foobar" } } }'

Although the modification is made instantly, the above command returns a message asking for a reset of the iLO to be effective.

Reset required

Sign-out from the iLO GUI (Top-Right) and refresh the page. You should see the new iLO name:

New iLO name

Python SDK

The python language and its multiple web and security related modules provides a perfect eco-system for creating RESTful for iLO programs.

The following python script is for didactic purposes only, and HPE does not support it. Use it with care. It requires python 2.7 or later. Sending low-level configuration commands can be dangerous to running systems and to avoid any problem, the user must understand what he does... NOTE: This version is not fully Redfish 1.0 compliant. A future version will be.

This python script contains several examples. We will explain how to run the first one and, if you have time, you will be able to run others.

A version of this script is present in your environment, but later you can download the latest version of this file from:

Once your Gen9 server is up and running, ssh/PuTTY to it as root (password) and cd /usr/kits. Using nano or the vi editor, edit the script:

Host# cd /usr/kits

Before launching the script, and for security reasons, you need to edit it with your favorite editor and perform at least three tasks.

Host# vi –c 1889

Supply your iLO info around line 1889:

  1. host = ’’
  2. iLO_loginname = ‘demopaq’
  3. iLO_password = ‘password’

Comment out the sys.exit call around line 1902:

# sys.exit (-1)

Move the if False: directive below exercice1 and remove leading spaces of exercise1:

ex1_change_bios_setting(host, 'AdminName', 'Mr. Rest',... )
if False:
    ex2_reset_server(host, iLO_loginname, iLO_password)
    ex3_enable_secure_boot(host, False, iLO_loginname, iLO_password)

Save the file and exit. Execute the script. It will modify the AdminName UEFI Bios parameter:

Host# python

Python script execution

Using the REST client Browser, verify that your modification is not yet in the BIOS, but still in the pending area of the BIOS. In BIOS, you should still read "AdminName": "Foo Bar":

Python script result1

In the pending area, you should see your modification:

Python script result2

NOTE: The pending area of the BIOS will updated with your modification at next reboot. Feel free to try other exercises and investigate how they have been implemented in this python script.

Scripting with PowerShell and the HPREST Cmdlets

HPE provides a suite of PowerShell Cmdlets in the PowerShell Gallery. They can be used with PS Version 5.0 coming with the Microsoft Windows Management Framework 5.0 (WMF 5) or natively with Windows10 or Windows server 2016.

Then, a SDK containing numerous examples is present in the cmdlet package or can be downloaded separately from

In this exercise, we will install the HPRESTCmdlets and launch one the examples of the SDK example file.

Your station is already equipped with the WMF 5.0 and the HPRESTCmdlets are have been downloaded (but not installed) under the Redfish-RESTful-lab folder on your Desktop.

Click on the Start tiles icon in the bottom left of the station screen, and search for PowerShell.exe. Right click on it and select Run as administrator:

Run as Admin

Issue the following install command and, if needed, type A to accept the installation from this untrusted repository:

Powershell install

Exit from this PowerShell session. From the Desktop, navigate toward in the Redfish-RESTful-lab folder present on your Desktop and then to HPRESTCmdlets\ Right click on the HPRESTExamples.ps1 file and choose Edit:

Powershell edit

Read the green comments explaining the license terms and providing the exhaustive list of cmdlets contained in the SDK. NOTE: This version of the HPRESTCmdlets is not fully compliant with Redfish 1.0. However, a future version will be. Around line 46, supply your iLO IP address (Replace X by your group number):

Powershell Line 46

The first example in this file is a function that can set a parameter in the BIOS of the server. Review the code of the Set-BIOSExamples1 function.

You can browse the other examples or go directly to example 13 around line 850. This example offers the possibility of changing the state of the UID (Indicator LED). Review the code of this function, uncomment the line calling this function (around line 899) and change the last parameter to Lit (Note the uppercase L) instead of Off if not already done:

Powershell Lit

Hit CTRL-S to save your modification and click on the green triangle icon in the top icon bar: Green Triangle

Enter the demopaq / password credentials:


Click on the Agree button of the license terms You should get a successful output like the following:

Powershell Run

From the web GUI of the iLO, verify that the UID is ON:

UID on

Feel free to test other examples.

Using python-redfish library.

Estimated time: 15 minutes

The python-redfish library is a reference implementation to enable Python developers to communicate with the Redfish API. The project is in it's infancy but already allows to retrieve information and perform few actions. The goal of this project compared to HP SDK is to stick to the Redfish standard to allow compatibility between HW providers. So not to manage the oem proprietary part provided by HW company such as HPE (or only for exceptions).

The project also comes with a client in order to interact with Redfish and is mainly used to validate the library.

This is a full 100% Free and Open Source Software, under the Apache v2 license and contributions are welcome at ! :)

Install the required repository

Install the python-redfish repository.

# cd /etc/yum.repos.d

# cat > python-redfish.repo << EOF

name=centos 7 x86_64 - python-redfish Vanilla Packages

name=centos 7 x86_64 - python-redfish Vanilla Packages

Install the EPEL repository.

# rpm -Uvh

Fix some dependencies not provided by current rpm.

# yum install -y python-future python-pbr # This is to fix some dep issues

Finally, install python-redfish.

# yum install -y python-redfish --nogpg

Using the redfish-client

Launch the binary, it should provide the usage:

# redfish-client

   redfish-client [options] config add <manager_name> <manager_url> [<login>] [<password>]
   redfish-client [options] config del <manager_name>
   redfish-client [options] config modify <manager_name> (manager_name | url | login | password) <changed_value>
   redfish-client [options] config show
   redfish-client [options] config showall
   redfish-client [options] manager getinfo [<manager_name>]
   redfish-client [options] chassis getinfo [<manager_name>]
   redfish-client [options] system getinfo [<manager_name>]
   redfish-client (-h | --help)
   redfish-client --version

Use the client to register a redfish manager. Manager is the wording used to define a management interface such as an iLO for instance.

# redfish-client config add iloX demopaq password

# redfish-client config showall

Managers configured :
    Url :
    Login : demopaq
    Password : password

Then retrieve manager data:

# redfish-client manager getinfo iloX

Gathering data from manager, please wait...

Connection error : [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
1- Check if the url is the correct one
2- Check if your device is answering on the network
3- Check if your device has a valid trusted certificat
   You can use openssl to validate it using the command :
   openssl s_client -showcerts -connect <server>:443
4- Use option "--insecure" to connect without checking   certificate

It fails, because there is no certificate installed on the Ilo.

# redfish-client manager getinfo iloX --insecure

Gathering data from manager, please wait...

Redfish API version :  1.00
HP RESTful Root Service

Managers information :

Manager id 1:
UUID : f240d59d-f156-56b7-9638-28a08615aa2f
Type : BMC
Firmware version : iLO 4 v2.40
Status : State :  / Health :
Ethernet Interface :
    Ethernet Interface id 1 :
    Manager Dedicated Network Interface
    FQDN :
    Mac address : FC:15:B4:93:12:4C
    Address ipv4 :
    Address ipv6 : FE80::FE15:B4FF:FE93:124C
Managed Chassis :
Managed System :

Now retrieve system data:

# redfish-client system getinfo iloX --insecure

Gathering data from manager, please wait...

Redfish API version :  1.00
HP RESTful Root Service

Systems information :

System id 1:
UUID : 30373237-3632-5A43-3235-303231315947
Type : Physical
Manufacturer : HPE
Model : ProLiant BL460c Gen9
SKU : 727026-B21
Serial : CZ250211YG
Hostname : lab1
Bios version : I36 v2.00 (12/15/2015)
CPU number : 1
CPU model : Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz
Available memory : 16 GB
Status : State : OK / Health : OK
Power : On
Description : Computer System View
Chassis : 1
Managers : 1
IndicatorLED : Off

Ethernet Interface :
    This system has no ethernet interface

Simple Storage :
    This system has no simple storage

Enable debugging information:

# redfish-client system getinfo iloX --insecure --debug=3

Lots of debugging info !

Using the python-redfish library directly

Use the client to register a redfish manager as default entry.

# redfish-client redfish-client config add default demopaq password

The library comes with a simple example called '' to use the library itself.

# cd /usr/share/doc/python-redfish-0.420160520014518

# more

For the moment, please comment all the lines containing 'set_parameters'. Then you can run:

# python

Now you can look at the python code to get data and perform some actions. The library documentation is available at: The classes are defined here:

You can then comment/uncomment and modify the code to experiment. e.g. below:

Retrieve manager bios version:


Retrieve chassis manufacturer:


Print chassis type:


Uncommenting the following line should reboot the system:

# mySystem.reset_system()

Debuging rest calls with httpfox

Estimated time: 5 minutes

httpfox is a firefox extension that could be used to catch the http/https requests done by the browser. This is really useful to debug REST calls. Another usage is also to know the calls done by an existing application (reverse engineering). As an example, this Firefox extension helps the author to know and better understand the calls sent by HPE OneView application to the HPE OneView API to build dynamic profile automation.

  1. Prepare http fox open it.
  2. Prepare http requester.
  3. Click on the start button of httpfox to listen to browser calls. Httpfox listen
  4. Sent a query via httprequester. Httpfox post
  5. Stop httpfox.

You can now inpect the query within httpfox.

In the example below, you can see that an authentication query was posted and the token provided by the redfish API to authenticate next calls. Httpfox inspect


The iLO RESTful API provides a rich set of means to display and modify HPE ProLiant servers. Just choose the one suiting best your needs: browser extension, hprest, wget/curl or python. For Windows users, PowerShell is an alternative as well.