Issue with a single Ruckus 7363

[Oaktech]

My partner school is having issues with a single Ruckus 7363 AP out of its network of 12.

 

Clients connect to it with good or excellent signal and and occasionally logins fail or are very slow. If you roam to it, Internet access seems zippy but access to internal services such as mapped drives is very slow or fails.

 

It's happening about 3-4 times a week and sometimes a reboot fixes it, sometimes leaving it off for an hour fixes it. Sometimes it just fixes itself.

 

Any ideas. I'm sure it's nothing serious becausevthe other 11 points are working fine.

[ITJS2015]

Is your AP on a vlan or on a unmanaged switch, have your tried replacing the cable from the AP to the switch or replacing the cable in the patch panel which leads to the AP

 

If you have the same settings as the other APs then it would be down to a firmware update or a rubbish cable.

 

Have a go with that first

[EricM_NetCtrl]

There a few things you could check out, like the previous post check the cable, also is the AP plugged into a POE switch or into Power Injector?, what link speed are you getting on your switch port? What firmware are you running? I would make sure your on 9.8.3.0.14. Is the newtwork flat or Vlan's? do you have any ACL's applyed?

 

Regards

 

Eric

[Oaktech]

Thanks guys.

 

It's a flat network, no vlans, acls or other jiggery :censored:ery.

 

It's plugged into a smart switch and is locally powered.

 

The link speed shows as 1gbps on both ap and console.

 

The only oddity is that the pass through port is being used. The machine on the pass through is off most of the time so I can't say whether that machine experiences any of the weirdness.

 

The console shows no abnormal events and it shows the firmware as being the same as all the other APs

[ITJS2015]

I would swap a working AP from one classroom to the location where is itsnt and see if there is anything off then

[Oaktech]

Ok,

 

I'm not on the site and my Tech has emailed to say that as of this morning a reset has fixed it.

 

He can't replace the cable without assistance as it's at high level and not plugged into a patch point, it's on a long cable (~25m) right back to the switch.

 

Firmware is 9.4.0.0.110 and has never been upgraded but as the school doesn't have a support contract we can't access firmware upgrades - its on next year's budget bid.

 

I'll pop in tomorrow and give him a spare brand new AP and see if that fixes it. I can't afford to swap a known good one because the wireless is heavily utilised by static clients (all printers, MFDs and a lot of desktops are wireless) I'm working on the wired infrastructure, someone sold them the wireless about 4 years ago and basically said 'you'll never need to use a wire again'

 

which is stupid.

[ITJS2015]

Its worth knowing that swapping it for a good one will work in that area for an hour or 2 so that it pin points if its either the cable or the AP.

 

If the cable is static then I would be tempted to take it to your switch and leave the iffy AP in you server room and leave it on so you can monitor it yourself and if you have a spare then put the spare one in the place where your iffy one was.