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.

[sathishas89]

Hi @smangali-qc,

Based on the clarification from Vincent and the EBBR specification, the expected compliance behavior is as follows:

If the platform has a network device, then EFI_SIMPLE_NETWORK_PROTOCOL (SNP) is a mandatory requirement as defined by the EBBR specification, regardless of whether network boot is intended to be used.
Therefore, the SCT failure is expected when the required network protocols are not implemented on a platform with network hardware.
Since this represents a specification compliance requirement rather than a test limitation, this test case is not eligible for waiver through the ACS waiver mechanism.

Accordingly, the current SCT behavior is correct and no changes are required on the ACS side for this test.

If you do not require any further clarification on this topic, shall we proceed with closing this ticket?

Regards,
Sathisha S

[sathishas89]

Hi @smangali-qc ,
Any update on this issue?

Regards,
Sathisha S

[smangali-qc]

HI @sathishas89 ,

SNP is a binding protocol that is typically installed only after the Ethernet controller is successfully detected and initialized.

Could you please check on other platforms whether the SNP protocol is installed even when no Ethernet cable/device is connected? This would help us determine whether the behavior is platform-specific or expected.

Regards,
shiva kumar

[sathishas89]

Hi @smangali-qc,

Verified the behavior on one of our reference platforms with both Ethernet cable connected and Ethernet cable disconnected.

The relevant SCT results are identical in both cases:

Without Ethernet cable connected:

UEFI Compliant - Boot from network protocols must be implemented -- PASS
PXE BC - Yes, SNP - Yes, MNP - No, UNDI - No

With Ethernet cable connected:

UEFI Compliant - Boot from network protocols must be implemented -- PASS
PXE BC - Yes, SNP - Yes, MNP - No, UNDI - No

From this verification, the presence of the Ethernet cable does not affect the installation or detection of the network boot protocols. The SNP protocol is available in both scenarios, indicating that it is installed when the network controller is initialized rather than depending on the physical link status.

Regards,
Sathisha S