Applies To:

Show Versions Show Versions

Archived Release Note: 3-DNS Controller version 4.5.14
Release Note

Software Release Date: 01/30/2006
Updated Date: 01/19/2011

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

Summary:

This release note documents version 4.5.14 of the 3-DNS® 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 Description of the F5 Networks software version number format.

Contents:

- Minimum system requirements and supported browsers
- Installing the software
     - Updating the big3d agent
- Activating the license
- New fixes and enhancements in this release
- Fixes and enhancements in prior maintenance releases
- Required configuration changes
- Known issues


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

Note: The IM package for this release is quite large. If the disk drive in your platform does not meet the minimum requirement, you may not be able to successfully install this release.

[ Top ]

Installing the software

Important: If you are upgrading a 3-DNS Controller that belongs to a sync group, you must remove the controller from the sync group before you apply the release. Failure to do so may cause irrevocable damage to the controllers in the sync group that are running older versions of the software. Once you have upgraded all controllers to the same version, you can then re-create the sync group. For details on removing a controller from a sync group, see Removing a controller from a sync group. Once you have removed the controller from the sync group, you can proceed with the installation.

Note:  If you are installing the 3-DNS Controller module on a BIG-IP system, refer to the BIG-IP version 4.5.14 note for instructions about installing the software. Installing the 4.5.14 software on BIG-IP version 4.5 also applies the upgrade to the 3-DNS module. The enhancements, fixes, and known issues for the 3-DNS Controller, however, are available only in the 3-DNS Controller version 4.5.14 release note.

Note:  If you have installed prior releases, this installation does not overwrite any configuration changes that you made for the prior releases.

The following instructions explain how to install the 3-DNS Controller version 4.5.14 onto existing systems running version 4.2 and later. The installation script saves your current configuration.

Once you install and license the software, refer to the Required configuration changes section, which contains important information about changes you must make before using the new software.

  1. Go to the Downloads site and locate the 3-DNS version 4.5.14 upgrade file, BIGIP_4.5.14_Upgrade.im.

    3-DNS is not listed as a product line on the Downloads site; the image file is listed under the BIG-IP 4.x product line.

  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 3-DNS 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 3-DNS Controller automatically reboots once it completes installation.

Updating the big3d agent

After the installation has completed, you need to install the new version of the big3d agent on all BIG-IP systems known to the 3-DNS Controller, as follows:
 

  1. Log on to the 3-DNS Controller at the command line.
     
  2. Type 3dnsmaint to open the 3-DNS Maintenance menu.
     
  3. Select Install and Start big3d, and press Enter.
    The 3-DNS Controller detects all BIG-IP systems in the network, and updates their big3d agents with the appropriate version of the agent.
     
  4. Press Enter to return to the 3-DNS Maintenance menu.
     
  5. Type Q to quit.

For more information about the big3d agent, see the 3-DNS Reference Guide.

[ Top ]

Activating the license

Once you install the upgrade and connect the controller 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 controller. This method automatically retrieves and submits the dossier to the F5 Networks license server, as well as installs the signed license certificate. In order for you to use this method, the controller must be installed on a network with Internet access.
     
  • Manual license activation
    You perform manual license activation from the Configuration utility, which is the browser-based user interface. With this method, you submit the dossier to, and retrieve the signed license file from, the F5 Networks license server manually. In order for you to use this method, the administrative work station must have Internet access.

Note:  You can open the Configuration utility using either 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 appear:

    IP:
    Netmask:
    Default Route:
    Select interface to use to retrieve license:

    The 3-DNS Controller 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 controller retrieves and sends the dossier to the F5 Networks license server, and the F5 Networks license server returns and installs a signed license file. 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. Press Enter to reboot the system.
    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.

    The following prompt displays:

    Number of keys: 1

  4. If you have more than one registration key, enter the appropriate number, and press Enter.

    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 controller retrieves and sends the dossier to the F5 Networks license server, and the F5 Networks license server returns and installs a signed license file. A message displays indicating the process was successful.
     

To manually activate a license using the Configuration utility

You can use the Configuration utility to manually activate a license for a previously-configured 3-DNS Controller and for a new controller. Before you can activate the license, however, you must log on to the Configuration utility.

To open the Configuration utility for an existing 3-DNS Controller

  1. Open the Configuration utility using the configured address.
     
  2. Type your user name and password at the logon prompt, and click OK.
    The Configuration utility home screen displays.

