No DHCP address for any AP122 client

[Trummel]

Hi everyone.

I’m new to Aerohive kit, so I suspect this is a simple lack of knowledge.  

I have an existing site with 6 AP122’s all working fine (configured by my predecessor).  I need to add a remote site.  The VPN’s are in place between the sites.  A client connected directly to the wired LAN at the remote site, picks up a DHCP address from the remote LAN DHCP server without issue. 

I have added a new AP122 on the remote site. It also picks up a DHCP address and downloads the profile from ECIQ.  Client devices seem to connect to the AP122 without issue, but don't get an IP address from the local DHCP server.  I have tried adding the local server to the AP122 DHCP helper, but that makes no difference. There is no vlan tagging of any sort configured on the remote site.  Other AP’s  (not Aerohive) allow DHCP clients on without any issues.

Any suggestions what I could be missing gratefully received.

[SamPirok]

Hi Trummel, I’d start with running a VLAN probe on the AP CLI to make sure it can get traffic to and from the correct DHCP server. The command to run a VLAN probe is: 

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. You should see the subnet returned if the VLAN probe is successful, I’d recommend confirming that is the subnet you would expect the DHCP server to return.