10-19-2011 01:35 PM - edited 07-03-2021 08:57 PM
Hi all,
I'm hoping somebody can lend some insight, primarily regarding the WET200.
We have a WLC5508, with 3 1242AG access points. When a PC connects to these access points, and does a DHCP release and renew wothout issue, and lists the DHCP server address as 1.1.1.1, as expected. (it proxies over to our windows DHCP server on the managment interface of the WLC)
However, we have multiple WET200 bridges in the area. Each bridge is set to a static IP address, and it has 3 devices connected through the ethernet ports. 2 of the devices are static addresses, and communicate properly. the third device is a workstation, set to DHCP, and it will not gain an address.
We have attempted setting the Bridge itself to DHCP, and it does not get an address. I'm stumped on this one, as client workstaions, not going through the bridge, get DHCP via the controller just fine, but the briges will not. Making it even weirder, is that if the bridges are taken into an area with autonomous access points, not on the controller, the workstaions connected to the bridges pick up DHCP just fine.
Thus, I'm thinking it has to be a setting on the WLC, as the bridges themselves really don't have much in the way of settings for DHCP.
The WLC is version 7.0.116.0.
Thanks in advance for any assistance.
10-21-2011 10:13 AM
OK, I need to expand on this a little:
We've noticed another anomaly. When we boot up the bridges, the bridge's IP, and all devices connected to it will respond to pings for about 5 minutes. Afterwards, random devices connected to the bridge, or the bridge itself, stop responding to pings, and may randomly begin responding again. It's not all devices at once that stop responding. Sometimes, the workstaion will time out, but other devices will respond fine, other times, 2 of 4 devices will timeout. It's just odd behavior.
What's weird though is that all devices remain connected back to the server they are talking to, and they are still fully functional. They simply don't respond to IP pings. I suspect this may have something to do with the ip-mac-binding, which I have disabled on the controller, but looking into the settings, it seems that this can only be enabled or disabled. All of the devices need to be able to talk on the WAN for the whole unit to perform it's job, and it's still able to do so.
Does anyone have any experience with a wet200 when conected to a WLC5508?
10-22-2011 06:21 AM
Michael,
EXACT same problem as you. See : https://supportforums.cisco.com/thread/2031997
Apparently It's a limitation on the WET200 as the WLC does not see it as a workgroup bridge.
I have the exact hardware and firmware as yourself.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide