Applies To:

Show Versions Show Versions

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

Software Release Date: 01/21/2007
Updated Date: 12/11/2013

Summary:

This release note documents the version 9.2.5 feature release of BIG-IP® Global Traffic Manager, and the BIG-IP® Link Controller. To review the features in this release, see New features and fixes in this release. This release is cumulative, and includes all fixes and enhancements since version 9.2. For existing 3-DNS Controller customers, you can apply the Global Traffic Manager upgrade to systems running 3-DNS® Controller version 4.5 PTF-04 through version 4.5.13, and version 4.6 through version 4.6.4. For existing Link Controller customers, you can apply the Link Controller upgrade to systems running Link Controller version 4.5 PTF-04 through version 4.5.13, and version 4.6 through version 4.6.4. For information about installing the upgrade, please refer to Installing the software.

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

Contents:

- User documentation for this release
- Minimum system requirements and supported browsers
- Supported platforms
- Installing the software
     - Performing a local installation
     - Performing a PXE server installation
     - Performing a remote installation
     - Verifying the MD5 checksum of the upgrade file
     - Re-activating the license on the BIG-IP system
- New features and fixes in this release
     - New features in this release
     - New fixes in this release
- Features and fixes in prior releases
- Optional configuration changes
     - Using SNMP read/write OIDs
     - New SNMP OIDs
     - Using the switchboot utility
- Known issues
- Workarounds for known issues
- Acknowledgments


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.

[ Top ]

Minimum system requirements and supported browsers

The minimum system requirements for this release are:

  • 512MB RAM (if installed as a stand-alone Local Traffic Manager or Global Traffic Manager product)
  • 768MB 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)
  • 512MB 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.2.5.

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 may 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 support.
  • 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)

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.2.5 software installation. Before you begin the installation process, you need to determine which installation option is appropriate.

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

Warning: The system to which you install the Global Traffic Manager or Link Controller must have at least 768MB of RAM.

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

Warning: You must turn off mirroring before you attempt to upgrade to version 9.2.5. We do not support mirroring between units that are not running the same version of the software.

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), and BIG-IP 8400 (D84) 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 a failover and apply the upgrade to the other unit in the redundant system.

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 earlier versions of 9.2.x only.

Important: If your environment requires that the Global Traffic Manager operate in a fail-safe or high availability mode, see the section titled Configuring fail-safe in the Setting Up a Redundant System chapter, in the BIG-IP® Network and System Management Guide.

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 are 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 are currently running. 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.

[ Top ]

Verifying the MD5 checksum of the upgrade file

After you download the installation file and the matching MD5 checksum file, and before you perform the installation, we recommend you test the install 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.2.5.5.1.im is the name of the file you downloaded.

md5sum local-install-9.2.5.5.1.im

Check the output with the contents of the corresponding MD5 file. If they match, install the file. If they do not match, you should download the file again and repeat the process.

[ Top ]

Re-activating the license on the BIG-IP system

You need to re-activate the license on the BIG-IP system to use some of the new features added in this release.

To re-activate the license on the system

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

    The License screen opens.
     
  2. Click the Re-activate button and follow the onscreen instructions to re-activate the license.

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

New features and fixes in this release

This release includes the following new features and fixes.

Note: For features and fixes in earlier releases, see Features and fixes in prior releases.

New features in this release

This release contains no new Global Traffic Manager/Link Controller features.

New fixes in this release

This release contains the following fixes.

[Global Traffic Manager/Link Controller] Translated addresses on a link with an ICMP monitor (CR63299)
Previously, using a translated address on a link with an ICMP monitor associated with it caused a system failure. This release supports using translated addresses on a link with an ICMP monitor.

[Global Traffic Manager/Link Controller] Persist_mask variable not supported in Global Traffic Manager 9.x (CR64350)
We have removed a 4.x variable, persist_mask, and replaced it with the variable static_persist_cidr for IPv4 addresses and static_persist_v6_cidr for IPv6 addresses.

[Global Traffic Manager] Unable to add SRV records in ZoneRunner (CR70051)
With this release, you can now add SRV records in ZoneRunner. Previously, an error in the Priority field prevented ZoneRunner from creating the record.

[Global Traffic Manager/Link Controller] Memory leak with multiple probe protocols (CR70157)
In previous versions, a memory leak occurred when a probe failed and more than one probe protocol was specified. In this release, there is no memory leak.

[Global Traffic Manager/Link Controller] Dynamic Ratio load balancing and link throughput (CR69986, CR70188)
In previous versions, if you set the outbound load balancing mode for a set of links to Dynamic Ratio, traffic might have moved through only one link. Now, if you set the outbound load balancing mode for a set of links to Dynamic Ratio, traffic moves dynamically between both links.

[Global Traffic Manager/Link Controller] Locked up connection between big3d and big3dshim (CR70620)
In previous releases, a rare situation existed in which the connection between big3d and big3dshim locked up. With these release, these connections do not lock up.

[Global Traffic Manager] Persistence records not synchronized (CR70934)
Previously, an issue existed with persistence records and Global Traffic Managers that were configured as a redundant system. In this situation, if the Active system went offline and then came back online, the persistence records did not synchronize between the two systems. These records now synchronize correctly.

[Global Traffic Manager/Link Controller] Quality of Service/Topology load balancing with equal scores (CR71555)
With this release, if several virtual servers contain the same Quality of Service or topology scores, the Global Traffic Manager load balances connections equally between the virtual servers.

[Global Traffic Manager] Persistence requests synchronization (CR72106)
Previously, a situation existed in which a Global Traffic Manager did not register that it was synchronized with other systems. As a result, it ceased to respond to persistence requests. In this release, the Global Traffic Manager responds to persistence requests correctly.

