Reset Search



CAPWAP Guide for HiveManager Classic

« Go Back


TitleCAPWAP Guide for HiveManager Classic

What is CAPWAP?

CAPWAP (Control And Provisioning of Wireless Access Points) is the process that is used to connect devices to the HiveManager.
  • HiveManager Classic
  • All HiveOS devices
    • Does not include SR22XX, SR23XX, or any Dell switch models.

How to SSH in to a device using PuTTY

CAPWAP Commands

Checking the CAPWAP status:
  • show capwap client
    • This will bring up the current AP settings.
      • Ideally, the RUN state should say "Connected securely to the CAPWAP server" to indicate the device is connected to the HiveManager.
      • Check that the HiveManager Primary Name is set to the correct HiveManager destination.
        • To confirm, check the URL displayed when logged in to the HiveManager Classic instance, up to
User-added image
  • If this is not correct, run the following commands to manually set the CAPWAP settings.

Setting CAPWAP manually
  • no hivemanager
    • Erases current CAPWAP settings
  • hivemanager [address] primary
    • Where the brackets are, enter the IP address of your hive manager. (I.e. hivemanager You can also use the URL address of your hive manager; so, for example using the picture above, the command would look like:
      • hivemanager primary
  • capwap client vhm-name [name]
    • Where the brackets are, you would enter the name of your VHM. So, for example, the command would look like:
      • capwap client vhm-name Aerohive_Training
        • To check your VHM name, look at the label next to MyHive in the Classic GUI
User-added image
  • save config
    • Will save the changes just made
  • no capwap client enable
  • capwap client enable
    • These two commands cycle your CAPWAP settings, allowing the new settings to come into effect.
  • show capwap client
Troubleshooting CAPWAP

It’s normal for the device to take up to a couple minutes after running receiving these commands before it can re-establish connection to the HiveManager. If it does not connect after running these commands, some more advanced troubleshooting steps are:
  • Ping the default gateway
    • If this fails, skip to setting the IP address and default gateway manually (see instructions below).
  • Ping google at
    • If it works we know we can get out to the internet (skip to pinging to test DNS)
    • If it fails it means we don’t have internet access (skip to setting IP address and default gateway manually).
  • Ping
    • If this fails but we were able to get to, we know DNS is not working (skip to setting DNS manually).
  • Manually setting IP address and Default gateway
    • Enter the following commands:
      • Int mgt0 ip <ip address> /<netmask>. For example if the IP address was and the netmask was, the command would be “int mgt0 ipâ€�
      • Ip route default gateway <address. For example, if the default gateway was, the command would be “ip route default gateway
  • Setting DNS manually
    • Enter the following command:
      • Dns server-ip <address>. For example, if the DNS address was, the command would be “dns server-ipâ€�.
      • If you want to see what the current DNS settings are, run the command “show dnsâ€�.
      • You can also check the DNS settings for your network policy by going to (Configuration> Select Network Policy> Additional Settings> Management server Settings> DNS Server> Modify> Check what the DNS server is).
  • Check the VLAN
    • Run a VLAN probe by entering the following command:
      • int mgt0 dhcp-probe vlan-range # # (if you want to run a range you would do 1 5 for example, if you want to do one you would just do 5 5 for example. So if I was running a VLAN probe for VLAN 5, the command would be “int mgt0 dhcp-probe vlan-range 5 5â€�.)
      • To set the VLAN you want to use manually, run the command “int mgt0 vlan #â€�. So if I wanted to set the VLAN to 5, the command would be “int mgt0 vlan 5â€�.
      • If the VLAN probe fails, we need to make sure the port is set correctly on the back end.
  • Check the ports
    • We need UDP 12222 and TCP 22 allowing outbound traffic on any firewall or content filter you have.
    • To confirm that TCP 22 is open, run the following command:
      • exec _test tcp-service host <HiveManager IP> port 22. So if my hive manager address was, the command would be “exec _test tcp-service host port 22â€�.
    • If we still can’t get out, try switching over to HTTP instead of UDP by running the following commands in order:
      • capwap client transport http
      • save config
      • no CAPWAP client enable
      • CAPWAP client enable
  • Ask Aerohive Support to check the Redirector to make sure the AP is pointed at the correct hive manager (be sure to provide them with the serial number of the device, and your VHM ID which can be found by going to Help> About Hive Manager). *If you are using a virtual appliance or on premise hive manager, just ask Support to make sure the serial number is not assigned to anything in our redirector.
    • **If the device has connected to your hive manager before, this is likely not your issue.
  • If you’ve performed all of these steps and the device still does not connect to your hive manager, set the device back to factory default settings and run through this guide one more time.
    • You can set the device to factory default settings two ways:
      • You can hold down the reset button on the device for 10 seconds.
      • You can run the command “reset configâ€�.
  • If it still doesn’t connect, run CAPWAP debugs.
    • Run the command “show log buff | include all debugâ€�
Additional notes



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255