cc/td/doc/product/rtrmgmt/ciscoasu/nr/nr_2_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Installing Network Registrar

Installing Network Registrar

Network Registrar supports enterprise IP address management. It automates IP address management, creating a stable infrastructure that increases the reliability and efficiency of the address assignment process, and substantially reduces the administrative burden associated with address management.

Network Registrar Features

Network Registrar includes support for Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) servers, and provides many features that makes administering these servers easy.

DNS Registrar Features

DNS Registrar includes the following features:

DHCP Registrar Features

DHCP Registrar includes the following features:

Registrar Administration Features

Registrar Administration includes the following features:

Before You Begin

Before you install Network Registrar Software Release 2.0, make sure your site meets the following system and client requirements.

System Requirements

Table 1-1 shows the requirements for the Network Registrar server.


Table 1-1: Server Requirements
Component Sun SPARC Intel

CPU Architecture

SPARCstation 20 or better

Intel 80486, Intel Pentium or Pentium Pro; 100 MHz or faster Pentium or Pentium Pro recommended

OS Version

Solaris 2.5.1 or 2.6

Windows NT 3.51 workstation or server, service pack 3 or 5 (not SP 4); Windows NT 4.0 workstation or server

Minimum RAM

64 MB

32 MB

Recommended RAM

96 MB

64 MB

Recommended Disk1

80 MB + 1 MB for each 100 clients managed by DNS or DHCP

50 MB + 1 MB for each 100 clients managed by DNS or DHCP

Swap Space

100 MB free swap space

100 MB free swap space

1. A system managed by DHCP with dynamic DNS update counts as one client for this calculation

Client Requirements

The Network Registrar GUI runs on Sun Solaris, Windows 95, or Windows NT 3.51 or 4.0 (server or workstation) for Intel. If you are running the GUI on the same machine as the servers, follow the requirements listed in Table 1-1. Follow the requirements listed in Table 1-2 if you are running the GUI on a remote system.


Table 1-2: Client Requirements
Component Sun SPARC Intel

CPU Architecture

Solaris 2.5.1 or 2.6

Intel 80486, Intel Pentium or Pentium Pro

OS Version

Solaris 2.5.1 and CDE 1.02 (Desktop 1.1)

Windows 95, Windows NT 3.51 workstation or server, service pack 3 or 5 (not SP 4).Windows NT 4.0 workstation or server

Minimum RAM

64 MB

24 MB (Windows 95), 32 MB (Windows NT)

Recommended RAM

32 MB, 48 MB for larger configurations (over 10,000 hosts)

Recommended Disk

50 MB

20 MB

Installing Network Registrar

You can install Network Registrar on a Solaris server or on a Windows NT server or workstation.


Note You can run both the servers and GUI on either a Windows NT server or on Solaris server. Or, you can run the servers on one platform and the GUI on another. For example, you can run the servers on a Solaris server and the GUI on a Windows NT server or vice versa. The only requirement is that both the servers and the GUI must be the same software release number.

Upgrading from Previous Releases

When you install Network Registrar Software Release 2.0, it automatically detects an existing Network Registrar 1.x installation, and asks if you would like to upgrade your database. The Network Registrar installation prevents you from installing Software Release 2.0 into the same location as your previous software release. You should not override this restriction.


Note The upgrade program does not copy the Network Registrar cluster list or DNS cache from the old installation. This prevents Network Registrar Software Release 2.0 from automatically trying to connect to 1.x servers. The Network Registrar Software Release 2.0 server starts with an empty cache.

Whether you choose to upgrade your database or not, your Network Registrar Software Release 1.x installation remains in its original location. You can choose to manually uninstall this software release when you are satisfied that Network Registrar Software Release 2.0 is running successfully. For more information about uninstalling, see the "Uninstalling on Solaris" section or the "Uninstalling on Windows NT" section in "Database Upgrade" appendix.

Installing Network Registrar on Solaris

Step 1 Insert the Cisco Network Registrar compact disk in your CD-ROM drive or mount the CD-ROM from your remote server.

Step 2 Become the root user by typing su, and then typing the root password.

Step 3 Enter the pkgadd command with the -d option that specifies the CD-ROM directory:

#pkgadd -d <CD-ROM>
 

Step 4 The installation prompts you for the package you want to install.

Select All or the default.

Step 5 Choose either server and GUI or server or GUI.

Step 6 Choose the location of the following directories or accept the following defaults. (If you have installed an earlier version of Network Registrar Software Release 2.0 the installer will use those paths.)

If the directories do not exist, the installation asks if you want them created. Choose to have the installation create them for you.

Step 7 If you are upgrading Network Registrar from a previous software release, select Yes to the question whether to upgrade the existing database.

Step 8 When the installation informs you that it will install scripts that will run as the superuser, select Yes.

If you select No, the installation does not complete and aborts.

Step 9 The installation copies all the files, and starts the AIC Server Agent, which in turn starts the Network Registrar servers. If you are performing an upgrade, you are prompted for your Network Registrar username and password.

Step 10 The installation displays a message informing you that the installation was successful.

Step 11 The installation returns to the opening prompt. Click q to quit the pkgadd program.

For a list of Network Registrar files, see the "Network Registrar Information" appendix.

