Applies To:

Show Versions Show Versions

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

Software Release Date: 07/21/2005
Updated Date: 03/05/2007

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

Summary:

This release note documents version 4.5.13 of the 3-DNS® Controller software. You can apply the software upgrade to version 4.2 and later. For information about installing the software, please refer to the instructions below.

F5 now offers both maintenance and new feature releases. Version 4.5.13 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 policies, please 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
     - Changes to existing features
- 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.13 note for instructions on installing the software. Installing the 4.5.13 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.13 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.13 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.13 upgrade file, BIGIP_4.5.13_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.13_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 command:
    md5 BIGIP_4.5.13_Upgrade.im
    cat BIGIP_4.5.13_Upgrade.md5

    The two md5 values should be identical.



  5. Install the IM by typing the following command:
    im BIGIP_4.5.13_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]:

    Type Y, and the following prompt displays:
    Registration Key:

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

  5. You are asked to accept the End User License Agreement (EULA).
    Note that the system is not fully functional until you accept this agreement.

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

  4. The following prompt displays:
    Number of keys: 1
    If you have more than one registration key, enter the appropriate number, and press Enter.

  5. 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 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 ]

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.

Solution Description
SOL4570 Support for the EDGE-FX Cache has been removed from this version
SOL4894 The 3-DNS Controller now staggers probes, rather than sending them all at once
[ Top ]

New fixes and enhancements in this release

Note: 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.

