Solution: BIG-IP software support policy

Fri, 03 Jul 2009 22:52:10 -0700

(SOL5903) For the F5 Networks software support policy for other F5 Networks products,refer to SOL8651: Software Support Policy for F5 Networks. The following versions of BIG-IP software are currently supported with active development: Software VersionBranch Version Type

Solution: Support for Firefox 3.5

Thu, 02 Jul 2009 10:51:44 -0700

(SOL10256) Mozilla Firefox 3.5 was released on June 30th, 2009. FirePass and BIG-IP SAM do not currently support FireFox 3.5; however, F5 Networks will shortly issue hotfixes for the following products and versions: FirePass version 6.0.2 FirePass version 6.0.3 BIG-IP SAM version 8.0 Important: FirePass versions prior to version 6.0.2 will not support Firefox 3.5. Note: For more information about Firefox 3.5, refer to http://www.firefox.com.

Solution: Obtaining a longer serial failover cable for BIG-IP, BIG-IP LTM, GTM, ASM, WebAccelerator, Link Controller, or 3-DNS

Thu, 02 Jul 2009 10:32:25 -0700

(SOL1901) F5 Networks stocks a range of replacement hardware failover cables in lengths of 6, 10, 15, 20, 30, and 50 feet. To purchase additional cable, contact your F5 Networks Sales Representative.

Solution: Troubleshooting and debugging Enterprise Manager iControl connectivity

Thu, 02 Jul 2009 10:16:02 -0700

(SOL7823) When diagnosing issues with Enterprise Manager iControl communications, use the following methods to help locate the point of failure: Verifying communications between the Enterprise Manager and the BIG-IP system using the curl utility Using the curl utility to verify that iControl is available on the target BIG-IP system Debugging the iControl flow Verifying communications between the Enterprise Manager and the BIG-IP system using the curl utility Communication must b

Solution: Troubleshooting Enterprise Manager software upgrade and hotfix installations

Thu, 02 Jul 2009 10:07:13 -0700

(SOL5557) If you attempt to install a new software version or hotfix with Enterprise Manager and the installation fails or Enterprise Manager reports an error, perform the following procedures to recover from the problem. Primary procedures If the installation fails and Enterprise Manager reports the Job has failed, installation is looping error message, perform the following procedure: Connect to the terminal port on the device to stop the installation process. Check the

Solution: Installing a new license file from the command line

Thu, 02 Jul 2009 10:06:07 -0700

(SOL2595) Note: For more information about licensing the BIG-IP system, refer to SOL7752: Overview of licensing the BIG-IP system. To manually license your F5 Networks product, perform the following procedure: Locate the 25-letter product registration key that was provided to you when you purchased the F5 Networks product. The key appears similar to the following example: ABCDE-ABCDE-ABCDE-ABCDE-ABCDE Note: In BIG-IP version 9.x andhigher, the F5 product registr

Solution: Processor change for the FirePass 4100 platform

Thu, 02 Jul 2009 10:05:49 -0700

(SOL10253) In spring 2005, F5 Networks began using a new motherboard for the FirePass 4100 platform. This motherboard has two AMD Opteron 2.0GHz single-core processors installed, which are displayed as two CPUs on the Device Management: Monitoring: System Health page in the FirePass Administrative Console. Previously, the FirePass 4100 platform shipped with two Intel Xeon 2.4GHz dual-core processors. When viewing the Device Management: Monitoring: System Health page on one of these models, four CPUs are r

Solution: Transferring files to or from an F5 Networks system

Thu, 02 Jul 2009 10:03:48 -0700

(SOL175) The following three options are available for transferring files between F5 devices: Secure Copy (SCP) File Transfer Protocol (FTP) Secure HTTP (HTTPS) SCP Secure Copy (SCP) is the preferred means of transferring files to or from an F5 device. SCP securely transfers files between hosts using the Secure Shell (SSH) protocol for authentication and encryption. Unlike FTP, SCP file transfers preserve the original datestamp on the file. You can use SCP to transfer files to or f

