Hello Everyone,
We encounter an issue using multiple BMC network interfaces under 30-maas-01-bmc-config commissioning script.
Depending on what we would like to accomplish we had to patch like this :
--- 30-maas-01-bmc-config 2022-11-30 06:56:20.108519941 +0100
+++ 29-Kontron-me1210-bmc-second-interface 2022-11-30 06:56:20.392523595 +0100
@@ -21,7 +21,7 @@
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
# --- Start MAAS 1.0 script metadata ---
-# name: 30-maas-01-bmc-config
+# name: 29-Kontron-me1210-bmc-second-interface
# title: Detect and configure BMC's for MAAS use.
# description: Detect and configure BMC credentials for MAAS use.
# tags: bmc-config
@@ -174,7 +174,7 @@ class IPMI(BMCConfig):
def _bmc_get_config(self, section=None):
"""Fetch and cache all BMC settings."""
print("INFO: Reading current IPMI BMC values...")
- cmd = ["bmc-config", "--checkout"]
+ cmd = ["bmc-config", "--checkout", "--lan-channel-number=2"]
if section:
cmd += ["-S", section]
try:
But this is very unconvenient cause depending on how the machine BMC is connected to the network we have to remember and check or not this new 29-Kontron-me1210-bmc-second-interface script in the list of commissioning scripts.
For sure we always connect only one BMC network interface.
So that would be great that in the case of no IP is detected on a BMC interface, and so the machine cannot be managed, this script just try next BMC interface.
So we wouldn’t have to care about using multiple commissioning scripts depending on which BMC interfaces we are connected to.
That would be even more great if this could be included in 3.3.
Thanks in advance,
Have a nice day,
Best Regard,
Mickaël.