With the completion of launch pad 1852328 [0], two change lists are under reviewed ([1][2]). After both change lists are merged, the way of provisioning board management control will be changed and the board management control settings will be configured as per-host basis. The new board management types are: none -- board management control is not provisioned redfish ipmi dynamic -- will try redfish then ipmi There are 2 ways to provision board management control 1. when adding a node, set bm_type, bm_ip, bm_username and bm_password, with the system command below: system host-add -n <host-name> -p <personality> -m <mgmt-mac> -I <board management IP> -U <board management username> -P <board management password> -T <board management type redfish|ipmi|dynamic> board management type is optional with default is 'dynamic' when board management IP and username are both provided. 2. after a node is added, set bm_type, bm_ip, bm_username and bm_password, with the system command below: system host-update <host-name> bm_ip=<board management IP> bm_username=<board management username> bm_password=<board management password> bm_type=<board management type redfish|ipmi|dynamic> The system command below can be used to deprovision board management control to a host: system host-update <host-name> bm_type=none The corresponding horizon GUI is also changed as attached screenshot (bmc-horizon.JPG). Additionally, bmc_access_method is no longer a valid service parameter. The system service-parameter commands to access such service parameter are invalid: system service-parameter-modify platform maintenance bmc_access_method=<...> system service-parameter-add platform maintenance bmc_access_method=<...> [0] https://bugs.launchpad.net/starlingx/+bug/1852328 [1] https://review.opendev.org/#/c/697177 [2] https://review.opendev.org/#/c/697175 Regards, Bin