EQ/OS Release Notes

Transcription

1 EQ/OS Release Notes About This Document...2 Supported Hardware...2 EQ/OS 10 Documentation...2 Enhancements and Fixes in c...3 What s New... 3 Change Notices... 3 Resolved Issues... 3 Enhancements and Fixes in b...4 What s New... 4 Change Notices... 4 Resolved Issues... 4 Enhancements and Fixes in a...5 What s New... 5 Change Notices... 5 Resolved Issues... 5 Known Issues...7 EQ/OS 10 Images and Documentation...9 Registering Your Product...10 Page 1 of 10

2 EQ/OS Release Notes 10 November 2017 About This Document These are the release notes for EQ/OS Version releases. Release notes are available from the Fortinet Support Site; in the Coyote Point file download area: 1. Log in to support.fortinet.com using your support account information. 2. Click on Download near the top of the Support Home Page, and choose Firmware Images from the drop-down menu. 3. In the Select Product box, choose CoyotePoint. 4. Click on the Download tab. 5. Click on Supported Hardware This release is supported on all LX and GX model Equalizer hardware. For download image links, see EQ/OS 10 Image and Documentation. EQ/OS 10 Documentation The online Webhelp system in the Equalizer graphical user interface (Web UI) contains complete hardware installation, configuration, and operation information. To display Webhelp while using the Web UI, press the F1 key or choose Help > Context Help from the menu at the top right of the Web UI screen. The Administration Guide is the PDF format version of the Webhelp available in the Web UI. The latest Guide is always available for download in PDF format here: Page 2 of 10

3 EQ/OS Release Notes 10 November 2017 Enhancements and Fixes in c What s New Enhanced security Improved file system management Configuration converter Bug Fixes Change Notices N/A Resolved Issues Bug ID Description File System Log FS gets overloaded in lower end systems Security Fix Multiple vulnerability fixes Configuration Management Configuration converter feature for CP/FortiADC E Series to FortiADC D Series systems SNMP Incorrect unit for sent/received L4 cluster data Server Side Encryption Fixes a race condition that causes YXOR to crash. Page 3 of 10

4 EQ/OS Release Notes 10 November 2017 Enhancements and Fixes in b What s New Enhanced security Improved failover stability Change Notices N/A Resolved Issues Bug ID Description Security fix CVE and CVE Failover Server cipher preference flag causing multiple issues Failover Panic (reboot) on default backup in HA when default primary name is changed Documentation Delay parameter for server pool statistics Documentation Server cipher preference flag on HTTPS clusters Documentation Outbound NAT should not be bound to a cluster IP. Page 4 of 10

5 Enhancements and Fixes in a What s New Updates to statistics library to minimize CPU usage Improved Header Editing reports Updated Brazilian Portuguese translations Updated localization support for traditional Chinese Change Notices Header Insert fixes for HTTP 0.9/1.0 Unclamp MTU for ixg interfaces Web UI ACL page fixed for locale other than English (en) Switch port statistics logging disabled by default Multiple SSL stability fixes Resolved Issues Bug ID Description 9231 CLI certificate fetch Fixes and issue where fetching certificates from a password protected FTP server was broken CLI regex Fixes an issue where the user was not allowed to remove "regex" from a redirect responder Web UI Locale Updated localization support for traditional Chinese Web UI Tool Tips Added tool tip for Header, Status Code and Authentication tabs on HTTP and HTTPS health check page Failover Fixes an issue where the floating IP entry was not cleared from the ARP cache when the interface alias is deleted Web UI Locale Updated Brazilian Portuguese translations CLI Smart Control Fixes an issue where force-deleting a smart control object was not working CLI Header Editing Improved header editing display in CLI CLI Fixes an EQCLI core dump in specific scenario CLI Terminal Settings Fixes an issue where the current CLI settings were destroyed in specific scenario. Page 5 of 10

