I cannot seem to find in the manual the exact method the IAP uses to find the other AP's (specifically the Virtual Controller one).
So my question is: how do they try to find the VC? Is it the same as a normal AP does to find the master controller (config, dhcp, adp, dns)?
Looking for this info as my IAP's will need to connect over a layer3 network. If dns is one of the methods, what name does it try to resolve?
"Up to 16 Aruba Instant APs can be configured per Layer 2 subnet, or Virtual Controller group, and enterprises can have as many subnets or Virtual Controller systems as needed on a campus or in a building."
Bit dubious way to put it, but I'm affraid you might be right. :smileysad:
Once you configure your first Instant AP, all Instant APs that connect to that layer2 segment will automatically discover the existing configured iAP and join the instance. All instant APs in the instance must reside on the same Layer2 segment for management.
Now - if you're dealing with multiple groups of instant APs, you can do automatic discovery of AirWave by defining option 60 in DHCP. You can find more info about this in the user guide under 'Airwave Integration and Management'.
about virtual controller, i have 4 IAP 105 operating in a virtual controller. I'm trying to add 2 more 105 IAP and when i connect the first one in the wired network it cant join in the virtual controller. I get some strange log messagens showing "fwd-mode:0 mesh":
asap_send_elected_master: sent successfullywait for stm to initialize overasap_send_elected_master: sent successfullyUser: asap_send_elected_master: sent successfullyvap aruba000 vlan is 0. fwd-mode:0 meshRESTARTING ALL TXasap_send_elected_master: sent successfullyasap_send_elected_master: sent successfully
Is this the right mode to join in the virtual controller?
what can be happening? (I'm newer with this products)
See the entire attached log file.
If you have 4 IAPs already up, then one of them is the master virtual controller (VC). Couple of things ot check:
- make sure the autojoin settings are enabled under the settings/advanced tab
- make sure the 2 new IAPs are in the same VLAN (subnet) as the ones you have set up already.
trying to figure out where to look for the logs as I don't see an attachment.
Hi Sassy, thanks for your fast replay.
Check for autojoin in these two Acess Points?
Yes, they are in the same vlan (subnet).
Check Auto join mode is enabled on the virtual controller as shown in the attachment.
I don't see anything unsual in the logs except for the "asap mode disabled :." It appears that the master was detected by this IAP. I will follow up on that.
Are they all IAP 105?
I just verified that the "asap mode disabled" message in the log refers to the Autojoin mode being disabled. Please connect to the UI of the virtual controller and check the settings as I described in the doc.
I hope this fixes the issue.
Look like a country code issue. Can you send me the output of summary from the virtual controller and the IAP that has issue?
Good thread here, i thought whether this could fit here too. If having 2 locations connected with VPN to each other but different subnets, could IAP connect to each other , im not sure if the traffic is tunneled between those (i dont think) so this cant properly work if having other subnet on branch location.
if having controller_based APs then this is working fine, but i dont think this could work with IAPs .e.g. you have HQ with 3 IAPs and then one branch connected via VPN and 1 IAP outside and then having some construction of 4 IAPS ,
Not working or?
You should have difference VC...
One by Subnet !
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 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.