Cisco CNS Network Registrar Installation Guide, 5.5
Overview

Overview

Table Of Contents

Overview

DNS Features

DHCP Features

TFTP Features

Administration Features

Types of Installations

Before You Begin

Server Requirements

GUI Requirements

Virus Scanning While Running Network Registrar

What to Do After Installation


Overview


Network Registrar automates enterprise IP address management. It provides a stable infrastructure that increases the reliability and efficiency of the address assignment process. It also substantially diminishes the administrative burden associated with address management. It includes Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), and Trivial File Transfer Protocol (TFTP) servers (Figure 1-1). You can control these servers using the Network Registrar graphical user interface (GUI) or command line interface (CLI). These user interfaces can control server clusters that run on different platforms.

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

DNS Features

Network Registrar supports the following DNS features:

Dynamic DNS update (RFC 2136), including zone record scavenging

Incremental zone transfer (IXFR; RFC 1995)

NOTIFY (RFC 1996)

Multithreading for scalable performance

DNS subnet sorting

Second generation design with two-level persistent cache and efficient memory management

Stale record scavenging

DHCP Features

Network Registrar offers the following DHCP features:

E-mail lease notification at a user-configurable level which, when reached, sends e-mail to the administrator

DHCP option validation

DHCP custom options

DHCP vendor-specific options

Name synchronization through dynamic DNS update

Pinging addresses before allocation

Address pools on multiple subnets

BOOTP relay

Audit log of address assignments

DHCP failover, proving server redundancy

TFTP Features

Network Registrar offers the following TFTP features:

High performance, multithreaded architecture

Integrated with DNS and DHCP servers

Configurable and controllable from the CLI

Flexible path and file access controls

Audit logging of TFTP connections and file transfers

Administration Features

Network Registrar offers the following administration features:

Motif" and Windows" GUIs that manage servers locally or remotely

Address utilization reports

Ability to start, stop, and reload servers, and monitor server statistics

Embedded configuration database

Easy import of existing DNS BIND zone files

Database exchange format for ASCII imports and exports

DNS zone transfer and dynamic update restrictions, by IP address or host name

Administrator login required to access the GUI; each administrator has a separate password

Log files to record server operations

Logging DHCP address assignments for later analysis

SNMP notification to warn of error conditions and possible problems with servers

Types of Installations

There are three basic types of installations:

New installations

Upgrading with data migration

Upgrading without data migration


Note You can upgrade Network Registrar 5.0 and 3.5 databases to 5.5, but you cannot downgrade from 5.5.


For Microsoft Windows (Chapter 2), one installation procedure handles all three types of installations.

Solaris (Chapter 3) and Linux (Chapter 4) installations involve separate procedures for new installations and upgrades. During the upgrade procedure, you are prompted to indicate whether to delete the earlier version of the database or convert it to the new one.

Before You Begin

If you already have an earlier version of Network Registrar installed, finish any critical updates and back up your 5.0 or 3.5 database. Your site must also meet the following server and client requirements.

Server Requirements

Table 1-1 shows the minimum requirements for the Network Registrar servers.

Table 1-1 Network Registrar Server Requirements 

Component
Windows
Solaris
Linux

CPU Architecture

Equivalent of Intel" Pentium 200 MHz or better (Pentium Pro or greater recommended)

Sun SPARCStation 20 or better

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

OS Version

Windows 2000 SP1 (SP2 or later recommended) or
Windows NT 4.0 SP6a1 workstation or server

Solaris 7 or
Solaris 8

Red Hat Linux 6.2 (kernel version 2.2)

Minimum RAM

64 MB

96 MB

64 MB

Minimum Disk Space 2

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

Recommended Disk

The fastest available disk (such as Ultra-SCSI) and mirrored or RAID disks

Swap Space

100 MB free swap space

1 Network Registrar 5.5 will crash if you run NT 4.0 with no Service Pack installed. This crash occurs when you add recipients to the enabled SNMP traps. SP6a is the minimum supported.

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


Solaris 2.6, Windows NT 3.5.1, Windows 95, Windows 98, HP-UX, and IBM AIX are no longer supported.


Caution Network Registrar is not compatible with Cisco Access Registrar (CAR). The two products cannot be run on the same host machine. Verify that CAR was not installed on your server. The integrity of Network Registrar and CAR will be compromised if you try to run both products simultaneously.

GUI Requirements

The Network Registrar GUI runs on Sun Solaris, Windows 2000, and Windows NT 4.0 systems only. The GUI does not run on Linux systems; however, you can access a Linux server using the GUI on another system. If you run the GUI on the same machine as the servers, you can use the requirements listed in Table 1-1. If you run the GUI on a separate system, use the requirements listed in Table 1-2.

Table 1-2 Network Registrar GUI System Requirements 

Component
Windows
Solaris

CPU Architecture

Equivalent of Intel" 80486, or Pentium or Pentium Pro

SPARCStation 20 or better

OS Version

Windows 2000 SP1 (SP2 or later recommended) or Windows NT 4.0 SP6a workstation or server

Solaris 7 or Solaris 8 and CDE 1.02 (Desktop 1.1)

Minimum RAM

32 MB, 48 MB for over 10,000 hosts

64 MB

Recommended Disk

20 MB

50 MB


Virus Scanning While Running Network Registrar

If you have virus scanning enabled on your system, it is best to configure it to exclude certain Network Registrar directories from being scanned. Otherwise, it could be damaging to Network Registrar operation. Exclude the following directories and their subdirectories:

On Windows—\Program Files\Network Registrar\data

On UNIX and Linux—/var/nwreg2/data

What to Do After Installation

After Network Registrar is installed, you must configure it for your network. For procedures on configuring Network Registrar, see the Network Registrar User's Guide. For details about commands available through the CLI, see the Network Registrar CLI Reference Guide. Additional on-line help is available from the CLI.