Installation Guide for Cisco Network Registrar 7.1
Overview
Downloads: This chapterpdf (PDF - 138.0KB) The complete bookPDF (PDF - 805.0KB) | Feedback

Overview

Table Of Contents

Overview

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

Upgrading


Overview


This guide describes how to install Cisco Network Registrar Release 7.1 on Windows, Solaris, and Linux operating systems. You can also refer to the following 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 the following 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.1 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. Network Registrar can run on 32-bit or 64-bit operating systems. The Network Registrar applications are 32-bit. These applications run in 32-bit mode.

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) and 7.0, Mozilla Firefox 2.0 and 3.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

Component
Operating System
Solaris 1
Linux
Windows

OS version2

Solaris 103

Red Hat Enterprise Linux ES (v. 4)

Red Hat Enterprise Linux 5

Windows Server 2003

Disk space4

2 x 73/146 SAS5 drives

With basic DHCP and optimal hardware configuration:

SATA6 drives with 7500 RPM drive > 500 leases/second

SAS drives with 15K RPM drive > 1000 leases/second

(Recommended hard drive 146 GB)

Memory7

16 GB

4 GB (small networks), 8 GB (average networks), or 16 GB (large networks)

1 Supports Solaris on Sun SPARC platform.

2 Network Registrar can run on 32-bit or 64-bit operating systems.

3 Network Registrar 7.1 supports 128-KB block sizes in the Solaris 10 ZFS.

4 Higher I/O bandwidth usually results in higher average leases per second.

5 Serial Attached SCSI.

6 Serial Advanced Technology Attachment (Serial ATA).

7 Faster CPU and more memory typically result in higher peak leases per second.


7 If you are upgrading from an earlier version of Network Registrar to Network Registrar 7.1, on the Solaris platform, make sure you upgrade the Solaris version as mentioned in "Upgrading" section.



Installation Modes

The modes of installation that exist for the local and regional clusters are new installations and upgrades from a previous version. 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 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. You can give any name to the license file. You must specify this file name while you install Network Registrar.

The type of the license file supported in Network Registrar 7.1 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.

To know about obtaining the license files for Network Registrar, see "Obtaining Network Registrar License Files" section on page 2-2.

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:

Windows—

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 sub directories contain data that you may want only the Administrators system group to access:

installdir\conf\cnr.conf

installdir\tomcat\conf\server.xml

installdir\conf\priv\

installdir\data\

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 and the directory itself. To keep this 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. If the Network Registrar installation process detects that a conflict exists, it displays a warning message.

On Windows systems, use one of these methods to change the configuration from the Service Control Manager:

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.

Upgrading

Network Registrar 7.1 supports upgrades from releases 6.2.x, 6.3.x, and 7.0. The upgrade process differs slightly depending on the release from which you are upgrading.

During the installation, the Network Registrar installer automatically detects an existing version and upgrades it. You can choose to archive the existing data in a location that you specify. If the upgrade process encounters any error, Network Registrar notifies you about that and rolls back the upgrade process.


Note On the Solaris platform:

Before you upgrade from Network Registrar 7.0.1 or 6.3.x to Network Registrar 7.1, you must upgrade to Solaris 10 from Solaris 9.

Before you upgrade from Network Registrar 6.2.x, you must upgrade to Network Registrar 6.3.x on Solaris 9, and then upgrade to Solaris 10.


We recommended that you upgrade the regional cluster before upgrading any local clusters, because an older version regional cluster cannot connect to newer local clusters.


Note This document describes the upgrade information for the versions starting from 6.2. If you are upgrading from a version prior to 6.2, refer the Installation and Setup Guides and the Release Notes for the relevant versions on Cisco.com.