First time setup for Aerohive

  • 1
  • Question
  • Updated 3 years ago
I am trying to switch our old Wi-Fi infrastructure for Aerohive. I have a windows server that provides the DHCP. 
Now, when I first setup the APs (AP230) and the Switch (SR2124P) it causes issues generally with any Mac devices and some Samsung devices.

Do I need to change anything on the default setup for those machine to be connected? what happens is that they dont get IP assigned, but when I see the DHCP server I see an IP there for that specific device. If I delete the lease, then it gets it ok. I notice this only wit the new Wi-Fi, the Old Wi-Fi APs didn't show this behavior, so I am discarding issues on the DHCP server for now.
Photo of gerjimi

gerjimi

  • 17 Posts
  • 1 Reply Like

Posted 3 years ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
what happens is that they dont get IP assigned, but when I see the DHCP server I see an IP there for that specific device. If I delete the lease, then it gets it ok.
What does Client Monitor show?

See: http://boundless.aerohive.com/blog/troubleshooting-wi-fi-connectivity-with-the-hivemanager-client-mo...

(Note, this is not applicable to HM-NG where you need to use the Troubleshooting tab.)

Nick
Photo of Kevin Gee

Kevin Gee

  • 54 Posts
  • 4 Reply Likes
Welcome to the party :-)

This is ringing a bell with me. When we first set up our AP 230s we had a problem specific to Apple devices, I think the resolution may have been to either to check or uncheck WMM. Sorry, memory is a bit hazy, I will ask a colleague if he remembers.
Also, what HiveOS version are you running?  I think this may have been fixed on later versions, we are running HiveOS 6.4r1g.2138 ,
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
He said he was running with the defaults. But yes...

OP: If you have disabled WMM by accident (it is enabled by default), you will definitely have issues. It must be enabled.
(Edited)
Photo of gerjimi

gerjimi

  • 17 Posts
  • 1 Reply Like
I am on the version (6.4r1e) and I have not touched WMM (I see that it is enabled)
Photo of gerjimi

gerjimi

  • 17 Posts
  • 1 Reply Like
This is what I see on the log on one of the systems:

