Applies To:

Show Versions Show Versions

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

Updated Date: 09/29/2011

Summary:

This release note documents the version 9.4.7 release of BIG-IP® Global Traffic Manager and BIG-IP® Link Controller. We recommend this general sustaining release only for those customers who want the fixes listed in New features and fixes in this release. For existing customers, you can apply the software upgrade to version 9.2.x, 9.3.x, or 9.4.x. For information about installing the software, refer to Installing the software.

Note: F5 offers general availability releases and general sustaining releases. For detailed information on our policies, refer to Solution 8986, F5 software lifecycle policy, which is available in the AskF5SM Knowledge Base, http://support.f5.com.

Contents:

- User documentation for this release
- Minimum system requirements and supported browsers
- Supported platforms
- Installing the software
     - Performing a USB thumb drive installation
     - Performing a local installation
     - Performing a PXE server installation
     - Performing a remote installation
- New and fixed in this release
     - New in version 9.4.7
     - Fixed in version 9.4.7
- New and fixed in prior releases
     - New in version 9.4.6
     - Fixed in version 9.4.6
     - New in version 9.4.5
     - Fixed in version 9.4.5
     - New in version 9.4.4
     - Fixed in version 9.4.4
     - New in version 9.4.3
     - Fixed in version 9.4.3
     - New in version 9.4.2
     - Fixed in version 9.4.2
     - New in version 9.4.1
     - Fixed in version 9.4.1
     - New in version 9.4
     - Fixed in version 9.4
- Known issues
- Contacting F5 Networks

[ Top ]

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 in the AskF5 Knowledge Base.


Minimum system requirements and supported browsers

The minimum system requirements for this release are:

  • 512 MB RAM (if running only Local Traffic Manager or only Global Traffic Manager)
  • 768 MB RAM (if running a combination of BIG-IP products, such as Local Traffic Manager and Global Traffic Manager, or running Link Controller)
  • 512 MB CompactFlash® media drive

Note: We recommend installing Global Traffic Manager or Link Controller on the hard drives of BIG-IP systems. Although installation on CompactFlash® drives is supported in most cases, it is not recommended.

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 the BIG-IP software.

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 only 512 MB of memory.

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

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

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 browser-based 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 the BIG-IP software.
  • BIG-IP 1500 (C36)
  • BIG-IP 1600 (C102)
  • BIG-IP 2400 (D44)
  • BIG-IP 3400 (C62)
  • BIG-IP 3410 (C100)
  • BIG-IP 3600 (C103)
  • BIG-IP 5100 and 5110 (D51)
  • BIG-IP 6400 (D63)
  • BIG-IP 6800 (D68)
  • BIG-IP 6900 (D104)
  • BIG-IP 8400 (D84)
  • BIG-IP 8800 (D88)
  • BIG-IP 8900 (D106)

Note: We recommend installing Global Traffic Manager or Link Controller on the hard drives of BIG-IP systems. Although installation on CompactFlash® drives is supported, it is not recommended.

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

Note: If you want to revert from version 10.x to 9.x, see SOL9745: Reverting BIG-IP version 10.x disk formatting (LVM) to version 9.x disk partitions.

[ Top ]

Installing the software

There are several installation options to consider before you begin the software installation. Before you begin the installation process, you need to determine which installation option is appropriate: USB thumb drive, local, PXE server, or remote.

Warning: Version 4.5.x or 4.6.x installation. You cannot upgrade directly to this version from BIG-IP version 4.x. You must first upgrade to version 9.2.x, or an earlier version of 9.3.x or 9.4.x. For details about these installation methods, see the release notes for the associated release.

Warning: Version 9.0.x or 9.1.x installation. You cannot upgrade directly to this version from BIG-IP versions 9.0.x through 9.1.x. You must first upgrade to version 9.2.x, or an earlier version of 9.3.x or 9.4.x. For details about these installation methods, see the release notes for the associated release.

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 installation. This is because the license check date in the software is verified against the service check date in the license file. For more information, see SOL7727: License activation may be required prior to software upgrade.

