Hi @GRL 

Thanks for posting in our business forum.

The remote site adoption and other description, are you referring to the controller being on a remote site?

GRL wrote

I have an ES205G that I am testing and will be installing at one of my remote sites.

 

I have discovered that it does not become visible on the site>devices page unless you log into its stand alone GUI and set the controller IP to where it needs to be.

 

On my main site where controller is, this is not a problem and it works immediately.

 

I have DHCP option 138 set to my controller IP on both the remote sites management vlans.

 

I think this may be because remote sites are inherently on a different IP range to the controller, so it seems to ignore the option138 setting served by the gateways at the remote sites.

 

Once logeed into standalone GUI for the switch and set its controller IP - adoption proceeds as normal.

 

Tested on a remote site adopted inside VPN and another adopted over port forward.

If it is the remote site, I think 138 does not work really well with this. If it is local, that should be fine.

Strange

I haven't had any issues with setting 138 on any of the remote sites - last month I added a SG2008P, didn't pre-config it at all - just plugged it in, controller saw it and adopted. (site adopted in VPN) Same when I added another EAP650 to a different site (site adopted via port forward)

Its only the ES205G model that i am seeing this behavior where the controller doesn't even see it as pending - just not on the list, until i manually set its controller IP in standalone.