Release Notes 2.0.3
Release Date: December 11, 2017
What's New
The 2.0.3 release is a small incremental update that includes all hotfixes from prior releases and addresses all known support cases at the time of release.
Upgrade Considerations
The 2.0.3 release includes all hotfixes from prior releases and addresses all known support cases at the time of release.
| We recommend you upgrade to 2.0.3 if: | |
|---|---|
|
You want to take advantage of performance and stability increases in the 2.0.3 update, especially for the recently added features in 2.0 and above:
|
You were impacted by any issues discovered in prior releases, especially if you have any of the following:
|
Extensive testing was conducted both in-house and with selected development partners, in lab and in production environments to ensure that performance is equivalent to 2.0.2. Additionally, 2.0.3 should be more stable than all prior releases.
Fixes
| ID | Component | Description |
|---|---|---|
| DEV-6872 | HIPswitch | Improved how a HIPswitch manages port configuration changes by attempting to validate the new configuration and reverting to the previous configuration if the Conductor is unavailable. |
| DEV-6737 | Conductor | Fixed an issue where the Blink LED option on the page did not work correctly. |
| DEV-6709 | Conductor | Fixed an issue where a notification would return 500 Internal Server Error. |
| DEV-6654 | Conductor | Fixed an issue where a HIPswitch no longer reports traffic stats until the HIPswitch was rebooted in cases where the HIPswitch was deleted and then came back online. |
| DEV-6513 | HIPserver, Windows | Fixed an issue where the HIPserver running on Windows 2012 R2 would stop responding. |
| DEV-6338 | BaseOS | Fixes dnsmasq security issues for DHCP and diagnostic mode:
|
| DEV-6293 | HIPswitch-Cellular | Fixed an issue where HIPswitches would go off-line if non-standard characters were used in the HIPswitch name. |
| DEV-6286 | HIPswitch | Fixed a bug where disabling Allow Pings on the page would not immediately block incoming pings. |
| DEV-6282 | HIPswitch, HA | Fixed an issue where promoting a secondary HIPswitch to primary could cause the HIPswitch to lose the secondary IP address. |
| DEV-6268, DEV-6630 | Conductor | Fixed an issue setting policy for an overlay where the same HIPswitch appears in multiple joined device groups, requiring a restart of the IF-MAP service. |
| DEV-6181 | Conductor UI | Static route entries in the Conductor have been updated with additional validation and clearer messaging. |
| DEV-6174 | Conductor | A Smart Device Group monitoring a HIPswitch group now correctly adds devices activated from a HIP invite. |
| DEV-5857 | HIPswitch | Fixed an issue where a HIPswitch 200 diagnostic report would not display CPU temperature. |
| DEV-5531 | API | Fixed an issue where a read-only administrator could reboot a HIPservice from the Try it Out! section in the API docs. |
Known Issues
| ID | Component | Description |
|---|---|---|
| DEV-6928 | HIPswitch | The LCD panel on HIPswitch hardware continues to display Diagnostic Mode when restarting the HIPswitch. This will be fixed in a later release. |
| DEV-6927 | Diagnostic mode | A Conductor using non-standard port configurations may not respond to a ping once ports have been changed. Browser access to the diagnostic mode UI on port 1 is not affected. |
| DEV-6919 | Conductor | A HIPservice Smart Device Group device matching rule displays null (ID) when the HIPservice does not have a name. |
| DEV-6913 | Diagnostic mode | Performing a factory reset on a HIPswitch 500 in diagnostic mode occasionally
does not clear IP and Conductor addresses. Workaround: Use the reset button on the front of the HIPswitch 500 to perform a factory reset. |
| DEV-6912 | Conductor | HIPswitches using AES-128 encryption cannot communicate with peers when the ESP transform is set to SHA-256 in the Conductor advanced settings. The option to use AES-128 will be removed in a later release. |
| DEV-6894 | Conductor | The creation of event monitors and actions are not added to the PCI User Activities Report. |
| DEV-6888 | Conductor | In the Conductor UI, port assignments for the HIPswitch 500 are not sorted correctly when expansion modules are in place. |
| DEV-6887 | Conductor | The creation of a HIPrelay rule is not added to the PCI User Activities Report. |
| DEV-6882 | HIPswitch 500 | The SFP+ expansion module for the HIPswitch 500 does not display port
assignments correctly in diagnostic mode. Workaround: Use the Conductor to configure and manage HIPswitch 500 expansion modules. |
| DEV-6881 | HIPswitch, Conductor | The LCD panels in the HIPswitch 500 and Conductor-500 are 16-characters wide. Messages are currently formatted for a 20-character LCD screen and may be truncated or display on more than one line. This will be fixed in a later release. |
| DEV-6879, DEV-6883 | HIPswitch, Conductor | The diagnostic mode ping function is currently not functional. |
| DEV-6226 | Conductor | Currently a fully qualified domain name cannot be used for local or peer replication addresses on an HA Conductor pair. |
| DEV-6195 | Conductor | The Conductor incorrectly displays an option to check bandwidth for HIPclients in diagnostic view. This option is not supported for HIPclients and will not function correctly if selected. |
| DEV-6196 | Conductor | When configuring the Conductor URL in diagnostic mode, you are able to enter an invalid IP address without receiving an error message. This will be fixed in a later release. |
| DEV-6172 | Conductor | When assigning a 1.x.x.x local device IP address to a HIPclient, the Conductor may continue to display the previous IP of the device. |
| DEV-6155 | Conductor, HIPswitch | If you add HIPswitches using different encryptions (AES-256 and AES-256 with
GCM) to an overlay, they cannot communicate with each other. Workaround: Configure any HIPswitches you want to use in the same overlay to use the same default encryption. |
| DEV-6089 | HIPclient, Windows | The Windows HIPclient and HIPserver will not connect to a standby Conductor after HA Failover and will report as offline. |
| DEV-6130 | HIPclient, Windows | Setting or removing a Local Device IP on a Windows HIPclient may cause the
client to report that the HIPservice is not running. Workaround: Restart the HIPclient to resolve the issue. |
| DEV-5832, DEV-5673 | HIPswitch | Device NAT functionality currently does not work with layer 2 traffic. |
| DEV-5530, DEV-5441 | Conductor UI | In some cases, Allow incoming pings (ICMP) and
SYN Flood Protection on the Firewall
page may be disabled and won't toggle. Workaround: Refresh your browser to resolve the issue. |
| DEV-5529 | HIPswitch | If you add an invalid overlay route to a HIPswitch from the Conductor UI, the
route will not be created on the HIPswitch and you will not receive a warning.
Workaround: None |
| DEV-5526 | Conductor UI | The Conductor will show devices that become active in real-time, but the UI
does not detect when active devices become inactive. Workaround: Refresh your browser |
| DEV-5448 | Conductor UI | Clicking the HA Edit Settings followed by the
Swap Roles button for a secondary HA-paired HIPswitch will
cause the UI to stop responding. Workaround: Refresh your browser. |
| DEV-5434 | Conductor UI | Clicking Detect Devices repeatedly on the HIPswitch
properties page will generate excess traffic. Workaround: Give the Conductor time to complete the operation. |
| DEV-5430 | Conductor | After configuring a Conductor for the first time, you may receive a
Lost connection to the original server message if you
select Return to settings too quickly. Workaround. Wait at least 20 seconds before selecting Return to settings. |
| DEV-5428 | Conductor UI | When you create a SDG with Ignore auto-discovered devices until
accepted checked, then unchecked after creation, the SDG will not pick
up non-accepted devices. Workaround: None |
| DEV-5368 | Conductor UI | Import devices has been removed from 2.0 and later. An improved version of the
feature will be added in a future update. Workaround: Tempered Networks Support can provide a tool enabling you to import a CSV, if required. |
| DEV-5343 | Conductor UI | If you try and log in after your session has timed out, you may receive the
following error: The change you wanted was rejected. Workaround: Refresh your browser and log in. |
| DEV-5008 | PCI Reporting | PCI Reporting shows the UUID reference instead of the name when generating a
PCI report from Workaround: To view names, you can download object references from the same page where you generated the PCI report. |
| DEV-4846 | HIPswitch | If a HIPswitch is in port dual-use mode and device discovery is enabled, the
HIPswitch will report an error. Workaround: None |
| DEV-4573 | Conductor | Cloud HIPswitches may not display the correct icon in the user interface if
they are on firmware version 1.12.3 or below. Workaround: None. |
| DEV-4537 | Conductor | When demoting a master Conductor to standby, the processing screen may not
correctly update. Workaround: Refresh your browser. |
| DEV-4188 | HIPswitch (Cellular) | In the Graphs section of the Reporting tab, several graphs are available to older HIPswitch 200g models with an Option Cellular card that are not applicable, such as LTE, CDMA, Cell temperature, etc. These graphs will not display data. |
| DEV-2417 | Conductor UI | The password reset email link defaults to the first web enabled interface, and
will be successful only if an administrator configures the first interface with a
publicly-facing default route. Workaround: None. |
| DEV-1994 | HIPswitch | When modifying an existing serial over IP configuration, you must reboot the HIPswitch to apply the new configuration settings. |