Cisco CNS Network Registrar Installation Guide, 6.1
Overview
Downloads: This chapterpdf (PDF - 213.0KB) The complete bookPDF (PDF - 805.0KB) | Feedback

Overview

Table Of Contents

Overview

Installation Modes

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

Name Changes in Release 6.1

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) or command line interface (CLI). These user interfaces can control server clusters that run on different platforms.

Network Registrar 6.1 also now offers a regional cluster for central management of local cluster servers and their address spaces. The regional administrator can pull and push configuration data from and to the local DNS, DHCP, and TFTP servers, and subnet utilization and lease history data from the local clusters. The regional administrator can also 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

Installation Modes

There are three basic installation modes, and each can be for the local or regional cluster:

New installations

Upgrade with data migration

Upgrade 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.1 and enter it when you run the product. License keys that were valid before Network Registrar 6.0 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 Network Registrar 6.1, 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.

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 recommended)

Solaris 8 or Solaris 9

Red Hat Linux 7.3 (kernel version 2.40) with Package Manager (RPM) 4.0.4, or Red Hat Linux Enterprise ES or WS 2.1 (kernel version 2.4.9-e.24)

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



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 two user interfaces, a Web UI for local and regional clusters, and a CLI for the local cluster:

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 CLI runs on the local cluster only and not on the regional cluster.

There is no longer a Windows-based graphical user interface (Win32 GUI).

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 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—Local cluster: C:\Program Files\Network Registrar\Local\data;
regional cluster: C:\Program Files\Network Registrar\Regional\data

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

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

Logging Server Events

When you start Network Registrar, this automatically starts logging system activity. Network Registrar 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 or Linux—Local cluster: /var/nwreg2/local/logs;
Regional cluster: /var/nwreg2/regional/logs


Tip To monitor the Unix 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.)

Usernames

Usernames are case-insensitive. 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.

Name Changes in Release 6.1

A number of name changes to processes, utilities, and files occurred in Network Registrar 6.1 that can affect automated scripts you have from previous releases. Table 1-2 summarizes these changes.

Table 1-2 Name Changes in Network Registrar 6.1 

Previous Name
New Name
Change Action

AIC Server Agent 2.0

nwreglocal (displays as Network Registrar Local Server Agent)
nwregregion (displays as Network Registrar Regional Server Agent)

Windows Network Registrar server agent process renamed to local and regional server agent processes

/etc/init.d/aicservagt

/etc/init.d/nwreglocal
/etc/init.d/nwregregion

Solaris and Linux server agent process renamed to local and regional server agent processes

aicservagt.exe

cnrservagt.exe

Windows Network Registrar server agent executable file renamed

aicservagt

cnrservagt

Solaris and Linux Network Registrar server agent executable file renamed

mcdsvr.exe

ccmsrv.exe

Windows MCD server file renamed to the CCM server file

mcdsvr

ccmsrv

Solaris and Linux MCD server file renamed to the CCM server file

config_mcd_1_log

config_ccm_1_log

Configuration log file renamed

aicstatus

cnr_status

Server status utility renamed


After Installation

After installing Network Registrar, you must enter a license key and configure Network Registrar for your network. For the configuration procedures, see the Network Registrar User's 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.