Installing Cisco Prime Network Registrar
Note |
If using the Authoritative or Caching DNS server, assure that connection tracking (conntrack) is not being used. For more information, see the "Firewall Considerations" section in Cisco Prime Network Registrar 9.0 Administration Guide. |
Procedure
Step 1 |
Log into the target machine using an account that has administrative privileges:
Windows—Close all open applications, including any antivirus software. |
||||||
Step 2 |
Download and install the Java Runtime Environment (JRE) 1.7 or later, or the equivalent Java Development Kit (JDK), if you have not already done so. These are available from the Oracle website.
|
||||||
Step 3 |
If you are not configuring secure login to the web UI, skip to Step 4. If you are configuring secure login, you must create a keystore file by using the Java keytool utility, which is located in the bin subdirectory of the Java installation (see Step 2). Use the utility to define a self-signed certificate, or to request and later import a certificate from an external signing authority:
|
||||||
Step 4 |
Load the installation CD, or browse to the network resource where the Cisco Prime Network Registrar software is located. If you download a distribution file from the Cisco website, run it from a different directory than where you will install Cisco Prime Network Registrar.
|
||||||
Step 5 |
Specify whether you want to install Cisco Prime Network Registrar in the local or regional cluster mode (see About Cisco Prime Network Registrar):
|
||||||
Step 6 |
On Linux, specify if you want to run Cisco Prime Network Registrar Local Server Agent as a non-root nradmin user. If you choose to run Cisco Prime Network Registrar for a non-root user, a user nradmin is created with the requisite privileges to run the Cisco Prime Network Registrar services. When running Cisco Prime Network Registrar as a non-root user (nradmin), some changes occur in the CLI operation of the product . Though it is still possible to run as root, it is not recommended. Instead, create regular Linux users and add them to the nradmin group. Users in this group will have full access to the Cisco Prime Network Registrar files. To start and stop Cisco Prime Network Registrar, these users may use the new ‘cnr_service program in the path which is in <install directory>/bin/cnr_service).
|
||||||
Step 7 |
Note these Cisco Prime Network Registrar installation default directories and make any appropriate changes to meet your needs:
Windows default locations:
Linux default locations:
|
||||||
Step 8 |
If there are no defined administrators, create an administrator by providing the username and password. You have to confirm the password entered. If you are installing a regional, continue; else go to Step 10. |
||||||
Step 9 |
Enter the filename, as an absolute path, for your base license see the "License Files" section.
Entering the filename during installation is optional. However, if you do not enter the filename now, you must enter it when you first log into the web UI or CLI.
|
||||||
Step 10 |
Register the local to the regional by providing the regional IPv4 or IPv6 address and SCP port. After the local is registered to the regional, it can provide those services for which the licenses are present in the regional.
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. |
||||||
Step 11 |
After you register local to the regional, you can select the required services from the licensed services.
|
||||||
Step 12 |
Choose whether to archive the existing binaries and database in case this installation does not succeed. The default and recommended choice is Yes or y: If you choose to archive the files, specify the archive directory. The default directories are:
|
||||||
Step 13 |
Choose the appropriate installation type: server and client (the default), or client-only:
|
||||||
Step 14 |
Enter CCM management SCP port number that the server agent uses for internal communication between servers. The default value is 1234 for local cluster and 1244 for regional cluster. |
||||||
Step 15 |
Enter the location of the Java installation (JRE) 1.7 or JDK selected in Step 2. (The installation or upgrade process tries to detect the location.):
|
||||||
Step 16 |
Choose whether to enable the web UI to use a nonsecure (HTTP) or secure (HTTPS) connection for web UI logins:
Enabling the secure HTTPS port configures security for connecting to the Apache Tomcat web server (see Step 3 for configuration). (To change the connection type, rerun the installer, and then make a different choice at this step.)
|
||||||
Step 17 |
If you enabled HTTPS web UI connectivity, you are prompted for the location of the necessary keystore and keystore files:
|
||||||
Step 18 |
Enter a port number for the web UI connection. The defaults are:
On Windows, click Next. |
||||||
Step 19 |
Choose Yes if you want to enable the Cisco Prime Network Registrar web services. |
||||||
Step 20 |
Select the security mode to be configured. Optional. Allow fallback to unsecure connection is selected by default. Click Next. |
||||||
Step 21 |
If you are installing a regional, select Yes to enable BYOD service.
The Cisco Prime Network Registrar installation process begins. Status messages report that the installer is transferring files and running scripts. This process may take a few minutes:
|
||||||
Step 22 |
Verify the status of the Cisco Prime Network Registrar servers:
If the upgrade fails, you can revert to the earlier Cisco Prime Network Registrar version. For details about reverting to the earlier version, see the Reverting to an Earlier Product Version. |
Upgrading on Windows
To upgrade to Cisco Prime Network Registrar 9.0:
Procedure
Step 1 |
Ensure that your environment meets the current system requirements (see System Requirements). |
||
Step 2 |
Use the currently installed release to complete any configuration changes in progress, so that the existing database is consistent before you perform the upgrade. |
||
Step 3 |
Uninstall the previous version of Cisco Prime Network Registrar. Your existing configuration data will remain in place after the uninstall. |
||
Step 4 |
Back up your Cisco Prime Network Registrar data on a different machine or a shared network device and upgrade your operating system to Windows Server 2012 R2. See documentation supplied by Microsoft for information about how to install/upgrade Windows servers.
|
||
Step 5 |
Install Cisco Prime Network Registrar 9.0 on the Windows Server 2012 R2 machine. For installation instructions, see Installing Cisco Prime Network Registrar. Ensure that you specify the path where your existing data can be found, for example, C:\NetworkRegistrar\{Local | Regional}, to run the upgrade.
We recommend upgrading the regional cluster before upgrading any local clusters, because an older version of a regional cluster cannot connect to newer local clusters. |
Upgrading on Linux
To upgrade to Cisco Prime Network Registrar 9.0:
Procedure
Step 1 |
Ensure that your environment meets the current system requirements (see System Requirements). |
Step 2 |
Use the currently installed release to complete any configuration changes in progress, so that the existing database is consistent before you perform the upgrade. |
Step 3 |
Stop the Cisco Prime Network Registrar server agent and backup the current system (or at least the Cisco Network Registrar\Program Files\Network Registrar\ directories and contents). To stop the Cisco Prime Network Registrar Local/Regional server agent:
|
Step 4 |
Install Cisco Prime Network Registrar 9.0. For installation instructions, see the section "Installing and Upgrading Cisco Prime Network Registrar". |