Wireless Access

Reply
Regular Contributor II
Posts: 219
Registered: ‎10-09-2009

DHCP issue - clients connect sometimes

The DHCP server is leasing IP addresses. Some devices will get an IP the first and after the client is shutdown or rebooted, they cannont get an IP again. Other clients connect fine but if they go to a screensaver or sleep  mode, they have to connect to another network then back to the network they need to be on. Lastly some just don't get an IP at all. I turned on debugging on the controller and I see the IP the client would get but the client never gets it.

Aruba
Posts: 1,644
Registered: ‎04-13-2009

Re: DHCP issue - clients connect sometimes

It sounds as though the client cannot obtain/renew an IP if it is in the client table and already assigned a role; but if they connect to another network and back again, they are able to (coming in anew).

 

Please share the output of the following for the role the clients are in when they cannot renew/obtain an IP.

show rights <nameofrole>

 

 

------------------------------------------------
Systems Engineer, Northeast USA
ACCX | ACDX | ACMX

Regular Contributor II
Posts: 219
Registered: ‎10-09-2009

Re: DHCP issue - clients connect sometimes

(ARUBA_CTR_LOCAL) #show rights xxxx-hosp-pol

Derived Role = 'xxxx-hosp-pol'
 Up BW:No Limit   Down BW:No Limit
 L2TP Pool = default-l2tp-pool
 PPTP Pool = default-pptp-pool
 Assigned VLAN = 104
 Periodic reauthentication: Disabled
 ACL Number = 69/0
 Max Sessions = 65535


access-list List
----------------
Position  Name      Location
--------  ----      --------
1         allowall
2         qakbot

allowall
--------
Priority  Source  Destination  Service  Action  TimeRange  Log  Expired  Queue  TOS  8021P  Blacklist  Mirror  DisScan  ClassifyMedia  IPv4/6
--------  ------  -----------  -------  ------  ---------  ---  -------  -----  ---  -----  ---------  ------  -------  -------------  ------
1         any     any          any      permit                           Low                                                           4
qakbot
------
Priority  Source  Destination  Service    Action  TimeRange  Log  Expired  Queue  TOS  8021P  Blacklist  Mirror  DisScan  ClassifyMedia  IPv4/6
--------  ------  -----------  -------    ------  ---------  ---  -------  -----  ---  -----  ---------  ------  -------  -------------  ------
1         any     any          udp 16666  deny                             Low                                                           4
2         any     any          udp 16669  deny                             Low                                                           4
3         any     any          tcp 16666  deny                             Low                                                           4
4         any     any          tcp 16669  deny                             Low                                                           4

Expired Policies (due to time constraints) = 0

 

Aruba
Posts: 1,644
Registered: ‎04-13-2009

Re: DHCP issue - clients connect sometimes

I know you said you turned on debugging, but did you turn on DHCP debugging?  Try the following:

 

logging level debugging network subcat dhcp

attempt to reconnect and obtain IP

show log network | all include <MAC>

 

Run the same test getting a successful IP; so switching networks for example.

 

when you are done, disable it:

no logging level debugging network subcat dhcp

------------------------------------------------
Systems Engineer, Northeast USA
ACCX | ACDX | ACMX

Regular Contributor II
Posts: 219
Registered: ‎10-09-2009

Re: DHCP issue - clients connect sometimes

I ran it but showed nothing. I added logging level debugging network process dhcpd.

 

Succesful IP:

