HyperFlash for HyperIP®

This document contains the latest updates and issues regarding HyperIP version 5.4.6
The latest release of HyperIP is version 5.5
(Updated July 14, 2008)

Release 5.4.6 is available for download from:

ftp://ftp.netex.com/downloads/hyperip/hyperip-5.4.6.nex 

(set your anonymous login password to your email address - instructions can be found at: FTP tips). 

 Click to see Instructions for De-installation of HyperIP appliances.

Critical Update Required

#1505:  Expired license may cause many error messages to fill logs to the point that HyperIP becomes non-operational; especially vulnerable is a powered-up spare unit.

Fix: install the required critical update (see NOTICE).

Outstanding issues/problems

#769:  If a memory stick or other USB device is plugged into a USB slot when a reboot is done, boot will be attempted from the memory stick (Boot may halt while writing the 'LILO' prompt to the console). 

Workaround: remove USB device before reboot. (see NOTICE below).

#1013, 1057: Email messages from graphing cron process when the HIP MIB is unavailable or a statistics counter wraps.

Workaround: deconfigure email notification, or Restart Force, or Reboot. 

#1174: ssh connections may hang and/or sshd may go away on Restart Force.  If done from the dialog, the appliance may hang.

Workaround: use the web or telnet when doing Restart Force. 

#1313: Internal connection blocks may not be released at failed connection close (in proxy mode). This may be related to a situation in which SRDF links receive errors and cannot re-establish.

Fix: a bugfix release for this issue only is available for download here

#1330: Various changes are needed in timezone files, including DST change in USA starting in 2007.

Fix: Download and install this update file just as you would for a new software release.

#1360: when de-configuring the management port (changing to 'common' in the dialog interface), it is possible to lock yourself out from all network access. The dialog may do this without querying whether or not to implement changes.

Workaround: Ensure firewall settings allow telnet and/or ssh access via the common (data) interface and the default route is correct before deconfiguring the management interface. 

#1433, 1434: bandwidth limit may not be set below 1000 Kbps (1 Mbps). HyperIP status shows rates < 1 Mbps as zero.

Workaround: a bugfix for this issue only is available for download here

#1523:  When an appliance is running with no valid key installed for a long period of time (greater than 1 year), the system generates and keeps unnecessary files which fill up the system resources.
Fix: a bugfix release for this issue only is available for download here and should be put on all appliances, but especially on 'hot' spares. If you can not attach to your hot spare units, contact Netex support.

Problems/Issues fixed in 5.4.6

#381: Illegal combinations of interface speed and duplexing are allowed by the web interface.

Fix: speed/duplex combined into a single selection option.

#866, 1047, 1072: Adaptive compression percentage is not changable by users.

Fix: added HyperIP configuration parameter to set this.

#844: Customer request for privacy statement for all user accesses.

Fix: added initial web page with statement.

#877: Enhancements to hipstatus requested:  add average write size, reformat proxy connection display, assure status is written to the log every hour.

Fix: hipstatus enhanced.

#885, 1013, 1027, 1028: HyperIP fails and may hang when taking a core dump due to pthread memory corruption.

Fix: Code corrected.

#914, 1048: AHS unit bounces between MASTER and BACKUP.

Fix: KAD priorities adjusted to avoid this condition.

#912, 991 , 999: If using the serial port to configure security settings, the dialog may hang in the middle of the change and leave the machine in a state such that any further configuration changes will not complete without also hanging.
Fix:  Code corrected.

#1021: NetApps traceroute doesn't work through HyperIP.

Fix: Code corrected for zero checksum traceroute.

#1029: System logs get very large and difficult to view.

Fix: Rotate logs daily and retain more cycles.

#1046: HyperIP output data graph indicates no data in a non-AHS configuration.

Fix: Code corrected when adding session counters.

#1064: During reboot, the web navigation frame is reloaded with an unreadable loss-of-connection message.

Fix: replace nav frame with "rebooting" or "halting" text that doesn't reload automatically.

#1077: Transfer of dump to memory stick from web fails.

Fix: Code corrected to pass correct variable.

#1080: When bandwidth limit is reset to zero (e.g. override rule deleted), the max transfer rate is set to zero.

Fix: if rate is being set to 0, set it to initial rate of session.

Problems/Issues fixed in 5.4.5

#824: running bi-directional Segment Size Tests, HyperIP fails and active connections stop. 

Workaround: HyperIP failover to backup occurs if configured for AHS, and HyperIP software restarts automatically.

Fix: Locking code added to avoid using released data areas.

#828:  It is difficult to relate 'Trap 7' SNMP alert (session established) with a specific 'Trap 8' SNMP alert (session terminated).

Workaround: none

Fix: Trap message text added to associate the established & terminated messages.

#848:  No way to cancel segment size test. Clicking 'STOP' or 'EXIT' on your browser may allow you to go on to other commands.  The test continues to attempt communication with the remote HyperIP.

Workaround: none

Fix: Added 'Kill Segtest' function on web.  The test runs in background & results must be requested.

#879:  Compile error using 3rd party compiler SNMPc on HYPERIP-MIB.

Workaround: new HYPERIP-MIB.txt is on our support site.  download it and compile on your SNMP client system.

Fix: new MIB is in the release.

#885:  Traffic stops flowing but no failover occurs, and management communication to the HyperIP is unavailable.

Workaround: Power appliance off, then on.

Fix: Corrected memory management problems with connection termination.

#889:  UDP flows show forever in connection display, when the remote HyperIP resources are unavailable.

Workaround: Restart Force or Reboot.

Fix: Changed to release the outstanding resources.

Problems/Issues fixed in 5.4.4

#854,861:  Problems converting data interface between fibre & copper.

Workaround: Restart Force or Reboot

Fix: Delay firewall change until reboot.

Problems/Issues fixed in 5.4

#714:  Performance lower than expected with large variances in measured round-trip times.

#717:  With many active TCP connections, status display may be truncated.
#784:  Displayed connection byte counts can go negative.
#798:  NetBackup using iSCSI proxy mode does not connect via HyperIP.
#805:  Multiple TCP connections can be established using the same port. 
#806, 807, 825:  Problems reconnecting after failover: No active routes, invalid ARP table entries, with Spanning Tree protocol.

NOTICES

  • the only USB device supported on HyperIP units is a memory stick and ONLY for file upload/download as implemented by the serial port & ethernet user interface.
  • Proxy mode must be supported and configured on both the local and remote HyperIP appliances for the proxy mode to function properly.
  • Alternative UDP port (other than 3919) must be supported and configured on both the local and remote HyperIP appliances for HyperIP to function properly.
  • If host routing is not set up correctly, HyperIP will not intercept traffic although TCP connections may be established, bypassing HyperIP acceleration. A “Display HyperIP State” command will show the NetEx/IP sessions connected, but no TCP connections will be shown. This situation was recently observed at a US field trial, where the routing was correct on the local end, but not the remote. So, if the local end attempted a connection, it could not connect. If the remote end attempted a connection, the connection was established, but data was not accelerated by HyperIP, but simply forwarded.

  • For AHS configurations, if your network is running spanning tree routing protocol, you should configure the port where HyperIP appliances are connected to 'PortFast' to avoid failover bouncing due to the lack of communication between the AHS pairs.
  • If you have configured separate management and data network interfaces on a HyperIP appliance:
    - For ARP to work correctly, the network interfaces must be in different ethernet broadcast domains.
    - For routing to work correctly, the network interfaces must be in different IP subnets.
  • For statements regarding RoHS compliance for the country of China, click these links for the chassis and motherboard.
  •