Author
Topic: Help with RFS 6000 installation (Read 14784 times)

So my friends, last week I bought a RFS 6000 with 24 licenses (I checked on-line and found that it had been upgraded from 8 licenses) and I tried to put it on my network and replace my old WS 5100. There are 16 AP300 on the network and the Firmware of the RFS 6000 is currently 5.4.3.0-018R, which is compatible with AP300 as it is before x5.7.1.x

Now first step was to factory reset the switch to get new username/passwordNext I connected with the Browser and fixed the IP address on the uplink port, changed password, put Country setup for the RF and created a Wireless Network with SSID.

Next I connected the my 16 units of AP300 which where on another switch in the uplink port of the RFS 6000.Within a few minutes it recognized and adopted all of them.

The problem now is that I cannot find the SSID anywhere with wireless devices.

When I check the status monitor of the RFS 6000 is has a red X mark with RF Quality Poor.

You can buy and sell the device on your own (that's law; it's call the right of first sale), and that includes the "demo" licenses the come with it. But my understanding is additional licenses are not transferable and cannot be resold. You might get it work, but you won't be able to get support or maintenance until you get your own licenses, and it's a legal gray area at best.

But for why there's no SSID: you did a factory reset on the RFS6000 controller and set up the network. Then you had it adopt APs. But at no point did you assign a profile to the APs. The wireless SSIDs don't attach to APs devices directly. Instead, they attach to profiles, and profiles attach to devices.

> Or change your encryption from TKIP-CCMP to WPA2-CCMP if your devices are compatible with WPA2

I'd hope so. TKIP is kinda broken now. If you're running that, I could sit in your parking with a laptop running the right software and after a few minutes start reading traffic as it goes across your network.

set the me port ip to to anything 10.x.x.x then give then set the virtual interface with the lan static address

The way I have it is the ME port is my backdoor if you like, off the LAN so if the switch throws a wobbly and you can not get access via the lan you should be able toovia the ME1 port

So ge1 is the physical and is enabledthen set the Lan ip on VLan 1 ( or what ever the vlan number is you have set for access

Thank you !!!!!!! I fixed it, I no longer get IP conflicts, and now I can actually manage the RFS 6000 from Wifi network !!!

The only thing left to fix now is the disconnections...

I found this article :

Wireless Clients are disassociated due to 4 Way Handshake Timeout

During the WPA/WPA2 handshake an access point waits a defined amount of time (timeout) for a response from the client. If a response is not received, the access point resends the handshake message. This process repeats until a successful handshake is performed or until the maximum number of attempts have been made. Some clients may be slow to respond to WPA handshake messages due to limitations of the device or problems in the RF environment. If the handshake is unsuccessful, the client will be disassociated from the WLAN and the following log message will be seen on the WLAN controller:

2015-03-12 11:51:05 OFFICE-FLOOR-AP2 DOT11 CLIENT_DISASSOCIATED Client '00-AA-BB-CC-DD-EE' disassociated from wlan 'OFFICE-FLOOR-AP' radio 'OFFICE-FLOOR-AP2:R2': dot11i 4way handshake timeout (reason code: 15)Resolution Increase the WLAN WPA-WPA2 handshake attempts and timeout values to allow the client to have more time to process and respond to the message.