Known Issue: The RSA Authentication field is pre-populated with existing credentials when using the VPN standalone client

Thu, 02 Jul 2009 09:59:54 -0700

(SOL10222) When RSA authentication is configured, the SecurID tokencode field is pre-populated with the previous tokencode on the VPN standalone client. Users may incorrectly assume that the information that has been pre-populated is correct andpress the Logon button, rather than submitting the new credentials. Thismay result in the user locking themselves out of their account. F5 Networks Product Development is tracking this issue as CR121875. Workaround To work around this issue,instruct your users t

Solution: Change in Behavior: The snapshot remove command now creates sparse snapshots for failed removals

Thu, 02 Jul 2009 09:57:15 -0700

(SOL10254) The snapshot remove command deletes one or more filer snapshots associated with an ARX snapshot rule, without removing the rule itself. Note: In the ARX GUI, the snapshot remove command corresponds to selecting the snapshot name and clicking the Remove button. Previously, if a back-end filer failed to delete a snapshot, ARX noted the failure and then removed all references to the snapshot from its database. Once the snapshot was removed from the database, administrators could no longer delet

Best Practice: The recommended upgrade path for older software versions

Wed, 01 Jul 2009 15:00:04 -0700

(SOL9353) The upgrade instructions in the product Release Notes include upgrade instructions that assume an upgrade from a recent release. However, upgrading from an older, end-of-life release to the latest supported software version may require a different upgrade path than that recommended in the Release Notes. In general, you should always upgrade to a maintenance release before upgrading to a feature release to ensure that any fixes made in the maintenance branch are incorporated in the upgrade. The

Solution: An FTP session may fail after initial connection

Wed, 01 Jul 2009 14:47:44 -0700

(SOL193) An FTP session failure, may indicate that the FTP server requires passive mode or is attempting to perform a reverse name lookup. Passive Mode FTP Many FTP clients will automatically enable passive mode when required. Some FTP clients require that you manually enable passive mode, by using the following command. pass Some FTP clients, such as the Windows FTP client, do not support passive mode. When you attempt to retrieve data from an FTP server that requires passive mode, but you have

Solution: Overview of BIG-IP LTM cookie encoding for the cookie persistence profile

Wed, 01 Jul 2009 14:26:56 -0700

(SOL6917) Whenyou configure a cookie insert or cookie rewrite persistence profile, the BIG-IP LTM system inserts a cookie into the HTTP response from the virtual server which the client should return for subsequent HTTP requests. The cookieby defaultis named BIGipServer<pool_name>. The expiry for the cookie is set based on the timeout configured in the persistence profile. The cookie value contains the encoded IP address and port of the destination server. Address encoding BIG-IP uses the followin

Solution: Finding the serial number or registration key of your BIG-IP LTM, GTM, ASM, PSM, or WebAccelerator system

Wed, 01 Jul 2009 14:26:39 -0700

(SOL3782) The serial number is located on the barcode sticker, and is also stored in the systemconfiguration database. The registration key is located in the license file. Important: You must have the serial number or the last 7 digits of the registration key to open a service case with F5 Networks Technical Support. If you are unable to provide either, your Support technician may be able to locate your system in the support entitilement database. Serial number format Forplatform models 1600 and 3600,

Known Issue: Passive FTP fails through Static Application Tunnels after installing cumulative hotfix HF-603-2.1 or HF-603-3

Wed, 01 Jul 2009 14:26:13 -0700

(SOL10197) If you install cumulative HF-603-2.1 or HF-603-3 on the FirePass controller, Passive FTP no longer works through Static Application Tunnels. Note: For additional troubleshooting steps, refer to SOL193: An FTP session may fail after initial connection. F5 Networks Product Development is tracking this issue as CR122966. Additionally, a hotfix has been issued. Customers affected by this issue should contact F5 Networks Technical Support, referencing this Solution number and the associated CR