(ARUBA_CTR_LOCAL) (config) #show log network all | include 00:21:5d:8b:98:68
Feb 7 09:01:52 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x40 opcode 0x5a ingress 0x1612 vlan 104 egress 0x0 src mac 00:21:5d:8b:98:68
Feb 7 09:01:52 :202538:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: RELEASE 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:02:18 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x119a vlan 104 egress 0x68 src mac 00:21:5d:8b:98:68
Feb 7 09:02:18 :202534:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: DISCOVER 00:21:5d:8b:98:68 Options 74:01 3d:0100215d8b9868 0c:4169724d61676e6574 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc00
Feb 7 09:02:18 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=00:21:5d:8b:98:68
Feb 7 09:02:18 :202534:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: DISCOVER 00:21:5d:8b:98:68 Options 74:01 3d:0100215d8b9868 0c:4169724d61676e6574 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc00
Feb 7 09:02:18 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: OFFER 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:02:18 :202527:  <DBUG> |dhcpdwrap| |dhcp| RelayToClient: OFFER dest=172.20.104.5 client yiaddr=172.20.104.5 MAC=00:21:5d:8b:98:68
Feb 7 09:02:18 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: OFFER 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:02:18 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x119a vlan 104 egress 0x68 src mac 00:21:5d:8b:98:68
Feb 7 09:02:18 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: REQUEST 00:21:5d:8b:98:68 reqIP=172.20.104.5 Options 3d:0100215d8b9868 36:ac1092a6 0c:4169724d61676e6574 51:0000004169724d61676e65742e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc0100
Feb 7 09:02:18 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=00:21:5d:8b:98:68
Feb 7 09:02:18 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: REQUEST 00:21:5d:8b:98:68 reqIP=172.20.104.5 Options 3d:0100215d8b9868 36:ac1092a6 0c:4169724d61676e6574 51:0000004169724d61676e65742e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc0100
Feb 7 09:02:18 :202544:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: ACK 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:02:18 :202527:  <DBUG> |dhcpdwrap| |dhcp| RelayToClient: OFFER dest=172.20.104.5 client yiaddr=172.20.104.5 MAC=00:21:5d:8b:98:68
Feb 7 09:02:18 :202086:  <INFO> |dhcpdwrap|  netlink_arp_changed(): ker_mac 00:21:5d:8b:98:68 pkt_mac 00:21:5d:8b:98:68 cip 172.20.104.5
Feb 7 09:02:18 :202544:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: ACK 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:03:39 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x40 opcode 0x5a ingress 0x119a vlan 104 egress 0x0 src mac 00:21:5d:8b:98:68
Feb 7 09:03:39 :202538:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: RELEASE 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:04:13 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x1612 vlan 104 egress 0x68 src mac 00:21:5d:8b:98:68
Feb 7 09:04:13 :202534:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: DISCOVER 00:21:5d:8b:98:68 Options 74:01 3d:0100215d8b9868 0c:4169724d61676e6574 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc00
Feb 7 09:04:13 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=00:21:5d:8b:98:68
Feb 7 09:04:13 :202534:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: DISCOVER 00:21:5d:8b:98:68 Options 74:01 3d:0100215d8b9868 0c:4169724d61676e6574 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc00
Feb 7 09:04:13 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: OFFER 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:04:13 :202527:  <DBUG> |dhcpdwrap| |dhcp| RelayToClient: OFFER dest=172.20.104.5 client yiaddr=172.20.104.5 MAC=00:21:5d:8b:98:68
Feb 7 09:04:13 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: OFFER 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:04:13 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x1612 vlan 104 egress 0x68 src mac 00:21:5d:8b:98:68
Feb 7 09:04:13 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: REQUEST 00:21:5d:8b:98:68 reqIP=172.20.104.5 Options 3d:0100215d8b9868 36:ac1092a6 0c:4169724d61676e6574 51:0000004169724d61676e65742e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc0100
Feb 7 09:04:13 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=00:21:5d:8b:98:68
Feb 7 09:04:13 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: REQUEST 00:21:5d:8b:98:68 reqIP=172.20.104.5 Options 3d:0100215d8b9868 36:ac1092a6 0c:4169724d61676e6574 51:0000004169724d61676e65742e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f21f92b 2b:dc0100
Feb 7 09:04:13 :202544:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: ACK 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:04:13 :202527:  <DBUG> |dhcpdwrap| |dhcp| RelayToClient: OFFER dest=172.20.104.5 client yiaddr=172.20.104.5 MAC=00:21:5d:8b:98:68
Feb 7 09:04:13 :202086:  <INFO> |dhcpdwrap|  netlink_arp_changed(): ker_mac 00:21:5d:8b:98:68 pkt_mac 00:21:5d:8b:98:68 cip 172.20.104.5
Feb 7 09:04:13 :202544:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: ACK 00:21:5d:8b:98:68 clientIP=172.20.104.5

 

 

