Applies To:

Show Versions Show Versions

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

Updated Date: 08/30/2013


This release note documents the version 10.0.1 release of BIG-IP® Global Traffic Manager and BIG-IP® Link Controller. To review what is new and fixed in this release, refer to New in version 10.0.1 and Fixed in version 10.0.1. For existing customers, you can apply the software upgrade to versions 9.3.x, 9.4.x, 9.6.x, and 10.0.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,


- User documentation for this release
- Minimum system requirements and supported browsers
- Supported platforms
- Installing the software
- Upgrading from earlier versions
- New in version 10.0.1
- Fixed in version 10.0.1
- New in version 10.0.0
- Fixed in version 10.0.0
- 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.

[ Top ]

Minimum system requirements and supported browsers

The minimum system requirements for this release are:

  • System hard drive
  • 768 MB RAM (1 GB recommended)

Note: You cannot run this software on a CompactFlash® media drive; you must use the system's hard drive.

You can work with the BIG-IP system Configuration utility using the following browsers:

  • Microsoft® Internet Explorer®, version 6.0x, and version 7.0x
  • Mozilla® Firefox®, version 1.5x, version 2.0x, and version 3.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 1500 (C36)
  • BIG-IP 1600 (C102)
  • BIG-IP 3400 (C62)
  • BIG-IP 3410 (C100)
  • BIG-IP 3600 (C103)
  • BIG-IP 4100 (D46) - unit running Application Security Manager only
  • BIG-IP 4500 (D43) - unit running WebAccelerator System only
  • 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: Although the BIG-IP 1500 with 768 MB of RAM is supported and does load the 10.x configuration, some performance metrics may be lower than for systems with 1 GB of RAM. It not recommended to attempt running additional product modules on a system that has only 768 MB of RAM

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

Note: The hardware and software for each unit in a redundant system must match.

[ Top ]

Installing the software

This section lists only the very basic steps for installing the software. The BIG-IP® Systems: Getting Started Guide contains details and step-by-step instructions for completing an installation. F5 recommends that you consult the getting started guide for all installation operations.

The steps in this section assume that:

  • The license is already reactivated and the service contract is already updated for this release, if applicable.
  • You downloaded the .iso file from F5 Downloads to /shared/images on the source for the operation.
    (Note that you might need to create this directory. If so, use this exact name, including capitalization.)
  • There is at least minimal partitioning on the system drives.
  • You have already configured a management port.
  • You are logged on to the management port of the system you want to upgrade.
  • You are logged on to a hard drive installation location other than the target for the operation.
  • You logged on using an account with administrative rights.
  • You have saved the user configuration set (UCS) in the /var/local/ucs directory on the source installation location, if applicable.
  • You are logged on to the standby unit in a redundant system, if applicable, and that you will synchronize the configuration to the active unit.
  • You turned off mirroring, if applicable.
  • If you are upgrading from 9.3.x or 9.4.x, you ran im <downloaded_filename.iso> to copy over the new installation utility.

Installation consists of the following steps.

  1. To copy the upgrade utility, run the command im (for first-time 10.x installation).
  2. To install the software, use one of the following methods:
  • Run the command image2disk --instslot=HD<volume_number> <downloaded_filename.iso> (for first-time 10.x installation).
  • Run the command bigpipe software desired HD<volume_number>version 10.x build <nnnn.n> product BIG-IP
  • Use the Software Management screens in the browser-based Configuration utility.

After the installation finishes, you must complete the following steps before the system can pass traffic.

  1. Reboot to the new installation location.
  2. Log on to the browser-based Configuration utility.
  3. Run the Setup utility.
  4. Provision the modules.

Each of these steps is covered in detail in the BIG-IP® Systems: Getting Started Guide, and we recommend that you reference the guide to ensure successful completion of the installation process.

The upgrade process installs the software on the inactive installation location that you specify. This process usually takes between three minutes and seven minutes. During the upgrade process, you see messages posted on the screen. For example, you might see a prompt asking whether to upgrade the End User Diagnostics (EUD), depending on the version you have installed. To upgrade the EUD, type yes, otherwise, type no.

You can check the status of an active installation operation by running the command b software status.

If installation fails, you can view the log file. For image2disk installations, the system logs messages to the file you specify using the --t option. For other installations, the system stores the installation log file as /var/log/liveinstall.log.

[ Top ]

Upgrading from earlier versions

How you upgrade from earlier versions depends on the version of software you have.

Important: BIG-IP version 10.x has introduced the ability to run multiple modules based on platform. The number and type of modules that can be run simultaneously is strictly enforced through licensing. For more information, see SOL10288: Supported product module combinations by platform.

Upgrading from version 9.6.x or 10.x

