Cisco Prime Network Registrar IPAM OVA 8.3 Quick Start Guide

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Prime Network Registrar IPAM OVA 8.3 Quick Start Guide

Chapter Title

Installing Cisco Prime Network Registrar IPAM 8.3

Results

Updated:
September 14, 2016

Chapter: Installing Cisco Prime Network Registrar IPAM 8.3

Installing Cisco Prime Network Registrar IPAM 8.3

This chapter contains the following sections:

Before You Begin

Cisco Prime Network Registrar IPAM is licensed separately from Cisco Prime Network Registrar DHCP, DNS, and Caching DNS. After deploying IPAM OVA, you will be asked for a separate license key to access the application. Note that IPAM 8.3 requires a separate license key and the license keys of previous versions cannot be used.

System Requirements

The memory and storage parameters are specified in the OVA file. However, you should ensure that sufficient resources are available on the host that you are targeting for the deployment to meet these requirements.

The OVA deployment allocates 4 GB of RAM to the virtual appliance. In addition, you will almost certainly find that you also will need disk space beyond the 10 GB minimum allocation provided when the virtual appliance is installed. It is possible to expand the disk usage after the virtual appliance is installed.


Note

It is worth some effort to determine the likely amount of disk storage that you need at the time you first install the virtual appliance. If you increase the size of the disk space after you have configured and used the product, you must back up all the work that you have done prior to increasing the disk storage. However, if you increase the disk storage when you first install the product, no backup is necessary, since in the unlikely event something goes wrong while expanding the disk storage, nothing valuable would be lost. At worst, you would simply have to reinstall the virtual appliance.

The Cisco Prime Network Registrar IPAM 8.3 virtual appliance is supported on VMware ESXi 5.0 or later and later systems that are themselves supported ESXi 5.0 or later systems. You can run ESXi on hardware systems that do not meet the minimum support requirements for ESXi 5.0 or later. VMware provides a bootable program which helps you identify whether the hardware on which it is run supports ESXi 5.0 and later. In some cases, the capabilities that are not available from ESXi 5.0 or later are capabilities that are required to run the Cisco Prime Network Registrar IPAM 8.3 virtual appliance. For example, ESXi 5.0 or later will run on some hardware on which it is not officially supported, and will run only 32 bit operating systems on that hardware. The Cisco Prime Network Registrar IPAM 8.3 virtual appliance consists of a 64 bit Linux operating system running a 32 bit version of the Cisco Prime Network Registrar IPAM application. Thus, the 64 bit OS included with the virtual appliance will not run on the ESXi 5.0 or later platform described above. The hardware platforms on which ESXi 5.0 or later runs in this degraded and unsupported mode are becoming less common over time.

Installing Cisco Prime Network Registrar IPAM 8.3 Virtual Appliance

The Cisco Prime Network Registrar IPAM virtual appliance is supported for production use on VMware ESXi 5.0 or later and can be accessed or managed using vSphere client of VMware. The Cisco Prime Network Registrar IPAM virtual appliance is installed using the Open Virtual Appliance (OVA) package.

The VMware vSphere client can be connected directly to your ESXi server/host, or it can be connected to a vCenter server which in turn is connected to your vSphere installation. Connecting through vCenter provides a number of capabilities that connecting directly to ESXi does not. If a vCenter server is available and associated with the ESXi server/host, it should be used.

Preparing to Deploy the Cisco Prime Network Registrar IPAM 8.3 Virtual Appliance

In order to deploy the Cisco Prime Network Registrar IPAM 8.3 virtual appliance and configure its network connection, you have to answer several questions. Some of these questions concern the networking environment in which the virtual appliance is being deployed, and some of them concern values which are unique to the particular virtual appliance being deployed.

The questions that are unique to the installation of this particular virtual appliance are listed below. You must decide on answers to these questions before you deploy the virtual appliance.

  • A virtual machine name for the deployed virtual appliance.

  • A root password for the underlying Linux CentOS operating system.

  • An IPv4 address for the virtual appliance.

  • A DNS name associated with the IPv4 address of the virtual appliance.

The questions concerning the networking environment are as follows. The answers to these questions are not unique to the virtual appliance, but are instead values that are determined by the environment in which you will deploy the virtual appliance:

  • The IP address or DNS name of the ESXi server/host on which you intend to deploy the virtual appliance.

  • The IP address or DNS name of any vCenter server associated with the ESXi server/host, above.

  • The IP address of the virtual appliance itself.

  • The network mask associated with the IP address of the virtual appliance itself.

  • The default gateway address for the virtual appliance.

  • The IP address of at least one DNS server that can be accessed by the virtual appliance, although it is best if you have the IP address of two DNS servers to provide additional availability.

  • Any proxy values necessary for the virtual appliance to access the Internet (if you want the virtual appliance to have access to the Internet).

Deploying the Cisco Prime Network Registrar IPAM 8.3 OVA


Note
Before deploying the virtual appliance, verify that your VMware server is running on VMware supported hardware. If you are not sure whether your environment can support a 64-bit guest operating system, you can verify by downloading and running the VMware "CPU Identification Utility" which indicates 64-bit VMware support. This utility can be found on the VMware site at: http:/​/​www.vmware.com/​download/​shared_​utilities.html

To install the Cisco Prime Network Registrar IPAM 8.3 virtual appliance, you must first download the correct installation file. There will be only one "Cisco Prime Network Registrar IPAM OVA" file, which is an OVA file and can be deployed without having to unzip.

The file name is:

  • cpnr_8_3_ipam.ova.

Download the ova file from www.cisco.com and follow the steps given below.

