18 replies
If these RF devices are able to step down their speed based on signal quality then they are running at a very low speed. Most likely though, there is interference that is effecting the signal quality causing either packet loss or retransmitted frames.
What types of devices? they should have counters that show these errors, as well as others.
HTH
by shanghai sam
by ebob
The next step I would have a look at is "traceroute" ("tracert" in Windoze-speak) to the device. This is just to confirm that the "problem" is with the last hop to/from the device.
Assuming that it is the last hop, then it suggests that there is some "error condition" over this hop. (OK, so that's not news...)
It could be some form of interference. This is likely related to the location of the RF device, in relation to the AP. Perhaps the problem device is located too close to a fluorescent light fixture (or there's one in the "path") or some other EMR source.
I would be tempted to simply try relocating the trouble device(s) to see how that affects your results. If the problem goes away, then the source is "environmental". If thetrouble stays, then you might simply have one or more faulty devices.
Do these devices have logs that you can review? Are they showing lots of retries, or do they show that your devices are stepping down? How about your LAN devices? do they show lots of retires when talking to these RFs?
by shanghai sam
by cavedweller
by shanghai sam
by akjacks
The RFs used in this network are 2.4 GHz Telxon 960SL PhaseIII portable transaction computers if that helps. The APs are CISCO 350s attached to yaggie antennas and 1 omni- directional. If interference is the problem, what average device would be inthe 2.4 GHz range for the 802.11b spec? Motorola radios, AM/FM radios, microwave ovens, ? Any other ideas?
Angela
by akjacks
by ann777
Flourescent lighting can also be a problem. Try with the lights off and compare your results.
Electrical clocks and monitors, tvs, etc. all of them can cause interferance. Even solid cement walls with rebar inside can do it.
How many computers in your network?
by shanghai sam
by stillatit
Looking at the rf issues, are the routers interfering with each other? If you take down all the routers but one, what happens to the ping time to the remaining devices? When you add back the rest, is there one which adds most significantly to ping times?
The long ping times are indicative of heavy traffic (including bad packets and retries). It may be that you have a bad remote unit which is "chattering." Try turning off all the remotes, and turning them back on in groups. If a certain groupseems to make things worse, find the bad unit in the group.
Looking at the handoff, this is supposed to happen smoothly because the routers can talk to each other. Check the manual -- this may be out-of-band communication, and may need to be direct. If they are using directional antennas, all pointed at a central box, they may not be able to talk quickly enough (or at all) to handle the hand-off.
Good luck.
by shanghai sam
by akjacks
by shmaltz
Looks to me like a window packet size problem. When you have different layer one devices IP will try to use the maximum allowed window size that the local Interface allows. When it comes to the bridge that has to convert it to a different size for the other interface. If the do not fragment flag is set it will require the bridge to drop the packet, When the client sees there is no reply it might try to resend the packet with a different size or if the do not fragment flag is not set it might take some time for the bridge to convert it.
You can test if this is the problem by using Ping and telling it the size and set the do not fragment flag. Here is how you do it in windows:
ping -l size (the size of the packet)
ping -f to set the flagping -l 1500 -f will send a packet of 1500 bytes and set the do not fragment flag.
Start out with a large size with flag set and then go down and see what happens. If you see that smaller packets come back faster the problem is because it can not take large packets so try decreasing the size of the packets the server sends out. This might be a problem since you don't want clients that are using the server on a network that can take bigger packets to communicate with smaller packets in that case you will have to use a router for the RFs.
by shmaltz
by shmaltz
The Ping commands I gave above works on Windows 2000 I don't know if it works on any other system.
by shanghai sam
by akjacks
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending