Release Notes 2.0.1
Release Date: August 8, 2017
The 2.0.1 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.1 if: | |
|---|---|
|
You want to take advantage of performance and stability increases in the 2.0.1 update, especially for the recently added features in 2.0:
|
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. Additionally, 2.0.1 should be more stable than all prior releases.
Upgrade Considerations
You can now upgrade directly to 2.0.1 from either 1.12.x or 2.0.
Changes and Enhancements
| ID | Component | Description |
|---|---|---|
| DEV-5549 | Conductor | One-arm mode has been renamed to dual-use mode. |
| DEV-1659 | HIPswitch | HIPswitch 100 series now supports VLAN tags. |
Fixes
| ID | Component | Resolution |
|---|---|---|
| DEV-5937 | ||
| DEV-5888 | HIPClient, HIPserver | Fixed an issue where upgrading from Windows 10 Anniversary Update to Windows 10 Creators Update could cause a HIPclient or HIPserver to revert to an unprovisioned state and require reprovisioning. |
| DEV-5802 | HIPswitch | Fixes an issue where packets originating from local devices were visible on the underlay when a HIPswitch's shared and device network gateways were configured in specific ways. |
| DEV-5788 | Conductor | You can no longer set transparent mode on a HIPswitch running in dual-use mode. |
| DEV-5776 | API | Fixed an issue where the internal_ip field in PATCH /api/v1/devices/ data structure could not be updated. |
| DEV-5733 | HIPapp-Win | Fixed an issue where in certain cases, a support bundle generated on a version 2.0 Conductor would result in a HIPswitch being unable to connect, or start going online and offline repeatedly. |
| DEV-5665 | Conductor, HIP Relay | Vouchers added containing a HIPrelay license will now display correctly in the Vouchers section of the Licensing page. |
| DEV-5663 | Conductor-SimpleConnect | Fixed an issue where a 1.12.x HIPservice could not communicate with a 2.0 HIPservice on a 2.0 Conductor. |
| DEV-5661 | Conductor UI | Fixed an issue where in rare circumstances, the Conductor may not correctly load when upgrading to 2.0. |
| DEV-5600 | Conductor | Fixed an issue where a HIPswitch in dual-use mode would not display traffic stats on the page. |
| DEV-5568 | Conductor | Fixed an issue where a HIPswitch HA pair could not build tunnels via relays to other peer HIP Services. |
| DEV-5546 | Conductor UI | Fixed an issue where would fail on the active secondary HIPswitch in an HA pair. |
| DEV-5535 | HIPswitch |
Fixed an issue where in rare cases, the identity data for a HIPswitch in the database was different from the data on the HIPswitch, preventing the HIPswitch from communicating with the Conductor. |
| DEV-5533 | HIPswitch | Fixed an issue where in rare cases, configuring a HIPswitch could result in corrupt policy metadata, causing the HIPswitch to disconnect and reconnect to IF-MAP repeatedly. |
| DEV-5532 | HIPswitch | Fixed an issue where upgrading a HIPswitch while in transparent mode would fail. |
| DEV-5528 | HIPswitch | Fixed an issue preventing you from enabling transparent mode for a HIPswitch 200 running 2.0. |
| DEV-5487 | Conductor UI | Fixed an issue where you could not move objects on the network visualization graph if you selected Restore positions. |
| DEV-5469 | Conductor UI | In the Conductor UI, Ping single IP address now works correctly. |
| DEV-4733 | HIPswitch | Fixed an issue where in some cases, a factory reset of a HIPswitch 100e would cause port 1 to disappear. |
| DEV-4514 | Conductor | Fixed an issue where devices would continue to appear in the Conductor user interface after a HIPswitch was factory reset |
| DEV-4494 | Conductor | Fixed an issue where rebooting HIPswitches via the HIPswitch group reboot menu did not correctly display them as offline. |
| DEV-4292 | Conductor, Cloud | Fixed an issue where cloud provider credentials entered in the Conductor could be seen by all administrators. |
| DEV-4028 | API | Fixed an issue where making a POST call to /api/v1/people, the role attribute is set to viewer regardless of the role specified. |
| DEV-2022 | Conductor | Fixed an issue where the Conductor UI would not return to the Dashboard after the configuration completes on two Conductors in an HA-pair. |
Known Issues
| ID | Component | Description |
|---|---|---|
| DEV-5832 | HIPswitch | Device NAT functionality 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 | Occasionally, the Conductor UI will not display the recent activity of a local
device correctly. 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 setings 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 UUID data instead of object names when generating a PCI
report from Workaround: You will need to make API calls to the Conductor in order to capture the object data. |
| 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. |