Step 1 Log in to your vSphere Client:
a. Open the VMWare vSphere client application on your desktop.
b. Connect to the vCenter Server with your vCenter user credentials.
Note You cannot deploy the OVA by connecting the vSphere Client directly to the ESXi server.
Step 2 Use the vSphere Client to access the OVF template:
a. Choose Home > Inventory > Hosts and Clusters .
b. Choose the host on which the OVF template will be deployed.
c. Choose File > Deploy OVF Template to open the Deploy OVF Template window.
Step 3 Choose the Source location:
a. Click the Browse button.
b. Locate the dcnm.ova file that you downloaded to your computer and click Next.
Step 4 Review the OVF Template Details and click Next .
Some of the details about the Cisco DCNM virtual appliance include:
- Version number
- Download size
- Size on disk:
– Thin provision for the amount of disk space consumed by the virtual appliance immediately after deployment. It is the minimum amount of disk space needed to deploy the virtual appliance.
– Thick provision for the maximum amount of disk space the virtual appliance can consume.
Note For more information on thick and thin provision, see Choose the disk format.
Step 5 Read and accept the End User License Agreement and click Next.
Step 6 Specify the name and location of the Cisco DCNM OVA.
a. In the Name box, enter a name for the virtual appliance. This name is not the hostname, but the name of the virtual appliance hardware and is specific to the vSphere infrastructure.
The name can contain up to 80 alphanumeric characters and must be unique within the Inventory folder.
b. In the Inventory Location tree, choose the folder location for the virtual appliance.
c. Click Next .
Step 7 Choose the deployment configuration:
- Choose Small to configure the virtual machine with two vCPUs and 8G RAM.
- Choose Large to configure the virtual machine with four vCPUs and 12G RAM.
Note We recommend that you use a Large deployment configuration when you are managing more than 50 devices (and up to the upper limit of the Cisco DFA fabric) to leverage better RAM, heap memory, and CPUs.
For setups that could grow, you should choose Large.
Choose Small for proof-of-concept and other small-scale environments with fewer than 50 switches that are not expected to grow with time.
Step 8 Click Next .
Step 9 Specify the host and click Next.
Note A host will not be available if you already selected a host in the vSphere Client before you deploy the OVA.
Note The OVA should not be deployed under a vApp.
Step 10 Choose the a destination storage for the virtual machine files and click Next.
Step 11 Choose the disk format.
- Choose one of the thick provision types if you have enough storage capacity as required by the virtual appliance and want to set a specific allocation of space for the virtual disks:
– Thick Provision Lazy Zeroed : The space that is required for the virtual disk is allocated when the virtual disk is created. The data that remains on the physical device is not erased when the virtual disk is created but is zeroed out on demand at a later time on first write from the virtual disk.
– Thick Provision Eager Zeroed : The space that is required for the virtual disk is allocated when the virtual disk is created. Unlike the Lazy Zeroed option, the data that remains on the physical device is erased when the virtual disk is created.
- Choose Thin Provision if you have less than 100 GB of disk space available. The initial disk consumption will be 2.8 GB and will increase as the size of the database increases with the number of devices being managed.
Step 12 Click Next.
Step 13 Choose your network mapping.
a. The dcnm-mgmt network provides connectivity (ssh, scp, http, https) to the Cisco DCNM OVA. In the Destination Network column, associate the network mapping with the port group that corresponds to the subnet that is associated with the Cisco DCNM management network.
b. Map the enhanced-fabric-mgmt network to the port group that connects to the management network of switches.
Note If you are deploying more than one OVA for HA functionality, you must meet the following criteria:
- Both OVAs should have their management access (eth0) and enhanced fabric management (eth1) interfaces in the same subnet.
- Both OVAs should be deployed with the same administrative password. This is to ensure that both OVAs are duplicates of each other for application access.
Step 14 Click Next.
Step 15 Choose the Cisco DCNM OVA Properties.
a. The Application Management check box is selected by default to install applications related to DFA.
DFA includes implementations for the following protocols:
DFA includes implementations for the following repositories:
b. In the Management Properties section, enter a password in the Enter Password and Confirm Password boxes to establish the password that will be used to connect all applications in the DCNM OVA.
Note The password must be at least eight characters long and must contain at least one alphabetic and one numeric character. It can contain the only the following special characters: .(dot), + (plus), _ (underscore), and - (hyphen).
If you do not comply with these password requirements, you can continue with the OVA deployment; however, you subsequently may not be able to log in to other applications like DCNM.
c. In the DCNM Network section, complete each of the required fields:
– Hostnam e (should be a fully qualified domain name, otherwise you may encounter issues when using the XMPP application after deployment)
– IP Address (for the outside management address for DCNM)
– Subnet Mask
– Default Gateway
– DNS IP
d. In the Enhanced Fabric Management section, complete each of the required fields:
– IP Address (for the inside fabric management address or OOB Management Network)
– Subnet mask
– DNS IP
Step 16 Click Next
Step 17 Review each of the deployment settings that you have established. Press the Back button to go to any settings if you want to change them.
After you have reviewed each of the deployment settings in the OVF template, perform the following procedure to deploy the virtual machine.
Deploying Virtual Machines
Step 1 Check the Power on after deployment check box.
Step 2 Click the Finish button.
A Deploying DNCM_OVA window appears and the OVA deployment starts and requires some time to complete.
Note The time for the OVA deployment could take 5 to 6 minutes (or more) depending on the network latency.
After the OVA is deployed, a Deployment Completed Successfully message appears.
Step 3 On the Summary tab in the vSphere Client, review the information about the VM and make note of the IP address.
Step 4 Check the console of the VM in the vSphere Client for the login prompt. Once the login prompt appears, log in with root credentials and use the appmgr status all command to check the status of the applications. After all applications are up and running, go to the next step.
Note For more information about verifying application status see the Verifying the Application Status after Deployment.
Step 5 Log in to the Cisco DCNM web UI:
a. Put the IP address in your browser.
The Cisco Prime Data Center Network Manager window is displayed.
b. In the User Name field, enter admin.
c. In the Password field, enter the administrative password given to you during the OVA deployment.
Note If you are deploying multiple OVAs for HA functions, you should deploy both the OVAs with the same administrative password. This action ensures that both OVAs are duplicates of each other for application access.
You are ready to begin POAP configuration and Device Discovery.
NoteSee the DCNM 7.0 Fundamentals Guide for configuration information.