Dell PowerConnect W-AirWave | Best Practices Guide AMP and Dell PowerConnect W-Series Integration Strategies | 19Chapter 5AMP and Dell PowerConnect W-SeriesIntegration StrategiesThis chapter describes strategies for integrating AMP and Dell PowerConnect W-Series, and contains thefollowing 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 26Integration GoalsThe following table summarizes the types of integration goals and strategies for meeting them in certainarchitectural 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 notpopulate 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 ArchitecturesIntegration Goals All Masters Architecture Master/ Local ArchitectureRogue & Client Info enable statsRogue containment only ssh access to controllers ssh access to controllersRogue & Client containment WMS Offload WMS OffloadReduce Master Controller Load WMS Offload debugging offIDS & Auth Tracking Define AMP as trap host Define AMP as trap hostTrack Tag Location enable RTLS WMS Offload enable RTLS WMS OffloadChannel Utilization enable AMON enable AMONSpectrum enable AMON enable AMON