Problem with OC200 and EAP 653 on subnet other than 192.168.0.X

Problem with OC200 and EAP 653 on subnet other than 192.168.0.X

Problem with OC200 and EAP 653 on subnet other than 192.168.0.X
Problem with OC200 and EAP 653 on subnet other than 192.168.0.X
a week ago - last edited a week ago
Model: OC200  
Hardware Version: V1
Firmware Version: v5.15.24.21

Tried to set up 8x EAP653's with my OC200 today, ran into issues because they either did not adopt, or if they did adopt would soon disconnect.
Worked out the issue was them falling back to their default IP 192.168.0.254 during the adoption process, despite having one assigned on the correct subnet by the router.
NB my subnet is not the same as the default fallback one 192.168.0.x so I think that got it confused as it could not reach them anymore mid adoption.
Had to log into each one set a static IP and then adopt, this worked. 

However, its a massive inconvenience as you need to reset them, change password, set up a network, then adopt them, I am just glad I did not install them before I found the issue as they need a hard reset to get them out of adopted mode when the adoption finally fails.

I suspect the fallback IP code has some issues and it chooses to fall back despite having been issued a valid DHCP IP.
Did contact tech support and they seem to agree its an issue and said they'd raise it with the dev team.

Posting this here to help other avoid a whole day of frustration.

 

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Problem with OC200 and EAP 653 on subnet other than 192.168.0.X-Solution
a week ago - last edited a week ago

  @RLeinfellner 

 

I havent seen anything like this, i have three sites with 172.x.x.x management networks, and my EAPs get DHCP via reservation, become adoptable, and adopt and configure correctly, even on a remote site where everything is adopted inside its vpn tunnel

 

I even tested this recently, i forgot an EAP form controller, and when it rebooted it came back up with the reserved IP and adopted fine without me changing any of its settings or even going into its standalone GUI

Have you set option 138 in DHCP settings on your management network to the controller IP ?

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:Problem with OC200 and EAP 653 on subnet other than 192.168.0.X-Solution
a week ago - last edited a week ago

  @RLeinfellner 

 

I havent seen anything like this, i have three sites with 172.x.x.x management networks, and my EAPs get DHCP via reservation, become adoptable, and adopt and configure correctly, even on a remote site where everything is adopted inside its vpn tunnel

 

I even tested this recently, i forgot an EAP form controller, and when it rebooted it came back up with the reserved IP and adopted fine without me changing any of its settings or even going into its standalone GUI

Have you set option 138 in DHCP settings on your management network to the controller IP ?

Recommended Solution
  0  
  0  
#2
Options