Cisco CNS Network Registrar Installation Guide, 5.5
Installing Network Registrar on Sun Solaris
Downloads: This chapterpdf (PDF - 200.0KB) | Feedback

Installing Network Registrar on Sun Solaris

Table Of Contents

Installing Network Registrar on Sun Solaris

Installation Checklist

System Requirements

Server or Complete Installation

GUI-Only Installation

New Installation

License Key

Upgrading From an Earlier Version

Uninstalling Network Registrar

Re-installing Network Registrar

Reverting to an Earlier Version

Starting and Stopping the Servers

What to Do Next


Installing Network Registrar on Sun Solaris


Network Registrar runs on Solaris 2.6, Solaris 7 and Solaris 8. This chapter covers the following installation topics:

Installation Checklist

System Requirements

New Installation

License Key

Upgrading From an Earlier Version

Uninstalling Network Registrar

Re-installing Network Registrar

Reverting to an Earlier Version

Starting and Stopping the Servers

What to Do Next

Installation Checklist

Before running the installation program, answer the following questions:

Does the target machine meet the system requirements?—See the "System Requirements" section.

Do you have the appropriate username and password for the target machine?—This is typically an administrative account. You must have root or superuser privileges to install Network Registrar.

What type of installation you want?

Complete—Installs the servers and user interfaces—the recommended option

Server only—Installs only the servers

GUI only—Installs only the user interfaces

In what directories do you want to install Network Registrar read-only, data, log, and temporary files?—There are default locations for these files.

Do you want to retain the ability to revert to a previous version of Network Registrar?—If so, you need to copy your database to another location. See the "Reverting to an Earlier Version" section.

Is this a new installation or an upgrade from Network Registrar 5.0 or 3.5?

If a new installation, see the "New Installation" section.

If an upgrade, see the "Upgrading From an Earlier Version" section.

If you need to upgrade from a version earlier than 3.5, contact the Cisco Technical Assistance Center as listed in the Preface in this guide.

System Requirements

On Solaris, you can monitor disk space using one of many third party packages and an automated script. A simple test is to run the df -k tool and check the available space on the /var volume that contains the database and log files. See the "New Installation" section.

Server or Complete Installation

To run Network Registrar 5.5 on Solaris requires:

Sun SPARCStation 20 or better

96 MB of RAM

Solaris 2.6, Solaris 7, or Solaris 8

80 MB plus 1 MB of disk space for each 100 clients managed by DNS or DHCP. A system managed by DHCP with dynamic DNS update counts as one client for this calculation.

Fastest disk (for example, Ultra-SCSI) and mirrored or RAID disks with 100 MB free swap space

GUI-Only Installation

To run the Network Registrar GUI on a Solaris machine requires:

Sun SPARCStation 20 or better

64 MB of RAM

Solaris 2.6, Solaris 7, or Solaris 8

50 MB of disk space

New Installation

The procedure for a new installation assumes that no previous version of Network Registrar is installed. If the installation program detects a Network Registrar file, it prompts you to overwrite it or abort the installation. To install Network Registrar 5.5 over a previous version, see the "Upgrading From an Earlier Version" section.

For a new installation of the Network Registrar servers or user interfaces on Solaris, do the following:


Step 1 If you are installing from a CD-ROM, insert it into the CD-ROM drive or mount it from a remote server.

If you are installing from a network resource, locate the resource containing the image of the Network Registrar CD-ROM files.

If you downloaded the distribution file from a Cisco web site, uncompress and unpack it as follows:

a. You must have the GNU gzip and gtar utilities installed and in your search path. See the GNU organization web site for additional information (www.gnu.org).

b. Use the cd command to change into the directory in which you wish to unpack the Network Registrar distribution file.

c. Run the gunzip and tar utilities to extract the files.

gtar -zxpf distribution_file_name 

Step 2 Become the root user by entering su and the root password.


Caution Do not set a permission that is too restrictive, such as 700 (drwx------), for the parent directory of the installation directory, or Network Registrar will not install. Use a permission of 755 (drwxr-xr-x) instead. Always include only the absolute path to the program; it will not work specified as a symbolic link.

