NVIDIA DGX B200 User Guide
▶ System/Chassis power operations
▶ Get health event log/advanced system event log
▶ Logging Service, which provides critical/informational severity events
▶ Event Services (SSE)
▶ Querying GPU power limit
▶ Power capping
Refer to the following documentation for more information:
▶ DMTF Redsh specication
▶ DSP0266 1.7.0 specication
▶ Redsh Schema 2019.1 announcement from DMTF
9.2. Connectivity Between the Host and BMC
You can congure internal network connectivity between the host and the BMC rather than using
external network connectivity and routing trac outside the host.
To congure internal network connectivity, you must congure an interface on the 169.254.0.0∕
255.255.0.0 network. The interface can then send and receive Redsh API trac between the host
and the BMC. The BMC is precongured to use the 169.254.0.17 IP address.
Run an ifconfig command like the following example to congure connectivity:
sudo ifconfig enx9638a3b292ec 169.254.0.18 netmask 255.255.0.0
Replace the network interface name and IP address in the preceding example according to your needs.
After you congure the network interface, you can use commands such as curl and nvfwupd with
the 169.254.0.17 IP address to connect to the BMC and use the Redsh API.
The following example command shows the rmware versions:
nvfwupd -t ip=169.254.0.17 username=<bmc-user> password=<password> show_version
9.3. Redsh Examples
9.3.1. BMC Manager
▶ Accounts
The following curl command changes the password for the admin user.
curl -k -u <bmc-user>:<password> --request PATCH 'https:∕∕<bmc-ip-address>∕
,→redfish∕v1∕AccountService∕Accounts∕1' --header 'If-Match: *' --header 'Content-
,→Type: application∕json' --data-raw '{"Enabled" : true, "Password" :
,→"DGXuser12345678!" , "UserName" : "admin" , "RoleId" : "Administrator" , "Locked
,→" : false}'
64 Chapter 9. Redsh APIs Support