DM-
SV01 Server ● BMC User Manual ● Rev. 2.1
56
3 Redfish API
The Redfish API is available at the DM-SV01 BMC as a standard way to manage several system
resources using the HTTP. The DM-SV01 redfish schema can be accessed by a web browser by means
of the URL below:
● https://<BMC_IP>/redfish/v1
After accessing the link above, the user is able to navigate throughout the links of the DM-SV01 redfish
interface in the web browser and access the resources available at the BMC, such as sensors, system
inventory data, etc.
The sections “3.1 HTTP Methods” and “3.2 HTTP responses” show general information regarding HTTP
methods and responses used for accessing the
redfish resources of the BMC. The section “3.3 Using
Redfish with RESTful APIs
” lists several available management resources and how to interact with each
one of them.
3.1 HTTP Methods
The HTTP methods below are available for the user to implement specific actions using the Redfish
interface.
Method
Description
POST
Create a resource in the specified resource collection.
GET
Retrieve a resource.
PUT
Replace an existing resource.
PATCH
Partially modify or update an existing resource.
DELETE
Remove completely a resource.
Table 4: HTTP resources description
3.2 HTTP responses
When an HTTP method is issued by the client, the server (BMC) answers the request with a
corresponding status code, depending on the result of the operation. The response status codes are
divided into five groups, each one starting with a specific digit.
● 1xx: Informational responses: the request was received, but the process is still continuing.
● 2xx: Successful responses: the request was received, understood and accepted.
● 3xx: Redirection messages: further actions are required to complete the request.
● 4xx: Client error responses: the request contains invalid syntax or cannot be fulfilled.
● 5xx: Server error responses: the request is aparentelly valid but cannot be fulfilled.
The tables from section “3.2.1 Informational Status Codes” list all response codes available. The
response codes are defined by the RFC9110 (3).