Before you install and use a 3DNS Controller, you must have the following:
When you unpack the 3DNS Controller, check the packing list to ensure that you received all of the following items:
A 3DNS Controller is an industrial network appliance, designed to be mounted in a standard 19 inch rack. To ensure safe installation and operation of the unit, be sure to consider the following before you install the unit in the rack:
Warning: The 3DNS Controller contains a lithium battery. There is danger of an explosion if you replace the lithium battery incorrectly. We recommend that you replace the battery only with the same type of battery originally installed in the unit, or with an equivalent type recommended by the battery manufacturer. Be sure to discard all used batteries according to the manufacturer's instructions.
The procedures for installation vary depending on whether you are installing a 3DNS Controller for the first time or upgrading an earlier version.
If you are installing the 3DNS Controller for the first time, you must perform the following tasks:
If you are upgrading from an earlier version of the 3DNS Controller, do the following:
If the file is correct, the command displays the correct checksum. Consult the product release notes for the correct checksum value.
tar xvf 3dns106kit.tar
The following table lists the files that are extracted
|3.v1.0.6.tar.gz||3DNS tarball (gzipped)|
|3dnsbook.pdf||3DNS Controller user manual|
|backupfile.txt||List of modified configuration files|
Again, consult the product release notes for the correct checksum values for each file.
/usr/contrib/bin/gtar -cvf 3dbackup.tar -T backupfile.txt
kill `cat /var/run/big3d.pid`
kill `cat /var/run/syslog.pid`
ps -aux|grep thttpd
/usr/contrib/bin/gtar -zxvpUf /var/tmp/3.v1.0.6.tar.gz
Note: Once you install the 3DNS software, you must install new versions of the BIG3d utility on all BIG/ip Controllers managed by the 3DNS Controller. See Setting up the big3d utility, on page 2-21 .
Once you install the software update, you must make the required configuration changes described in the following section.
The following configuration changes are required. All other configuration changes in this release are optional.
To check whether the First-Time Boot utility has run, the 3DNS Controller now looks for the /etc/netstart file rather than /etc/wideip.conf. If the /etc/netstart file exists, the 3DNS Controller does not run the First-Time Boot utility at start up. If the 3DNS Controller does not find the /etc/netstart file, it runs the First-Time Boot utility at start up and saves the /etc/netstart file upon completion.
The 3DNS Controller now automatically manages all datasize statements, including process data and stack sizes, based on the amount of memory installed. We recommend that you remove or comment out datasize statements from /etc/named.conf files because they are no longer necessary.
If you configure the 3DNS Controller to use the registered iQuery port 4353 for iQuery traffic, you must change the corresponding bigip.open_3dns_lockdown_ports sysctl variable on all BIG/ip Controllers running version 2.0 and earlier. The default setting for this variable is 0, but if iQuery traffic is set to run on port 4353, you must change the variable setting to 1.
All versions of the big3d utility must be updated on BIG/ip Controllers. The 3DNS Controller includes big3d utilities for BIG/ip Controller version 1.8.3, version 2.0, and version 2.0.4. Use the Install and Start big3d command on the 3DNS Maintenance menu to automatically copy and install the appropriate version of the big3d utility to all BIG/ip Controllers in your environment.
Move zone files to the /var/namedb directory, which offers substantially more storage space than the /etc/namedb directory.
To make the 3DNS Controller Y2K compliant, you may need to change the serial numbering scheme you apply to zone files. Use the YYYYMMDDXX serial number format where the XX portion of the number reflects a series number that is attached to the date. This serial number format accommodates zone file transfers that occur more than once in a 24 hour period, but does not create serial numbers that exceed a 32-bit integer. For more information on zone file serial numbers, see page 136 in the O'Reilly & Associates' book DNS and BIND, third edition.
If you are upgrading from an earlier version of 3DNS Controller and you plan to use the RTT or QOS load balancing modes, change the following globals sub-statements to the values shown below:
To boot the 3DNS Controller, turn on the power switch located on the front of the 3DNS Controller chassis. The power switch is item 7 on Figure 3.1 :
|1. Fan filter 2. Keyboard lock 3. Reset button 4. Keyboard lock LED 5. Hard disk drive LED||6. Power LED 7. On/off button 8. 3.5 floppy disk drive 9. CD-ROM drive|
Figure 3.2 shows the rear of the 3DNS Controller.
|1. Fan 2. Power in 3. Voltage selector 4. Mouse port* 5. Keyboard port 6. Universal serial bus ports* 7. Terminal serial port||8. Printer port* 9. Fail-over port 10. Video (VGA) port 11. Internal interface (RJ-45) 12. External interface (RJ-45) 13. Interface indicator LEDs 14. Watchdog card*|
*Not to be connected to any peripheral hardware.
When the 3DNS Controller is successfully powered up, you must read and agree to the conditions in the displayed license agreement before the First-Time Boot utility starts and begins prompting you for configuration information.
The configuration is not saved until after you have completely gone through the series of screens. Any changes you need to make to the configuration can be made during the display of the screens to confirm each setting.
After you press any key at the initial screen, the First-Time Boot Utility screen is displayed, as shown in Figure 3.3 .
To continue with the configuration, press any key.
System Configuration Utility
Welcome to 3DNS(tm). Before using your
3DNS(tm), you will have to configure the
root password, 3DNS(tm) hostname, and
This utility will take you through this
Before any configuration files are written to
disk, you will be asked to confirm all your
[Press ctrl-E to exit and configure manually]
[ press any key to continue ]
At the Set Root Password screen, enter the password that you want to assign to the root user account. The password should be a minimum of six characters, a maximum of 128, and should contain a combination of uppercase, lowercase, and punctuation characters.
Next you are prompted to reset the root password. Press any key to continue.
You are prompted to confirm your new password by typing it again at the second Set Root Password screen. Press any key to continue.
Enter a fully qualified domain name for the 3DNS Controller (for example, 3dns.seattle.domain.com), and press Enter.
In the next series of screens, you set and configure the interface and netmask. To select the interface as either exp0, de0, or fddi0, move the cursor to highlight your selection, and press Enter.
Enter the IP address for the interface used in configuration.
In this screen you can either accept the default netmask (255.255.255.255), or you can define a custom netmask for the interface.
In this screen you can either accept the default broadcast address (the combination of the IP address and the netmask), or you can define a custom broadcast address for the interface.
Move the cursor to highlight the media type to be used for the interface, then press Enter. The options for the Interface Media Type are dependent on the NIC being used. An example of media type is as follows:
Enter the IP address from which you want to perform all remote configuration, administration, and monitoring tasks. Note that you can use an asterisk (*) as a wildcard to specify a range of IP addresses.
For 3DNS Controllers distributed in the US, administrative command line tasks are conducted using the F-Secure SSH client, which is a secure shell. For international 3DNS Controllers, administrative command line tasks are conducted via Telnet.
The default route is used to determine where the 3DNS Controller should send network traffic for which it does not have a static route. The default route is usually the IP address of a router.
After you confirm all of your configuration entries, the Finished screen opens, as shown in Figure 3.4 .
---F I N I S H E D--------------------------
BIND 8 and 3DNS(tm) are set up. You are
ready to configure 3DNS.
Once your 3DNS has re-booted,
login and run
[ press any key to continue ]
At this point, the 3DNS Controller writes your configuration to the disk. A status window shows the progress as each of the listed configuration files are saved.
Once the First-Time Boot utility is done, press any key to start the 3DNS Controller. At the login prompt, log in as root and halt the system using the halt command.
After the system halts, set the power switch to the Off position. You must completely power down the 3DNS Controller before attaching it to a network, as described in the next section.
This section applies only to products sold in the U.S.
If you want to configure the 3DNS Controller from a remote workstation, you need to install the F-Secure SSH client on your remote administration workstation. Note that you can also use the F-Secure SSH suite for file transfer to and from the 3DNS Controller, as well as for remote backups. A F-Secure SSH client is pre-installed on the 3DNS Controller hardware to assist with file transfer activities. Please refer to the F-Secure SSH User's Guide shipped with your 3DNS Controller for more information about the SSH client itself.
The F-Secure server is started upon 3DNS Controller boot up. The 3DNS First-Time Boot Utility configures the F-Secure SSH server based on information you provide, so no further modification of the F-Secure configuration is required.
You are licensed to install one (1) copy of the client on your administration workstation. To ease the ordering and installation process, both UNIX and Windows versions of F-Secure SSH client are shipped with the 3DNS Controller. Please contact Data Fellows if you need to purchase additional F-Secure SSH clients, or if you need to purchase the Mac version of the SSH client.
To transfer the F-Secure SSH client to the administration workstation:
The following text is displayed:
Connected to big.f5.com. 220 big.f5.com FTP server (OSF/1 Version 5.60) ready. Name (big:the user): 331 Password required for the user. Password:
The F-Secure SSH client is now installed on your administration workstation. You are now ready to remotely log on to the 3DNS Controller to finish configuration.
If you have any problems building the F-Secure SSH client for the UNIX operating system on your administration workstation, please contact Technical Support at F5 Networks, Inc.
ssh -l root [3DNS Controller IP address]
After the 3DNS Controller is installed, you must perform several configuration tasks to implement the system. These tasks are described in Chapter 4, Configuring a 3DNS Controller .