sudo -i -u postgres /opt/vmware/vpostgres/current/bin/repmgr
cluster show you see the below outcome ID | Name | Role | Status | Upstream | Location | Priority | Timeline | Connection string
-------+-------+---------+-----------+----------+----------+----------+----------+---------------------------------------------------------------------------------
###46 | Cell1 | standby | running | Cell2 | default | 100 | 4 | host=##.##.##.## user=repmgr dbname=repmgr gssencmode=disable connect_timeout=2
###07 | Cell2 | primary | * running | | default | 100 | 4 | host=##.##.##.## user=repmgr dbname=repmgr gssencmode=disable connect_timeout=2
###18 | Cell3 | primary | - failed | ? | default | 100 | | host=##.##.##.## user=repmgr dbname=repmgr gssencmode=disable connect_timeout=2
WARNING: following issues were detected
- unable to connect to node "Cell3" (ID: ###18)
VMware Cloud Director 10.x
A a failover occurred and the primary cell changed, however the old primary is still part of the cluster as failed cell.
The failed primary cell needs to be removed from the Cloud Director infrastructure, since it is broken and not following the Primary cell. For more information about VMware Cloud Director Appliance Cluster Health follow he document: View Your VMware Cloud Director Appliance Cluster Health and Failover Mode
For removing a standby cell from VMware Cloud Director, please follow the document: Unregister a Running Standby Cell in Your VMware Cloud Director Database High Availability Cluster
If you are unable to use the Cloud Director API for unregistering a standby, please contact Broadcom Support and note this Article ID (384401) in the problem description. For more information, see Creating and managing Broadcom support cases.