Release Notes : BIG-IP Link Controller version 4.5.14 Release Note

Applies To:

Show Versions Show Versions

BIG-IP versions 1.x - 4.x

  • 4.5.14
Release Notes
Software Release Date: 01/31/2006
Updated Date: 04/18/2019

Summary:

This release note documents version 4.5.14 of the BIG-IP® Link Controller software. You can apply the software upgrade to version 4.2 and later. For information about installing the software, refer to the instructions below.

F5 now offers both maintenance and new feature releases. Version 4.5.14 is a maintenance release which includes security updates and enhancements that stabilize the version 4.5 software, but it contains no major new features. For more information on our new release polices, see New Versioning Schema for F5 Software Releases.

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
[ Top ]

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.5.14 note for instructions about 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.5.14 onto existing systems running version 4.5 and later. The installation script saves your current configuration.

  1. Go to the Downloads site and locate the BIG-IP 4.5.14 upgrade file, BIGIP_4.5.14_Upgrade.im.
     
  2. Download the software image and the BIGIP_4.5.14_Upgrade.md5 file.

    For information about how to download software, refer to SOL167: Downloading software from F5 Networks.

  3. 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.
     
  4. Check the md5 of the upgrade file by typing the following commands:

    md5 BIGIP_4.5.14_Upgrade.im
    cat BIGIP_4.5.14_Upgrade.md5

    The two md5 values should be identical.

  5. Install the IM by typing the following command:

    im BIGIP_4.5.14_Upgrade.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. Go to the Downloads site and locate the BIG-IP 4.5.14 upgrade file, BIGIP_4.5.14_Upgrade.im.
     
  3. Download the software image and the BIGIP_4.5.14_Upgrade.md5 file.

    For information about how to download software, refer to SOL167: Downloading software from F5 Networks.

  4. 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.
     
  5. Check the md5 of the upgrade file by typing the following commands:

    md5 BIGIP_4.5.14_Upgrade.im
    cat BIGIP_4.5.14_Upgrade.md5

    The two md5 values should be identical.

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

    im /mnt/BIGIP_4.5.14_Upgrade.im

    The 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.

[ Top ]

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 obtain 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
 

  1. Type the user name root and the password default at the logon prompt.
     
  2. 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.

  3. 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]:

  4. Type Y, and the following prompt displays:

    Registration Key:

  5. 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.
     
  6. You are asked to accept the End User License Agreement (EULA).

    Note that the system is not fully functional until you accept this agreement.
     
  7. 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
 

  1. Type your user name and password at the logon prompt.
     
  2. At the prompt, type setup.
     
  3. Choose menu option L.
     
  4. The following prompt displays:

    Number of keys: 1

    If you have more than one registration key, enter the appropriate number.
     
  5. The following prompt displays:

    Registration Key:

  6. 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.
     
  7. 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
 

  1. 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.
  2. 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.
    The Configuration utility menu displays.
     
  3. Click License Utility to open the License Administration screen.
     
  4. 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.
     
  5. 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.
  6. Click the link in the License Server box.

    The Activate F5 License screen opens in a new browser window.
     
  7. 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.
    The screen returns a signed license file.
     
  8. 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.
  9. Return to the Manual Authorization screen, and click Continue.
     
  10. 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.
    The License Status screen displays status messages, and Process complete appears when the licensing activation is finished.
     
  11. Click License Terms, review the EULA, and accept it. The system is not fully functional until you accept this agreement.
     
  12. 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
 

  1. 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.
  2. 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.
    The Configuration utility menu displays.
     
  3. Click License Utility to open the License Administration screen.
     
  4. 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.
     
  5. Click License Terms, review the EULA, and accept it. The system is not fully functional until you accept this agreement.
     
  6. At the Reboot Prompt screen, select when you want to reboot the platform.

    License activation is complete only after rebooting.
[ Top ]

Changes to existing features

This release includes the following changes in product behavior.

Note:  If you encounter a solution that does not have an active 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.

