Release Notes 1.12.6

Release Date: September 5, 2017

The 1.12.6 release is a small incremental update that includes all hotfixes from prior releases and addresses all known support cases at the time of release.

We recommend you upgrade to 1.12.6 if you were impacted by any issues fixed in this release.

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 1.12.5. Additionally, 1.12.6 should be more stable than all prior 1.12.x releases.

Upgrade Considerations

If you are upgrading from a prior release you should review the following information:
  • A HIPswitch running 1.11 can only be updated to 1.12 with a Conductor running 1.12 or higher. Update your Conductor before updating your HIPswitches from 1.11.
  • If you are upgrading to 2.0 from a release prior to 1.12.6, you should upgrade to 1.12.6 first, then proceed with the upgrade to 2.0. This step is not required for upgrades to 2.0.1 or above.

Fixes

ID Component Resolution
DEV-6061 HIPclient, HIPserver Fixed an issue where enabling the Windows firewall in the Conductor for a HIPclient or HIPserver would not enable the firewall.
DEV-5991 HIPclient Fixed an issue where device ID verification may fail preventing the HIP service from starting successfully.
DEV-5960 Conductor Fixes an issue where logging in to a Conductor using macinfo from the console would result in a command not found error .
Note: This issue exists for HIPswitches and will be fixed in a future release.
DEV-5951, DEV-5888 HIPClient, HIPserver Fixes 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-5903 HIPswitch Fixes an issue that could cause a firmware update to fail on systems that were running for an extended period of time.
DEV-5901 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-5900 HIPswitch Fixes an issue when upgrading a HIPswitch that may cause it to go offline and never come back online.

Known Issues

ID Component Description
DEV-6068 HIPserver If the Windows firewall is enabled for a HIPserver, the HIPserver may not uninstall correctly, leaving the HIPserver firewall rules on Windows Server.

Workaround: None

DEV-6005 Conductor, AWS When creating a new subnet, it is not explicitly associated with a route table, which can cause the subnet to incorrectly associate with the main route table for the virtual private cloud.
Workaround:
  1. After creating a subnet in AWS, create a new route table
  2. Navigate to Route Table > Edit > Subnet Associations
  3. Click Edit
  4. In the Associate field column, select the desired subnet
  5. Click Save
DEV-5960 HIPswitch Logging in to a HIPswitch from the console using macinfo will result in a command not found error.
Note: This issue was fixed for the Conductor in this release.

Workaround: None.

DEV-5010 HIPswitch If a static IP is configured on a HIPswitch, failover between cellular or WiFi to a wired connection does not complete successfully.
DEV-4588 Conductor When configuring a standby HA Conductor, the list of firmware updates present in the system on the standby might not necessarily be available if promoted to be the master.
DEV-4581 Conductor Configuring a standby HA Conductor may take a significant amount of time.
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.
DEV-4537 Conductor When demoting a master Conductor to standby, the processing screen might not correctly update.

Workaround: Refresh your browser.

DEV-4535 Conductor When upgrading an HA-paired standby Conductor, the Return to Dashboard link is shown prematurely. Clicking the link results in a broken link page.

Workaround: Wait a few minutes and refresh your browser.

DEV-4514 Conductor After a HIPswitch is factory reset, its devices may still appear in the Conductor user interface.

Workaround: Refresh your browser.

DEV-4494 Conductor Rebooting HIPswitches from the group Reboot menu may not display their offline status correctly.
DEV-4493 Conductor When using the Conductor user interface, a browser JavaScript exception may cause the interface to function incorrectly. If this occurs, click the refresh button in your browser.
DEV-4418 Conductor UI HIPswitch 100 series units do not support specifying VLAN tags in the Port assignment view. Additionally, you cannot specify an MTU in excess of 1500.
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-4170 Conductor UI The Shared throughput and Overlay throughput graphs in the Graphs section of the Reporting tab may show a drop in traffic after a HIPswitch is rebooted until the next collection interval occurs.
DEV-4028 API When making a POST call to /api/v1/people, the role attribute is set to viewer regardless of the role specified.
DEV-3342 Conductor When configuring a HIPswitch, the firewall settings page may become unresponsive.

Workaround: Refresh the browser and try the operation again.

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.
DEV-1994 HIPswitch When modifying an existing Serial over IP configuration, you must reboot the HIPswitch to apply the new configuration settings.