| Issue | Description |
|---|---|
| CFD-14254 and IQVPN-279 | There is an issue with the Network Usage calculation for Tunnel Concentrator. Some APs have reported a high network usage during periods where no clients are connected. |
| CFD-16364 |
When Tunnel Concentrator receives a large volume of multicast traffic (for example, mDNS traffic) from the client traffic bridge port, Tunnel Concentrator may become unresponsive. Workaround: A workaround is to block multicast traffic on the switch port that is connected directly to Tunnel Concentrator. |
| CFD-16486 | Tunnel Concentrator statistics are showing packets being transmitted for inactive tunnels |
| CFD-16801 | There is an issue with pushing configuration from ExtremeCloud IQ to Tunnel Concentrator where there is a large number of APs. A fix for this issue is being provided in an upcoming ExtremeCloud IQ patch release. |
| IQVPN-210 | Tunnel Concentrator may drop packets at ~50-second intervals when the Dashboard is accessed or viewed; this behavior occurs only during Dashboard use. |
| IQVPN-220 | Spanning Tree BPDUs are replicated by Tunnel Concentrator to all tunnels, resulting in extra frames being sent to clients but no functional side effects. |
| IQVPN-247 | Changing VLAN Settings on a data port of Universal Compute Platform (host) after Tunnel Concentrator installed may cause networking access issues to the application. This issue has been experienced on 1130C platforms. Rebooting the Universal Compute Platform host may be required to re-establish connectivity. This issue will be resolved in a future revision. |
| IQVPN-336 |
When a multicast ACL is enabled but contains no entries, Tunnel Concentrator mistakenly allows all multicast traffic (for example, allowing mDNS). The correct behavior is to block all multicast traffic. Workaround: Add at least one multicast IP address to the ACL (for example, 224.0.0.200). Once an address is configured, the ACL allows that multicast address and blocks all other multicast traffic, including mDNS (224.0.0.251, UDP port 5353). |