Example Use Cases; When To Use Enable Stats; When To Use Wms Offload; When To Use Rtls - Dell PowerConnect W-Airwave Manual

Example Use Cases

The following are example use cases of integration strategies:

When to Use Enable Stats

You want to pilot AMWS and doesn't want to make major configuration changes to their infrastructure or
manage configuration from AWMS.
NOTE: Enable Stats still pushes a small subset of commands to the controllers via SSH.
See "Enable Stats Utilizing AWMS" on

When to Use WMS Offload

You have older Dell PowerConnect W infrastructure in a Master/Local environment and their Master

controller is fully taxed. Offloading WMS will increase the capacity of the Master Controller by offloading
statistic gathering requirements and device classification coordination to AWMS.
You want to use AWMS to distribute client and rogue device classification amongst multiple Master

Controllers in a Master/Local environment or in an All-Masters environment.
See the following topics:

"WMS Offload Utilizing AWMS" on page 22

"Understanding WMS Offload Impact on Dell PowerConnect W Infrastructure" on page 26

"WMS Offload Details" on page 41


When to Use RTLS

A hospital wants to achieve very precise location accuracy (5 -15 feet) for their medical devices which are

associating to the WLAN.
You want to locate items utilizing WiFi Tags.

NOTE: RTLS could negatively impact your AWMS server's performance.
See "Leveraging RTLS to Increase Accuracy" on


When to Define AWMS as Trap Host

You want to track IDS events within the AWMS UI.

You are in the process of converting their older third-party WLAN devices to Dell PowerConnect W and want

a unified IDS dashboard for all WLAN infrastructure.
You want to relate Auth failures to a client device, AP, Group of APs, and controller. AWMS provides this

unique correlation capability.
See "Define AWMS as Trap Host using Dell PowerConnect ArubaOS CLI" on

20 | AWMS and Dell PowerConnect W Integration Strategies
page 21.
page 43.
Dell PowerConnect W AirWave 7.2 | Best Practices Guide
page 23.