310I AP Default Profile

[OGB-NIKO]

Does this solution below work with the NX5500 controller ?

https://extremeportal.force.com/ExtrArticleDetail?an=000093990

[Christopher_Fra]

The following is a Knowledge Article explaining manual/static controller host entry for WiNG APs to adopt over L3 (recommend using MiNT Level 2 for remote Rf-domains):

https://extremeportal.force.com/ExtrArticleDetail?an=000079188&q=Wing%20controller%20host

Otherwise, you will need to follow the documentation that Chris provided regarding DHCP option 191 on external DHCP server that serves the APs. 

For Windows Servers DHCP, option is 191 and format is ascii/string: 

pool1=xxx.xxx.xxx.xxx, yyy.yyy.yy.yyy;level=z (x represents primary wireless controller. Y represents standby controller, if cluster is deployed, and z represents MiNT Level 1 or Level 2 (for remote site AP in different Rf-domain, Level 2 is recommended)

[ckelly]

The ‘controller host’ entry is what is placed on the AP either directly...or as part of the AP’s profile….or both. This is a manual process and would only be needed if the AP and controller are on different VLANs. If the APs and controller on the same VLAN, the APs will automatically discover the presence of the controller without you making any configuration changes or setting up DHCP Option 191. This is layer-2 adoption. Super simple. Plug in the AP and it finds the controller on its own. (on same VLAN)

But, if you need an AP to be able to find the controller when the AP and controller are different VLANs, then you would need to either log into the APs and manually add the controller host entry or configure the DHCP server with Option 191 so that the AP learns the controller’s address as part of the DHCP lease process. Another option is to add an A-record to your internal DNS server that will translate a fixed hostname address to that of the controller.

So, in your case, if you are manually adding the controller host entry to the APs one at a time (manually), then no, you do not need to do anything with the DHCP server. But, this would mean you need to log into each of those APs to do this. That is the reason why the DHCP Option 191 and DNS options exist - to automate the process.

[OGB-NIKO]

Yes the DHCP server that sits on the same subnet as the controller does that DHCP server also require that same string created on it ? Not the other subnets that i have been adding it to

[ckelly]

Not 100% sure I know what you mean here.

Can you give me an example of what you are referencing? (Is this something on the DHCP server or something else?)