Applies To:

Show Versions Show Versions

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

Updated Date: 12/11/2013

Summary:

This release note documents the version 9.3.1 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 Fixes and enhancements in this release. 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, and to systems running version 9.0.5 through 9.2.5. 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, and to systems running version 9.0.5 through 9.2.5. Note that you cannot apply this upgrade to systems running BIG-IP version 9.0 through 9.0.4 software. You must first upgrade to version 9.0.5 through 9.2.5.) 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 Networks 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 Microsoft Windows hosted installation
     - Performing a USB mass storage device installation
     - Performing a local installation
     - Performing a PXE server installation
     - Performing a remote installation
- Verifying the MD5 checksum of the installation file
- Re-activating the license on the BIG-IP system
- Fixes and enhancements in this release
     - Enhancements in this release
     - Fixes in this release
- Optional configuration changes
     - Using SNMP read/write OIDs
     - New SNMP OIDs
     - Using the switchboot utility
- Known issues
- Workarounds for known issues
     - Resolving issues with the /var directory (CR57265)

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 Knowledge Base web site.

[ Top ]



 

Minimum system requirements and supported browsers

The minimum system requirements for this release are:

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

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

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 Configuration utility. If you experience issues with navigation, we recommend that you disable these types of browser plug-ins and add-ons.

[ Top ]



 

Supported platforms

This release supports the following platforms:

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

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.3.1 software installation. Before you begin the installation process, you need to determine which installation option is appropriate: local, PXE server, or remote.

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

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

Important: You cannot upgrade to version 9.3.1 from versions 9.0 through 9.0.4. You must first upgrade to 9.0.5, or a later 9.x release.

Warning: You must turn off mirroring before you attempt to upgrade to version 9.3.1. 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 unit 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 installation file.

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

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

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.

Performing a Microsoft Windows hosted installation

Before performing Microsoft® Windows® hosted installation, read the following information.

Performing a USB mass storage device installation

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

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

Performing a local installation

Before performing a local installation, read the following information.

Important: You cannot upgrade to version 9.3.1 from versions 9.0 through 9.0.4. You must first upgrade to 9.0.5, or a later 9.x release.

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 installation file

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

md5sum local-install-9.3.1.<build_number>.im
cat local-install-9.3.1.<build_number>.im.md5

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

[ Top ]



 

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.

Note: If you create a stand-alone Global Traffic Manager installation or a Local Traffic Manager/Global Traffic Manager installation, 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.

[ Top ]



 

Fixes and enhancements in this release

This release includes the following fixes and enhancements.

Enhancements in this release

This release contains the following enhancements:

  • Underscores allowed in resource record names
    The ZoneRunner utility in the Global Traffic Manager system now supports underscore characters ( _ ) in wide IP names and A/AAAA records.
  • [Global Traffic Manager]: iQuery certificate expiration Warning:
    The imminent expiration (within 30 days) of certificates used in iQuery connections to or from the gtmd and big3d now generates an advance warning. The warning message contains the offending unit's IP address and the certificate expiration date (in Global Traffic Manager ). Once the certificate has expired, the customer continues to receive a warning message. These warnings are sent to syslog (seen using the /var/log/gtm file), and also triggers SNMP traps.

Fixes in this release

This release contains the following fixes.

[Global Traffic Manager] gtmd sends probes for translated virtual servers to an unconnected self IP address (CR61003)
When probing BIG-IP system translated virtual servers, the Global Traffic Manager now attempts to select a self IP address to which the Global Traffic Manager is already connected, rather than selecting the first self IP address it detects on the link.

[Global Traffic Manager] Provide means for setting GTM_TOTAL_SIZE to control ldns reaping (CR69683)
We have added the GTM.MaxSize database variable to let the user control the size at which aggressive reaping of DNS records and path and persistence records takes place. The new default maximum size is 128 megabytes (the same default maximum as in previous releases).

[Global Traffic Manager] Allow underscore in resource record names (CR72770)
ZoneRunner now allows underscores ( _ ) in Global Traffic Manager wide IP names and A/AAAA records as well as allowing any character the user wants to use in other records.

