Cisco Network Registrar Installation Guide, 6.2
1 - Overview
Downloads: This chapterpdf (PDF - 211.0KB) The complete bookPDF (PDF - 899.0KB) | Feedback

Overview

Table Of Contents

Overview

About Network Registrar

System Requirements

Installation Modes

License Keys

Backup Software and Virus Scanning Guidelines

Server Event Logging

Running Performance Monitoring Software on Windows

Running Other Protocol Servers

Upgrading


Overview


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

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

For details about commands available through the command line reference (CLI), see the Cisco CNS 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 these 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 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 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 6.2:

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

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), Mozilla Firefox 1.0, or Netscape 7.0 and requires Java JRE 1.4.2 or later.

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
Windows
Solaris
Linux

CPU architecture

Intel Pentium III or its equivalent

Sun Netra AC200

Intel Pentium III or its equivalent

OS version

Windows XP or Windows 2003

Solaris 8 or Solaris 9

Red Hat Enterprise Server (ES) 3.0

RAM

512 MB for all operating systems

Disk space

18 GB recommended, minimum 310 MB required for installation

Swap space

100 MB free swap space


Installation Modes

The modes of installation that exist for the local and regional clusters are new installations and upgrades from a previous version with or without data migration. 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 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.

You can enter the license key during software installation or later in the Web UI or CLI. However, you are prompted for a license key during installation only if there is no valid key in a license file, if such a file exists from a previous installation.

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 cannot 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.

The license keys that you may need are:

Local cluster key—Manages the local cluster servers in the Web UI or CLI. If you have Network Registrar 6.1 installed, you can upgrade by 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.

IPv6 addressing key—Manages IPv6 addresses in the 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 you need a new license key:

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

Upgrading from 6.1—Use the license key from 6.1.

Upgrading from a release before 6.1—Add a new license key. License keys that were valid before 6.1 will not work.

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)

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; hence, the directory itself. To keep this event 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. In many Windows 2000 server systems, these services are enabled and running by default. If the Network Registrar installation process detects that a conflict exists, it displays a warning message.

Use one of these methods to change the Windows configuration from the Service Control Manager (Control Panel > Administrative Tools > Services in Windows 2000):

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

The upgrade process differs slightly depending on the release from which you are upgrading. To preserve your existing configurations during the upgrade:

From Network Registrar 5.5 or earlier, you must first upgrade to 6.0 or 6.1. You must then do a further upgrade to 6.2.

You can upgrade to 6.2 while preserving the earlier configuration, or you can replace the configuration.

Improvements in the Network Registrar software database from release to release can result in important changes that affect the way that you use Network Registrar:

The DHCP server's configuration changed substantially in 6.2. Attributes formerly set on a scope or DHCP server to configure DHCP failover, DNS updates and traps are now set separately and stored in new data objects. You cannot upgrade custom or vendor-specific DHCP options; you must reenter them using the new 6.2 functions.

Beginning with Network Registrar 6.1.1, administrators and related data can be centrally managed, which allows administrators, 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 configured administrators 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, but only for roles that have administrators associated with them.

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

Table 1-2 Name Changes from Release 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