We are running a test controller so that we can try out the upgrade process to 6.5.1 (we currently run 126.96.36.199). The two live masters are 7210s and the locals are 7220s. The test controller is a 7220.
The test controller is running in the same layer 2 domain as the other controllers.
We want to switch a single group of APs from the existing controllers to the test controller (the test controller was set up initially by joining it to the existing mobility domain so that it picked up all the necessary config, and now it is running independently as a master).
I'm trying this out initially with a single AP to see what I need to do = I created a new group with a new provisioning profile with the test controller's hostname as the master, I also created a new system profile with the test controller's IP as the LMS IP. But whatever happens when I regroup the AP it still uses the live master, console output:
Running ADP...Done. Master is aruba-master.net.cam.ac.uk
Using saved lms 188.8.131.52 as the master directly
Reprovisioning the AP doesn't seem to work either ie
read-boot info wired-mac <mac>
reprovision wired-mac <mac>
For a single AP I know I could purge the AP and set the master manually by consoling in, but the APs we want to switch have been deployed so this isn't an option. What else do I need to do to make this switch happen?
Gah! Guess what I forgot to do?... write mem!
That has done it. I need that written on a post-it on my screen!
...well I thought that it had worked, but somehow I am now back in the old situation. The AP is appearing on the live controller not the test controller despite being in its own group, with its own system profile (LMS IP) and provisioning profile (Master FQDN).
The console shows that it is now provisioned with the test controller name:
Running ADP...Done. Master is aruba-master-65.net.cam.ac.uk
But later on:
184.108.40.206 is a local in the live system. I tried reprovisioning the AP but no luck.
I'm sure I'm missing something obvious, can anyone help?
Based on your first post, the only way that you can do this is to:
1. Remove any LMS-IP from any ap-group
2. Provision the AP using Wireless> AP Installation and point it to the controller you need it to go to:
You should not be using a provisioning profile for this, so please delete it or change it to N/A in that ap group.
Combining an ap move between controllers that do not have the same version of code is disastrous, because when a controller is upgraded or downgraded, it starts discovery all over. Everything that you did up to this point, just creates another variable or increases the possibility of an upgrade/downgrade loop. Keep it simple by hardcoding the ip address of the controller you want to point it to and reboot.
Thanks as always Colin,
Actually at the moment all the controllers are on the same code. We want to move this group of APs across to the test controller and then perform the upgrade to 6.5.1 see how they respond.
The single AP move I'm doing now is just me testing moving an AP between controllers so that when we move the group it (hopefully) goes smoothly.
How do the instructions you gave translate into CLI commands? Can I apply this to a group?
Provisioning an AP to a specific controller is not applied to a group, it is typically applied to a specific AP. It can be applied to multiple APs of the same model.
There are cli commands to do this, but what you need to undo should be done via the GUI until you get it working.
Ok so here's what I tried:
Changed the system profile to be default (no LMS IP)
Removed the provisioning profile completely
Moved the AP into the test group
Went to the controller URL, found the AP and provisioned it with:
Host controller name: aruba-master-65
Master Controller IP Address/DNS name: 220.127.116.11
...And booted it.
It looked like it was going to work, the AP appeared on the test controller briefly, got as far as 'Configuring Logging' and then silently switched back to the original controller.
Subsequently if I try repeating that process (of provisioning the test controller details via the GUI) it reboots but doesn't even seem to touch the test controller any more. But the provisioning parameters for it on the controller that it _does_ appear on are showing correctly, ie with the test controller details:
AP "18:64:72:c7:3b:0e" Provisioning Parameters----------------------------------------------Item Value---- -----AP Name 18:64:72:c7:3b:0eAP Group maths-master-65_apsLocation name N/ASNMP sysLocation N/AMaster 18.104.22.168Gateway N/AIPv6 Gateway N/ANetmask N/AIP Addr N/AIPv6 Addr N/AIPv6 Prefix 64DNS IP N/ADNS IPv6 N/ADomain Name N/AServer Name aruba-master-65Server IP N/A
And during bootup the console shows:
Running ADP...Done. Master is 22.214.171.124
But then later reverts to:
Using saved lms 126.96.36.199 as the master directly
I'm a little confused! We do use DHCP otion 43, but that wouldn't supply 188.8.131.52.
Please open a TAC case to find out what else is going on...
It turned out the AP I was using had some per-AP config that was pushing it back onto the other controller, so all good now.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.