Warning: Once you reactivate the license, make sure to save your configuration. The system does not roll forward unsaved portions of configurations. You can save your configuration by running the command b config save /config.ucs.

Warning: Once you save your configuration, copy the config.ucs file to a secure, remote location. The installation process overwrites the locally maintained UCS file, so you should maintain the UCS file remotely as a recovery strategy in case the upgrade does not perform as you expect. For more information, see SOL2250: Overview of UCS archives.

Warning: You must turn off mirroring before you attempt to upgrade. Mirroring between units with differing versions of the BIG-IP software is not supported.

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 1600 (C102), BIG-IP 3400 (C62), BIG-IP 3410 (C100), BIG-IP 3600 (C103), BIG-IP 6400 (D63), BIG-IP 6800 (D68), BIG-IP 6900 (D104), BIG-IP 8400 (D84), BIG-IP 8800 (D88), and BIG-IP 8900 (D106) platforms support this functionality.

Important: This installer is capable of automatically generating UCS files at install-time. Installations of 9.4.2 and later generate UCS files, if there is not one already present in the root directory, as /config.ucs. In order to roll-forward a pre-9.4.2 configuration, you must manually create the /config.ucs file before starting the installation.

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

Important: You should perform the installation first on the standby unit 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 the section Verifying the MD5 checksum of the installation file in the appropriate installation release note.

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.

Note: We recommend installing Global Traffic Manager or Link Controller on the hard drives of BIG-IP systems. Although installation on some CompactFlash® drives is supported in most cases, it is not recommended.

Performing a USB thumb drive installation

Before performing a USB thumb drive installation, read the following information.

  • USB thumb drive
    The USB thumb drive-based upgrade provides the ability to install the BIG-IP software from a USB thumb drive onto a BIG-IP system. For details about this installation method, see Installing BIG-IP software from a USB Thumb Drive.

Performing a local installation

Before performing a local installation, read the following information.

  • Local upgrade
    The local upgrade provides the ability to copy an installation manager (IM) package onto the system you intend to upgrade. You can apply this upgrade to any system with a hard drive. For details about this installation method, see Local Installation: Upgrading the BIG-IP software.

Performing a PXE server installation

Before performing a PXE server installation, read the following information.

Performing a remote installation

Before performing a remote installation, read the following information.

  • Remote upgrade
    The remote upgrade provides the ability to run the upgrade from a management workstation that is not directly connected to the system you intend to upgrade. For more information about this upgrade option, see Remote Installation: Upgrading the BIG-IP software.
[ Top ]

New and fixed in this release

New in version 9.4.7

Support for a new platform

This release provides support for the new 8900 platform, which is designed to provide superior performance. For more information, see Platform Guide: 6900 and 8900.

[ Top ]

Fixed in version 9.4.7

