Follow

10.7.1

Ecessa Firmware Release Notes
Version: 10.7.1
Release Date: 2017.01.16
Revision 1.0: 2017.01.16

New Features
1. Open Shortest Path First (OSPF) dynamic routing protocol is now supported.

Changes
1. Add ability to configure OSPF dynamic routing using the CLI.
2. Add ability to configure OSPF dynamic routing using the graphical user interface.

Fixes
1. Static Routes with a destination of 0.0.0.0/0 do not get applied.
2. Remote Syslog may get critical error messages when running static route path testing.
3. Port Link Speed and Duplex Settings can get stuck displaying 'Auto Negotiate' when there are manual settings selected.
4. When dynamic local endpoint for WAN Virtualization/Channel Bonding site is entered as an IP, the site will not function correctly.
5. DNS SOA e-mail entry is too strict which does not allow valid SOA e-mail addresses.
6. WAN Virtualization email alerts can cause delays in processing Site and Tunnel status changes.
7. Loading configurations that use Static Route Path testing can cause the software to restart.
8. Making changes to services email-alert via command line interface may cause a services reset.
9. WAN Virtualization status is not correct when viewing the live site from the cloud.
10. Traffic pulled from a bridge on a LAN to be forwarded will be dropped if the firewall is enabled.
11. Static routes with a WAN IP entered as the route will not fail over correctly.
12. The serial console can get into a state where it is not accessible after the device has been powered on.
13. One to one NAT rule may not be fully removed when a matching LAN address exists in the disabled state.
14. When using aliases in a static route, and path testing fails for a WAN, traffic for the static route may still be sent over that WAN.
15. Next Hop Routes feature allows user to enter total number of Sources that exceeds the maximum number allowed.
16. Static Route Path testing can get in a state where it does not work as expected.
17. One-to-one NAT rule will not be applied to a WAN in special circumstances.
18. After deleting a WAN, or moving a WAN to a different port, any non-base IP addresses used by other features within the WAN subnet will not be removed from the old port.
19. Hardware Failover Idle device performs static route path testing.
20. Management ACL which uses hostnames can get into a state where those hostnames are not added to the ACL.

Known Issues
1. Virtual Product may boot slowly.
2. Adding an encrypted WAN Virtualization site using the CLI may not work as expected.
3. The DHCP service can stop unexpectedly.
4. The LCD display can become stuck and not display new information when keys are pressed.
5. Enabling WAN Virtualization encryption using the CLI without specifying a VPN name will create an IPSec VPN security association entry which has no name.
6. Phone calls made within a short time after enabling the VoIP feature may not choose the Primary WAN.
7. 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.
8. When a DHCP WAN is given a very short lease time by the modem the Ecessa device can become unresponsive.
9. Using Hardware Failover with high traffic throughput can cause excessive loading of the device.
10. DNS Reverse Zone may not work correctly for load-balanced hosts.
11. 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.
12. Activating Port Forwarding configuration changes can cause the device software to restart.
13. WAN Virtualization hub location cannot have a site number that is greater than 127.
14. IPSec VPN failover test point type 'Manual IP Configuration' does not work as expected.
15. IPSec VPN Failback option does not work as expected.
16. When changing static routes that use aliases it is possibie that traffic could continue using the WAN over which it was previously routed.
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.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.