User Manual

4-44

Chapter 4: Redfish Technology Pack

4.3.12 EthernetInterface

A. Systems

This resource shall be used to represent host side NIC resources. This requires host agent

support from OS and in-band communication channel.

• In BMC, Redfish Inventory population for this API can be achieved by one of

the 2 methods and is available as part of Build Time PRJ Selection “Inventory

Configuration”:

- HostInterface

- SMBIOS

Northbound API is supported but still requires host agent support from host agent and

in-band communication channel and platform specific porting needed.

• Host Agent should be running in Host and should be capable to send this information

through a channel created between Host & BMC like IPMI/KCS/USB interface etc or

by some other proprietary protocol.

• Sync agent OEM extension should be written in which this data should be written onto

redis db. Customer can refer to section 1.3 in “How to add OEM Extensions” for it.

• Key to populate on redisdb:

SET Redfish:Systems:Self:EthernetInterfaces:{{Interface1}}:

Example:

SET Redfish:Systems:Self:EthernetInterfaces:

eth0:ResourceExists:Name eth0

B. Managers

This resource shall be used to represent the NIC resources in the manager.

• GET - EthernetInterface Instance

- Request for EthernetInterface Instance

https://{{ip}}/redfish/v1/Managers/{{manager_instance}}/

EthernetInterfaces/{{manager_ethifc_instance}}

Content-Type: application/json

- Response

The response of the request will be in JSON format. The properties are mentioned in

the following table.

Manager Ethernet Interface typically supports at max one VLAN per interface for a single

BMC.

E16160_ASMB9-iKVM_UM_V3.indb 44E16160_ASMB9-iKVM_UM_V3.indb 44 1/17/2020 2:29:27 PM1/17/2020 2:29:27 PM