Release Notes 2.0.2
Release Date: September 28, 2017
What's New
New in this release are HIP invitations. An administrator can now pre-license and manage HIPclients in bulk by generating HIP invitations directly in the Conductor. Users added to an invitation receive an email containing a link to download the HIPclient and activate it after installation. Configuration is then done automatically without an administrator or the user needing to change any settings manually.
Upgrade Considerations
The 2.0.2 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.2 if: | |
|---|---|
|
You want to take advantage of performance and stability increases in the 2.0.2 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.1. Additionally, 2.0.2 should be more stable than all prior releases.
Enhancements
| ID | Component | Description |
|---|---|---|
| DEV-6024 | Conductor | Updated the Conductor System Configuration dialog, improving the UI for adding static routes. |
| DEV-5943 | Conductor | In order to edit HIPswitch properties, you must be a manager in only one network where the HIPswitch is present in instead of all networks that contain the HIPswitch. |
Fixes
| ID | Component | Description |
|---|---|---|
| DEV-6240 | HIPswitch 100e | Fixed an issue where you could not add overlay routes to a HIPswitch 100e. |
| DEV-6213 | Conductor |
Fixed an issue where changing an event monitor would not update the page for other users viewing the same page in the Conductor UI. |
| DEV-6085 | HIPclient, Windows | Rebooting a HIPclient from the Conductor UI now works correctly. |
| DEV-6081 | HIPclient and HIPserver, Windows | Fixed an issue where a device running a HIPclient or HIPserver could not maintain a connection with the Conductor during device ID verification, preventing the service from starting successfully. |
| DEV-6073 | Conductor | Fixed an issue where a HIPswitch connection to the Conductor would fail if network latency was higher than 500ms. |
| DEV-6069 | HIPswitch | Fixed an issue where logging in to a HIPswitch using macinfo from the console would result in a command not found error. |
| DEV-6033 | HIPswitch | Fixed an issue where a HIPswitch firmware upgrade would fail when the HIPswitch was running in transparent mode. |
| DEV-6030 | HIPclient, Windows | Fixed an issue where uninstalling a HIPserver while the firewall is enabled resulted in the loss of the original firewall settings. |
| DEV-6015 | API | Filtering the ip parameter when performing a GET /api/v1/hipservices now works correctly and no longer returns an error 400. |
| DEV-6006 | HIPswitch, 200 Series | Fixed an issue where a HIPswitch 200 running in dual-use mode would stop passing traffic. |
| DEV-5969 | HIPserver, Windows | Enabling the firewall on Windows HIPserver 2.0 and later now works correctly. |
| DEV-5966 | Conductor | Fixed an issue where a 2.0 or later Conductor was unable to set a local device IP address on 1.12.x Windows HIPclients. |
| DEV-4758 | HIPswitch | Fixed an issue where the domain name server would not correctly provision a HIPswitch. A SRV record can now be used for provisioning. |
| DEV-4589 | HIPswitch | Fixed an issue where the Cellular menu would appear in diagnostic mode for HIPswitches with no cellular component. |
Known Issues
| ID | Component | Description |
|---|---|---|
| DEV-6268 | Conductor | Upon setting policy for an overlay where the same HIPswitch appears in multiple joined device groups, the you must also restart the IF-MAP service. |
| DEV-6226 | Conductor | Currently a fully qualified domain name cannot be used for local or peer replication addresses on an HA Conductor pair. |
| 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-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-6174 | Conductor | If a smart device group contains a HIPswitch group in its rules, any device
activated from a HIP invite will not be added to the group
automatically. Workaround: Add the device to the group manually after activation. |
| 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-6170 | Conductor | You currently cannot enable a HIPswitch to use device NAT when it is configured to run in dual-use mode. |
| 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-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-6089 | HIPclient, Windows | The Windows HIPclient and HIPserver) will not connect to a standby Conductor after HA Failover and will report as offline. |
| DEV-5857 | HIPswitch | A HIPswitch 200 diagnostic report does not display CPU temperature. |
| DEV-5832 | HIPswitch | Device NAT functionality currently does not work with layer 2 traffic. |
| DEV-5704 | HIPswitch 200e | You currently cannot upgrade a HIPswitch 200e from 2.0 to
2.0.2. Workaround: Upgrade to 2.0.1 and then upgrade to 2.0.2. |
| 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-5457 | Conductor | In the Conductor network settings, Default gateway is mislabeled as Default route. This will be fixed in a future update. |
| DEV-5448 | Conductor UI | Clicking 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 uncheck 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-5021 | HIPswitch | In some cases, a HIPswitch may factory reset if the reset button is held for
close to 5 seconds. Workaround: Don't hold the reset button for a full 5 seconds. Anything after 3 seconds should place the HIPswitch in diagnostic mode. |
| DEV-5010 | HIPswitch | A HIPswitch with a static IP does not failover between cellular/WiFi and wired
interfaces successfully. Workaround: None |
| 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 might 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. |