Users Guide

OmniVista 3600 Air Manager 8.2.4 | Best Practices Guide Appendix C WMS Offload Details | AS
Appendix C
WMS Offload Details
WMS Offload instructs the master switch to stop correlating ARM, WIPS, and WIDS state information among its
local switches because OV3600 will assume this responsibility. Figure 28 depicts how OV3600 communicates
state information with local switches.
Figure 28: ARM/WIPS/WIDS Classification Message Workflow
State Correlation Process
1. AP-1-3-1 hears rogue device A.
2. Local switch 1-3 evaluates devices and does initial classification and sends a classification request to OV3600.
3. OV3600 receives message and reclassifies the device if necessary and reflects this within the OV3600 WebUI
and via SNMP traps, if configured.
4. OV3600 sends a classification message back to all local switches managed by master switch 1, (1-1, 1-2, and 1-
3).
5. OV3600 sends a classification message back to all additional local switches managed by the OV3600 server.
In this example all local switches under master switch 2, (2-1, 2-2, and 2-3) would receive the classification
messages.
6. If an administrative OV3600 user manually overrides the classification, then OV3600 will send a re-
classification message to all applicable local switches.
7. OV3600 periodically polls each local switch's MIB to ensure state parity with the OV3600 database. If the
local switch's device state does not comply with the OV3600 database, OV3600 will send a re-classification
message to bring it back into compliance.
TheRogue Detail page includes a BSSID table for each rogue that displays the desired classification and the
classificationon the device.