Cisco Network Registrar Installation Guide, 7.0
Chapter 1: Installation Overview
Downloads: This chapterpdf (PDF - 131.0 KB) The complete bookPDF (PDF - 710.0 KB) | Feedback


Table Of Contents


About Network Registrar

System Requirements

Installation Modes

License Files

Backup Software and Virus Scanning Guidelines

Modifying ACLs in Windows Installations

Server Event Logging

Running Performance Monitoring Software on Windows

Running Other Protocol Servers



This guide describes how to install Cisco Network Registrar Release 7.0 on Windows, Solaris, and Linux operating systems. You can also refer to these documents for important information about configuring and managing Network Registrar:

For configuration and management procedures for Network Registrar, see the Cisco Network Registrar User's Guide.

For details about commands available through the command line reference (CLI), see the Cisco Network Registrar CLI Reference.

About Network Registrar

Network Registrar is a network server suite that automates managing enterprise IP addresses. It provides a stable infrastructure that increases address assignment reliability and efficiency. It includes these servers (see Figure 1-1):

Dynamic Host Configuration Protocol (DHCP)

Domain Name System (DNS)

Router Interface Configuration (RIC)

Simple Network Management Protocol (SNMP)

Trivial File Transfer Protocol (TFTP)

You can control these servers by using the Network Registrar web-based user interface (web UI) or the command line interface (CLI). These user interfaces can also control server clusters that run on different platforms.

You can install Network Registrar in either local or regional mode:

Local mode is used for managing local cluster protocol servers.

Regional mode is used for managing multiple local clusters through a central management model.

A regional cluster centrally manages local cluster servers and their address spaces. The regional administrator can perform these operations:

Push and pull configuration data to and from the local DNS and DHCP servers.

Obtain subnet utilization and IP lease history data from the local clusters.

Manage the router interface configuration (RIC) server that integrates with cable modem termination systems (CMTSs) directly from the regional cluster.

Figure 1-1 Network Registrar User Interfaces and the Server Cluster

System Requirements

Review these system requirements before installing the Network Registrar 7.0 software:

Java—You must have the Java Runtime Environment (JRE) 5.0 (1.5.0_06) or later, or the equivalent Java Development Kit (JDK) installed on your system. (The JRE is available from Sun Microsystems on its website.)

Operating system—Your Network Registrar machine must meet the minimum requirements on the Windows, Solaris, or Linux operating systems that are specified in Table 1-1.)

User Interface—Network Registrar currently includes two user interfaces: a web UI and a CLI:

The web UI runs on a minimum of Microsoft Internet Explorer 6.0 (Service Pack 2), Mozilla Firefox 1.5, or Netscape 7.0 and requires JRE 5.0 [1.5].

The CLI runs in a Windows, Solaris, or Linux command window.

Tip Include a network time service in your configuration to avoid time differences between the local and regional clusters. This method ensures that aggregated data at the regional server appears consistently.

Table 1-1 Network Registrar Server Minimum Requirements 


CPU architecture

Intel Pentium III or its equivalent

Sun Netra AC200

Intel Pentium III or its equivalent

OS version

Windows 2003 server

Solaris 9 or Solaris 10

Red Hat Enterprise Linux ES 4.0


512 MB for all operating systems

Disk space

18 GB recommended, minimum 310 MB required for installation

Swap space

100 MB free swap space

Installation Modes

The modes of installation that exist for the local and regional clusters are new installations and upgrades from a previous version with or without data migration. These installations or upgrades are performed by using operating-system-specific software installation mechanisms:

Windows—InstallShield setup program

Solaris—pkgadd command

Linux—install_cnr script that uses RPM Package Manager (RPM)

License Files

Network Registrar now uses the FLEXlm licensing tool. Your license file defines the features of Network Registrar to which you have access. When you install the software, you are prompted to provide the name of the license file and its location. The name of the license file supported in Network Registrar 7.0 is ip-node.

An ip-node license gives you the right to manage a specified number of IP addresses. One license covers both IPv4 and IPv6 nodes. For example, to manage 24,000 IPv4 nodes and 10,000 IPv6 nodes in a local cluster, you must purchase an ip-node license that covers 34,000 total nodes.

This method also applies on a regional server. With a regional server, however, you must aggregate the licensed nodes from all managed local clusters. Consider the following scenario in which the regional server manages three local clusters:

local cluster A has 24,000 IPv4 nodes and 10,000 IPv6 nodes

local cluster B has 2,000 IPv4 nodes and 12,000 IPv6 nodes

local cluster C has 48,000 IPv4 nodes and 1,000 IPv6 nodes

The regional cluster must have an ip-node license that covers 97,000 total nodes.

Backup Software and Virus Scanning Guidelines

If you have automatic backup or virus scanning software enabled on your system, exclude these Network Registrar directories and their subdirectories from being scanned. If they are not excluded, file locking issues can corrupt the databases or make them unavailable to the Network Registrar processes. If you are installing to the default locations, exclude the following directories and their subdirectories:


