Original Message:
Sent: Jan 21, 2026 11:50 PM
From: Te10
Subject: DHCP POOLs
Ok I got you now
So you mean i put the ip helper in the management interface vlan in access switch that is connected me to core and put the imterface vlan of the client in core as ip helper which my default router
But before this actually yesterday it worked for me without this configuration but i faced an issue that access points were able to get an IP address but PCs were not able that means client can reach dhcp server, is this step you provided will resolve the issue i am facing
Original Message:
Sent: Jan 21, 2026 11:15 PM
From: shpat
Subject: DHCP POOLs
Do you have a default route towards your core? ip route 0.0.0.0/0 192.168.60.1
Your access switch must have a DHCP helper for the specific SVI, in your case:
Interface vlan 60
Ip address 192.168.60. 11
ip helper-address 192.168.61.1
------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
Original Message:
Sent: Jan 20, 2026 11:57 PM
From: Te10
Subject: DHCP POOLs
I didn't get it
Let me post my config here
2 vsx cores configuration
Vlan 60 management
Vlan 61 data
Interface vlan 60
Ip address 192.168.60. 2
Active gateway 192.168.60. 1
Interface vlan 61
Ip address 192.168.61. 2
Active gateway 192.168.61. 1
Dhcp-server vrf default
Range 192.168.61. 50 192.168.61. 254
Leases 12:00:00
Default-router 192.168.61. 1
Enable
Multi chassies lag
Native vla 1
Trunk allowed all
Same in other vsx pair
_________________
Access switch configuration
Vlan 60 management
Vlan 61 data
Interface vlan 60
Ip address 192.168.60. 11
I could not ping first after default route to 192.168.60.1 i could ping
Lag
Vlan trunk allowed all
Native vlan 1
Original Message:
Sent: Jan 20, 2026 11:22 PM
From: shpat
Subject: DHCP POOLs
On the access-switch, in the client vlan, you need to make it as and interface (which will be the default gateway for your clients) and then you need to configure the dhcp-helper.
Something like
interface vlan 30
ip address 10.30.30.1/24
ip helper-address 10.30.30.10
no shutdown
------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
Original Message:
Sent: Jan 20, 2026 01:31 PM
From: Te10
Subject: DHCP POOLs
Hi
1st actually I have network from core and access switches
in core i configured the management interface vlan and also client interface vlan with dhcp configured in the core too
in access switch i configured the management interface vlan and only the client vlan with default route to core through management vlan so there reachability to client interface vlan which is in core but still clients are not taking ip
Original Message:
Sent: Jan 19, 2026 12:45 AM
From: shpat
Subject: DHCP POOLs
Hi Te10,
1) A small syntax mistake on your config, but the rest is ok
dhcp-server vrf default
pool VLAN30-POOL
range 10.30.30.50 10.30.30.150
lease 12:00:00
domain-name example.org.in
default-router 10.30.30.1
dns-server 125.0.0.1 125.0.0.2
enable
2) Yes this is mandatory. Without an SVI, DHCP will not work.
You should have something like:
interface vlan 30
ip address 10.30.30.1/24
no shutdown
You sould need an ip helper-address only if dhcp server is external or dhcp server is in another VLAN or VRF
3) Yes the gateway MAC address can be the same across all VLAN SVIs.
------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
Original Message:
Sent: Jan 18, 2026 11:02 AM
From: Te10
Subject: DHCP POOLs
Hi
I am working for aruba cx network implementation and i have to create dhcp pools in the core swtch so I have 3 questions
1st wnats to confirm that conigurations are right
dhcp-server vrf name
pool VLAN30-POOL
range 10.30.30.50 10.30.30.150
lease 12:00:00
domain-name example.org.in
default-router ip 10.30.30.1
dns-server 125.0.0.1 125.0.0.2
enable
2nd do I have to configure any command in interface vlan related to dhcp
3rd I have confusion regarding ip gateway mac in the interface vlan can be the same in all interface vlans and if so what is the best practice should be different or same
Thanks in advance
-------------------------------------------