Cisco Prime Network Registrar 8.3 Administration Guide
- Updated:
- March 6, 2018
Chapter: Introduction to Cisco Prime Network Registrar Virtual Appliance
Introduction to Cisco Prime Network Registrar Virtual Appliance
The Cisco Prime Network Registrar virtual appliance aims at eliminating the installation, configuration and maintenance costs associated with running Cisco Prime Network Registrar on a local system. It also guarantees portability and thus reduces the risk in moving Cisco Prime Network Registrar from one machine to another.
You must get a license of Cisco Prime Network Registrar virtual appliance, and download the virtual appliance from Cisco.com. Upon initializing the virtual appliance, you have to add the license file. Cisco Prime Network Registrar will then be up and running, available to be configured. This is applicable for both the local and regional appliance.
This is different from just downloading a copy of Cisco Prime Network Registrar and installing it on a server or virtual machine provided by the customer, in that the operating system on which Cisco Prime Network Registrar runs is also provided in the virtual appliance.
The Cisco Prime Network Registrar virtual appliance supports VMware ESXi 5.0 or later platforms.
To know about the difference between vApp and a virtual appliance, see the User’s Guide to Deploying vApps and Virtual Appliance s.
- How the Cisco Prime Network Registrar Virtual Appliance Works
- Invoking Cisco Prime Network Registrar on the Virtual Appliance
- Monitoring Disk Space Availability
- Increasing the Size of Disk
- Troubleshooting
How the Cisco Prime Network Registrar Virtual Appliance Works
The virtual appliance consists of a virtual machine in the OVF format, which contains a runnable guest OS (CentOS 7.4 in CPNR 8.3.6 and CentOS 6.x in pre-8.3.6 releases) and Cisco Prime Network Registrar installed on that OS. When the virtual appliance is installed, Cisco Prime Network Registrar is already installed and is started by the virtual machine power-up like in the case of any regular server power-up.
How to Download the Cisco Prime Network Registrar Virtual Appliance
Do the following to download the Cisco Prime Network Registrar virtual appliance:
Invoking Cisco Prime Network Registrar on the Virtual Appliance
You can invoke the Cisco Prime Network Registrar application directly by using the URL http://hostname:8080. The secure https connection is also available via the URL https://hostname:8443.
Monitoring Disk Space Availability
To view the disk space availability, do the following:
Monitoring Disk Space Availability (Using the Console)
To monitor the disk space availability using the console, do the following:
| Step 1 | Select the virtual machine in the vSphere Client window and either click the Console tab on the right pane or right-click the virtual machine name and choose Open Console. |
| Step 2 | Log in as
root and type df -k. The disk space details are displayed.
If the disk space on the disk mounted on /var/nwreg2 is not enough, then you should increase the size of the disk (see Increasing the Size of Disk). |
Increasing the Size of Disk
The cnr_growfilesystem script causes the data partition, /dev/sdb1 to grow to be the size of the entire data disk. It is trivial to expand the size of the data disk that the operating system sees, using VMware. To ensure that the operating system recognizes the bigger disk, you have to restart the VM and run the cnr_growfilesystem after increasing the size of the disk.
 Note | Before running the cnr_growfilesystem script, ensure that you backup the entire /var/nwreg2/ data and that it is not stored anywhere in the file system under /var/nwreg2. Running the cnr_growfilesystem script after restarting the VM ensures that the filesystem uses all the space in the partition. |
If you need a bigger disk, do the following:
Troubleshooting
If you experience any issues while working with the Cisco Prime Network Registrar virtual appliance, we recommend you to do the following:
Examine the log files in /var/nwreg2/{local | regional}/logs. Look particularly for errors in the log files as these signal exceptional conditions. If you are unable to resolve the problem and you have purchased Cisco support, then submit a case to Cisco Technical Assistance Center (TAC) regarding the problem.
Feedback