Monitoring, Management & Location Tracking

Aruba AP125: "No radio cards found in device"; device displayed as AP50

Aruba Employee

After discovery of Aruba AP125, device is displayed as AP50 and the following error message is displayed: "No radio cards found in device."

One possible cause of this behavior is that the AP is reporting one ID number and the AMP is expecting another (in ThinAPDiscovery.pm) --e.g. the ID number being reported by that type of AP is different in a later version of the AP and the AMP code hasn't been updated yet to include that number.

Possible Solutions: 
...Upgrade to the latest version of the AWMS server
...Contact Support for a patch
...Ignore the incorrect type being displayed

The first two options require that you delete all of the affected APs and let AMP rediscover them --to cause AMP to discover the APs more quickly, go to the APs / Devices | Monitor page for the controller and press <Poll Now>.

Things to try:
Check to see that the correct credentials have been entered for the controller (View Device Credentials link on the APs / Devices | Manage page)

Do an snmpwalk of the controller to see if the APs are correctly reporting their type (the resulting output can be sent to Support to help diagnose the problem):

# s2w [controller's IP address] [community string] wlanAPModel -On

Check to see if the APs are in "air monitor" mode. If so, contact Support.
After discovery of Aruba AP125, device is displayed as AP50 and the following error message is displayed: "No radio cards found in device."

One possible cause of this behavior is that the AP is reporting one ID number and the AMP is expecting another (in ThinAPDiscovery.pm) --e.g. the ID number being reported by that type of AP is different in a later version of the AP and the AMP code hasn't been updated yet to include that number.

Possible Solutions: 
...Upgrade to the latest version of the AWMS server
...Contact Support for a patch
...Ignore the incorrect type being displayed

The first two options require that you delete all of the affected APs and let AMP rediscover them --to cause AMP to discover the APs more quickly, go to the APs / Devices | Monitor page for the controller and press <Poll Now>.

Things to try:
Check to see that the correct credentials have been entered for the controller (View Device Credentials link on the APs / Devices | Manage page)

Do an snmpwalk of the controller to see if the APs are correctly reporting their type (the resulting output can be sent to Support to help diagnose the problem):

# s2w [controller's IP address] [community string] wlanAPModel -On

Check to see if the APs are in "air monitor" mode. If so, contact Support.

Version history
Revision #:
1 of 1
Last update:
‎06-09-2014 09:41 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.