09-07-2018 06:01 PM
11-19-2018 02:59 PM
I see this thread has been idle for a bit, but in case you all are still having issues or if someone else runs in to this later on, when we see the AP connect and clients not obtaining IP addresses, we'd want to look in to the VLANs and switch port settings. If you're using more than one VLAN on your network, the switches need to be trunked to allow all the VLANs in use. To make sure a client connected to an particular AP should be able to reach a DHCP server on the VLAN assigned to it, run the following command on the CLI of the AP:
int mgt0 dhcp-probe vlan-range # #
*If you want to run a range you would do 1 5 for example, if you want to check a single VLAN you would just use that VLAN number twice, such as 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”.
09-07-2018 07:13 PM
I am also having this issue with a 230. I am going to look into the Client Monitoring but please do let me know what you find out on your end.
09-07-2018 07:02 PM
I setup the Client Monitor, traffic will be light until Monday. I did just receive this error.
"The current capwap delay time higher than threshold value"
09-07-2018 06:47 PM
I am new to the Aerohive system. Yes the WAP reports to the manager. I can see clients but they have 0.0.0.0 as an IP. I have not concoled into a AP. I'm not familiar with "show station" command. I'll research that. Yes I'm using HM classic. again not familiar with client monitor. Thank you for giving me a direction, I will research these suggestions and post what I discover.