Kvik SH060 User manual

Cisco Prime Network Registrar 9.1 Installation Guide
First Published: 2017-12-21
Last Modified: 2017-12-21
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright ©1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
©2017 Cisco Systems, Inc. All rights reserved.

CONTENTS
CHAPTER 1 Installation Overview 1
Overview 1
About Cisco Prime Network Registrar 1
CHAPTER 2 Configuration Options 3
Mixed DHCP and DNS Scenarios 3
One-Machine Mixed Configuration 3
Two-Machine Mixed Configuration 3
Three-Machine Mixed Configuration 4
Four-Machine Mixed Configuration 4
DHCP-Only Scenarios 4
One-Machine DHCP Configuration 5
Two-Machine DHCP Configuration 5
DNS-Only Scenarios 5
One-Machine DNS Configuration 5
Two-Machine DNS Configuration 5
Three-Machine DNS Configuration 5
CHAPTER 3 Installation Requirements 7
System Requirements 7
Recommendations 9
Installation Modes 9
License Files 9
CHAPTER 4 Preparing for the Installation 13
Installation Checklist 13
Before You Begin 14
Obtaining Cisco Prime Network Registrar License Files 14
Cisco Prime Network Registrar 9.1 Installation Guide
iii

Running Other Protocol Servers 15
Backup Software and Virus Scanning Guidelines 15
Server Event Logging 16
Modifying ACLs in Windows Installations 16
CHAPTER 5 Installing and Upgrading Cisco Prime Network Registrar 17
Installing Cisco Prime Network Registrar 17
Upgrade Considerations 23
DNS Upgrade Considerations 24
Upgrading on Windows 24
Upgrading on Linux 25
Reverting to an Earlier Product Version 25
Moving an Installation to a New Machine 27
Moving a Regional Cluster to a New Machine 28
Troubleshooting the Installation 29
Troubleshooting Local Cluster Licensing Issues 30
CHAPTER 6 Next Steps 31
Starting Cisco Prime Network Registrar 31
Starting and Stopping Servers 32
Starting and Stopping Servers on Windows 33
Starting and Stopping Servers on Linux 33
Starting or Stopping Servers using the Local Web UI 34
Starting and Stopping Servers using the Regional Web UI 34
CHAPTER 7 Uninstalling Cisco Prime Network Registrar 37
Uninstalling on Windows 37
Uninstalling on Linux 38
Running Performance Monitoring Software on Windows 38
CHAPTER 8 Cisco Prime Network Registrar Virtual Appliance 39
System Requirements 39
Installing and Upgrading Cisco Prime Network Registrar Virtual Appliance 40
Preparing to Deploy the Cisco Prime Network Registrar Virtual Appliance 40
Deploying the Regional Cluster OVA or Local Cluster OVA on VMware 41
Cisco Prime Network Registrar 9.1 Installation Guide
iv
Contents

Booting and Configuring Cisco Prime Network Registrar Virtual Appliance 42
Deploying the Regional Cluster or Local Cluster on a KVM Hypervisor 43
Deploying the Regional Cluster or Local Cluster on OpenStack 44
Upgrading the Cisco Prime Network Registrar Virtual Appliance 46
Upgrading a Cisco Prime Network Registrar Installation to run on a Cisco Prime Network
Registrar Virtual Appliance 46
Upgrading to a new Version of the Virtual Appliance Operating System 48
Upgrading the Cisco Prime Network Registrar Application 48
Next Steps: Cisco Prime Network Registrar Virtual Appliance 49
Configuring Cisco Prime Network Registrar with the CLI on Virtual Appliance 49
Configuring the Virtual Appliance to Automatically Power Up 49
Managing the Cisco Prime Network Registrar Virtual Appliance 50
APPENDIX A Performing a Silent Installation 51
Performing a Silent Installation 51
APPENDIX B Lab Evaluation Installations 57
Lab Evaluation Installations 57
Installing Cisco Prime Network Registrar in a Lab 58
Testing the Lab Installation 58
Uninstalling in a Lab Environment 58
APPENDIX C Installing the Cisco Prime Network Registrar SDK 59
Installing on Linux 59
Installing on Windows 60
Testing Your Installation 60
Compatibility Considerations 60
APPENDIX D Enhancing Security for Web UI 63
Enhancing Security for Web UI 63
APPENDIX E Hardening Guidelines 65
Hardening Guidelines 65
APPENDIX F Configuring Network Access on CentOS 7.3 Using nmcli 67
Cisco Prime Network Registrar 9.1 Installation Guide
v
Contents

