10.6.9

Ecessa Firmware Release Notes 
Version: 10.6.9 
Release Date: 2018.02.12 
Revision 1.0: 2018.02.12 

Improvements
1. Add validation to not allow aliases with FQDNs to be used for static routes. 
2. Diagnostics iperf now has the ability to set UDP bandwidth. 
3. The web interface now informs the user that user account information is not sent to the idle hardware failover device during replication. 

Fixes 
1. The idle hardware failover unit can get in a state where it can't communicate with the active unit. 
2. QoS applied to WAN Virtualization sites may cause packet loss when packet throughput rates are high. 
3. The GUI "IP Address or Hostname" field for simple host records in a DNS domain will handle only up to 63 characters. 
4. DNS simple host records do not accept underscores where an FQDN is accepted. 
5. Devices connected to Ecessa Insight can create duplicate monitoring alerts. 

Known Issues 
1. When a device is running a configuration which has WAN Virtualization sites and loads a configuration which does not have WAN Virtualization sites configured the device software may restart. 
2. WAN Virtualization configurations where tunnels have high packet loss and the tunnel testing parameters are set high can cause the tunnel to bounce more often then the testing parameters. 
3. Virtual Product may boot slowly. 
4. Adding an encrypted WAN Virtualization site using the CLI may not work as expected. 
5. The DHCP service can stop unexpectedly. 
6. The LCD display can become stuck and not display new information when keys are pressed. 
7. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN entry with no name. 
8. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN. 
9. Using the CLI to create an alias with multiple addresses will reorder the addresses and remove duplicates, making the alias unusable for firewall forwarding rules. 
10. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive. 
11. Using Hardware Failover with high traffic throughput can cause excessive loading of the device. 
12. DNS Reverse Zone may not work correctly for load-balanced hosts. 
13. WAN Virtualization which is using non base IP addresses can not route as expected when a static route is in place which applies to all traffic. 
14. WAN Virtualization hub location cannot have a site number that is greater than 127. 
15. Site-to-site VPN may attempt to use a WAN that is down. 
16. IPSec VPN failover test point type 'Manual IP Configuration' does not work as expected. 
17. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow. 
18. A VTI VPN on an Ecessa device which is behind NAT will not be able to connect. 
19. Failback static route over WAN Virtualization doesn't fail back after failing over to a WAN.