I checked the firmware and it looks like it's the recommended "prod" level.
Petitboot System Information:
System type: 8001-22C
System id: C829UAF04B10265
Primary platform versions: open-power-IBM-P8DTU-V2.00.GA2.SP1-20180105-prod op-build-4059438 hostboot-7fdfb37
occ-301b535 skiboot-5.4.2-2a21b57 linux-4.4.24-openpower1-48c3582 petitboot-v1.4.0-ee0f918 p8dtu-xml-04e8a01
BMC current side:
Device ID: 0x20
Device Rev: 0x1
Firmware version: 1.27.00000
IPMI version: 2
Since I booted manually into Petitboot anyway, I verified what's possible there to avoid PXE boot from multiple interfaces. And it looks like it can be configured / restricted.
I changed the Petitboot settings to only allow nw boot from enP2p1s0f0 and only allow DHCP on that same, single interface, too - looks now like this:
Petitboot (v1.4.0-ee0f918) 8001-22C C829UAF04B10265
──────────────────────────────────────────────────────────────────────────────
[Network: enP2p1s0f0 / 0c:c4:7a:89:f0:64]
execute
netboot enP2p1s0f0 (pxelinux.0)
[Disk: sda2 / bdbebffe-6fa8-4783-a82b-3b470dd78440]
Ubuntu, with Linux 5.4.0-12-generic (recovery mode)
Ubuntu, with Linux 5.4.0-12-generic
Ubuntu
System information
System configuration
System status log
Language
Rescan devices
Retrieve config from URL
*Exit to shell
After booting (an already existing) test Ubuntu from disk, I was able to verify that all interfaces are (still) there (as expected, just double-checked).
I then commissioned the system again and deployed it using MAAS - it all worked fine.
And afaics it only did PXE from one interface.
So it 'seems' like it is now fixed with the Petitboot re-config.
So would you be able to re-try, Jeff?
PS: I think we didn't faced such an issue before, because we usually only have one port connected to the nw, to not waste too many switch ports. But for this machine it was recently requested to have all ports connected...
I checked the firmware and it looks like it's the recommended "prod" level.
open-power- IBM-P8DTU- V2.00.GA2. SP1-20180105- prod
op-build- 4059438
hostboot- 7fdfb37
skiboot- 5.4.2-2a21b57
linux- 4.4.24- openpower1- 48c3582
petitboot- v1.4.0- ee0f918
p8dtu- xml-04e8a01
Petitboot System Information:
System type: 8001-22C
System id: C829UAF04B10265
Primary platform versions:
occ-301b535
BMC current side:
Device ID: 0x20
Device Rev: 0x1
Firmware version: 1.27.00000
IPMI version: 2
Since I booted manually into Petitboot anyway, I verified what's possible there to avoid PXE boot from multiple interfaces. And it looks like it can be configured / restricted.
I changed the Petitboot settings to only allow nw boot from enP2p1s0f0 and only allow DHCP on that same, single interface, too - looks now like this:
Petitboot (v1.4.0-ee0f918) 8001-22C C829UAF04B10265 ─────── ─────── ─────── ─────── ─────── ─────── ─────── ─────── ─────── ─────── ── 6fa8-4783- a82b-3b470dd784 40]
──────
[Network: enP2p1s0f0 / 0c:c4:7a:89:f0:64]
execute
netboot enP2p1s0f0 (pxelinux.0)
[Disk: sda2 / bdbebffe-
Ubuntu, with Linux 5.4.0-12-generic (recovery mode)
Ubuntu, with Linux 5.4.0-12-generic
Ubuntu
System information
System configuration
System status log
Language
Rescan devices
Retrieve config from URL
*Exit to shell
After booting (an already existing) test Ubuntu from disk, I was able to verify that all interfaces are (still) there (as expected, just double-checked).
I then commissioned the system again and deployed it using MAAS - it all worked fine.
And afaics it only did PXE from one interface.
So it 'seems' like it is now fixed with the Petitboot re-config.
So would you be able to re-try, Jeff?
PS: I think we didn't faced such an issue before, because we usually only have one port connected to the nw, to not waste too many switch ports. But for this machine it was recently requested to have all ports connected...