Hey all,
So I did a fair bit of reading before posting this and I couldn't find anything that would answer my questions, so let me define what my dilema is:
1. I have two locations that we'll call "A" and "B".
2. "A" location has 4 people and a controller with 4 APs.
3. "B" location has 100+ people and 11 APs.
4. "A" location has an Aruba 3400 controller that terminates both "A" and "B" APs.
5. The controller has both AP groups listed on it
6. Each location has its own subnet, 10.A and 10.B
7. The controller has an IP address of 10.A
The goal is to move the controller from "A" to "B", and this is the proposed way of doing it:
(assume LMS failover is in place)
1. Change all VLAN interface IPs (except the main management IP address) to match the NEW location (10.B instead of 10.A)
2. Change the main VLAN IP from 10.A to 10.B (and lose ability to http, telnet, or ssh to it)
3. Check LMS to assess fail-over
4. Physically move the controller from "A" and plug it into one of the switches at "B"
5. Check to see if we can log into the controller at new location (with 10.B IP)
6. Access aruba-master and re-provision the APs to the correct AP group (in theory)
The strangest part is that since the original controller's IP address will be changing, how are the APs going to know which controller to re-associate with? If the APs fail over to the aruba-master controller, how can I push them to the new controller? It might be easier to know how to tell the APs to associate with the AP-Group on the controller with the new IP address, since the APs are now on X AP-Group terminating at controller 10.A, when I need them to terminate to X AP-Group at controller 10.B.
I might be making this more complicated than it needs to be, but I figure that someone here might know. Also, I'm sure that I'm going to need to clarify something, so please, ask away.
Thank you!
#3400