SCT wavier for boot from network test

[smangali-qc]

HI @chetan-rathore ,

we are unable to bypass the test result from wavier.json in SCT. as we know boot from network is an optional test , but still it is blocking the sct compilance .

here is the SCT report could you please check and update

sct_summary.html

Regards,
Shiva Kumar

[chetan-rathore]

Hi @smangali-qc,

If feasible, could you please share the SCT results JSON and waiver JSON so we can review them in detail on our side?

Regards,
Chetan

[smangali-qc]

HI @chetan-rathore ,
here is the wavier .json and sct.json. let me know what change is needed to make it waiver .

BTW, can you confirm boot from network is an optional test or not.

acs_waiver.json

sct.json

regards,
shiva kumar

[sathishas89]

Hi Shiva Kumar,
As of now, acs-waiver applies waivers at the Test Suite level only. It does not currently apply waivers at the Sub Test Suite or Test Case level.
For your case, the Test Suite is GenericTest, and it is marked as not waivable.

We will discuss internally on your use case and we will share our feedback shortly.

Regards,
Sathisha S

[sathishas89]

Hi Shiva Kumar,

Regarding the waiver request for the "UEFI Compliant - Boot from network protocols must be implemented" test case, the SCT failure indicates that the required UEFI network boot protocols are not present:

PXE BC – No
SNP – No
MNP – No
UNDI – No

The EBBR specification (Section 2.2.2 – Required Platform-Specific Elements) explicitly states:

"EFI_SIMPLE_NETWORK_PROTOCOL – Required if the platform has a network device."

It also states:

"HTTP Boot – Required if the platform supports network booting."

Although EBBR does not require the EFI_PXE_BASE_CODE_PROTOCOL itself (it is listed as a notable deviation because PXE boot is considered insecure), the SCT checks for the presence of UEFI network boot-related protocols, including SNP and PXE BC.

Since the platform has a network device, the absence of the required EFI_SIMPLE_NETWORK_PROTOCOL (SNP) represents a compliance issue rather than a test limitation. Therefore, this test case is a valid failure and should not be waived through the ACS waiver process.

Regards,

Sathisha S

[smangali-qc]

HI @chetan-rathore ,

For our product, we do not support or implement any UEFI network boot use cases. Consequently, the network-related UEFI protocols are not present in the firmware. What is the recommended approach for compliance in this scenario?

The EBBR specification states:
"EFI_SIMPLE_NETWORK_PROTOCOL – Required if the platform has a network device."

Does this imply that the SCT suite has detected a network device on the platform and is therefore validating the presence of the network boot protocols? If network hardware is present but network boot is not a supported use case, what is the expected compliance requirement?

Regards,
shiva kumar

[vstehle]

Dear @smangali-qc,

EBBR requires the EFI_SIMPLE_NETWORK_PROTOCOL "if the platform has a network device".

Best regards,
Vincent.