Wireless Access

Reply
Frequent Contributor I
Posts: 82
Registered: ‎02-15-2008

Controller vs IAP

Hallo, is there any Document available where i an see the Differences on the Feature Set between a IAP and a Controller based Solution?

 

Thank you and best Regards 

MVP
Posts: 1,401
Registered: ‎05-28-2008

Re: Controller vs IAP

[ Edited ]

Hi,

**LOOK ON THE PDF ATTACHED TO THIS POST-ISNT UPDATED SO MUCH - BUT WILL GIVE U SOME CLUE**

 

IAP is close to a contoller in capabilities but is not eqaul. Depending on your deployment requirements you might need one or the other. Currently these are some of the features that are available in a controller but not on an IAP. 

 

(off the top of my head)

Spectrum analysis

L3 roaming

DHCP fingerprinting

VIA and VPN client termination

Site-Site VPN

 

This may change in the future.

 

Normally if customer is looking at security features we would go for the controller base as it comes with PEFNG and RFP etc and support RAP at the end of the day. As for roaming is L2 versus L2 + L3.

 

Besides some feature difference, also consider the following.

 

A controller simplifies VLANs at the edge.  You do not have to worry about deploying VLANs. 

A controller will manage both your wired and wireless Aruba network.   All clients, wired and wireless, have the same policy.

A controller provide remote functionality such as VPN and Remote APs to extend your network.

 

Aruba Instant will scale, now beyond 16APs, but are limited to a L2 subnet.  Using basic network architecture rules, A class C subnet is 256 users.  It's best to keep a subnet to that limit.  For a Class B flat network, while IAP and Controllers will both manage much more than 256 users, you should be careful.  Large L2 subnets create a lot of chatter and the network can and will have issues.

 

ALSO CONTROLLER WILL GIVE YOU:

 

-an option for HSPA+ backhaul

- flexibility to use the multiple ports as 'legs' into different networks (e.g. admin, guest, internal).

- Assuming you are already trained in Aruba OS (AOS) then == zero learning curve

 

If you are trying to make this site 'look like' other corporate sites (say HQ) then I would go controller, and do master--local.   If on the other hand its a one-off site and never needs/wants to be in sync with other sites than Instant (IMHO) is a good candidate, if you don't need any of the 650 additions that have been mentioned in this thread already.

 

Hope this info helpd u

*****************2Plus Wireless Solutions****************************
Aruba Airheads - Powered By community for empower the community
************ Don't Forget to Kudos + me,If i helped you******************
Frequent Contributor II
Posts: 118
Registered: ‎02-10-2011

Re: Controller vs IAP

[ Edited ]

They both change quite often.  The IAP is very robust and seems to do most of what a controller based solution would do.  I would suggest deciding based on the limitation of the IAP solution. Things such as max IAP's, max users supported, whether you have airwave to centrally manage pods of IAP's, etc.

 

MVP
Posts: 1,401
Registered: ‎05-28-2008

Re: Controller vs IAP

Take a look in my POST (I attached a small PDF - isnt so updated , but will give u some idea)

 

Me.

*****************2Plus Wireless Solutions****************************
Aruba Airheads - Powered By community for empower the community
************ Don't Forget to Kudos + me,If i helped you******************
Frequent Contributor II
Posts: 158
Registered: ‎12-06-2010

Re: Controller vs IAP

Bump. Is there any updates to this document. There have been a lot of enhancements & changes to the Instant platform. It would be great to see a document that explains ALL of the comparisons betwen Instant & Controller-based wireless.

 

Network Engineer | Airhead | Titus 3:5
Frequent Contributor II
Posts: 158
Registered: ‎12-06-2010

Re: Controller vs IAP


kdisc98 wrote:

.

.

.

Normally if customer is looking at security features we would go for the controller base as it comes with PEFNG and RFP etc and support RAP at the end of the day. As for roaming is L2 versus L2 + L3.

 

Besides some feature difference, also consider the following.

 

A controller provide remote functionality such as VPN and Remote APs to extend your network.

 

 


This part concerns me. I'd like to confirm whether or not there are any site-to-site or VPN capabilities in the new version of Instant.

Network Engineer | Airhead | Titus 3:5
MVP
Posts: 1,110
Registered: ‎10-11-2011

Re: Controller vs IAP

Yes, VPN capabilities exist for the purpose of connecting the branch office running an IAP to a controller at your home office.

 

See details here: http://www.arubanetworks.com/techdocs/Instant_40_WebHelp/InstantWebHelp.htm#UG_files/VPN_Conf/Plan VPNl.htm%3FTocPath%3DVPN%20Configuration%7C_____1

=======================================
If a reply adequately addresses your issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users.
Moderator
Posts: 681
Registered: ‎04-16-2009

Re: Controller vs IAP

VPN termination is possible between an IAP and an Aruba controller.  This has been around since IAP 3.2 and AOS 6.2.  You cannot do VPN between IAPs.

Frequent Contributor II
Posts: 158
Registered: ‎12-06-2010

Re: Controller vs IAP

The VPN I'm referring to is a user VPN via IPSEC to the controller.

Network Engineer | Airhead | Titus 3:5
Moderator
Posts: 681
Registered: ‎04-16-2009

Re: Controller vs IAP

If you are referring to the VIA Client that is a controller-based feature only.

Search Airheads
Showing results for 
Search instead for 
Did you mean: