Aruba Instant & Cloud Wi-Fi

Reply
Occasional Contributor II
Posts: 15
Registered: ‎07-22-2015

Reduce the time an IAP waits before failing to mesh point

In my lab, it takes about 15 minutes for an IAP225 to fail connecting to the VC and then attempt to mesh. It eventually meshes just fine but it takes forever. I've searched but I can't find a CLI command to reduce the time the IAP decides it isn't cabled to the network and try to mesh.

 

Do you know the command? Is it possible?

Guru Elite
Posts: 20,416
Registered: ‎03-29-2007

Re: Reduce the time an IAP waits before failing to mesh point

Do you have any of the ethernet interfaces up?



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 15
Registered: ‎07-22-2015

Re: Reduce the time an IAP waits before failing to mesh point

The portal uplink is Bridging Disabled. The point uplink is Bridging Enabled. The bridge is working fine. While watching the point come up, I get to the 

        <<<<<       Welcome to the Access Point     >>>>>

message at about 132. Around 790 or so, it sees that it is not connecting to Interenet and then reboots, using WiFi as the uplink. 

 

The point is connected to a switch that is not connected to the main network. I would love to be able to adjust how long the AP takes before rebooting and faulting over to the WiFi uplink.

 

Below is my diagram.

aruba bridge.jpg

Aruba Employee
Posts: 1,253
Registered: ‎11-07-2008

Re: Reduce the time an IAP waits before failing to mesh point

Is something handing out DHCP on the IAP mesh point's network? Is the mesh point getting an IP address on the wire when coming up?

Jerrod Howard
Sr. Techical Marketing Engineer
Occasional Contributor II
Posts: 15
Registered: ‎07-22-2015

Re: Reduce the time an IAP waits before failing to mesh point

Spoiler
Yes, 10.0.0.1 is the DHCP server. The two APs are static.

At about [54.00000] I get 
Got all network params from APboot env. Skipping DHCP
Static IP detected. Checking if LACP needs to be configured


Occasional Contributor II
Posts: 15
Registered: ‎07-22-2015

Re: Reduce the time an IAP waits before failing to mesh point

If it helps, I've attached a PDF of everything I've done in my test lab.

Aruba Employee
Posts: 1,253
Registered: ‎11-07-2008

Re: Reduce the time an IAP waits before failing to mesh point

WiFi Uplink is not supported on any 11ac IAP currently (unless it was added VERY VERY recently). Are you creating the 'Bridge1' SSID for the mesh point to use? I think this config is causing some delays in the mesh coming up (likely), and you would need to default everything and JUST setup the basics. Stand up the two APs in the same cluster, disable the Extended SSID, make sure the cluster is formed, and then disconnect the mesh point and move it to the remote switch. If everything is in VLAN 1, there's no need to set the bridged interface to trunk either.

 

If the switch the mesh point is connected to is handing out DHCP, then the mesh point would never come up or could take a VERY long time to come up. Once you have a simple config (one client SSIDs, extended disablted), let it come up, then look to enable the ethernet bridge. Change one thing at a time so you know what broke. There's dozens of links here on setting up the mesh for IAP, just do the bare minimum first. 

Jerrod Howard
Sr. Techical Marketing Engineer
Search Airheads
Showing results for 
Search instead for 
Did you mean: