cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
659
Views
0
Helpful
4
Replies

guest anchor local dhcp is not working

raymond wang
Level 1
Level 1

                   The client can assiciate with internal wlc. Internal wlc has tunnel up with guest controller, but the client can not get the ip from guest controller which has local scope dhcp configured

any idea?

Thanks

Ray

2 Accepted Solutions

Accepted Solutions

Sandeep Choudhary
VIP Alumni
VIP Alumni

Can u paste the output of the command:

debug client

Please also check:

1. Interoperability issues can exist between a controller with DHCP proxy enabled and devices acting as both a firewall and DHCP server. This is most likely due to the firewall component of the device as firewalls generally do not respond to proxy requests. The workaround for this issue is to disable DHCP proxy on the controller.

2. When a client is in DHCP REQ state on the controller, the controller drops DHCP inform packets. The client will not go into a RUN state on the controller (this is required for the client to pass traffic) until it receives a DHCP discover packet from the client. DHCP inform packets are forwarded by the controller when DHCP proxy is disabled.

3. All controllers that will communicate must have the same DHCP proxy setting.

Regards

View solution in original post

DHCP proxy is required when using the WLC as a dhcp server.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

View solution in original post

4 Replies 4

raymond wang
Level 1
Level 1

should I enable dhcp proxy under controller-advance? I also confused with dhcp proxy mode global or enable under interface configuration

DHCP proxy is required when using the WLC as a dhcp server.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

Sandeep Choudhary
VIP Alumni
VIP Alumni

Can u paste the output of the command:

debug client

Please also check:

1. Interoperability issues can exist between a controller with DHCP proxy enabled and devices acting as both a firewall and DHCP server. This is most likely due to the firewall component of the device as firewalls generally do not respond to proxy requests. The workaround for this issue is to disable DHCP proxy on the controller.

2. When a client is in DHCP REQ state on the controller, the controller drops DHCP inform packets. The client will not go into a RUN state on the controller (this is required for the client to pass traffic) until it receives a DHCP discover packet from the client. DHCP inform packets are forwarded by the controller when DHCP proxy is disabled.

3. All controllers that will communicate must have the same DHCP proxy setting.

Regards

Thanks All for the reply. As Scot mentioned, I need to enable dhcp proxy on the guest controller...

Cheers.

Review Cisco Networking products for a $25 gift card