Controller Based WLANs

How to bring up mesh point using setenv parameters ?

by ‎08-04-2015 05:49 PM - edited ‎08-04-2015 05:49 PM
Requirement:

Instead of bringing up an AP locally and push the mesh configuration from controller, we can also bring up mesh point using setenv parameters.



Solution:

Instead of bringing up an AP locally and push the mesh configuration from controller, we can also bring up mesh point using setenv parameters. 

STEPS:

  • Copy the output of 'printenv' command from existing mesh point.
  • Add "setenv" and Remove equals (" = ") from the output.
  • Paste the modified output in apboot> mode.
  • save and boot.

 



Configuration:

Example:
========

Collect the below output:

printenv

bootdelay=2
baudrate=9600
autoload=n
boardname=Palomino
bootcmd=boot=ap
autostart=yes
bootfile=mips64.ari
ethaddr=00:24:6c:c3:cb:56
num_ipsec_retry=85
name=00:24:6c:c3:cb:56
group=MESH-GRP
ip6prefix=64
servername=aruba-master
a_ant_gain=ee3efa2492d0e7145c6414f50ffe9d8396540310000x002
g_ant_gain=ee3efa2492d0e7145c6414f50ffe9d8396540310000x002
ap70_ext_ant=1
a_antenna=0
g_antenna=0
usb_type=0
uplink_vlan=0
auto_prov_id=0
is_rmp_enable=0
priority_ethernet=0
priority_cellular=0
cellular_nw_preference=1
usb_power_mode=0
cert_cap=0
mesh_role=1
installation=0
mesh_sae=0
start_type=cold_start
numcores=1
stdin=serial
stdout=serial
stderr=serial
ethact=en0


Paste it in apboot> mode. 

apboot>setenv bootdelay 2
apboot>setenv baudrate 9600
apboot>setenv autoload n
apboot>setenv boardname Palomino
apboot>setenv bootcmd boot ap
apboot>setenv autostart yes
apboot>setenv bootfile mips64.ari
apboot>setenv ethaddr 00:24:6c:c3:cb:56
apboot>setenv num_ipsec_retry 85
apboot>setenv name 00:24:6c:c3:cb:56
apboot>setenv group MESH-GRP
apboot>setenv ip6prefix 64
apboot>setenv servername aruba-master
apboot>setenv a_ant_gain ee3efa2492d0e7145c6414f50ffe9d8396540310000x002
apboot>setenv g_ant_gain ee3efa2492d0e7145c6414f50ffe9d8396540310000x002
apboot>setenv ap70_ext_ant 1
apboot>setenv a_antenna 0
apboot>setenv g_antenna 0
apboot>setenv usb_type 0
apboot>setenv uplink_vlan 0
apboot>setenv auto_prov_id 0
apboot>setenv is_rmp_enable 0
apboot>setenv priority_ethernet 0
apboot>setenv priority_cellular 0
apboot>setenv cellular_nw_preference 1
apboot>setenv usb_power_mode 0
apboot>setenv cert_cap 0
apboot>setenv mesh_role 1
apboot>setenv installation 0
apboot>setenv mesh_sae 0
apboot>setenv start_type cold_start
apboot>setenv numcores 1
apboot>setenv stdin serial
apboot>setenv stdout serial
apboot>setenv stderr serial
apboot>setenv ethact en0
apboot>
apboot>
apboot>
apboot>save
apboot>boot

 

Note: Make sure that the AP is also running controller's AOS version. If not, AP should be upgraded to avoid code mismatch. 

 



Verification

Execute the below commands to verify if the config has been pushed to the AP.

#show ap debug received-config ap-name <ap name>
#show ap mesh topology

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.