topic Re: Clients on ports getting their VLANs via Policy not getting a DHCP address in ExtremeSwitching (EXOS/Switch Engine)

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

Michael_P — Fri, 12 Jul 2019 04:27:00 GMT

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.

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

Matthew_Hum — Sat, 13 Jul 2019 10:48:21 GMT

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?

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

Michael_P — Mon, 15 Jul 2019 20:02:27 GMT

Matthew,
Not blocking anything with Policy. I do not use a policy on the X620 at the core - just the X440s on the edge.

configure policy profile 1 name "UPS" pvid-status "enable" pvid 4095
configure policy profile 2 name "CleartouchWindows" pvid-status "enable" pvid 4095
configure policy profile 3 name "V23Clients" pvid-status "enable" pvid 4095
configure policy profile 4 name "Phones" pvid-status "enable" pvid 4095 cos-status "enable" cos 6 egress-vlans 30
configure policy profile 5 name "V22Clients" pvid-status "enable" pvid 4095
configure policy profile 6 name "V21Clients" pvid-status "enable" pvid 4095
configure policy profile 7 name "Printer" pvid-status "enable" pvid 4095
configure policy profile 8 name "DLE-Default" pvid-status "enable" pvid 4095
configure policy profile 9 name "SecurityCameras" pvid-status "enable" pvid 4095
configure policy profile 10 name "Wireless AP" pvid-status "enable" pvid 4095 egress-vlans 60,70
configure policy profile 11 name "Phone Switches" pvid-status "enable" pvid 4095
configure policy profile 12 name "Safari" pvid-status "enable" pvid 4095
configure policy vlanauthorization enable
enable policy

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

Matthew_Hum — Fri, 19 Jul 2019 08:55:19 GMT

Is the server seeing the DHCP requests?
I'm assuming you're bridging at the AP. is the AP and phones sending the correct tags to the switch?

code:

configure policy profile 4 name "Phones" pvid-status "enable" pvid 30 cos-status "enable" cos 6 egress-vlans 30

try this for the phones and see if it still has problems.

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

Michael_P — Wed, 24 Jul 2019 04:13:44 GMT

This is for wired ports. DHCP is not making it to the server when the untagged vlan is dynamically assigned, but is making it to the server when the untagged vlan is statically assigned.

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

Michael_P — Wed, 24 Jul 2019 05:30:26 GMT

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.