Installing the PTF

Apply the PTF to BIG/ip Controller version 3.0 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 v30ptf2domkit.tar file.
   • For international BIG/ip Controllers, download the v30ptf2intlkit.tar file.
3. Enter the following commands to install this PTF:

   cd /var/tmp
   tar -xvpf v30ptf2domkit.tar (Domestic HA/HA+ and LB)
   tar -xvpf v30ptf2intlkit.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 6588:  Forwarding virtual servers do not support FTP
  Added support for FTP through forwarding virtual servers.
• CR 4849:  Network virtual servers
  Added support for network virtual servers. For more information, see Configuring a network virtual server.

Released in prior PTFs

BIG/ip Controller version 3.0PTF-01

• CR 6122:  Encryption for big3d conversations is not turned off on international controllers
  3DNS Controllers now automatically disable encryption on big3d agents residing on international controllers.
• CR 6249:  ICMP port unavailable messages return a corrupt encapsulated IP header
  When sending a UDP packet to a BIG/ip Controller through an unavailable port, the returned message you receive now contains the original IP header that was sent out with the UDP packet.
• CR 6358:  International missing some of the new help files
  Online help for the international version of the BIG/ip System Properties page and Virtual Server Properties page is now current.
• CR 6391:  FTP data connections do not utilize lasthop routing feature
  FTP data connections now use the lasthop routing feature.
• CR 6394:  BIG/top crashes if DNS names are longer than 22 bytes
  When performing a DNS name lookup, BIG/top now uses a buffer that exceeds 22 bytes.
• CR 6399: Virtual servers outbound UDP blocked through source and destination interface
  Outbound UDP packets are no longer blocked when source and destination processing are simultaneously enabled.
• CR 6400:  Reverse ECV service checks fail
  Bignode reverse service ping now correctly handles responses larger than one packet.

Configuring and using the updated software

The following configuration options are available with this PTF.

Configuring a network virtual server

You can configure a network virtual server with this release. A network virtual server is a virtual server that handles a whole network range, instead of just one IP address, or all IP addresses (wildcard virtual servers). For example, the following virtual server handles all traffic addresses in the 192.168.1.0 network:

Note:  Network virtual servers should be assigned to interface none.

A network virtual server is a virtual server that has no bits set in the host portion of the IP address. In other words, the host portion is zero. You must specify a network mask to indicate which portion of the address is the network address and which portion is the host address. In the previous example, since the network mask is 255.255.255.0, the network portion of the address is 192.168.1 and the host portion is .0. The previous example would direct all traffic destined to the subnet 192.168.1.0/24 through BIG/ip Controller to the ingress_firewalls pool.

Another way you can use this feature is to create a catch-all webserver for an entire subnet. For example, you could create the following network virtual server:

This configuration directs a web connection destined to any address within the subnet 192.168.1.0/24 to the default_webservers pool.

Known issues

The upgrade for international BIG/ip Controllers version 3.0 creates an /etc/bigip.interfaces file. This file is no longer necessary and is deprecated with this release.