But its already configured and assigned to an interface...
If I look at the list of vlans on the gui.. there are about 10. One of them, vlan 123 is configured with the IP address 1.2.3.4 and assigned to an interface. This vlan exists on each of our controllers with appropriate IP.
The one controller is saying its IP is from one of the other vlans. A tech I was speaking to, who was unfamiliar with v3 cli commands, says in newever versions you can simply select the IP for the controller from the a drop down box in the gui.. this doesnt exisit on the code we have.
At the time of setup vlan 123 was the "first" configured vlan.. obviously, so a connection across the lan could be made.. then more vlans added. This vlan, based on vlan id, is now at the higher end of the vlans configured. Even the vlan and ip it is saying it is, is not the first configured vlan.. I dont know how or why it changed.
I cant believe I cant just tell the controller that its ip should be 1.2.3.4 on vlan 123 and not ip 5.6.7.8 on vlan 456.
Maybe ill try the loopback.. it just doesnt seem right, when none of the others have one configured!