[Global Traffic Manager/Link Controller] iRule parser and comment indicator (CR85806)
Previously, the system did not prevent entering an iRule in the Configuration utility that the iRule parser would reject when either entered on the command line or parsed from the command line (for example, when later loading the system configuration containing that iRule). Such iRules are no longer rejected. Note, however, that iRules must conform to Tcl grammar, so only the pound symbol ( # ) is permitted as a comment indicator in iRules. Comments in the style of C (the paired /* and */ construction) or C++ ( // ) may be used elsewhere in configuration files, but the parser does not treat them as comment indicators inside iRules. For more information about this issue, see SOL7988: The iRule parser can fail to correctly parse and load an iRule from the command line.

[Global Traffic Manager] Format of Unknown string behavior change (CR101680)
The system now returns a consistent Unknown string for continent and country tags for the IP Classifier or netIana.inc file. Previously, the system returned UNKNOWN for unknown country codes and unknown for unknown continent codes. This might impact you if you are using the whereis iRule command for the Global Traffic Manager.

[Global Traffic Manager] IPv6 NoError and pool using drop-packet load balancing (CR109438)
IPv6 NoError is now respected when the pool is using drop-packet load balancing mode.

[Global Traffic Manager] Performance and large topology region databases (CR109303)
We have improved performance when loading and load-balancing large topology region databases.

Important: For features that pertain to platform-related or cross-product issues, see Release Note: BIG-IP Local Traffic Manager and TMOS version 9.4.7.

[ Top ]

New and fixed in prior releases

New in version 9.4.6

Support for a new platform

This release provides support for the new 6900 platform, which is designed to provide superior performance. For more information, see the guide for the associated platform, available in the AskF5 Knowledge Base.

Fixed in version 9.4.6

[Global Traffic Manager/Link Controller] UDP monitor and timeout (CR87859-2)
This releases corrects the condition in which the active queue eventually filled up with UDP monitor requests if the host virtual server did not exist. Now, the monitor times out when appropriate.

[ Top ]

New in version 9.4.5

Wide-IP alias search support (CR91859)

This release provides support for searching for wide-IP aliases in the Configuration utility.

FirePass monitor

This release profiles a new FirePass monitor for use in monitoring FirePass systems.

Transparent support for HTTPS, TCP Half Open, and UDP monitors (CR57570, CR92916)

This release makes transparent mode an available option for the HTTPS, TCP Half Open, and UDP monitors.

[ Top ]

Fixed in version 9.4.5

[Global Traffic Manager/Link Controller] Parent pool name reported to SNMP (CR68235)
In previous releases, the SNMP table, gtmPoolMemberStat, returned the parent virtual server name instead of the parent pool name. Now, the correct pool name is returned.

[Global Traffic Manager] 4.x to 9.x migration with disabled wide IPs (86578-2)
In previous releases, when migrating configurations from software version 4.x to 9.x, if the wideip.conf file contained any wide IPs marked disabled_until or disabled, the migration process failed. This release corrects this issue, so you can successfully migrate configurations containing disabled wide IPs.

[Link Controller] snmp_link or snmp monitor (CR88297)
In previous releases, an snmp_link monitor or snmp monitor with an explicitly defined destination always timed out. In this release, these monitors work correctly with an explicitly defined destination.

[Link Controller] snmp_link monitor probe (CR90685)
In earlier releases, if probe responses were returned to gtmd with identical uptimes, then the statistics could show zero values. In this release, the snmp_link monitor does not send out multiple requests during the same polling interval, so this issue no longer occurs.

[Global Traffic Manager] Domain Validation IDN Compatible option (CR93706)
Earlier releases showed the unsupported option IDN Compatible on the System-> General Properties-> Global Traffic-> General-> screen, in the Domain Validation list of the Configuration utility. We have removed this unsupported option in this release.

[Global Traffic Manager] Domain Validation Help screen (CR93708)
In previous releases, there was no Help screen for the Domain Validation feature. Now there is a Help screen that describes all of the options.

[Global Traffic Manager] big3d process memory leak (CR93994-1)
In a previous release, The big3d process could leak memory during monitor probe responses for Host virtual servers, which could intermittently mark Host virtual servers up and down. In this release, we have optimized the big3d process memory usage when monitoring a large number of virtual servers, so the leak no longer occurs.

[Global Traffic Manager] Misconfigured pool member and configuration load (CR94706-3)
In this release, the system successfully parses and loads a wideip.conf file that contains a manually misconfigured pool member.

[Global Traffic Manager] Virtual server discovery on additional systems (CR96163)
In previous releases, the system could fail to discover virtual servers from a Global Traffic Manager server that was added to the configuration. This release provides improved reliability of the virtual server discovery process in sync groups containing multiple Global Traffic Manager systems.

[ZoneRunner] TTL option change and record deletion (CR96871)
In a previous release, if you changed the time-to-live (TTL) value for an existing record in the ZoneRunner utility, the system could delete the record. Now, changing the TTL value does not cause deletion of this record.

[ Top ]

New in version 9.4.4

This release included no new items specific to this version.

Fixed in version 9.4.4

Virtual server statistics (CR57443)
Global Traffic Manager now returns virtual server statistics correctly if the virtual server names are the same on two 9.x BIG-IP systems.

Allow underscores in names (CR72770)
The ZoneRunner utility now allows underscores in Global Traffic Manager wide IP names and in A or AAAA records. To enable this feature, navigate to the System -> General Properties -> Global Traffic -> General -> screen in the Configuration utility, and change the Domain Validation setting from Strict to Allow Underscores. See SOL8140: Adding the underscore character to a wide IP name for additional information.

Allow slash(/) and anything else in names (CR73425)
The Global Traffic Manager ZoneRunner utility now allows slashes in zone names or resource record names to support classless in-addr.arpa delegation as defined in RFC2317. To enable this feature, navigate to the System -> General Properties -> Global Traffic -> General -> screen in the Configuration utility, and change the Domain Validation setting from Strict to None. Note that the None option actually allows any character in a name.

ZRD allows semi-colon (CR86682)
The ZoneRunner utility now properly handles TXT records that contain semicolons in the resource record, and no longer displays the message Error retrieving database.

Cert expiration notifications (CR87209)
Imminent expiration (within 30 days) of certificates used in iQuery connections to or from gtmd and big3d processes now generate an advance warning. The warning message contains the offending unit's IP address and the certificate expiration date (in GMT). Once the certificate expires, the customer continues to receive a warning message with the offending unit's IP address. These warnings are sent to syslog from the log file /var/log/gtm, and also trigger SNMP traps.

Redundant Local Traffic Manager systems frequent status changes (CR87940)
Global Traffic Manager now obtains correct status information from a redundant pair of Local Traffic Manager systems, version v.9.4.1 after installing newer big3d on those systems. Global Traffic Manager no longer marks the Standby box up and down every 60 seconds.

big3d stops on BSDI boxes (CR88060)
On BSDI boxes the big3d daemon no longer silently stops running after a config sync process.

SNMP trap log changes (CR88087)
Now SNMP trap log entries in the /var/log/gtm file, show both the name and the IP:Port combination for any virtual server that changes status to up or down.

ZoneRunner errors when modifying MX records (CR88214)
Now with BIND 9.4.2, you cannot create an MX record without a matching A record. This eliminates errors in ZoneRunner when deleting or modifying MX records.

9.2.5 configuration (CR88397)
Upgrading from 9.2.5 now loads the configuration correctly. Previously, after the installation and reboot, there were no errors and the /config/gtm/wideip.conf file was correct. However, none of the information showed up in the user interface.

Requesting all resource records (CR89209)
The Global Traffic Manager Configuration utility, now requires that the user press the Search button before the screen displays any resource records. Resource records are displayed according to the Search criteria.

Query to Local Traffic Manager virtual server using iRule (CR89944)
A query to a Local Traffic Manager virtual server with two or more pools in a iRule now correctly shows a status of green even if some pools have zero members marked as up.

VS topology update (CR89362)
Adding a topology record after a virtual server is created now updates the virtual server's topology references correctly.

bg3d memory leak (CR89582)
This release corrects a 4K memory leak in the big3d process when it loses connectivity with the gtmd process.

Short DNS messages (CR89666)
This release provides improved stability when handling UDP DNS packets with payloads less than 12 bytes.

big3d memory reallocation (CR89888)
This release resolves memory reallocation issues in the big3dprocess when connections change frequently from up to down.

Virtual server in iRule status (CR91030)
A query from a BSDI Global Traffic Manager to a virtual server with two or more pools in a iRule now correctly shows a status of green even if some pools have zero members with a status of up.

syncer and sync_zones with IPv6 (CR91639)
Running the syncer and sync_zones commands against IPv6 formatted addresses now works correctly.

rsync upgrade required for ipv6 (CR91819)
The sync, sync-zones, and big3d_inbstall command now works correctly on IPv6 only systems after upgrading to a newer version of the rsync utility.

big3d installation (CR91885)
The big3d agent installation script now contains more error checking and debugging, eliminating some potential installation failure points.

[ Top ]

New in version 9.4.3

This release included no new items specific to this version.

Fixed in version 9.4.3

Missing httpd file and Configuration utility access (CR85993, CR80083)
In previous releases, a rare installation error condition or a clean installation could block creation of the Pluggable Authentication Modules (PAM) httpd file, which prevented access to the Configuration utility. In this release, the installation process correctly creates the httpd file, so this problem no longer occurs.

[ Top ]

New in version 9.4.2

This release included no new items specific to this version.

Fixed in version 9.4.2

[Global Traffic Manager] Global Availability load balancing mode functions correctly (CR58514)
In previous releases, the Global Availability load balancing mode did not correctly load balance for virtual servers. With this release, this load balancing mode now performs as expected.

[Global Traffic Manager] Probes for translated virtual servers sent to connected self IP addresses (CR61003)
Previously, the gtmd utility sent probes for translated virtual servers to the first self IP address on the system that used the same link, regardless of whether this self IP address was actually connected. With this release, the gtmd checks to ensure it sends probes to a connected self IP address.

[Global Traffic Manager] gtm_add utility retains contents of server.crt file (CR72708)
In earlier releases, when you updated a server.crt file in the Configuration utility, the system did not update the certificate in its own directories. This resulted in the updated file being overwritten when running the gtm_add utility. With this release, the updated file is stored in the correct locations as expected.

[Link Controller] System support for ipv6_noerror responses (CR73573-1)
In previous releases, Link Controller did not support ipv6_noerror responses, which delayed BIND resolution for DNS requests of IPv6 addresses. A new option for configuring wide IPs, IPv6 NoError Response, allows you to control how the system responds to these requests.

[Global Traffic Manager] Errors in server.crt file generate correct error messages (CR73694)
Previously, if the server.crt file became corrupted, the gtmd utility crashed the system. In this release, errors in the file generate a log message and stop the gtmd utility, allowing you the opportunity to fix the errors and restart the gtmd utility.

[Global Traffic Manager] Improved performance with large numbers of DNS requests (CR74170)
In earlier releases, a large number (greater than 1000) of DNS requests could cause the system to drop some of the requests. This release improves the system's ability to handle large numbers of DNS requests.

[Global Traffic Manager] System now uses prober IP address assigned to host server (CR74182)
In previous releases, the system did not use the IP address assigned to a host server for handling probe requests for SNMP communications. With this release, the system uses the IP address you assigned to the host server for SNMP probe requests.

[Global Traffic Manager] System support for tcp-based listener (CR74218)
Previously, you could not create a Global Traffic Manager that used TCP. This release includes support for TCP-based listeners.

[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] Tcp_half_open monitor reports virtual server status correctly (CR75808-1)
This release corrects a problem in which the tcp_half_open monitor incorrectly marked a virtual server as down. This issue was caused by an error in the reporting mechanism that failed to recognize that a virtual server was up under certain conditions.

[Global Traffic Manager] Unmonitored pool member status interpretation (CR76025)
Global Traffic Manager now correctly interprets the status of Local Traffic Manager virtual servers. Thus, unmonitored pool members associated with a Local Traffic Manager virtual server now result in green Global Traffic Manager virtual servers.

[Global Traffic Manager] LB::status pool my_pool member 10.0.10.82 80 down won't parse (CR76723)
In previous releases, using the iRule statement LB::status pool | node resulted in MCP and gtmd syntax errors. The system now supports this statement correctly.

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

[Global Traffic Manager] External monitor improvements (CR76978)
This release fixes an issue in which the external monitor failed to remove processes after they were no longer needed. The monitor now removes these processes.

[Global Traffic Manager] Systems stuck in config sync loop (CR77929)
This release resolves an issue in which several Global Traffic Managers could get stuck in a continuous config sync process. This issue was the result when a system received a new configuration but was unable to get the new timestamp for the configuration file. With this release, this error no longer occurs.

[Global Traffic Manager] Topology load balancing accepts regions of pools (CR80154)
Previously, the Topology load balancing mode did not function correctly if its destination was a region that consisted only of pools. The system now load balances correctly with this release.

[Link Controller] Link status reported in redundant pair configuration improved (CR81809)
In earlier releases, a condition existed in which a link on the active Link Controller in a redundant pair configuration remained active even if the Link Controller itself had a status of down. This condition resulted from the standby unit incorrectly identifying the down system as still active. With this release, the state of the primary Link Controller is reported correctly, ensuring that links that are associated only with that unit are unavailable when the unit goes down.

[Global Traffic Manager] RADIUS monitor operates correctly (CR82051)
This release resolves a previous issue that occurred when you attempted to create a RADIUS monitor. This issue caused the system to display an error when you selected RADIUS as the monitor type. With this release, you can create RADIUS monitor types as needed.

[Global Traffic Manager] gtm_add script no longer corrupts zone files (CR82646)
In previous releases, running the gtm_add script could corrupt the zone files on the system. This issue occurred when the zone files were modified during the synchronization process. With this release, the zrd utility shuts down during the synchronization process, ensuring that zone file changes do not occur until after the gtm_add script completes.

[ Top ]

New in version 9.4.1

This release included no new items specific to this version.

Fixed in version 9.4.1

[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 ]

New in version 9.4

The 9.4 release included new items in several areas. Some of the new items offer new capabilities for managing traffic, while others offer enhanced security and system performance. For documentation and details, see User documentation for this release.

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.

Fixed in version 9.4

This release included no fixed items specific to this version.

[ 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/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)
When you create a Wide IP with more than one pool, the system makes an ordinal assignment for each pool. If you remove a pool, the remaining pools retain their ordinal assignment. The system does not reorder the pools to match their new number for the Wide IP. This issue can be safely ignored.

[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 does 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] 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] iRule sorting order (CR68727)
Currently, the only order in which you can run iRules is alphabetical order within a Wide IP.

[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/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] 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/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] Configuration utility does not display pool members when pool name contains a slash ( / ) (CR79276)
If a pool name contains a slash ( / ) character, the system is unable to display the pool members that belong to that pool. To work around this issue, rename the pool, removing the slash character.

[Global Traffic Manager] System attempts iQuery connection with self management port (CR79329)
A condition exists in which Global Traffic Manager attempts to create an iQuery connection with its own management port. This issue occurs rarely, and is often resolved by running the command bigstart restart.

[Global Traffic Manager] Configuration utility displays an error when IPv6 is mistyped (CR79544)
When adding an IPv6 address through the Configuration utility, if you type only one colon instead of two, the system displays an error message. To work around this issue, verify that you have entered the IPv6 address correctly.

[Global Traffic Manager] bigip_link monitor and address translations (CR82153)
In this release, the bigip_link monitor cannot process a link that uses a translated IP address. We recommend that you use this monitor only on links that do not use translated IP addresses.

[ZoneRunner] HINT zones (CR83505)
When a HINT zone is configured on a Global Traffic Manager, ZoneRunner attempts to query it every time the user refreshes the Record Resource List tab in the Global Traffic Manager Configuration utility. When it fails, an error is logged in the /var/log/gtm file. You can safely ignore these errors.

[Global Traffic Manager] Changing a pool in a region (CR84815-2)
If you make changes to a Global Traffic Manager pool for a region, they do not take effect until you restart the system.

[Link Controller] SSL profile appears in the Configuration utility (CR84890)
When adding profiles to Link Controller, the option to add an SSL profile is available; however, this profile type is unsupported in Link Controller.

[Global Traffic Manager] Topology Threshold setting not saved if no topology records exist (CR84965)
If you set the Topology Threshold setting in the Global Traffic Manager General Properties section, but have not yet created any topology records, the system does not save this setting. To work around this issue, create at least one topology record before setting the Topology Threshold value.

[Global Traffic Manager] Zone file changes on redundant systems (CR85597)
Occasionally, modifying a zone file on one Global Traffic Manager in a redundant system configuration results in the system displaying the error message: 01020005:3: The requested operation is not implemented yet. To resolve this issue, modify the INI file in usr/local/bin/sync_zones to ensure the rsync operations uses the -u option.

[Global Traffic Manager] Extend Text area functionality reversed for named (CR85615)
If you use the Firefox or Mozilla browser, and are editing the named configuration file, a situation occurs in which the Extend Text option reverses functionality. This situation occurs when you enable the Extend Text option, enable the Wrap Text option, and then disable the Extend Text option.

[Global Traffic Manager] Deleting views causes View Not Found error (CR85657)
If you select multiple views to delete, then deselect a view when prompted to confirm the deletion, the system displays a View Not Found error. To work around this issue, verify that you have correctly selected the views that you want to delete before you proceed with the deletion process.

