MSM7xx Controllers Configuration Guide v6.4.0

To ensure a high quality of service for voice applications, disable all rates below 5.5. Also, ensure
that the radio is configured as follows:
• Operating mode is set to Access point only.
• Channel is set to a fixed channel, or Automatic with interval set to Disabled.
• Automatic power control is disabled under Transmit power control.
Notes on 802.11ac/n
• 802.11n supports legacy rates (1 to 54), as well as high-throughput (HT) rates MCS 0 to MCS
23.
• You must always enable at least one legacy rate for 802.11n.
• 802.11ac supports legacy rates (6 to 54), as well as high-throughput (HT) rates MCS 0 to
MSC 23, and very high-throughput (VHT) rates MCS 0 to MSC 9. The supported VHT rates
are configurable depending on the number of spacial streams (Nss): 1, 2, or 3.
• VHT MCS 9 is not supported for Nss=1 or 2 when using the 20 MHz channel width.
• VHT MCS 6 is not supported for Nss=3 when using the 80 MHz channel width.
Note regarding the HP 425, MSM430, MSM460, MSM466, and MSM466-R
On these products, the wireless rates shown for 802.11n apply to all wireless modes supported
on both radios, which are 802.11/a/b/g/n. If you remove a rate, it is removed for all wireless
modes.
VSC ingress mapping
These settings apply to the controller only and define how ingress (incoming) user traffic is assigned
to a VSC on the controller. The ingress lets you control what type of traffic the VSC will handle.
Untagged traffic on the LAN port (LAN Network on the MSM720), that is from wired client stations
or third-party APs is always handled by the default VSC defined on the controller.
• When access control is enabled, available options are:
The SSID option cannot be disabled. When enabled, the VSC accepts incoming traffic that
has its SSID set to the WLAN name (SSID) defined under Virtual AP.
If you enable the VLAN option, you can choose a network profile that is mapped to a single
VLAN, or a VLAN range, enabling the VSC to handle traffic from multiple sources. For example,
if you define different egress networks when binding VSCs to your APs, you could specify a
range to have all traffic handled by one VSC. (Ingress VLANs are not supported when controller
teaming is active.) For a network profile to appear in this list it must have a VLAN assigned
to it (on the Controller >> Network > Network profiles page) and be mapped to a port (on
the Controller >> Network > VLANs page). However, it must not be assigned an IP address
(on the Controller >> Network > IP interfaces page)
• When access control is disabled, available options are:
122 Working with VSCs