CR Solution Description
CR22419 SOL4408 Inability to delete files during an upgrade can result in unallocated iNodes
CR36377 SOL4405 High speed interface statistics are reported in the wrong units
CR41881 SOL4405 High speed interface statistics are reported in the wrong units
CR41948 SOL4408 Inability to delete files during an upgrade can result in unallocated iNodes
CR42715 SOL4431 Hotfixed kernels with names longer than 63 characters could cause problems with configuration commands
CR42791 SOL4210 The bigpipe command might occasionally become unresponsive due to insufficient error handling
CR42792 SOL4210 The bigpipe command might occasionally become unresponsive due to insufficient error handling
CR45625 SOL4559 3dnsd has a small memory leak
CR45736 SOL4559 3dnsd has a small memory leak
CR45780 SOL4431 Hotfixed kernels with names longer than 63 characters could cause problems with configuration commands
CR46405 SOL4810 The BIG-IP system and 3-DNS Controller might report "date not found" during installation
CR46407 SOL4810 The BIG-IP system and 3-DNS Controller might report "date not found" during installation
CR46892 SOL4441 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0468 and CAN-2005-0469
CR46923 SOL4441 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0468 and CAN-2005-0469
CR46924 SOL4441 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0468 and CAN-2005-0469
CR46925 SOL4447 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0490
CR46931 SOL4447 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0490
CR46932 SOL4447 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0490
CR47075 SOL4326 Crashes, panics, hangs, and reboots that were fixed in recent releases
CR47076 SOL4326 Crashes, panics, hangs, and reboots that were fixed in recent releases
CR47235 SOL4572 The login.conf file might be overwritten during an upgrade
CR47236 SOL4572 The login.conf file might be overwritten during an upgrade
CR47240 SOL4450 The message IMPROPERLY FORMATTED TEXT DELETED is incorrectly appended to many SNMP traps
CR47264 SOL4450 The message IMPROPERLY FORMATTED TEXT DELETED is incorrectly appended to many SNMP traps
CR47558 SOL4441 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0468 and CAN-2005-0469
CR47917 SOL5077 The Configuration utility might become unresponsive when displaying production rules
CR47918 SOL5077 The Configuration utility might become unresponsive when displaying production rules
CR48152 SOL4809 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-1278, CAN-2005-1279, and CAN-2005-1280
CR48153 SOL4809 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-1278, CAN-2005-1279, and CAN-2005-1280
CR48448 SOL4450 The message IMPROPERLY FORMATTED TEXT DELETED is appended to many SNMP traps
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 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0488
CR49337 SOL4616 The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0488
CR49505 SOL4326 3dnsd might become unresponsive when a very large configuration is loaded and the unit is configured as a receiver
CR49506 SOL4326 3dnsd might become unresponsive when a very large configuration is loaded and the unit is configured as a receiver
[ 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.

CR Solution Description
CR9333 SOL5189 Multiple instances of the Configuration utility may overwrite each other
CR11703 SOL5265 Production rules do not stop when the Stop Time is reached
CR11710 SOL5265 Production rules do not stop when the Stop Time is reached
CR14294 SOL765 The Generate and Copy iQuery Encryption Key option detects BIG-IP system/3-DNS Controller combination products twice and attempts to copy the iQuery keys to each detected unit
CR14955 SOL5078 The Configuration utility allows special characters in configuration object names
CR14956 SOL5078 The Configuration utility allows special characters in configuration object names
CR16629 SOL311 The production rule wizard does not allow changes to QOS settings for existing rules
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
CR18008 SOL312 Equivalence operators in production rules must be separated on either side with a space
CR18859 SOL5370 The Configuration utility reports an error if you attempt to add an invalid VS dependency
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 for VS Capacity and Kilobytes/Second might change
CR20322 SOL328 Ports List screen does not display the ports enabled for a wide IP
CR20337 SOL766 Debugging commands are not entirely removed from the 3-DNS Controller
CR21176 SOL767 Changing the address of a wide IP to an invalid address can cause the 3dnsconf.cgi file to become unstable
CR21513 SOL334 The Configuration utility might become unstable if a router is configured with multiple self IP addresses
CR22374 SOL780 The Last Hit column on the Requests Statistics screen actually displays persistence expiration
CR22875 SOL5260 A unit in a redundant pair may still become active when 3dnsd is disabled
CR23224 SOL5032 The Configuration utility does not correctly modify wide IP names
CR23287 SOL5254 Correcting mis-matched self IP addresses in an active-active system may cause 3dnsd to crash
CR23564 SOL783 Saving a new copy of snmptrap.conf file can create a conflict after an upgrade
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
CR25821 SOL816 F5 source addresses are not added to the hosts.allow file when the support account is enabled
CR26610 SOL336 Disabling SNMP traps using the Configuration utility causes an error
CR26784 SOL5030 3-DNS may not respond to requests after upgrade if persistence and a sync group are configured
CR27037 SOL5186 Changing a self IP address does not change associated bigdb entries
CR27260 SOL371 You cannot change default gateway pools using the config command
CR27359 SOL5185 3dnsmaint cannot copy big3d to BIG-IP 3.x versions
CR27399 SOL5274 Explicit IP and Drop Packet are allowed as Alternate load balancing methods
CR27501 SOL399 The config command reports an unnecessary error when a copy of 3dnsd is already running
CR27791 SOL437 An error is logged to the /var/log/3dns file when a router is not configured for a datacenter
CR27799 SOL445 An error might be reported when synchronizing iQuery keys
CR27820 SOL5057 The error message "WARN:FlushAllIQM: iqBufFlush() failed" may be logged after restart
CR27823 SOL1290 The 3-DNS Controller adds a forward slash (/) to the beginning of the text added to the File Name field
CR27923 SOL446 The network map never marks pool virtual servers red
CR27924 SOL446 The network map never marks pool virtual servers red
CR28099 SOL486 The 3-DNS Controller still uses BIG-IP systems for probing when all prober factories have been deleted
CR28180 SOL5262 3-DNS may not properly create configuration statements for redundant pairs
CR28228 SOL509 The 3-DNS Controller might display a 331781 memory error, but not fail the operation that caused the error
CR28348 SOL1491 The Configuration utility appears to allow you to disable a datacenter, but does not actually change the configuration
CR28529 SOL509 The 3-DNS Controller might display a 331781 memory error, but not fail the operation that caused the error
CR28459 SOL1664 Modifying a data center from the Configuration utility results in an error
CR28626 SOL554 You cannot manage topology records with a web browser that uses the Sun Java Virtual Machine
CR29967 SOL2853 The Wide IP Port box can list only pre-configured ports
CR30139 SOL5169 3-DNS cannot determine the state of SSL proxies that use remote target servers
CR30212 SOL5032 The Configuration utility does not correctly modify wide IP names
CR30225 SOL5258 Manual configuration changes and synchronization may conflict
CR30242 SOL5185 3dnsmaint cannot copy big3d to BIG-IP 3.x versions
CR30243 SOL5191 Versions of big3d included in 3-DNS 4.5 PTF-04 and later do not work on BIG-IP version 4.5
CR30783 SOL2942 If you use the Configuration utility, the default gateway entry is converted to a default gateway pool
CR31239 SOL1865 You must use the command line to clear LDNS statistics
CR31388 SOL5178 The full_debug script may add duplicate or overlapping statements to syslog.conf
CR31928 SOL766 Debugging commands are not entirely removed from the 3-DNS Controller
CR31946 SOL1902 You must configure a self IP address for a new system before using the 3dnsmaint menu to set up SSH communication
CR32729 SOL743 You cannot configure the ECV scan level of none using the Configuration utility
CR32755 SOL573 In rare cases, a 3-DNS Controller might create a BIG-IP system object with an address of 127.0.0.1
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 it is initially run after configuring the 3-DNS Controller
CR33671 SOL5137 Changes to Check Static Dependencies require a 3ndc restart to take effect
CR33666 SOL3343 The 3-DNS Controller displays a large pending value for a link on the Probers Statistics screen
CR33735 SOL653 The summary statistics provided for BIG-IP systems are inaccurate
CR33815 SOL761 The table that contains Nokia NetAct SNMP traps might grow very large and use excessive disk space
CR33921 SOL3657 Available memory reported by the memAvailReal OID and the vmstat command differs
CR34267 SOL4717 The 3-DNS Controller changes the interface media settings after you run the Setup utility
CR34737 SOL5041 The Configuration utility will not accept host addresses that end in .255
CR34599 SOL2325 The gray virtual server status is not documented
CR35174 SOL3818 The 3-DNS Controller logs an error message in the /var/log/3dns file
CR35320 SOL309 The Telnet and FTP servers are not started when you enable Telnet and FTP
CR37565 SOL814 After logging out, you cannot log in to NameSurfer as the same user
CR37656 SOL659 Adding aliases to wide IPs can lead to NameSurfer zone corruption
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
CR38569 SOL146 The Return to previous page link does not work after entering invalid dates for the change log
CR39381 SOL150 Disabling a link by name in an application object does not work
CR39967 SOL5259 3-DNS may not always create backward-compatible iQuery messages
CR41714 SOL312 Equivalence operators in production rules must be separated on either side with a space
CR41803 SOL2942 If you use the Configuration utility, the 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
CR41808 SOL311 The production rule wizard does not allow changes to QOS settings for existing rules
CR41809 SOL312 Equivalence operators in production rules must be separated on either side with a space
CR41810 SOL320 You cannot access the Configuration utility after running the Setup utility
CR41811 SOL327 QOS values for VS Capacity and Kilobytes/Second might change
CR41812 SOL328 Ports List screen does not display the ports that are 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
CR41816 SOL5032 The Configuration utility does not correctly modify wide IP names
CR41824 SOL371 You cannot change the default gateway pools using the config command
CR41826 SOL399 The config command reports an unnecessary error when a copy of 3dnsd is already running
CR41829 SOL437 An error is logged to the /var/log/3dns file when a router is not configured for a datacenter
CR41830 SOL445 An error might be reported when synchronizing iQuery keys
CR41831 SOL446 The network map never marks pool virtual servers red
CR41833 SOL467 You can partially remove a link by deleting its self IP address and VLAN
CR41834 SOL486 The 3-DNS Controller still uses BIG-IP systems for probing when all prober factories have been deleted
CR41835 SOL5262 3-DNS may not properly create configuration statements for redundant pairs
CR41837 SOL509 The 3-DNS Controller might display a 331781 memory error, but not fail the operation that caused the error
CR41839 SOL554 You cannot manage topology records with a web browser that uses the Sun Java Virtual Machine
CR41843 SOL743 You cannot configure the ECV scan level of none using the Configuration utility
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
CR41849 SOL653 The summary statistics provided for BIG-IP systems are inaccurate
CR41853 SOL659 Adding aliases to wide IPs can lead to NameSurfer zone corruption
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
CR41866 SOL766 Debugging commands are not entirely removed from the 3-DNS Controller
CR41876 SOL2853 The Wide IP Port box can list only pre-configured ports
CR41877 SOL761 The table that contains Nokia NetAct SNMP traps might grow very large and use excessive disk space
CR41884 SOL765 The Generate and Copy iQuery Encryption Key option detects BIG-IP system/3-DNS Controller combination products twice and attempts to copy the iQuery keys to each detected unit
CR41887 SOL767 Changing the address of a wide IP to an invalid address can cause 3dnsconf.cgi file to become unstable
CR41888 SOL780 The Last Hit column on the Requests Statistics screen actually displays persistence expiration
CR41889 SOL783 Saving a new copy of the snmptrap.conf file can create a conflict after an upgrade
CR41891 SOL816 F5 source addresses are not added to the hosts.allow file when the support account is enabled
CR41897 SOL1290 The 3-DNS Controller adds a forward slash (/) to the beginning of the text added to the File Name field
CR41899 SOL1491 The Configuration utility appears to allow you to disable a datacenter, but does not actually change the configuration
CR41902 SOL1664 Modifying a data center from the Configuration utility results in an error
CR41909 SOL1865 You must use the command line to clear LDNS statistics
CR41911 SOL1866 You must configure a self IP address for a new system before using the 3dnsmaint menu to set up SSH communication
CR41912 SOL1902 You must configure a self IP address for a new system before using the 3dnsmaint menu to set up SSH communication
CR41917 SOL3343 The 3-DNS Controller displays a large pending value for a link on the Probers Statistics page
CR41919 SOL3657 Available memory reported by the memAvailReal OID and the vmstat command differs
CR41922 SOL3818 The 3-DNS Controller logs an error message in the /var/log/3dns file
CR41926 SOL5259 3-DNS may not always create backward-compatible iQuery messages
CR42101 SOL5041 The Configuration utility will not accept host addresses that end in .255
CR42147 SOL4717 The 3-DNS Controller changes the interface media settings after running the Setup utility
CR43497 SOL5257 3-DNS will not sync changes to the prober address when you change it back to the default value
CR43498 SOL5257 3-DNS will not sync changes to the prober address when you change it back to the default value
CR44999 SOL5828 Zone changes are not synced when named is reloaded or restarted
CR46509 SOL4497 Switch appliances do not send an SNMP trap when booting because the switch ports are disabled
CR47276 SOL4574 The BIG-IP system and the 3-DNS Controller do not prevent you from installing unsupported versions on older hardware
CR47531 SOL5064 3dnsd may crash when several hundred BIG-IPs are added to the configuration
CR47532 SOL5064 3dnsd may crash when several hundred BIG-IPs are added to the configuration
CR58321 SOL6551 Changes in US and Canada Daylight Saving Time
[ 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)