Cisco CNS Network Registrar Installation Guide, 6.1.1
1 - Overview
Downloads: This chapterpdf (PDF - 222.0KB) The complete bookPDF (PDF - 781.0KB) | Feedback

Overview

Table Of Contents

Overview

About Network Registrar

Installation Modes

Before You Begin

Before Upgrading

License Keys

System Requirements

Virus Scanning

Server Event Logging

Running Other Protocol Servers

Upgrade Impacts to the System


Overview


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

Before performing an installation or upgrade, review the Release Notes for Cisco CNS Network Registrar Release 6.1.1 document. It provides an overview of new features and describes resolved and open bugs.

For configuration and management procedures for Network Registrar, refer to Cisco CNS Network Registrar User's Guide.

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

You can access Network Registrar technical documentation at this website:

http://www.cisco.com/en/US/products/sw/netmgtsw/ps1982/index.html

About Network Registrar

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

Domain Name System (DNS)

Dynamic Host Configuration Protocol (DHCP)

Trivial File Transfer Protocol (TFTP)

Central Configuration Management (CCM)

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 control server clusters that run on different platforms.

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

Local mode is used for managing local cluster protocol servers.

Regional mode is used for managing multiple local clusters through the 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

Installation Modes

The modes of installation that exist for the local or regional cluster are new installations and upgrades from a previous version with or without data migration. These installations or upgrades are performed through these means:

Windows—Using a Windows-based InstallShield setup program

Solaris—With the pkgadd command

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

Before You Begin

This section describes critical Network Registrar information that you must read before performing a new installation or upgrade:

Before Upgrading

License Keys

System Requirements

Virus Scanning

Server Event Logging

Running Other Protocol Servers

Upgrade Impacts to the System

Before Upgrading

The upgrade process differs slightly depending on which release you are upgrading from:

If you are upgrading from Network Registrar 3.5 or earlier, you must upgrade first to Release 5.5. Then you can upgrade from Release 5.5 to 6.1.1. You cannot upgrade directly from Release 3.5 to 6.1.1.

If you are upgrading from Network Registrar Release 6.0. 5.5, or 5.0, you can upgrade to Release 6.1.1 while preserving the earlier configuration, or you can replace the configuration.

Before beginning an upgrade from an earlier version of Network Registrar, ensure that you have completed these tasks:

Verify that no user interface sessions are active before beginning the upgrade because if sessions are active, configuration changes may not have been committed to the configuration database.

Back up your database. The installation program tries to detect configuration data from a Network Registrar 6.0, 5.5, and 5.0 installation. It also upgrades the data to the Network Registrar 6.1.1 database format if you choose to upgrade.

If you are upgrading from Release 5.5 and have IP history enabled, export and save your existing lease history data. If you do not save the data, it will be lost.

To complete the upgrade, your system must also meet the current server requirements. Refer to the "System Requirements" section section.

License Keys

Each Network Registrar software license key addresses a separate functional area. You enter these license keys in the Web UI or CLI, which accepts the local cluster key only, or during an upgrade installation. During an upgrade, you are prompted for a license key only if no valid license keys are found in the existing license file. If a valid license key is found, no prompting occurs during the upgrade.

The license that you have determines the options:

If you have a permanent license, you must enter it once for each cluster. Once it is entered, you are not prompted for a license key again until you install the cluster on another machine or the license key expires.

If you have an invalid or expired license key, you will not be able to configure or manage the Network Registrar servers through the user interfaces until you obtain a valid license key, although the servers will continue to function normally.

These are the license keys that you may need.

Local cluster key—Manages the local cluster servers in the Web UI or command line interface (CLI). If you have Network Registrar 6.0 installed, you can upgrade using the key from that release.

Regional central configuration key—Manages multiple local clusters at the regional cluster, in the Web UI only.

Regional address space key—Manages the address space (address blocks and subnets) in the multiple local clusters at the regional cluster.

Router management key—Manages the RIC server at the regional cluster.

Node count key—Records the number of managed IP addresses at the regional or local cluster.

Follow the guidelines to determine whether or not you need a new license key:

Installing a new Network Registrar—Use the license key that shipped with Network Registrar.

Upgrading from Release 6.1 or 6.0—Use a license key from Release 6.1 or 6.0 for a local server upgrade. The regional cluster requires one or more new license keys introduced in Release 6.1 to view or change the server configuration data.

Upgrading from a version before Release 6.0—Add a new license key. License keys that were valid before Network Registrar 6.0 will not work.

If you need a new license key for installation or upgrade, ensure that it is available to avoid delays.

System Requirements

Review these system requirements before installing the Network Registrar 6.1.1:

Java—You must have the Java Runtime Environment (JRE) 1.3.1 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 these minimum requirements on Windows, Solaris, or Linux operating systems. (See Table 1-1.)

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 its equivalent

OS version

Windows 2000 (Service Pack 2 recommended)1

Solaris 8 or Solaris 9

Red Hat Linux 7.3 (kernel 2.4) or Red Hat Enterprise Linux ES (Enterprise Server) or WS (Workstation) 2.1 (kernel 2.4.9-e.24). Use RPM 4.0.4 or later.

RAM

512 MB on all platforms

Disk space

18 GB recommended, minimum 310 MB required for installation

Swap space

100 MB free swap space

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


User Interface—Network Registrar currently includes two user interfaces: a Web UI for local and regional clusters, and a CLI for local clusters:

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 1.3.1 or later installed.

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


Note Include a network time service in your configuration to avoid time differences between the local and regional clusters. This will ensure that aggregated data at the regional server appears in a consistent way.



Caution You cannot run Cisco Network Registrar and Cisco Access Registrar on the same machine. Attempting to do so will compromise the integrity of both products.

Virus Scanning

If you have virus scanning or automatic backup 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)
install-path\logs (for example, C:\Program Files\Network Registrar\Local\logs)

Solaris and Linux—

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

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 To avoid losing the most recent log entries when the Event Log is full in the Windows Event Viewer, check 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 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 may exist, it displays a warning message.

Change the Windows configuration from the Service Control Manager (Control Panel > Administrative Tools > Services in Windows 2000) by using one of these means:

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.

In the CLI, the server {DNS | DHCP | TFTP} disable start-on-reboot command prevents the Network Registrar servers from starting automatically after a system reboot.

Upgrade Impacts to the System

Improvements in the Network Registrar software database from release to release can result in important changes that you must be aware of before using Network Registrar:

Beginning with Network Registrar 6.1.1, administrators (admins) and related admin data can be centrally managed, which allows admins, 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 have configured admins 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, and only roles that have admins associated with them have a group created. The upgrade does not automatically generate a group for roles that have no admins associated with them.

If you are upgrading from Release 5.0 or 5.5 with usernames that differed in case only, the upgrade deconflicts these names, and a warning message to that effect appears in the log files. Existing usernames are converted to NRCMD limited access users, except the admin account, which is converted to superuser. If no admin account exists, it is created with the changeme password.

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

Table 1-2 Name Changes from Release 5.0, 5.5, or 6.0

Previous Name
New Name
Change Action

AIC Server Agent 2.0

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

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

/etc/init.d/aicservagt

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

Solaris and Linux start/stop script renamed

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 executable renamed to the CCM server

mcdsvr

ccmsrv

Solaris and Linux MCD server executable renamed to the CCM server

config_mcd_1_log

config_ccm_1_log

Server log file renamed

aicstatus

cnr_status

Solaris and Linux server status utility renamed