Configuring Network Access on CentOS 7.3 Using nmcli 67
APPENDIX G Changing the IP Address using nmcli 71
Changing the IP Address Using nmcli 71
Cisco Prime Network Registrar 9.1 Installation Guide
vi
Contents

CHAPTER 1
Installation Overview
This chapter contains the following sections:
•Overview, page 1
•About Cisco Prime Network Registrar, page 1
Overview
This guide describes how to install Cisco Prime Network Registrar Release 9.1 on Windows and Linux
operating systems, and how to install the Cisco Prime Network Registrar Virtual Appliance. You can also see
the following documents for important information about configuring and managing Cisco Prime Network
Registrar:
•For configuration and management procedures for Cisco Prime Network Registrar and Cisco Prime
Network Registrar Virtual Appliance, see the Cisco Prime Network Registrar 9.1 Administrator Guide.
•For details about commands available through the command line interface (CLI), see the Cisco Prime
Network Registrar 9.1 CLI Reference Guide.
About Cisco Prime Network Registrar
Cisco Prime 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 (see ).
•Dynamic Host Configuration Protocol (DHCP) server
•Domain Name System (DNS) server
•Caching Domain Name System (CDNS) server
•Simple Network Management Protocol (SNMP) server
•Trivial File Transfer Protocol (TFTP) server
You can control these servers by using the Cisco Prime 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.
Cisco Prime Network Registrar 9.1 Installation Guide
1

You can install Cisco Prime Network Registrar in either 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 the following operations:
•Manage licenses for Cisco Prime Network Registrar. An installation must have at least one regional
cluster for license management purposes.
•Push and pull configuration data to and from the local DNS and DHCP servers.
•Obtain DHCP utilization and IP lease history data from the local clusters.
Figure 1: Cisco Prime Network Registrar User Interfaces and the Server Cluster
Cisco Prime Network Registrar 9.1 Installation Guide
2
Installation Overview
About Cisco Prime Network Registrar

CHAPTER 2
Configuration Options
Cisco Prime Network Registrar DHCP, Authoritative DNS, and Caching DNS components are licensed and
managed from the regional server. You need to have a regional server and all services in the local clusters
are licensed through the regional cluster. Only a regional install asks for a license file and only the regional
server accepts new license files. Then the regional server can authorize individual local clusters based on
available licenses.
The sample configuration shown in this chapter is based on the typical use cases described in the following
sections:
•Mixed DHCP and DNS Scenarios, page 3
•DHCP-Only Scenarios, page 4
•DNS-Only Scenarios, page 5
Mixed DHCP and DNS Scenarios
You can set up Cisco Prime Network Registrar for a mixed DHCP and DNS configuration with different
numbers of machines.
One-Machine Mixed Configuration
Configure both DHCP and Auth DNS servers on a single machine, initially enabling the servers as primaries,
and enabling the TFTP server and SNMP traps. Then configure at least one forward zone and corresponding
reverse zone, at least one scope.
Configure both DHCP and Caching DNS servers on a single machine, initially enabling the servers as primaries,
and enabling the TFTP server and SNMP traps. Then you can configure forwarders and exception lists.
Two-Machine Mixed Configuration
A mixed DHCP configuration on two machines offers a few alternatives:
Cisco Prime Network Registrar 9.1 Installation Guide
3

