Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-09-2019 09:57 AM
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.
Our nx5500 controllers will be handing out the address and not our DHCP servers we just need to point everything in the right direction.
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-09-2019 07:28 PM
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)
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)
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-11-2019 02:26 PM
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)
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)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-11-2019 12:23 PM
That would be the only option that we would need ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-09-2019 07:28 PM
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)
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)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-09-2019 03:28 PM
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 ?
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 ?
