Deployment and Management Guide for Cisco IoT FND on OVA with Postgres and InfluxDB, Release 5.x.x and Later

Verify the OVA signature

Updated: February 4, 2026

Overview

Use this procedure to verify the OVA signature for your deployment, ensuring the integrity and authenticity of the OVA file before installation. This process helps confirm that the file has not been tampered with and is safe to use.

Use the instructions provided in this section to verify the OVA signature:

Here are the contents of the OVA zip file for different use cases:


Use case	Contents
Oracle-based deployments	iot-fnd-oracle-<release>-<build number>_SHA1_signed.ova
TPS-related deployments	iot-tps-<release>-<build number>_SHA1_signed.ova

Before you begin

The following knowledge is required to verify OVA signature:

Python 2.7.x
OpenSSL
Internet connection

Procedure

Use the ovftool command on your terminal to verify the signed OVA file.

Example:

ovftool iot-fnd-<release>-<build number>_SHA256_signed.ova

This command checks the integrity and authenticity of the OVA file by verifying its signature.

Opening OVA source: iot-fnd-<release>-<build number>_SHA256_signed.ova
        The manifest validates
        Completed successfully

What to do next

Verify the upgrade RPM signature

Need help?

Open a support case

(Requires a Cisco Service Contract)

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.