Applies To:

Show Versions Show Versions

Archived Release Note: BIG-IP Link Controller version 4.5 PTF-01
Release Note

Software Release Date: 12/05/2002
Updated Date: 03/05/2007

This article has been archived, and is no longer maintained.

Summary:

This product temporary fix (PTF) provides enhancements and fixes for the BIG-IP Link Controller software, version 4.5. The PTF is recommended only for those customers who want the enhancements and fixes listed below. You can apply the software upgrade to BIG-IP Link Controller software, version 4.5 only. For information about installing the PTF, please refer to the instructions below.

Contents:

- Installing the PTF
- Software enhancements and fixes
     - What’s new in this PTF
     - What’s fixed in this PTF
- Known issues

Installing the PTF

Important:  If you are upgrading a Link Controller redundant system, both units must be upgraded. We do not support running different PTF versions on a Link Controller redundant system. Additionally, If you are updating the Link Controller module on a BIG-IP system, refer to the BIG-IP, version 4.5PTF01 note for instructions on installing the PTF.

Apply the PTF to the BIG-IP Link Controller, version 4.5 using the following process.  Note that the installation script saves your current configuration.

Important:  If you are upgrading an IP Application Switch or a Link Controller unit that uses a CompactFlash® media drive, use the installation instructions here.

  1. Change to the /var/tmp/ directory by typing:

    cd /var/tmp/

  2. Connect to the F5 Networks FTP site (ftp.f5.com).

  3. Use FTP in passive mode from the BIG-IP unit to download the file.  To place FTP in passive mode, type pass at the command line before transferring the file. 

  4. Download the PTF file BIGIP_4.5PTF-01.im to the /var/tmp/ directory on the Link Controller.

  5. To install this PTF, type the following command:

    im BIGIP_4.5PTF-01.im

    The Link Controller automatically reboots once it completes installation.

To upgrade an IP Application Switch or a CompactFlash media drive, use the following process.

  1. Create a memory file system, by typing the following:

    mount_mfs -s 200000 /mnt

  2. Type the following command:

    cd /mnt

  3. Connect to the FTP site (ftp.f5.com).

  4. Download the PTF file, BIGIP_4.5PTF-01.im, from the /crypto/bigip/ptfs/bigip45ptf1/ directory.

  5. On the BIG-IP unit, run the im upgrade script:

    im /mnt/BIGIP_4.5PTF-01.im

    When the im script is finished, the Link Controller reboots automatically.

Note:  This procedure provides over 90MB of temporary space on /mnt.  The partition and the im package file are deleted upon rebooting.

[ Top ]

Software enhancements and fixes

What’s new in this PTF

CA-2002-31, Multiple Vulnerabilities in BIND
This PTF addresses the security vulnerabilities that are listed in CERT® advisory, CA-2002-31, Multiple Vulnerabilities in BIND. This PTF upgrades the BIND package to version 8.3.4. For more information on the CERT advisory, see http://www.cert.org/advisories/CA-2002-31.html.

Support for the 2400 platform
This release includes enhanced support for the F5 Networks 2400 platform.

Viewing licensing error log files from the Configuration utility (CR25055)
You can now view the log files for errors that occur during the licensing process using the Configuration utility. A View Log File button appears on the licensing screen when the licensing process generates errors.

What’s fixed in this PTF

Resets (RSTs) with incorrect sequence numbers   (CR22219)
Resets (RSTs) from aging-out connections no longer cause some connections to hang due to incorrect sequence numbers for the resets.

[ Top ]

Known issues

The following items are the known issues identified since the release of BIG-IP Link Controller, version 4.5. For a list of the known issues in the 4.5 release, refer to the BIG-IP Link Controller, version 4.5 release note on AskF5.

Deleting hardware-accelerated connections (CR22494)
You cannot force the BIG-IP system to delete hardware-accelerated connections using the bigpipe command, b conn delete all. The BIG-IP system, however, does delete hardware-accelerated connections when the system initiates the delete command.

Creating pools and the admin VLAN (CR22599)
If you create a pool that uses the admin VLAN, the system cannot use hardware acceleration for that pool. We recommend that you do not use the admin VLAN for load balancing connections.

SNAT automap and acceleration (CR24959)
If you configure SNAT automap and do not associate the SNAT with a virtual server, the traffic is not accelerated. Note that you can associate the SNAT with a wildcard virtual server to accelerate any SNAT automap traffic.

Changing the hardware acceleration mode and resetting connections (CR25009)
When you change the hardware acceleration mode for a pool, and there are current connections for the nodes in the pool, the connections do not reset when you use the b conn reset command. The connections do close when they reach their time-to-live (TTL).

Invalid OID for the shutdown trap in the SNMP MIB (CR25059)
The shutdown trap, in the SNMP MIB, has an invalid object identifier (OID) associated with it. Therefore, this trap does not function properly.

b conn dump verbose command does not display correct values for packet counts or byte counts (CR25119)
The bigpipe command, b conn dump verbose, displays incorrect values for packet counts and byte counts.

Default gateway pool does not display properly when there is only a single pool member (CR25141)
In the Configuration utility, on the Outbound LB screen, the default gateway pool does not display properly when you define only one router when you first run the Setup utility. Once you configure a link for that router, the default gateway pool displays properly on the Outbound LB screen.

Invalid metrics statistics and graphs for down remote links (CR25146)
The Link Statistics screen, in the Configuration utility, displays very large, invalid values for remote links that are down (red ball). This invalid value causes the link statistics graphs to inaccurately display the data for both the link that is down, and any available links.

Changes in US and Canada Daylight Saving Time (CR58321)
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 are not reflected 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.

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