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

Monitor servers

Updated: February 4, 2026

Overview

Learn how to monitor HA databases and nodes using Cisco IoT FND. This procedure explains how to access the server inventory and interpret key status fields such as connectivity, IP addresses, and open issues to ensure the health of your network infrastructure.

The task aims to help you monitor the HA databases and the nodes using Cisco IoT FND.

Procedure

From the Cisco IoT FND menubar, choose Devices > Servers.

A detailed inventory of all the servers is displayed. Here are the fields and their descriptions in collapsed view:

Field	Field Description
Name	Displays the name assigned to the server
EID	Displays the EID associated with the server.
Status	Displays the status of the server if it is up or down.
Last Heard	Displays the time at which Cisco IoT FND communicated with the server for the last time.
IP	Displays the IP addresses associated with the server.
Open Issues	Displays open issues that needs to be resolved in the server.
Labels	Displays the lables added to the server, if any.

Click the + icon adjacent to the Name column to expand a server's details. Here are the fields and their descriptions in expanded view:

Field	Field Description
NAME	Displays the name assigned to the server
EID	Displays the EID associated with the server.
STATUS	Displays the status of the server if it is up or down.
IP	Displays the IP addresses associated with the server.
TYPE	Displays if the server is either a node or a PGD proxy.

You've successfully learnt how to monitor the servers once HA is configured.

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.