You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our current implementation, we use MAC address to identify Redfish network interface. However, from OpenBMC implementation, the MAC on host side is different from the MAC on BMC side. BMC engineer suggest us to use VID and DID in order to identify the network interface on BMC.
SMBIOS type 42 provides this information as below
If this is the case, we need to update RedfishConfigHandler driver.
The text was updated successfully, but these errors were encountered:
We probably still use MAC address because network protocol can only provide MAC address of NIC. MAC address is defined in Host Interface specification so we can use this.
Locate all EFI Device Path Protocol
Check if both USB device path and MAC device path specified in the EFI Device Path
If yes, get the MAC address from EFI Device Path
Go through all IPMI channels,
Send IPMI NetFn: Net Parameter selector:5 Get MAC address)
Compare the MAC address specified in EFI Device Path ( Step 2) and the one retrieved via step 4.
If matched, this is the USB NIC exposed by BMC.
In our current implementation, we use MAC address to identify Redfish network interface. However, from OpenBMC implementation, the MAC on host side is different from the MAC on BMC side. BMC engineer suggest us to use VID and DID in order to identify the network interface on BMC.
SMBIOS type 42 provides this information as below
If this is the case, we need to update RedfishConfigHandler driver.
The text was updated successfully, but these errors were encountered: