Applies To:

Show Versions Show Versions

Release Note: BIG-IP GTM and BIG-IP Link Controller version 9.4.1
Release Note

Software Release Date: 06/26/2007
Updated Date: 12/11/2013

Summary:

This release note documents the version 9.4.1 feature release of the BIG-IP® Global Traffic Manager and BIG-IP® Link Controller. To review the features and fixes included in this release, see New features and fixes in this release.

For existing customers, you can apply the software upgrade to 9.2.x and later.

For information about installing the software, see Installing the software.

Note: F5 now offers both feature releases and maintenance releases. For more information on our new release policies, see Description of the F5 Networks software version number format.

Warning: This is a feature release, not a maintenance release. Unless you need specific features that are new to this feature release, please upgrade to the latest maintenance release instead.

Contents:

- User documentation for this release
- Minimum system requirements and supported browsers
- Supported platforms
- Installing the software
     - Performing a Windows hosted installation
     - Performing a USB mass storage device installation
     - Performing a local installation
     - Performing a PXE server installation
     - Performing a remote installation
     - Verifying the MD5 checksum of the installation file
     - Reactivating the license on the BIG-IP system
- New features and fixes in this release
     - New features in this release
     - Fixes in this release
- Features and fixes introduced in prior releases
     - Features introduced in version 9.4
     - Fixes introduced in version 9.4
- Known issues


User documentation for this release

In addition to these release notes, the following user documentation is relevant to this release.

You can find the product documentation and the solutions database on the AskF5 Technical Support web site.


Minimum system requirements and supported browsers

The minimum system requirements for this release are:

  • 512 MB RAM (if installed as a stand-alone Local Traffic Manager or Global Traffic Manager product)
  • 768 MB RAM (if installed as a combination of BIG-IP systems, such as a Local Traffic Manager/Global Traffic Manager installation, or as a Link Controller installation)
  • 512 MB CompactFlash® media drive

Note: The 520/540 platform must meet certain requirements in order to support this version of the BIG-IP software. For more information, including memory requirements, see 520/540 Platform: Installing BIG-IP version 9.4.1.

The supported browsers for the BIG-IP Configuration utility are:

  • Microsoft® Internet Explorer®, version 6.x
  • Mozilla® Firefox®, version 1.5x

Note that we recommend that you leave the browser cache options at the default settings.

Important: Popup blockers and other browser add-ons or plug-ins might affect the usability of the Configuration utility. If you experience issues with navigation, we recommend that you disable these types of browser plug-ins and add-ons.

[ Top ]

Supported platforms

This release supports the following platforms:

  • BIG-IP 520 and 540 (D35), for more information, see 520/540 Platform: Installing BIG-IP version 9.4.1.
  • BIG-IP 1000 (D39)
  • BIG-IP 1500 (C36)
  • BIG-IP 2400 (D44)
  • BIG-IP 3400 (C62)
  • BIG-IP 5100 and 5110 (D51)
  • BIG-IP 6400 (D63)
  • BIG-IP 6800 (D68)
  • BIG-IP 8400 (D84)
  • BIG-IP 8800 (D88)

Warning: If you plan to upgrade a system licensed for Link Controller, Global Traffic Manager, or a combination Local Traffic Manager and Global Traffic Manager system, the BIG-IP unit you intend to upgrade must have a minimum of 768 MB of RAM. Originally, the BIG-IP 1000 (D39) and BIG-IP 2400 (D44) platforms were shipped with 512 MB of memory only.

If you are unsure which platform you have, look at the sticker on the back of the chassis to find the platform number.

[ Top ]

Installing the software

There are several installation options to consider before you begin the version 9.4.1 software installation. Before you begin the installation process, you need to determine which installation option is appropriate: Windows® hosted, USB mass storage device, local, PXE server, or remote.

Warning: Version 4.5.x or 4.6.x installation. You cannot upgrade directly from BIG-IP version 4.x to 9.4.1. You must first upgrade to a 9.2.x version. For details about this installation method, see the release notes for one of the 9.2.x releases.

Warning: Version 9.0.x or 9.1.x installation. You cannot upgrade directly from BIG-IP versions 9.0.x through 9.1.x to 9.4.1. You must first upgrade to a 9.2.x version. For details about this installation method, see the release notes for one of the 9.2.x releases.

Warning: A valid service contract is required to complete this upgrade.

Warning: You must reactivate the license on the BIG-IP system you intend to upgrade before you begin the upgrade.

Important: You are prompted to install the software on multiple boot images if the unit supports the multiple boot option. The BIG-IP 1500 (C36), BIG-IP 3400 (C62), BIG-IP 6400 (D63), BIG-IP 6800 (D68), BIG-IP 8400 (D84), and BIG-IP 8800 (D88) platforms support this functionality.

Important: You must perform the installation from the management interface (Management) on the BIG-IP system.

Important: You should perform the installation on the standby system in a redundant system. If you are satisfied with the results, initiate failover and apply the upgrade to the other unit in the redundant system.

Important: Each unit in a redundant system must be running the same version of the software.

Important: We recommend that you run the MD5 checksum on any ISO image or IM upgrade file you download. For information about MD5 checksums, see Verifying the MD5 checksum of the upgrade file.

Important: If you are upgrading from 9.2.x, and you have a Global Traffic Manager unit that belongs to a sync group, you must remove the unit from the sync group before you install the software or apply the upgrade. Failure to do so may cause irrevocable damage to the units in the sync group that are running older versions of the software. Once you have upgraded all units to the same version, you can then re-create the sync group. For details on removing a unit from a sync group, see the product documentation. Once you have removed the unit from the sync group, you can proceed with the installation or upgrade. Note that this is for upgrades from 9.2.x only.

Performing a Windows hosted installation

Before performing Windows hosted installation, read the following information.

Performing a USB mass storage device installation

Before performing a USB mass storage installation, read the following information.

  • Version 9.4.1 USB mass storage device installation
    The USB mass storage device-based upgrade provides the ability to install the BIG-IP software from a USB mass storage device onto a BIG-IP system. For details about this installation method, see Installing BIG-IP version 9.4.1 from a USB Mass Storage Device.

Performing a local installation

Before performing a local installation, read the following information.

Performing a PXE server installation

The procedure for performing a PXE installation depends on the version of the BIG-IP system you area currently running, and whether you have the 520/540 platform.

Performing a remote installation

The procedure for performing a remote installation depends on the version of the BIG-IP system you area currently running.

[ Top ]

Verifying the MD5 checksum of the installation file

After you download the installation file and its associated MD5 checksum file, and before you perform the installation, we recommend you test the integrity of the installation file. This verifies that you have downloaded a good copy of the file. To run the test, type the following commands, where local-install-9.4.1.29.0.im is the name of the file you downloaded, and local-install-9.4.1.29.0.im.md5 is the name of its associated MD5 checksum file.

md5sum local-install-9.4.1.29.0.im
cat local-install-9.4.1.29.0.im.md5

If the output from both commands does not exactly match, download the file again. Repeat the download process until the MD5 checksum of the downloaded file exactly matches the text string in the associated .md5 file.

[ Top ]

Reactivating the license on the BIG-IP system

You must reactivate the license on the BIG-IP system to use some of the new features added in this release.

To reactivate the license on the system

  1. On the Main tab, expand System and click License.

    The License screen opens.
     
  2. Click the Reactivate button and follow the onscreen instructions to reactivate the license.

    For details about each screen, click the Help tab.
[ Top ]

New features and fixes in this release

This release includes the following features and fixes.

New features in this release

Important: For features that pertain to platform-related or cross-product issues, please see the release notes for Local Traffic Manager version 9.4.1.

This release includes no new features specific to Global Traffic Manager or Link Controller.

Fixes in this release

This release includes the following fixes.

[Global Traffic Manager/Link Controller] Translated virtual IP address reported as target IP address and target port 0 (CR75126)
This release corrects a problem in which the system could report the translated virtual IP address as the target IP address, and a zero ( 0 ) as the value for the translated port. Although this condition did not cause any failures in all 9.x installations, the 3-DNS Controller on versions 4.x marked these virtual servers as down.

[Global Traffic Manager/Link Controller] Global availability load balancing and switched member order (CR79808)
In previous releases, using global availability load balancing could result in incorrect member order. This release corrects this condition.

[ Top ]

Features and fixes introduced in prior releases

The current release includes the fixes and enhancements that were distributed in prior releases, as listed below. (Prior releases are listed with the most recent first.)

Features introduced in version 9.4

The 9.4 release included the following features.

Upgraded synchronization
The synchronization utility, rsync, has been upgraded from version 2.6.2 to version 2.6.8. This version takes advantage of several synchronization fixes and provides improved error messages.

Heartbeat Interval timer configuration added
You can now configure the Heartbeat Interval timer. In some scenarios, you may need to adjust the heartbeat timer to allow one system to more quickly detect the unavailability of another system. This allows available systems to more quickly compensate for unavailable ones, and to make sure that no objects time out before the system sends the next probe. You can find the Heartbeat Interval setting on the General Configuration screen of the Global Traffic Manager General Properties screen.

Fixes introduced in version 9.4

The 9.4 release contained no fixes specific to the release.

[ Top ]

Known issues

This release contains the following known issues.

[Link Controller] Enforcement of limits and cost segments (CR53442)
If you have links configured with traffic limits, or with the price type of weighting, and all links are yellow, the bandwidth continues to exceed the specified limits or cost structure. There is no workaround for this condition.

[Link Controller] Message in daemon.log (CR54443)
After configuration or upgrade, you may see the following message in daemon.log:

modprobe: modprobe - Can't locate module char-major-240

This message occurs when the system attempts FIPS driver initialization on non-FIPS systems. Because this occurs only on non-FIPS systems, this message is benign.

[Global Traffic Manager] Application status regeneration after moving virtual servers (CR56703)
The Global Traffic Manager does not regenerate the status of a distributed application when you move a virtual server from one server to another.

[Global Traffic Manager] Duplicate virtual server names for different Local Traffic Manager systems (CR57443)
If you configure the same virtual server name on two Local Traffic Manager systems, the Global Traffic Manager Virtual Server Discovery process resolves the conflict by modifying the virtual server name on one server. When a query searches for that named virtual server, the system cannot look up the virtual server by name, so it fails to return the appropriate information. You can work around this situation by renaming the virtual servers to remove duplications.

[Global Traffic Manager/Link Controller] Decimal values for link segment cost (CR57533)
If you specify a decimal number for a link segment cost, the system presents the general form error:

An error has occurred while trying to process your request.

You can work around this issue by only specifying integers for link segment cost.

[Global Traffic Manager] Differing timestamps on configuration files (CR58847)
When the timestamps on two wideip.conf files differ, running the gtmparse command can result in configuration mismatch. For example, if the /config/gtm/wideip.conf file has a date of 01/25/2006 10:00 and the /shared/wideip.conf.older has a date of 01/24/2006 10:00, when you run the command gtmparse -m -i /shared/wideip.conf.older, the system loads the configuration, but does not write the contents to /config/gtm/wideip.conf, since that file is newer. The result is a condition where the information in the file does not match the loaded configuration. To work around this issue, make sure the timestamp on the file you load is newer than the timestamp of any shared configuration files.

[Global Traffic Manager] Statistics Collection Server list contents (CR60385)
The Statistics Collection Server list on a server's Properties screen contains all of the servers that are defined in the configuration, instead of just Global Traffic Manager systems. This setting determines which Global Traffic Manager is going to probe the server, so you must select a Global Traffic Manager one.

[Link Controller] Topology Regions help (CR60579)
If a system is licensed for Link Controller, it presents an HTTP 404 error when you access the help for the Regions screen of the Topology section. Systems that are licensed for Global Traffic Manager properly present the help screen.

[Global Traffic Manager] Virtual Server Discovery and virtual server definition requirement (CR60680)
For the snmp_gtm monitor to work, you must have at least one virtual server defined. If you do not have at least one virtual server defined, the Virtual Server Discovery process halts. You can work around this issue by manually defining one virtual server before switching over to Virtual Server Discovery so that the system can discover the rest of the virtual servers.

[Global Traffic Manager] Pool order value update after pool removal (CR62940)
If you create a wide IP with more than one pool, the system makes an ordinal assignment (whether you use it or not). If you remove a pool, the remaining pools retain their ordinal assignment. The system does not reorder the pools to match the number pools. There is no workaround for this issue.

[Link Controller] Performance of 280+ wide IP addresses in the browser-based Configuration utility (CR64328)
Depending on your configuration, you might experience significant performance impact using the Show All option in the browser-based Configuration utility to show all wide IP addresses. For example, the system can take well over a minute to list 286 wide IP addresses, but only a few seconds to list 419 virtual servers.

[Global Traffic Manager] ZoneRunner restart with zero-byte configuration file (CR67325)
ZoneRunner restarts continuously if the named.conf file is zero-bytes. To work around this condition, make sure there is appropriate content in the named.conf file.

[Global Traffic Manager] Unavailable pools after assigning the none monitor (CR67580)
You can select none as the monitor for a Global Traffic Manager pool. However, selecting none results in the pool being unavailable. To work around this issue, select a monitor other than none.

[Global Traffic Manager/Link Controller] IPv6 and IPv4 addresses in the same link (CR67931)
Global Traffic Manager cannot parse link addresses that contain both IPv4 and IPv6 addresses as part of the same link. If the unit is part of a synchronization group, then the second device will not show the IPv6 address in the browser interface, though it does show in the wideip.conf file. If you make changes to the links section, the system overwrites and removes the IPv6 link address completely. You can work around this issue by adding IPv6 addresses as a separate link.

[Global Traffic Manager/Link Controller] Parent pool name reported to SNMP (CR68235)
The SNMP table, gtmPoolMemberStat, returns the parent virtual server name instead of the parent pool name. This affects only iControl and SNMP; it does not affect other functionality, and the browser interface displays the pool name correctly.

[Global Traffic Manager] No support for backslash character in email address (CR68352)
ZoneRunner does not support use of the backslash ( \ ) character to specify email addresses. When ZoneRunner adds an email address, it has to add a period in front of the at sign ( @ ). In order to include characters such as period in the name portion of email addresses, you must precede the period with a backslash. However, ZoneRunner does not currently support the backslash character. There is no workaround for this situation.

[Global Traffic Manager] Nonexistent pool name in iRules (CR68654)
When you create an iRule that uses the pool command, the system does not validate that the pool exists. You can specify an invalid pool name, and the system accepts the iRule without posting an error. You can work around this issue by ensuring that a pool exists before specifying it for use in an iRule.

[Global Traffic Manager] Virtual server status from unconnected self IP address instead of translated virtual IP address (CR68682)
When probing translated virtual IP addresses, the system can incorrectly report one or more Local Traffic Manager virtual servers as being down. This occurs because the Global Traffic Manager attempts to send a probe through an unavailable self IP address. This might happen when an unavailable or bogus self IP address is lower sequentially than an available self IP address (for example, 10.1.1.9 is lower sequentially than 10.1.1.12). If this occurs, you can try checking the self IP addresses configured for the virtual servers to make sure they are correct and available.

[Global Traffic Manager] iRule sorting order (CR68727)
Currently, the only order in which you can run iRules is alphabetical order.

[Global Traffic Manager] Differences in zone creation when creating wide IPs (CR68988)
When you create a wide IP that contains a pool, ZoneRunner creates a new zone for that wide IP. If your wide IP references only iRules, ZoneRunner does not create a new zone for that wide IP.

[Global Traffic Manager] Creating wildcard port virtual servers (CR69257)
When you create a server for the first time, and try to add a wildcard port virtual server, the system does not create the virtual server, and the system does not present an error. To work around the issue, create the server first, and then add the wildcard port virtual server.