[Global Traffic Manager] IPv4 and IPv6 DNS requests and persistence entries (CR72128)
In previous releases, switching between IPv4 and IPv6 DNS request resulted in the Global Traffic Manager removing persistence entries. Now, the Global Traffic Manager retains persistence entries when switching between IPv4 and IPv6 IP addresses.

[ Top ]

Features and fixes 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.)

Version 9.2.4 features and fixes

[Global Traffic Manager] ZoneRunner and undoing misconfigured allow-transfer statements (CR67968)
Previously, if you entered a misconfigured allow-transfer statement in ZoneRunner, the user interface did not operate correctly and allow you to fix the error. With this release, the user interface continues to function, allowing you to fix the allow-transfer statement.

[Global Traffic Manager/Link Controller] Wide IP validation issues with wide IPs without pools (CR67972, 68282)
In earlier versions, Global Traffic Manager generated a consistent stream of warning messages when you created a wide IP without associating a pool with it. These messages no longer appear.

[Global Traffic Manager] big3d_install and big3d agents over iQuery protocol (CR67986)
Previously, the big3d_install script did not always update big3d agents over the iQuery protocol. These agents are now updated successfully with this script.

[Global Traffic Manager] ZoneRunner and updates to forwarding zones (CR67990)
In earlier versions, updating a forwarding zone caused ZoneRunner to stop functioning. ZoneRunner now continues to function when you update a forwarding zone.

[Global Traffic Manager] ZoneRunner updates wide IPs with existing zone files (CR67992)
In earlier versions, if you added a wide IP that corresponded to an existing zone in your BIND configuration, ZoneRunner did not recognize that the zone already existed, and created a new master record. ZoneRunner now updates BIND correctly.

[Global Traffic Manager] System probes hosts with translated virtual servers (CR68005)
Previously, if Global Traffic Manager attempted to probe a host with translated virtual servers, the probe failed. The system can now probe these hosts correctly.

[Link Controller] Redundant systems and global traffic data (CR68006)
In earlier versions, a Link Controller redundant system did not synchronize global traffic data, such as wide IPs. Link Controller redundant systems now synchronize global traffic data.

[Global Traffic Manager/Link Controller] big3d and -broadcast_all option (CR68135)
Previously, systems responded to probes on the same interface on which the system received the probe. This behavior was different from the 3-DNS Controller, and resulted in situations where one Global Traffic Manager received a probe response on one interface, while another Global Traffic Manager did not receive that response because it was listening on a different interface. With the -broadcast_all option, all Global Traffic Manager systems listening from probes receive probe responses, regardless of interface. See the man page for the big3d command for more information.

[Global Traffic Manager] LDNS files with references to non-existent pools (CR68140)
Previously, upgrading the Global Traffic Manager occasionally resulted in the entries for pools that did not exist in an LDNS file. With this release, pools that have been removed do not appear in the LDNS file.

[Global Traffic Manager] ZoneRunner support for SRV records (CR68143)
Previously, ZoneRunner did not correctly manage SRV records. ZoneRunner now supports SRV records.

[Global Traffic Manager] BSDI compatible big3d and status of virtual servers from v.4.x standby unit (CR68148)
Previously, Global Traffic Manager received responses on the virtual servers that resided on a v.4.x BIG-IP redundant system, resulting in the appearance that the virtual servers were fluctuating between up and down states. The Configuration utility showed these servers as moving between a status of green and a status of red. With this release, the Global Traffic Manager is not affected by these responses.

[Global Traffic Manager] Translated addresses and Global Traffic Manager (CR68154)
In previous versions, Global Traffic Manager occasionally did not recognize that its addresses were translated addresses. This issue occurred when the system was starting up. The system now recognizes its addresses correctly with this release.

[Global Traffic Manager] Persistence record value on distributed applications (CR68155)
In earlier versions, the persistence record expiration time did not timeout correctly. With this release, persistence records time out as intended.

[Global Traffic Manager] Systems and set synchronization flags (CR68156)
Previously, Global Traffic Managers that were synchronizing persistence records did not always close their communication properly. These communications are now closed correctly.

[Global Traffic Manager/Link Controller] Status of virtual servers managed by Local Traffic Managers (CR68157, CR68158)
In earlier releases, it was possible for Local Traffic Managers to show that a set of virtual servers were up, while the Global Traffic Manager continued to display them as down. This issues has been resolved with this release, and the system now correctly reflects the status of virtual servers managed by Local Traffic Managers.

[Global Traffic Manager] System persistence in redundant system setup (CR68159)
Previously, if one of the Global Traffic Manager units in a redundant system missed a synchronization message, the systems did not maintain persistent LDNS connections. These units now maintain persistent LDNS connections.

Path probe messages (CR68161)
In earlier versions, the big3dshim might drop path probe messages. In this release, the big3dshim processes these messages correctly.

[Global Traffic Manager] ZoneRunner and master zone creation with transferred zone information (CR68162)
Previously, if you wanted to create a master zone by using the Transfer from Server option, ZoneRunner generated an error. You can now use this option to create master zones within ZoneRunner.

[Global Traffic Manager/Link Controller] Memory leak with certain messages (CR68163)
A memory leak that occurred when errors occurred in mpcd messages has been resolved with this release.

[Global Traffic Manager] System slowing when probing other systems (CR68164)
Previously, there were rare instances when Global Traffic Manager used too much memory and CPU when probing a very large number of LDNS clients. This release improves the performance of the Global Traffic Manager when probing a large number of LDNS clients.

[Global Traffic Manager] Traceroute utility router information (CR68165)
In earlier versions, the traceroute utility did not return the correct probe information when communicating with specific routers. The utility now returns information correctly.

[Link Controller] Fallback load balancing mode on Link Controllers (CR68166)
In previous releases, the fallback load balancing mode did not operate on Link Controllers. This mode now operates correctly on systems licensed for the Link Controller product.