Unsuccessful IP (gets Windows default IP when it cannot get IP (169.254.x.x)
(ARUBA_CTR_LOCAL) (config) #show log network all | include 84:3a:4b:88:33:60
Feb 7 09:06:04 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x119a vlan 104 egress 0x68 src mac 84:3a:4b:88:33:60
Feb 7 09:06:04 :202534:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: DISCOVER 84:3a:4b:88:33:60 Options 3d:01843a4b883360 0c:49532d572d3130 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:04 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=84:3a:4b:88:33:60
Feb 7 09:06:04 :202534:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: DISCOVER 84:3a:4b:88:33:60 Options 3d:01843a4b883360 0c:49532d572d3130 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:04 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: OFFER 84:3a:4b:88:33:60 clientIP=172.20.104.4
Feb 7 09:06:04 :202527:  <DBUG> |dhcpdwrap| |dhcp| RelayToClient: OFFER dest=172.20.104.4 client yiaddr=172.20.104.4 MAC=84:3a:4b:88:33:60
Feb 7 09:06:04 :202546:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: OFFER 84:3a:4b:88:33:60 clientIP=172.20.104.4
Feb 7 09:06:04 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x119a vlan 104 egress 0x68 src mac 84:3a:4b:88:33:60
Feb 7 09:06:04 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: REQUEST 84:3a:4b:88:33:60 reqIP=172.20.104.4 Options 3d:01843a4b883360 36:ac1092a6 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:04 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=84:3a:4b:88:33:60
Feb 7 09:06:04 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: REQUEST 84:3a:4b:88:33:60 reqIP=172.20.104.4 Options 3d:01843a4b883360 36:ac1092a6 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:07 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x119a vlan 104 egress 0x68 src mac 84:3a:4b:88:33:60
Feb 7 09:06:07 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: REQUEST 84:3a:4b:88:33:60 reqIP=172.20.104.4 Options 3d:01843a4b883360 36:ac1092a6 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:07 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=84:3a:4b:88:33:60
Feb 7 09:06:07 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: REQUEST 84:3a:4b:88:33:60 reqIP=172.20.104.4 Options 3d:01843a4b883360 36:ac1092a6 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:15 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x119a vlan 104 egress 0x68 src mac 84:3a:4b:88:33:60
Feb 7 09:06:15 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: REQUEST 84:3a:4b:88:33:60 reqIP=172.20.104.4 Options 3d:01843a4b883360 36:ac1092a6 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:15 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=84:3a:4b:88:33:60
Feb 7 09:06:15 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: REQUEST 84:3a:4b:88:33:60 reqIP=172.20.104.4 Options 3d:01843a4b883360 36:ac1092a6 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:57 :202541:  <DBUG> |dhcpdwrap| |dhcp| Received DHCP packet from Datpath, sos msg hdr flags 0x41 opcode 0x5a ingress 0x1612 vlan 104 egress 0x68 src mac 84:3a:4b:88:33:60
Feb 7 09:06:57 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: REQUEST 84:3a:4b:88:33:60 reqIP=192.168.1.63 Options 3d:01843a4b883360 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b
Feb 7 09:06:57 :202533:  <DBUG> |dhcpdwrap| |dhcp| Relayed: DISCOVER server=172.16.146.166 giaddr=172.20.104.1 MAC=84:3a:4b:88:33:60
Feb 7 09:06:57 :202536:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: REQUEST 84:3a:4b:88:33:60 reqIP=192.168.1.63 Options 3d:01843a4b883360 0c:49532d572d3130 51:00000049532d572d31302e6d696c7265672e6f7267 3c:4d53465420352e30 37:010f03062c2e2f1f2179f92b

 

 

 

Aruba
Posts: 1,644
Registered: ‎04-13-2009

Re: DHCP issue - clients connect sometimes

[ Edited ]

What VLAN should the client be on; 1 or 104?  I see requests for both.  

 

Feb 7 09:04:13 :202544:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan1: ACK 00:21:5d:8b:98:68 clientIP=172.20.104.5
Feb 7 09:04:13 :202527:  <DBUG> |dhcpdwrap| |dhcp| RelayToClient: OFFER dest=172.20.104.5 client yiaddr=172.20.104.5 MAC=00:21:5d:8b:98:68
Feb 7 09:04:13 :202086:  <INFO> |dhcpdwrap|  netlink_arp_changed(): ker_mac 00:21:5d:8b:98:68 pkt_mac 00:21:5d:8b:98:68 cip 172.20.104.5
Feb 7 09:04:13 :202544:  <DBUG> |dhcpdwrap| |dhcp| Datapath vlan104: ACK 00:21:5d:8b:98:68 clientIP=172.20.104.5

------------------------------------------------
Systems Engineer, Northeast USA
ACCX | ACDX | ACMX

Regular Contributor II
Posts: 219
Registered: ‎10-09-2009

Re: DHCP issue - clients connect sometimes

The gateway resides on the controller is on VLAN 1 and is the gateway. The clients go to a DHCP server which assigns a VLAN 104.

Aruba
Posts: 1,644
Registered: ‎04-13-2009

Re: DHCP issue - clients connect sometimes

OK; maybe I am confusing your setup.    I am wondering why it appears the client is asking for an IP on VLAN 1 at times.   I see that you have VLAN 104 tied to the role; what is the default VLAN for the Virtual AP?  Also, what type of authentication is used on the network?

 

 

 

 

------------------------------------------------
Systems Engineer, Northeast USA
ACCX | ACDX | ACMX

Regular Contributor II
Posts: 219
Registered: ‎10-09-2009

Re: DHCP issue - clients connect sometimes

Does it matter that I have an IP address helper on ther controller?  Or should it be on the core switch?

 

The controller is VLAN 1, which is the gateway for all wireless clients. Each SSID in the Virtual AP has a VLAN (20, 104 and 108). The APs uses VLAN 47. The DHCP server is on VLAN 146. The IP address helper address is the IP of the DHCP server.

 

I am puzzled becauseI have a test client is connected fine all day but when I come in the next morning, it has limited access. I connect to another network and back and it is fine.

Search Airheads
Showing results for 
Search instead for 
Did you mean: