cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
621
Views
0
Helpful
2
Replies

Client cannot get IP from ex DHCP

fgao
Level 1
Level 1

I have a WLC5508 , we are using external DHCP for WLANs

one WLAN is able to get IP  from DHCP server but another WLAN not , the DHCP server is same , only 2 different scopes.

anyone know why ?                  

This is debug

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP received op BOOTREQUEST (1) (len 308,vlan 1, port 1, encap 0xec03)

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP processing DHCP DISCOVER (1)

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   xid: 0x2e3b1473 (775623795), secs: 8, flags: 0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   chaddr: e8:06:88:9b:a8:04

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP successfully bridged packet to DS

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP received op BOOTREQUEST (1) (len 308,vlan 1, port 1, encap 0xec03)

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP processing DHCP DISCOVER (1)

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   xid: 0x2e3b1473 (775623795), secs: 8, flags: 0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   chaddr: e8:06:88:9b:a8:04

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0

*DHCP Socket Task: Feb 05 21:26:43.106: e8:06:88:9b:a8:04 DHCP successfully bridged packet to DS

2 Replies 2

David Watkins
Level 4
Level 4

Looks like you have DHCP Proxy behavior disabled, so this is just briding to the respective network ("DHCP successfully bridged packet to DS")

Verify that you have an IP Helper address on the L3 gateway for this respective network.  If you do, start by simply taking a "wired" client and placing them in the same VLAN from the same switch as your WLC.  Verify whether or not the wired client can get an IP in this VLAN before focusing on the WLC.  It "looks" like this is bridging on to VLAN 1, so verify the WLAN is using the desired interface for the VLAN these clients should be on.

Thanks for your reply

(1) L3 gatewat is Firewall which is connect to ISP , The Firewall has DHCP reply configured for this subnet ,

(2) , Wired LAN Egress interface is same outlet as wireless , It cannot get IP from DHCP as well .

Really don't know why it just stop work now

Review Cisco Networking for a $25 gift card