Applies To:

Show Versions Show Versions

Archived Release Note: BIG-IP Controller PTF note, version 2.1.4 PTF-01
Release Note

Original Publication Date: 01/20/2000

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

Summary:

This product temporary fix (PTF) provides fixes for BIG/ip Controller, version 2.1.4.  The PTF includes all fixes released since version 2.1.4, including fixes originally released in prior PTFs.

Contents:

- Installing the PTF
- What's fixed in this PTF
- Configuring and using the updated software
- Known Issues

Installing the PTF

Apply the PTF to BIG/ip Controller version 2.1.4 using the following process:

  1. Click here and follow the instructions for using the F5 Networks FTP site.

    Use FTP in passive mode from the BIG/ip Controller to download the file. To place FTP in passive mode, type pass from the command line before transferring the file.

  2. Download the appropriate file to the /var/tmp/ directory on the target BIG/ip Controller:

    • For US BIG/ip Controllers, download the v214ptf1domkit.tar file.
    • For international BIG/ip Controllers, download the v214ptf1intlkit.tar file.
  3. Enter the following commands to install this PTF:

    cd /var/tmp
    tar -xvpf v214ptf1domkit.tar (Domestic HA/HA+ and LB)
    tar -xvpf v214ptf1intlkit.tar
    (International HA/LB)

  4. Run the following commands:

    cd /
    var/tmp/upgrade_ptf

  5. Follow the on-screen instructions.

The install automatically creates a backup of the /etc/syslog.conf file in /var/save/backupyymmdd_hhmm/ on the BIG/ip Controller and removes any old files that are no longer used. If you have made changes to the /etc/syslog.conf file, you may need to edit that file and retype your modifications.

The checksums for this PTF are available in a file called sums, which can be downloaded from the FTP site.

Once you have installed the PTF software, please refer to the Configuring and using the updated software.


What's fixed in this PTF

  • CR 6015:  Added support for AOL proxies 152.163 to 152.207
    Added support for AOL proxies so that client addresses map to a common address when the sysctl variable bigip.persist_map_proxies is set to 1. For more information, see Setting up AOL proxy mapping.

Configuring and using the updated software

Setting up AOL proxy mapping
To set up AOL proxy mapping, set the sysctl variable bigip.persist_map_proxies to 1. This maps the 152 and 170 class A networks and the 202.67 and 205.188 class B networks to a common address. By default, this feature is turned on:

sysctl -w bigip.persist_map_proxies=1

Note:  To turn this feature off, set the sysctl variable to 0.

We recommend in addition to setting the sysctl variable bigip.persist_map_proxies, that you set a persist mask of 255.255.0.0 so that all the AOL addresses map to a common address.

To set the persist mask in the F5 Configuration utility

  1. In the navigation pane, click Virtual Servers.
    The Virtual Servers screen opens.
  2. In the Virtual Servers list, click the virtual server you want to configure.
    The Virtual Servers Properties screen opens.
  3. In the Persistence section, type the following information:
    • Timeout (seconds)
      Type the number of seconds for persistence on the virtual server. This timeout overrides the persistence timeout set at the port level.
    • Mask
      Type the mask 255.255.0.0.
  4. Click the Apply button.
  5. Repeat this procedure for each virtual server.

To set the persist mask from the command line
To set the persist mask 255.255.0.0 from the command line, type the following command:

bigpipe vip <virtual IP> persist mask 255.255.0.0

For <virtual IP>, type in the IP address of the virtual server for which you want to set the persist mask.

The following table is an example of how a set of client addresses would map with the persist mask set to 255.255.0.0:

Client Address Persist Address
152.44.12.3 195.93.0.0
152.2.99.7 195.93.0.0
170.11.19.22 195.93.0.0
202.67.34.11 195.93.0.0
205.188.11.2 195.93.0.0
208.33.23.4 208.33.0.0 (non AOL address is not mapped)

Known Issues

Virtual servers configured with 0 or 255 in the last octet
The F5 Configuration utility does not handle virtual servers configured with 0 or 255 in the last octet. If a virtual server is configured with 0 or 255 in the last octet, no virtual servers are displayed in the F5 Configuration utility.

Manually configured host names in the /etc/bigip.conf file
If you use the configsync feature or change the configuration in the F5 Configuration utility, host names configured in the /etc/bigip.conf file are changed to IP addresses.



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)