Step 3 Enter the pkgadd command with the -d option that specifies the directory from which you are installing.

pkgadd -d cdrom-dir/solaris/see_readme_before_using 

The cdrom-dir variable is the directory on which the CD-ROM is mounted or in which you unpack the distribution file, or the network resource from which you are installing. For the exact directory location, see the README.solaris file in the top-level directory.

Step 4 The installation program prompts you for the package you want to install from that directory. Enter all or accept the default. This starts the Network Registrar installation program. If the program detects that your operating system is earlier than Solaris 2.6, it terminates.

Step 5 Enter Complete, Server only, or GUI only.

Complete—Installs the Network Registrar servers and user interfaces—the recommended option

Server only—Installs the Network Registrar servers only

GUI only—Installs the user interfaces only

Step 6 Choose the location of the following files or accept the defaults:

Read-only files (shared libraries, user executables, and configuration files)—The default directory is /opt/nwreg2. Its size is basically static and requires minimal monitoring.

Data files—The default directory is /var/nwreg2/data. Its size can grow significantly, especially with backup files.

Log files—The default directory is /var/nwreg2/logs. You can set the maximum size and number of these log files. See the Network Registrar User's Guide, the Administering Network Registrar chapter.

Temporary files—Include lock management files that are recreated during a reboot in the /.A subdirectory. Be sure to exclude these files from any cleanup process. The default directory is /var/nwreg2/temp.

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

Step 7 The installation program informs you that it will install scripts that run as the superuser. Enter y. If you enter n, the installation program terminates.

Step 8 If the installation program detects a previous version of Network Registrar, it prompts you to either overwrite it by entering y, or abort the installation by entering n. Enter y, unless you want to stop the installation and investigate the earlier files.

Step 9 The installation program copies all the files and starts the AIC Server Agent, which in turn starts the Network Registrar servers.

Step 10 The program displays a message that the installation was successful, then returns to the opening prompt. Click q to quit the pkgadd program.


To check the status of the Network Registrar servers, use the /opt/nwreg2/usrbin/aicstatus command. See the "Starting and Stopping the Servers" section.

License Key

To administer the cluster of Network Registrar servers that you just installed, you must enter the license key, which enables the user interfaces. The license key is located on the CD-ROM case.

You can run the user interfaces and the servers on different machines. You must tell the user interface which cluster you want to access and whether the cluster is on the local host or on a remote machine. (A cluster is a group of Network Registrar servers that share a database.)

If you have a permanent license, you must enter it once for each cluster that you want to access through the user interface. You are not prompted to enter a license key for that cluster again unless you move the cluster to another machine.

If you have an evaluation copy of Network Registrar, you have a license that expires.

If you have an invalid, missing, or expired license key, you cannot configure or manage the Network Registrar servers until you obtain a valid license key. The servers continue to function normally.

Enter the license key as follows:


Step 1 Start the Network Registrar CLI or GUI from the Solaris command line prompt.

To start the CLI, enter:

# /opt/nwreg2/usrbin/nrcmd -C clustername -U admin -P changeme 

Include the name of the Network Registrar server cluster, and username admin and password changeme. (You should change this password later on.)

To start the GUI, enter:

# /opt/nwreg2/usrbin/ntwkreg 

Step 2 If you are using the CLI, enter the following command at the nrcmd> prompt:

nrcmd> license set key=keystring 

The keystring is the 16-digit license identifier found on the back of your installation CD-ROM case.

If you are using the GUI, when the Server Manager window appears, do the following:

a. From the Admin pull-down menu and select Clusters.

b. In the Cluster dialog box, click Add Cluster.

c. In the Add Cluster dialog box, enter the cluster name. This name is the host (DNS) name of the machine on which the Network Registrar servers are installed.

d. Select the Connect to this cluster check box, then click OK.

e. In the Login for Cluster dialog box, enter the username admin and password changeme, then click OK. (You should change this password later on.)

f. From the License dialog box, click New Key.

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

h. Enter the 16-digit license identifier found on the back of your installation CD-ROM case, then click OK.

