09-20-2016 07:22 PM
Can anyone help me answer why my Instant 215's can't find the Virtual Controller across our wireless bridge? I'm guessing the heartbeat packet isn't making it across some how, but that's why I'm asking the experts. Here is our setup, I'll be happy to clarify as needed.
Building 1: has working IAP215's with a virtual controller in VLAN 100.
Building 2: is connected to building 1 with two AP277's acting as a wireless bridge. IAP215's in this building won't join the VC in Building 1 even though they are receiving an ip from the correct subnet. VLANs are configured on switch ports for AP's and Uplinks in both buildings as follows. IAP215's in this building do receive an ip that is pingable in both buildings.
Default VLAN1: Switches and VC for Bridge here
Vlan 100 = Ap's here
Vlan 105 = Employee wireless access
Vlan 110 = Guest wireless access.
09-20-2016 07:45 PM
I would type "show log system" on the commandline of both APS to see the discovery process and what is happening. If you can, make sure both IAPs are the same version of instant before putting them on the same LAN. That will eliminate one possible issue.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
09-20-2016 08:22 PM
The point side AP shows several of these in the logs. This is the side that contains the AP that won't join.
Sep 20 17:33:53 stm: <304065> <ERRS> |AP email@example.com stm| PAPI_Send failed, send_papi_message_with_args, 887: Resource temporarily unavailable, dstport 15200
Sep 20 17:33:58 cli: <341258> <WARN> |AP firstname.lastname@example.org cli| AP receive delta configuration id 12 current_cfg_id 12 from msg CLI_EXECUTE_CONFIG_COMMAND is not correct.
Sep 20 17:34:22 cli: <341005> <ERRS> |AP email@example.com cli| Master received alerts message from unknown AP,
Sep 20 20:36:40 cli: <341005> <ERRS> |AP firstname.lastname@example.org cl i| Master received alerts message from unknown AP, message dropped
09-20-2016 11:32 PM
Currently, IAP over an IAP mesh link on the same cluster is not supported. You can put the IAP mesh link in a separate L2 VLAN so that the indoor IAP clusters and mesh clusters are separated.
Sr. Techical Marketing Engineer
09-21-2016 05:35 AM
In my current setup the VLANS are configured on the switchs. The bridge AP's are in VLAN1 and the 215's are in VLAN 100. Is this what you were describing?
09-21-2016 06:31 AM
So the IAP-277s are a separate VC/cluster and are managed separately from the IAP-215 VC/Cluster. So where is the VC for the 215s relative to the mesh link, are they all on the same side or is the VC on one side and the other 215 cluster members are on another? I assume VLAN 100 is trunked over the mesh link and the IAP-277s have no addressing in VLAN 100 where the 215s are?
Sr. Techical Marketing Engineer
09-29-2016 05:13 PM
So here is an update on my situation, any thoughts?
Building A, the portal side of the bridge has IAP-215's in Vlan 100 with a VC running those Ap's
The bridge consists of two IAP-277's running on their own cluster on Vlan 1.
Building B - the point side, i took a new 215 IAP and configured via the instant ssid. made it a master. This IAP works fine, but none of the other IAP-215's on the point side join it when plugged up even though they get an address in the same VLAN. Is there a way to force them to join?