Skip main navigation (Press Enter).
Log in
Toggle navigation
Search Options
Log in
Home
Discussion Forum
Support
Documentation Portal
Support Knowledge Base
HPE Networking Support Portal
Live + Virtual Events
Webinar Archive
Upcoming Events
News
Technical Blog
ACEX Hall of Fame
MVP Program
Become a Member
Search Options
Controller-less WLANs
×
Community Home
Discussion
1
Members
14
View Only
Back to Library
Are there any requirements for IAPs to form an Instant Cluster?
0
Kudos
Jul 02, 2014 03:40 PM
ssasi
Environment :
This article applies to all IAP platforms and OS versions.
For the IAPs to form an Instant Cluster:
1. all IAPs should be of the same regulatory domain. Each IAP in a regulatory domain will take the role of master if no other IAPs are in the same regulatory domain.
Aruba Instant APs (IAPs) are shipped in four variants based on regulatory domain:
Restricted Regulatory Domain - US
Restricted Regulatory Domain - Israel
Restricted Regulatory Domain - Japan
Unrestricted Regulatory Domain or ROW (Rest of World)
2. Master IAP and the new IAP should be in
same Layer-2 domain
.
3. Auto Join should be enabled. If the Auto-Join is disabled, then you will see a message in “AP Log System” :
Controller doesn’t allow new AP = xx:xx:xx:xx:xx:xx, reboot it.
The mac-address is the MAC of the new IAP. Alternatively, we can disable the auto-join mode and manually add the new member IAP's mac address in the allowed-ap list on the master (virtual controller).
4. Hardware class of the master and the new IAP should be same. If the hardware class is different then the new IAP should have the same InstantOS version as of Master.
Statistics
0 Favorited
3 Views
0 Files
0 Shares
0 Downloads
Related Entries and Links
No Related Resource entered.
Copyright 2024. All rights reserved.
Powered by Higher Logic