After enlisting IBM S822LC 8335 GTA autodetects IPMI 1.5 instead of IPMI 2.0

[Larry Michel]

After S822LC 8335 GTA is enlisted, power parameters shows IPMI 1.5 instead of IPMI 2.0.

With IPMI 1.5 instead of IPMI 2.0, I also find that doing a Power Query hangs and never errors out even if the password is wrong.

In the end, it will incorrectly show the server as Powered On even though it's powered off.

Switching it back to 2.0, and I get an error as expected. I monitored the log and I don't see anything being logged for this so I will not attach any log.

ubuntu@maas-trusty-back-may22:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=====================================-================================-============-===============================================================================
ii maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Andres Rodriguez (andreserl)]

Hi Larry,

Can you attach the output of :

bmc-config -L
ipmi-locate

Looking at the code, we do:

def bmc_supports_lan2_0():
    """Detect if BMC supports LAN 2.0."""
    output = run_command(('ipmi-locate'))
    return 'IPMI Version: 2.0' in output

[Andres Rodriguez (andreserl)]

also, after commissioning, is this the same for 1.9 and 2.0 ??

[Larry Michel (lmic)]

Hi Andres,

This is what I got:

root@entei:~# bmc-config -L
could not find inband device
root@entei:~# ipmi-locate
Probing KCS device using DMIDECODE... ERROR: permission denied

Probing SMIC device using DMIDECODE... ERROR: permission denied

Probing BT device using DMIDECODE... ERROR: permission denied

Probing SSIF device using DMIDECODE... ERROR: permission denied

Probing KCS device using SMBIOS... ERROR: permission denied

Probing SMIC device using SMBIOS... ERROR: permission denied

Probing BT device using SMBIOS... ERROR: permission denied

Probing SSIF device using SMBIOS... ERROR: permission denied

Probing KCS device using ACPI... ERROR: permission denied

Probing SMIC device using ACPI... ERROR: permission denied

Probing BT device using ACPI... ERROR: permission denied

Probing SSIF device using ACPI... ERROR: permission denied

Probing KCS device using PCI... FAILED

Probing SMIC device using PCI... FAILED

Probing BT device using PCI... FAILED

Probing SSIF device using PCI... FAILED