Step 3 Exit Network Registrar by entering the exit command from the CLI, or selecting Exit from the Admin menu in the GUI.


Upgrading From an Earlier Version

If Network Registrar 5.0 or 3.5 is already installed, you can upgrade your existing databases to 5.5, or delete them and use the newer 5.5 databases.

To upgrade from 5.0 or 3.5, you must run the upgrade_cnr program, which is in the solaris subdirectory of the CD-ROM, and not the pkgadd command. If you use the standard configuration of the Solaris automounter, this program is in the /cdrom/cnr_5_5/solaris directory.


Caution Do not run the pkgrm command. It will delete your data.

To upgrade from an earlier version of Network Registrar, do the following:


Step 1 Prepare yourself for the upgrade program:

a. Back up the Network Registrar 5.0 or 3.5 databases. You cannot downgrade to them again.

b. If you are installing from a CD-ROM, insert it into the drive or mount it from your remote server. If you are installing from a network resource, locate the resource containing the image of the Network Registrar CD-ROM files.

If you download the distribution file from a Cisco web site, you must have the GNU gzip and gtar utilities installed and in your search path (see the GNU organization web site at www.gnu.org) for assistance). Change to the directory where you want to unpack the Network Registrar distribution file. Then, run the gunzip and tar utilities to extract the files, and include the distribution filename.

gtar -zxpf distribution-filename 

c. Become the root user by entering su and the root password. Ensure that the current directory is the directory in which the CD-ROM is mounted.

Step 2 Run the upgrade_cnr program.

# /cdrom-path/solaris/upgrade_cnr 

Include the absolute path to run the program, or it will not work. If you mount the CD-ROM manually, or have a nonstandard automounter configuration, replace cdrom-path with the directory on which the CD-ROM is mounted (for example, /cdrom/cnr_5_5). If you are installing from a network resource or a directory in which you unpacked the distribution file, replace cdrom-path with that directory.

Step 3 When prompted, enter y to continue with the upgrade.

Step 4 The program tries to validate your administrative username and password from the values of the AIC_NAME and AIC_PASSWORD environment variables. If these do not exist, enter the administrative username and password when prompted. This verifies your authentication.

Step 5 When prompted, enter y to stop the Network Registrar servers. Your host stops providing DNS and DHCP services throughout the rest of the upgrade process.

Step 6 The upgrade must save a backup copy of the databases as a precaution if the upgrade is interrupted. Decide on a backup directory path and enter it at the prompt, or press Enter to accept the default (/usr/tmp). Network Registrar creates a cnr_db.bak subdirectory at this location and places the backup files in that subdirectory.


Note Ensure that the specified directory has at least one megabyte of free space, or the backup may fail. Also, ensure that the directory is on a real filesystem, and not a memory-based one (such as /tmp frequently is), so as to preserve the database through a reboot.


If the program senses that a previous backup already exists, it prompts whether you want to overwrite the existing backup. Enter y to overwrite the existing backup, or n to receive a prompt at which to enter a different location for the new backup.

Step 7 You can either preserve your data as part of the upgrade or erase it and start over with a fresh one. To preserve the old data, enter y; to overwrite it, enter n.

Step 8 The program warns you that this is the last chance to abort the upgrade. Enter y to continue with the upgrade. This should successfully remove the /nwreg2 directory and its contents.

An important notice appears, indicating that the upgrade does not remove files that were added after Network Registrar was initially installed. It also notifies you that it copies the aic.conf file as /export/home/aic/conf/aic.conf.SAVE, and preserves the data files in the /export/home/aic/temp, /export/home/aic/logs, and /export/home/aic/data directories. To completely remove Network Registrar, you must also remove these files and directories.

The program then installs Network Registrar 5.5 and re-installs the /nwreg2 directory and its contents.

Step 9 You should next get a message that the software was successfully upgraded, and that your database and extension scripts were preserved. The program then asks if you want to preserve a backup of the database. As a precaution, enter y to preserve the database backup. The program preserves the backup files in the location you specified in Step 6.

