Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2430
Views
0
Helpful
9
Replies

New SSID - client unable to get DHCP address

Go to solution
stephendrkw
Level 3
Level 3

‎03-25-2019 03:30 AM - edited ‎07-05-2021 10:07 AM

hi all, I have setup a new SSID for BYOD this SSID is configured to the use the same DHCP Servers as Guest SSID to test with ISE

 

I configured the WLAN exactly the same setup as Guest SSID to start with, same DHCP Server in Advanced options etc with same interface both on Foreign Controllers and Anchor controllers basically just a mimic for Guest but a new SSID for BYOD, the following is happening, I've gone back to the WLAN config and seems to match GUEST exactly.

 

Is there a problem with a new SSID using the same DHCP server as GUEST?

 

debug client

Foreign WLC

 

dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 10.66.108.3 VLAN: 201
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP selected relay 2 - 10.66.110.1 (local address 10.66.108.3, gateway 10.66.108.7, VLAN 201, port 13)
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 2
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP xid: 0x792be926 (2032920870), secs: 15, flags: 0
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP chaddr: ec:8c:9a:df:ce:55
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP siaddr: 0.0.0.0, giaddr: 10.66.108.3
*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP ARPing for 10.66.108.7 (SPA 10.66.108.3, vlanId 201)
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP received op BOOTREQUEST (1) (len 324,vlan 10, port 13, encap 0xec03)
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP (encap type 0xec03) mstype 0ff:ff:ff:ff:ff:ff
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 10.66.108.3 VLAN: 201
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP selected relay 1 - 10.66.110.2 (local address 10.66.108.3, gateway 10.66.108.7, VLAN 201, port 13)
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 10.66.108.3 VLAN: 201
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP selected relay 2 - 10.66.110.1 (local address 10.66.108.3, gateway 10.66.108.7, VLAN 201, port 13)
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 10.66.108.3 VLAN: 201
*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP selected relay 1 - 10.66.110.2 (local address 10.66.108.3, gateway 10.66.108.7, VLAN 201, port 13)
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP xid: 0x792be926 (2032920870), secs: 22, flags: 0
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP chaddr: ec:8c:9a:df:ce:55
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP siaddr: 0.0.0.0, giaddr: 10.66.108.3
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP ARPing for 10.66.108.7 (SPA 10.66.108.3, vlanId 201)
*DHCP Socket Task: Mar 25 09:54:14.803: ec:8c:9a:df:ce:55 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 10.66.108.3 VLAN: 201

 

debug client

Anchor WLC

 


*mmListen: Mar 25 09:36:09.417: Received mmIpAddrUpdateAck for client

*mmListen: Mar 25 09:37:36.814: Received mmIpAddrUpdateAck for client

*mmListen: Mar 25 09:37:59.524: Received mmIpAddrUpdateAck for client

*mmListen: Mar 25 09:38:24.230: Received mmIpAddrUpdateAck for client

*mmListen: Mar 25 09:41:25.868: Received mmIpAddrUpdateAck for client

*mmListen: Mar 25 09:44:36.971: Received mmIpAddrUpdateAck for client

*Dot1x_NW_MsgTask_5: Mar 25 09:53:13.469: ec:8c:9a:df:ce:55 Mobile Announce recvd from 10.136.4.54 Vlan List payload not found, ignoring ...

*Dot1x_NW_MsgTask_5: Mar 25 09:53:14.469: ec:8c:9a:df:ce:55 Mobile Announce recvd from 10.136.4.54 Vlan List payload not found, ignoring ...

*mmListen: Mar 25 09:54:07.280: Received mmIpAddrUpdateAck for client

*mmListen: Mar 25 10:08:50.861: Received mmIpAddrUpdateAck for client

*mmListen: Mar 25 10:14:14.586: Received mmIpAddrUpdateAck for client

 

 

 

 

 

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Ric Beeching
Level 7
Level 7
In response to stephendrkw

‎03-25-2019 06:10 PM

Hi Stephen,

Under Mobility Anchor lists for BYGSUK you haven't defined the anchors. Go to your WLAN page and on the right hand side select the blue arrow and then mobility anchors from drop down. In that section you need to apply the same two anchors as seen in the TGSLUK list:

