Comment 24 for bug 1852678

> The question is whether this is a firmware issue with the NIC, or whether this is expected behaviour?

For background, on Power servers with the OPAL firmware (such as this one) we use an embedded Linux distribution as the boot environment. All the PXE interactions are handled by petitboot which runs in userspace rather than a PXE ROM on the NIC itself.

When no specific interface is assigned as the boot device petitboot will request an IP via DHCP on every available interface and assign it as you'd expect. You're seeing all the tftp requests from the same IP because petitboot doesn't bind the tftp client to the "correct" NIC when requesting the config file for it's MAC. I'll agree that's a bit odd and probably a bug on our end, but that is the default behaviour.

Anyway, I think you'll either need to document this a limitation which requires the user to configure a specific NIC as the boot device or re-think how things are handled on the MAAS end. If we patch petitboot to bind the tftp request to the "correct NIC" it'll still depend on SuperMicro shipping a firmware update for the system to update the bootloader since the bootloader is signed and a part of the firmware secureboot chain.