| 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-18164 |
Adding a new AP to the network does not automatically sync to Tunnel Concentrator. Workaround: When you add APs, manually push a complete configuration to the Tunnel Concentrator. |
| CFD-18411 | Primary Tunnel Concentrator does not dynamically learn or update when an AP's IP address changes. |
| 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-242 | An issue has been observed where upgrading Tunnel Concentrator and then making changes, RX and TX counters do not reflect changes. |
| 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: Multicasting is not supported in this release. Disable all multicasts. |