@pmonardo uses a 3rd party mib crawler tool against the aruba mibs. If you don't want to use a 3rd party app, you could just take the oid and run it against the internal translation scripts on the AMP like so:
[root@amp mibs]# oidtranslate 1.3.6.1.4.1.12028.4.15
AWAMP-MIB::awampEvent
[root@amp mibs]# oidinfo 1.3.6.1.4.1.12028.4.15
AWAMP-MIB::awampEvent
awampEvent OBJECT-TYPE
-- FROM AWAMP-MIB
::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) airwave(12028) awamp(4) 15 }
Some of the mibs may be harder to define from just viewing in the mibs, which is why I suggested checking with support.