•Configure one machine as primary DHCP and Auth DNS server, and the second machine as a secondary
Auth DNS server. Then configure a zone distribution and DNS access controls on the first machine and
optionally access controls on the second machine.
•Configure one machine as DHCP and Auth DNS main servers and the second machine as DHCP and
Auth DNS backup servers. Perform minimal configuration on the backup machine (changing the password,
enabling DHCP and Auth DNS, and selecting partner backup roles). On the main machine, build the
configuration, creating server pairs and scheduling synchronization tasks with the backup machine.
•Configure one machine as a DHCP server and the second machine as a Auth DNS primary then configure
either machine with DNS Update and push the configuration to the other machine.
•Configure one machine with both DHCP server and Auth DNS server and the second machine as a
Caching DNS server with the Auth DNS server as the Forwarder.
Three-Machine Mixed Configuration
A mixed configuration on three machines offers a few additional alternatives:
•Configure one machine as a DHCP server, the second machine as an Auth DNS primary, and the third
machine as an Auth DNS secondary. Optionally revisit the machines to make the DHCP main the Auth
DNS backup, and make the Auth DNS main the DHCP backup.
•Configure one machine as DHCP failover and Auth DNS High-Availability (HA) main servers, the
second machine as DHCP failover and Auth DNS HA backup servers, and the third machine as a Auth
DNS secondary server.
•Configure one machine as a DHCP server, the second machine as the Auth DNS server and the third
machine as a Caching DNS, with the Auth DNS as the Forwarder.
•Configure one machine as a DHCP primary server and Auth DNS primary, the second machine as a
DHCP secondary and Auth DNS secondary server and the third machine as a Caching DNS, with the
primary Auth DNS of the first machine as the Forwarder.
Four-Machine Mixed Configuration
A mixed configuration on four machines could include:
•DHCP and Auth DNS main and backup pairs, with the first machine as a DHCP main, the second
machine as a DHCP backup, the third machine as an Auth DNS main configured with DNS Update, and
the fourth machine as an Auth DNS backup.
•An add-on to the three-machine scenario, with the first machine as a DHCP main, the second machine
as an Auth DNS main, the third machine as DHCP and Auth DNS backups, and the fourth machine as
an Auth DNS secondary.
•Configure the first machine as DHCP main, second machine as DHCP backup, third machine as Auth
DNS, and Caching in fourth, with Auth DNS as Forwarder.
DHCP-Only Scenarios
A DHCP-only configuration could be on a single machine or two machines.
Cisco Prime Network Registrar 9.1 Installation Guide
4
Configuration Options
Three-Machine Mixed Configuration

One-Machine DHCP Configuration
Initially configure only DHCP, skip the class-of-service and failover options, and revisit the setup to enable
class-of-service and policy options.
Two-Machine DHCP Configuration
Configure the first machine as a DHCP main and the second machine as a backup, with minimal backup
configuration (changing password, enabling DHCP, and selecting the backup role), and set up the first machine
with failover load balancing, optionally scheduling failover synchronization tasks.
DNS-Only Scenarios
A DNS-only configuration could be on one, two, or three machines.
One-Machine DNS Configuration
Initially configure DNS as an Auth primary, Auth secondary, or caching server.
Two-Machine DNS Configuration
Configure the first machine as an Auth DNS primary and the second machine as a secondary, or the first
machine as a main primary and the second machine as a backup primary.
Configure the first machine as an Auth DNS and the second machine as Caching DNS.
Three-Machine DNS Configuration
Configure the first machine as an Auth DNS main primary, the second machine as a backup primary, and the
third machine as a secondary server.
Configure the first machine as Auth DNS primary, the second machine as secondary, and the third machine
as Caching DNS.
Cisco Prime Network Registrar 9.1 Installation Guide
5
Configuration Options
One-Machine DHCP Configuration

Cisco Prime Network Registrar 9.1 Installation Guide
6
Configuration Options
Three-Machine DNS Configuration