[Global Traffic Manager] Blank iRule generated causes error (CR85671)
When creating a new wide IP or link, if you click Add in the iRules section but do not add an iRule, the system creates a blank iRule. This blank iRule is invalid and generates an error. To work around this issue, do not click Add if you do not intend to add an iRule to the wide IP or link.

[Global Traffic Manager] ZoneRunner fails to display more than 2000 wide IPs (CR85826)
With this release, the ZoneRunner is unable to display more than 2000 wide IP addresses that reside in the same zone and use the same pool. This issue is partially fixed in CR89209.

[Global Traffic Manager/Link Controller] MSQL monitor (CR87524)
The MSSQL monitor fails to send monitor traffic. A workaround is to run the chmod +s /usr/bin/monitors/builtins/DB_monitor command as root on each Global Traffic Manager system that is doing the monitoring.

A workaround is to disable the hosts or the specific virtual servers that do not exist. You must restart the big3d process to clear out the active queue.

 

[Link Controller] snmp_link monitor stats (CR88298)
If you define two self IP addresses on a link, and use the snmp_link monitor, then the result is zero value link stats.

[Global Traffic Manager/Link Controller] Hotfix containing big3d and uninstall (CR88602)
Uninstalling a hotfix fails to overwrite the big3d application if the version numbers are the same, even if the build numbers are different. This is normally not a concern, and can be ignored.

