<html><head></head><body><div>Hi,</div><div><br></div><div>We have noticed while deploying Red Hat OpenStack 10 Platform, that 2017 versions of ipxe.efi file cause Intel x710 NIC failure to complete PXE-boot.</div><div><br></div><div>Comparison of 2016 and 2017 boot sequences shows a small difference, we would like to get a comment on this:</div><pre><br></pre><pre>-- after loading the <b>2016 ipxe.efi image</b> the x710 NIC is sending the DHCP Discover with
<span class="Apple-tab-span" style="white-space:pre"> </span>Option 93 Client System Architecture:<b> EFI x86-64 (9)</b>
Option 60 Vendor Class Identifier: PXEClient:Arch:<b>00009</b>:UNDI:003010
and this causes the RHOSP Director to offer to load the <a target="_blank" href="http://192.0.2.1:8088/inspector.ipxe
">http://192.0.2.1:8088/inspector.ipxe</a> then the introspection completes
-- after loading the <b>2017 ipxe.efi image</b>, the x710 NIC is sending the DHCP Discover with
Option 93 Client System Architecture:<b> EFI BC (7)</b>
Option 60 Vendor Class Identifier: PXEClient:Arch:<b>00007</b>:UNDI:003010
and this causes the RHOSP Director to offer to load the ipxe.efi file again, then PXE boot is looping</pre><pre><br></pre><pre><br></pre><pre>We have a question: could anyone please explain why the same NIC (Intel x710) with no other changes identifies it's Client System Architecture as 7 or 9, depending on the version of ipxe.efi file?</pre><pre><br></pre><pre>What is the appropriate Client System Architecture for this NIC?</pre><pre><br></pre><pre>Thanks!</pre><pre>/Konstantin</pre></body></html>