To open the Configuration utility for a new 3-DNS Controller

  1. From the administrative work station, 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 root and the password default at the logon prompt, and click OK.
    The Configuration utility home screen displays.

Once you have successfully logged on to the Configuration utility, you can proceed with the manual license activation.

To manually activate a license using the Configuration utility

  1. Click License Utility to open the License Administration screen.
     
  2. 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.
     
  3. 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.
  4. Click the link in the License Server box.
    The Activate F5 License screen opens in a new browser window.
     
  5. 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.
     
  6. 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.
  7. Return to the Manual Authorization screen, and click Continue.
     
  8. 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.
     
  9. Click License Terms, review the EULA, and accept it.
     
  10. At the Reboot Prompt screen, select when you want to reboot the platform.
    You must reboot the controller to complete the license activation.

To automatically activate a license using the Configuration utility

You can use the Configuration utility to automatically activate a license for a previously-configured 3-DNS Controller and for a new controller. Before you can activate the license, however, you must log on to the Configuration utility.

To open the Configuration utility for an existing 3-DNS Controller

  1. Open the Configuration utility using the configured address.
     
  2. Type your user name and password at the logon prompt, and click OK.
    The Configuration utility home screen displays.

To open the Configuration utility for a new 3-DNS Controller

  1. From the administrative work station, 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 root and the password default at the logon prompt, and click OK.
    The Configuration utility home screen displays.

Once you have successfully logged on to the Configuration utility, you can proceed with the automatic license activation.

To automatically activate a license using the Configuration utility

  1. Click License Utility to open the License Administration screen.
     
  2. 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.
     
  3. Click License Terms, review the EULA, and accept it.
     
  4. At the Reboot Prompt screen, select when you want to reboot the platform.
    You must reboot the controller to complete the license activation.