[Global Traffic Manager] Monitoring Local Traffic Manager redundant systems (CR68167)
Previously, Global Traffic Manager monitors collected the status of virtual servers from both units of a redundant system which sometimes caused virtual servers to be marked down. This issue no longer causes virtual servers to be marked down.

[Global Traffic Manager/Link Controller] Static Persistence load balancing mode (CR68168)
In previous releases, the Static Persistence load balancing mode infrequently caused the system to crash. With this release, static persistence still does not function, but no longer causes a system crash.

[Global Traffic Manager/Link Controller] Pools with only one pool member (CR68169)
In earlier releases, pools with only one pool member might cause the system to crash. The system now supports pools with only one pool member.

[Global Traffic Manager] System probes to translated self IP addresses (CR68170)
Previously, the Global Traffic Manager connected to an incorrect self IP address when conducting a probe and translation was enabled. The system now sends probes to the correct self IP address.

[Global Traffic Manager] ZoneRunner and multiple include statements (CR68203)
In previous versions, ZoneRunner could only accept one include statement. With this release, you can use multiple include statements.

[Global Traffic Manager] Autodiscovery of links (CR68205)
Previously, the autodiscovery feature of the Global Traffic Manager discovered links and then incorrectly mark them as down. The system no longer marks these links as down on discovery.

[Global Traffic Manager/Link Controller] Virtual servers with same IP address and port number (CR68206)
It is possible, in certain network configurations, to have several virtual servers that have the same IP address and port number. In previous releases, this configuration was not supported by the Global Traffic Manager. This release includes support for virtual servers with the same IP address and port number.

[Global Traffic Manager/Link Controller] Server objects changes affect synchronization processes (CR68207)
In earlier versions, if a Global Traffic Manager server object was either deleted or fluctuated between an up and down state, there was a small risk that the Global Traffic Manager got stuck in a state in which it was unable to synchronize with other Global Traffic Managers. The state of these objects no longer affects the synchronization process.

[Global Traffic Manager] Zone files and the file associated with the zone (CR68208)
Previously, deleting a zone file did not actually delete the file from the system. This issue is resolved with this release, and the system removes deleted zone files.

[Global Traffic Manager] ZoneRunner and multiple resource records with the same name. (CR68259)
In previous versions, if two resource records shared the same name, ZoneRunner only displayed the properties of the first record, even if the second record was selected. ZoneRunner now returns the correct record in the properties screen.

[Global Traffic Manager/Link Controller] Virtual server unavailable when LTM pools have no enabled pool members (CR68281)
In the Local Traffic Manager, if a virtual server has no pool members it is still considered available. With this release, Global Traffic Manager does not send connections to virtual servers that have no members associated with them.

[Global Traffic Manager/Link Controller] Changes in US and Canada Daylight Saving Time (CR68781)
The Energy Policy Act of 2005, which was passed by the US Congress in August 2005, changed both the start and end dates for Daylight Saving Time in the United States, effective March 2007. Canada is also adopting this change. The resulting changes have been addressed in this version of the product software. To find out more about this issue, refer to SOL6551: F5 Networks software compliance with the Energy Policy Act of 2005.

[Global Traffic Manager] Persistence record performance improved (CR68950)
In earlier versions, continual updates to persistence records could dramatically decrease system performance. With this release, performance has been improved when updating persistence records.

[Global Traffic Manager/Link Controller] Links with multiple IP addresses (CR69124)
Previously, if you created a link that had two IP addresses, the system only recognized the first IP address. With this release, the system recognizes and uses all IP addresses.

[Global Traffic Manager/Link Controller] Monitors and resources with ampersands (&) (CR69128)
In earlier releases, if a resource, such as an HTML file name, contained an ampersand (&), the system was unable to process incoming information from that resource. The ampersand symbol is now fully supported with this release.

[Global Traffic Manager] Global Traffic Manager and incoming data from 3-DNS Controller probes (CR69132)
In previous versions, in mixed environments of 3-DNS Controllers and Global Traffic Managers, the Global Traffic Manager required a restart if it received data generated from a 3-DNS Controller gateway probe. With this release, the Global Traffic Manager can handle gateway probes from 3-DNS Controllers.

[Global Traffic Manager/Link Controller] Object name persistence (CR69145)
Previously, if you disabled and enabled a Global Traffic Manager object repeatedly, the name of that object might disappear from the configuration files and from the Configuration utility. With this release, names persist regardless of how often they move between being enabled and disabled.

[Global Traffic Manager/Link Controller] Do Not Reboot option now operates correctly (CR69149)
With this release, installing the software with the Do Not Reboot option now correctly instructs the system to not reboot after the installation completes. In previous releases, the system would occasionally reboot regardless of this option.

[Link Controller] One-time autodiscovery error in redundant system configuration (CR69152)
In earlier releases, if the bigdb variable, OneTimeAutoConfig was enabled, a system error occurred. This variable no longer generates a system error.

[Global Traffic Manager] Topology record matching request (CR69154)
With this release, if you designate Topology load balancing as the preferred or alternate load balancing method, the system moves to the next load balancing method any time a matching topology record cannot be found. Previously, the system would use Round Robin to load balance the connection request.

[Global Traffic Manager/Link Controller] Memory on big3d agents (CR69155)
Previously, the big3d agent could get overloaded with probe requests, resulting in the agent acquiring too much memory and affecting system performance. We have placed new limits to ensure that big3d agents have only a specific number of probe requests at any given time.

[Global Traffic Manager] Large numbers of probe requests can cause big3d agent to stop processing (CR69156)
In earlier versions, if a big3d agent was processing a large number of probe requests, it would stop processing those requests. The agent now handles a larger number of probe requests.

