On MAAS 1.5+bzr1977-0ubuntu5 enlisting nodes fails to detect the BMC power type and therefore not able to create a user to control the BMC.
This is for a Cisco B200 M3 server running UCSM to control the BMC.
Running ipmitool manually on an ephemeral image or manual installation of Ubuntu 12.04.4 or 14.04 fails when trying the following:
ipmitool user list
Get User Access command failed (channel 14, user 1): Invalid command
ipmitool user set name 10 maas
Set User Name command failed (user 10, name maas): Invalid command
Running ipmitool against the system event log(sel), chassis status or lan print all work fine.
Cisco mentions that controlling ipmi directly is disabled by default as well as behind a firewall that is disabled. Going through hardware enablement for UCSM might be the better choice.
On MAAS 1.5+bzr1977- 0ubuntu5 enlisting nodes fails to detect the BMC power type and therefore not able to create a user to control the BMC.
This is for a Cisco B200 M3 server running UCSM to control the BMC.
Running ipmitool manually on an ephemeral image or manual installation of Ubuntu 12.04.4 or 14.04 fails when trying the following:
ipmitool user list
Get User Access command failed (channel 14, user 1): Invalid command
ipmitool user set name 10 maas
Set User Name command failed (user 10, name maas): Invalid command
Running ipmitool against the system event log(sel), chassis status or lan print all work fine.
Cisco mentions that controlling ipmi directly is disabled by default as well as behind a firewall that is disabled. Going through hardware enablement for UCSM might be the better choice.