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

Installing Network Registrar on Linux

Table Of Contents

Installing Network Registrar on Linux

Installation Checklist

System Requirements

New Installation

License Key

Uninstalling Network Registrar

Re-installing Network Registrar

Starting and Stopping the Servers

What to Do Next


Installing Network Registrar on Linux


Cisco Network Registrar runs on Red Hat Linux 6.2. This document covers the required installation topics and has the following contents:

Installation Checklist

System Requirements

New Installation

License Key

Uninstalling Network Registrar

Re-installing Network Registrar

Starting and Stopping the Servers

What to Do Next

Installation Checklist

Before you run the Network Registrar for Linux installation program, answer the following questions:

Do you meet the system requirements?—See the "System Requirements" section.

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

System Requirements

To run Network Registrar on Red Hat Linux 6.2, you require the following for the target machine:

IBM Power PC or better with an Intel-based processor, Pentium II or greater.

A minimum 64 MB of RAM.

Red Hat Linux 6.2 (kernel version 2.2)

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

Fastest available disk (such as Ultra-SCSI) and mirrored or RAID disks with 100 MB free swap space.

New Installation

The procedure for a new installation assumes that no previous version of Network Registrar is installed. To install the Network Registrar servers and command line interface on Linux, do the following:


Step 1 Ensure that Red Hat Linux 6.2 (kernel 2.2) is properly installed.

Step 2 If you install from a CD-ROM, insert it in your CD-ROM drive or mount it from your remote server.

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

Step 3 Enter username su and the root password to become the root user.

Step 4 Run the install_cnr program from the installation directory. Always include only the absolute path to the program; it will not work specified as a symbolic link.

install-directory # install_cnr 
Welcome to the Network Registrar installation program for Linux.

Please enter the directory where you would like Network Registrar binaries to be 
installed.

Step 5 Enter at the prompt the location where you want the Network Registrar binaries installed, or accept the default /opt/nwreg2 directory.

[Default to /opt/nwreg2]: 

Please enter the directory where you would like the databases and log files to be created.

Step 6 Enter at the prompt the location where you want to store the database and log files, or accept the default /var/nwreg2 directory.

[Default to /var/nwreg2] :

You will see a few processing and server startup messages, and the installation is complete.


License Key

In Network Registrar terminology, a cluster is a group of Network Registrar server processes that share a database. To administer the cluster of servers you just installed, you must enter the license key. This license key appears on the back of the installation CD-ROM case.

The license is for the command line interface (CLI). The servers and CLI can run on different machines.

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

If you have an evaluation copy of Network Registrar, your license will expire.

If you have an invalid license or missing license key, you cannot configure or manage the Network Registrar servers, although the servers will continue to function normally.

Enter the license key as follows:


Step 1 Start the Network Registrar CLI (the nrcmd program) from the Linux command prompt. The standard location of the program is:

# /opt/nwreg2/usrbin/nrcmd 

Step 2 When prompted, enter username admin and password changeme.

Step 3 Enter the 16-digit license key at the nrcmd> prompt.

nrcmd> license set key=license-key 

Step 4 Change the password of the admin account.

nrcmd> admin admin enterPassword 
password: 
verify password: 

Step 5 Exit the CLI by entering exit at the nrcmd> prompt.

nrcmd> exit 


Uninstalling Network Registrar

The uninstall_cnr program 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.

Run the uninstall_cnr program as follows:

install-directory# uninstall_cnr 
Stopping Server Agent...
Deleting startup files...
Removing Network Registrar...
cannot remove /opt/nwreg2/usrbin - directory not empty
cannot remove /opt/nwreg2/conf - directory not empty
package optnwreg2 not found in file index
Note that any files that have been changed (including your database) have _not_ been 
uninstalled. You should delete these files by hand when you are done with them, before you 
reinstall the package.

The "cannot remove" warnings means that, although the uninstall program removes the server and user interface components, it cannot delete the database and log files. You must delete these separately before you re-install Network Registrar. You might want to delete what is left in the binary, data, and log directories.