When you upgrade from software version 9.6.x or 10.x, you can use the Software Management screens in the Configuration utility to complete these steps. To open the Software Management screens, in the navigation pane of the Configuration utility, expand System, and click Software Management. For information about using the Software Management screens, see the online help, or the relevant chapters in the BIG-IP® Systems: Getting Started Guide.

Upgrading from version 9.3.x or 9.4.x

If you plan to install this version of the software onto a system running 9.3.x or 9.4.x, you must perform a one-time upgrade procedure to make your system ready for the new installation process. When you update from software version 9.3.x or 9.4.x to 10.x, you cannot use the Software Management screens in the Configuration utility. Instead, you must run the image2disk utility on the command line. For information about using the image2disk utility, see the BIG-IP® Systems: Getting Started Guide.

Upgrading from versions earlier than 9.3.x

You cannot upgrade directly to this version from BIG-IP version 4.x or from BIG-IP versions 9.0.x through 9.2.x. You must be running software version 9.3.x, 9.4.x, or 9.6.x. For details about upgrading to those versions, see the release notes for the associated release.

Note: Beginning with version 10.0.0 of the software, a redundant system configuration must contain failover peer management addresses for each unit. If you roll forward a redundant system configuration from 9.3.x or 9.4.x, the units start up in an offline state because each one needs a failover peer management address. To configure the failover peer management addresses, navigate to the Network Failover screen, available under High Availability on the System menu on the navigation pane, and specify the management IP address of the peer unit in the Peer Management Address field. Then do the same on the other unit in the redundant system. Once you specify both IP addresses, the system should operate as expected. For more information, see SOL9947: Change in Behavior: The Peer Management Address setting is required for BIG-IP version 10.x systems configured for network failover.

[ Top ]

New in version 10.0.1

This release contains no new items specifically related to Global Traffic Manager or Link Controller.

Important: For platform-related or cross-product issues, see Release Note: BIG-IP Local Traffic Manager and TMOS version 10.0.1.

Fixed in version 10.0.1

This release contains no fixed items specifically related to Global Traffic Manager or Link Controller.

Important: For platform-related or cross-product issues, see Release Note: BIG-IP Local Traffic Manager and TMOS version 10.0.1.

[ Top ]

New in version 10.0.0

New search feature
In this release, you can search for a specific component or group of components that you want to manage or configure. This feature is especially useful for companies with large networks that contain numerous physical and logical components.

Traffic Management shell (tmsh)
This release includes a new command line interface known as the Traffic Management shell, or tmsh. The Traffic Management shell is a hierarchically based interface that offers features such as command completion, command history, and context-sensitive help. You can use tmsh to set up your network, configure local and global traffic management, and display information about performance, load balancing decisions, network traffic, and Traffic Management Operating System (TMOS®). The tmsh utility provides the first complete command line interface for configuring Global Traffic Manager.

New performance data graphs
With this release, you can use the browser-based Configuration utility to view graphs that display information about how the Global Traffic Manager is performing. You can use this information to determine how to modify the configuration to obtain the best possible performance from the system.

New Ignore Down Response setting for ECV monitors
Normally, the Global Traffic Manager ECV monitor marks a monitored object down right after it receives the first down response when probing the object. You can use the new Ignore Down Response monitor setting to override this default behavior, by marking a monitored object down only after a Timeout value for the monitor has been exceeded.

Probe information now available in the logs
With this release, you can configure the Global Traffic Manager to log information about the probes that track the health and availability of your network resources. You can use this information to help you fine tune the probes.

Support for Fallback IPv6 address
In this release, when you configure the Fallback IP load balancing mode for a pool, you can specify both IPv4 and IPv6 addresses as fallback IP addresses.

Support for IPv6 NoError response
With this release, you can configure the Global Traffic Manager or the Link Controller to send a NoError response when either receives a AAAA request for a wide IP that does not have any associated AAAA resources.

Support for delaying when the system marks virtual servers as down
In the past, if all iQuery connections were lost to a BIG-IP system's big3d process, the system marked all virtual servers down. This is still the default behavior. You can configure a new global variable, vs_depends_server_state, to control this behavior. If this variable is set to yes, the system operates as it did previously. If you set this variable to no, then the system marks the virtual servers down only when their monitors time out.

New iRule commands
In this release, you can use the following new iRule commands to configure the Global Traffic Manager: whoami, whereami, uptime, members [-list] pool_name [blue|green|yellow|red|gray], pools [-list] [blue|green|yellow|red|gray], persist [enable|disable], and nodes_up [vs_name | ip port].

Fixed in version 10.0.0

This release lists no specific fixes because it is a zero-level release.

[ Top ]

Known issues

This release contains the following known issues.

[Global Traffic Manager] Enable/disable object status (CR92216)
Occasionally, changes to object status (specifically, enable/disable) you make using the browser-based Configuration utility do not always immediately reflect in the Configuration utility. The corresponding config file (for example, wideip.conf) is correctly modified, but the object's visual status might remain in its previous state.

