Gabe,Have you enabled the proxy-radius option against the M-Wireless WLAN within the RFS-7000? I assume the external radius server ip is already configured under the wlan. You’ll just need to make sure that this external radius server is reachable through the switch and enable the aap-radius-proxy setting.  You should also start the onboard radius server.

 

For example :

 

If the external radius server ip is 10.10.10.111, first make sure it is reachable through switch.

RFS7000(config)#do ping 10.10.10.111

 

Configure following cli commands under

RFS7000(config-wireless)#wlan 1 radius server primary 10.10.10.111

RFS7000(config-wireless)#wlan 1 radius server primary radius-key 0 testme

RFS7000(config-wireless)#wlan 1 aap-proxy-radius enable

 

To enable onboard radius server under

RFS7000(config)#service radius

 

With the aap-proxy-radius option enabled, switch configures the AAP to forward all requests to the onboard radius server and it proxies the requests to the external radius server. If you don’t enable proxy-radius you’d have to add the IP address of each AAP 5131 as a RADIUS client within your external RADIUS server.

Thanks for the quick replies. Raymond, the checkbox for Independent Mode is not checked. Bill, we think the overall radius configuration is correct on the switch because we are able to authenticate to M-Wireless through an AP300 that is directly connected to the switch.  I don't think we have the onboard radius server enabled so we will give that a try. Thanks, Gabe

Hi Gabe, As Bill said, "If you don’t enable proxy-radius you’d have to add the IP address of each AAP 5131 as a RADIUS client within your external RADIUS server" You can check that by checking your radius log. You will see that the radius client (IP address of AAP 5131) is not known. Matt

Under the WLAN settings on the RFS7000 do you the Independent mode check? If so uncheck that box.