Go to main content

Oracle® Solaris Cluster 4.3 Geographic Edition System Administration Guide

Exit Print View

Updated: June 2017

Removing Trust Between Partner Clusters

This section describe how to remove trust between partner clusters.

How to Remove Trust Between Two Clusters

Perform this procedure to remove trust from between two clusters.

Note -  You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface. Click Partnerships, highlight the name of the partnership, and click Remove Partner Trust. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager in Oracle Solaris Cluster 4.3 System Administration Guide.

Before You Begin

Ensure that the following conditions are met:

  1. Log in to a cluster node.
  2. If a partnership is configured between the two clusters, dissolve that partnership.

    Run the following command on both clusters:

    # geops leave
  3. On all nodes of both clusters, remove all keys for the remote cluster from the truststore file on the local node.
    # geops remove-trust -c remote-partner-cluster-name

    Perform this step on all the nodes of the local cluster, and then repeat this step on all nodes of the partner cluster.

    –c remote-partner-cluster-name

    Specifies the logical hostname of the cluster from which you want to remove the keys. The name for the remote cluster must be identical to the cluster name you specified when adding trust with the geops add-trust command. You do not need to specify the fully qualified name if the remote cluster is reachable by partial name.

    When you use this option with the add-trust or remote-trust subcommand, the option specifies the alias where the public keys on the remote cluster are stored. An alias for certificates on the remote cluster has the following pattern:


    Only keys that belong to the remote cluster should have their alias match this pattern.

    For more information about the geops command, refer to the geops(1M) man page.

  4. Repeat the preceding steps on a node of the remote partner cluster.