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

PDF

Check DB and status post upgrade

Updated: February 4, 2026

Overview

Use this procedure to check the database and Cisco IoT FND status after an upgrade to ensure the process was successful. You will learn how to verify system services, Docker versions, and container health to confirm that all critical components are operational.

Use the following steps to check the DB and Cisco IoT FND status to ensure that your upgrade is successful:

Before you begin

Use the following credentials for SSH access after upgrading OVA:

  • Username: fnduser

  • Password: C!sco123

    See Guidelines for resetting password.

Procedure

1.

Log in to the server or machine using SSH.

2.

Execute the /opt/scripts/status.sh command:

Example:

/opt/scripts/status.sh
Checking system status...
            Service: Database
            Status: Running
            Uptime: 24 hours
            Service: IoT FND
            Status: Running
            Uptime: 12 hours
            Service: Web Server
            Status: Stopped
            Action Required: Restart service
            Disk Usage:
            Filesystem      Size  Used Avail Use% Mounted on
            /dev/sda1        50G   30G   18G  63% /
            Memory Usage:
            Total: 8GB
            Used:  4GB
            Free:  4GB
            Network Status:
            eth0: Connected
            IP Address: 192.168.1.10
            All critical services are operational except the Web Server. Please address the issues noted above.
3.

Execute the docker version command:

Example:

docker version
Client: Docker Engine - Community
            Version:           20.10.14
            API version:       1.41
            Go version:        go1.16.15
            Git commit:        a224086
            Built:             Thu Mar 24 01:50:09 2022
            OS/Arch:           linux/amd64
            Context:           default
            Experimental:      true
            Server: Docker Engine - Community
            Engine:
            Version:          20.10.14
            API version:      1.41 (minimum version 1.12)
            Go version:       go1.16.15
            Git commit:       87a90dc
            Built:            Thu Mar 24 01:48:43 2022
            OS/Arch:          linux/amd64
            Experimental:     false
            containerd:
            Version:          1.5.11
            GitCommit:        3df54a852345ae127d1fa3092b95168e4a88e2f8
            runc:
            Version:          1.0.3
            GitCommit:        f46b6ba2c9314cfc8caae24a32ec5fe9ef1059fe
            docker-init:
            Version:          0.19.0
            GitCommit:        de40ad0
4.

Execture the /opt/fnd/scripts/fnd-container.sh status command to check the status of the Cisco IoT FND container:

Example:

/opt/fnd/scripts/fnd-container.sh status
Checking IoT FND container status...
            Container Name: fnd-container
            Status: Running
            Uptime: 36 hours
            CPU Usage: 15%
            Memory Usage: 512MB / 2GB
            Network: Active
            IP Address: 172.17.0.2
            Port Mappings: 8080:80, 8443:443
            Last Health Check: Passed
            Health Check Interval: 5 minutes
            All monitored services within the container are operational.
5.

Execute the docker exec -it fnd-container /etc/init.d/cgms status command to check the status of the cgms service inside the Cisco IoT FND container.

Example:

docker exec -it fnd-container /etc/init.d/cgms status
Checking status of cgms service...
            cgms service is running
            PID: 1234
            Uptime: 24 hours
            Listening on Port: 9090
            No issues detected with the cgms service.
You've checked the Cisco IoT FND status to ensure that the upgrade has been successful.

What to do next

Log into Cisco IoT FND to check if the services are working fine. For example, you can refresh the metrics for a couple of devices or add/delete devices using CSV.