3.4 How to list clusters?

Log in to UMC with your admin credentials, and then follow these steps:

  1. Browse and select the cluster objects you want to view.

  2. The following information is displayed for each cluster object.

    Column Name

    Description

    Status (Colour Coding)

    Status

    Green

    Running: The cluster is up and running.

    Blue

    Maintenance: The cluster is temporarily suspended by the admin for maintenance.

    Gray

    Down: The cluster is stopped, and admin intervention is required.

    Red

    Failed: One or more nodes in the cluster have failed, and admin intervention is required.

    White

    Unknown: UMC cannot determine the status of the cluster.

    BCC state (Colour Coding)

    Status

    Green

    Normal: The connections between clusters are functioning normally.

    Blue

    Authenticating: BCC is in the process of authenticating to a peer cluster.

    Red

    Invalid credentials: You entered the wrong user name or password for the selected peer cluster.

    Red

    Cannot connect: This cluster cannot connect to the selected peer cluster.

    Red

    Not authorized: The connected user does not have sufficient rights for permissions.

    White

    Connection unknown: The connection state between clusters is unknown.

    Name

    The name assigned to the cluster.

    Master node

    The name of the currently assigned master node for the cluster.

    Node availability

    Number of available nodes out of the total nodes.

    Resources

    The number of resources running in this cluster.

    Epoch

    The number of times the cluster state has changed. The cluster state changes every time a server joins or leaves the cluster.

    The columns listed above are the default ones. You can select to add additional columns such as Type, Master IP address, BCC state, and Location.

  3. Select a refresh frequency that allows you to comfortably view all items in the list.

    NOTE:If the status of a healthy cluster is Down or Unknown, then increase the timeout value CLUSTER_LISTING_FAILURE_TIMEOUT = 2000 in the /opt/novell/umc/apps/umc-server/prod.env file. The default value is 2000 ms, and due to network latency, it might not be able to retrieve the correct status of the cluster. Additionally, if this parameter is missing in the prod.env file, ensure to add it so that the cluster listing timeout occurs after the specified time.