Applies To:
Show Versions
Link Controller
- 4.6.4
Updated Date: 04/18/2019
Summary:
This release note documents version 4.6.4 of the Link Controller® software. You can apply the software upgrade to version 4.5 and later. For information about installing the software, please refer to the instructions below.
F5 now offers both maintenance-only and new feature releases. Version 4.6.4 is a feature release that is based on version 4.5.12 code. This release includes all features and fixes included in versions 4.5.12 and 4.6.2. For more information on our new release polices, please see New Versioning Schema for F5 Software Releases.
Warning: This is a feature release, not a maintenance release. Unless you need specific features that are new to this feature release, please upgrade to the latest maintenance release instead.
Contents:
Minimum system requirements and supported browsers
The minimum system requirements for this release are:
- Intel® Pentium® III 550MHz processor
- 512MB disk drive or CompactFlash® card
- 256MB RAM
The supported browsers for the Configuration utility are:
- Microsoft® Internet Explorer 5.0, 5.5, and 6.0
- Netscape® Navigator 4.7x
Installing the software
Important: If you are upgrading a Link Controller redundant system, you must upgrade both units. We do not support running different 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.6.4 note for instructions on installing the upgrade.
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.
Note: If you have installed prior releases, this installation does not overwrite any configuration changes that you made for prior releases.
The following instructions explain how to install the BIG-IP Link Controller software version 4.6.4 onto existing systems running version 4.5 and later. The installation script saves your current configuration.
- Go to the Downloads site and locate the BIG-IP 4.6.4 upgrade file, BIGIP_4.6.4_Upgrade.im.
- Download the software image and the BIGIP_4.6.4_Upgrade.md5 file.
For information about how to download software, refer to SOL167: Downloading software from F5 Networks.
- If you downloaded the image file to a directory other than /var/tmp, copy the image file to the /var/tmp/ directory on your BIG-IP system.
- Check the md5 of the upgrade file by typing the following command:
md5 BIGIP_4.6.4_Upgrade.im
cat BIGIP_4.6.4_Upgrade.md5The two md5 values should be identical.
- Install the IM by typing the following command:
im BIGIP_4.6.4_Upgrade.imThe Link Controller automatically reboots once it completes installation.
To upgrade an IP Application Switch or a CompactFlash media drive, use the following process.
- Create a memory file system, by typing the following:
mount_mfs -s 200000 /mnt
- Go to the Downloads site and locate the BIG-IP 4.6.4 upgrade file, BIGIP_4.6.4_Upgrade.im.
- Download the software image and the BIGIP_4.6.4_Upgrade.md5 file.
For information about how to download software, refer to SOL167: Downloading software from F5 Networks.
- If you downloaded the image file to a directory other than /mnt, copy the image file to the /mnt directory on your BIG-IP system.
- Check the md5 of the upgrade file by typing the following command:
md5 BIGIP_4.6.4_Upgrade.im
cat BIGIP_4.6.4_Upgrade.md5The two md5 values should be identical.
- On the BIG-IP unit, run the im upgrade script:
im /mnt/BIGIP_4.6.4_Upgrade.imThe Link Controller automatically reboots once it completes installation.
Note: This procedure provides over 90MB of temporary space on /mnt. The partition and the im package file are deleted upon rebooting.
Activating the license
Once you install the upgrade and connect the unit to the network, you need a valid license certificate to activate the software. To gain a license certificate, you need to provide two items to the license server: a registration key and a dossier.
The registration key is a 25-character string. You should have received the key by email. The registration key lets the license server know which F5 products you are entitled to license.
The dossier is obtained from the software, and is an encrypted list of key characteristics used to identify the platform.
You can obtain a license certificate using one of the following methods:
- Automatic license activation
You perform automatic license activation from the command line or from the web-based Configuration utility of an upgraded unit. This method automatically retrieves and submits the dossier to the F5 license server, as well as installs the signed license certificate. In order for you to use this method, the unit must be installed on a network with Internet access. - Manual license activation
You perform manual license activation from the Configuration utility, which is the software user interface. With this method, you submit the dossier to, and retrieve the signed license file from, the F5 license server manually. In order for you to use this method, the administrative workstation must have Internet access.
Note: You can open the Configuration utility with Netscape Navigator version 4.7x, or Microsoft Internet Explorer version 5.0, 5.5, or 6.0.
To automatically activate a license from the command line for first time installation
- Type the user name root and the password default at the logon prompt.
- At the prompt, type license. The following prompts display:
IP:
Netmask:
Default Route:
Select interface to use to retrieve license:
The unit uses this information to make an Internet connection to the license server. - After you type the Internet connection information, continue to the following prompt:
The Registration Key should have been included with the software or given when the order was placed. Do you have your Registration Key? [Y/N]:
Type Y, and the following prompt displays:
Registration Key: - Type the 25-character registration key you received. If you received more than one key, enter all of the keys, separating each with a space.
The dossier is retrieved and sent to the F5 license server, and a signed license file is returned and installed. A message displays indicating the process was successful. - You are asked to accept the End User License Agreement.
The system is not fully functional until you accept this agreement. - You are prompted to reboot the system. Press Enter to reboot.
The system is not fully functional until you reboot.
To automatically activate a license from the command line for upgrades
- Type your user name and password at the logon prompt.
- At the prompt, type setup.
- Choose menu option L.
- The following prompt displays:
Number of keys: 1
If you have more than one registration key, enter the appropriate number. - The following prompt displays:
Registration Key:
Type the 25-character registration key you received. If you received more than one key, enter all of the keys, separating each with a space.
The dossier is retrieved and sent to the F5 license server, and a signed license file is returned and installed. A message displays indicating the process was successful. - When you are finished with the licensing process, type the following command to restart the services on the system:
bigstart restart
To manually activate a license using the Configuration utility
- Open the Configuration utility according to the type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- If you are licensing a new BIG-IP unit, from the administrative workstation, open the Configuration utility using one of the following addresses: https://192.168.1.245 or https://192.168.245.245. These are default addresses on the units local area network.
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- Type the user name and password, based on the type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- If you are licensing a new BIG-IP system, type the user name root, and the password default at the logon prompt.
- If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- Click License Utility to open the License Administration screen.
- In the Registration Key box, type the 25-character registration key that you received. If you have more than one key to install, click Enter More Keys to install multiple keys. Once you have entered all registration keys, click Manual Authorization.
- At the Manual Authorization screen, retrieve the dossier using one of the following methods:
- Copy the entire contents of the Product Dossier box.
- Click Download Product Dossier, and save the dossier to the hard drive.
- Copy the entire contents of the Product Dossier box.
- Click the link in the License Server box.
The Activate F5 License screen opens in a new browser window. - From the Activate F5 License screen, submit the dossier using one of the following methods:
- Paste the data you just copied into the Enter your dossier box, and click Activate.
- At the Product Dossier box, click Browse to locate the dossier on the hard drive, and then click Activate.
- Paste the data you just copied into the Enter your dossier box, and click Activate.
- Retrieve the license file using one of the following methods:
- Copy the entire contents of the signed license file.
- Click Download license, and save the license file to the hard drive.
- Copy the entire contents of the signed license file.
- Return to the Manual Authorization screen, and click Continue.
- At the Install License screen, submit the license file using one of the following methods:
- Paste the data you copied into the License Server Output box, and click Install License.
- At the License File box, click Browse to locate the license file on the hard drive, and then click Install License.
- Paste the data you copied into the License Server Output box, and click Install License.
- Click License Terms, review the EULA, and accept it.
- At the Reboot Prompt screen, select when you want to reboot the platform.
License activation is complete only after rebooting.
To automatically activate a license using the Configuration utility
- Open the Configuration utility according to the type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- If you are licensing a new BIG-IP unit, from the administrative workstation, open the Configuration utility using one of the following addresses: https://192.168.1.245 or https://192.168.245.245. These are default addresses on the units local area network.
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- Type the name and password, based on what type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- If you are licensing a new BIG-IP unit, type the user name root, and the password default at the logon prompt.
- If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- Click License Utility to open the License Administration screen.
- In the Registration Key box, type the 25-character registration key that you received. If you have more than one key to install, click Enter More Keys to install multiple keys. Once you have entered all registration keys, click Automated Authorization. The License Status screen displays status messages, and Process complete appears when the licensing activation is finished.
- Click License Terms, review the EULA, and accept it.
- At the Reboot Prompt screen, select when you want to reboot the platform.
License activation is complete only after rebooting.
New features in this release
This release includes no new features. The primary reason we released version 4.6.4 was to fix an issue that existed in version 4.6.3 which, under certain circumstances, caused the system to become unresponsive. The issue has been resolved in version 4.6.4.
New fixes in this release
Note: In version 4.6.3, we modified the format for displaying CRs for fixes and known issues. So from version 4.6.3 on, the CRs are listed in a table format, with the corresponding solution listed next to the CR. Clicking the solution link directs you to the more detailed solution document that is posted on the AskF5 Technical Support Web Site. We continually update these solution documents on AskF5 as new details become available. If additional known issues are discovered after we release a version, we will update the known issues table with the new CR and solution numbers, with the goal of keeping you current on our known issues.
If you encounter a CR that does not have an active solution link, it is likely that we have not yet had a chance to get the solution posted on AskF5, but please continue to check this table for new content or links.
This release includes the following new fixes.
CR | Solution | Description |
CR47613 | SOL4722 | SSL sessions might not be closed correctly when SSL persistence is enabled |
CR47719 | SOL4819 | The BIG-IP system might become unresponsive when performing delayed binding operations |
CR47758 | SOL4819 | The BIG-IP system might become unresponsive when performing delayed binding operations |
CR47829 | SOL4821 | The BIG-IP system might reset HTTP connections that contain a retransmitted response |
CR47830 | SOL4821 | The BIG-IP system might reset HTTP connections that contain a retransmitted response |
CR48224 | SOL4720 | Connections to a Siebel application server might fail due to pipelining protection |
CR48262 | SOL4583 | Some versions of the BIG-IP system are subject to the vulnerability described in VU#222750 |
CR48301 | SOL4718 | The BIG-IP system might become unresponsive or behave unpredictably when you use header insert |
CR48302 | SOL4718 | The BIG-IP system might become unresponsive or behave unpredictably when you use header insert |
CR48303 | SOL4718 | The BIG-IP system might become unresponsive or behave unpredictably when you use header insert |
CR48313 | SOL4583 | Some versions of the BIG-IP system are subject to the vulnerability described in VU#222750 |
CR48314 | SOL4720 | Connections to a Siebel application server might fail due to pipelining protection |
CR48315 | SOL4722 | SSL sessions might not be closed correctly when SSL persistence is enabled |
CR48351 | SOL4817 | The 3-DNS Controller might corrupt the class field when responding to a AAAA record query |
CR48352 | SOL4817 | The 3-DNS Controller might corrupt the class field when responding to a AAAA record query |
CR48353 | SOL4819 | The BIG-IP system might become unresponsive when using delayed binding features |
CR48563 | SOL4821 | The BIG-IP system might reset HTTP connections that contain a retransmitted response |
CR48835 | SOL4900 | The BIG-IP system might corrupt UDP packets when the packets are accelerated by PVA |
CR49011 | SOL4900 | The BIG-IP might corrupt UDP packets when the packets are accelerated by PVA |
Fixes and features in prior releases
To view fixes and features that were distributed in prior releases, see the previous release notes on AskF5.
Known issues
The following items are known issues in the current release.
CR | Solution | Description |
CR9333 | SOL5189 | Multiple instances of the Configuration utility may overwrite each other |
CR14294 | SOL765 | 3dnsmaint copies iQuery keys twice to BIG-IP/3-DNS combination systems |
CR14955 | SOL5078 | The Configuration utility allows special characters in configuration object names |
CR14956 | SOL5078 | The Configuration utility allows special characters in configuration object names |
CR16971 | SOL5078 | The Configuration utility allows special characters in configuration object names |
CR16972 | SOL5078 | The Configuration utility allows special characters in configuration object names |
CR16973 | SOL5078 | The Configuration utility allows special characters in configuration object names |
CR17173 | SOL5078 | The Configuration utility allows special characters in configuration object names |
CR19648 | SOL320 | The Configuration utility home screen contains erroneous instructions |
CR20183 | SOL5179 | 3dpipe will not allow pool names that consist only of numerals |
CR20213 | SOL327 | QOS values may be changed when you configure QOS as the LB mode for a pool |
CR21513 | SOL334 | The Configuration utility might become unresponsive if a router is configured with multiple self IP addresses |
CR22131 | SOL327 | QOS values may be changed when you configure QOS as the LB mode for a pool |
CR23224 | SOL5032 | The Configuration utility does not correctly modify wide IP names |
CR23564 | SOL783 | Saving a new copy of snmptrap.conf file can create a conflict after an upgrade |
CR24687 | SOL5277 | Link Controller displays available remote Wide IPs as green, rather than gray |
CR24734 | SOL5230 | Auto-configuration may incorrectly set the Unit IDs on 3-DNS redundant pairs |
CR24735 | SOL5230 | Auto-configuration may incorrectly set the Unit IDs on 3-DNS redundant pairs |
CR24976 | SOL815 | The link to the BIG-IP Link Controller Solutions Guide is missing from the Configuration utility |
CR25821 | SOL816 | F5 source addresses are not added to the hosts.allow file when the support account is enabled |
CR26154 | SOL327 | QOS values may be changed when you configure QOS as the LB mode for a pool |
CR26610 | SOL336 | Disabling SNMP traps using the Configuration utility causes an error |
CR27037 | SOL5186 | Changing a self IP address does not change associated bigdb entries |
CR27219 | SOL5055 | 3dns_add will run on a Link Controller even when no sync group is configured |
CR27260 | SOL371 | You cannot change the default gateway pools using the config command |
CR27486 | SOL389 | BIG-IP Link Controller provides an unhelpful error when you attempt to add gray virtual servers to a wide IP |
CR27501 | SOL399 | The config command reports an unnecessary error when a copy of 3dnsd is already running |
CR27547 | SOL298 | Ratio settings are not available when ratio is used as the alternate load balancing mode |
CR27650 | SOL433 | You must manually configure Hops factories before hops load balancing works on a BIG-IP Link Controller |
CR27791 | SOL437 | An error is logged to /var/log/3dns when a router is not configured for a datacenter |
CR27799 | SOL445 | An error might be reported when synchronizing iQuery keys |
CR28057 | SOL461 | Changing the port of a virtual server results in multiple virtual server statements |
CR28072 | SOL467 | You can partially remove a link by deleting its self IP address and VLAN |
CR28099 | SOL486 | The 3-DNS Controller still uses BIG-IP systems for probing when all prober factories have been deleted |
CR28228 | SOL509 | The BIG-IP Link Controller might display a 331781 memory error, but not fail the operation that caused the error |
CR28529 | SOL509 | The BIG-IP Link Controller might display a 331781 memory error, but not fail the operation that caused the error |
CR29751 | SOL3783 | The verify command rejects configurations using SNAT connection mirroring |
CR29967 | SOL2853 | The Wide IP Port box can list only pre-configured ports |
CR30783 | SOL2942 | Default gateway entry is converted to a default gateway pool |
CR31239 | SOL1865 | You must use the command line to clear LDNS statistics |
CR31946 | SOL1902 | Must configure a self IP address for a new system before using the 3dnsmaint menu to set up SSH communication |
CR32755 | SOL573 | In rare cases, a BIG-IP system object with an address of 127.0.0.1 might be created |
CR32762 | SOL591 | The random pool load balancing mode distributes connections using a fixed ratio |
CR32977 | SOL2853 | The Wide IP Port box can list only pre-configured ports |
CR33161 | SOL604 | Auto configuration might not add all virtual servers when initially run after configuring the 3-DNS Controller |
CR33815 | SOL761 | The table that contains Nokia NetAct SNMP traps might grow very large and use excessive disk space |
CR34267 | SOL4717 | The BIG-IP system changes the interface media settings after running the Setup utility |
CR34599 | SOL2325 | The gray virtual server status was not documented in the 3-DNS Controller statistics page |
CR35019 | SOL763 | BIG-IP Link Controllers do not display statistics for virtual servers that are not part of a wide IP |
CR35320 | SOL309 | The Telnet and FTP servers are not started when you enable Telnet and FTP |
CR36729 | SOL764 | Wide IPs created in the Link Controller Configuration utility are not included in NameSurfer |
CR36811 | SOL310 | Link statistics are not displayed correctly after links are added or removed |
CR37919 | SOL676 | File locking is not performed when running the 3dns_add and sync_zones scripts |
CR38086 | SOL145 | Copper gigabit switch ports do, but should not, allow manual media settings |
CR38087 | SOL145 | Copper gigabit switch ports do, but should not, allow manual media settings |
CR38163 | SOL681 | Load balancing modes Explicit IP, Return to DNS, None, and Drop Packet do not work correctly |
CR38193 | SOL688 | The hops, RTT, and QOS load balancing modes return a single virtual server if probing is disabled |
CR38340 | SOL692 | Sync groups allow synchronization across versions |
CR38491 | SOL688 | The hops, RTT, and QOS load balancing modes return a single virtual server if probing is disabled |
CR39381 | SOL150 | Disabling a link by name in an application object does not work |
CR40319 | SOL694 | An error is displayed if you refresh the Configuration utility after creating a link |
CR41799 | SOL298 | Ratio settings are not available when ratio is used as the alternate load balancing mode |
CR41803 | SOL2942 | Default gateway entry is converted to a default gateway pool |
CR41805 | SOL309 | The Telnet and FTP servers are not started when you enable Telnet and FTP |
CR41807 | SOL310 | Link statistics are not displayed correctly after links are added or removed |
CR41810 | SOL320 | Cannot access the Configuration utility after running the Setup utility |
CR41811 | SOL327 | QOS values may be changed when you configure QOS as the LB mode for a pool |
CR41812 | SOL328 | Ports List screen does not display the ports enabled for a wide IP |
CR41814 | SOL334 | For multi-homed routers, you must configure the 3-DNS Controller with a link to the router that uses a self IP address on each of the multi-homed networks |
CR41824 | SOL371 | You cannot change default gateway pools using the config command |
CR41825 | SOL389 | BIG-IP Link Controller provides an unhelpful error when you attempt to add gray virtual servers to a wide IP |
CR41826 | SOL399 | The config command reports an unnecessary error when a copy of 3dnsd is already running |
CR41828 | SOL433 | You must manually configure hops factories before hops load balancing works on a Link Controller |
CR41829 | SOL437 | An error is logged to /var/log/3dns when a router is not configured for a datacenter |
CR41830 | SOL445 | An error might be reported when synchronizing iQuery keys |
CR41832 | SOL461 | Changing the port of a virtual server results in multiple virtual server statements |
CR41833 | SOL467 | You can partially remove a link by deleting its self IP address and VLAN |
CR41834 | SOL486 | 3-DNS Controller still uses BIG-IP systems for probing when all prober factories have been deleted |
CR41837 | SOL509 | The BIG-IP Link Controller might display a 331781 memory error, but not fail the operation that caused the error |
CR41844 | SOL573 | In rare cases, a 3-DNS Controller might create a BIG-IP object with an address of 127.0.0.1 |
CR41845 | SOL591 | The random pool load balancing mode distributes connections using a fixed ratio |
CR41847 | SOL604 | Auto configuration might not add all virtual servers when initially run after configuring the 3-DNS Controller |
CR41854 | SOL676 | File locking is not performed when running the 3dns_add and sync_zones scripts |
CR41855 | SOL681 | Load balancing modes Explicit IP, Return to DNS, None, and Drop Packet do not work correctly |
CR41856 | SOL688 | The hops, RTT, and QOS load balancing modes return a single virtual server if probing is disabled |
CR41857 | SOL692 | Sync groups allow synchronization across versions |
CR41858 | SOL688 | The hops, RTT, and QOS load balancing modes return a single virtual server if probing is disabled |
CR41860 | SOL694 | An error is displayed if you refresh the Configuration utility after creating a link |
CR41876 | SOL2853 | The Wide IP Port box can only list pre-configured ports |
CR41877 | SOL761 | The table that contains Nokia NetAct SNMP traps might grow very large and use excessive disk space |
CR41878 | SOL763 | BIG-IP Link Controllers do not display statistics for virtual servers that are not part of a wide IP |
CR41882 | SOL764 | Wide IPs created in the Link Controller Configuration utility are not included in NameSurfer |
CR41884 | SOL765 | 3dnsmaint copies iQuery keys twice to BIG-IP/3-DNS combination systems |
CR41889 | SOL783 | Saving a new copy of the snmptrap.conf file can create a conflict after an upgrade |
CR41890 | SOL815 | The link to the BIG-IP Link Controller Solutions Guide is missing from the Configuration utility |
CR41891 | SOL816 | F5 source addresses are not added to the hosts.allow file when the support account is enabled |
CR41894 | SOL5055 | 3dns_add will run on a Link Controller even when no sync group is configured |
CR41909 | SOL1865 | You must use the command line, not the Configuration utility, to clear LDNS statistics |
CR41912 | SOL1902 | You must configure a self IP address for a new system before using the 3dnsmaint menu to set up SSH communication |
CR42147 | SOL4717 | The BIG-IP system changes the interface media settings after running the Setup utility |
CR46509 | SOL4497 | Switch appliances do not send an SNMP trap when booting because the switch ports are disabled |
CR46906 | SOL5150 | The default values shown for WideIP load-balancing in on-line help and wideip.conf are incorrect |
CR46907 | SOL5150 | The default values shown for WideIP load-balancing in on-line help and wideip.conf are incorrect |
CR47235 | SOL4572 | The login.conf file might be overwritten during an upgrade |
CR47236 | SOL4572 | The login.conf file might be overwritten during an upgrade |
CR47276 | SOL4574 | The BIG-IP system and 3-DNS Controller do not prevent you from installing unsupported versions on older hardware |
CR47330 | SOL5219 | Auto-configuration is disabled by default for Link Controller |
CR47331 | SOL5219 | Auto-configuration is disabled by default for Link Controller |
CR48152 | SOL4809 | BIG-IP and 3-DNS are vulnerable to CAN-2005-1278, CAN-2005-1279, and CAN-2005-1280 |
CR48153 | SOL4809 | BIG-IP and 3-DNS are vulnerable to CAN-2005-1278, CAN-2005-1279, and CAN-2005-1280 |
CR49272 | SOL4532 | The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0758, CAN-2005-0988, and CAN-2005-1228 |
CR49273 | SOL4532 | The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0758, CAN-2005-0988, and CAN-2005-1228 |
CR49336 | SOL4616 | BIG-IP and 3-DNS are vulnerable to CAN-2005-0488 |
CR49337 | SOL4616 | BIG-IP and 3-DNS are vulnerable to CAN-2005-0488 |
CR58321 | SOL6551 | Changes in US and Canada Daylight Saving Time |