Added Revised CR Solution Description
01/16/06 01/16/06 CR40892 SOL5848 Configuring BIG-IP to use an automap SNAT when no match is found in a SNAT pool
01/16/06 01/16/06 CR42117 SOL5848 Configuring BIG-IP to use an automap SNAT when no match is found in a SNAT pool
01/16/06 01/16/06 CR54130 SOL5862 Performance of health monitor smoothing has been improved
01/16/06 01/16/06 CR54131 SOL5862 Performance of health monitor smoothing has been improved
[ Top ]

New fixes and enhancements in this release

Note: Starting in version 4.5.13, we modified the format for displaying CRs for fixes and known issues. 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.

This release includes the following new fixes.

Added Revised CR Solution Description
01/16/06 01/16/06 CR29394 SOL5135 In rare circumstances, the active unit in a redundant pair may fail back to standby when the standby reboots
01/16/06 01/16/06 CR29395 SOL5135 In rare circumstances, the active unit in a redundant pair may fail back to standby when the standby reboots
01/16/06 01/16/06 CR44999 SOL5828 Zone changes are not synced when named is reloaded or restarted
01/16/06 01/16/06 CR46906 SOL5150 Default settings for wide IP load-balancing are different in the on-line help, Configuration utility, and wideip.conf
01/16/06 01/16/06 CR46907 SOL5150 Default settings for wide IP load-balancing are different in the on-line help, Configuration utility, and wideip.conf
01/16/06 01/16/06 CR51441 SOL144 Internal, hidden interfaces may be displayed by bigpipe vlan fdb show
01/16/06 01/16/06 CR35906 SOL144 Internal, hidden interfaces may be displayed by bigpipe vlan fdb show
01/16/06 01/16/06 CR51581 SOL5850 The global update_cached_routes is not saved
01/16/06 01/16/06 CR49623 SOL5851 Incorrect internal masking may cause trunk ports to receive traffic destined for ports in other VLANs
01/16/06 01/16/06 CR51635 SOL5851 Incorrect internal masking may cause trunk ports to receive traffic destined for ports in other VLANs
01/16/06 01/16/06 CR52661 SOL5852 BIG-IP may drop connections through a delayed binding virtual server if the first data packet from the node does not acknowledge all of the data sent by BIG-IP
01/16/06 01/16/06 CR52705 SOL5852 BIG-IP may drop connections through a delayed binding virtual server if the first data packet from the node does not acknowledge all of the data sent by BIG-IP
01/16/06 01/16/06 CR52663 SOL5853 The big3d package included in BIG-IP and 3-DNS version 4.5.13 is not compatible with prior BIG-IP versions
01/16/06 01/16/06 CR52664 SOL5853 The big3d package included in BIG-IP and 3-DNS version 4.5.13 is not compatible with prior BIG-IP versions
01/16/06 01/16/06 CR52827 SOL5854 BIG-IP does not mirror existing connections when a peer becomes available
01/16/06 01/16/06 CR53583 SOL5857 Client certificate check vulnerability in Apache - CVE-2005-2700
01/16/06 01/16/06 CR53585 SOL5857 Client certificate check vulnerability in Apache - CVE-2005-2700
01/16/06 01/16/06 CR53605 SOL4326 Crashes, hangs, and other significant disruptions that are corrected in BIG-IP version 4.5.14
01/16/06 01/16/06 CR53606 SOL4326 Crashes, hangs, and other significant disruptions that are corrected in BIG-IP version 4.5.14
01/16/06 01/16/06 CR20760 SOL5388 The Configuration utility implies that a wide IP alias must be configured
01/16/06 01/16/06 CR53664 SOL5859 BIG-IP may crash and reboot when you use the Reset all Statistics function in the Configuration utility
01/16/06 01/16/06 CR53665 SOL5859 BIG-IP may crash and reboot when you use the Reset all Statistics function in the Configuration utility
01/16/06 01/16/06 CR54058 SOL5860 GSSAPI authentication vulnerability in OpenSSH - CAN-2005-2798
01/16/06 01/16/06 CR54059 SOL5860 GSSAPI authentication vulnerability in OpenSSH - CAN-2005-2798
01/16/06 01/16/06 CR47540 SOL5863 BIG-IP creates a route on the loopback interface for forwarding virtual servers that represent a single IP address
01/16/06 01/16/06 CR54467 SOL5863 BIG-IP creates a route on the loopback interface for forwarding virtual servers that represent a single IP address
01/16/06 01/16/06 CR54742 SOL5858 The fix for CR44712/CR44807 caused a performance decrease
01/16/06 01/16/06 CR54742 SOL5858 The fix for CR44712/CR44807 caused a performance decrease
01/16/06 01/16/06 CR57149 SOL3768 The description of the OID loadBalTrapPortString is confusing
01/16/06 01/16/06 CR57150 SOL3768 The description of the OID loadBalTrapPortString is confusing
01/16/06 01/16/06 CR57700 SOL5869 BIG-IP may specify a source port of 0 when the use_incrementing_autoport internal variable is enabled
01/16/06 01/16/06 CR57701 SOL5869 BIG-IP may specify a source port of 0 when the use_incrementing_autoport internal variable is enabled
01/16/06 01/16/06 CR57929 SOL5868 Buffer overflow vulnerability in cURL - CVE-2005-4077
01/16/06 01/16/06 CR57928 SOL5868 Buffer overflow vulnerability in cURL - CVE-2005-4077
01/16/06 01/16/06 CR58135 SOL5828 Zone changes are not synced when named is reloaded or restarted
01/16/06 01/16/06 CR55070 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 CR55203 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 CR55204 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 CR55283 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 CR55426 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
[ Top ]

