Skip to content

fix: add a note on DGX's FW_RESET_AFTER_CONFIG_UPDATE env var feature… #281

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2025
Merged

fix: add a note on DGX's FW_RESET_AFTER_CONFIG_UPDATE env var feature… #281

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/nic-conf-operator/nic-fw-configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,9 @@ Install the NIC Configuration Operator and observe NIC devices in the cluster
After deploying the NFS server and NFS CSI driver, the `storage class <https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/deploy/example/storageclass-nfs.yaml>`_ should become available in the cluster. The name of the storage class should then be passed when configuring the NIC Configuration Operator.
To disable the Firmware upgrade and validation logic, do not define the ``nicFirmwareStorage`` section in the NicClusterPolicy CR.

.. note::
On some DGX servers, the configuration update is not successfully applied after the warm reboot. In this case, it is recommended to explicitly reset the NIC's Firmware before the reboot and after updating its non-volatile configuration. This can be achieved by specifying the ``FW_RESET_AFTER_CONFIG_UPDATE`` environment variable in the NicClusterPolicy CR. Please see the commented section in the example below.

First install the Network Operator helm chart with the Maintenance Operator enabled and deploy a NIC Cluster Policy CRD with NIC Configuration Operator and DOCA-OFED Driver enabled:

``values.yaml``:
Expand Down Expand Up @@ -111,6 +114,11 @@ First install the Network Operator helm chart with the Maintenance Operator enab
image: nic-configuration-operator-daemon
repository: |nic-configuration-operator-repository|
version: |nic-configuration-operator-version|
# Uncomment to explicitely reset the NIC's Firmware before the reboot and after updating its non-volatile configuration.
# Might be required on DGX servers where configuration update is not successfully applied after the warm reboot.
# env:
# - name: "FW_RESET_AFTER_CONFIG_UPDATE"
# value: "true"
nicFirmwareStorage:
create: true
pvcName: nic-fw-storage-pvc
Expand Down