Cisco CNS Network Registrar Installation Guide, 6.0
Overview
Downloads: This chapterpdf (PDF - 201.0KB) The complete bookPDF (PDF - 794.0KB) | Feedback

Overview

Table Of Contents

Overview

Types of Installations

Before You Begin

License Keys

Java Requirements

Server Requirements

User Interface Requirements

Virus Scanning While Running Network Registrar

Logging Server Events

Running Network Registrar and Other Protocol Servers

Usernames

After Installation


Overview


Cisco CNS 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 Web-based user interface (Web UI), Windows-based 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

Types of Installations

There are three basic types of installations:

New installations

Upgrading with data migration

Upgrading without data migration

Before You Begin

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

License Keys


Caution You must use the software license key shipped with Network Registrar 6.0 and enter it when you run the product. License keys that were valid for previous versions will not work. To avoid delays in accessing the user interfaces, ensure that the new license key is available before you install or upgrade.

Java Requirements

Before installing the Network Registrar 6.0 Web-based user interface (Web UI), you must have the Java Runtime Environment (JRE) version 1.3.1 (or equivalent Java Development Kit, JDK) or later installed on your system. The JRE is available from Sun Microsystems at their website.

Solaris systems also require certain patches to be installed to run the JRE or JDK. Instructions on how to check your current patches are also available from the Sun website.

Server Requirements

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

Table 1-1 Network Registrar Server Minimum Requirements 

Component
Windows
Solaris
Linux

CPU architecture

Intel Pentium III or equivalent

Sun Netra AC200

Intel Pentium III or equivalent

OS version

Windows 2000
Service Pack 1 (SP2 recommended1 ) or Windows NT 4.0 SP6a2 workstation or server

Solaris 8 or Solaris 9

Red Hat Linux 7.3
(kernel version 2.4), with Red Hat Package Manager (RPM) 4.0.4

RAM

512 MB

512 MB

512 MB

Disk space

18 GB recommended, minimum 310 MB required for installation

Swap space

100 MB free swap space

1 Network Registrar was tested for Japanese Windows 2000 SP2, with support for the English language version only.

2 Network Registrar 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 service pack supported.


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


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

User Interface Requirements

Network Registrar currently includes three user interfaces, a Web-based user interface (Web UI), a command line interface (CLI), and a Windows-based graphical user interface (GUI):

The Web UI runs on a minimum of Microsoft Internet Explorer 5.5 (Service Pack 2) or Netscape 6.2, and requires at least the Java JRE version 1.3.1 installed.

The CLI runs in the Windows, Solaris, and Linux command window.

The GUI runs on Windows 2000 and Windows NT 4.0 systems only. It does not run on Solaris and Linux systems. However, you can access these servers 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 Minimum Requirements 

Component
Windows

CPU Architecture

Intel Pentium III or equivalent

OS Version

Windows 2000 Service Pack 1 (SP2 or later recommended) or Windows NT 4.0 SP6a

Minimum RAM

256 MB

Recommended Free Disk Space

310 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, file locking issues might corrupt the Network Registrar databases or make them unavailable to the Network Registrar process. If you are installing to the default locations, exclude these directories and their subdirectories; on:

Windows—C:\Program Files\Network Registrar\data

UNIX and Linux—/var/nwreg2/data

It you are installing to alternative directories, substitute these in your exclusion list.

Logging Server Events

When you start Network Registrar, it automatically starts logging system activity. Network Registrar maintains all the logs by default in the these directories:

On Windows—Program Files\Network Registrar\logs

On UNIX or Linux—/var/nwreg2/logs


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


To avoid losing the most recent log entries in the Windows Event Viewer, in the Event Log Settings, check the "Overwrite Events as Needed" box. If the installation process detects that this option is not set properly, it displays a warning message advising corrective action.

Running Network Registrar and Other Protocol Servers

You cannot run the Network Registrar DNS and DHCP servers concurrently with any other DNS and DHCP 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 might exist, it displays a warning message. To correct the Windows configuration, from the Service Control Manager (Control Panel > Administrative Tools > Services in Windows 2000), either change the Microsoft servers from a Startup Type of Automatic to Manual or Disabled, or stop the Network Registrar protocol server that conflicts with the Microsoft one by using the Stop function in one of the user interfaces. (The server {DNS | DHCP | TFTP} disable start-on-reboot command is available in the CLI to prevent the Network Registrar servers from starting automatically after a system reboot.) For details, see the Network Registrar User's Guide.

Usernames

Usernames are now case-insensitive in Network Registrar 6.0. If you upgrade with usernames that differ in case only, the upgrade process deconflicts these usernames, and a warning message to that effect appears in the mcdupgrade_log file.

All existing usernames are converted to NRCMD limited access users, as defined in the Web UI, except the admin account, which is converted to superuser. If there is no admin account, it is created with a password of changeme.

After Installation

After installing Network Registrar, you must enter a new license key and configure Network Registrar for your network. For the configuration procedures, see the Network Registrar User's Guide and the Network Registrar Web UI Guide. For details about commands available through the CLI, see the Network Registrar CLI Reference. Additional on-line help is available from the Web UI and CLI.