Closed jgruber closed 4 years ago
This has nothing to do with mgmt port and the license activation process..
This is mcpd error saying ConfigSync IP address can not be the same as the mgmt IP address.. when it can be. I listed the multistep work around to make this work.
AT-454 for tracking
We're getting conflicts between our internal bug tracking system and GitHub. Our internal system also has an issue 42 which relates to the targetPort and when licensing from BIG-IQ license pools.
+1 - Hit this trying to cluster a couple 14.1 1-nic devices. Need to re-architect to work around. Not sure customer's appetite for non-1nic solution.
This was resolved in the 1.11.0 release.
DO validation will produce the mcpd error: "The configsync and management IP addresses cannot be the same.", which is simply not true for 1NIC deployments. ConfigSync declaration is required to use device groups for config sync and trusts (not failover cluster which is not supported in 1NIC).
In order to set the ConfigSync and FailoverUnicast addresses to the management IP within your DO declaration, you must:
This is the TMOS supported way to allow this configuration. All of which can be done via iControl REST, so once 1NIC is discovered, these steps can be handles totally within DO.
Once these steps are properly provisioned, you can proceed to handle your DO declaration.
These steps are not 'bootstrapping' as the bootstrapping for 1NIC was done via DHCP for TMOS and are only required to make a perfectly valid TMOS configuration possible using a DO declaration.
Alternatively, we can just say DO doesn't support 1NIC with config sync'ing, but that would basically knock DO from being used for all of our major WAF 1NIC deployments (NFV WAF service tier).