6 Bug ID Description Web UI Health Check Updated tool tips for HTTP/HTTP Heath Check configuration page Web UI DDoS Fixes an issue where the drop count was not reported on the GUI plot Web UI DDoS Updated caption when there are no logs to display Web UI CLI widget Fixes an issue where the "show" command was not working Web UI Event Log Fixes an issue where the Event Log Filter pop-up window was broken Web UI Health Check Fixes an issue where the "Add Health check" pop-up appears blank in specific scenario Web UI ACL Fixes an issue where the "Access Control Lists Summary" page was broken with locales other than English (en) ACL Blacklist Fix for an issue where the show command for large ACL Blacklists was not working CPU Usage Switch port statistics logging has been disabled by default. A flag has been added to enable it for collecting debug information HTTP Header Insert Fix for an issue where a header was inserted in the wrong order for HTTP/0.9 and HTTP/1.0 client requests, which made it invalid HTTP Caching Fix for a kernel panic when HTTP caching is enabled. Page 6 of 10

7 Known Issues Read this section thoroughly before upgrading! Bug ID Description Match Rules: debug_message(), ssl2(), ssl3(), and tls1() functions (supported in Version 8) are not accepted for expressions. Clusters: The Reset on server failure global option supported in previous releases is not yet implemented in Version 10. Layer 4 UDP clusters: The persist override flag on UDP cluster server instances does not override persistence. (4101 TCP/ACV Health Checks: The CLI and Web UI will indicate that a server instance is 'ACV DOWN' (or not responding to ACV probes) even when ACV is not set, when the server is not responding to TCP probes. It should be shown as L4 TCP DOWN. In any case, the server is correctly marked down. Health Checks: In a server pool configuration, do not define more than 16 health check instances per server instance. If 17 health check instances are defined on a server instance, the system will become unresponsive and reboot. The workaround, after the system comes back up, is to remove the 17th health check from the configuration file. This bug will be fixed in a future release. VMware Integration: In a VMware configuration where Microsoft Active Directory is used, logging in to VMware from Equalizer will fail if the VMware account used to log into VMware is defined within an Active Directory domain. On VMware the login succeeds, but on Equalizer the login attempt fails. If you test the login, it will appear to hang. Messages like the following appear in the Equalizer log: vlbd[22043]: e v vcenter; : unable to send message Message too long.the workaround is to use a VMware account that is not defined within Active Directory to log into VMware. ACV Probes Require \r\n at Layer 7: In Version 8.6, Layer 7 ACV probes did not require that the user insert \r\n characters at the end of the Probe. In Version 10, the user must add these characters at the end of the probe string manually. (6497) Web UI: Cannot define an SNMP Trap server in the Web UI. The workaround is to use the CLI. Web UI: Some CLI commands are not supported by the CLI Console widget in the Web UI Dashboard. See the online WebHelp for more information. Page 7 of 10

8 Subnet destination (or policy) routes have been removed (see bug 7556, above). That feature included the ability to specify the source IP address to use for a packet routed to another network. Now, the system automatically configures destination routes, and uses the subnet IP address as the source IP address. The capability to specify a source IP address will be provided in a future release. Layer 4 TCP Clusters: The IP address and port for an FTP cluster (a TCP cluster with a start port of 21) cannot be modified. The workaround is to create a new FTP cluster. Failover: The per-subnet command flag has been moved in the CLI to a new failover context. This flag must currently be managed through the CLI. In the Web UI, this flag remains on the subnet configuration tab. Attempting to disable the flag in the Web UI appears to succeed, but if the tab is redisplayed the flag is still set on that subnet. This issue in the Web UI will be fixed in a subsequent release. Preferred static routes: If the user adds a 0/0 static route and a preferred static route for a server with the same gateway, then the preferred static route is ignored. SSL Ciphers: The following cipher is temporarily disabled for all HTTPS clusters due to reconnection issues: AES256-GCM-SHA384 Web UI Certificate: A certificate that requires a DSA (DSS) private key cannot be selected for use as the certificate for Web UI HTTPS connections. VLB Manager: VLB Managers currently do not work if an IPv6 address is specified in the manager URL. USB Drive Support: If you unplug the USB drive without unmounting it, errors of the form umass0: IOERROR" appear on the console. Manual recovery is needed when you unplug the USB drive without unmounting it and then plug it back in again. The drive will not be usable, until you manually unmount and then re-mount the USB filesystem. HTTP Cache Configuration (Web UI only): Caching cannot be enabled on a server pool until the server pool is attached to a Layer 7 cluster. The workaround is to use the CLI to enable caching on a server pool before it is attached to a cluster. Downgrading to a Version prior to f: If you downgrade from Version f or above to a release prior to Version f, and if you have Server Side Encryption (SSE) enabled on any clusters, all protocol flags for SSE will be disabled after the downgrade and SSE will be disabled. The workaround is to re-enable the protocol flags for SSE after downgrade. In the GUI, these flags are located under System > Global > Server Side Encryption. In the CLI, they are located under the sse context at the top level of the CLI. Page 8 of 10

9 EQ/OS 10 Images and Documentation This release is supported for upgrade on all LX model Equalizers and on the following GX models: E350GX, E450GX, E650GX. Note that a separate upgrade image will be provided for the E250GX. The following Coyote Point Equalizer images are available on the Fortinet Support Site: c-RELEASE.tgz c-250GX.tgz EqualizerOnDemand.zip EqualizerOnDemand-ESX.zip LX/GX Version 10 upgrade image. E250GX Version 10 upgrade image. VM Player / VM Fusion Equalizer OnDemand VM c installation image. VMware ESX Server Equalizer OnDemand VM c installation image. These images are located in the Coyote Point file download area. To download: 1. Log in to support.fortinet.com using your support account information. 2. Click on Download near the top of the Support Home Page, and choose Firmware Images from the drop-down menu. 3. In the Select Product box, choose CoyotePoint. 4. Click on the Download tab. 5. Click on Click on the HTTPS link for the image you want to download. Page 9 of 10

10 Registering Your Product Fortinet customer services (such as firmware updates and technical support) require product registration. Take a moment now to register your product at the Fortinet Customer Service and Support web site: Before you can register, you will need: 1. Access to a new or existing Support Account. Information on how to create and manage a support account is provided in the Fortinet Support Portal User Guide. If your organization already has an account, obtain the user name and password information from your local account administrator to log in. 2. The serial number of the unit you want to register. You can find this information using either the CLI or the GUI after powering up your appliance: To use the CLI, log in to the CLI (over the serial console or, if networking is configured, using SSH over an appropriately configured subnet) and enter the following CLI command: eqcli > version Record the System Serial Number from the command output. If networking is configured and the GUI has been enabled on a subnet., you can also get the serial number from the System Information widget on the GUI dashboard. The Dashboard appears automatically when you log into the GUI. Once you have obtained both the login credentials of a support account and the System Serial Number of the unit to register, do the following: 1. Log in to using the login credentials obtained above. 2. Follow the instructions provided in the Registration Frequently Asked Questions under the heading How do I register a Fortinet device?. When requested, enter the System Serial Number you obtained above into the appropriate form. Once registration is completed, the appliance serial number and other information will appear in the FortiCare Registration area. Your system is now registered. If your system can connect to the internet, you can now update the support information displayed in the CLI and GUI by doing one of the following: In the CLI, enter the following to update the support information on your unit: eqcli > forticare registration View the updated Support information (including Last refresh date, Support end, and ) by entering: eqcli > version Page 10 of 10

11 In the GUI, select the System configuration tab on the left navigational pane and then click on Global > Dashboard. The System information widget on the right pane will indicate the Support information (including Last refresh date, Support end, and ). Click on the Refresh button to update the registration information. Note that the registration information does not update automatically in either the CLI or the GUI; you must use either the CLI forticare registration command or the Refresh button in the GUI Dashboard s System Information widget to update. Page 11 of 10