When a system is part of multiple Teradata Fabric Manager clusters, the fabric port numbers and the link names involving that system must be unique across clusters. When Teradata Fabric Manager detects fabric port or link name conflicts, those conflicts are reported as an issue in the Viewpoint Teradata Fabric portlet.
When there is a conflict, the fabric or link that has been in existence the longest has precedence. This helps prevent new changes from breaking working functionality.
To resolve a conflict, change the conflicting port number or link name in one of the clusters. Remember to also update the foreign server definition after changing the link name.
All nodes within a system must have the same primary cluster. It is possible for nodes to differ on what the primary cluster is, based on local node settings. When this occurs, an issue is reported in the Teradata Fabric portlet. The primary cluster is also listed in the node section and node details of the Teradata Fabric portlet. To set the primary cluster for a system, use the set-primary.sh command.