[Link Controller] Link status flap (CR88771)
If a standby Global Traffic Manager is responsible for sending out bigip_link monitor probes, restarting the standby gtmd process can cause the link status to repeatedly change status (down and up) on the active unit. To work around this problem, increase the bigip_link timeout value from the default of 30 to 40 seconds, and change the getconfig request timer setting from a 30 second start delay to 10 seconds on the standby Global Traffic Manager unit.

[Global Traffic Manager] Heartbeat failure and gtmd core (CR92917)
On a 3400 platform, adding a topology.inc file of 20,000 records with the gtmparse -l command, results in a heartbeat failure and a gtmd core file. The records do successfully load.

[Global Traffic Manager] Sync group and time differences (CR98631-2)
For communication between hosts, such as a sync group, a system clock that runs fast or slow might cause the timestamps communicated between the units to diverge, even if the system clock is kept accurate with Network Time Protocol (NTP). Once the time drifts as far as the value of time tolerance, the system starts to log messages about it. The workaround in this case is to restart the gtmd utility. This resets the system's monotonic clock to the wall clock time, which should be the same as all other systems in the sync group.

[Global Traffic Manager] Debug option in FTP monitor (CR99014)
The Debug setting for the Global Traffic Manager FTP monitor has no function. When you enable the Debug option, the system does not write debug messages to the /var/log file as is expected. There is no workaround for this issue.

[Link Controller] Log message Unexpected proxy reply from %zrd (CR99087)
During bootup after rolling forward a .ucs file, the system posts the following message in the Local Traffic Manager log files: Unexpected proxy reply from %zrd. The message is benign, and you can safely ignore it. Note that this occurs only on systems licensed for Link Controller.

[Global Traffic Manager] ZoneRunner default * search operation with 3,500 Resource Records (CR108670)
When you click the ZoneRunner menu item and search with the default * (all) option on a system that has a large number of Resource Records (approximately 3,500), the operation can fail with a General database error. You can use the following procedure as a workaround.

  1. Provision additional host operating system memory using the command bigpipe db Provision.extraMB 256.
  2. Provision some Tomcat memory using the command bigpipe db Provision.Tomcat.extraMB 256.
  3. Reboot the system using the command full_box_reboot.

     

[ Top ]

Contacting F5 Networks

  Phone: (206) 272-6888
Fax: (206) 272-6802
Web: http://support.f5.com
Email: support@f5.com

For additional information, please visit http://www.f5.com


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)