CHAPTER 3
Installation Requirements
This chapter contains the following sections:
•System Requirements, page 7
•Installation Modes, page 9
•License Files, page 9
System Requirements
Review the system requirements before installing the Cisco Prime Network Registrar 9.1 software:
•Java—You must have the Java Runtime Environment (JRE) 1.7 or later, or the equivalent Java
Development Kit (JDK) installed on your system. (The JRE is available from Oracle on its website.)
•Operating system—We recommend that your Cisco Prime Network Registrar machine run on the
Windows or Linux operating systems as described in the server minimum requirements table below.
Cisco Prime Network Registrar is supported on 64-bit operating systems.
Cisco Prime Network Registrar supports running in VMWARE ESXi 5.5 or later environment.
For the 64-bit Linux kit, Cisco Prime Network Registrar applications are 64-bit executable
programs and require the 64-bit operating system and applications (Java JRE/JDK,
OpenLDAP library).
Note
•User Interface—Cisco Prime Network Registrar currently includes two user interfaces: a web UI and a
CLI:
◦The web UI has been tested on Microsoft Internet Explorer 9, Mozilla Firefox 21 later and Google
Chrome. Internet Explorer 8 is not supported.
◦The CLI runs in a Windows or Linux command window.
Cisco Prime Network Registrar 9.1 Installation Guide
7

Include a network time service in your configuration to avoid time differences between the local and
regional clusters. This method ensures that the aggregated data at the regional server appears consistently.
The maximum allowable time drift between the regional and local clusters is five minutes. If the time
skew exceeds five minutes, then the installation process will not be able to correctly register the server
with the regional. In this case, unset and set the password on the regional cluster, and sync again.
Tip
Table 1: Cisco Prime Network Registrar Server Minimum Requirements
Operating SystemComponent
WindowsLinux
Windows Server 2012 R23 Red Hat Enterprise Linux ES 6.5
and CentOS 6.52
OS version1
With basic DHCP and optimal hardware configuration:
•For expected peak load between 500 and 1000 DHCP leases per
second, 7500 RPM SATA5drives are recommended.
•For expected peak load above 1000 DHCP leases per second,
15000 RPM SAS drives are recommended. Recommended hard
drive-146 GB
Disk space4
Small networks-8 GB, Average networks-16 GB, or Large networks-32
GB
Memory6
1Cisco Prime Network Registrar 9.1 is supported on 64-bit operating systems. We highly recommend customers move to a 64-bit operating system.
2Cisco Prime Network Registrar 9.1 supports Red Hat Enterprise Linux ES 6.5 , running standalone or on VMWare (ESX Server 5.5 or later) on Cisco Unified
Computing System (CUCS) and other hardware supported by VMWare.
3Cisco Prime Network Registrar 9.1 supports Windows Server 2012 R2, running standalone or on VMWare (ESX Server 5.5 or later) on Cisco Unified Computing
System (CUCS) and other hardware supported by VMWare.
4Higher I/O bandwidth usually results in higher average leases per second.
5Serial Advanced Technology Attachment (Serial ATA).
6Faster CPU and more memory typically result in higher peak leases per second.
System Requirements for Linux OS (RH 6.5 and CentOS 7.3)
To run Cisco Prime Network Registrar (64-bit kit) on Red Hat Enterprise Linux ES 6.5 (64-bit), ensure that
the Java Runtime Environment (JRE) (64-bit) is installed along with its dependencies. The Linux OS has the
following packages. To support External Authentication using AD and GSS TSIG features ensure installation
of the following:
•krb5-libs
•cyrus-sasl-gssapi
Cisco Prime Network Registrar 9.1 Installation Guide
8
Installation Requirements
System Requirements