[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 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] Monitor timeout and changing timeout values (CR101679)
If you have a large configuration, and you change a monitor's timeout and interval values at the same time, the system might report hosts changing to a down state immediately followed by an up state. In general it is best to change either the timeout or interval, but not both simultaneously. If you plan to use bigger values, change the timeout first. If you plan to use smaller values, change the interval first. In each case, always allow for a full configuration propagation in between changes.

[Global Traffic Manager] ?Active? string in command line prompt (CR106291)
When you load a large configuration, the command line prompt might change to ?Active?. Pressing return resets the prompt to Active, as expected.

[Global Traffic Manager] Translated IP and Port (CR113989)
Using the Traffic Management Shell (tmsh), it is possible to add only a translated IP address or only a translated port, rather than specifying both values together. If you only specify one, the system does not save the configuration, and uses 0 (zero) as the port. The workaround is to change the port, define the IP address, and then set the port to the value you want to use.

[Global Traffic Manager] mprov logging errors in /var/log/gtm (CR112754)
When you use the bigpipe utility or the tmsh utility to set provisioning, make sure to wait a minimum of 30 seconds (more, if you are provisioning several modules) before issuing any other provisioning command. If you do not, the system could end up misconfigured, which requires a full reboot to correct.

[Global Traffic Manager] Operator role and enable/disable pool members (CR111032)
Users with the Operator role can now use the interactive command line to enable and disable pool members. However, users with the Operator role cannot use the edit command to perform the same functions, because there is no way to determine what part of the configuration is legitimate for the Operator user to edit.

[Global Traffic Manager] Data centers across gateways (CR110976)
If you configure two data centers, one with a default gateway pool and links to another subnet, and the other with no links to another subnet, the system might show incorrect status until it resolves all the input from the links. In that case, you might see the following error message in the /var/log/gtm log:

Nov 3 11:28:22 local/gtm3603 crit gtmd: 011a1002:2: Can not find GATEWAY target member for pool default_gateway_pool

Although there is no workaround for this issue, the systems eventually sort out the conflicts and mark all objects up.

[Global Traffic Manager] Upgrade and sync groups (CR103265)
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.

[Global Traffic Manager] FTP monitor and multi-line responses (CR104562)
The Global Traffic Manager FTP monitor does not handle multi-line responses correctly. If an FTP server uses multi-line responses, you might encounter undefined behavior, which could include monitor flapping or consistent monitor failure.

[Global Traffic Manager/Link Controller] Licensing for Global Traffic Manager or Link Controller only (CR107158)
When you install the software for a Global Traffic Manager only or Link Controller only, the system reports provisioning only for Local Traffic Manager, even though the Global Traffic Manager and Link Controller menus are active. Before you can use Global Traffic Manager or Link Controller, you must open the Resource Provisioning screen on the System menu in the navigation pane, and provision Global Traffic Manager or Link Controller.

[Global Traffic Manager] Routing domains and Global Traffic Manager (CR107402)
Routing Domains are supported on internal interfaces only when there is a Global Traffic Manager system on the network and monitoring the Local Traffic Manager system. Routing Domains are supported on internal and external interfaces (virtual servers, self IP addresses, and so on) when there is Global Traffic Manager in the network or the operator decides not to monitor that Local Traffic Manager. Note that there is nothing in the software to prevent you from configuring Routing Domains on both the internal and external interfaces when there is a Global Traffic Manager system on the network. Therefore, it is the system administrators' responsibility to ensure the proper configuration for their network environment. Also note that Routing Domains are not supported on a Local Traffic Monitor system that is also running the Global Traffic Monitor product module.

[Global Traffic Manager] Topology record creation and error checking (CR108969)
When you use tmsh to create topology records, the system posts potentially confusing error messages when you omit a parameter value in the ldns portion of the record. For example, if you omit the value for the parameter continent, the system presents the following error message:

root@combo54(Active)(tmos.gtm.topology)# create ldns: continent
01070242:3: Topology record contains bad server type: 15

To work around this situation, specify all parameters for the ldns portion of the topology record.

[Global Traffic Manager/Link Controller] Roll forward from 9.x and Application Security Manager and Global Traffic Manager provisioning (CR120828)
When you roll forward a 9.x user configuration set (UCS) file that is configured for Application Security Manager and Global Traffic Manager, provisioning for Global Traffic Manager is not enabled. To enable Global Traffic Manager using the browser-based Configuration utility, in the navigation pane, expand System, and click Resource Provisioning. In the Module Resource Provisioning section, select the provisioning level you want from the Global Traffic (GTM) and Link Controller (LC) drop-down lists.

[ Top ]

Contacting F5 Networks

  Phone: (206) 272-6888
Fax: (206) 272-6802

For additional information, please visit

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)