Wireless Access

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

ADP as in the APs are L2 adjacent to the controller?

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

ADP as in the APs are L2 adjacent to the controller?

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

ADP as in the APs are L2 adjacent to the controller?

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

I'm sorry, we are using DNS instead of ADP..

ADP as in the APs are L2 adjacent to the controller?

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

You've added aruba-conductor in addition to or in place of the old aruba-master host entry?

I would also recommend looking at and potentially moving to DHCP options for discovery.

I'm sorry, we are using DNS instead of ADP..

ADP as in the APs are L2 adjacent to the controller?

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

addition to..

Why would your recommend using the DHCP option?

You've added aruba-conductor in addition to or in place of the old aruba-master host entry?

I would also recommend looking at and potentially moving to DHCP options for discovery.

I'm sorry, we are using DNS instead of ADP..

ADP as in the APs are L2 adjacent to the controller?

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

We're using the ADP method. I agree it shouldn't take any longer. My confusion is it doesn't happen to all the time. Only about 20 percent of the APs have this problem. Like my first post.. I replaced 7 APs, 3 came up quickly like they should, 1 came up 2 hours later and 3 I'm still waiting for them to come up and it's been over 4 hours. They are all on the same network, replaced AP 315s that were working perfectly and the controller can ping all 7 of them

What discovery method have you configured to point the APs at the controller?  The AP-635 shouldn't take any longer than the AP-515 to contact the controller and perform the initial connection process.

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..

I'm in the process of replacing my AP-315s with AP-635s. We have over 4200 APs installed. They are a mix of 315, 515 and 635s. When I replace some of the 315s with a 635 it takes hours before the AP establishes and IPSec tunnel. The AP dhcps fine and the controller can ping the AP. It doesn't happen all the time. We just replaced 7 APs in a building and 3 came up perfectly. The other 4 took about 4 hours. We have 6 7280s in a cluster running 8.10.0.9. I tried deleting the new whitelist and recreating it. Also, the old APs whitelist entry has been deleted and cleared the ap database information..