Allied Telesis AT-TQ6602 Wireless Access Point Instructions

: June 6, 2024
: Allied Telesis

Table of Contents

Firmware File
New Features
Resolved Issues
Known Issues
New Specifications
Limitations
Limitations on Channel Blanket
Supported Countries
Contacting Allied Telesis
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

Allied Telesis AT-TQ6602 Wireless Access Point Instructions

Firmware File

The firmware filename for the AT-TQ6602 Version 7.0.1-0.1 access point is:

AT-TQ6602-7.0.1-0.1.img

For instructions on how to upgrade the management software on the AT TQ6602 wireless access point, see the AT-TQ6602 Wireless Access Point Management Software User’s Guide, available on the Allied Telesis Inc. website at www.alliedtelesis.com/library.

New Features

The following new features are added to the AT-TQ6602 Version 7.0.1-0.1 access point:

Channel Blanket
For more information, see “Limitations on Channel Blanket” on page 4.
Orthogonal Frequency-Division Multiple Access (OFDMA)
Proxy ARP in standalone mode
Fast Roaming (IEEE802.11r)
Wireless Distribution System (WDS)
Inactivity Timer
Association Advertisement in standalone mode
Disabling Automatic Power Save Delivery (APSD) in standalone mode
Simple Network Management Protocol (SNMP)
Neighbor Manager AP Detection via the AT-Vista Manager EX

Resolved Issues

The following issues were resolved in Version 7.0.1-0.1 for the AT-TQ6602 wireless access point:

When MAC filtering denied a wireless client’s access to the access point, it might not issue a log about the event of disassociation.
The access point issued an error log when the technical support file was downloaded.
CCMP was displayed instead of GCMP in the Cipher Suites field on GUI page when WPA3 Enterprise was selected. GCMP is displayed from this version.
The access point issued an error log when LLDP for PoE negotiation was enabled.
The access point might fail to update firmware from the AT-Vista Manager EX.
The access point issued a log of firmware update failure even when firmware update by the AT-Vista Manager EX was successful.
The access point might shut off when it received auth and deauth frames at short intervals.
The access point could not be managed by the AT-Vista Manager EX when the Apply Config was repeatedly executed.
The access point could not be managed by AWC even when the IP of a CWM server was acquired with DHCP option 43.
The access point issued an internal log of WLAN(wdevXapX) along with an association log of a wireless client.
The access point might fail to generate dump files when it shut off unexpectedly.
The access point might cause memory leak when numerous wireless clients connected and disconnected repeatedly.
Wireless clients were not able to connect to the access point when WPA3 personal was selected and Band Steering was enabled at the same time.
The session timeout was not functioning when WPA Enterprise was selected.
Wireless clients were not able to connect to the access point with RADIUS MAC authentication using session timeout.
Radar might be detected falsely. Radar detection is improved.

Known Issues

Here are the known issues for the AT-TQ6602 Version 7.0.1-0.1 management software:

The client’s User ID and password are not included in the technical support file.
The access point might save an empty value for the Secondary RADIUS Server Key even when it is entered properly.
The access point might send NTP packets before receiving its IP address from DHCP servers.
When a wireless client’s password includes the “%” symbol, the access point does not allow the wireless client to connect to a WEP VAP.
An NTP process might start randomly.
The access point issues an error log when a radio interface starts up.
The access point might issue duplicated logs when radar is detected.
When Band steering is enabled on Radio1 and Hidden SSID is enabled on VAPs, the access point does not allow wireless clients to connect to the VAPs on Radio1.
The TX and RX rates on the Associated Clients value are displayed
incorrectly.
An ad hoc device is displayed as an AP in the type field on the Neighbor AP page.
A wireless client fails to connect to the access point when using PMKSA cache.
The access point issues an error log when the firmware is upgraded or the access point is reset to the Factory Default.
The access point issues an error log when a Radio status setting is changed.
The access point might send a Neighbor AP detection report without an SSID to the AT-Vista Manager.
Multiple unicast de-authentication packets are sent to the Radio 2 interface when an STA is disconnected due to a setting change.
The access point issues the scale of Neighbor AP with a high score.

New Specifications

The following specifications were changed in Version 7.0.1-0.1 for the AT TQ6602 wireless access point:

Autonomous Wave Control (AWC) Controller supports the AT-TQ6602 access points and other models in the same management group.
AWC Calculation results are applied to the Neighbor Managed AP detection feature.
When applying an AWC Calculation result, the access point maintains connection with wireless clients.

Limitations

Here are the limitations for the AT-TQ6602 Version 7.0.1-0.1 management software:

Changing the RTS threshold value is not supported.
The 80+80 MHz option for the Bandwidth (Radio2) is not supported.
Zero Wait DFS is not supported.
Neighbor Managed AP Detection, which is operated by AT-Vista Manage EX Management, is not supported for the access point.
Displaying of Client Traffic Counter, which is operated by AT-Vista Manage EX Management, is not supported for the access point.
Wireless clients are not able to connect via the Radio 1 interface in certain conditions. Allied Telesis verified that this behavior occurs when the number of enabling VAPs of Radio 1 and number of surrounding APs (BSSID) exceed the numbers shown in the table.
Number of Enabling VAPs| Number of Surrounding APs (BSSID)
---|---
1| 120
3| 95
5| 75
10| 55
16| 35

In real environments, this behavior may occur even if the numbers are not exceeded. It is likely caused in conditions when the wireless spatial is congested by low-rate packets.

Limitations on Channel Blanket

Channel Blanket is a single-channel wireless architecture to solve channel interferences and wireless clients’ roaming limitations in a multiple-channel architecture. Channel Blanket is enabled by AWC Controller.

Here are the limitations on Channel Blanket:

When Channel Blanket is Enabled

Band Steering on the access point is not supported.
Neighbor AP Detection on the access point is not supported.
Changing the Proxy ARP setting on the access point is not supported.
All the access points in the channel blanket must have the same radio settings.
Association Advertisement on the access point is not supported.

When Channel Blanket Radio is Enabled

Changing the RTS threshold on the access point is not supported.
Airtime Fairness on the access point is not supported.
OFDMA on the access point is not supported.
MU-MIMO on the access point is not supported.

When Channel Blanket VAP is Enabled

Changing the Broadcast Key Refresh Rate on the access point is not supported.
RADIUS Accounting on the access point is not supported.
Fast Roaming on the access point is not supported.
Dynamic VLAN on the access point is automatically disabled.
The Session-Timeout RADIUS attribute on the access point is automatically disabled.
Changing the Inactivity Timer value on the access point is not supported.
IEEE802.11a (MFP) on the access point must be disabled.

Channel Blanket Settings on AWC

The Management VLAN ID and Control VLAN ID settings are not supported.
The VAP VLAN ID and Control VLAN ID settings are not supported

Wireless Clients’ Behavior on Channel Blanket

Communications of wireless clients are interrupted when the access point is turned off or reboots. It takes approximately two minutes for the wireless clients connected to the access point that was turned off or rebooted to restore communications.

Supported Countries

The AT-TQ6602 access point version 7.0.1-0.1 management software added the following new countries:

Malaysia

Hong Kong
Thailand
Singapore

The following counties have been supported:

Australia
European Union (EU) member countries
Japan
New Zealand
United Kingdom (UK)
United States of America (USA)

Contacting Allied Telesis

If you need assistance with this product, you may contact Allied Telesis technical support by going to the Services & Support section of the Allied Telesis web site at www.alliedtelesis.com/support. You can find links for the following services on this page:

Helpdesk (Support Portal) – Log onto Allied Telesis interactive support center to search for answers to your questions in our knowledge database, check support tickets, learn about Return Merchandise Authorizations (RMAs), and contact Allied Telesis technical experts.
Software Downloads – Download the latest software releases for your product.
Licensing – Register and obtain your License key to activate your product.
Product Documents – View the most recent installation guides, user guides, software release notes, white papers and data sheets for your product.
Warranty – View a list of products to see if Allied Telesis warranty applies to the product you purchased and register your warranty.
Allied Telesis Helpdesk – Contact a support representative.

To contact a sales representative or find Allied Telesis office locations, go to
www.alliedtelesis.com/contact.

Copyright 2021 Allied Telesis Inc., Inc.
All rights reserved. No part of this publication may be reproduced without prior written permission from Allied Telesis Inc., Inc. Allied Telesis Inc. and the Allied Telesis Inc. logo are trademarks of Allied Telesis Inc., Incorporated. All other product names, company names, logos or other designations mentioned herein are trademarks or registered trademarks of their respective owners. Allied Telesis Inc., Inc. reserves the right to make changes in specifications and other information contained in this document without prior written notice. The information provided herein is subject to change without notice. In no event shall Allied Telesis Inc., Inc. be liable for any incidental, special, indirect, or consequential damages whatsoever, including but not limited to lost profits, arising out of or related to this manual or the information contained herein, even if Allied Telesis Inc., Inc. has been advised of, known, or should have known, the possibility of such damages.