Comment 9 for bug 1300476

This isn't exactly a matter of detection alone. The Cisco B series uses UCSM to control it's BMC. We will need to work with the HWE team to build in support for UCSM as this is the preferred method of controlling the BMC per Cisco.

That said, just to make sure things work ok, we worked with Cisco to enable their implementation of IPMI following along with: http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-0/b_UCSM_GUI_Configuration_Guide_2_0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_011100.html#d129007e3491a1635

This will allow us to hard code a username and password for IPMI for all blades in the chassis and utilize IPMI to powercycle the blades. This does not include IPMI functionality to create or edit IPMI authenticated users which is what MASS tries to do.

After enabling IPMI and manually setting the power settings for each node to IPMI and IPMI 2.0 and adding in the hard coded credentials, MAAS was able to start and stop nodes without issue.

We also ran into bug 1293791 again and had to delete the offending lines from the ipmi.template file in /etc/maas/templates/power/

Another issue we ran into which might end up being created as a separate bug was the usb flash drive(s) being detected as /dev/sda and utilizes as the /target installation which promptly runs out of space. I will know more tomorrow once Cisco removes the usb drive(s) and we restart the installations.