The dhcp pool is mapped to the IP address on your VLAN interface.
By putting the client in a specific VLAN, you determine which IP address it will receive.
Please note that running dhcp on the controller is deprecated, also using an external L3 (and DHCP) would be preferred if your network is larger than small.
And ArubaOS 6.5.1.4 is end-of-life, end-of-support and has known security vulnerabilities. Running unsupported equipment (outside lab) would be deprecated as well.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Sep 03, 2024 08:05 AM
From: SANI
Subject: how can I ensure that those connecting to the new SSID receive an IP address from the new DHCP pool?
Hello everyone,
I have an Aruba controller Model: Aruba7010 & Aos: 6.5.1.4 and several access points.
I want to create an SSID on each access point that is isolated from the internal network, but I don't have a WebCC and Policy Enforcement Firewall (PEF)license.
Therefore, I thought about creating a new VLAN and DHCP pool.
What will ensure that when creating a new DHCP pool, the IP addresses don't conflict?
More specifically, how can I ensure that those connecting to the new SSID receive an IP address from the new DHCP pool?