12-09-2021 04:13 AM
We have deployed a virtual Infoblox (IB805 - version 8.4.3) on Azure following the best pratices (Bicep deployment via Azure Devops).
This machine is by default having two NICs (1x LAN1 and 1x MGMT) in 2 different subnets.
However the Infoblox system didn't provision the MGMT interface and it is only having a single LAN1 activated.
When I try to manual bring up the MGMT interface through the CLI, I get the following error: "Cannot enable Management interface when LAN1 is configured with a dynamic address".
The message shouldn't be expected because the LAN1 IP was statically defined during the pipieline deployment.
Did anyone within the community experience a similar problem ?
01-18-2022 06:32 AM
Had the same issue. We had to just do a quick run through of the "set network" command first then the "set interface mgmt" on the console port to enable it. The set network command will give the IP information that was used during setup.
2 weeks ago - last edited 2 weeks ago
I have done some further testing and I have a theory that this was either a bug or a disabled / missing feature:
8.1.2 / 8.2.1
Cannot enable MGMT interface no matter what I try
8.2.5+ / 8.3.0 / 8.4.0
Can enable the MGMT (eth0) interface with no problems at all, 100% repeatable
It appears that not being able to enable the MGMT interface on AWS was indeed a bug up that was fixed sometime after 8.2.1.