cc/td/doc/product/iaabu/cddm/css_1196
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Testing the CDDM Servers

Testing the CDDM Servers

This chapter presents an exercise that demonstrates how to make sure the CDDM software is installed and working. The exercise consists of the following steps:

Step 1 Making sure that the initial configuration has been done (see "Check the Initial Configuration")

Step 2 Making sure that CDDM ports are not being used by services provided by your operating system (see "Check the CDDM Default Ports")

Step 3 Restarting and testing NetControl (see "Restart and Test NetControl")

Step 4 Starting the Service Configuration Manager (see "Start the Service Configuration Manager (SCM)")

Step 5 Configuring the DNS server for caching-only operation (see "Configure the DNS Server as a Caching-only Name Server")

Step 6 Configuring the DNM (Domain Name Manager) server to perform zone transfers of port 705 (for the local DNS server) and to allow users to log into an administrator's account (see "Configure the DNM Server")

Check the Initial Configuration

To make sure the CDDM is completely installed:

Step 1 Log in as root.

Step 2 Check the directory install_dir/MultiNet/config/ (where install_dir is the directory in which you installed the CDDM software) for the service.cnf file.

Step 3 If the service.cnf file is not present, run install_dir/MultiNet/bin/ddm_xconfig (or ddm_config) to perform an initial CDDM configuration.


Note See the Cisco Server Suite Installation and Basic Configuration Guide for details about initial configuration.

Check the CDDM Default Ports

For the purposes of this guide, you must disable native services that are using the ports required by CDDM services. The following procedures show the commands to enter to check for other services running on the ports. The Cisco Server Suite Installation and Basic Configuration Guide contains information about how to stop any services using the ports.

Step 1 Make sure that NetControl is not running:

ps -ef | grep netc


If NetControl is installed correctly, a line similar to the following appears:


root 349 1 0 16:51:28 pts/3 0:00 ./netcntrl.exe

install_dir/MultiNet/bin/stop_netcontrol


Step 2 Verify that no other service is using the NetControl port, 599:

netstat -an | grep 599


Step 3 Verify that no other service is using the DomainName port, 53:

netstat -an | grep 53


Step 4 Verify that no other service is using the DNM ports, 704 and 705:

netstat -an | grep 704


netstat -an | grep 705


Step 5 On HP-UX or AIX, verify that no other service is using the Syslog port, 514:

netstat -an | grep 514


Step 6 On Solaris, make sure the native Syslog service is not running:

ps -ef | grep syslogd


Step 7 Verify that no other service is using the DHCP/BootP port, 67:

netstat -an | grep 67


Restart and Test NetControl

To stop and restart the NetControl master server and make sure it is running:

Step 1 Stop NetControl by entering the following commands:

cd install_dir/MultiNet/bin


./stop_netcontrol


Step 2 Restart NetControl:

./netcontrol


Step 3 Verify that NetControl is running:

ps -ef | grep netc


If NetControl is installed correctly, a line similar to the following appears:


root 349 1 0 16:51:28 pts/3 0:00 ./netcntrl.exe

Start the Service Configuration Manager (SCM)

To start the SCM, which is used to configure other services, enter the following command:

install_dir/MultiNet/bin/scm

Configure the DNS Server as a Caching-only Name Server

To configure the DNS server (listed in the SCM as DomainName) to operate as a caching-only name server:

Step 1 Choose DomainName from the list of Available Services in the SCM.

Step 2 Select the Startup tab.

Step 3 Select the Basic tab.

Step 4 Verify that the Start field is set to AUTOMATIC. If not:

Step 5 Open a UNIX shell and test the configuration by attempting to resolve a name with the following command:

nslookup www.cisco.com 127.0.0.1


Configure the DNM Server

The DNM server acts a primary to the zone yoyodyne.com and will manage the zone files. The DNS server (DomainName Service) acts as a secondary to the DNM and resolves DNS queries. Because the DNM server and DNS server exist on the same node, the DNM server must transfers zones to the DNS server on port 705 to avoid conflict with DNS name resolution performed on the default DNS port, 53. Refer to the Cisco DNS/DHCP Manager Concepts and Planning Guide for detailed information.

To configure the DNM server:

Enabling the DNM Service

To enable the DNM service:

Step 1 Choose DNM from the SCM's Available Services list.

Step 2 Select the Startup tab.

Step 3 Select the Basic tab.

Step 4 Verify that the Start field is set to AUTOMATIC. If not, change it to AUTOMATIC.

Adding the "admin" User Account

To set up a DNM user account:

Step 1 Choose the Users tab.

Step 2 Type admin in the User Name field.

Step 3 Type admin in the Password field.

The password characters are not echoed.



Note Although this guide uses the password "admin" in all exercises, to avoid potential security problems, Cisco recommends using a password other than admin.

Step 4 Click on Add. "admin" now appears in the list of users.

Setting the DNM name service port to 705

Step 1 Select the Startup tab.

Step 2 Select the Parameters tab.

Step 3 Click on the Nameserver-port box to enable it, and set its value to 705.

Saving the Configuration and Restarting NetControl

To complete this procedure:

Step 1 Choose Save Configuration from the File menu to save your configuration, and click on OK in the confirmation dialog box.

Step 2 Stop and restart NetControl:

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.