[Global Traffic Manager] One-time autodiscovery (no delete) option now acquires virtual server names (CR69161)
In previous releases, if you enabled the One-Time Autodiscovery (No Delete) option, the process would discover virtual servers, but not the names of those virtual servers. This issue is resolved with this release.

[Global Traffic Manager] Statistics Collection Server option in wideip.conf file (CR69164)
Previously, if you specified a probing server in the Statistics Collection Server option, that setting was not saved to the wideip.conf file. This setting is now saved correctly.

[Global Traffic Manager] Multiple big3dshim instances (CR69166)
In previous releases, it was possible for multiple big3dshim instances to occur. This issue happened primarily when a Global Traffic Manager system was trying to control a Local Traffic Manager running a version earlier than 9.2.x. These multiple instances caused the Local Traffic Manager to be displayed as unavailable on Global Traffic Manager system. In this release, these multiple instances no longer occur.

[Global Traffic Manager] Probe requests and systems with multiple external interfaces (CR69316)
In earlier releases, Global Traffic Manager did not distribute probe requests to other systems that had multiple external interfaces when one interface was up and others were down. With this release, the system distributes probe requests to these systems using an available external interface.

[Global Traffic Manager/Link Controller] -all-ip option (CR69320)
With this release, we have added the -all-ip option to big3d so it can communicate with multiple self-IP addresses specified on the same VLAN. See the appropriate man page for more information.

[Global Traffic Manager] Performance when synchronizing large numbers of zone files (CR69461)
In previous releases, if you synchronized a large number of zone files, the system might fall into an unresponsive state. With this release, the system can handle synchronizing large numbers of zone files.

[Global Traffic Manager/Link Controller] Links for systems set with Unit ID 2 (CR69729)
Previously, if you attempted to add a link to a system with a Unit ID of 2, an error occurred. You can now add links to systems with a Unit ID of 2.

[Global Traffic Manager/Link Controller] Autodiscovery of self server (CR69733)
In earlier releases, when you enabled autodiscovery on a Link Controller, it did not discover its own system correctly. The system now adds itself to its configuration through autodiscovery.

[Global Traffic Manager] Deleted objects and corresponding persistence records (CR70253)
Previously, if you deleted an object in the Global Traffic Manager configuration, any persistence records associated with that object remained. With this release, deleting Global Traffic Manager objects now initiates the deletion of any corresponding persistence records.

[Global Traffic Manager] Communication through firewalls (CR70580)
In previous versions, if you had two Global Traffic Managers in a data center, with one inside a firewall and one outside, the two system did not communicate correctly with each other. With this release, the two systems communicate with each other as expected.

Version 9.2.3 fixes

[Link Controller] Throughput statistics unavailable (CR57647)
Previously, the Throughput statistics screen was unavailable in Link Controller. This screen is now available.

SNAT continuously using same SNAT pool member instead of load balancing (CR57636)
When you implemented SNAT, the system used the same SNAT pool member; it did not load balance between other pool members that might be available. The system now load balances across pool members correctly.

bigip_add and big3d_install processes sometimes acquire incorrect SSL certificate (CR59299)
In earlier versions, a BIG-IP system had multiple SSL certificates, the bigip_add and big3d_install processes could acquire the incorrect certificate, resulting in the Global Traffic Manager being unable to communicate with the other system. These scripts now acquire the correct certificate.

RTT score of 0 treated as a valid RTT score (CR57946)
In earlier versions, the system considered an RTT score of 0 as valid, allowing for the possibility that an unreachable LDNS server would have the highest RTT priority. An RTT score of 0 is no longer considered valid.

Uplink addresses not written to the wideip.conf file (CR59042)
Previously, the system did not write uplink addresses to the wideip.conf file correctly. The system now writes uplink addresses entered in the Configuration Utility to the wideip.conf file correctly.

big3d_install script removing big3dshim from the output of bigstart status (CR59165)
You can no longer start or the big3dshim utility directly. To start or stop the big3dshim utility, type the command bigstart <action> big3d.

[Global Traffic Manager] Configuration utility and deletion of all wide IP resources (CR58757)
Previously, the Configuration utility allowed you to delete all the pools/rules associated with the Wide IP without removing the Wide IP. This resulted in a wideip.conf file that cannot load. The system now does not allow you to delete the pools and rules associated with the wide IP without first removing the Wide IP itself.

[HF] Path probing protocols not passed to the big3d agent by the gtmd agent (CR57976)
In earlier versions, changing the default probing protocols resulted in the parameters not being passed to big3d agent properly. Parameters are now passed correctly to the big3d agent.

[Global Traffic Manager] ZoneRunner unresponsive after creating a new view and then a new forwarding zone (CR58751)
Previously, if you used ZoneRunner to create a new view and then a new forwarding zone, ZoneRunner became unresponsive. ZoneRunner can now handle the creation of a new view and the association of a new zone to that view.

Version 9.2.2 features

TMOS Architecture
BIG-IP Global Traffic Manager has been re-architected using TMOS as its building block. Now BIG-IP Global Traffic Manager can leverage the modularity, scalability and the intelligence of TMOS to provide organizations a way to solve distributed application challenges such as performance, security, high availability, and management with ease.

iRules
With this release of the Global Traffic Manager, you can use the iRule functionality similar to that available in the Local Traffic Manager to customize how the system handles your network traffic.

Application Specific Monitors
Through the Global Traffic Manager, you can now monitor a host of different application types, including LDAP, SIP, Oracle, MySQL, SOAP, SIP, and many others.

Pools
You can now configure and view pools at the top level without having to dig deeper under WideIPs.

ZoneRunner
The Global Traffic Manager now has an integrated Zone File Management Utility called ZoneRunner. This replaces the tool from NiXu, NameSurfer.

Distributed Applications
The Global Traffic Manager now provides a way of combining multiple Wide IPs into a distributed applications that you can manage from the user interface.

IPv6 Support
The Global Traffic Manager can now provide support for IPV6 AAAA records.

