Wireless Access

I have 2 Aruba AP 0215, runing well with virtual controller configured. I just decided to buy a dedicated controller, Aruba 7030.

In initial configuration, i configure the controller with vlan 80 10.100.20.2 (since I set the AP in the same segment). The 7030 interface is configured in trunk mode, because I have multiple SSID with multiple vlan in it, so it has to be trunk mode.

But the case is, the 7030 wont detect the AP0215, the configured or even the fresh one.

Thank you,

Lazuardi Nurfaiz

The IAP 215 needs to be converted to a campus AP first.   http://community.arubanetworks.com/t5/Controller-less-WLANs/How-to-convert-a-whole-IAP-cluster-as-Campus-APs/ta-p/215053

I tried to convert the AP to Campus AP. But the process never get done, it just said "Conversion - Please wait". Is it normal?

How can I check what version of code is running in my controller? What is the different of campus ap and remote ap? The controller still not detecting / controlling the AP :(

---

@lazuardiadli wrote:

How can I check what version of code is running in my controller?

 

=> check under tab maintenance

 

What is the different of campus ap and remote ap?

 

=> campus AP uses the internal address to connect to the controller. Remote AP uses a public address to connect to the controller. The remote AP has some limitations in specific tunnel types. 

 

The controller still not detecting / controlling the AP :(

 

=> is there a dns record for aruba-master? Or are the AP's in same VLAN as controller?

---

Can I use remote AP if the controller and the AP in the different network?

For now, the controller and the AP is on the same network. But in the future, the controller and the AP will be in the different private network.

When provisioning the AP as a remote, you just put in the public ip address of the controller, and then the Remote AP will route its traffic to that ip address when it boots up.  It does not need to be on the same subnet:

Please see the remote AP VRD here:  http://community.arubanetworks.com/t5/Validated-Reference-Design/Remote-AP-Networks/ta-p/155140 for more details.

What I get from your explanation is this:

Remote AP: the controller should be in public address

Campus AP: the controller should be in private address, and it can be in the different network?

Is it correct?

The campus AP is the default method of connecting an AP to a controller and it uses GRE to transport client traffic back to the controller.  Connecting a Campus AP to a controller beyond a firewall will not work, because gre cannot travers a nat boundary.  The Remote AP uses ipsec to transport all traffic so it CAN pass beyond a firewall.  The Remote AP is ideal for remote offices, as a result.  For a Remote AP to work, the controller would need either a public address on one of its interfaces, or a public address provided via a 1:1 NAT by a firewall.

The campus AP requires very little configuration to work.  A remote AP requires more planning and configuration.