11-13-2008 09:11 AM - edited 07-03-2021 04:46 PM
I have a network of multiple WiSM' in different locations. Each has the same SSID's configured. They are all in the same mobility domain. They can all see each other when I look under mobility groups.
The problem I am having is that my guest SSID allows people to connect but are not getting a DHCP address. I verified the DHCP server is working with plenty of leases available. If I hard code the IP address on a laptop I still cannot get out. It appears that I am not getting from one remote WiSM thru to the main WiSM and out to the internet. This was up and running but stopped.
Seth
11-13-2008 12:54 PM
I'm guessing one of Wism is Achoring the Guest traffic, you will need to make sure both WLANs configured the same, to ensure both the data and control paths are up.
11-13-2008 12:58 PM
That is correct and all paths are up. The mobility group shows up and I verified that the mobility group name is correct on each WiSM, the WLAN ssid is exactly the same and the Virtual IP address is 1.1.1.1 on all WiSM.
We will reboot the WiSM tonight at midnight to see if that clears it up.
All the users who associate to the host WiSM direct work fine. User at the other WiSM's do not.
Seth
11-13-2008 01:21 PM
Lets hope that does the job keep us informed.
Good luck
11-18-2008 11:46 AM
Ok, got to reboot all the WiSM's and still cannot get this WLAN to work.
Any suggestions?
Seth
11-18-2008 12:16 PM
Out of curiousity are all the controllers running the same software version?
11-18-2008 12:17 PM
yes, all are running the exact same version.
11-21-2008 06:19 AM
Just an update, I did both and MPING and an EPING from the WiSM and both work.
Any suggestions as to why I still cannot get this guest WLAN working?
Seth
11-21-2008 06:34 AM
Is the DNS address reachable from all controllers?
11-21-2008 06:37 AM
That I will have to verify. Does DNS even come into play in this as each WiSM knows about the others because they have been configured in each WiSM.
Seth
11-23-2008 08:45 AM
Can u run the following debugs
1. Debug Client
2. Debug DHCP ...
and check what is happening
Thanks
Vinay
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