Fixes and enhancements in prior releases

To view fixes and enhancements that were distributed in prior releases, see the previous release notes on AskF5.

[ Top ]

Known issues

The following items are known issues in the current release. To sort by column, click a column header.

Added Revised CR Solution Description
03/06/07 03/06/07 CR58321 SOL6551 Changes in US and Canada Daylight Saving Time
01/16/06 01/16/06 CR28429 SOL1566 The Setup utility does not allow VLAN names with more than 12 characters
01/16/06 01/16/06 CR41900 SOL1566 The Setup utility does not allow VLAN names with more than 12 characters
01/16/06 01/16/06 No CR SOL2279 The network interface LED indicators on the rear panel of the BIG-IP 520 and BIG-IP 540 server appliance do not work correctly
01/16/06 01/16/06 CR29967 SOL2853 You cannot use the Configuration utility to make changes to wide IPs that use ports that are not listed in the port menu
01/16/06 01/16/06 CR32977 SOL2853 You cannot use the Configuration utility to make changes to wide IPs that use ports that are not listed in the port menu
01/16/06 01/16/06 CR41876 SOL2853 You cannot use the Configuration utility to make changes to wide IPs that use ports that are not listed in the port menu
01/16/06 01/16/06 CR30783 SOL2942 On BIG-IP and 3-DNS combination systems, default gateways are converted to gateway pools
01/16/06 01/16/06 CR41803 SOL2942 On BIG-IP and 3-DNS combination systems, default gateways are converted to gateway pools
01/16/06 01/16/06 CR41599 SOL3024 The netstat utility does not display VLAN MAC addresses correctly
01/16/06 01/16/06 CR41971 SOL3024 The netstat utility does not display VLAN MAC addresses correctly
01/16/06 01/16/06 CR32245 SOL3036 BIG-IP and 3-DNS may not respond to non-original MAC addresses when auto lasthop is enabled
01/16/06 01/16/06 CR33921 SOL3657 The "memAvailReal" OID reports more available memory than the "vmstat" command does
01/16/06 01/16/06 CR41919 SOL3657 The "memAvailReal" OID reports more available memory than the "vmstat" command does
01/16/06 01/16/06 CR44570 SOL4160 3-DNS marks down BIG-IP version 9 virtual servers that are configured to use rules
01/16/06 01/16/06 CR44804 SOL4237 3-DNS version 4 may mark virtual servers on BIG-IP LTM versions 9.0 through 9.0.4 as unknown
01/16/06 01/16/06 CR44805 SOL4237 3-DNS version 4 may mark virtual servers on BIG-IP LTM versions 9.0 through 9.0.4 as unknown
01/16/06 01/16/06 CR30877 SOL4242 The im -Q command does not always report the correct versions for installed packages
01/16/06 01/16/06 CR45293 SOL4288 BIG-IP version 9 iQuery messages have an incorrect time stamp
01/16/06 01/16/06 CR42843 SOL4326 Problems that cause crashes, panics, hangs in BIG-IP versions 4.5 - 4.5.14 and versions 4.6 - 4.6.4
01/16/06 01/16/06 CR44302 SOL4326 Problems that cause crashes, panics, hangs in BIG-IP versions 4.5 - 4.5.14 and versions 4.6 - 4.6.4
01/16/06 01/16/06 CR44320 SOL4326 Problems that cause crashes, panics, hangs in BIG-IP versions 4.5 - 4.5.14 and versions 4.6 - 4.6.4
01/16/06 01/16/06 CR44321 SOL4326 Problems that cause crashes, panics, hangs in BIG-IP versions 4.5 - 4.5.14 and versions 4.6 - 4.6.4
01/16/06 01/16/06 CR44376 SOL4326 Problems that cause crashes, panics, hangs in BIG-IP versions 4.5 - 4.5.14 and versions 4.6 - 4.6.4
01/16/06 01/16/06 CR44712 SOL4326 Problems that cause crashes, panics, hangs in BIG-IP versions 4.5 - 4.5.14 and versions 4.6 - 4.6.4
01/16/06 01/16/06 CR45496 SOL4343 BIG-IP LTM version 9 does not use lasthop correctly with UDP iQuery datagrams
01/16/06 01/16/06 CR41267 SOL4378 The man page for the dig command is not included
01/16/06 01/16/06 CR46509 SOL4497 BIG-IP and 3-DNS switch appliances may not send an SNMP trap at boot
01/16/06 01/16/06 No CR SOL4574 BIG-IP and 3-DNS do not prevent installation on platforms that are no longer supported
01/16/06 01/16/06 CR28072 SOL467 It is possible to partially remove a link by deleting its self IP address and VLAN
01/16/06 01/16/06 CR41833 SOL467 It is possible to partially remove a link by deleting its self IP address and VLAN
01/16/06 01/16/06 CR47748 SOL4781 BIG-IP LTM may respond to 3-DNS discovery and automatic configuration with an IP address of zero
01/16/06 01/16/06 CR28099 SOL486 The 3-DNS Controller still uses BIG-IP systems for probing when all prober factories have been deleted
01/16/06 01/16/06 CR41834 SOL486 The 3-DNS Controller still uses BIG-IP systems for probing when all prober factories have been deleted
01/16/06 01/16/06 CR26784 SOL5030 3-DNS will not respond to requests until it receives an updated persistence table from the synchronization group
01/16/06 01/16/06 CR23224 SOL5032 The Configuration utility adds a new wide IP alias, rather than changing the name of a wide IP
01/16/06 01/16/06 CR30212 SOL5032 The Configuration utility adds a new wide IP alias, rather than changing the name of a wide IP
01/16/06 01/16/06 CR41816 SOL5032 The Configuration utility adds a new wide IP alias, rather than changing the name of a wide IP
01/16/06 01/16/06 CR36782 SOL5035 The ntpd daemon is not restarted after the Setup utility is used to make time server configuration changes
01/16/06 01/16/06 CR42107 SOL5035 The ntpd daemon is not restarted after the Setup utility is used to make time server configuration changes
01/16/06 01/16/06 CR27219 SOL5055 3dns_add will not add a Link Controller to an existing sync group
01/16/06 01/16/06 CR41894 SOL5055 3dns_add will not add a Link Controller to an existing sync group
01/16/06 01/16/06 CR14955 SOL5078 The Configuration utility allows characters in configuration objects that 3dpipe does not allow
01/16/06 01/16/06 CR14956 SOL5078 The Configuration utility allows characters in configuration objects that 3dpipe does not allow
01/16/06 01/16/06 CR16971 SOL5078 The Configuration utility allows characters in configuration objects that 3dpipe does not allow
01/16/06 01/16/06 CR16972 SOL5078 The Configuration utility allows characters in configuration objects that 3dpipe does not allow
01/16/06 01/16/06 CR16973 SOL5078 The Configuration utility allows characters in configuration objects that 3dpipe does not allow
01/16/06 01/16/06 CR17173 SOL5078 The Configuration utility allows characters in configuration objects that 3dpipe does not allow
01/16/06 01/16/06 CR28228 SOL509 The 3-DNS Controller or the BIG-IP Link Controller may not properly create configuration statements for redundant pairs
01/16/06 01/16/06 CR28529 SOL509 The 3-DNS Controller or the BIG-IP Link Controller may not properly create configuration statements for redundant pairs
01/16/06 01/16/06 CR41837 SOL509 The 3-DNS Controller or the BIG-IP Link Controller may not properly create configuration statements for redundant pairs
01/16/06 01/16/06 CR46906 SOL5150 Default settings for wide IP load-balancing are different in the on-line help, Configuration utility, and wideip.conf
01/16/06 01/16/06 CR46907 SOL5150 Default settings for wide IP load-balancing are different in the on-line help, Configuration utility, and wideip.conf
01/16/06 01/16/06 CR30243 SOL5191 The big3d daemon included in versions 4.5 PTF-04 and later is not compatible with BIG-IP version 4.5
01/16/06 01/16/06 CR29281 SOL5263 Systems that are licensed for both BIG-IP and 3-DNS automatically add a router statement and perform a health check on the router
01/16/06 01/16/06 CR42027 SOL5263 Systems that are licensed for both BIG-IP and 3-DNS automatically add a router statement and perform a health check on the router
01/16/06 01/16/06 CR28330 SOL5360 The Configuration utility menu bar does not scale to small window sizes
01/16/06 01/16/06 CR28331 SOL5360 The Configuration utility menu bar does not scale to small window sizes
01/16/06 01/16/06 CR40319 SOL694 An error displays if you refresh the Configuration utility after creating a link
01/16/06 01/16/06 CR41860 SOL694 An error displays if you refresh the Configuration utility after creating a link
01/16/06 01/16/06 CR32977 SOL758 BIG-IP doesn't provide a list from which to select an option in the wide IP port field
01/16/06 01/16/06 CR41876 SOL758 BIG-IP doesn't provide a list from which to select an option in the wide IP port field
01/16/06 01/16/06 CR33815 SOL761 The table that contains Nokia NetAct SNMP traps may become very large and use disk space
01/16/06 01/16/06 CR41877 SOL761 The table that contains Nokia NetAct SNMP traps may become very large and use disk space
01/16/06 01/16/06 CR35019 SOL763 Link Controllers will not display statistics for virtual servers that are not part of a wide IP
01/16/06 01/16/06 CR41878 SOL763 Link Controllers will not display statistics for virtual servers that are not part of a wide IP
01/16/06 01/16/06 CR36729 SOL764 Wide IPs created in the Link Controller Configuration utility are not included in NameSurfer
01/16/06 01/16/06 CR41882 SOL764 Wide IPs created in the Link Controller Configuration utility are not included in NameSurfer
01/16/06 01/16/06 CR14294 SOL765 The Generate and Copy iQuery Encryption Key option detects BIG-IP/3-DNS combination products twice and attempts to copy the iQuery keys to each detected unit
01/16/06 01/16/06 CR41884 SOL765 The Generate and Copy iQuery Encryption Key option detects BIG-IP/3-DNS combination products twice and attempts to copy the iQuery keys to each detected unit
01/16/06 01/16/06 CR23564 SOL783 Saved copies and new copies of snmptrap.conf can conflict after an upgrade
01/16/06 01/16/06 CR41889 SOL783 Saved copies and new copies of snmptrap.conf can conflict after an upgrade
01/16/06 01/16/06 CR24946 SOL815 The link to the BIG-IP Link Controller Solutions Guide is missing
01/16/06 01/16/06 CR41890 SOL815 The link to the BIG-IP Link Controller Solutions Guide is missing
01/16/06 01/16/06 CR25821 SOL816 F5 source addresses are not added to hosts.allow when the support account is enabled
01/16/06 01/16/06 CR41891 SOL816 F5 source addresses are not added to hosts.allow when the support account is enabled
[ Top ]