Updated Date: 06/24/1999
Apply the PTF to 3DNS System version 1.0.4, or 3DNS System 1.0.4PTF-01 using the following process:
kill `cat /var/run/big3d.pid`
kill `cat /var/run/syslog.pid`
ps -aux thttpd
gtar xvzpUf /var/tmp/<file name>
Note: It is very important that you start big3d on all BIG/ip controllers, and then restart named on all 3DNS Systems.
The current PTF-02 includes the following fix, and also includes fixes originally released in version 1.0.4PTF-01 as described below.
This PTF resolves the following issue:
Fix 2401: The Round Robin,
Global Availability, and Random pool load balancing modes ignore the first pool in the
These three pool load balancing modes now use the first pool in the list as expected. Note that this fix does not affect the big3d utility, nor does it require you to make any changes to your current configuration.
In the following sample wideip.conf file, the 3DNS System would first use the Los Angeles pool. If all virtual servers in the Los Angeles pool went down, the 3DNS System would then use the Tokyo pool. If all virtual servers in the Tokyo pool went down, the 3DNS System would then use the wideip key address 192.168.102.70. The New York pool would never be used. Once you apply the current PTF, however, the 3DNS System would use the New York pool first (as it should), and then move on the Los Angeles pool if all virtual servers in the New York pool went down.
name "New York"
address 192.168.101.50 ratio 2
address 192.168.101.60 ratio 1
address 192.168.101.70 ratio 1
name "Los Angeles"
address 192.168.102.50 ratio 3
address 192.168.102.60 ratio 2
address 192.168.102.70 ratio 1
address 192.168.103.50 ratio 3
address 192.168.103.60 ratio 2
address 192.168.103.70 ratio 1
The corresponding excerpt from /var/namedb/db.domain.com would read:domain.com. IN MX 10 mx.domain.com
The PTF does not introduce new software configuration issues.
There are no known issues at this time.