Working:
Mobility Anchor List
WLAN ID IP Address Status
------- --------------- ------
5 10.66.110.1 Up
5 10.66.110.2 Up

Not working:
Mobility Anchor List
WLAN ID IP Address Status
------- --------------- ------

Cheers,
Ric
-----------------------------
Please rate helpful / correct posts

View solution in original post

0 Helpful
9 Replies 9

Go to solution
Ric Beeching
Level 7
Level 7

‎03-25-2019 06:10 AM - edited ‎03-25-2019 06:29 AM

Do you have DHCP Proxy configured on any of the WLCs? Have you got "DHCP override" set on the SSID? If so remove the override and let the WLCs handle it based on interface to see if that helps.

Can you do a "show wlan <#>" for each of the Guest and BYOD WLANs on the foreign WLC and attach?


Ric

-----------------------------
Please rate helpful / correct posts
0 Helpful

Go to solution
Ric Beeching
Level 7
Level 7
In response to Ric Beeching

‎03-25-2019 06:14 AM

Also are you running same software version on both anchor and foreign and what is it?
-----------------------------
Please rate helpful / correct posts
0 Helpful

Go to solution
stephendrkw
Level 3
Level 3
In response to Ric Beeching

‎03-25-2019 07:35 AM

8.0.140.0 on all WLC's
0 Helpful

Go to solution
Ric Beeching
Level 7
Level 7
In response to stephendrkw

‎03-25-2019 06:10 PM

Hi Stephen,

Under Mobility Anchor lists for BYGSUK you haven't defined the anchors. Go to your WLAN page and on the right hand side select the blue arrow and then mobility anchors from drop down. In that section you need to apply the same two anchors as seen in the TGSLUK list:

Working:
Mobility Anchor List
WLAN ID IP Address Status
------- --------------- ------
5 10.66.110.1 Up
5 10.66.110.2 Up

Not working:
Mobility Anchor List
WLAN ID IP Address Status
------- --------------- ------

Cheers,
Ric
-----------------------------
Please rate helpful / correct posts
0 Helpful

Go to solution
stephendrkw
Level 3
Level 3
In response to Ric Beeching

‎03-26-2019 02:40 AM

Thanks Ric, being about 2 years since I've created a new SSID as we pretty much stick with what we have until now! I can't believe I forgot about Mobility Anchor setup..........once applied worked straight away!

 

Steve

0 Helpful

Go to solution
Ric Beeching
Level 7
Level 7
In response to stephendrkw

‎03-26-2019 03:30 AM

Easy to do, glad its working!
-----------------------------
Please rate helpful / correct posts
0 Helpful

Go to solution
stephendrkw
Level 3
Level 3
In response to Ric Beeching

‎03-25-2019 07:34 AM - edited ‎03-25-2019 07:35 AM

Hi Ric,

 

Those settings are already have DHCP Proxy enabled and DHCP override disabled


find attached config for guest & byod from foreign wlc

 

Thanks,

Steve

Preview file
9 KB
Preview file
9 KB
0 Helpful

Go to solution
Jurgens L
Level 3
Level 3
In response to stephendrkw

‎03-25-2019 11:42 PM

Double check your mobility tunnel mapping for your BYOD SSID.

 

Under your Guest config your tunnels are mapped, for the output provided for the BYOD it's not the case.

 

To map it, at the WLAN page go to the far right of the page and scroll over the blue box a down arrow that align with your BYOD SSID, you will see the mobility anchor option which will allow you to add your anchors as you have for the Guest SSID.

 

 

<<< Please help the community by marking useful posts helpful, or accept as a solution if it resolved your issue >>>

0 Helpful

Go to solution
Leo Laohoo
Hall of Fame
Hall of Fame

‎03-25-2019 11:00 PM

@stephendrkw wrote:

*DHCP Socket Task: Mar 25 09:54:06.960: ec:8c:9a:df:ce:55 DHCP siaddr: 0.0.0.0, giaddr: 10.66.108.3

*DHCP Socket Task: Mar 25 09:54:14.802: ec:8c:9a:df:ce:55 DHCP selected relay 1 - 10.66.110.2 (local address 10.66.108.3, gateway 10.66.108.7, VLAN 201, port 13)

What is the DHCP server?  Windows-based or not?  

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card