Cisco IoT FND Deployment on an Open Virtual Appliance, VMware ESXi 5.5/6.0

Cisco IoT FND Deployment on an Open Virtual Appliance, VMware ESXi 5.5/6.0

This chapter provides an overview of the steps required to install the Cisco IoT Field Network Director (Cisco IoT FND) Release 4.3 or greater application within Open Virtual Appliance (OVA) software, VMware ESXi versions 5.5 or 6.0. The same instructions work for both versions.


For an overview of the features and functionality of the IoT FND application and details on how to configure features and manage the Cisco IoT Field Network Director after its installation, refer to Cisco IoT Field Network Director User Guide, Release 4.8.x.

Installing VMware ESX 5.5 or 6.0 on a Server

You use the VMware vSphere client to import OVA files into ESXi 5.5 and ESXi 6.0.

Log in to the VMware vSphere 5.5 or 6.0 client via a web browser with your user credentials (username and password).

Your IT admin can provide you the IP address to the VMware ESXi server.

If you are installing the VMware ESXi server software yourself, please go to the VMware ESXi site to download the software:

  • Install the VMware vSphere Client for the ESXi 5.5 or 6.0 server.

  • Locate the VMware credentials to create virtual machines in ESXi 5.5. or 6.0, respectively.

  • Ensure that you meet the VMware server machine requirements.

Listed below are the VM CPU and memory requirements for a small scale deployment:

  • 16 GB memory

  • 1 core and 4 virtual sockets

  • 150 GB of virtual storage

To import the IoT FND open virtual appliances (OVA) into ESXi 5.5 or ESXi6.0 using VMware vSphere Client version 5.5 or 6.0, respectively:


Step 1

Select the Network Adapter > NAT setting for the server.

Step 2

At the VMware vSphere Client window enter the IP address, username, and password of the server where VMware resides.

Step 3

Click Login.

Figure 1. VMware vSphere log in screen
Step 4

Select File > Deploy OVF Template... (see Deploy New Template)

Figure 2. Deploy New Template
Step 5

Browse to an OVF package from the Internet or a file accessible from your computer (for example, iot-fnd- See Deploy OVF Template.

Figure 3. Deploy OVF Template
Step 6

Ensure that the correct OVA file (or URL) displays in the Source location window, and then click Next.

Step 7

OVF Template Details page displays again with the following information for planning purposes (OVF Template Details Page Noting Download File Size and Provision File Sizes)

  • Product name: iot-fnd <-- default

  • File download size: 3.0 GB

  • Size on disk: 957.1 GB (Thick Provision Lazy Zeroed), 600 GB (Thick Provisioned) or 6.2 GB (Thin Provisioned)

Select one of the options above later in the install process.

Figure 4. OVF Template Details Page Noting Download File Size and Provision File Sizes
Step 8

Note the storage requirements (Size on Disk) for Thin and Thick Provisioning, click Next.

Figure 5. Define a name for the Deployment Template
Step 9

You may keep the default name of the template or enter a new name (up to 80 characters). A suggested name is to enter the Name and Inventory Location of the deployed template (for example, iot-fnd).

Be sure that the name you select is a unique name within its destination folder. Click Next.
In the next window that appears, verify the OVA filename matches what you entered in the previous window. If no issues, click Next. If the OVA filename does not match, click Back and reenter the information.
Figure 6. Select Storage Location for Virtual Machine Files
Step 10

Select a storage location for the virtual machine files from the listed options (example: datastore1).

Note: If the selected storage location does not have sufficient storage for the largest file installation option, a message displays noting insufficient storage. This message appears before you select the provisioning type, so you can locate a storage resource with greater capacity if you want to support Thick provisioning (600 GB) as shown in this example.


Thin Provision allows the VM disk to grow as needed.

If no warning message appears, click Next. Go to Step 11.

If a warning message does appear and you want to use Thick Provisioning, select another server that has sufficient storage then click Next. Go to Step 11.

Figure 7. Select Provisioning Type
Step 11

After selecting a Datastore successfully, select the Provisioning type. Click Next.

Figure 8. Network Mapping
Step 12

Map the networks in the OVF template to a source and destination network within the inventory. Click Next.

Figure 9. Final Review: Ready to Complete
Step 13

At the Ready to Complete window, do a final review of the Ready to Complete window:

  1. If you want to change any settings, use the Back button to parse back through the windows and save your changes. After making your changes, parse forward through the windows until you reach the Ready to Complete window. Click Finish To power on the Virtual Machine immediately after deployment completes, select the Power on after deployment box. Click Finish.To complete the deployment process without powering on after the deployment, click Finish.

  2. If you do not want to change any settings, click Finish.

Step 14

After completion of the IoT-FND 4.3 install, the Deployment Completed window displays.

IoT FND is now fully setup. You can log in with your new credentials and configure IoT FND to manage your network.

Figure 10. Deployment Completed
Step 15

After completion of the install, a window displays.

  1. In the left panel, select the IoT FND machine name.

  2. In the right panel, Under Basic Task, select Edit virtual machine settings to confirm CPU and MEM settings.

  3. Click OK to close the window.

Figure 11. FND Virtual Machine
Step 16

In IoT FND Virtual Machine, Under Basic Tasks, click Power on the virtual machines and select the Console tab in the window that opens. The console opens showing possible RHEL server versions to select.

Figure 12. VM Console Window
Step 17

After you select a RHEL option, you will be prompted for your username and password.

Step 18

Click Sign In and select the GNOME Classic option.

Figure 13. Log in Window
Step 19

Click Sign In.

Step 20

At the Welcome screen, select the default language (such as English-United States) for the interface, Click Next.

Step 21

Continue through the install script until you reach the final screen that indicates that “Your computer is ready to use.” Click Start using Red Hat Enterprise Linux Server button.

Step 22

Close Getting Started window, right-click to open.

Step 23

At the Application Places window, right-click in the window to display a menu panel. Select Open in Terminal.

  1. Open a browser window and enter the IP address for your IoT FND application using your credentials (Log in Window for IoT FND 4.3)

Figure 14. Log in Window for IoT FND 4.3
Step 24

You are prompted to reset your password.


After you complete the password reset, IoT FND 4.3 is fully deployed.

  1. You can log in with your new credentials and configure IoT FND to manage your network.

  2. Please add the following property in cgms.properies file: googleMapsClientId=gme-ciscosystemsinc2

  3. Restart IoT FND services.

  4. Send the IoT FND server ip/fqdn to to register it for Google Maps access.