Using vSphere, connect directly to the ESXi server/host or the vCenter server, and select the ESXi server/host where the OVA is to be deployed.

If you have a vCenter server available, you can connect the ESXi hypervisor to your existing vCenter server and manage it through that vCenter server. Managing all your VMware hypervisors through a common vCenter server provides many benefits.

The screens that you see while managing the ESXi hypervisor with a vSphere client through a vCenter server are different from the screens that you see while connecting the vSphere client directly to the ESXi hypervisor. You can see additional screens if connected through vCenter server. These screens do not actually provide any benefit for the operations in which you will engage to deploy the Cisco Prime Network Registrar IPAM 8.3 virtual appliance. The benefits to using the vCenter server approach come after the initial deployment of the virtual appliance.

Follow the steps below to deploy IPAM OVA:

    Step 1   From vSphere menu, choose File > Deploy OVA Template.

    The Deploy OVA Template Source window appears.

    Step 2   To import the OVA file from hard disk, click Browse and choose the OVA file (.ova) available in the local machine where the vSphere is running, usually cpnr_8_3_ipam.ova. You can also enter a URL to download and install the OVA package from the internet.
    Step 3   Click Next.

    The OVA Template Details window appears. It displays the product name, the size of the OVA file, and the amount of disk space that needs to be available for the virtual appliance.

    Step 4   Verify the OVA template details and click Next.
    Step 5   The Name and Location window appears.
    Step 6   Enter the name of the new virtual appliance. If you are using the vCenter to manage the virtual machine, then you have the option of selecting the location of the inventory too. Click Next to continue.

    The default name is generic. You may want to change it to something more specific, such as Cisco Prime Network Registrar IPAM 8.3.

    Note   

    You can change the name of the virtual machine running the virtual appliance after the virtual appliance is deployed. However, while the name of the virtual machine will change, the original name (entered in Step 6) continues to be used as the location of the disk files that describe the virtual machine. Thus, confusion may arise in the future as whatever name you enter on this page remains for the life of the virtual machine and the virtual machine name and the disk file names will differ. Thus, choosing a descriptive name now that you will not need to change later will provide some benefits in maintainability of this installation.

    If you are using the vCenter to manage the virtual machine, then the Host/Cluster window appears. Go to Step 7.

    If you are managing the ESXi host directly, then the Disk Format window appears. Go to Step 8.

    Step 7   Choose the destination host on which you want to deploy the virtual machine and click Next.

    The Disk Format window appears.

    Step 8   The Thick provisioned format is selected by default. Click Next to continue.
    Note   

    The virtual appliance is only supported when deployed with thick provisioning.

    If you are using the vCenter to manage the virtual machine, then the Network Mapping window appears. Go to Step 9.

    If you are managing the ESXi host directly, then the Ready to Complete window appears. Go to Step 12.

    Step 9   To map the networks used in this OVA template to the networks in your inventory, select the current destination network and choose the destination network from the Destination Networks drop-down list. Click Next.

    The Properties window appears.

    Step 10   Enter the required values for Default Gateway, DNS, Network 1 IP Address, and Network 1 Netmask.
    Note    You should not enter the root password in this window.
    Step 11   Click Next.

    The Ready to Complete window appears.

    Step 12   Review the setting details of your deployment and click Finish to complete the deployment.

    In this configuration, the host name of the virtual appliance is created by default after the appliance.

    Booting and Configuring Cisco Prime Network Registrar IPAM 8.3 Virtual Appliance

    To boot and then configure the Cisco Prime Network Registrar IPAM virtual appliance:

      Step 1   After deploying the Virtual Appliance OVA, select the virtual machine name in vSphere, right-click on it and select Open Console.
      Step 2   Click the Power on button on the console and click in the window after clicking the Power on button.

      During the initial boot of the newly deployed machine, you will be prompted to enter a root (system) password, which is not the Cisco Prime Network Registrar IPAM application password. Before prompting to enter the root password, the end user agreement will be displayed and the user to type y or n after reading it.

      Note   

      This is the root password for the underlying Linux operating system on which the Cisco Prime Network Registrar IPAM 8.3 application is installed. You will be asked to enter this password twice. You will need root access to the underlying Linux operating system at various times in the future, so make sure that you remember this password.

      The boot process takes a little while, both before you are asked for a root password, as well as after you enter the root password. Then the console will display the configuration window. After setting the root password, a message will be displayed to execute the configurenetwork script to configure the network and one more script called configureipam.

      If you are managing the ESXi hypervisor with a vSphere client through a vCenter server, then the configuration window displays the networking values you configured while deploying the OVA and you can skip Step 3.

      If you are managing the ESXi host directly, then go to Step 3.

      Step 3   Execute the command "configurenetwork" to configure the network settings. You must configure the virtual appliance to use a static address.

      • IP Address of the virtual appliance

      • Netmask of the virtual appliance

      • Gateway of the network in which you are creating virtual appliance

      • DNS Server 1

      • DNS Server 2

      • Hostname of the virtual appliance

      • Whether or not you need a proxy set

      Step 4   To save the settings, select y (Yes) when prompted, after reviewing the settings. Select n (No) if you do not want to save the settings.
      Step 5   Type exit to exit the configurenetwork application and the system settings will be changed with the values you entered.
      Step 6   Proceed by executing the configureipam script. This script requires no input but is based on the values used in the configurenetwork step. Be sure to run configurenetwork before attempting to run configureipam.
      Note    You must run configureipam script to make IPAM work.

      Was this Document Helpful?

      FeedbackFeedback

      Contact Cisco