Recommended is to use DHCP for the IAPs in the 'untagged/native' VLAN, and configure the VC IP to get a 'known' IP for configuration. For me the biggest reason is that it is simple, you can't really make IP addressing errors/wrong/missing gateway, etc. And if you need to change the IP range at a certain point (like moving to test/production), you just change the DHCP scope.
The IAPs do not use the VC IP (which is optional) to find each other. There is a broadcast/multicast protocol for that coordination and VC election.
As mentioned earlier, what is really important in a mixed IAP cluster (325/555) is that before you introduce a new AP type in the same network, they run the same firmware version (same build number). As soon as you have an AP555 in the cluster, new AP555s should get upgraded from there.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Nov 29, 2021 11:54 PM
From: Christopher Hernandez
Subject: AP-555 not being recognized in my VC
Yes that's right though that's just what my company has done in other offices so I've just been following their advice to use static IDs for the APs. But just to be clear your saying I shouldn't add a static IP to the AP but I should add the VC IP so that it knows where to search. Or do you mean there's no need to configure anything just boot it up and let it search for the VC on it's own.
------------------------------
Christopher Hernandez
Original Message:
Sent: Nov 29, 2021 08:41 AM
From: Dustin Burns
Subject: AP-555 not being recognized in my VC
When you said that you "tried to link it back up after adding the VC's IP", did you mean that you configured the VC address in the config of the AP? You do not need to do that. You should be able to set a static IP via console if you can not use DHCP (Static is not recommended). I would not apply any settings once it is booted up. It should get everything from the VC.
------------------------------
Dustin Burns
Lead Mobility Engineer @WEI
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2021
If my post was useful accept solution and/or give kudos
Original Message:
Sent: Nov 29, 2021 05:57 AM
From: Christopher Hernandez
Subject: AP-555 not being recognized in my VC
So I took your advice just updated the firmware did the reboot tried to link it back up after adding the VC's IP and configuring the IP for the AP but after that it stopped sending out any SSID which put me back at being unable to actually configure it after the reboot and it still not being recognized in the VC.
------------------------------
Christopher Hernandez
Original Message:
Sent: Nov 26, 2021 12:43 PM
From: Dustin Burns
Subject: AP-555 not being recognized in my VC
Is the 555 on the same software version as the rest of the IAP cluster? You will need to update to same version on your first 555. Any other 555 joining after will use another 555 in the IAP as the software "seed" and will get the file from that AP.
------------------------------
Dustin Burns
Lead Mobility Engineer @WEI
ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2021
If my post was useful accept solution and/or give kudos
Original Message:
Sent: Nov 25, 2021 12:55 AM
From: Christopher Hernandez
Subject: AP-555 not being recognized in my VC
Hey y'all,
I'm having a bit of an issue having my new AP-555 being recognized by my current VC. To give you a bit of an idea of how it's set up my company had previously installed Aruba AP-325's in the office with a VC setup to manage all of them. We've bought another floor in our building and have our switch connected via fiber, the new floor has Aruba AP-555's installed but I'm running into 2 separate issues.
1. When I log into setmeup.arubanetworks.com I'm able to make changes but once I reboot it to apply the changes my device no longer shoots out any SSID and the VC doesn't recognize it at all. I've tried setting it up on both our new floor and the old one but in either one the VC won't recognize it and it won't shoot out any SSID.
2. One way of getting it to boot up and shoot out an SSID was by taking the a backup of the current config of our 325 and upload that into the 555 from there I'm able to reboot the AP and it will start shooting out our Staff and Guest SSID but it still doesn't get recognized in the VC and I'm also unable to log into the AP to do any sort of management.
To give a bit more context into our network we have 2 Cisco 2960-x one of which is 24 ports the other 48 connected via SFP.
------------------------------
Christopher Hernandez
------------------------------