Solution: Overview of BIG-IP ASM daemons

Wed, 01 Jul 2009 12:33:01 -0700

(SOL10227) Note: For information about BIG-IP daemons, refer toSOL8035: Overview of BIG-IP daemons. When the BIG-IP system is licensed with BIG-IP ASM, a separate set of processes is initiated, in addition to the standard set of BIG-IP processes. The following table lists the core BIG-IP ASM services, and indicates the impact to the BIG-IP ASM system operation if the service is not running: Daemon Description Impact if not running L

Known Issue: A 'write permission not available' error message occurs for an NFS quorum disk

Wed, 01 Jul 2009 11:34:17 -0700

(SOL10248) Note: For information about configuring thequorum disk, refer to the Adding the Quorum Disk section of the Configuring Redundancy chapter in the ARX CLI Network Guide. When specifying the quorum disk forredundant ARX systems, one of thequorum-disk commandfunctions is to create a hidden .acopia_qdisk directory on the quorum disk share specified, and to write a test file to the directory to ensure that the quorum disk is functioning properly. When specifying an NFS quorum disk using the quorum-d

Known Issue: Accessing an NFS share on a direct volume fails if NFSv2 UDP is disabled on the back-end filer

Wed, 01 Jul 2009 11:28:18 -0700

(SOL10162) If a user mounts an NFS share on a direct volume, the user may receive an input/output error when attempting to access the mounted directory. For example: $ cd /mnt/arx/share1 -bash: cd: /mnt/arx/share1: Input/output error This issue occurs when the NFSv2 UDP is disabled on the back-end filer. Note: Direct volumes are referred to as presentation volumes in the ARX GUI. F5 Networks Product Development tracked this issue as ARX ID 34771 and it was fixed in ARX versions 4.1.1 and 5.0.1.

Solution: End of Sale announcement for the 8400 and 8800 platform

Wed, 01 Jul 2009 09:23:24 -0700

(SOL10252) With the release of the BIG-IP 8900 platform, F5 Networks is announcing the End of Sale of the 8400 and 8800 platforms, effective July 1, 2010. F5 Networks is providing Advanced Product Notification to customers and partners announcing intent to retire the followingproducts: Platform Platform name End of Sale (EoS) End of New Software Support (EoNSS) End of Software Development (EoSD) End of Support C

Solution: ARX software support policy

Wed, 01 Jul 2009 08:57:21 -0700

(SOL8466) For the F5 Networks software support policy for other F5 Networks products,refer to SOL8651: Software support policy for F5 Networks. The following versions of ARXsoftware are currently supported with active development: Software Version Branch Version Type Latest Release Hotfix Supported Releases Announced End of Major Version Support

Solution: Most recent versions of F5 Networks software

Wed, 01 Jul 2009 08:57:15 -0700

(SOL2200) Beginning in October 2008, F5 Networks products beganusinga newsoftware lifecycle policy versioning schema, which no longer categorizes arelease asa Feature Release or Maintenance Release. The new software lifecycle policy versioning schema categorizes a release phaseasGeneral Availability (GA)orGeneral Sustaining (GS). On rare occasions, a release phase of Limited Availability (LA)may be used. For information about the new software lifecycle policy, refer toSOL8986: F5 Networks software lifecy

Manual: ARX CLI Maintenance Guide, version 5.0.1

Wed, 01 Jul 2009 08:51:15 -0700

Manual: ARX Master Glossary, version 5.0.1

Wed, 01 Jul 2009 08:51:06 -0700

Manual: ARX Log Catalog, version 5.0.1

Wed, 01 Jul 2009 08:50:58 -0700

Manual: ARX CLI Reference Guide, version 5.0.1

Wed, 01 Jul 2009 08:50:41 -0700

AskF5 Knowledge Base - Recent Additions and Updates