To check the status of the Network Registrar servers, enter the /opt/nwreg2/usrbin/ aicstatus command. For information about this command, see the "Starting the AIC Server Agent on Solaris" section later in this chapter.

Installing Network Registrar on Windows


Note Be sure to close all open applications before installing Network Registrar Software Release 2.0 on a Windows 95 system. The installation program may not work properly if other applications are running.

Step 1 Insert the CISCO Network Registrar 2.0 compact disk in your CD-ROM drive.

Step 2 Do one of the following:

Step 3 Follow the instructions that appear on your screen.

Step 4 Reboot your system after the installation finishes.

Starting Network Registrar's Servers

In order to run Network Registrar you need to start Network Registrar's services. You can do this either by:

Manually Starting the AIC Server Agent

The AIC Server Agent is responsible for controlling the Network Registrar servers on a given host. This includes loading and unloading each server's executable programs into memory, and initiating service by starting each server. The AIC Server Agent is the first Network Registrar program to run each time the host boots, and is the last Network Registrar program to exit when you shut down the service.

Starting the AIC Server Agent on Solaris

Starting the AIC Server Agent starts the DNS and DHCP servers.

Step 1 Become the superuser.

Step 2 Change to the /etc/init.d directory.

Step 3 Enter the aicservagt command with the start argument:

./aicservagt start
 Starting AIC Server Agent for Network Registrar
 

Step 4 Check that the servers are running, by typing the aicstatus command:

/opt/nwreg2/usrbin/aicstatus
DNS server running	(pid: 649)
MCD server running	(pid: 648)
DHCP server running	(pid: 650)
Server Agent running	(pid: 647)
MCD Lock Manager running		(pid: 651)

Starting the AIC Server Agent on Windows NT

Starting the AIC Server Agent starts the DNS and DHCP servers.

Step 1 From the Program Manager:

Step 2 From the Control Panel, double-click Services.

Step 3 From the Service list, select AIC Server Agent 2.0.

Step 4 Click Start.

Step 5 Click Close.

Starting Network Registrar

To start Network Registrar you need to start the program and log in to a cluster. A cluster is a DNS or DHCP server that share the same Network Registrar database. Adding a cluster tells Network Registrar about the existence of a cluster. To configure or administer the cluster you must also connect to it.


Note Typically, Network Registrar's DNS and DHCP servers are running on the same physical machine. In this case, the term cluster refers to the physical machine.

You can start the Network Registrar GUI at anytime---the servers do not need to be running. You cannot save any changes however, unless the servers are running.

Starting Network Registrar on Solaris

When running the Solaris GUI, you should choose the Common Desktop Environment (CDE) if available, in preference to the OpenWindows Desktop. The appearance of the Solaris GUI is superior under CDE.

Step 1 Type the following at the command line:

/opt/nwreg2/usrbin/ntwkreg
 

Network Registrar displays the Server Manager.

Step 2 Click Add to add a new cluster.

Step 3 In the Login to Cluster dialog box, enter the username admin and the password changeme.


Note You should change the username and the password from the defaults to appropriate ones for your site.

Step 4 Enter your license key.

For more information about licensing, see the "Entering Network Registrar License Key" section later in this chapter.

Starting Network Registrar on Windows NT

Step 1 Do one of the following:

Step 2 In the login to cluster dialog box, enter the username admin and the password changeme.


Note You should change the username and the password from the defaults to appropriate ones for your site.

Step 3 Enter your license key.

For more information about licensing, see the "Entering Network Registrar License Key" section later in this chapter.

Running Network Registrar From a Remote Site

If you are running Network Registrar's GUI remotely rather than from your server, you must first add a cluster. Adding a cluster connects the remote machine on which you are running the GUI with the server that provides DNS or DHCP services. After you add the cluster, you can configure and monitor the servers.


Note You need to enter your Network Registrar license key the first time you configure each cluster. For more information about the license key, see the
"Entering Network Registrar License Key" section later in this chapter.

Adding a Cluster

Step 1 Select Admin>Clusters.

Step 2 In the Cluster dialog box, click the Add Cluster button.

Step 3 In the Add Cluster dialog box, enter the cluster name.

The cluster name must be the name of the host on which the database runs. This is usually the name of the DNS server.

Step 4 If you want to connect the cluster at this time, select the Connect to this cluster check box.

Step 5 Click OK.

Step 6 In the Login for Cluster dialog box for that cluster, enter the username and password.

Step 7 Click OK.

Entering Network Registrar License Key

Network Registrar licensing controls your ability to configure your servers. Every copy of Network Registrar requires a license. Your license key is located on the back of your software CD case. You need to enter your license the first time you configure each cluster.

Specifying Your License Key

Step 1 Select Admin>Clusters.

Step 2 In the Cluster dialog box, click the Add Cluster button.

Step 3 In the Add Cluster dialog box, enter the cluster name.

The cluster name must be the name of the host on which the database runs. This is usually the name of the DNS server.

Step 4 If you want to connect the cluster at this time, select the Connect to this cluster check box.

Step 5 Click OK.

Step 6 In the Login for Cluster dialog box for that cluster, enter the username and password.

Step 7 Click OK.

Step 8 From the License dialog box, click New Key.

Step 9 From the Cluster Properties dialog box, select Edit License Key.

Step 10 Enter the 16-digit license.

Step 11 Click OK.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Jul 13 11:09:54 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.