Deploy Cisco IoT FND OVA on VMware ESXi

Here are the instructions to install Cisco IoT FND Release 5.x.x or later releases with an Open Virtual Appliance (OVA) software on VMware ESXi 7.x or 8.0 versions.

 Note
For an overview of the features and functionality of the Cisco 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 5.0 .

Install and set up VMware ESXi for Cisco IoT FND OVA deployment

This task outlines the installation of VMware ESXi 7.x or 8.0 on a server and the deployment of the Cisco IoT FND 5.x.x OVA.

Step 1

Verify that your VMware ESXi server meets the minimum hardware and system resource requirements as listed in the table. These specifications apply to both VMware ESXi 7.x and 8.0 versions.

VMware ESXi Server Requirements

Resources

Minimum Requirements

Memory

32 GB

vCPUs

4

Hard Disk

450 GB

Step 2

Install and set up VMware ESXi. For more information, refer to Installing and Setting Up ESXi for 7.x version and Installing and Setting Up ESXi for 8.0 version.

Step 3

Log in to the ESXi server (7.x or 8.0) by entering its IP address in a web browser and authenticating with your ESXi credentials.

Step 4

Deploy the Cisco IoT FND 5.x.x OVA on VMware ESXi. For instructions to deploy OVA, refer to Deploy an OVF or OVA Template for ESXi version 7.x and Deploy an OVF or OVA Template for ESXi version 8.0.

 Note
  • In the Select OVF and VMDK files tab, enter a name for the VM and search for an OVF package which is available on the internet or as a file accessible from your computer (for example, iot-fnd-5.0.0-40.ova) and then click Next.
  • If the warning message “Failed: Access to resource settings on the host is restricted to the server that is managing it [vCenter Server IP]” appears during deployment, then cancel the current upload, disconnect the ESXi host from the vCenter Server by selecting Actions > Disconnect from vCenter Server, and then re‑upload the OVA file.

Step 5

After the Cisco IoT FND VM is deployed, select the VM from the left pane in ESXi to view its details.

This completes the installation and deployment of the VM.

Access the Cisco IoT FND using the RHEL console

This task provides steps to access the newly deployed Cisco IoT FND 5.x.x using the RHEL console.

Step 1

After the Cisco IoT FND VM is deployed in ESXi, log in as root user to access the RHEL console.

 Note
  • To access the console, enter the username and password as given:
    • Username: root
    • Default Password: C!sco123
  • Password must be changed mandatorily after accessing the console.
  • If you want to reset the default password, then the following conditions apply:
    • The password must be at least 8 characters in length,
    • The password must have at least 1 uppercase character,
    • The password must have at least 1 lowercase character,
    • The password must have at least 1 special character,
    • The password must have at least 1 digit,
    • The password cannot be the same as any of the previous 5 passwords used.
  • After you enter the default password, the prompt for re-setting your password will appear.
 Note

Before accessing the root credentials, use the following credentials to access SSH after installing OVA. The existing credentials for username and password are disabled for 4.12 and later releases:

  • Username: fnduser
  • Password: C!sco123

Step 2

Reset the default root password using the password re-setting option. After you complete the password reset, Cisco IoT FND 5.x.x is fully deployed.

Step 3

Configure the network IPv4 settings. For more information, refer to Configuring IPv4 Settings.

Step 4

After you change the default password and the VM has network connectivity, you can manage the VM using the RHEL web console. For more information, refer to Managing Virtual Machines in the Web Console for RHEL version 7.x and Managing Virtual Machines in the Web Console for RHEL version 8.0.

You are able to access Cisco IoT FND using RHEL console successfully.