Site icon EfmSoft

What does NTSTATUS 0xC0130017 (STATUS_CLUSTER_POISONED) mean?

 
Previous Next
STATUS_CLUSTER_NETWORK_NOT_INTERNAL STATUS_CLUSTER_NON_CSV_PATH

STATUS_CLUSTER_POISONED

The public status identifies node containment but not the poison trigger

STATUS_CLUSTER_POISONED is a failover-clustering status. Microsoft publishes the same text for the corresponding Win32 cluster error, but the public code table does not define the internal transition criteria that place a node into this exact poisoned state. Do not infer one specific disk, network, or hardware cause from the word poisoned.

Modern failover-cluster documentation uses a related containment concept called node quarantine. Microsoft describes quarantine after recurring node failures and lists persistent cluster service, hardware, storage, and network problems as possible contributors. Health Service faults likewise report a quarantined server due to recurring failures. These modern documents are useful for a diagnostic model, but they do not establish that historical STATUS_CLUSTER_POISONED is identical to the current quarantine mechanism.

Collect the cluster log and identify the first transition or fault before the node-wide status appears. Record node state, cluster service restarts, membership/join events, network health, storage connectivity, and resource failures. Avoid clearing state repeatedly just to make the node rejoin: containment may be preventing repeated failures from destabilizing the cluster. The decisive evidence is the earlier cluster event chain and component-specific errors, not the generic final NTSTATUS.

What to inspect

References


Looking for a different code? Search another status or error code.

Exit mobile version