[ 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 now 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 and enhancements.

Added Revised CR Solution Description
01/16/06 01/16/06 29394 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 29395 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 44999 SOL5828 Zone changes are not synced when named is reloaded or restarted
01/16/06 01/16/06 51441 SOL144 Internal, hidden interfaces may be displayed by bigpipe vlan fdb show
01/16/06 01/16/06 35906 SOL144 Internal, hidden interfaces may be displayed by bigpipe vlan fdb show
01/16/06 01/16/06 51581 SOL5850 The global update_cached_routes is not saved
01/16/06 01/16/06 52663 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 52664 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 53583 SOL5857 Client certificate check vulnerability in Apache - CVE-2005-2700
01/16/06 01/16/06 53585 SOL5857 Client certificate check vulnerability in Apache - CVE-2005-2700
01/16/06 01/16/06 53605 SOL4326 Crashes, hangs, and other significant disruptions that are corrected in BIG-IP version 4.5.14
01/16/06 01/16/06 53606 SOL4326 Crashes, hangs, and other significant disruptions that are corrected in BIG-IP version 4.5.14
01/16/06 01/16/06 54058 SOL5860 GSSAPI authentication vulnerability in OpenSSH - CAN-2005-2798
01/16/06 01/16/06 54059 SOL5860 GSSAPI authentication vulnerability in OpenSSH - CAN-2005-2798
01/16/06 01/16/06 57149 SOL3768 The description of the OID loadBalTrapPortString is confusing
01/16/06 01/16/06 57150 SOL3768 The description of the OID loadBalTrapPortString is confusing
01/16/06 01/16/06 57929 SOL5868 Buffer overflow vulnerability in cURL - CVE-2005-4077
01/16/06 01/16/06 57928 SOL5868 Buffer overflow vulnerability in cURL - CVE-2005-4077
01/16/06 01/16/06 58135 SOL5828 Zone changes are not synced when named is reloaded or restarted
01/16/06 01/16/06 55070 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 55203 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 55204 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 55283 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
01/16/06 01/16/06 55426 SOL5533 Potential protocol version rollback vulnerability in OpenSSL - CVE-2005-2969
[ Top ]

Fixes and enhancements in prior maintenance releases

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

[ Top ]

Required configuration changes

Once you have installed the software, you must make the following required configuration changes, if appropriate.

Removing a controller from a sync group

If you are upgrading a 3-DNS Controller that belongs to a sync group, you must remove the controller from the sync group before you apply the upgrade. Once you have upgraded all controllers to the same version, you can then re-create the sync group. Once you have removed the controller from the sync group, you can proceed with the upgrade installation.

Note: You can re-create the sync group once you have upgraded the software for all of the controllers that belong to the sync group.

To remove a controller from a sync group using the Configuration utility

  1. In the navigation pane, click 3-DNS Sync.
    The Synchronization screen opens.
     
  2. In the Remove column, next to the controller that you want to remove from the sync group, click the Remove button.
    A popup screen opens to confirm the removal of the controller.
     
  3. Click OK.
    The screen refreshes, and the controller is no longer listed as a member of the sync group.
     
  4. Repeat these tasks for any additional sync group members that you want to remove from the sync group.

Alternately, you can remove the entire sync group, instead of removing the controllers one at a time.

To remove a sync group using the Configuration utility

  1. In the navigation pane, click 3-DNS Sync.
    The Synchronization screen opens.
     
  2. On the toolbar, click Remove this Group.
    A popup screen opens to confirm the removal of the sync group.
     
  3. Click OK.
    The screen refreshes, and the Add a New Sync Group screen opens, where you can re-create your sync group once you have upgraded the software on all of the controllers that belong to the sync group.
     

 

[ 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 58321 SOL6551 Changes in US and Canada Daylight Saving Time
08/30/06 08/30/06 CR26610 SOL336 Disabling SNMP traps using the Configuration utility causes an error
08/30/06 08/30/06 CR27260 SOL371 Default gateway pools cannot be changed using the config command
01/16/06 01/16/06 CR27823 SOL1290 The 3-DNS Controller adds a forward slash (/) to the beginning of text added to the File Name field
01/16/06 01/16/06 CR41897 SOL1290 The 3-DNS Controller adds a forward slash (/) to the beginning of text added to the File Name field
01/16/06 01/16/06 CR28348 SOL1491 The Configuration utility appears to allow you to disable a datacenter, but does not actually change the configuration
01/16/06 01/16/06 CR41899 SOL1491 The Configuration utility appears to allow you to disable a datacenter, but does not actually change the configuration
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 CR28459 SOL1664 Modifying a data center from the Configuration utility results in an error
01/16/06 01/16/06 CR28534 SOL1664 Modifying a data center from the Configuration utility results in an error
01/16/06 01/16/06 CR41902 SOL1664 Modifying a data center from the Configuration utility results in an error
01/16/06 01/16/06 CR28901 SOL1687 There is no bounds check on the time that is entered when an object is disabled
01/16/06 01/16/06 CR41903 SOL1687 There is no bounds check on the time that is entered when an object is disabled
01/16/06 01/16/06 CR31239 SOL1865 The Clear LDNS Statistics button in the Configuration utility does not work
01/16/06 01/16/06 CR41909 SOL1865 The Clear LDNS Statistics button in the Configuration utility does not work
01/16/06 01/16/06 CR31928 SOL1866 It is not possible to create a default gateway pool on a stand-alone 3-DNS system
01/16/06 01/16/06 CR41911 SOL1866 It is not possible to create a default gateway pool on a stand-alone 3-DNS system
01/16/06 01/16/06 CR31946 SOL1902 3dnsmaint may report an error when you attempt to set up SSH communication
01/16/06 01/16/06 CR41912 SOL1902 3dnsmaint may report an error when you attempt to set up SSH communication
01/16/06 01/16/06 CR23431 SOL2072 All 3-DNS Controllers in a synchronization group may update at the same time, causing an interruption in service
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 CR26833 SOL2340 3-DNS does not use BIG-IP connection limits
01/16/06 01/16/06 CR27235 SOL2438 NameSurfer creates an authoritative top level zone when you create a wide IP that does not begin with www
01/16/06 01/16/06 CR27275 SOL2438 NameSurfer creates an authoritative top level zone when you create a wide IP that does not begin with www
01/16/06 01/16/06 CR27618 SOL2557 It is not possible to define additional files for synchronization in 3-DNS version 4.5 and later
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 CR19648 SOL320 The instructions displayed on the Setup utility splash screen contain the wrong instructions for starting the Configuration utility
01/16/06 01/16/06 CR19672 SOL320 The instructions displayed on the Setup utility splash screen contain the wrong instructions for starting the Configuration utility
01/16/06 01/16/06 CR41810 SOL320 The instructions displayed on the Setup utility splash screen contain the wrong instructions for starting the Configuration utility
01/16/06 01/16/06 CR33666 SOL3343 The reported value for pending probes may be inaccurate after a link has been down
01/16/06 01/16/06 CR41917 SOL3343 The reported value for pending probes may be inaccurate after a link has been down
01/16/06 01/16/06 CR25575 SOL3505 The /config partition may not be large enough to contain very large DNS configurations
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 CR35714 SOL3818 Error messages are logged on 3-DNS systems when bigstart restart is run
01/16/06 01/16/06 CR41922 SOL3818 Error messages are logged on 3-DNS systems when bigstart restart is run
01/16/06 01/16/06 CR27501 SOL399 The config command reports an unnecessary error when a copy of 3dnsd is already running
01/16/06 01/16/06 CR41826 SOL399 The config command reports an unnecessary error when a copy of 3dnsd is already running
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 CR42764 SOL4209 RRD graphs are being improperly cached
01/16/06 01/16/06 CR44148 SOL4209 RRD graphs are being improperly cached
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 CR27791 SOL437 An error is logged to /var/log/3dns when a router is not configured for a datacenter
01/16/06 01/16/06 CR41829 SOL437 An error is logged to /var/log/3dns when a router is not configured for a datacenter
01/16/06 01/16/06 CR41267 SOL4378 The man page for the dig command is not included
01/16/06 01/16/06 CR27799 SOL445 An error may be reported when synchronizing iQuery keys
01/16/06 01/16/06 CR41830 SOL445 An error may be reported when synchronizing iQuery keys
01/16/06 01/16/06 CR27923 SOL446 The network map never marks pool virtual servers as red
01/16/06 01/16/06 CR27924 SOL446 The network map never marks pool virtual servers as red
01/16/06 01/16/06 CR41831 SOL446 The network map never marks pool virtual servers as red
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 CR34737 SOL5041 The Configuration utility only allows IP addresses that end in .255 to be used as broadcast addresses
01/16/06 01/16/06 CR42101 SOL5041 The Configuration utility only allows IP addresses that end in .255 to be used as broadcast addresses
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 CR27820 SOL5057 A startup conflict may occur between the big3d and 3dnsd daemons
01/16/06 01/16/06 CR47531 SOL5064 The 3dnsd daemon may crash if several hundred BIG-IP objects are added to the configuration
01/16/06 01/16/06 CR47532 SOL5064 The 3dnsd daemon may crash if several hundred BIG-IP objects are added to the configuration
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 CR33671 SOL5137 3-DNS does not use a changed value for Check Static Dependencies until 3dnsd is restarted
01/16/06 01/16/06 CR41804 SOL5137 3-DNS does not use a changed value for Check Static Dependencies until 3dnsd is restarted
01/16/06 01/16/06 CR30139 SOL5169 3-DNS marks the status of SSL proxies that use remote target servers as unknown (blue)
01/16/06 01/16/06 CR31388 SOL5178 The full_debug script may create duplicate or overlapping syslog statements
01/16/06 01/16/06 CR20183 SOL5179 The 3dpipe command does not accept pool names that consists entirely of numerals
01/16/06 01/16/06 CR27359 SOL5185 3dnsmaint cannot copy big3d to BIG-IP 3.x versions
01/16/06 01/16/06 CR30242 SOL5185 3dnsmaint cannot copy big3d to BIG-IP 3.x versions
01/16/06 01/16/06 CR27037 SOL5186 Configuration database records are not updated when a self IP address is changed
01/16/06 01/16/06 CR09333 SOL5189 The Configuration utility may refresh with information from another 3-DNS or BIG-IP when multiple browser instances are open
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 CR24734 SOL5230 Discovery and automatic configuration sets the unit ID of a 3-DNS or Link Controller redundant peer to unit 1
01/16/06 01/16/06 CR24735 SOL5230 Discovery and automatic configuration sets the unit ID of a 3-DNS or Link Controller redundant peer to unit 1
01/16/06 01/16/06 CR23287 SOL5254 The 3dnsd daemon may crash when the self IP address of a member of a redundant pair is changed
01/16/06 01/16/06 CR43497 SOL5257 Changes are not synchronized when a prober statement is reset to its default setting
01/16/06 01/16/06 CR43498 SOL5257 Changes are not synchronized when a prober statement is reset to its default setting
01/16/06 01/16/06 CR30225 SOL5258 3-DNS may overwrite configuration changes that are made while synchronization is in progress
01/16/06 01/16/06 CR39967 SOL5259 3-DNS may create iQuery messages that are not compatible with 4.2 versions
01/16/06 01/16/06 CR41926 SOL5259 3-DNS may create iQuery messages that are not compatible with 4.2 versions
01/16/06 01/16/06 CR22875 SOL5260 A disabled 3dnsd daemon will re-enable itself when failover occurs
01/16/06 01/16/06 CR28180 SOL5262 3-DNS may create individual server statements for each unit in a redundant pair, rather than a redundant pair statement
01/16/06 01/16/06 CR41835 SOL5262 3-DNS may create individual server statements for each unit in a redundant pair, rather than a redundant pair statement
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 CR24722 SOL5264 3-DNS automatically associates link objects with router objects
01/16/06 01/16/06 CR11703 SOL5265 Production Rules may not revert to the normal load balancing mode when the Stop Time is reached
01/16/06 01/16/06 CR11710 SOL5265 Production Rules may not revert to the normal load balancing mode when the Stop Time is reached
01/16/06 01/16/06 CR27399 SOL5274 Explicit IP and Drop Packet are permitted as Alternate load balancing methods
01/16/06 01/16/06 CR24687 SOL5277 Link Controller displays the remote status of remote wide IPs, rather than their availability on the Link Controller
01/16/06 01/16/06 CR24751 SOL5302 The network map displays disabled virtual servers as available if the Manual Resume setting is enabled
01/16/06 01/16/06 CR24754 SOL5302 The network map displays disabled virtual servers as available if the Manual Resume setting is enabled
01/16/06 01/16/06 CR49888 SOL5351 3-DNS may add an unrelated top level domain when you add a wide IP alias
01/16/06 01/16/06 CR27542 SOL5352 The NameSurfer log file is not rotated and may fill the /var partition
01/16/06 01/16/06 CR28615 SOL5352 The NameSurfer log file is not rotated and may fill the /var partition
01/16/06 01/16/06 CR36844 SOL5352 The NameSurfer log file is not rotated and may fill the /var partition
01/16/06 01/16/06 CR46027 SOL5356 NameSurfer may delete the zone when you remove a secondary name server from the zone
01/16/06 01/16/06 CR27546 SOL5358 Production Rules may change the load balancing mode but do not change the load balancing mode that is displayed
01/16/06 01/16/06 CR30228 SOL5359 The sample BIND configuration files included in 3-DNS do not reference the proper file locations
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 CR50372 SOL5362 The database used to store statistics information may become corrupt, eventually resulting in file descriptor exhaustion
01/16/06 01/16/06 CR23831 SOL5363 3dnsd -v will not report the 3dnsd version if 3dnsd is already running
01/16/06 01/16/06 CR27501 SOL5363 3dnsd -v will not report the 3dnsd version if 3dnsd is already running
01/16/06 01/16/06 CR41826 SOL5363 3dnsd -v will not report the 3dnsd version if 3dnsd is already running
01/16/06 01/16/06 CR27758 SOL5364 3-DNS only uses SNMP version 1 for probing
01/16/06 01/16/06 CR42072 SOL5364 3-DNS only uses SNMP version 1 for probing
01/16/06 01/16/06 CR28210 SOL5365 Systems that are licensed for both BIG-IP and 3-DNS do not send SNMP traps for failed 3-DNS ECV checks
01/16/06 01/16/06 CR42082 SOL5365 Systems that are licensed for both BIG-IP and 3-DNS do not send SNMP traps for failed 3-DNS ECV checks
01/16/06 01/16/06 CR29189 SOL5367 Failed probing may cause strange values in the BIG-IP statistics page
01/16/06 01/16/06 CR30464 SOL5367 Failed probing may cause strange values in the BIG-IP statistics page
01/16/06 01/16/06 CR36766 SOL5367 Failed probing may cause strange values in the BIG-IP statistics page
01/16/06 01/16/06 CR41840 SOL5367 Failed probing may cause strange values in the BIG-IP statistics page
01/16/06 01/16/06 CR18258 SOL5368 The Configuration utility does not display the correct number of LDNS pages
01/16/06 01/16/06 CR18887 SOL5369 The Configuration utility does not allow the use of the Enter key to commit content in the Wide IP Alias name field
01/16/06 01/16/06 CR18859 SOL5370 An error is displayed if you enter the VS dependencies page when only one virtual server is configured
01/16/06 01/16/06 CR24081 SOL5385 Changes made in the Configuration utility are discarded when synchronization begins
01/16/06 01/16/06 CR23770 SOL5386 Statistics graphs may be cached by the web browser
01/16/06 01/16/06 CR24209 SOL5386 Statistics graphs may be cached by the web browser
01/16/06 01/16/06 CR41927 SOL5387 3-DNS does not provide an error when a dynamic load balancing method is chosen but no probers are configured
01/16/06 01/16/06 CR09888 SOL5387 3-DNS does not provide an error when a dynamic load balancing method is chosen but no probers are configured
01/16/06 01/16/06 CR45042 SOL5389 Messages in the log files may report the word "numItems" where they should report a number
01/16/06 01/16/06 CR45283 SOL5389 Messages in the log files may report the word "numItems" where they should report a number
01/16/06 01/16/06 CR18436 SOL5391 It is not possible to successfully upgrade 3-DNS from the Mindterm SSH terminal
01/16/06 01/16/06 CR24750 SOL5392 The network map displays an IP address associated with each wide IP
01/16/06 01/16/06 CR24752 SOL5392 The network map displays an IP address associated with each wide IP
01/16/06 01/16/06 CR28626 SOL554 You cannot manage topology records with a web browser that uses the Sun Java Virtual Machine
01/16/06 01/16/06 CR28627 SOL554 You cannot manage topology records with a web browser that uses the Sun Java Virtual Machine
01/16/06 01/16/06 CR29626 SOL554 You cannot manage topology records with a web browser that uses the Sun Java Virtual Machine
01/16/06 01/16/06 CR41839 SOL554 You cannot manage topology records with a web browser that uses the Sun Java Virtual Machine
01/16/06 01/16/06 CR32755 SOL573 In rare cases, 3-DNS may create a BIG-IP object with an address of 127.0.0.1
01/16/06 01/16/06 CR41844 SOL573 In rare cases, 3-DNS may create a BIG-IP object with an address of 127.0.0.1
01/16/06 01/16/06 CR32762 SOL591 The random pool load balancing mode distributes connections using a fixed ratio
01/16/06 01/16/06 CR41845 SOL591 The random pool load balancing mode distributes connections using a fixed ratio
01/16/06 01/16/06 CR33161 SOL604 After initial configuration of the 3-DNS Controller, auto-configuration may not add all virtual servers
01/16/06 01/16/06 CR41847 SOL604 After initial configuration of the 3-DNS Controller, auto-configuration may not add all virtual servers
01/16/06 01/16/06 CR33735 SOL653 The summary statistics provided for BIG-IP systems are inaccurate
01/16/06 01/16/06 CR41849 SOL653 The summary statistics provided for BIG-IP systems are inaccurate
01/16/06 01/16/06 CR37656 SOL659 Adding aliases to wide IPs can lead to NameSurfer zone corruption
01/16/06 01/16/06 CR41853 SOL659 Adding aliases to wide IPs can lead to NameSurfer zone corruption
01/16/06 01/16/06 CR38163 SOL681 The Explicit IP, Return to DNS, None, and Drop Packet load balancing modes do not work correctly
01/16/06 01/16/06 CR41855 SOL681 The Explicit IP, Return to DNS, None, and Drop Packet load balancing modes do not work correctly
01/16/06 01/16/06 CR38193 SOL688 The Hops, RTT, and QoS load balancing modes return a single virtual server if probing is disabled
01/16/06 01/16/06 CR38491 SOL688 The Hops, RTT, and QoS load balancing modes return a single virtual server if probing is disabled
01/16/06 01/16/06 CR41856 SOL688 The Hops, RTT, and QoS load balancing modes return a single virtual server if probing is disabled
01/16/06 01/16/06 CR41858 SOL688 The Hops, RTT, and QoS load balancing modes return a single virtual server if probing is disabled
01/16/06 01/16/06 CR38340 SOL692 Sync groups allow synchronization across versions
01/16/06 01/16/06 CR41857 SOL692 Sync groups allow synchronization across versions
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 CR32729 SOL743 You cannot configure the ECV scan level of "none" using the Configuration utility
01/16/06 01/16/06 CR41843 SOL743 You cannot configure the ECV scan level of "none" using the Configuration utility
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 CR20337 SOL766 Debugging commands are not entirely removed from 3-DNS
01/16/06 01/16/06 CR41886 SOL766 Debugging commands are not entirely removed from 3-DNS
01/16/06 01/16/06 CR21176 SOL767 Changing the address of a wide IP to an invalid address can cause the Configuration utility to become unstable
01/16/06 01/16/06 CR41887 SOL767 Changing the address of a wide IP to an invalid address can cause the Configuration utility to become unstable
01/16/06 01/16/06 CR22374 SOL780 The Last Hit column on the Requests Statistics page actually displays persistence expiration
01/16/06 01/16/06 CR41888 SOL780 The Last Hit column on the Requests Statistics page actually displays persistence expiration
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 CR37565 SOL814 After logging out, you cannot log in to NameSurfer as the same user
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 ]

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)