User Guide: Vista Manager AWC Plug-in version 3.11.0

# Overview

AWC-DCN (AWC-Dynamic Client Navigation)
Configured VAPs
Supported Wireless APs
Support Limits
Process of introducing AWC-DCN
Notes

## AWC-DCN (AWC-Dynamic Client Navigation)

When a large wireless network consisting of multiple wireless APs is deployed, wireless clients may enter a "Sticky Client" situation, in which they try to continue communicating with an AP once they associate with it, even though the signal has weakened after they leave the vicinity of the AP.
Sticky terminals not only slow down their own communications, but also affect surrounding wireless clients by repeatedly retransmitting in unstable radio environments.
AWC-DCN (AWC-Dynamic Client Navigation) uses the functions of IEEE 802.11k Radio Resource Measurement (RRM) and IEEE 802.11v Wireless Network Management (WNM), It shares wireless clients information within the wireless APs in the same group, and encourages Sticky Client to migrate to an AP that has a stronger signal and is better suited for communication. Also, even in environments where Channel Blanketing cannot be adopted, the APs can equalize the number of associating clients and distribute the load among them.

### Configured VAPs

The DCN VAP, which optimizes the number of associating clients by AWC-DCN, is defined in the "DCN Profile".
The DCN profile creates a DCN group, which is the administrative unit of the AWC-DCN. It sets the monitor intervals of the sticky client and load, specifies the applicable APs, in addition to configuring the DCN VAP.
The configurations which are related to the management and basic operation of APs, such as Basic Configuration (Timezone, NTP, syslog, and SNMP configurations), Radio Configuration, and LAN Configuration, are defined in AP Profile.
For VAP configuration with a VAP number that overlaps with the AP profile, the DCN profile takes precedence.
If other profiles are applied at the same time, the SC profile, CB profile, DCN profile, and AP profile will take precedence in that order.

> Note

> > AWC-DCN is not supported mixed with AWC-SC or AWC-CB.

## Supported Wireless APs

The following AP models can be used with the AWC-DCN:

- TQ series
  - TQ6602 GEN2 and TQ6702 GEN2
    Firmware Version 8.0.2-0.1 or later

## Support Limits

The number of AWC-DCN-related settings that can be managed by the AWC plug-in is as follows:

- Number of profiles
  Unlimited
- Number of APs per DCN profile
  350 APs (up to the maximum number of managed APs per profile)
- Number of VAPs (multipul SSIDs) per DCN
  - TQ6602 GEN2 and TQ6702 GEN2:
    32 VAPs (16 for each of 2.5GHz and 5GHz)

## Process of introducing AWC-DCN

To build a hybrid wireless system, follow the steps below.

1. Create a management group.
2. Resister APs.
3. Next, create the AP profile.
4. Create the DCN profile, and select the APs to assign.
5. Turn the DCN profile ON.
6. Assign the AP profile to apply the AP and DCN profiles to the APs.

## Notes

- The wireless client must support IEEE 802.11k/v/r.
- DCN profile needs to be associated with a management group. That is, all APs which that apply the same DCN cocnfigurations must belong to the same management group.
- When creating SSIDs for DCN VAPs, SSIDs that overlap with other DCN profiles cannot be used.
- AWC-DCN is not supported mixed with AWC-SC or AWC-CB.
- AWC-DCN cannot be used with Band Steering.
- AWC-DCN cannot be used with WDS.
- Emergency mode can not be used in conjunction with AWC-SC.
  When configuring an AP Profile, do not set "Condition" to "Only Emergency Mode" on the radio used for AWC-DCN.
  In addition, do not set any VAP Statuses to "Emergency" in the radio band.

14 Dec 2023 10:09