Creating a Local Controller (Converting a Master to a Local) 1) Take a new controller and build it as a master controller initially (reference the how to for building a master controller) 2) Ensure the code version is the same between the new temporary master and your production master controller. 3) Verify IP connectivity between the new temporary master and your production master controller (ping for example) Also ensure your firewall is configured to allow traffic between the two controllers (papi udp 8211, tcp 4500, etc. 4) On the new temporary master type the following to point to the IP of the production master controller. Note you can use a preshared key or a certificate based solution. conf t masterip 1.2.3.4 ipsec keytexthere exit write mem 5) on the production master controller type the following to point to the IP of the new local controller. Note you can use a preshared key or a certificate based solution. conf t localip 2.3.4.5 ipsec keytexthere exit write mem 6) To verify they have synced up, issue the following and ensure it says update successful. Also you can look at the config on the local controller and you should see lots of extra configuration pushed down from the master to the local. (7210-hq-1) # show switches All Switches ------------ IP Address Name Location Type Model Version Status Configuration State Config Sync Time (sec) Config ID ---------- ---- -------- ---- ----- ------- ------ ------------------- ---------------------- --------- 10.9.0.4 7210-hq-1 3rd Floor DC master Aruba7210 6.3.1.2_41362 up UPDATE SUCCESSFUL 0 53 172.17.36.4 3600-sd-1 San Diego Local Controller local Aruba3600 6.3.1.2_41362 up UPDATE SUCCESSFUL 10 53 7) Now you can reconfigure your AP profiles for your AP's to point to the IP of the local controller for the primary LMS and the AP's will build their tunnel to the local controller versus the master.