install-path\data (for example, C:\Program Files\Network Registrar\Local\data and C:\Program Files\Network Registrar\Regional\data)
install-path\logs (for example, C:\Program Files\Network Registrar\Local\logs and C:\Program Files\Network Registrar\Regional\logs)

Solaris and Linux—

install-path/data (for example, /var/nwreg2/local/data and /var/nwreg2/regional/data)
install-path/logs (for example, /var/nwreg2/local/logs and /var/nwreg2/regional/logs)

Modifying ACLs in Windows Installations

The Network Registrar installation program for Windows does not try to modify ACLs to restrict access to installed files and directories. If you want to restrict access to these files and directories, use the native Microsoft utilities cacls and icacls to manually change file and directory permissions.

If you decide to manually change ACLs, Cisco recommends that you control the settings so that the contents of the entire installation area are read-only to everyone except those in the Administrators system group.

The following files and subdirectories are used to restrict access to the Administrators system group:





Modifying the ACLs is strictly optional, and Network Registrar will function normally without making any changes to them. Refer to documentation supplied by Microsoft for information about how to use the cacls and icacls utilities.

Server Event Logging

System activity begins logging when you start Network Registrar. The server maintains all the logs by default in these directories:

Windows—Local cluster: C:\Program Files\Network Registrar\Local\logs;
Regional cluster: C:\Program Files\Network Registrar\Regional\logs

Solaris and Linux—Local cluster: /var/nwreg2/local/logs;
Regional cluster: /var/nwreg2/regional/logs

To monitor the logs, use the tail -f command.

Caution In Windows, to avoid losing the most recent system Application Event Log entries if the Event Log fills up, use the Event Viewer system application to click the Overwrite Events as Needed check box in Event Log Settings for the Application Log. If the installation process detects that this option is not set properly, it displays a warning message advising corrective action.

Running Performance Monitoring Software on Windows

On Windows systems only, if you uninstall Network Registrar and try to remove the associated data directories while having software installed that integrates with the Windows Performance Monitor, the software might take possession of certain shared libraries. This action prevents you from removing these files from the Network Registrar folder; hence, the directory itself. To keep this event from happening:

1. Stop the service that is associated with the performance monitoring software.

2. Delete the Network Registrar folder.

3. Restart the service.

Running Other Protocol Servers

You cannot run the Network Registrar DNS, DHCP, or TFTP servers concurrently with any other DNS, DHCP, and TFTP servers. In many Windows 2000 server systems, these services are enabled and running by default. If the Network Registrar installation process detects that a conflict exists, it displays a warning message.

Use one of these methods to change the Windows configuration from the Service Control Manager (Control Panel > Administrative Tools > Services in Windows 2000):

Change the Microsoft servers from a Startup Type of Automatic to Manual or Disabled.

Stop the Network Registrar protocol server that conflicts with the Microsoft one by using the Stop function in one of the user interfaces.

If you want to disable a protocol server and prevent the Network Registrar server from starting automatically after a system reboot, use the server {dns | dhcp | tftp} disable start-on-reboot command in the CLI.


Network Registrar 7.0 supports upgrades from releases 6.1.x, 6.2.x, and 6.3. The upgrade process differs slightly depending on the release from which you are upgrading. To preserve your existing configurations during the upgrade:

From Network Registrar 5.5 or earlier, you must first upgrade to 6.1. You must then do a further upgrade to 6.2.1.

You can upgrade to 6.2.1 while preserving the earlier configuration, or you can replace the configuration.

Improvements in the Network Registrar software database from release to release can result in important changes that affect the way that you use Network Registrar:

The DHCP server's configuration changed substantially in 6.2. Attributes formerly set on a scope or DHCP server to configure DHCP failover, DNS updates and traps are now set separately and stored in new data objects. You cannot upgrade custom or vendor-specific DHCP options; you must reenter them using the new 6.2 functions.

Beginning with Network Registrar 6.1.1, administrators and related data can be centrally managed, which allows administrators, groups, and roles to be defined centrally at one time and then populated throughout the system. To simplify central management, groups are used exclusively to associate administrators with roles. These groups now manage the role assignments.

If you configured administrators with direct role assignments, the upgrade converts these role assignments to group assignments. Group names are created from role names by appending the suffix -group, with numbers appended as needed to avoid conflicting names. These groups are only created for the upgrade, but only for roles that have administrators associated with them.

If you are upgrading from 6.0, a number of name changes to processes, utilities, and files occurred in 6.1 that can affect automated scripts that you have from previous releases.Table 1-2 summarizes these changes.

Table 1-2 Name Changes from Release 6.0 

Previous Name
New Name
Change Action

AIC Server Agent 2.0

Displays as Network Registrar Local (or Regional) Server Agent

Windows Network Registrar server name renamed to local and regional server names



Solaris and Linux start/stop script renamed



Windows Network Registrar server agent executable file renamed



Solaris and Linux Network Registrar server agent executable file renamed



Windows MCD server executable renamed to the CCM server



Solaris and Linux MCD server executable renamed to the CCM server



Server log file renamed



Solaris and Linux server status utility renamed