**This is an old revision of the document!**
Table of Contents
ArubaInstant_Norma_8.12.0.5_92330
If the IAP is part of a cluster, the username will be admin, and the password will be the serial number of any AP in the cluster. If the IAP is running a software version earlier than ArubaOS 8.5.0.0, admin will remain the default password.
**[[https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=1013490535&tab=driversAndSoftware|HPE Support Center]]**
| Field | Value |
|---|---|
| Filename |
| Field | Value |
|---|---|
| Filename |
interface 1/1/1
description AP_172.20.76.24/_44:12:44:cd:ed:45_635(indoor)_AP_59 no shutdown mtu 9100 no routing vlan trunk native 735 vlan trunk allowed all
! ——– LINK TO AP (VLAN 706) ——– interface 1/1/2
description LINK TO AP no shutdown mtu 9100 no routing vlan trunk native 706 vlan trunk allowed all
! ——– AP 172.20.76.22 / AP57 ——– interface 1/1/3 description AP172.20.76.22/44:12:44:cd:f1:05635(indoor)AP57
no shutdown mtu 9100 no routing vlan trunk native 735 vlan trunk allowed all
! ——– AP 172.20.76.21 / AP56 ——– interface 1/1/4 description AP172.20.76.21/44:12:44:ce:26:7e635(indoor)AP56
no shutdown mtu 9100 no routing vlan trunk native 735 vlan trunk allowed all
! ——– LINK TO AP (VLAN 706) ——– interface 1/1/5
description LINK TO AP no shutdown mtu 9100 no routing vlan trunk native 706 vlan trunk allowed all
! ——– AP 172.20.76.23 / AP58 ——– interface 1/1/6 description AP172.20.76.23/44:12:44:ce:01:d3635(indoor)AP58
no shutdown mtu 9100 no routing vlan trunk native 735 vlan trunk allowed all
!
! LAG-1 toward Core 6400 (MDF-1) !
interface lag 1
description Access LAG-1 to MDF-1 - Core 6400 no shutdown no routing vlan trunk native 1 vlan trunk allowed all lacp mode active loop-protect
interface 1/1/49
description Access LAG-1 to MDF-1 no shutdown mtu 9100 lag 1
interface 1/1/50
description Access LAG-1 to MDF-1 no shutdown mtu 9100 lag 1
Virtual Controller Settings (RW Controller)
virtual-controller-country RW virtual-controller-ip 172.20.76.20
Verification commands:
show running-config | include virtual show swarm state show swarm leader show aps
If Virtual Controller appears as 0.0.0.0, set it manually:
virtual-controller-ip 172.20.76.20 commit apply
SSID Renaming – RW Controller
SSIDs were renamed to avoid conflict with the US controller.
configure terminal
wlan ssid-profile “SFEWiFi” essid “SFEWiFi-RW” exit
wlan ssid-profile “SFE-Guest-WiFi”
essid "SFE-Guest-WiFi-RW"
exit
wlan ssid-profile “IoT”
essid "IoT-RW"
exit
wlan ssid-profile “SFEST” essid “SFEST-RW” exit
wlan ssid-profile “SFEStaff” essid “SFEStaff-RW” exit
wlan ssid-profile “SFEStudent” essid “SFEStudent-RW” exit
wlan ssid-profile “SFETeacher” essid “SFETeacher-RW” exit
wlan ssid-profile “CouperPortal” essid “CouperPortal-RW” exit
commit apply
Verification:
show network show network <SSID>
CLI Verification Commands
AP Health and Radios
show aps show ap debug system-status show ap name <APNAME> status show ap debug radio-stats
Client/IP Assignment
show client show client detail <mac-address> show client network <SSID> show ip dhcp binding
WLAN/SSID Validation
show network show network <SSID> show wlan ssid-profile
VC Cluster and Leadership
show swarm state show swarm leader show running-config | include virtual
Switch VLAN and MTU
show vlan port 1/1/x show interface 1/1/x show interface 1/1/x | include MTU
MTU End-To-End Test
ping 8.8.8.8 size 1472 repeat 5
Notes and Recommendations
RW and US APs cannot join the same Virtual Controller cluster because they run different regulatory domains.
RW SSIDs include the “-RW” suffix to avoid SSID duplication inside the same L2/L3 space.
VLAN 735 is used for AP access, VLAN 706 for AP uplinks/mesh/internal management.
Jumbo MTU (9100) is required end-to-end to avoid fragmentation or CAPWAP instability.
Always verify DHCP bindings if clients fail to obtain IP.
Ensure each AP is correctly mapped to its trunk native VLAN.