--- title: "Cluster is unhealthy or malformed" slug: "cluster-is-unhealthy-or-malformed" updated: 2026-08-24T20:40:08Z published: 2026-08-24T20:40:08Z canonical: "docs.trellix.com/cluster-is-unhealthy-or-malformed" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Cluster is unhealthy or malformed ##### Problem The nodes cannot authenticate with each other, there is a problem with a cluster process or component, or a sensor or broker is not connected. ##### Reason The following are probable reasons for the problem: - The authentication key hash is not the same on all nodes. - The broker role is disabled. - Cluster processes are unhealthy or not running. - Guest images are not installed on the nodes. ##### Action To correct the problem: - Use the show mvx node status full command on a node to determine the specific issue and view a list of connected sensors, hybrid appliances, and brokers. - If the Key Hash value is not the same on all nodes, remove the nodes from the cluster and then create the cluster again. - If the node should be a broker, but the broker role is disabled, use the `cmc mvx cluster <cluster name> broker <node name> enable` command in the Central Management CLI. - If guest images are not installed, install them. - If the Web services API (WSAPI) process is not running, use the `wsapi enable` command in the Virtual Execution (node) CLI.