If you are setting up a crypto 3-DNS Controller that needs to communicate with non-crypto 3-DNS Controllers, you must enable the rsh and rcp tools on the crypto 3-DNS Controller. These are the standard communication and copying tools that non-crypto 3-DNS Controllers, BIG-IP Controllers, and EDGE-FX Caches use.
Run the rsetup script from the command line utility. The rsetup script performs several essential steps to enable access for rsh and rcp, and we strongly recommend that you use the script rather than doing this manually.
The type of system you have determines the options you have for remote command line administration:
If you are working with a crypto 3-DNS Controller, you can access a Mindbright Mindterm console through the web-based Configuration utility.
You must address several networking issues when you place a 3-DNS Controller in your network. These networking issues include routing, DNS configuration, and special email considerations. The type of hardware and software in your network determine how you address these issues. This section describes the following networking issues:
To configure a serial terminal, in addition to the standard console, for the 3-DNS Controller, you need to complete the following configuration steps. Note that if you are using a serial VT100 connection, you must edit both the /etc/ttys and bash_profile files on the 3-DNS Controller.
Note: Before you configure the serial terminal, you must disconnect the keyboard from the 3-DNS Controller. When there is no keyboard connected to the 3-DNS Controller, the 3-DNS Controller defaults to using the serial port for the console.
Before the 3-DNS Controller is booted, you must attach a serial device to the serial port in order for the controller to use the serial port as the console.
You can configure the 3-DNS Controller to send email notifications to you, or to other administrators, using the Sendmail utility. The 3-DNS Controller includes a sample Sendmail configuration file that you can use to start with, but you must customize the Sendmail setup for your network environment before you can use it.
Before you begin setting up Sendmail, you may need to look up the name of the mail exchanger for your domain. If you already know the name of the mail exchanger, refer to Setting up Sendmail, on page 4-4 for details about setting up the sendmail daemon itself.
You can use the nslookup command on any workstation that is configured for lookup. Once you find the primary IP address for your domain, you can find the mail exchanger for your domain.
Default Server: <server name>
The returned information includes the name of the mail exchanger. For example, the sample information shown in Figure 4.1 lists bigip.net as the preferred mail exchanger.
bigip.net preference = 10, mail exchanger = mail.domain.com
bigip.net nameserver = ns1.bigip.net
bigip.net nameserver = ns2.bigip.net
bigip.net internet address = 184.108.40.206
ns1.bigip.net internet address = 220.127.116.11
ns2.bigip.net internet address = 18.104.22.168
When you set up Sendmail, you must edit two configuration files. Since the 3-DNS Controller does not accept email messages, you can use the crontab utility to purge unsent or returned messages and send them to yourself or another administrator.
0,15,30,45 * * * * root /usr/sbin/sendmail -q > /dev/null 2>&1
/usr/sbin/sendmail -bd -q30m