I believe that the classifications are actually being pushed as shown by the output of:
(MC6000-WH-LISCR-S0) #show wms ap A0:F3:C1:78:63:1E
AP Info
-------
BSSID SSID Channel Type RAP_Type Status Ageout HT-Type HT-Sec-Chan
----- ---- ------- ---- -------- ------ ------ ------- -----------
a0:f3:c1:78:63:1e TP-LINK_78631E 6 generic-ap manually-contain up 0 HT-40mhz 10
The classification 'manually contain' is set when the Airwave sends the classification. When we disable management of rogues through Airwavem this classification changes to automatic, but our results are the same (i.e. the rogue isn't contained).
The other thing is that containment works fine when the rogue is on the same channel as a nearby AP. This is consistent with client-aware configuration, in that the AP is containing rogues on it's same channel, but won't go of channel when clients are connected.
So it's clear that rogue detection, classification, containment, and client-aware work fine. The issue is that the air monitors, which are configured to be rogue aware, and to scan multiple bands and all regulatory domains aren't doing anything to contain the rogue. The rogue is only contained when I put an Aruba AP on the same channel as the rogue.