Appendix B – WMS Offload Details
WMS offload instructs the Master controller to stop correlating ARM, WIPS, and WIDS state
information amongst its Local controllers, because AWMS will assume this responsibility. Figure 4
below depicts how Dell PowerConnect W AMWS communicates state information with Local
controllers.
Figure 19 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 the AWMS
3.
AWMS receives message and re-classifies the device if necessary and reflects this within AWMS
GUI and via SNMP traps, if configured.
4.
AWMS sends a classification message back to all Local controllers managed by Master controller 1,
(1-1, 1-2, and 1-3)
5.
AWMS sends a classification message back to all additional Local controllers managed by the
AMWS 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 AWMS user manually overrides the classification, then AWMS will send a re-
classification message to all applicable local controllers.
7.
AWMS periodically polls each Local controller's MIB to ensure state parity with AWMS' database.
If the Local controller's device state does not comply with AWMS' database, AWMS will send a re-
classification message to bring it back into compliance.