To know the kind of Linux system you are on, use the following command:
more /etc/redhat-release
Note
Recommendations
When Cisco Prime Network Registrar is deployed on virtual machines, review the following recommendations:
•Do NOT deploy HA DNS or DHCP failover partners on the same physical server (in separate VMs).
This will not provide high availability when the server goes down. Ideally, the high available/failover
partners should be sufficiently "separate" that when one fails (because of a hardware, power, networking
failure), the other does not.
•When deploying multiple CPNR VMs on the same physical server (or servers served by a common set
of disk resources), you should stagger the automatic nightly shadow backups (by default, they occur at
23:45 in the server's local time). To know how to alter this time, see the "Setting Automatic Backup
Time" section in Cisco Prime Network Registrar 9.1 Administrator Guide.
It may be acceptable to not follow the above recommendations for lab environments; but they must be
followed for production.
Note
Installation Modes
The modes of installation that exist for the local and regional clusters are new installations and upgrades from
a previous version. These installations or upgrades are performed by using operating system-specific software
installation mechanisms:
•Windows—InstallShield setup program
•Linux—install_cnr script that uses Red Hat Package Manager
License Files
Cisco Prime Network Registrar's license is perpetual and enables specific components. Previously, Cisco
Network Registrar was licensed as a single system with a single license type called ip-node. For Cisco Prime
Network Registrar 9.1, the licensing is done according to the services that you require. The following are the
types of licenses available:
•base-system—Licenses the CCM services. This license is mandatory if you want to run Cisco Prime
Network Registrar.
•base-dhcp—Licenses DHCP/TFTP services and, optionally, an initial count of leases
•base-dns—Licenses authoritative DNS services and, optionally, an initial count of RRs
•base-cdns—Licenses caching DNS services and, optionally, an initial count of servers
Cisco Prime Network Registrar 9.1 Installation Guide
9
Installation Requirements
Recommendations

•count-dhcp—Licenses an incremental number of active leases
•count-dns—Licenses an incremental number of RRs
•count-cdns—Licenses an incremental number of caching server instances
The different services provided by Cisco Prime Network Registrar are associated with the different license
types as follows:
•CCM services—base-system
•DHCP services—base-dhcp and count-dhcp
•Authoritative DNS services—base-dns and count-dns
•Caching DNS services—base-system and base-cdns
Licenses for Cisco Prime Network Registrar 8.x or earlier are not valid for Cisco Prime Network Registrar
9.x. You should have a new license for Cisco Prime Network Registrar 9.x.
Note
You should have at least one base license for a server to enable that service.Note
Cisco Prime Network Registrar IPAM uses a separate license and install process. For more information,
see Cisco Prime Network Registrar 8.3 IPAM Installation Guide.
Note
License management is done from the regional cluster when Cisco Prime Network Registrar is installed. You
must install the regional server first, and load all licenses in the regional server. When you install the local
cluster, it registers with regional to obtain its license.
When you install the regional, you are prompted to provide the license file. You can store the license file in
any location provided the location and file are accessible during the installation.
The utilization of licenses are calculated by obtaining statistics from all the local clusters in the Cisco Prime
Network Registrar system for all counted services (DHCP, DNS, and CDNS). The regional CCM server
maintains the license utilization history for a predetermined time period.
Utilization is calculated for different services as:
•DHCP services—total number of active DHCP leases (including v4 and v6)
•Auth DNS services—the total number of DNS resource records (all RR types)
•Caching DNS services—total number of Caching DNS servers being run in the Cisco Prime Network
Registrar system
The services on each local cluster will be restricted based on the services for which licenses are present.
When you configure DHCP failover, only simple failover is operational and supported (see Failover scenarios
section in the Configuring DHCP Failover chapter of the Cisco Prime Network Registrar 9.1 DHCP User
Guide).
Cisco Prime Network Registrar 9.1 Installation Guide
10
Installation Requirements
License Files

To learn about obtaining the license files for Cisco Prime Network Registrar, see Obtaining Cisco Prime
Network Registrar License Files, on page 14.
Market Segment Specific Licensing
Cisco Prime Network Registrar license types are offered specific to market segments. Market specific licensing
generates license keys for use by market segments, that is, Service Provider, Smart Grid, and so on. Cisco
Prime Network Registrar features are enabled based on the market segment specific license you choose. For
example, the PNR license offers features designed for the Service Provider market segment whereas the
PNR-SG license offers features designed for the Smart Grid market segment.
Cisco Prime Network Registrar offers the following market segment specific licenses:
•Prime Network Registrar—PNR
•Prime Network Registrar Connected Grid—PNR-SG
•Prime IP Express—PNR-ENT
If the licenses for all market segments are installed, then only the PNR license will be active.Note
The regional server which uses the PNR-SG license can be converted to PNR by installing the PNR license.
Local cluster licenses will be converted automatically at the next compliance check, or can be manually
updated by resynchronizing the local cluster.
For a given market segment license, only the counts from corresponding market segment license will apply.
For example, if the PNR count license is applied when the PNR-SG base license is active, the Right to Use
count will not be updated. If the PNR-SG count license is applied when the PNR base license is active, the
Right to Use count will not be updated.
PNR Licenses
The PNR license provides all the features available for the Cisco Prime Network Registrar release you install.
PNR-SG Licenses
The PNR-SG license disables the following PNR features which have been identified as not necessary for
Smart Grid implementations:
•Tenants
•External Authentication
The DHCP service PNR-SG license offers you the PNR features with the exception of:
•Extensions
•Lightweight Directory Access Protocol (LDAP)
•TCP Listeners (client notification)
•Trivial File Transfer Protocol (TFTP)
•Regional lease history
•Regional DHCP utilization history
Cisco Prime Network Registrar 9.1 Installation Guide
11
Installation Requirements
License Files

•BYOD
Prime IP Express—NETREG-ENT
To know the list of features supported by Prime IP Express—NETREG-ENT licenses see IP Express Installation
Guide.
Cisco Prime Network Registrar 9.1 Installation Guide
12
Installation Requirements
License Files

CHAPTER 4
Preparing for the Installation
This chapter covers any tasks that you have to perform before installing Cisco Prime Network Registrar.
•Installation Checklist, page 13
•Before You Begin, page 14
•Obtaining Cisco Prime Network Registrar License Files, page 14
•Running Other Protocol Servers, page 15
•Backup Software and Virus Scanning Guidelines, page 15
•Server Event Logging, page 16
•Modifying ACLs in Windows Installations, page 16
Installation Checklist
This section explains the procedures you must follow to install Cisco Prime Network Registrar.
Before you perform the installation or upgrade, ensure that you are prepared by reviewing this checklist:
Table 2: Installation Checklist
CheckoffTask
☐
Does my operating system meet the minimum requirements to support Cisco Prime Network
Registrar 9.1? (See the System Requirements, on page 7 section.)
☐
Does my hardware meet the minimum requirements? (See the System Requirements, on page 7
section.)
☐
If necessary, have I excluded Cisco Prime Network Registrar directories and subdirectories from
virus scanning? (See the Backup Software and Virus Scanning Guidelines, on page 15 section.)
☐
On Windows, are other applications closed, including any virus-scanning or automatic-backup
software programs? Is the Debugger Users group included in the Local Users and Groups?
Cisco Prime Network Registrar 9.1 Installation Guide
13

CheckoffTask
☐
Do I have the proper software license? (See the License Files, on page 9 section.)
☐
Am I authorized for the administrative privileges needed to install the software?
☐
Does the target installation server have enough disk space?
☐
Is this a new installation or an upgrade?
☐
Is the cluster mode of operation regional or local?
☐
Is this a full or client-only installation?
☐
Is the Java Runtime Environment (JRE) 1.7 or later, or the equivalent Java Development Kit (JDK),
installed on the system? If so, where?
☐
Should the web UI use an HTTP or HTTPS connection, or both?
☐
Am I upgrading from an earlier version of Cisco Prime Network Registrar? If so:
☐
Are there any active user interface sessions?
●
☐
Is my database backed up?
●
☐
Am I upgrading from a supported version (Cisco Prime Network Registrar 7.2 and later)?
●
Before You Begin
Verify that you are running a supported operating system and that your environment meets all other current
system requirements (see System Requirements, on page 7).
To upgrade the operating system:
1Use the currently installed Cisco Prime Network Registrar release to complete any configuration changes
in progress, so that the existing database is consistent before you perform the upgrade.
2Back up your database. The installation program tries to detect configuration data from an earlier installation
and will upgrade the data.
3Upgrade your operating system.
Obtaining Cisco Prime Network Registrar License Files
When you purchase Cisco Prime Network Registrar 9.1, you receive a FLEXlm license file in an e-mail
attachment from Cisco, after you register the software.
You must copy the license file to a location which will be accessible during the regional cluster installation
before you attempt to install the software. The installation process will ask you for the location of the license
file.
Cisco Prime Network Registrar 9.1 Installation Guide
14
Preparing for the Installation
Before You Begin