HyperFlash for HyperIP®

This document contains the latest updates and issues regarding HyperIP
(Updated July 14, 2008)

Release 5.5 is an upgrade kit, available by contacting support@netex.com

Because of the extent of this upgrade, for existing customers, this release is only available via an upgrade kit (harddrive replacement) or via appliance exchange/refresh.

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

Issue: With the release of HyperIP 5.5, the currently supported versions of HyperIP are 5.4.6 and later. If you are running an older version please upgrade ASAP to continue to receive support from Network Executive Software, Inc.

Fix: install a supported version (upgrade to 5.5 or 5.4.6).

Outstanding Issues in 5.5

#1833: If you need to change your local site ID, you must halt all sites and delete all sites before doing so. Then when you are finished configuring the sites again, you must perform a Restart Force.
#1835: If you are running with large number of application connections and experience HyperIP outages, you may need to explicitly set the maximum connection limit to a lower value.
#1838: Changing the NetEx UDP port requires HyperIP to be restarted, as well as a firewall restart so that the proper port is accepted through the firewall.
#1853: If you need to set the other (alternate) partition to boot next and do not wish to specify a new configuration file, you will need to use the command line interface; the web interface requires a configuration file to be specified.

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.

Issues & Workarounds for 5.4.6

#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 (5.4.6): install the required critical update (see NOTICE).

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

Workaround (5.4.6): 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 (5.4.6): 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 (5.4.6): 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 (5.4.6): 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 (5.4.6): 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. 

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

Workaround (5.4.6): 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 (5.4.6): 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 adressed 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.

See hyperipHistory.html

NOTICES

  • Poorly configured HyperIP sessions (i.e. small segments) may result in overdriving local interface. This can be observed as excessive retransmits.
  • The 'enable/disable' state of intercepts does not persist when HyperIP is restarted. All intercepts are applied upon startup.
  • 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. The memory stick must contain only a single partition.
  • 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.

©2008 Network Executive Software, Inc. All rights reserved.

NetEx is a registered trademark; NetEx/IP and HyperIP are trademarks of NetEx.

All other trademarks herein are the property of their respective owners.