Wireless Access

Occasional Contributor II

provision ap ip address via the controller command line

Does anybody know how to provision an ap and give it a static ip address using the controller command line?


I have 500 AP's that I would like to convert from DHCP over to static IP's, but I dont want to do them one by one in the controller GUI.  I would like to provision an ap via the controller command line and give each AP a static ip and subnet mask (I dont need a gateway or dns).


I would also be interested in any other method of automating the assignment of static IP's to an AP.


Thanks in advance!



Guru Elite

Re: provision ap ip address via the controller command line

You have a problem.


This is the list of commands generated when you convert an AP from DHCP to Static:

provision-ap copy-provisioning-params ap-name "Office-225"
provision-ap installation default
provision-ap ipaddr
provision-ap netmask
provision-ap gateway
provision-ap dns-server-ip
provision-ap domain-name none.com
provision-ap no external-antenna
provision-ap no usb-dev
provision-ap no usb-dial
provision-ap no usb-init
provision-ap no usb-modeswitch
provision-ap no usb-passwd
provision-ap no usb-tty
provision-ap no usb-type
provision-ap no usb-user
provision-ap server-name aruba-master
provision-ap ap-group "default"
provision-ap ap-name "Office-225"
provision-ap no syslocation
provision-ap no remote-ap
provision-ap reprovision ap-name "Office-225"

 You would have to (1) identify the list of ap names you would need to convert (2) identify the range of static ip addresses you want to provision (3) write a script to merge the two (4) Hope you do not make any mistakes, because statically addressed access points do not recover themselves.


Before embarking on this, the big question is why you would want to convert from DHCP to static, because statically ip addresses access points do not recover themselves.  In addition, if you accidentally configure a duplicate ip address for two, you probably will have to get into the ceiling to pull them down to reset them.  Also, if you ever decide to change the existing network below the access points to expand or re-number the network, you must manually change all 500 access points again.


Aruba access points were designed to have DHCP addresses and the controller will keep track of the DHCP-assigned address, even if the access points are down.  If you have Airwave, that will also keep track of all the access points, in addition to historical information.  You are a couple mis-assigned static addresses from climbing into a ceiling if you do not use DHCP.  I would say that on a small scale, static ip addresses for access points is not bad.  On a large scale, it makes it much much more difficult, because you have to maintain a list of ip addresses to names of APs manually, which can be brutal....


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: provision ap ip address via the controller command line

Thanks very much for this - it settles it for me - no statics on AP's.  I was trying to develop the script below and got very scared thinking about the damage I could do.


This all started because we have the DHCP server for the AP's on the controller.  When adding a second controller for redundancy we discovered that you must split the DHCP scope between the controllers if you want DHCP to persist when one controller is down.  This means that in a controller outage, at least some AP's will get new IP addresses, forcing an AP reboot.  We did not have another redundant DHCP option so I started exploring static IP's on the AP's.


We will get a redundant DHCP server setup going on a pair of new routers that will be going in soon.



Re: provision ap ip address via the controller command line

Canucklehead wrote:

We will get a redundant DHCP server setup going on a pair of new routers that will be going in soon.



just my opinion, get a dedicated DHCP server. aruba mobility controller should control access points and transfer traffic, not hand out IPs, firewalls should block access, not hand out IPs, routers should route traffic not hand out IPs. if you cant do it any other way, sure you can combine things, but if you can, just use an actual DHCP server.

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