failed
asked on
Cisco WAP stops passing DHCP
Hello
I have 4 Cisco WAP551s at one of our sites, and I have discovered a problem whereby they stop distributing/passing through DHCP addresses to clients. This happens roughly every 2 days, at which point I simply reboot them all and magically the clients get addresses again and everything is OK for another couple of days.
I don't think it's the DHCP server (Win 2012 R2) since it still gives out addresses on wired clients when this problem occurs.
I have upgraded them all to the latest firmware and tried running them in a cluster (single point setup mode) and separately with the same SSID. Problem occurs in both modes.
If I give my wireless interface a static IP, I get full network access, so I don't think there's any routing/switch config issues.
Any ideas please? They're under warranty but I have no Cisco technical support contract. I could try get them all replaced but it seems unlikely to be a hardware fault with all 4.
I have 4 Cisco WAP551s at one of our sites, and I have discovered a problem whereby they stop distributing/passing through DHCP addresses to clients. This happens roughly every 2 days, at which point I simply reboot them all and magically the clients get addresses again and everything is OK for another couple of days.
I don't think it's the DHCP server (Win 2012 R2) since it still gives out addresses on wired clients when this problem occurs.
I have upgraded them all to the latest firmware and tried running them in a cluster (single point setup mode) and separately with the same SSID. Problem occurs in both modes.
If I give my wireless interface a static IP, I get full network access, so I don't think there's any routing/switch config issues.
Any ideas please? They're under warranty but I have no Cisco technical support contract. I could try get them all replaced but it seems unlikely to be a hardware fault with all 4.
You need to do a packet capture from the AP. This should show you whether the AP is passing DHCP requests either way.
The fact that wired clients receive addresses, and that it works after the AP is rebooted tells me that it's not a DHCP server issue, or a lease issue.
The fact that wired clients receive addresses, and that it works after the AP is rebooted tells me that it's not a DHCP server issue, or a lease issue.
ASKER
I've just jumped on the switch and noticed an active dhcp pool, so I guess that must be interfering! Not sure what it's doing there, it's certainly not required.
I've tried to remove it by issuing the no ip dhcp pool command, which ran without error, but the pool is still present when I show run? If I try issue the no ip dhcp command again it says the pool is not in the database??
Excerpt from running config:
no ip dhcp use vrf connected
!
ip dhcp pool guest-builds
default-router 192.168.69.254
!
When I try run the no ip dhcp pool command:
Switch1(config)#no ip dhcp pool guests-builds
% guests-builds is not in the database.
I've tried to remove it by issuing the no ip dhcp pool command, which ran without error, but the pool is still present when I show run? If I try issue the no ip dhcp command again it says the pool is not in the database??
Excerpt from running config:
no ip dhcp use vrf connected
!
ip dhcp pool guest-builds
default-router 192.168.69.254
!
When I try run the no ip dhcp pool command:
Switch1(config)#no ip dhcp pool guests-builds
% guests-builds is not in the database.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yep it was a simple typo, thanks for spotting that, I've removed the pool now!
I'll keep an eye on things now and see if I still get the same problem. If it's OK after a few days I'll come back and close the question.
I'll keep an eye on things now and see if I still get the same problem. If it's OK after a few days I'll come back and close the question.
Check the "Lease" times and settings on them and the DHCP Server.
Sounds like they might not be "renewing" properly, for one reason or another.
Mostly I'm thinking the AP's are holding the addys too long, and run out of numbers to hand out.
If a lot of people connect/disconnect all day long, the addy they get is reserved for the full Lease.
eg:
if most people only connect for 1 hour, and the Lease is for 1 day, that's 23 hours that that addy is unusable (except if the same computer connects again, and it's Lease is still good).