topic Re: DHCP NX5500 Cluster in ExtremeWireless (WiNG)

DHCP NX5500 Cluster

OGB-NIKO — Wed, 09 Jan 2019 17:57:25 GMT

What Windows server DHCP scope/server options need to be configured when working with an active passive 5500NX controller cluster for layer3 ap adoption to work properly ? Can a cluster be update or should i update both controllers before building a cluster ?

Our nx5500 controllers will be handing out the address and not our DHCP servers we just need to point everything in the right direction.

Re: DHCP NX5500 Cluster

ckelly — Wed, 09 Jan 2019 23:12:21 GMT

Not completely understanding what you're asking here, so let's break things down first so we're on the same page.

You have an Active/Standby cluster.
You have a DHCP service setup and running on the cluster config.
You wan to adopt APs at layer-3.

I think what you're looking for is maybe the DHCP Option configuration to allow zero-touch layer-3 AP adoption. If that's the case, then you need to configure DHCP Option 191. (maybe this is the 'config' you're asking for?)

But.....the fact that you want to do layer-3 adoption leads me to think that the APs won't have layer-2 connectivity to the controller cluster (routed connection). In that case, you'll need a DHCP helper on the APs VLAN so that it can allow for DHCP operations between the APs and the controller cluster.
But if this isn't the case and the APs are on the same management VLAN as the controller cluster, then you could just set this up with layer-2 adoption.

I'll stop there because anything further would be based on speculation of how you have your network setup and what you are needing to achieve.
What does the network(s) look like...as far as where the APs and controller sit?

Re: DHCP NX5500 Cluster

OGB-NIKO — Wed, 09 Jan 2019 23:28:33 GMT

Chris
This are our current options on DHCP servers in a different subnet for the RFS6000 that is running would it be the same for NX5500 ?

Re: DHCP NX5500 Cluster

ckelly — Thu, 10 Jan 2019 03:28:29 GMT

Based on that screenshot, no.

The Option Type setup will look like this:

Name: ControllerIPAddress
Data Type: String
Code: 191
Description: ControllerIPAddress

And in the String Field, the Value will look like this:

pool1=10.10.10.10, 10.10.10.11;level=2 (10.10.10.10 and 10.10.10.11 being the controller's 2 IP addresses)

Re: DHCP NX5500 Cluster

OGB-NIKO — Fri, 11 Jan 2019 20:23:56 GMT

That would be the only option that we would need ?

Re: DHCP NX5500 Cluster

ckelly — Fri, 11 Jan 2019 22:26:26 GMT

Yes. For WiNG-5 APs, you only should use Option 191. Relevant section from another guide is here.
Deployment Guide - Start Page 108

The Option-189 that you have there is for WiNG-4 migrations. If all of your APs/controllers are running WiNG-5 now, then I don't think that this DHCP Option is even used by the APs any longer.

Your Option-191 setup should end up looking like this: (This assumes level-2 MINT adoption)