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

PDF

Prerequisites

Updated: February 4, 2026

Overview

This topic outlines the prerequisites for implementing high availability (HA) and disaster recovery (DR) for Cisco IoT Field Network Director (FND) with a Postgres database.

Here are the prerequisities to use HA and DR on Cisco IoT FND with Postgres:

  • Deploy EnterpriseDB PostgreSQL Standard v16 with Postgres Distributed (PGD), and manage database upgrades, backup, and restore in coordination with the EDB vendor.

  • Provision separate Bare Metal servers or VMs for Cisco IoT FND application servers, the EDB Witness node, and PostgreSQL data nodes, with the PGD Proxy co-located on the data nodes; do not use the standalone OVA for HA deployments.

  • Deploy the solution across multiple data centers with reliable, low‑latency network connectivity, including multiple PostgreSQL data nodes and a witness node distributed across sites.

  • Configure a PGD Proxy for each PostgreSQL data node and ensure reachability from all Cisco IoT FND application servers.

  • Deploy two active Cisco IoT FND application servers in different data centers and enable secure REST‑based communication between them.

  • Deploy a high‑availability DNS solution such as F5 GSLB with the required licenses, and configure Cisco IoT FND access using fully qualified domain names.

  • Install custom JBoss web certificates on Cisco IoT FND servers to enable secure inter‑application communication and accept the defined security behavior when using self‑signed certificates.

  • Run the setupCgms.sh script with high‑availability options, including configuration of PGD proxy addresses and database node details.

  • Acknowledge architectural constraints and requirements, including unsupported FogD HA, InfluxDB HA, and TPS HA, adequate infrastructure capacity for large‑scale deployments, and compliance with Cisco security standards.