Welcome to Ecessa Support, we have a variety of technical information and tools for a variety of solutions. If you aren't finding a solution, or would like to talk to a technical support team member, please call 800-669-6242.

See Ecessa's full line of products and solutions
Ecessa Firmware Release Notes
Version: 10.7.5
Release Date: 2018.09.24
Revision 1.0: 2018.09.24

1. User can set system interrupt-throttle rate via CLI.

1. A WAN Virtualization static route for all traffic can cause internal route testing to work incorrectly.
2. When a translucent LAN is set to be a DHCP server, if the cable on that physical port is unplugged during boot or LAN activation, the DHCP server may not start.
3. DNS domains which have DNSSEC enabled do not automatically renew.
4. Device can show 2 Main configurations.
5. VPN dead peer options can be lost on upgrading to versions 10.7.3 or 10.7.4.
6. SSL VPN may not connect properly when it is on a translucent WAN.
7. Site that is configured for hardware fail-over and WAN Virtualization can end up in a state where one side shows as UP while the other side shows as DOWN.
8. VTI and WAN Virtualization VPN's used for accessing the internet can encounter problems with dropped TCP packets due to an MSS that is too high.
9. IPSec VPN connections associated with WAN Virtualization may not connect when using remote identifiers.
10. Adding and moving a domain row on the main DNS page in the same action causes another domain to be overwritten.
11. DHCP and PPPoE address changes will restart all encrypted WAN Virtualization sites and VPNs.
12. Ecessa Insight monitoring and user SNMP monitoring will not both work.

Known Issues
1. Creating a WAN using the CLI, with an alias of 24 characters, causes a software restart.
2. Creating a WAN Virtualization site with a name longer than 22 characters causes a software restart.
3. 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.
4. Virtual Product may boot slowly.
5. Adding an encrypted WAN Virtualization site using the CLI may not work as expected.
6. The DHCP service can stop unexpectedly.
7. The LCD display can become stuck and not display new information when keys are pressed.
8. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN entry with no name.
9. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN.
10. 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.
11. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive.
12. Using Hardware Failover with high traffic throughput can cause excessive loading of the device.
13. DNS Reverse Zone may not work correctly for load-balanced hosts.
14. 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.
15. WAN Virtualization hub location cannot have a site number that is greater than 127.
16. Ports can become disabled on legacy 600 product (7568c) when pulling a cable during traffic flow.
17. Failback static route over WAN Virtualization doesn't fail back after failing over to a WAN.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.