[Global Traffic Manager] Allow slash (/) in names for classless in-addr.arpa. delegation (CR73425)
The ZoneRunner utility now allows slashes in Zone Names or Resource Record Names to support classless in-addr.arpa delegation as defined in RFC2317.

[Global Traffic Manager] ZoneRunner times-out syncing zones after gtm_add is run against two IP addresses (CR73583)
With this version, ZoneRunner more reliably syncs zones between multiple Global Traffic Manager systems.

[Global Traffic Manager] Sync process can get stuck causing continuous configuration syncing (CR77929)
We have corrected a problem with multiple Global Traffic Manager systems (three or more), where one of the systems continuously tried to sync its configuration with the other Global Traffic Manager systems.

[Global Traffic Manager] Persist sync traffic with multiple systems can exceed iQuery read and write bufs (CR78495)
Persistence record syncing is now rate-limited to ensure that records are more consistently transferred to multiple Global Traffic Manager systems.

[Global Traffic Manager] Global Traffic Manager server with translated IP causes gtmd core and continuous restart (CR78721)
GTM no longer crashes when user is adding a server with a translated IP address.

[Global Traffic Manager] SQL exception when updating Global Traffic Manager pools (CR78767)
Updating a Global Traffic Manager pool member from the Configuration utility no longer generates SQL exception errors.

[Global Traffic Manager] RTT, Completion Rate path metrics are set to 0 for IPv6 ldns clients (CR79408)
Global Traffic Manager now correctly performs IPV6 path probes.

[Global Traffic Manager] Global availability load balancing mode and member order (CR79808) Global Traffic Manager pool members are no longer reordered inadvertently during a configuration load.

[Global Traffic Manager] Topology on Wide IP does not work with destination set to Region of Pools (CR80154)
The Topology load balancing method on a Global Traffic Manager Wide IP level now works with topology records that are set to destinations with regions containing pools.

[Global Traffic Manager] BIND vulnerability (CR83397)
Previous versions included a flaw in the way the Internet Systems Consortium, Inc. (ISC) Berkeley Internet Name Domain (BIND) software versions 9.0 through 9.5.0a5 generate outbound DNS query IDs. This vulnerability affected only BIND servers. This version corrects the flaw The Common Vulnerabilities and Exposures (CVE) project assigned the ID CVE-2007-2926 to the problem. For more information about the vulnerability, see CVE-2007-2926.

[Global Traffic Manager] Target name for PTR records (CR85072)
When displaying a pointer (PTR) record in the properties view, clicking update no longer creates a false PTR record. Now, the system displays the correct target.

[Global Traffic Manager] bigip_link probes should get stats from node address and gateway pool member (CR85292)
The Global Traffic Manager BIG-IP monitor probes now gathers link statistic data from the node address in addition to the status of the gateway pool member.

[Global Traffic Manager] Single Global Traffic Manager may consume large amounts of memory (CR85608)
Previously, a single Global Traffic Manager could consume large amounts of memory. Now, the Global Traffic Manager built-in memory monitoring functionality works effectively, even if only a single Global Traffic Manager server is specified in the configuration.

[Global Traffic Manager] Add automatic rate limiting to path probing (CR86554)
We have added automatic rate limiting of gtmd path probing. This restricts the sending of path probes if the delay associated with completing path probes exceeds a specified global time limit.

[Global Traffic Manager] Gtmparse fails (SIGSEGV) when 4.x config has pool member or wide IP disabled (CR86578)
The gtmparse utility no longer crashes while migrating a 4.x configuration to a 9.x configuration containing disabled wide IPs.

[ZoneRunner] ZRD does not allow detail view of TXT RR containing ";" (CR86676)
In previous versions, ZRD did not allow a detail view when the user selected a TXT record in a list view that contained a comma ( , ) in the RDATA portion of the record. We have corrected that issue, and you can now use a detail view in those circumstances.

