Setup Guide

32 | Dell Networking W-Series Specific Capabilities in AirWave Dell Networking W-AirWave 8.0 | Best Practices Guide
Controller classification can also be updated from RAPIDS > List via the Modify Devices link.
All rogue devices will be set to a default controller classification of unclassified when WMS is first offloaded except for
devices classified as valid. Rogue devices classified in AOS as valid will also be classified within AirWave as valid for
their controller classification as well. As APs report subsequent classification information about rogues, this classification
will be reflected within AirWave UI and propagated to controllers that AirWave manages. The device classification
reflected in the controller's UI and in the AirWave UI will probably not match, because the controller/APs do not
reclassify rogue devices frequently.
To update a group of devices' controller classification to match the AOS device classification, navigate to RAPIDS >
List and utilize the Modify Devices checkbox combined with the multiple sorting a filtering features.
AMP AOS (ARM)
Unclassified (default state) Unknown
Valid Valid
Contained DOS
Table 4: ARM to AMP Classification Matrix
1. Navigate to the Clients > Client Detail page for the user.
2. In the Device Info section, select the proper classification from the Classification drop-down list (see Figure 25):
Figure 25:User Classification
Changing User Classification within the AirWave UI will push a user reclassification message to all controllers managed by
the AirWave server that are in Groups with Offloading the WMS database set to Yes.
All users will be set to a default classification of unclassified when WMS is first offloaded. As APs report subsequent
classification information about users, this classification will be reflected within the AirWave UI and propagated to
controllers that AirWave manages. It is probable that the user’s classification reflected in the controller’s UI and in the
AirWave UI will not match, because the controllers/APs do not reclassify users frequently.
There is no method in the AirWave UI to update user classification before bulk to match the controller’s classification.
Each client must be updated individually within the AirWave UI.