cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

Clients on ports getting their VLANs via Policy not getting a DHCP address

Clients on ports getting their VLANs via Policy not getting a DHCP address

Michael_P
New Contributor II
I have an X620 setup as a core to a LAN with X440-G2 switches on the edge. I have policy working at the switches - for example: when a IP Camera is plugged in, policy assigns VLAN 13 untagged to the port, When an AP is plugged in, policy assigns VLAN 80 untagged and 60 & 70 tagged, etc. That part is working.

The cameras are setup with static IP addresses and are reachable, but the APs (and other DHCP enabled devices) get the port configured correctly according to policy, but do not get DHCP addresses.

For ports that have static VLANs assigned - DHCP is working fine.

On a similar note: DHCP relay is working fine (except as listed above) but PXE booting is not working on any port static or dynamic. I figured I would mention this in case these issues are related.
1 ACCEPTED SOLUTION

Michael_P
New Contributor II
I think this may be solved. In the policy, under "Default Actions" I changed "Permit Traffic" to "Contain to VLAN" and set the "Contain to VLAN" to the proper VLAN (100 in this example). The client received a DHCP address and I was able to get connected to the LAN and Internet.

1390c7486eca4a50a30b92bb66ddd6fd_594b70fc-1c03-4f8d-b0d7-fc6a93bb0892.jpg

View solution in original post

5 REPLIES 5

Matthew_Hum
Contributor
Hi. There are a few things here.
Can you post the policy config that is pushed to the switches?
At the DHCP server do you see requests? that will help identify if the problem with policy is on ingress of the DHCP request or egressing the DHCP reply.
DHCP does in fact use the BootP protocol, so I'm not sure why your PXE is not working while DHCP does work. Are you blocking something else with policy?
GTM-P2G8KFN