cancel
Showing results for 
Search instead for 
Did you mean: 

Users unable to get IP address after several months running normally!

flavio_borup
New Contributor III
My ZD is 9.9.0.0 build 216 and i can ́t do any change right now
I have several old APs which doesn ́t allow me to upgrade

I ́m running this very same solution in the last 3 years with no problems at all

Yesterday, some users complain about the were unable to get IP addresses

My DHCP Server is a Windows 2012
My Ruckus environment have 12 APs and several SSIDs and Serveral VLANs
My network uses HP/3COM Switchs models 2600, 5550, etc


After doing a investigation:

The problem only affected a single SSID and is related to a single VLAN
At DHCP Server logs, i can see SOME clients are still able to get IPs, but randomly, some users can ́t. After some network tracing, i can see DHCP requests arriving at DHCP Server and all requests that come to DHCP are served with no problem. 

But the clients with problems, the DHCP request does not arrive at the interface, for some reason, the traffic was blocked at some point and the DHCP packets were not arriving at the DHCP Server.. Again, for some clients, other can connect with no problem.

Yesterday, afet several months of uptime i rebooted my ZD and all things got normal again. Ok, maybe it was a "glitch", anyway, after the reboot.. everyting got back normal

Today, the problem is back! After some tests i did the following: I changed the VLAN ID of the SSID and clients were able to get IP address again (each VLAN has its own IP range), so, in the new range, things were nromal. And, after re-configuring back as before, the problem was gone. First a reboot, now a little change in configuration to solve the problem. Weird!

Some monutes ago, the problem is back again! and i didnpt reboot yet, but now, no matter what change i do, the problem is here, some clients can leas IPs and some not (randomly) and if the pacjets arrive at DHCP Server they ́re leased with no problem, but some packets simply didn ́t arrive at the DHCP Server interface to be processed

So, what ́s next? What should I do?
28 REPLIES 28

andrew_giancol1
Contributor III
Try hitting `set cap` then use tab to complete.

flavio_borup
New Contributor III
ok, now i got, wlan100 for 2.4 GHz radio, i ́m testing WS remote capture, and i can see a lot of "sub interfaces" available

flavio_borup
New Contributor III
now, after selecting the wlan40 (my case)

---------------------------

---------------------------
The capture session could not be initiated on interface 'rpcap://[10.121.60.59]:2002/wlan40' (Unknown error (pcap bug; actual error cause not reported)).
---------------------------



Please check that "rpcap://[10.121.60.59]:2002/wlan40" is the proper interface.


Help can be found at:

       https://wiki.wireshark.org/WinPcap
       https://wiki.wireshark.org/CaptureSetup

---------------------------
OK   
---------------------------

flavio_borup
New Contributor III
---------------------------

---------------------------
The capture session could not be initiated on interface 'rpcap://[10.121.60.59]:2002/eth2' (Unknown error (pcap bug; actual error cause not reported)).
---------------------------



Please check that "rpcap://[10.121.60.59]:2002/eth2" is the proper interface.


Help can be found at:

       https://wiki.wireshark.org/WinPcap
       https://wiki.wireshark.org/CaptureSetup

---------------------------
OK   
---------------------------

andrew_giancol1
Contributor III
can you attach a screen shot? of your remote session failing?