Environment : Tested in 6.3.1.9 Version
Mesh radio will Still work eventhough Radio is enabled or disabled
“When Radio-enabled, virtual-APs that are configured as valid on the mesh radio will be configured in the usual way once the mesh-node receives the configuration from the controller,
And clients can connect to those VAPs. The mesh-radio bandwidth will then be shared between mesh-backhaul traffic and client traffic. When rf-radio-profile:radio-enable is disabled no client access-VAPs will be configured on the mesh radio,
and the mesh-radio will continue to carry only mesh-backhaul traffic. The rf-radio-profile:radio-enable attribute should not affect the mesh-radio and mesh_p/mesh_c interfaces but should bring the access-VAPs up or down.
An ARM profile can be assigned to the mesh-radio and ARM features such as automatic channel-assignment will work as normal on mesh-portals (it will remain disabled for mesh-points)”.
Example test outputs
=====================
Here is the A radio profile were the radio is disabled
(Aruba7240) # show rf dot11a-radio-profile default
802.11a radio profile "default"
-------------------------------
Parameter Value
--------- -----
Radio enable Disabled
Mode ap-mode
High throughput enable (radio) Enabled
Very high throughput enable (radio) Enabled
Channel 132
Transmit EIRP 29 dBm
Non-Wi-Fi Interference Immunity 2
Enable CSA Disabled
CSA Count 4
Advertise 802.11d and 802.11h Capabilities Disabled
Spectrum Load Balancing Disabled
Spectrum Load Balancing Mode channel
Spectrum Load Balancing Update Interval (sec) 30 seconds
Spectrum Load Balancing Threshold (%) 20 percent
Spectrum Load Balancing Domain N/A
Beacon Period 100 msec
Beacon Regulate Disabled
Advertized regulatory max EIRP 0
ARM/WIDS Override OFF
Reduce Cell Size (Rx Sensitivity) 0 dB
Energy Detect Threshold Offset 0 dB
Management Frame Throttle interval 1 sec
Management Frame Throttle Limit 20
Maximum Distance 0 meters
RX Sensitivity Threshold 0 dB
RX Sensitivity Tuning Based Channel Reuse disable
Adaptive Radio Management (ARM) Profile default
High-throughput Radio Profile default-a
AM Scanning Profile default
Output of the mesh portal were we can the A radio us active
=============================================================
(Aruba7240) # show ap mesh active
Mesh Cluster Name: aruba-mesh
-----------------------------
Name Group IP Address BSSID Band/Ch/EIRP/MaxEIRP MTU Enet Ports Mesh Role Parent #Children AP Type Uptime
---- ----- ---------- ----- -------------------- --- ---------- --------- ------ --------- ------- ------
00:24:6c:cd:86:1a default 172.16.0.253 00:24:6c:58:61:a8 802.11a/132/29/29 1500 - Portal - 0 175P 5d:9h:45m:51s
Output of the Ap bss table were the A radio is disabled.
========================================================
Aruba AP BSS Table
------------------
bss ess port ip phy type ch/EIRP/max-EIRP cur-cl ap name in-t(s) tot-t mtu acl-state acl fm
--- --- ---- -- --- ---- ---------------- ------ ------- ------- ----- --- --------- --- --
00:24:6c:58:61:a0 Arubatest N/A 172.16.0.253 g-HT ap 6/15/19 0 00:24:6c:cd:86:1a 0 2d:21h:30m:54s 1500 - 1 T
Port information is available only on 6xx controller.
Channel followed by "*" indicates channel selected due to unsupported configured channel.
"Spectrum" followed by "^" indicates Local Spectrum Override in effect.
Num APs:1
Num Associations:0