Applies To:

Show Versions Show Versions

Archived Release Note: BIG-IP Controller PTF note 2.0.1PTF-02
Release Note

Original Publication Date: 03/11/1999

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

Summary:

This note describes a Product Temporary Fix (PTF) to the BIG/ip Controller version 2.0.1, and it is recommended only for those customers who want the enhancements and fixes listed below. We strongly recommend that, if you are using the persist_any_vip or persist_any_port_same_vip settings, you install this PTF.

This PTF incorporates all fixes included in all PTFs subsequent to version 2.0.1. See the version 2.0.1 Release Notes for information about changes between version 2.0 and version 2.0.1.

Contents:

- Installing the PTF
- Configuring and using the updated software
- Enhancements and fixes

Installing the PTF

These installation instructions apply to all customers using version 2.0.1 of the BIG/ip software and who need the functionality listed in the Enhancements and Fixes section.

Use the following process to install the software:

  1. Click here and follow the instructions for using the F5 Networks FTP site.
  2. Download bigipv201-02domkit.tar file to the /var/tmp/ directory on the BIG/ip Controller.

    International customers need use FTP in passive mode from the BIG/ip Controller to download the bigipv201-02intlkit.tar file. To place FTP in passive mode, type pass from the command line before transferring the file.
  3. Enter the following commands to install this PTF:

    cd /var/tmp
    tar -xvpf /var/tmp/bigipv201-02domkit.tar

  4. From the root, run the following command:

    /var/tmp/upgrade_install

  5. Follow the on-screen instructions.

The install will automatically create a backup of your /etc/rc.local and /etc/rc.sysctl files and remove any old files that are no longer used. If you have made changes to your /etc/rc.local file, you may need to edit the file and retype your modifications. Backups of the files are stored in /var/save/backupyymmdd.hhmm/ on your BIG/ip Controller.


Configuring and using the updated software

BIG/ip version 2.0.1PTF-02

There are no configuration issues for BIG/ip Controller version 2.0.1PTF-02.

BIG/ip version 2.0.1PTF-01

There are no configuration issues for BIG/ip Controller version 2.0.1PTF-01.


Enhancements and fixes

BIG/ip version 2.0.1PTF-02

BIG/ip version 2.0PTF-02 provides significant performance improvements effected by the following enhancements and fixes:

  • 756: Log rotation fails if sendmail.cf does not exist
    The daily log rotations, controlled by the /etc/daily script, verifies that the sendmail.cf file exists on the BIG/ip Controller, before sending the results. If the sendmail.cf file does not exist on the unit, then sendmail is not used.
  • 1395: TCP persistence does not work
    TCP persistence now works properly with the persist_any_vip and persist_any_port_same_vip settings.
  • 1430: Y2K problem setting date to February 29, 2000
    The BSDI patch, M310-023, has now been applied to the BIG/ip Controller, solving this problem.
  • 1434: Port rewrite not correct for TCP and UDP fragments
    When a packet fragment arrives, the BIG/ip Controller now saves the fragment number according to the user's IP address. The remaining fragment packets are then forwarded to the correct node for that user's connection.

BIG/ip version 2.0.1PTF-01

BIG/ip version 2.0.1PTF-01 provides significant performance improvements effected by the following enhancements and fixes:

  • 1066: The BIG/ip Controller sends a reset when it receives a reset
    The BIG/ip Controller now discards the resets it receives, in accordance with RFC 793.
  • 1346: Transparent Node Mode, UDP and ICMP not routed properly through firewalls
    UDP and ICMP packets are now routed through firewalls using the node route.
  • 1350: Order of checking NATs and virtual servers reversed in Transparent Node Mode
    When working in Transparent Node Mode, NATs are now checked before virtual servers so that a wildcard virtual server does not mask the NATs. In Normal Mode, virtual servers are still checked first.
  • 1387: ICMP need frag packets to a virtual server in Transparent Node Mode are not handled correctly
    The BIG/ip kernel now handles ICMP packets so that the route MTU is adjusted and an ICMP need to fragment message is sent to the sender.
  • 1388: ICMP need frag packets to a NAT external IP address are not handled correctly
    The BIG/ip kernel now handles ICMP packets so that the route MTU is adjusted and an ICMP need to fragment message is sent to the sender.
  • 1389: icmp_error receives a translated offending packet and calls icmp_reflect
    The BIG/ip kernel now saves a portion of the original packet and retranslates the packet before passing it to the icmp_error function.
  • 1390: BSD incorrectly sets icmp-nextmtu to if_mtu when generating an ICMP need frag packet
    If Path MTU discovery is on and the BIG/ip Controller receives a packet that is longer than its MTU, BSD sends an ICMP need to fragment message with the icmp_nextmtu> variable set to the MTU of the route, so that the sender can reduce its MTU for that route. Otherwise, BSD sends an ICMP need to fragment message with the icmp_nextmtu variable set to if_mtu.
  • 1398: Disabled nodes reject persistent connections
    The BIG/ip Controller now allows persistent connections to continue after you disable a node.


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)