At this point you dont know if.... 1) It was client traffic/usage or traffic type causing the problem. (streaming, DDOS, MAC level virus, etc)
2) Client Interference causing the problem. (For example hidden node) 3) Actually failing client hardware. 4) a Poor quality link, attempting to pass excessive traffic. 5) a software timing issue, or software config issue. (Is it running 802.11, or NStreme polling? A or N? Is there anything unique about this CPE set up? Improper bridging config? IP conflict?Enryption or not? ) I would start out by testing the problem link individually, to determine if the individual link performs OK. (That could require taking off other subs, which is not easy.) Maybe even ask the customer to unplug his Soho router or PC from the Outdoor radio's POE, so CPE radio is isolated from LAN traffic, and see if it causes any problems associated without customer's traffic. Then you can slow load up his CPE, to see at what points the sector starts to have issues. Does the trouble CPE have a lower RSSI ? Could it be being effected by interference sooner, because of link strength? You are looking for whether this radio is sending an excessive amount of TX retries, monopolizing AP's time, starving the other CPEs? or if its interference, and all CPE start having retries, when the trouble CPE is added back. Tom DeReggi RapidDSL & Wireless, Inc IntAirNet- Fixed Wireless Broadband ----- Original Message ----- From: "Scott Reed" <sr...@nwwnet.net> To: "WISPA General List" <wireless@wispa.org> Sent: Thursday, October 06, 2011 8:52 PM Subject: [WISPA] Pulling my hair out > Earlier this week one of the APs running 900MHz with SR9 in RB433s with > RB133 and RB411 clients started dropping clients and they would come > right back. I tried different frequencies, etc. Then it cleared up in > the morning. OK, maybe it is RTK or the weather or ... > Happened again the next night night. Replaced the AP electronics, > antenna and 65' of LMR400. Nothing I did seemed to make a bit of > difference. I did have a couple of clients that were actually off wrong > sector, behind this one. Changed them to the proper AP this morning. > 5:30 tonight 2 customers called within 2 minutes. Both off the AP in > question. I looked. None of the 14 clients would stay registered for > more than 10 seconds. Wildest registration table I have ever watched. > Nothing seemed to make a difference. I finally moved everyone to the > access list and disabled them. Enabled them one-by-one. Found tow that > would drop and come back and then apparently knock down everyone else. > Left them disabled and enabled all the others. Let it run that way 1 > hour with no drops. Enabled on of the 2 clients that was disabled. It > has now been up for over 52 minutes. > Turn on the last one and all goes out to lunch. Turn it off and > everything is OK. > Obviously that CPE has a problem. > Two reasons for the post: > 1) Clients can cause the whole AP to misbehave. > 2) Anyone have any trouble shooting tips on how to know whether to > check AP or clients first? > > -- > Scott Reed > Owner > NewWays Networking, LLC > Wireless Networking > Network Design, Installation and Administration > > > > Mikrotik Advanced Certified > > www.nwwnet.net > (765) 855-1060 > (765) 439-4253 > (855) 231-6239 > > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
