Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Repairing a cluster node

You can use the repair feature on a node that is in BLOCKING state.

When you repair a node, all cluster connections are reset for the node, and the node rejoins the cluster and resynchronizes its metadata with the cluster. If the node contains metadata changes that are incompatible with the rest of the cluster, it is removed from the cluster when it tries to reconnect.

If the node being repaired is the timekeeper, it loses its timekeeper role to another operational node in the cluster. The new timekeeper keeps its role as timekeeper even after the old timekeeper node is repaired.

Warning

Note

 Review the cluster status information to find out the current status of a node.

Follow the procedure given below to repair a cluster node:

  1. On the BMC Atrium DIL server node that is in BLOCKING state, navigate to BSMDASHBOARDS_HOME\DIL\CIS\apps\dil and run DILCluster.bat (Microsoft Windows) or DILCluster.sh (UNIX or Linux).

  2. In the BMC Atrium DIL Configuration Utility, type option 5 (Repair this cluster node) and press Enter.

    The output that you receive is similar to the following example:

    Using configuration from C:\BMCSoftware\BMCDashboardsForBSM\DIL
    OS = Windows Server 2008
    Executing "C:\BMCSofware\BMCDashboardsForBSM\DIL\CIS\bin
    \cluster_util.bat"     -server localhost -port 9400 -user dil_admin -password
    <BLOCKED_PASSWORD> -domain composite -repair -debug:
    Cluster connections have been reset
    DONE

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Dashboards for Business Service Management 7.7.00