[Global Traffic Manager] gtmd and big3d notifying customer about cert expiration (CR87209)
The imminent expiration (within 30 days) of certificates used in iQuery connections to or from gtmd and big3d now generates an advance warning. The warning message contains the offending unit's IP address and the certificate expiration date (in Global Traffic Manager). Once the certificate has expired, the customer continues to receive a warning message with the offending unit's IP address. These warnings are sent to syslog (seen using /var/log/gtm), and also triggers SNMP traps.

[ 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), BIG-IP 6800 (D68), and BIG-IP 8400 (D84) 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.3.1 Build <number> - 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.

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.3.1.

[Global Traffic Manager] System active indication with failed Global Traffic Manager configuration load (CR49178)
When you have a Global Traffic Manager-only installation, the command prompt for that system indicates that the system is active even if an error occurred when loading the wideip.conf file. 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.

[Global Traffic Manager] Setup utility and selecting all ports (CR52161)
If you decide to implement the port lockdown feature available through the Setup utility, you cannot initially set the Port Lockdown to allow for all ports. After you finish using the Setup utility, you can access the self IP address in the Configuration utility and change the Port Lockdown setting to Allow All.

[Global Traffic Manager/Link Controller] SSL certificates and keys containing bracket characters (CR53446)
When adding SSL certificates and keys to your Global Traffic Manager installation, you must ensure that each certificate and key does not contain brackets ([ and ]). If you add certificates or keys that contain these characters, you can remove them through the command line interface to prevent them from affecting the Configuration utility.

[Global Traffic Manager] Encrypted UCS file and config.encryption value of off (CR54052)
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.

