Deployment Guide

Dell Networking W-AirWave 7.7 | Best Practices Guide WMS Offload Details | 43
Appendix C
WMS Offload Details
WMS Offload instructs the master controller to stop correlating ARM, WIPS, and WIDS state information amongst its
local controllers because AirWave will assume this responsibility. Figure 27 depicts how AirWave communicates state
information with local controllers.
Figure 27 ARM/WIPS/WIDS Classification Message Workflow
State Correlation Process
1. AP-1-3-1 hears rogue device A.
2. Local controller 1-3 evaluates devices and does initial classification and sends a classification request to AirWave.
3. AirWave receives message and re-classifies the device if necessary and reflects this within the AirWave GUI and via
SNMP traps, if configured.
4. AirWave sends a classification message back to all local controllers managed by master controller 1, (1-1, 1-2, and 1-
3).
5. AirWave sends a classification message back to all additional local controllers managed by theAirWave server. In
this example all local controllers under master controller 2, (2-1, 2-2, and 2-3) would receive the classification
messages.
6. If an administrative AirWave user manually overrides the classification, then AirWave will send a re-classification
message to all applicable local controllers.
7. AirWave periodically polls each local controller's MIB to ensure state parity with the AirWave database. If the local
controller's device state does not comply with the AirWave database, AirWave will send a re-classification message
to bring it back into compliance.
The Rogue Detail page includes a BSSID table for each rogue that displays the desired classification and the classification
on the device.