You can ignore the "package optnwreg2 not found in file index" warning; the package does not actually exist. This is a known issue with the RPM utility on Linux 6.2.


Note The uninstall process usually stops the Network Registrar AIC Server Agent first. If you find that the server processes are not shutting down, see the "Starting and Stopping the Servers" section.


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 Linux, this involves backing up the product databases, uninstalling, re-installing, and recover the databases. If you do not want to retain your data, simply uninstall, delete any leftover files, and re-install. The full process is as follows.


Step 1 Ensure that you have a copy of the most recent shadow backup of the databases. If not, ensure that you have enough disk space for the backup and run the mcdshadow backup program. For the MCD data, check its integrity using the dbcheck program from the .../data/db directory; for the CNRDB data, use the cnrdb_check program from the .../data/server-type/ndb directory.

.../bin# mcdshadow 
.../data/db# dbcheck -a mcddb 
.../data/dns/ndb# cnrdb_check 
.../data/dhcp/ndb# cnrdb_check 

Step 2 Shut down the servers.

...# /etc/rc.d/init.d/aicservagt stop 

Step 3 Copy the operational database and log files in the .../data directory to the /recover and /dbcopy directories, which should not be in the installation path. The /recover directory contains the actual recovery files, while the /dbcopy directory stores a safety copy.

.../data# cp -rf *.bak .../recover/. 
.../data# cp -rf *.bak .../dbcopy/. 

Step 4 Uninstall Network Registrar using the uninstall_cnr program. Be sure to remove any leftover files not deleted by the uninstall program.

install-directory# uninstall_cnr 

Step 5 Re-install Network Registrar using the install_cnr program.

install-directory# install_cnr 

Step 6 Stop the servers again, check for disk space, and recover the databases.

a. Recover the MCD data by copying the three mcddb.* files in .../data/db.bak to .../data/db. Rebuild the key files and check the data integrity.

...# /etc/rc.d/init.d/aicservagt stop 
.../recover/db.bak# cp mcddb.* ./db 
.../data/db# keybuild mcddb 
.../data/db# dbcheck mcddb 

a. Recover the CNRDB data by running the cnrdb_recover -c -v recovery program on the server subdirectories of the .../recover directory. Then, verify and (optionally) archive the recovery. Finally, if no errors occur, copy all the files in .../recover to the .../data directories.

.../recover/dns.bak# cnrdb_recover -c -v 
.../recover/dns.bak# cnrdb_verify dns.ndb 
.../recover/dns.bak# cnrdb_archive -l 
.../recover/dns.bak# cnrdb_archive -s 
.../recover/dhcp.bak# cnrdb_recover -c -v 
.../recover/dhcp.bak# cnrdb_verify dhcp.ndb 
.../recover/dhcp.bak# cnrdb_archive -l 
.../recover/dhcp.bak# cnrdb_archive -s 
.../recover# cp -rf dns.bak/* ../data/dns/. 
.../recover# cp -rf dhcp.bak/* ../data/dhcp/. 

Step 7 Restart the servers and start using the recovered data on the re-installed product.


Starting and Stopping the Servers

You can start and stop the Network Registrar servers (DNS, DHCP, TFTP) from the Linux command line. If the installation is successful and you did not stop the servers, they run automatically and start each time you reboot. However, you can explicitly stop and restart the servers through the AIC Server Agent program. This is the first Network Registrar program to run each time the host boots up and the last one to exit when you shut down. It controls loading and unloading each server's executable programs.

To stop the AIC Server Agent and all Network Registrar server processes, log in to Linux as superuser and enter the aicservagt stop command.

# /etc/rc.d/init.d/aicservagt stop 

To start the AIC Server Agent and all Network Registrar server processes, enter the aicstatus command in the /opt location to check that the servers are running.

# install-path/usrbin/aicstatus 

Then enter the aicservagt start command.

# /etc/rc.d/init.d/aicservagt start 

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.