Service Manual

Dell PowerConnect W-AirWave | Best Practices Guide AMP and Dell PowerConnect W-Series Integration Strategies | 19
Chapter 5
AMP and Dell PowerConnect W-Series
Integration Strategies
This chapter describes strategies for integrating AMP and Dell PowerConnect W-Series, and contains the
following topics:
 “Integration Goals” on page19
 “Example Use Cases” on page20
 “Prerequisites for Integration” on page21
 “Enable Stats Utilizing AMP” on page21
 “WMS Offload Utilizing AMP” on page22
 “Define AMP as Trap Host using ArubaOS CLI” on page22
 “Understanding WMS Offload Impact on Dell PowerConnect W-Series infrastructure” on page26
Integration Goals
The following table summarizes the types of integration goals and strategies for meeting them in certain
architectural contexts:
Key integration points to consider include the following:
 IDS Tracking does not require WMS Offload in an All-Master or Master/Local environment
 IDS Tracking does require enable stats in a Master/Local environment
 WMS Offload will hide the Security Summary tab on Master Controller's web interface
 WMS Offload encompasses enable stats or enable stats is a subset of WMS Offload
 Unless you enable stats on the Local Controllers in a Master/Local environment, the Local Controllers do not
populate their MIBs with any information about clients or rogue devices discovered/associated with their APs.
Instead the information is sent upstream to Master Controller.
Table 4 Integration Goals in All Masters or Master/Local Architectures
Integration Goals All Masters Architecture Master/ Local Architecture
Rogue & Client Info enable stats
Rogue containment only ssh access to controllers ssh access to controllers
Rogue & Client containment WMS Offload WMS Offload
Reduce Master Controller Load WMS Offload debugging off
IDS & Auth Tracking Define AMP as trap host Define AMP as trap host
Track Tag Location enable RTLS WMS Offload enable RTLS WMS Offload
Channel Utilization enable AMON enable AMON
Spectrum enable AMON enable AMON