This release includes the following new features for the Link Controller:

TMOS Architecture
BIG-IP Global Traffic Manager has been re-architected using TMOS as its building block. Now BIG-IP Global Traffic Manager can leverage the modularity, scalability and the intelligence of TMOS to provide organizations a way to solve distributed application challenges such as performance, security, high availability, and management with ease.

Rate Shaping
You can now use the Link Controller to provide an efficient way for organizations to use the bandwidth on their WAN link efficiently and eliminate bandwidth starvation of mission critical applications by low priority applications.

Optional Compression
The Link Controller now supports an optional Compression module. Through this module, you can use the BIG-IP Link Controller V9.0 to intelligently compress traffic to boost bandwidth savings.

Composite Monitors
You can now use the Link Controller to combine multiple monitors to accurately determine the health and the availability of a link

Topology-based routing
You can now use the Link Controller to route traffic intelligently over multiple links based on the location of the user.

iRules
With this release of the Link Controller, you can use the iRule functionality similar to that available in the Local Traffic Manager to customize how the system handles your network traffic.

Optional IPv6 Gateway
The Link Controller now supports an optional module that provides IPv6 gateway support. Using this module, you can have the Link Controller translate between IPv6 and IPv4 addresses.

[ Top ]

Optional configuration changes

Once you have installed the software, you can use any of the following configuration options to update your configuration.

Using SNMP read/write OIDs

You can use the following SNMP OIDs in read/write mode. However, SNMP is not intended to be used as a general API for configuring the Global Traffic Manager or Link Controller. You can use the following SNMP OIDs in read/write mode.

OID Name OID Value
ltmVirtualServEnabled Enable/disable virtual server
ltmVirtualAddrEnabled Enable/disable virtual address
ltmNodeAddrNewSessionEnable Enable/disable node address
ltmNodeAddrMonitorState Force up/down node address
ltmPoolMemberNewSessionEnable Enable/disable pool member
ltmPoolMemberMonitorState Force up/down pool member
[ Top ]

New SNMP OIDs

The version 9.x releases often include SNMP OID updates related to new functionality. See the document, New SNMP Objects for a complete list.

[ Top ]

Using the switchboot utility

Beginning with the version 9.0.2 release, we added functionality to install multiple versions of the BIG-IP software on different boot images on one unit. A boot image is a portion of a drive with adequate space required for an installation. If the hardware supports multiple boot images, you are prompted to install the software on multiple boot images during the installation. The BIG-IP 1500 (C36), BIG-IP 3400 (C62), BIG-IP 6400 (D63), and BIG-IP 6800 (D68) platforms support this functionality.

The switchboot utility is available to manage installations on different boot images. You can use the switchboot utility from the command line to select which installed image boots.

To run the switchboot utility

  1. Type the following command:

    switchboot

    A list of boot images and their descriptions displays.
     
  2. Type the number of the boot image you want to boot at startup.

    When you reboot the system, it starts from the slot you specify.

If there is only one boot image available, the switchboot utility displays a message similar to this one and exits.

There is only one boot image to choose from: title BIG-IP 9.2.1 Build 167.4 - drive hda.1

Note: Any change you make using the switchboot utility is saved in the boot configuration file, grub.conf.

To use switchboot in non-interactive mode

If you know which boot image you want to boot, you can type the following command and specify the boot image number for <bootimage_number>:

switchboot -s <bootimage_number>

To use switchboot to list available boot images and the currently active boot images.

If you want to list the available boot images without specifying a new boot image from which to boot, type the following command:
switchboot -l

To list options for switchboot

To list the options for the switchboot utility, type the following command:
switchboot -h

To view the contents of the boot configuration file using switchboot

You can view the complete contents of the boot configuration file (grub.conf) with the following command:
switchboot -d

This command is slightly different from switchboot -l in that -l only lists the boot image header lines, while -d displays the complete file.

[ Top ]

Known issues

The following items are known issues in the current release. For platform-related or cross-product issues, please see the release notes for Local Traffic Manager version 9.2.5.

Command prompt for combination boxes indicates the system is active even if Global Traffic Manager configuration does not load (CR49178)
When you have a combination box (a system that contains more than one F5 module, such as both the Global Traffic Manager and the Local Traffic Manager), the command prompt for that system indicates that the system is active even if an error occurred when loading the Global Traffic Manager configuration files. We recommend that you verify the availability of any F5 system through the Configuration utility to ensure that all necessary components are installed and operational.

Setup utility does not provide an option to lock down all ports (CR52161)
If you decide to implement the port lockdown feature available through the Setup utility, you will notice that there is no user interface option that allows you to select all ports simultaneously. You can still select all ports manually.

Configuration utility does not support SSL certificates and keys that contain bracket characters (CR53446)
When adding certificates and keys to your Global Traffic Manager installation, you must ensure that each certificate and key does not contain brackets ([ and ]). If certificates or keys are added to the Global Traffic Manager that contain these characters, you can remove them through the Command Line Interface to prevent them from affecting the Configuration utility.

Configuration utility does not allow you to install an encrypted ucs file when the config.encryption value is off (CR54052)
In the Global Traffic Manager version 9.2.2, you cannot install an encrypted ucs file if you have set the config.encryption value to off. To install an encrypted ucs file, change the config.encryption value to on.

Unable to activate the configsync.encryption value in the Configuration utility if the config.encryption value is off (CR54446)
In the Configuration utility, when you disable the config.encryption value, the Configuration utility also hides the configsync.encryption values as well. This occurs even if you have turned off the config.encryption value, yet have not turned off the configsync.encryption value. You can still modify these variables through the command line interface.