2015-11-19 09:08:51AP-LeftD854A2212A14BasicRx auth <open> (frame 1, rssi -46dB)2015-11-19 09:08:51AP-LeftD854A2212A14BasicTx auth <open> (frame 2, status 0, pwr 19dBm)
2015-11-19 09:08:51AP-LeftD854A2212A14BasicRx assoc req (rssi -46dB)
2015-11-19 09:08:51AP-LeftD854A2212A14BasicTx assoc resp <accept> (status 0, pwr 19dBm)
2015-11-19 09:08:51AP-LeftD854A2212A14InfoWPA-PSK auth is starting (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14InfoSending 1/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14InfoReceived 2/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14InfoSending 3/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14InfoReceived 4/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14InfoPTK is set (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14BasicAuthentication is successfully finished (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14BasicAuthentication is successfully finished (at if=wifi0.1)
2015-11-19 09:08:51AP-LeftD854A2212A14InfoIPv6 address fe80::62f8:1dff:fece:d620 is snooped.
2015-11-19 09:08:52AP-LeftD854A2212A14Infostation sent out DHCP DISCOVER message
2015-11-19 09:08:54AP-LeftD854A2212A14Infostation sent out DHCP DISCOVER message
2015-11-19 09:08:54AP-LeftD854A2212A14InfoDHCP server sent out DHCP OFFER message to station
2015-11-19 09:08:56AP-LeftD854A2212A14Infostation sent out DHCP REQUEST message
2015-11-19 09:08:56AP-LeftD854A2212A14InfoDHCP server sent out DHCP ACKNOWLEDGE message to station
2015-11-19 09:08:56AP-LeftD854A2212A14BasicDHCP session completed for station
2015-11-19 10:31:56AP-LeftD854A2212A14InfoSnooped IPv6 address fe80::62f8:1dff:fece:d620 is expired
2015-11-19 11:02:01AP-LeftD854A2212A14BasicSta(at if=wifi0.1) is de-authenticated because of notification of driver
2015-11-19 11:27:03AP-LeftD854A2212A14BasicRx auth <open> (frame 1, rssi -43dB)
2015-11-19 11:27:03AP-LeftD854A2212A14BasicTx auth <open> (frame 2, status 0, pwr 19dBm)
2015-11-19 11:27:03AP-LeftD854A2212A14BasicRx assoc req (rssi -43dB)
2015-11-19 11:27:03AP-LeftD854A2212A14BasicTx assoc resp <accept> (status 0, pwr 19dBm)
2015-11-19 11:27:03AP-LeftD854A2212A14InfoWPA-PSK auth is starting (at if=wifi0.1)
2015-11-19 11:27:03AP-LeftD854A2212A14InfoSending 1/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 11:27:03AP-LeftD854A2212A14InfoReceived 2/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 11:27:03AP-LeftD854A2212A14InfoSending 3/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 11:27:03AP-LeftD854A2212A14InfoReceived 4/4 msg of 4-Way Handshake (at if=wifi0.1)
2015-11-19 11:27:03AP-LeftD854A2212A14InfoPTK is set (at if=wifi0.1)
2015-11-19 11:27:03AP-LeftD854A2212A14BasicAuthentication is successfully finished (at if=wifi0.1)
2015-11-19 11:27:05AP-LeftD854A2212A14Infostation sent out DHCP REQUEST message
2015-11-19 11:27:05AP-LeftD854A2212A14InfoDHCP server sent out DHCP ACKNOWLEDGE message to station
2015-11-19 11:27:05AP-LeftD854A2212A14BasicDHCP session completed for station
2015-11-19 11:27:05AP-LeftD854A2212A14BasicIP 192.168.99.85 assigned for station
2015-11-19 11:27:07AP-LeftD854A2212A14InfoIPv6 address fe80::62f8:1dff:fece:d620 is snooped.



It gave an address later on but on previous attempt there was no IP assigned (see 2015-11-19 09:08:56 Vs. 2015-11-19 11:27:05)

Note: on wired connections, this does not happen at all.
(Edited)
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi gerjimi,

Sadly, that doesn't really get us any further.

Can you get a packet capture on both the wired and wireless side please? We should then be able to see where your issue is occurring.

http://boundless.aerohive.com/blog/innovative-wi-fi-how-to-do-packet-captures.html

Nick
(Edited)
Photo of gerjimi

gerjimi

  • 17 Posts
  • 1 Reply Like
The option on the link does not show on the Hive Manager. I am also on version 6.5r3 now, and still same issue. 
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Works for me. You are selecting a single online AP first, right?
(Edited)
Photo of gerjimi

gerjimi

  • 17 Posts
  • 1 Reply Like
This is what I get:




I think I am on different portal. I use Hive Manager NG
(Edited)
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Ah, you did not say that you were using HM-NG. Many people are still using classic HM so I assumed you would be. My bad!

This feature of HiveOS has not yet made it in to HM-NG.

You can achieve the same thing at the CLI through: exec capture remote-sniffer

At the CLI we can see the capturing related commands via:

show cmds | include capture
capture save interface <wifix> <string> 
capture interface <wifix> [ count <number> ] [ filter <number> ] [ promiscuous ]
show capture interface <wifix>
show capture local
clear capture local [ <string> ]
exec capture remote-sniffer [ user <string> <string> ] [ host-allowed <string> ] [ local-port <number> ] [ promiscuous ]
show capture remote-sniffer
save {capture} local <string> <location>
save {capture} local <string> <url> [ admin <string> password <string> {basic|digest} ] [ proxy <string> [ proxy-admin <string> password <string> ] ]
There's something to get you started here written by the awesome Crowdie:

https://community.aerohive.com/aerohive/topics/is_there_a_limit_to_the_number_of_wireless_clients_pe...

I suspect that this may over complicate things for you though.

Have you therefore considered opening a support case with your point of support for somebody  to help you?

If you do manage to get packet captures, I am more than happy to analyse them for you.

Nick
(Edited)
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
As you are using HM-NG and not classic HM, what does the new troubleshooting tools show for the client?
Photo of gerjimi

gerjimi

  • 17 Posts
  • 1 Reply Like
Here is the log for that:

2015-11-25 12:17:05 AP-CHM-Admin-Right D854A2220154 Info station sent out DHCP DISCOVER message2015-11-25 12:17:14 AP-CHM-Admin-Right D854A2220154 Info station sent out DHCP DISCOVER message
2015-11-25 12:17:14 AP-CHM-Admin-Right D854A2220154 Info DHCP server sent out DHCP OFFER message to station
2015-11-25 12:17:22 AP-CHM-Admin-Right D854A2220154 Info station sent out DHCP DISCOVER message
2015-11-25 12:17:22 AP-CHM-Admin-Right D854A2220154 Info DHCP server sent out DHCP OFFER message to station
2015-11-25 12:17:31 AP-CHM-Admin-Right D854A2220154 Info station sent out DHCP DISCOVER message
2015-11-25 12:17:31 AP-CHM-Admin-Right D854A2220154 Info DHCP server sent out DHCP OFFER message to station
2015-11-25 12:17:39 AP-CHM-Admin-Right D854A2220154 Info station sent out DHCP DISCOVER message
2015-11-25 12:17:39 AP-CHM-Admin-Right D854A2220154 Info DHCP server sent out DHCP OFFER message to station
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Detail Rx <broadcast> probe req (rssi -90dB)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Basic Tx probe resp (pwr 19dBm)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Basic Tx probe resp (pwr 19dBm)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Detail Rx <broadcast> probe req (rssi -49dB)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Basic Tx probe resp (pwr 19dBm)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Basic Tx probe resp (pwr 19dBm)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Detail Rx <broadcast> probe req (rssi -49dB)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Basic Tx probe resp (pwr 19dBm)
2015-11-25 12:17:40 AP-CHM-Admin-Right D854A2220154 Basic Tx probe resp (pwr 19dBm)

Not really telling me anything. The difference with a working device is that there will be a message telling the IP address. On the DHCP LOG I see the following:

30,11/25/15,11:11:36,DNS Update Request,68.99.168.192,AdministorsAir2,
10,11/25/15,11:11:36,Assign,192.168.99.68,AdministorsAir2,843835607E30,
31,11/25/15,11:11:37,DNS Update Failed,192.168.99.68,AdministorsAir2,2,
30,11/25/15,11:11:37,DNS Update Request,68.99.168.192,AdministorsAir2,,
11,11/25/15,11:11:37,Renew,192.168.99.68,AdministorsAir2,843835607E30,
31,11/25/15,11:11:39,DNS Update Failed,192.168.99.68,AdministorsAir2,2,
30,11/25/15,11:11:39,DNS Update Request,68.99.168.192,AdministorsAir2,,
11,11/25/15,11:11:39,Renew,192.168.99.68,AdministorsAir2,843835607E30,
31,11/25/15,11:11:43,DNS Update Failed,192.168.99.68,AdministorsAir2,2,

 
Photo of gerjimi

gerjimi

  • 17 Posts
  • 1 Reply Like
Any thoughts on this?

Looks like DHCP server sends the offer to the AP but the AP does not do anything with it.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi,

I needed a packet capture to look at this further.

That log doesn't show anything as being wrong from an AP / DHCP server perspective.

I see that you have asked about this in other threads. You may find that enabling the DHCP relay works around this as others have suggested.

Have you updated to 6.5r3 from within HM-NG?

Nick