Site 1 has been up for a little over a year with no problems until recently, the issue is when the system gets rebooted. After a reboot only about 1 to 3 of the CPE’s will re-associate. If I go disable the card and re-enable it, I may get 1-3 different or some of the same CPE’s to reconnect. I have to proceed to disable/enable the card over and over from 70-150 times until finaly all of the CPE’s will all associate then everything works like normal.
Site 2 is a replacement unit for an existing system that was in place that I am replacing with the setup from above. As soon as I replaced the old unit with this new one and booted up the new one, I get the exact same issue as Site 1 where I have to disable/enable the card until it finally associates everyone.
I noticed a few threads on the forum about people having to disable/enable their wireless interfaces to get everyone re-associated but I haven’t seen a resolution. I left a message for Ubiquiti to call me back and also emailed them so we will see where that gets us.
Anyone have any idea’s what might be going on here?
Mixture of Tranzeo CPE-200 and CPQ’s. If I log into the CPE via local ethernet, it sometimes shows the AP in the AP list and sometimes it doesn’t during the process of trying to get the devices connected. When it shows up, I can click on it to tell it to connect but it still won’t associate. But once I do the disable/enable trick long enough, it will connect and then I can reboot the CPE as much as I want and it will reconnect everytime.
I received a response back from Ubiquiti stating they have not heard of any issues like this related to the SR2. I guess I need to try swapping the cards out with a CM9 or R52. Any other suggestions?
I am running an RB532, with an SR2. The backhaul is the Ether1, connected directly to the network switch in the equipment shelter.
When I do something to promp the A.P. to ask the clients to re-register, they usually don’t unless I toggle something else, like the bridge, etc.
Sometimes when in the fugue state, I only see one to three clients registering. Why does this happen? MikroTik support can’t seem to figure out what I am talking about here.
I assume you are using POE? If so, are you running 48v? I wonder if it is power related, I have thought about switching out the power supplies to see if that makes a difference.
I replaced the unit at one of my sites with the same setup except I used an XR2 instead of SR2 and I am still having the same assocation issue, i have to change frequencies and enable/disable the card until the CPE’s finally start associating. I am beginning to wonder if it is related to the CPE. I am using Tranzeo TR-CPE200s. The only other thing I could think of would be my wireless config which I will post below.
How many Tranzeo CPE-200’s and CPQ’s do you have at each site?
I seem to remember a lot of people having problem’s with Prizm clients connecting to Atheros AP’s when they first came out. Maybe this is just the same old problem.
One way to know for sure is to put a prizm card in the AP. Or you could move all the CPQ’s to one AP and all the 200’s to the other and put in a Prizm card in the AP for the prizm clients and a Atheros card for the Atheros clients.
Anyway, I have always found it’s better to keep the chipset as close as possible on the AP’s and clients.
I too am having this problem. Using routerboard 532 and SR2. Setup as AP Bridge. Have to disable and enable. CPEs are a mix of CB3s, Smartbridges and Zinwell boards. I did notice that if you let it sit for a while groups of the CPEs will associate. Like 5 first then 10 more 15 minutes later. Diffferent groups associate at different times, but the qroups aren’t the same everytime.
Worked on it some more last night while everbody was hopefully sleeping. Tried every different config on the AP with no luck. Sometimes most of the CPEs asscociated and other time 1 or 2. There is about 25 total.
Sometimes when I made a change to the wireless card like channel, the card doesn’t even start running. I had to enable/disable the card to get it running again.
I did notice that the CPEs seemed to associate better when the SSID wasn’t hidden. Maybe just a coincidence though.
I have another exact setup that does the same thing but not as bad. I make a change to it, then disable/enable card and all CPEs come back. It has more clients than the other one.
I am starting to see a pattern, I first posted this http://forum.mikrotik.com/t/rouge-cpe-kill-alls-cleints/13111/1 and thought it was a single user to start, then I figured it was mixing the Atheros chipset and the prism.. Now I am see it even more clearly
Basically I am seeing the problem spread over my 27 node network like a disease. It happened on my most popular nodes first, and then has been affecting the other nodes as well, and the same fix works on all node.
to fix you do one of 2 things
disable…enable.. a 1000 times till you see everyone get on.
stick in a prism chip set, everyone connects but then they complain about speed and other things, things that are solved by switching to the atheros.
Now I have a theory, I believe it is the RB113 board out there. When I get a call that no one can connect on a node that has not had the problem, I notice that there has been an 133 user added. the node in question was working perfectly with 32 people on it, now 2we added 2 133 mikrotik clients, and BAM, that node is now having the same problem.
I am in the process of adding a new card to the AP, and moving all the atheros cards to it, I have done that to 1 node, and as soon as I moved the RB133 clients to the new card, everything went back to normal
I need people to chime in here and let us know if you have this problem, and if you are using RB133s in the field.
NOTE: I love the RB133 as a client, I have solved many issues by having the ability to login to peoples’ CPEs and do diagnostics, now if we could beat this latest issue we will be in Mikrotik Heaven.
Funny you suggest that; I am about to roll out my first Rb133C client on Monday.
All of my clients are Engenius radios presently.
When you program your RB133C, do you do this via the serial cable, or by using the Winbox? When I set-up my Rb133C units to talk via serial cable, the computer freezes and the Rb133 seems to stop responding.
Don’t have that problem when talking to the RB 532, though. Not sure why it is prevelant to the RB133C.
I use winbox and connect via the MAC address to configure. I wonder if this problem is occurring from bug in the OS.. what versions are people running? All my problem nodes are 2.9.38 or newer.
I need to get the RB133 running for Monday’s install. It should be the first one I have out in the field for the clients. - Wish me luck!!
I will connect to it using WinBox and see how it goes. I am trying to get some more compatibility out of the system, and I think that if I use the RB532 and RB133C, this would be best.