Term "software reboot" is ambiguous (CR55012)
After licensing the Global Traffic Manager, the system requests that you perform a software reboot. This statement is intended to indicate that you should restart the system (such as through the command bigstart restart before moving the system into a production environment.

Unable to change a server's type after initial configuration (CR55355)
When you add a server into the Global Traffic Manager, you determine the server's type, such as a BIG-IP system, or a generic host. Once you assign a server type, you cannot change it. If you need to change a server's type, you must delete the old server and then add the new one with the correct type.

[Link Controller only] Cannot create a wide IP that only contains iRules (CR55484)
In the Link Controller, you get an error if you create a wide IP that contains only iRules for determining load balancing operations. You must add at least one pool to each wide IP in the Link Controller.

When Global Traffic Manager has not yet probed a path, the system displays its last probe time as 1969 (CR56008)
When a new path is added to the Global Traffic Manager, the system probes the path to determine its viability. Before the first probe occurs, the Configuration utility displays the last probe time for the path as 1969. If you see this value, it indicates that the Global Traffic Manager has not yet probed the path.

[Link Controller only] Status of a disabled link is not populated in the Link Statistics screen (CR56569)
If you disable a link in the Link Controller, the system will stop sending traffic through the link. However, the Links Statistics screen does not update; instead, it shows the last set of data acquired before the link was disabled.

ZoneRunner utility does not remove database files referencing deleted zones (CR 56597)
When you delete a zone from ZoneRunner, one of its utilities, zrd, does not delete the referencing database files. This issue does not impact performance.

Selecting Advanced from the Configuration list in the Links screen does not persist (CR56677)
After you select Advanced from the Configuration list in the Links screen, you have access to more advanced link configuration options. When you click the Update button, the screen refreshes to display only the basic options. To review the advanced options, re-select Advanced from the Configuration list again.

Updating the Name Server name on an NS record results in two NS records (CR56794)
The first time you update a Name Server name on an NS record, ZoneRunner adds the changed NS record as a new record and does not delete the old one. This prevents the ZoneRunner from creating an invalid zone that does not contain an NS record. To resolve this issue, delete the old NS record after the new one is created.

Cannot set a prepaid segment to 0 (CR57031)
When you are configuring prepaid segments for a link, you must specific a positive value. If you do not, an error appears, informing you that the prepaid value and the prepaid limit do not match.

Server status message metrics is inconsistent between 9.2.2 big3d and 4.6.4 big3d (CR57162)
In version 9.2.2, the bytes in and bytes out metrics are determined by dividing the total bytes value by 2. Consequently, the values for these two metrics will always be identical. This metrics change does not impact metrics collection or performance on either the 9.2.2 system or the 4.6.4 system.

Configuration utility can cease to function if the /var directory fills up (CR57265)
In instances where an extremely large amount of debugging information is generated, the /var directory can grow too large for the system to handle. See Workarounds for known issues for assistance with this issue. In environments where debugging is inactive, this issue does not occur.

Include statements configured with the ZoneRunner utility require a path of /config/namedb (CR57497)
If you are using ZoneRunner to manage your domains and you elect to use include statements, the files you reference in each include statement must reside somewhere within the /var/named directory. The path you supply in the include statement must include the path from this directory. For example, if you want to include a file that resides in /var/named/myzones/firstzone/main.file, the file path for the include statement would be /myzones/firstzone/main.file.

In addition, if you elect to modify files manually (instead of using ZoneRunner), you must ensure that you place any include statements at the top of the file. If you do not, the include statement might not get read correctly by ZoneRunner.

We highly recommend that if you use ZoneRunner to manage your domains, you use only the ZoneRunner user interface to make modifications to any files.

System doubles the monitors assigned to a virtual server and pool level (CR57646)
If you create a generic host virtual server, and have that server monitored at both the virtual server and pool level, the system assigns twice the number of monitors to that resource. To resolve this issue, deactivate monitoring of this virtual server at either the virtual server or pool level.

[Global Traffic Manager only] Monitor list for pool members does not initially appear in the properties screen (CR57724)
When you add monitors to pool members in a given pool, the monitors are assigned through the Global Traffic Manager to the specified resource. When you return to one of these pool members, the properties screen does not initially display the list of assigned monitors. To update the properties screen to display these monitors, select modify a monitor-related setting in the screen.

[Link Controller] Disabled auto-discovery feature marks all links as down. (CR59052)
The Link Controller uses an auto-discovery feature to manage and maintain links. You can access this feature from the Main tab of the navigation pane by expanding System, clicking General Properties, and then choosing General from the Global Traffic menu. If you disable this feature, the Link Controller marks all links as down and is unable to manage traffic. We recommend that you do not de-activate this feature.

[Global Traffic Manager] Deleting multiple zone types at once through ZoneRunner restarts named (CR59093)
If you attempt to delete multiple zone files from the ZoneRunner component of the Global Traffic Manager, the named utility restarts, and an error message appears. To work around this issue, delete only one zone file at a time from the ZoneRunner user interface.

[Global Traffic Manager] In Internet Explorer, check boxes do not automatically update until the check box loses focus (CR59191)
When managing zone files through the ZoneRunner in Internet Explorer, two check boxes change the appearance of the user interface: Create Reverse Zone and Create A Record. These check boxes prompt the addition of other configuration options. In Internet Explorer, these additional options do not appear until you clear the check box.

[Link Controller] Maximum Addresses Returned / Round Robin LDNS is not configurable in Link Controller (CR59781)
The feature Maximum Addresses Returned (formerly known as Round Robin LDNS) cannot be configured in LC via the UI or CLI.

[Link Controller] Maximum Addresses Returned / Round Robin LDNS is not configurable in Link Controller (CR59781)
The feature Maximum Addresses Returned (formerly known as Round Robin LDNS) cannot be configured in Link Controller using the user interface or command-line interface.

[Global Traffic Manager/Link Controller] qkview utility does not display configuration data for topologies or regions (CR60559)
When you run the qkview utility, the system attempts to look in directories that were previously valid for 3-DNS Controller, but changed with the introduction of Global Traffic Manager 9.2.2. This results in a message saying that the configuration data for these objects cannot be found.

[Global Traffic Manager] ZoneRunner inaccessible with match-destination clauses in views (CR61046)
If you use match-destination clauses in your BIND configuration, ZoneRunner requires that you add the following line:

zrd-acl-xxx-xxx

Where xxx-xxx being consecutive numerical sequence unique to each clause, starting with 000-000. For example, the first match-destination clause contains zrd-acl-000-000, the second zrd-acl-000-001, and so on.

[Global Traffic Manager/Link Controller] Configuration utility does not always reflect contents of wideip.conf file (CR62382)
Some instances exist in which the communication between the Configuration utility and other system utilities fall out of synchronization, resulting in the Configuration utility displaying incorrect information. This situation occurs very infrequently, and typically resolves itself within a short period of time.

[Link Controller] Remote virtual servers show status of up instead of unknown (CR63647)
If your system configuration includes remote virtual servers, those virtual servers appear green, indicating an up status. In fact, these virtual servers should appear gray, indicating a remote status.

[Global Traffic Manager] Global Traffic Manager-only licensed systems cannot access certificate management screens in the Configuration utility (CR63730)
If the system is licensed only for Global Traffic Manager, the certificate management screens in the Configuration utility are unavailable. You must update these certificates through the command line interface.

[Global Traffic Manager/Link Controller] Synchronization and backup files (CR64376)
When synchronizing files, Global Traffic Manager creates backups of each file, which it then backs up again during the next synchronization.

[Global Traffic Manager/Link Controller] Probing unavailable resources and log files (CR65113)
If the system generates a connection failed message, that message appears as a notice level log, causing log files to fill when these messages occur. These messages do not necessarily indicate a problem with the system.

[Global Traffic Manager] Windows® 2000 server object in the Configuration utility creates a Windows NT object in the configuration file (CR65293)
When you use the Configuration utility to create a Windows® 2000 server object, the configuration file is incorrectly written out as a Windows® NT server object. These designations do not impact the performance of the product.

[Global Traffic Manager/Link Controller] Restart if gtm_add script fails to connect to the other Global Traffic Manager (CR65477)
If the gtm_add script fails for any reason, it does not restart the appropriate services to return the system to a functional state. You must restart the system manually using the command, bigstart start gtmd named.

[Global Traffic Manager/Link Controller] iRule command, LB::status, before the command, LB::selected (CR65522)
The LB::status command must be called after the LB::selected command; otherwise, the system fails, resulting in a system restart.

[Global Traffic Manager]SNMP query for application context status does not contain application name (CR66454)
An issue exists when an SNMP walk is done on the entire Global Traffic Manager application or the application name was omitted when requesting statistics for the Global Traffic Manager application context. This results in the error message being logged in the /var/log/Global Traffic Manager log file.

[Global Traffic Manager/Link Controller] Topology records containing ampersands (&) (CR66566)
Topology Regions containing ampersands (&) cannot be deleted from user interface. If you have a topology with & in it, you must remove the & from the name of a user-specified Topology Region by editing the /config/Global Traffic Manager/region.user file, and then to run the gtmparse -l command from the console.

[Global Traffic Manager] Misapplied monitors and disappearance of Global Traffic Manager configuration (CR66576)
If you create a monitor to check a specific port, assign that monitor to a server with a wildcard virtual server, and restart the system, your Global Traffic settings do not appear in the Configuration utility, and incoming DNS requests are sent to BIND. To return your configuration to a functional state, you must open the wideip.conf file, locate and remove the monitor entry, and then run the gtmrparse -1 command from the console, verifying that gtmparse does not return any errors.

[Link Controller] Incorrect link in Paths Statistics page (CR66594)
In the Path Statistics section of the Configuration utility, selecting a specific link directs you to a non-existent HTML page.

[Global Traffic Manager] Forwarding zone with a zone type of forward only, forwarder statements, and ZoneRunner to stop functioning (CR66847)
If you create a forwarding zone in ZoneRunner, you must save the zone before you add any forwarder statements to the zone. Otherwise, ZoneRunner stops functioning.

[Global Traffic Manager/Link Controller] The attribute probe_num_successes in the wideip.conf file and Global Traffic Manager monitors (CR67180)
In the wideip.conf file, the attribute probe_num_successes appears as an option for some monitors. This attribute does not apply to Global Traffic Manager monitors and has no affect on system performance.

[Global Traffic Manager] Member-specific monitor on Pool Member Properties page (CR68603)
The Configuration utility displays the monitor assigned to another pool member with the same IP address with the lowest port number as the currently selected member-specific health monitor. However, this is not always the correct monitor to display. This can cause the incorrect monitor do be associated with the pool member if the you click the Finished button on the member's properties page. You can restore the required association by returning to the properties page, selecting the appropriate member from the list, and clicking Finished again.

[Global Traffic Manager] Journal file error causes ZoneRunner to shut down (CR68608)
If named discovers that the journal file has gotten out of synchronization, it generates an error, which in turn causes ZoneRunner to shut down. To reactivate ZoneRunner, use the following commands to remove the journal file:

bigstart stop named
bigstart stop zrd
rm <journal file name>
bigstart start named
bigstart start zrd

[Global Traffic Manager/Link Controller] Invalid monitors can be assigned to links (CR68663)
The Configuration utility displays monitors that are invalid when assigned to links. The only valid monitors for links are: bigip_link and gateway_icmp.

[Global Traffic Manager] LDNS records that refer to non-existing objects cause system failure (CR68883)
If an LDNS record refers to an object, such as virtual server, that does not exist, the Global Traffic Manager system fails. We recommend you do not delete objects unless you are sure that they are not referenced by any LDNS records.

[Global Traffic Manager] snmp_link monitor fails if index returned is unrecognized (CR69494)
Certain routers, when queried by the snmp_link monitor, do not return a valid interface index. This results in the monitor marking the link as down, which may not be the case. To resolve this issue, you can set the Version option of the monitor to v2.

[Global Traffic Manager] Dependency setting for distributed applications affects wide IPs (CR69974)
If a wide IP in a distributed application is unavailable, it causes the distributed application associated with that wide IP to also become unavailable, even if the Dependency Level option is set to None.

9.1.x hotfixes overwrite 9.2.x big3d agent that Global Traffic Manager installed (CR70143)
A hotfix installed on a 9.1.x Local Traffic Manager BIG-IP system can overwrite a 9.2.x big3d that was installed on that system by a Global Traffic Manager. This results in the Global Traffic Manager marking the Local Traffic Manager as down after it loses its iQuery connection. A workaround is to rerun the big3d_install command on the Global Traffic Manager unit after the upgrade.

[Global Traffic Manager] ZoneRunner view, external, must always be first view (CR70262)
When you create a new view in ZoneRunner and then create a new Resource Record, an error occurs. When you create a new view, that view must follow the external view in the list. If it comes before the external view, ZoneRunner generates an error. You can work around this issue by changing the name of the external view, saving your changes, and then changing it back.

[Global Traffic Manager] Radware probe not mapped correctly (CR70387)
When probing a Radware system with SNMP, the Radware OIDs are not mapped correctly when the probe data returns.

[Global Traffic Manager/Link Controller] Large configurations can cause links to change status incorrectly (CR70544)
In large configurations, using the bigip_link monitor when no server on the link has virtual server discovery enabled can inadvertently cause other links to appears offline temporarily. These links return to their online status within approximately 60 seconds.

[Global Traffic Manager] ZoneRunner does not read zone files that use the SPACE or TAB shortcut notation for domain names (CR70555)
The ZoneRunner utility does not read zone files that use the SPACE or TAB shortcut notation for domain names. We recommend that you update your zone files without this notation before importing the zone files into ZoneRunner.

[Global Traffic Manager] System does not validate when applying a bigip_link monitor (CR70600)
If you assign the bigip_monitor to a link that has only disabled virtual servers associated with it, you do not get a validation error, although this configuration is not supported with this monitor.

[ Top ]

Workarounds for known issues

The following section describes a workaround for the corresponding known issue listed in the previous section.

Resolving issues with the /var directory (CR57265)

You can work around this issue by deleting the log files within the /var directory. To delete these log files, use the following steps:

  1. From the command line, type du -h /var.
     
  2. Identify the largest log file in the directory.
     
  3. Delete the log file.
     
  4. From the command line, type bigstart restart syslog.
     
  5. Optionally, remove the file SESSIONS.ser from the /var/cache/tomcat4/work/StandAlone/localhost/tmui, if it exists.
     
  6. From the command line, type bigstart restart tomcat4.

Note that log files are swept every 30 minutes. For this issue to occur, the log files would have to fill up the available space on the system in less than 30 minutes.

[ Top ]

Acknowledgments

This product includes software developed by Gabriel Forté.
This product includes software developed by Bill Paul.
This product includes software developed by Jonathan Stone.
This product includes software developed by Manuel Bouyer.
This product includes software developed by Paul Richards.
This product includes software developed by the NetBSD Foundation, Inc. and its contributors.
This product includes software developed by the Politecnico di Torino, and its contributors.
This product includes software developed by the Swedish Institute of Computer Science and its contributors.
This product includes software developed by the University of California, Berkeley and its contributors.
This product includes software developed by the Computer Systems Engineering Group at the Lawrence Berkeley Laboratory.
This product includes software developed by Christopher G. Demetriou for the NetBSD Project.
This product includes software developed by Adam Glass.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Dean Huxley.
This product includes software developed by John Kohl.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Herb Peyerl.
This product includes software developed by Jochen Pohl for the NetBSD Project.
This product includes software developed by Chris Provenzano.
This product includes software developed by Theo de Raadt.
This product includes software developed by David Muir Sharnoff.
This product includes software developed by SigmaSoft, Th. Lockert.
This product includes software developed for the NetBSD Project by Jason R. Thorpe.
This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com.
This product includes software developed for the NetBSD Project by Frank Van der Linden.
This product includes software developed for the NetBSD Project by John M. Vinopal.
This product includes software developed by Christos Zoulas.
This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman.
In the following statement, "This software" refers to the Mitsumi CD-ROM driver: This software was developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. "Similar operating systems" includes mainly non-profit oriented systems for research and education, including but not restricted to "NetBSD," "FreeBSD," "Mach" (by CMU).
This product includes software developed by the Apache Group for use in the Apache HTTP server project (http://www.apache.org/).
This product includes software licensed from Richard H. Porter under the GNU Library General Public License (© 1998, Red Hat Software), www.gnu.org/copyleft/lgpl.html.
This product includes the standard version of Perl software licensed under the Perl Artistic License (© 1997, 1998 Tom Christiansen and Nathan Torkington). All rights reserved. You may find the most current standard version of Perl at http://www.perl.com.
This product includes software developed by Jared Minch.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product contains software based on oprofile, which is protected under the GNU Public License.
This product includes RRDtool software developed by Tobi Oetiker (http://www.rrdtool.com/index.html) and licensed under the GNU General Public License.
This product contains software licensed from Dr. Brian Gladman under the GNU General Public License (GPL).
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes Hypersonic SQL.
This product contains software developed by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and others.
This product includes software developed by the Internet Software Consortium.
This product includes software developed by Nominum, Inc. (http://www.nominum.com).
This product contains software developed by Broadcom Corporation, which is protected under the GNU Public License.

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