Ecessa Firmware Release Notes
Release Date: 2016.03.08
Revision 1.0: 2016.03.08
1. Automatic error reporting feature has been added to improve the quality of the software.
2. Added SerialNumber object to ECESSA-MIB.
3. When the device sees that the available memory is getting low an e-mail alert will be sent.
4. Improve Hardware Failover to attempt recovery of Idle device when communication is lost.
5. WAN Virtualization can send out e-mail alerts on status changes.
1. Multiple simultaneous QoS changes can cause the system to restart.
2. Static Routes may not apply properly for bridges which had the same name as the WAN.
3. Loading a configuration while IPSec VPN is active may cause device to become inaccessible.
4. It should be recommended to the user that e-mail alerts are also enabled when Hardware Failover is enabled.
5. Web service can potentially not start during the boot up sequence.
6. When viewing current sessions in the GUI or the CLI ports show up incorrectly.
7. VPN IPSec security associations which have auto start enabled will attempt to start the connection twice.
8. Multiple email alerts triggered simultaneously are received as duplicates of the last alert created.
9. DNS domains that are queried for load balanced records always respond in the same order.
10. IPSec VPN connections can lose their ability to properly route traffic.
11. A translucent mode WAN and a NAT WAN on the same port can cause encrypted WAN Virtualization traffic problems.
12. Dual Role DNS backup site could potentially not respond with the updated zone from the master site when a change was made.
13. Replacing a Hardware Failover unit with a different device, then replicating the configuration to the idle unit, can cause the pair to lose communication with each other.
14. The network device driver can cause the device to become unresponsive.
15. Diagnostics iperf not accepting time parameter.
16. IPSec VPN connections may connect with the wrong configured Security Association.
17. IPSec IKEv2 security associations to Cisco devices not properly passing traffic on all subnets.
18. VPN IKEv2 connections can fail when connectivity to the remote device is lost, and continue to fail after connectivity is restored.
19. VPN entries with long names may crash the web server on disable.
20. VoIP CLI show command prints empty source port.
21. IPSec VPNs might not work properly when adding security associations while disabled and then enabling the VPN.
22. Loading a different configuration can cause problems when trying to create and connect IPSec VPN's.
23. Deleting a QoS classifier from the GUI might not work properly.
24. Configured IPSec VPN connections may not get activated.
25. When creating an IPSec VPN with the CLI the number of tests default to zero, which can cause an unnecessary fail-over.
26. Top Services graph shows incorrect port numbers.
27. When connecting to a PPTP server behind the Ecessa with WAN Virtualization enabled the device can become unresponsive.
28. Loading configurations with IPSec VPN SA names that differ only by case from existing SA names can result in both connections running and incorrect behavior.
29. VPN between two Ecessa devices could get into a scenario where one side shows UP and the other shows DOWN.
30. All comment sections throughout command line and web interface should not allow invalid characters.
31. L2TP VPN connections can fail to establish after activating changes to another VPN connection.
32. Translucent mode WAN's with auto-created LAN's can use the wrong network mask for the WAN.
33. Device can become unresponsive for a period of time when stopping and starting VPN connections from the CLI.
34. When creating an IPSec Site to Site VPN in the GUI there is no validation to not allow the user to not enter any local or remote LANs, which will result in the connection not working.
35. SNMP Trap and Inform functionality plus WAN Virtualization tunnel information added to the ECESSA MIB.
36. Loading a configuration with IPSec VPNs can cause device to become unresponsive.
37. Deleting and adding IPSec VPN security associations can cause some connections to not come up properly.
38. Deleting IPSec VPN Security Associations, then adding others, can result in some of them not connecting or not passing traffic properly.
1. 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.
2. Encrypted WAN Virtualization traffic may not route as expected when the feature is not configured correctly.
3. WAN Virtualization hub location cannot have a site number that is greater than 127.
4. IPSec VPN failover test point type 'Manual IP Configuration' does not work as expected.
5. IPSec VPN Failback option does not work as expected.
6. When changing static routes that use aliases there is a small possibility that traffic could continue using the WAN over which it was previously routed.
7. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow.
8. VTI VPN which is behind NAT will not be able to connect.
9. Device can restart after a period of time when the sites tunnel configurations do not match.