We are excited to announce that we have launched our new Hive Community! HiveNation will remain as an archive, but all new posts, discussions, and articles will be created on Hive Community. You can visit our new community at thehivecommunity.aerohive.com

So: Having read the other questions, I SSHed into the AP via the fallback IP and found out that the CAPWAP server IP is 0.0.0.0

Maybe that's the problem? No DNS Server found? So I even told the AP * ntp server <NTP Source IP Address>* dns server-ip <DNS Server IP Address>(I found this somewhere)﻿Now there is a server IP, but it still can't connect. Maybe one of you has an idea!

I assume that you guys have a firewall at school. Do you have udp port 12222 open to the internet? if that fails, it will failback to TCP 80 and 443 are tried. The failback will work, but it has been my experience that having 122222 open is more reliable.

Thanks for the advice. We do hava firewall and it seems to be blocking the port 12222. I need the school district tech people to change that. It doesn't seem to go to the other ports.The ping doesn't go through, but the DNS seems to work, I get an IP number to ping.

You can use the IP address 52.5.91.205 from your ping as the CAPWAP server name. i.e.:

capwap client server name 52.5.91.205

then do the

no capwap client enable capwap client enable

commands.
Then your APs should be able to talk to the CAPWAP server via http on port 80 and appear in HiveManager Online.
If the AP can't talk to the redirector, then it can't get your CAPWAP server name/IP and will not find your hive settings.

Yes, the Capwap Client IP, is of course your APs IP address. Are you sure that it was getting one? The only times that I've not seen one of my APs not get an IP address is when one of the following occurs:1. Client not getting DHCP because dhcp server server or relay agent not working correctly2. Incorrect switch port settings: example, AP is configured for trunk port and the switch port is set to static access or vice versa, switch port set to wrong vlan, etc.

Since I don't have a DHCP, this can't be the problem.I gave it a fixed IP that I can use to SSH onto the device. But in the config the IP is gone. Must have been one of the many things I tried to make it work.

If you've changed it over to using HTTP over TCP via port 80, just do a normal ping, not a CAPWAP ping of the IP. This will tell you if you have L3 connectivity to the server. A show int mgt0 dhcp client will also show you any IP info obtained via DHCP.

Comparing your output to mine, I don't see any obvious discrepancies. It look and sounds like it should all work at this point unless your school firewall is still blocking somehow. For instance, to access the internet from a workstation, do you have to pass any network credentials to a proxy server? That would definitely cause a problem for the APs since they aren't passing those credentials. We used to have a device like that and we'd have to tell the server to allow this particular client IP to by-pass network authentication. In re-reading through the posts, I see that you had them connected to HMOL from home. Probably a stupid question, but you didn't remove them from the inventory did you (Monitor > Device Inventory > Remove)? If you did, the APs won't reconnect to HMOL because the server no longer recognizes them as valid APs for your site. To remedy that, you'd have to click on Device Inventory > Add/Import and add the serial numbers of each AP. If by chance you get an error about the serial already existing, you would have to call support and have them associate the serial number with your VHN.

It's not losing its IP address. It is restarting the connection process. A "show int mgt0" will show you that the statically assigned IP that you gave it still applies. Your issue most likely lies with your firewall and/or content filter. Look for any logs in them that source from the statically assigned IP that you gave the AP.

Thanks Brian, I think you're right that our firewall is most likely the main problem.I guess I need to have the school district people open the ports for me.The fallback IP seems to work fine.The AP works and provides an internet connection, but just can't connect through the firewall.It was to my understanding that the connection will (eventually) try to use port 80 if others fail. Apparently this isn't so.