Step 10 Check whether your servers are now operating properly.



Note Upgrading to Network Registrar 5.5 from 5.0 or 3.5 automatically converts the DHCP failover and lease objects in the state database, but only those within a certain upgrade time frame (opportunity). The upgraded failover server gets from its partner all lease binding changes that occurred since the two servers last communicated. The upgrade time frame (without any server down time) depends on the number of leases issued or renewed each minute and the configured lease time. For example, if a configuration database upgrade takes 30 minutes and if there are 1000 leases with an expiration of six hours issued or renewed every hour, Network Registrar generates a maximum of 500 lease binding updates as part of the failover upgrade.


Uninstalling Network Registrar

The Solaris package removal program (pkgrm) uninstalls Network Registrar 5.5. You can save the 5.5 databases by using the mcdshadow backup program. See the Network Registrar User's Guide for details on backing up your database. Note that you cannot convert the 5.5 databases back to the 5.0 or 3.5 databases.

To uninstall Network Registrar, use the pkgrm program to remove the nwreg2 files, from a root account.

# pkgrm nwreg2 

The uninstall procedure removes the server and user interface components, but does not delete user data, such as the log and data files. To delete the data associated with Network Registrar, follow the instructions in the uninstall dialog about which directories to remove.

Re-installing Network Registrar

Infrequently, you may need to re-install the product because of a failure that could cause corrupted database files or if a file is accidentally deleted. On Solaris, this is the same as an upgrade. See the "Upgrading From an Earlier Version" section for details

Reverting to an Earlier Version

To revert to Network Registrar 5.0 or 3.5 from 5.5, do the following:


Step 1 Uninstall Network Registrar 5.5, as described in the "Uninstalling Network Registrar" section.

The uninstall program does not remove the Network Registrar log and data files. However, it displays a list of the directories and files not being removed. Delete these files manually before installing the earlier version of Network Registrar.

Step 2 Re-install Network Registrar 5.0 or 3.5 as directed in the Network Registrar Installation Guide for that version.

Step 3 Stop the Network Registrar servers. Otherwise, you may get errors. See the "Starting and Stopping the Servers" section.

Step 4 If you are reverting to Network Registrar 3.5, copy the mcddb.d01, mcddb.d02, and mcddb.d03 files from their backup location into the database subdirectory of the Network Registrar installation directory (for example, /var/nwreg2/data/db). Copy and do not move the files.

If you are reverting to Network Registrar 5.0, you must also recover the data in CNRDB. You must run the cnrdb_recovery utility. For details on recovering this data, see the Network Registrar User's Guide.

Step 5 Change directories to the database directory.

Step 6 Run the keybuild tool to rebuild the key files. This can take several minutes.

# opt/nwreg2/bin/keybuild mcddb 

Step 7 Verify the integrity of the database by running the dbcheck tool.

# opt/nwreg2/bin/dbcheck mcddb 


Starting and Stopping the Servers

You can start and stop the Network Registrar servers (DNS, DHCP, and TFTP) and databases from the Solaris command line. If the installation completed successfully and you did not stop the servers, they will run automatically and start each time you reboot the machine. However, you can stop and restart them by stopping and restarting the AIC Server Agent program.

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. It controls the loading and unloading of each executable server program and initiates service by starting each server.

To start the AIC Server Agent, do the following:


Step 1 Log in as superuser.

Step 2 Enter the aicservagt command with the start argument.

# /etc/init.d/aicservagt start 

Step 3 Check that the servers are running by entering 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)


To stop the AIC Server Agent, perform the previous steps, except enter the aicservagt command with the stop argument at Step 2.

# /etc/init.d/aicservagt stop 

What to Do Next

After you complete the installation, Network Registrar is ready for configuration. The details are specific to your network. However, the sequence of configuration tasks is generally as follows:

1. Add clusters

2. Add user accounts

3. Configure DNS server properties

4. Configure DNS zones

5. Configure DHCP server properties

6. Configure DHCP scopes (including policies, options, clients, and client-classes)

7. Customize server operations

Procedures for these tasks are included in the Network Registrar User's Guide.