Hotfixes

Please follow the links below to download the hotfix for your platform.

2.1.x Series

Download Applies to: Date Behavior Resolution
Hotfix 8551 HIPswitch 250 Series running version 2.1.3 August 23, 2018 HIPswitch repeatedly connects and disconnects. See Product Bulletin 201808B-001 for more information. Apply Hotfix 8551 to resolve the issue.
Hotfix 8543 HIPswitch 100 Series running version 2.1.3 August 23, 2018 HIPswitch repeatedly connects and disconnects. See Product Bulletin 201808B-001 for more information. Apply Hotfix 8543 to resolve the issue.
Hotfix 7414 2.1.2 virtual HIPswitches running in VMware ESXi March 15, 2018 VMware reports 100% CPU usage when running a 2.1.2 virtual HIPswitch Apply Hotfix 7414 to resolve the issue.

2.0.x Series

Download Applies to: Date Behavior Resolution
Hotfix 6933 All HIPswitches running 2.0.3 December 14, 2017 HIPswitches running 2.0.3 cannot enable serial-over-IP. Apply Hotfix 6933 to enable serial-over-IP on HIPswitches running 2.0.3.
Hotfix 5661 All Conductors running 1.12.0 to 1.12.3 June 23, 2017 In rare circumstances, the Conductor may not correctly load when upgrading to 2.0.0. Apply Hotfix 5661 to the Conductor in diagnostic mode to restore connectivity.

1.12.x Series

Download Applies to: Date Behavior Resolution
Hotfix 4837 All HIPswitches running 1.12.4 March 6, 2017 HIPswitches now use spanning tree protocol (STP) on device network ports. Apply Hotfix 4837 to disable STP for device network ports.
Hotfix 4733 HIPswitch 100e running 1.12 March 27, 2017 Under certain conditions, performing a factory reset on a HIPswitch 100e may cause port 1 to become unavailable.

Apply Hotfix 4733 to resolve the issue.

Note: You must place the HIPswitch in diagnostic mode to apply this hotfix.
Hotfix 4107 Conductor running 1.12.2 September 30, 2016 Changes to firewall settings (Local Devices -> Firewall) do not display correctly in the Conductor UI. Apply Hotfix 4107 to resolve the issue.
Hotfix 3721 Conductor running 1.12.1 July 13, 2016
This hotfix addresses two issues:
  • Under certain high-load conditions, the Conductor may use an excessive amount of memory.
  • In rare cases IF-MAP server (ompad) logs an excessive number of SSL_ERROR_SYSCALL entries causing 100% CPU usage and filling all available space on the data disk.

Apply Hotfix 3721 to resolve both issues.
Deprecated: See Hotfix 3721 Conductor running 1.12.1 July 5, 2016 In rare cases IF-MAP server (ompad) logs an excessive number of SSL_ERROR_SYSCALL entries causing 100% CPU usage and filling all available space on the data disk. Apply Hotfix 3715 to resolve the issue.

Hotfix 3707 - HIPswitch ramips (100g and 100e HIPswitches)

Hotfix 3707 - HIPswitch cns3xxx (All 200-series HIPswitches)

Hotfix 3707 - HIPswitch x86_64 (100v, 100rc, all 300-series and 400-series HIPswitches)

 All physical HIPswitch platforms running 1.12.1 June 30, 2016 Firewall blocks traffic when a HIPswitch is in transparent mode, causing it to become unresponsive.

Apply Hotfix 3707 to resolve the issue.

If your HIPswitch is already affected by the issue, do the following:

  1. In the Conductor, turn off transparent mode, returning the HIPswitch to protected mode
  2. Restart the HIPswitch
  3. After the HIPswitch is back online, apply the hotfix

You can then enable transparent mode for the HIPswitch.

1.11.x Series

Download Applies to: Date Behavior Resolution

Hotfix 4286

 HIPswitch 100g platforms running 1.11.3 only November 15, 2016 The HIPswitch 100g may lose network connectivity, and become unable to manage overlay network traffic or communicate with Conductor. The fix resolves a firmware issue specific to the HIPswitch 100g cellular card. With the fix in place, the cellular card functions normally, and HIPswitch connectivity is maintained.
Note: This hotfix is permanently addressed in firmware 1.12.1 and above. We recommend considering upgrading to the latest release level to address this and other recently fixed issues.

Hotfix 2861

 Conductors with firmware versions 1.11.0, 1.11.1, 1.11.2, and 1.11.3 March 8, 2016 Adding a device to an overlay network with the same IP used by another device in a different overlay network will result in an error. Additionally, upgrading a Conductor running 1.10 or below to 1.11 with devices using the same IP address will cause the upgrade to fail. This hotfix removes the restriction and allows devices to use the same IP address in different overlay networks.

Hotfix 2794 Downloads

100-series (2nd Generation)
200-series
300-series
400-series
Siemens RuggedCom
 All HIPswitch platforms running 1.11.3 only February 24, 2016 In HIPswitch HA deployments with more than (approximately) 100 devices, failover/failback is unsuccessful, and there is potential loss of overlay network connectivity. The fix resolves potential HA heartbeat starvation and route management problems on HIPswitches that are part of overlay networks with very large numbers of devices (approximately 100 devices or more). Under certain conditions in these configurations, failover/failback device route creation on the standby was failing, and device traffic was not resuming as normal.

Hotfix 2774

 Conductor platforms running 1.11.3 only February 24, 2016 The data partition on Conductors in HA configurations may grow over time and potentially fill the Conductor hard disk completely. The fix resolves an issue where the HA data replication accumulates files over time, eventually filling the Conductor disk completely if the administrator remains unaware. In some cases, the issue also causes long sync times when pairing two Conductors in an HA configuration.