Is this page helpful?

Resolved Issues#

The following issues that were previously identified as known issues have been resolved.

PWR_SYSTEM Reports 0W Power Reading in Busbar System#

Issue#

The PWR_SYSTEM reading is pulled directly from IPMI sensors rather than the telemetry service. Consequently, the busbar system value remains at 0.

Workaround#

Reconfigure PWR_SYSTEM to pull from the telemetry service. Total system power is now calculated by summing the following metrics:

  • PWR_50V_PDB_HSC

  • PWR_PDB_MB_HSC

  • PWR_PDB_FAN_HSC

  • PWR_GB1_TOT_HSC

Status#

This issue was resolved in version 26.05.1.

Custom Domain Policy Creation Issue Encountered#

Issue#

When transitioning from DGX B200 to DGX B300, an attempt to create a custom domain policy using a JSON file results in an error similar to:

"message": " /redfish/v1/Managers/BMC/NodeManager/Domains is failed, Server provided invalid data.
Please try again after sometime."

Status#

This issue was resolved in version 26.03.1.

Custom Domain Policy Creation Issue Encountered#

Issue#

When transitioning from DGX B200 to DGX B300, an attempt to create a custom domain policy using a JSON file results in an error similar to:

"message": " /redfish/v1/Managers/BMC/NodeManager/Domains is failed, Server provided invalid data.
Please try again after sometime."

Status#

This issue was resolved in version 26.03.1.

BlueField-3 DPU Firmware Version Not Displayed in Inventory After Upgrade#

Issue#

When a BlueField-3 DPU is upgraded to a firmware version greater than 32.43.2024, the system’s inventory might not accurately display the new firmware version. The inventory might continue to show the previously installed version or no version information for the DPU.

Status#

This issue was resolved in version 26.03.1.

Redfish Service on BMC Might Experience Intermittent Unresponsiveness#

Issue#

An intermittent issue affecting several nodes where the BMC Redfish service might become unresponsive. When this happens, any attempt to query Redfish returns the following error:

"code": "Base.1.12.ServiceInUnknownState",
"message": "The operation failed because the service is in an unknown state and can no longer take incoming requests."

Workaround#

For systems that have exhibited the "code": "Base.1.12.ServiceInUnknownState" failure, follow these steps as part of updating the new BMC firmware:

Option 1: Reinitialize the Redis database using the Redfish API

  1. Perform a Redis database reset by invoking the BMC/Actions/Oem/AMIManager.RedfishDBReset action.

    curl -k -u <username>:<password> --request POST --location 'https://$BMCIP/redfish/v1/Managers/BMC/Actions/Oem/AMIManager.RedfishDBReset' --header 'Content-Type: application/json' --data '{"RedfishDBResetType":"ResetAll"}' | jq

    Example response:

    {
  "@odata.context": "/redfish/v1/$metadata#Task.Task",
  "@odata.id": "/redfish/v1/TaskService/Tasks/1",
  "@odata.type": "#Task.v1_4_2.Task",
  "Description": "Task for RedfishDBReset Task",
  "Id": "1",
  "Name": "RedfishDBReset Task",
  "TaskState": "New"
}

  2. Wait approximately 3-4 minutes for the Redfish service to recover and stabilize.

  3. Run the following curl command to reboot the BMC.

    curl -k -u <bmc-user>:<password> --request POST --location 'https://<bmc-ip-address>/redfish/v1/Managers/BMC/Actions/Manager.Reset'  --header 'Content-Type: application/json'  --data '{"ResetType":  "ForceRestart"}'

Option 2: Restore to defaults using IPMItool while preserving all configuration settings except Redfish

To preserve all configuration settings except the Redfish configuration using IPMItool:

  1. Get the current preserve configuration settings.

    $ ipmitool -H $BMCIP -I lanplus -U <username> -P <password> raw 0x32 0xBB
00 00 00 ff 77

  2. Set all preserve configuration settings except Redfish (byte 2, bit 6).

    $ ipmitool -H $BMCIP -I lanplus -U <username> -P <password> raw 0x32 0xBA 0xff 0x37

  3. Get the current preserve configuration settings.

    $ ipmitool -H $BMCIP -I lanplus -U <username> -P <password> raw 0x32 0xBB
00 ff 37 ff 77

  4. Initiate a restore to defaults, which will cause the BMC to reboot.

    $ ipmitool -H $BMCIP -I lanplus -U <username> -P <password> raw 0x32 0x66

  5. After the BMC finishes rebooting, restore all settings to their initial state.

    $ ipmitool -H $BMCIP -I lanplus -U <username> -P <password> raw 0x32 0xBA 0x00 0x00

  6. Get the current preserve configuration settings.

    $ ipmitool -H $BMCIP -I lanplus -U <username> -P <password> raw 0x32 0xBB
00 00 00 ff 77

Status#

This issue was resolved in version 26.03.1.

Instantaneous Power Reading Persists#

Issue#

The instantaneous power consumption reported by the system remains the same when the chassis power is ON, but the system power is OFF.

Status#

This issue was resolved in version 26.03.1.

Redfish BIOS Boot Order Update Not Retained After Reboot#

Issue#

Updating the BIOS boot order via Redfish might fail to take effect after a system reboot.

When initially checking the current BIOS boot order using Redfish, the reported order correctly matches the output from the local OS utility, efibootmgr. After successfully submitting a new boot order via the Redfish API and performing a system reboot, the actual boot sequence used by the system does not reflect the order set via Redfish. Specifically, the system does not boot from PXE as intended (for example, PXE/Boot0004), and the boot order reported by Redfish and efibootmgr becomes inconsistent.

Workaround#

To configure the boot order:

  1. Enter the SBIOS setup.

  2. Navigate to the Boot menu (or screen).

  3. Specify your preferred boot sequence.

Status#

This issue was resolved in version 26.03.1.

Temperature Sensors Can Report No Reading#

Issue#

The following sensors can report No Reading rather than a temperature value:

  • TEMP_PSU4

  • TEMP_PSU5

  • PWR_PSU5

  • SPD_FAN_PSU5_R

  • SPD_FAN_PSU5_R

  • STATUS_PSU0

  • STATUS_PSU1

  • STATUS_PSU2

  • STATUS_PSU3

  • STATUS_PSU4

  • STATUS_PSU5

  • STATUS_HMC

  • TEMP_PCIE_SW_1

  • TEMP_Cedar_OSFP0

  • TEMP_Cedar_OSFP1

  • TEMP_Cedar_OSFP2

  • TEMP_Cedar_OSFP3

  • TEMP_PCIE_CX7_1

  • TEMP_PCIE_CX7_2

  • TEMP_CX7_QSFP0

  • TEMP_CX7_QSFP1

  • TEMP_CX7_QSFP2

  • TEMP_CX7_QSFP3

  • TEMP_Intel_NIC

  • TEMP_NIC_QSFP0

  • TEMP_NIC_QSFP1

Workaround#

Polling the sensors again can resolve the issue.

Status#

This issue was fixed.