[Global Traffic Manager/Link Controller] Connection resolution using listeners (CR69270)
When no listener exists on a particular Global Traffic Manager interface, then the DNS BIND operation resolves the connection request. If you configure a listener after a UDP connection has already been established, DNS BIND continues to resolve the connection for about five minutes or longer until the existing connection expires. Additional DNS requests in the interval serve to extend the life of the existing connection for another five minutes or longer. Note that the opposite is also true: if you delete a listener after a connection has been established, DNS BIND does not begin resolving the requests until the existing connections time out. You can work around this situation by using the command line to manually delete the connection.

[Global Traffic Manager] Duplicate zone name alert (CR70234)
When you delete a view, ZoneRunner removes the associated zones, but leaves the associated files in the /var/named/config/namedb folder. If you later create a zone with the same name, the system posts a message, similar to the following:

"01150331:3: Error creating zone zone.com., zone file /var/named/config/namedb/db.view.zone.com. already exists. zone gtm.net/IN: loaded serial 2."

To work around this situation, you must use the command line to delete the zone file first. Then you can add the previously failed zone.

[Global Traffic Manager] Deletion of views containing zones (CR70294)
ZoneRunner does not warn you that deleting a view with a zone in it also deletes the zone. There is no workaround for this condition, so you should use caution when deleting views.

[Global Traffic Manager] View deleted instead of moved (CR70508)
If you specify an invalid argument with the iControl method, View_impl::move_view, the system deletes the view. To work around this issue, only use the Configuration utility to move views.

The alertd daemon sends wrong message when status of distributed application changes (CR70822)
When the status of a distributed application changes (from available to unavailable, for example), the alertd daemon sends an incorrect SNMP trap. This issue does not affect system functionality.

[Global Traffic Manager] Virtual server status update requirements (CR71009)
If you have virtual servers with no monitors set in the Local Traffic Manager configuration, and you switch between the bigip and gateway_icmp monitors, the system reports the status for those virtual servers as down (red). To work around this issue, make sure to specify monitors for each virtual server you configure in Local Traffic Manager.

[Global Traffic Manager/Link Controller] Limiting link traffic and duplex billing (CR71075)
Limiting total link traffic fails to disable duplex billing. To work around this issue, you can manually disable duplex billing.

[Global Traffic Manager/Link Controller] gtm_add script and IPv6 addresses (CR71311)
The gtm_add script does not accept IPv6 addresses. To work around this issue, use IPv4 address formatting when running the gtm_add script.

[Global Traffic Manager] 251-character named zone limit (CR71346)
For zone files, the maximum valid number is 251 characters, because of the appended .jnl extension. Although you can create files with longer names, the system cannot open it because the file name exceeds the system limit. ZoneRunner recovers but cannot report back the error. If you create the file manually, you will receive an error indicating that the file is invalid. To work around this condition, limit the names of zone files to 251 characters or less.

[Global Traffic Manager/Link Controller] gtm_add script and parsing error reporting (CR71504)
The gtm_add script does not report any parsing errors from a newly acquired configuration. To be sure there are no errors, run the gtmparse -l command after running the gtm_add script.

[Global Traffic Manager/Link Controller] Configuration synchronization file timestamp mismatch (CR71547)
Typically, when you perform a configuration synchronization operation, the system updates the configuration file's timestamp on the receiving unit. In the case where there are no actual changes in the configuration, the timestamp is not changed on configuration file on the receiving unit. However, you may have a configuration file with a newer timestamp on the sending unit (for example, when you edit the file manually). This results in mismatched configuration file timestamps, and the synchronization process recurs without success. To work around this situation, make an actual change on either system.

[Global Traffic Manager/Link Controller] PVA acceleration impact on link throughput statistics (CR71947)
Intermittently, the system displays incorrect link throughput statistics when Packet Velocity® ASIC (PVA) acceleration is set to either assist or full.

[Global Traffic Manager] ANY queries and partial response (CR76811)
When performing an ANY query for a wide IP address-based domain name, the system returns a partial response under the following conditions: if the queried wide IP contains an IPv6-formatted pool member, and if the DNS database contains a CNAME record, which is returned only when all of the virtual servers are down. In all other cases, the responses work as expected.

[ Top ]

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)