AMP Won't Auto-discover Downgraded Cisco APs

Aruba Employee
Aruba Employee

After downgrading some Cisco access points from LWAPP to IOS devices, AMP may fail to discover the newly modified AP(s). The reason is that the APs sysObjectId can become mangled during the downgrade to IOS, rendering AMP unable to determine exact device type. You can test this by walking the devices MIB Using_AMPs command line SNMP tool: 

sw public sysObjectId

Will return an error message like:

RFC1213-MIB::sysObjectID.0 = OID: CISCO-SMI::ciscoUnknownRptrGroup

The work-around to this auto-discovery failure is to manually add the IOS device Using_AMPs Device Setup -> Add page, specifying the correct device type, IP address and other credentials. Devices can also be manually added using CSV files

Version history
Revision #:
1 of 1
Last update:
‎06-09-2014 08:53 AM
Updated by:
Labels (1)

Have you ever found a resolution? I am having the same issue however it is that AMP can discover my 1140, 1200, and 1240 APs but not auto discover my 2602, those have to be added manually.


Hi Dusco,


could you please try doing a snmp walk to the AP from Amp's Cli?


#s2w <ip-of-ap> <community-string> .1


Please run this command for an AP which is not already added to Airwave. If you see a response, please open a support ticket by sending your request to




Aruba Networks Inc.

Search Airheads
Showing results for 
Search instead for 
Did you mean: