| 2023-06-11 18:44:56 |
Jeff Lane |
description |
When enlisting recent Lenovo machines, I've noticed that MAAS is setting the Cipher Suite ID to 3. This is incorrect and makes ipmi-over-lan fail.
These machines all use Cipher Suite 17 and I have to manually modify them in MAAS to use ID 17, at which point MAAS can successfully control them remotely. |
When enlisting recent Lenovo machines, I've noticed that MAAS is setting the Cipher Suite ID to 3. This is incorrect and makes ipmi-over-lan fail.
These machines all use Cipher Suite 17 and I have to manually modify them in MAAS to use ID 17, at which point MAAS can successfully control them remotely.
Note, in this most recent case (SR635 V3 with XCC 2) it set the cipher suite id to 3 during enlistment. I had to change it manually to commission. After commissionin, MAAS had changed it back to 3 again, once more making the machine unmanageable. |
|
| 2023-06-13 14:42:24 |
Jeff Lane |
description |
When enlisting recent Lenovo machines, I've noticed that MAAS is setting the Cipher Suite ID to 3. This is incorrect and makes ipmi-over-lan fail.
These machines all use Cipher Suite 17 and I have to manually modify them in MAAS to use ID 17, at which point MAAS can successfully control them remotely.
Note, in this most recent case (SR635 V3 with XCC 2) it set the cipher suite id to 3 during enlistment. I had to change it manually to commission. After commissionin, MAAS had changed it back to 3 again, once more making the machine unmanageable. |
When enlisting recent Lenovo machines, I've noticed that MAAS is setting the Cipher Suite ID to 3. This is incorrect and makes ipmi-over-lan fail.
These machines all use Cipher Suite 17 and I have to manually modify them in MAAS to use ID 17, at which point MAAS can successfully control them remotely.
Note, in this most recent case (SR635 V3 with XCC 2) MAAS set the cipher suite id to 3 during enlistment. I had to change it manually to get commissioning to work. After commissioning, MAAS changed it back to ID 3 again, once more making the machine unmanageable. So had to correct this a second time, resetting it once again to 17 |
|