[Link Controller] Hidden configsync.encryption values in the Configuration utility (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.

[Global Traffic Manager] Server type change restriction (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] Synchronizing Link Controllers and Global Traffic Managers. (CR55484)
At this time, we do not recommend that you put Link Controllers into the same synchronization group as Global Traffic Manager, as these are two different products with different roles on the network.

[Global Traffic Manager] Last probe time of new path as 1969 (CR56008)
When Global Traffic Manager has not yet probed a path, the system displays its last probe time as 1969. 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.

[Global Traffic Manager] Server status message metrics differences between big3d versions 9.2.2 and 4.6.4 (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 are always identical. This metrics change does not impact metrics collection or performance on either the 9.2.2 system or the 4.6.4 system.

[Global Traffic Manager] Full /var directory and Configuration utility halt (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.

[Global Traffic Manager] Path requirement for include statements configured with the ZoneRunner (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.

[Global Traffic Manager] System doubling of 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] Initial appearance of monitor list for pool members 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 a monitor-related setting in the screen.

[Global Traffic Manager/Link Controller] Disabled auto-discovery feature and link 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 links stay available until after next reboot, after which time the Link Controller marks all links as down and is unable to manage traffic. After re-enabling the auto-discovery feature, the links are available immediately. We recommend that you do not de-activate this feature.

[Global Traffic Manager] Multiple zone type delete in ZoneRunner and named restart (CR59093)
If you attempt to delete multiple zones 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 at a time from the ZoneRunner user interface.

[Global Traffic Manager] Named and snmpd utilities restart after running commands (CR59131)
After running the b config sync, b config save <savename>, or b config install <installname> commands, you might see erroneous-looking named and snmpd restart messages. The named restart message appears similar to the following:

Feb 1 09:42:52 d84unit1 zrd: 01150c10:3: Error 'No such file or directory'
from stat of '/var/named/config/named.conf

These messages are benign, and you can safely ignore them.

[Global Traffic Manager] Option display with ZoneRunner in Internet Explorer (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.

[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 run the gtmparse -l command from the console.

[Global Traffic Manager] Missing configuration with monitors on wildcard virtual server (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 gtmparse -1 command from the console, verifying that gtmparse does not return any errors.

[Global Traffic Manager/Link Controller] probe_num_successes attribute in the wideip.conf file (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 effect on system performance.

[Global Traffic Manager] Monitor none and unavailable pools (CR67581)
When you are working with pools, we do not recommended that you select the none monitor, as this monitor immediately marks the pool red, or unavailable. The none monitor is present in the Health Monitors list on the Global Traffic Pools screen to be as consistent as possible with the Local Traffic Manager implementation of monitors. In Local Traffic Manager the monitor none is a special monitor that serves as a placeholder to allow to intentionally have the system not monitor a specific pool member.
With Global Traffic Manger, the system cannot set the status to unknown when you assign the monitor none; in the case of Global Traffic Manager, a pool member with an unknown state does not receive any traffic. In order to be functionally consistent with Local Traffic Manager, an object in Global Traffic Manager that is assigned the monitor none should have its monitor instance set to the green, or available state. That does not occur in this release. Instead, the system sets the status to red, or unavailable.

[ZoneRunner] Backslash character in Email Contact field for Start of Authority record (CR68353)
The system should support the backslash ( \ ) character in the Email Contact field for an SOA record. Using the backslash character prevents the first period ( . ) in an email name from being recognized as the at sign ( @ ). Currently, the system does not support the backslash character.

[Global Traffic Manager] Journal file error and ZoneRunner shutdown (CR68608)
If the named utility 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] Translated server addresses and gtmd restart (CR68682)
Adding a server that uses a translated IP address causes the gtmd process to core and continuously restart. For more information, see SOL7482: Adding a server that uses a translated IP address to the BIG-IP GTM causes the gtmd process to core and continuously restart.

[Global Traffic Manager] big3d probe queues using over 512MB of memory (CR71516)
This problem might occur only on BIG-IP 3400 systems. When the system is operating very close to the threshold (512MB) of what the unit can handle, a log roll-up operation might push the unit over the limit. When this occurs, the system distributes queues evenly to all big3d agents, as opposed to selecting the agent with the fewest probe requests in its queue.

[Global Traffic Manager] Link Capacity upper limit (CR73148)
The maximum value for Link Capacity in the Quality of Service (QOS) load balancing method, as limited by the browser-based Configuration utility, is 2147483647. The system limit for QOS values should be 4294967295. There is no workaround for this issue.

[Global Traffic Manager] Nonexistent IP address for server prober (CR74186)
If you manually edit the wideip.conf file to have the Global Traffic Manager object defined after the server object, when you configure the server's prober IP address as the Global Traffic Manager system's IP address, a warning appears when you issue the gtmparse or gtmload command. To work around this issue, make sure to define the Global Traffic Manager object before other server objects in the wideip.conf file.

[Global Traffic Manager] Duplicate virtual server name during create or modify (CR74789)
You can create two virtual servers with the same name, but the system removes the duplicate when the configuration is written to the wideip.conf file. In this case, the second virtual server effectively has no name specified. To work around this issue, make sure each virtual server you create has a unique name.

[Global Traffic Manager] Duplicate virtual server name during auto-discovery (CR74792)
When adding a Local Traffic Manager to a Global Traffic Manager configuration, the auto-discovery process has no mechanism for catching virtual server names for other hosts that already exist in the wideip.conf file, so the process does not add the duplicate virtual server name. You can work around this issue by adding the appropriate server name to the virtual server name that already exists, or by renaming the virtual servers on the other device so that all names are unique.

[Global Traffic Manager] qkview should not capture entire ldns.gz file (CR74876)
The current qkview tool gathers all files under the /config/gtm directory, including the ldns.gz file. This file can get rather large, since it contains the known LDNS list.

[Global Traffic Manager] LB::status pool my_pool member 10.0.10.82 80 down won't parse (CR76723)
Using the iRule statement LB::status pool | node results in MCP and gtmd syntax errors. The system should require you to specify the pool name in this case. The workaround is to use LB::status vs.

[Global Traffic Manager] Persist when persist pool member is unknown (CR76866)
At startup time, the gtmd process invalidates persist entries if the persist pool member is unknown, as denoted by a blue icon.

[Global Traffic Manager] Gtmd fails when disabled link is deleted and virtual servers are disabled by parent (CR79212)
Gtmd fails when a disabled link is deleted if there are virtual servers present on that link. In order to avoid this issue, make sure that link is enabled before deleting it.

[Global Traffic Manager] Topology records with IPv6 addresses and netmasks greater than 32-bits cannot be created in the Configuration utility (CR79322)
Topology records for an IPv6 address cannot be created using the Configuration utility if the supplied subnet mask is greater than 32. You can work around his issue by creating a topology record with 32-bit mask first. Then, you can change the mask to the desired length by manually editing the /config/gtm/topology.inc file and by running the gtmparse -l command after that.

[Global Traffic Manager] custom SNMP monitor and specified Port or Alias Service Port settings (CR80104)
The Global Traffic Manager GTM custom SNMP monitor always uses default port 161 for probing. It ignores the custom Port and Alias Service Port settings.

[Global Traffic Manager] The -c option for big3d fails to load certificate level (CR80361)
Big3d does not use the [-c <0-9>] option to set a required certificate depth. The better method of setting the certificate depth is to use the b db Big3d.CertificateDepth bigpipe command.

[Global Traffic Manager] Big3d does not correctly acquire the certificate depth without a connection (CR80402)
Big3d on a Local Traffic Manager may fail to obtain a user-defined certificate depth setting configured on a Global Traffic Manager. In order to avoid this issue, consider adding a Local Traffic Manager to the Global Traffic Manager configuration prior to changing the certificate depth setting on the Global Traffic Manager.

[Global Traffic Manager] Behavior of ANY query type with A/AAAA and CNAME records (CR80405)
Global Traffic Manager does not respond correctly to DNS ANY queries.

[Global Traffic Manager] ACL Threshold and Respect Fallback ACL improperly named and documented (CR80561)
The Global Traffic Manager setting ACL Threshold is improperly labeled. It is, in fact, a "Topology Threshold". If you use it to set a number greater than 0, then the system ignores all topology records with weights lower than the topology threshold.

[Global Traffic Manager] probe_interval is not being passed to big3d pinger monitors (CR81368)
Global Traffic Manager monitors do not honor the user-defined Probe Interval setting, instead they use the default setting.

[Global Traffic Manager] Selecting RADIUS type monitor results in an immediate error (CR82051)
Selecting type RADIUS from the Configuration utility Monitor menu during a Global Traffic Manager monitor creation generates an error.

[Global Traffic Manager] GTM bigip_link monitor does not handle address translation on links (CR82153)
The bigip_link monitor does not work on links with translated addresses. If a link has address translation enabled, we recommend using a gateway_icmp monitor on it as a workaround.

[Link Controller] LC auto-configure deletes self IP with link name and no matching gateway member (CR82635)
Link Discovery removes a user-defined link if the link does not have a matching default gateway pool member. If this behavior is undesirable, we recommend that you disable Link Discovery.

[Global Traffic Manager] gtm_add needs to stop zrd before syncing operations (CR82646)
On rare occasions, running gtm_add script may cause a sync_zones script failure message. If this happens, stop zrd (bigstart stop zrd) on the Global Traffic Manager where the gtm_add script was executed and re-run the gtm _add script one more time. Running the bigstart start zrd command after that should synchronize the zone information between the Global Traffic Manager systems.

[ZoneRunner] HINT zones (CR83505)
When a HINT zone is configured on a Global Traffic Manager ZoneRunner attempts to query it every time when 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.

[Link Controller] Virtual server link names not set in mcpd db for new virtual servers, or after gtmparse (CR83832)
Virtual servers may fail to display an associated link in its properties. This may happen on a Local Traffic Manager or Link Controller. This is a cosmetic issue that does not affect performance.
 

[Global Traffic Manager] Inadequate space between certificates causes big3d to continually restart (CR84524)
Multiple certificates added to the /config/big3d/client.crt and /config/gtm/server.crt files are designed to use the "\n" character as a separator. If there is no "\n" character present between any two certificates, big3d may restart continuously.

[Global Traffic Manager] GTM FTP monitor always marks FTP IPv6 server down (CR84785)
Global Traffic Manager FTP monitors do not work with IPv6 FTP servers.

[Global Traffic Manager] Changes in zone files on redundant system configuration are not saved correctly (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.

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



 

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)