Basic questions

[bill.beckett]

We have an 802.11b infrastructure in our warehouse. Most of the PC's there are running a variety of 802.11b devices but we are about 90% wireless now so the reliability is very key now.

Couple of questions because I know enough to get things working but am far from a wireless guru. First question, why do AP's lock up/freeze, whatever term you want to use. We have 350 AP's (ruggedized) and once in a while the clients connecting to them will be unable to ping our Terminal Servers. If we reboot the AP, everything works fine. Secondly, when this happens, why doesnt the client move on to another AP? They are within range. Lastly, what is the best way to create redundancy within the infrastructure so that if an AP "locks up", clients can still work.

Thanks for any help.

[s.konduru]

hi

client does not move to another AP when a AP goes dowm in the area he is in.AP's exchange info abt the client when he roams from one AP to other.

regarding the redundnacy u got to have standby AP's att to ur primary AP's.

regards

[bill.beckett]

Like I said, I'm no expert here. So let me get this straight...I can roam and pick up another AP BUT if I'm connected to an AP and it goes down, even if I am within range of another, it will not pick up that working AP?

[bott]

We have APs (350 and 1200s) across our entire building to provide full coverage everywhere. When I brought AP's down while we were upgrading to IOS, (brought down = unplugged from ethernet & power-over-ethernet) my laptop with a Cisco 350-series PCMCIA card *stayed on the network* with no interruption of network service, and immediately reauthorized itself and connected to a different access point.

I don't know what he was talking about, but I can roam to a different AP when one goes down, even our wireless IP phones can.

[bill.beckett]

That's always how I thought it would/should work but that's my problem, it's not.