mirror of https://git.proxmox.com/git/fwupd synced 2025-05-28 18:57:37 +00:00

History

Richard Hughes b3f9841924 Support more than one protocol for a given device Devices may want to support more than one protocol, and for some devices (e.g. Unifying peripherals stuck in bootloader mode) you might not even be able to query for the correct protocol anyway.		2021-03-01 16:14:36 +00:00
..
fu-plugin-redfish.c	Use FWUPD_COMPILATION define to indicate an in tree build	2021-01-22 14:01:25 -06:00
fu-redfish-client.c	Support more than one protocol for a given device	2021-03-01 16:14:36 +00:00
fu-redfish-client.h	Only include the start year in the copyright header	2021-01-07 14:48:16 +00:00
fu-redfish-common.c	Only include the start year in the copyright header	2021-01-07 14:48:16 +00:00
fu-redfish-common.h	Only include the start year in the copyright header	2021-01-07 14:48:16 +00:00
fu-self-test.c	Only include the start year in the copyright header	2021-01-07 14:48:16 +00:00
meson.build	Move the plugin build logic to the plugins themselves	2021-02-18 14:46:20 +00:00
README.md	Add a new internal flag to opt-in to GUID matching	2021-02-25 15:47:25 +00:00
redfish.conf	redfish: Add an option for CA verification	2018-08-06 06:19:56 +01:00

README.md

Redfish Support

Introduction

Redfish is an open industry standard specification and schema that helps enable simple and secure management of modern scalable platform hardware.

By specifying a RESTful interface and utilizing JSON and OData, Redfish helps customers integrate solutions within their existing tool chains.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in an unspecified binary file format.

This plugin supports the following protocol ID:

org.dmtf.redfish

GUID Generation

These devices use the provided GUID provided in the SoftwareId parameter without modification. Devices without GUIDs are not supported.

Update Behavior

The firmware willl be deployed as appropriate. The Redfish API does not specify when the firmware will actually be written to the SPI device.

Vendor ID Security

No vendor ID is set as there is no vendor field in the schema.

Setting Service IP Manually

The service IP may not be automatically discoverable due to the absence of Type 0x42 entry in SMBIOS. In this case, you have to specify the service IP to RedfishUri in /etc/fwupd/redfish.conf

Take HPE Gen10 for example, the service IP can be found with the following command:

# ilorest --nologo list --selector=EthernetInterface. -j

This command lists all network interfaces, and the Redfish service IP belongs to one of "Manager Network" Interfaces. For example:

{
  "@odata.context": "/redfish/v1/$metadata#EthernetInterface.EthernetInterface",
  "@odata.id": "/redfish/v1/Managers/1/EthernetInterfaces/1/",
  "@odata.type": "#EthernetInterface.v1_0_3.EthernetInterface",
  "Description": "Configuration of this Manager Network Interface",
  "HostName": "myredfish",
  "IPv4Addresses": [
    {
      "SubnetMask": "255.255.255.0",
      "AddressOrigin": "DHCP",
      "Gateway": "192.168.0.1",
      "Address": "192.168.0.133"
    }
  ],
  ...

In this example, the service IP is "192.168.0.133".

Since the conventional HTTP port is 80 and HTTPS port is 443, we can set RedfishUri to either "http://192.168.0.133:80" or "https://192.168.0.133:443" and verify the uri with

$ curl http://192.168.0.133:80/redfish/v1/

$ curl -k https://192.168.0.133:443/redfish/v1/

External interface access

This requires HTTP access to a given URL.