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.

Retrieving cluster status information


Follow the procedure given below to retrieve cluster information. The information returned is for all nodes in the cluster.

  1. On a BMC Atrium DIL server node, navigate to BSMDASHBOARDS_HOME\DIL\CIS\apps\dil and run DILCluster.bat (Windows) or DILCluster.sh (UNIX or Linux).
  2. In the BMC Atrium DIL Configuration Utility, type option 7 (Retrieve cluster status information) and press Enter.

    The output that you receive is similar to the following example. Lines similar to the following are displayed for each node in the BMC Atrium DIL cluster:

    SERVER_ID, SERVER_NAME, SERVER_HOST, SERVER_PORT, STATUS, TIMEKEEPER,
    CONNECT_TIME, LAST_CONTACT, IDLE_DURATION, NUM_CONNECTS, BYTES_TO,
    BYTES_FROM, MESSAGE
    bsmdash5.bmc.com-9400-1719378104, bsmdash5.bmc.com-9400-1719378104,
    bsmdash5.bmc.com, 9400, OPERATIONAL [29], Y, null, null, , 0, , ,

    The following table describes the status information that is displayed.

    Parameter

    Description

    SERVER_ID

    The unique ID of the BMC Atrium DIL server.

    SERVER_NAME

    The server name of the BMC Atrium DIL server.

    SERVER_HOST

    The host name for the BMC Atrium DIL server.

    SERVER_PORT

    The port number used by the BMC Atrium DIL server.

    STATUS [#] (for a local node)

    For the local node (the BMC Atrium DIL server on which you are running the utility), the following statuses may be displayed:

    INITIALIZING_LOCAL—This server node is initializing its internal state

    INITIALIZING_REMOTE—This server node is initializing its connections with other remote cluster nodes

    OPERATIONAL—This server node is fully operational and synchronized.

    BLOCKED—This server node is awaiting a response from one or more server nodes for a period of time that exceeds the Block Threshold specified in Composite Studio.

    LEAVING—This Composite Server node is being removed from the cluster. The Message column provides additional information pertaining to the current status. For OPERATIONAL nodes, the Message column lists the pending responses from remote nodes this node is waiting on.

    [#]—The change level for this node. This value is non-negative numerical indicator of the level at which changes have been captured in the metadata repository. In general, in steady state, all nodes in a cluster should be operating at the same change level. However, because changes might be occurring on other nodes at any time, only the local node change level is known and displayed.

    STATUS (for a remote node)

    For a remote node, displays one of these values:

    CONNECTED—This server node is connected to the cluster. A

    CONNECTED node is not necessarily synchronized with the rest of the cluster.

    CONNECTED_READY—This server node is connected to the cluster and is synchronized and ready to receive change notifications.

    BLOCKING—This server node has not responded to another server node for a period that is longer than the Block Threshold specified in Composite Studio.

    DISCONNECTED—This server node is not connected to the cluster.

    INVALID_LICENSE—This server node is attempting to join the cluster but does not have a valid license.

    TIMEKEEPER

    Displays one of two values:

    Y—This server node is the timekeeper for the cluster.

    N—This server node is not the timekeeper for the cluster.

    The role of the timekeeper is to control the sequence of metadata updates.

    When a cluster is created, the first member of the cluster is the timekeeper.

    CONNECT_TIME

    The time that the cluster connection was established between the local server node and the cluster node displayed in that row. Each time the server connects to a cluster node and becomes an active member of the cluster, this value is updated. Note that this value defaults to GMT.

    LAST_CONTACT

    The last time that a message was received across the cluster network connection by the local server node. Note that this value defaults to GMT.

    IDLE_DURATION

    Number of milliseconds between the LAST_CONTACT time and now.

    NUM_CONNECTS

    Number of successful connection attempts by the local server node to the cluster.

    BYTES_TO

    Number of bytes sent to the local server node since it started.

    BYTES_FROM

    Number of bytes sent from the remote server node to the local server node.

    MESSAGE

    Additional information about the activity of the server node. Also indicates the cluster nodes from which this node is awaiting responses.

 

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