Aerohive VPN solution - client reservation problem with BR200WP

  • 1
  • Question
  • Updated 1 year ago
  • Answered
Hello,

We are running a PoC for 200 locations and we have a problem with clients that are changing the IP address...which shouldn't be the case. Please see logs below:


08EA444072C0 02/06/2017 12:25:08 PM Station(54a2:7439:14d4) ip(10.201.12.46) changed to 10.210.192.178 AUTH
E01C41313980 02/06/2017 12:24:39 PM Station(f4cf:e201:34ec) ip(10.201.12.75) changed to 10.210.193.38 AUTH
08EA444072C0 02/06/2017 12:24:35 PM Station(54a2:7439:14d4) ip(10.210.192.178) changed to 10.201.12.46 AUTH
E01C41313980 02/06/2017 12:24:30 PM Station(f4cf:e201:34ec) ip(10.210.193.38) changed to 10.201.12.75 AUTH
08EA44515FC0 02/06/2017 12:24:24 PM Station b87c:f201:20ef is de-authenticated from 08ea:4451:5fc4 thru SSID CMB-to-MOL vid 10 AUTH
E01C4131D300 02/06/2017 12:23:36 PM Station(003a:7d60:200c) ip(10.201.12.96) changed to 10.210.193.122 AUTH
08EA444072C0 02/06/2017 12:23:19 PM Station(54a2:7439:14d4) ip(10.201.12.46) changed to 10.210.192.178 AUTH
 E01C41313980 02/06/2017 12:23:11 PM Station(f4cf:e201:34ec) ip(10.201.12.75) changed to 10.210.193.38 AUTH
08EA444072C0 02/06/2017 12:23:06 PM Station(54a2:7439:14d4) ip(10.210.192.178) changed to 10.201.12.46 AUTH
E01C4131D300 02/06/2017 12:23:04 PM Station(003a:7d60:200c) ip(10.210.193.122) changed to 10.201.12.96 AUTH
E01C41313980 02/06/2017 12:23:00 PM Station(f4cf:e201:34ec) ip(10.210.193.38) changed to 10.201.12.75 AUTH
08EA444072C0 02/06/2017 12:21:54 PM Station(54a2:7439:14d4) ip(10.201.12.46) changed to 10.210.192.178 AUTH
E01C41313980 02/06/2017 12:21:45 PM Station(f4cf:e201:34ec) ip(10.201.12.75) changed to 10.210.193.38

Customer receives this logs every 30-40 seconds only from 5 locations...but soon we will be expending to 200...and until that time, we need to solve this...

We assume that this is because partner has configure VPNs with VLAN-pooling and SEs from support only told us that we shouldn't be using VLAN-pooling...but didn't provide further steps on how to solve it. Now i would like to ask for your help.

We also think that this could be resolved by configuring "client reservation" on BR200WP, but this functionality is only supported on version 6.6r1...but we can't find it under software downloads from Aerohive page...:/

Would anyone be able to provide us with some help on what could be causing these logs and how to solve it? 

If this is a configuration issue, i would be also willing to pay for consultation services.

Thank you,

Best regards,
Photo of Aleš Gošek

Aleš Gošek

  • 9 Posts
  • 0 Reply Likes
  • frustrated

Posted 1 year ago

  • 1
Photo of Gary Smith

Gary Smith, Official Rep

  • 299 Posts
  • 61 Reply Likes
Official Response
Hi Aleš,

I worked with you and your partner via the support ticket that you raised. I believe that the issue is now under control. That is, the issue reported is that the IP is changing but in fact, it is a cosmetic issue. What we are seeing is the HiveManager and the BR200 logs showing that the client device is using a different IP address. 

08EA444072C0 02/06/2017 12:25:08 PM Station(54a2:7439:14d4) ip(10.201.12.46) changed to 10.210.192.178 AUTH \
08EA444072C0 02/06/2017 12:24:35 PM Station(54a2:7439:14d4) ip(10.210.192.178) changed to 10.201.12.46 AUTH\

08EA444072C0 02/06/2017 12:23:19 PM Station(54a2:7439:14d4) ip(10.201.12.46) changed to 10.210.192.178 AUTH\
08EA444072C0 02/06/2017 12:23:06 PM Station(54a2:7439:14d4) ip(10.210.192.178) changed to 10.201.12.46 AUTH\
08EA444072C0 02/06/2017 12:21:54 PM Station(54a2:7439:14d4) ip(10.201.12.46) changed to 10.210.192.178 AUTH\


The issue is not service affecting and the client is not seeing any disconnects or performance issues as a result. The reason we believe that this is being seen is that the client device is configured with a loopback IP address. The two IP addresses we see in the logs are; the loopback IP (10.210.x.x) and the DHCP IP (10.210.x.x). There is no risk of duplicate IP's in this situation.

As an advisory, I asked for the HiveOS-VA to be upgraded to the latest and greatest 6.5r6. It was previously on 6.6r2. 

I hope the issue is addressed appropriately.

Kind Regards,
Gary Smith