@pedro-tomo wrote:
Hi everyone, I have two radius servers connected to my L3 switch on the same vlan, each radius authenticates users mapped to two different vlans, one for vlan 100 and other for vlan 200. The clients connect to both vlans via WIFI(Meraki APs), the dhcp pool of vlan 200 is on L3 and for the vlan 100 is on the windows server. I'm having a problem with dhcp on vlan 100, I'm getting the following error on meraki dashboard: "client made a request to the dhcp server but the dhcp server rejected the client's request" and I think it has something to do with the radius configuration on the L3. Please find attached my configuration regarding the radius and tell me how to redirect radius1 and radius2 traffic to the correct ports.
aaa new-model
!
!
aaa authentication login default local line enable
aaa authentication dot1x default group radius
.
.
.
ip radius source-interface VlanX!
!
!
radius server RADIUS1
address ipv4 X.X.X.X auth-port 1812 acct-port 1813
key *******
!
radius server RADIUS2
address ipv4 X.X.X.X auth-port 1812 acct-port 1813
key *******
!
interface GigabitEthernet1/0/13
description to RADIUS1
switchport mode access
switchport access vlanX
interface GigabitEthernet1/0/14
description to RADIUS2
switchport mode access
switchport access vlanX
This suggests a misconfiguration between your RADIUS servers, VLAN assignments, and DHCP settings. First, ensure that your RADIUS servers are correctly configured to assign VLANs based on user authentication. This requires setting attributes like Tunnel-Type, Tunnel-Medium-Type, and Tunnel-Private-Group-ID to designate VLAN assignments properly. Additionally, verify that the switch ports connected to the Meraki APs are set to trunk mode, allowing multiple VLANs to pass through. This ensures that clients can be dynamically assigned to the correct VLAN.
Another crucial step is to confirm that the DHCP server for VLAN 100 is accessible and properly configured to distribute IP addresses to clients. Check for any IP conflicts or exhausted address pools, as these can prevent proper DHCP assignment. Additionally, review the VLAN tagging settings on your Meraki APs to ensure they align with your network’s VLAN assignments, as misconfigurations here can block clients from reaching the correct DHCP server. If conflict logging is enabled on your DHCP server, consider disabling it, as it can sometimes interfere with address assignment and lead to similar issues.
To resolve this problem, review and adjust the configurations mentioned above, and monitor the Meraki dashboard along with switch logs for any persistent errors.
