# US 2026/0220005 A1 · Node Fencing In Storage Clusters

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0220005 A1
- Document ID: US20260220005A1
- Status: Published application
- Kind: A1
- Application number: 19/036,914
- Filed: 2025-01-24
- Published: 2026-07-30
- Earliest claimed: 2025-01-24
- Applicants: NetApp, Inc.
- Inventors: Reyaz Ahmed; Todd Jason Mills; Aleksandr Sergeev Khasymski; Rahul Thekkalore Srinivasa
- Web page: https://patentgrep.com/patent/US20260220005A1

## CPC

- G06F 11/2025: {using centralised failover control functionality}
- G06F 11/1666: {where the redundant component is memory or memory area}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques and systems for enhanced storage system management and failure detection/mitigation are presented. In one example, a method includes, responsive to detection of a trigger event for a first host node monitored by at least a second host node, initiating fencing of the first host node by at least transferring a fencing notification to a controller module for a set of storage drives assigned to the first host node. The method also includes preventing the first host node from communicating with the set of storage drives, and alerting a client node communicating with the first host node that the second host node is handling communication with the set of storage drives.

## Claims

### Claim 1

A method, comprising:
responsive to detection of a trigger event for a first host node monitored by at least a second host node, initiating fencing of the first host node by at least transferring a fencing notification to a controller module for a set of storage drives assigned to the first host node;
preventing the first host node from communicating with the set of storage drives by at least revoking a connection between the controller module and the first host node to block future connection requests with respect to the first host node; and
alerting a client node communicating with the first host node that the second host node is handling communication with the set of storage drives.

### Claim 2 (depends on 1)

The method of claim 1, wherein the trigger event corresponds to one or more conditions being satisfied with regard to operational status of the first host node as monitored by at least the second host node.

### Claim 3 (depends on 2)

The method of claim 2, wherein the operational status corresponds to periodic heartbeat signaling indicating the first host node is unresponsive.

### Claim 4 (depends on 1)

The method of claim 1, wherein several redundant host nodes, including the second host node, monitor operation of the first host node and transfer associated fencing notifications to the controller module; and
wherein the second host node is selected by the controller module among the several redundant host nodes based at least on a prioritization scheme.

### Claim 5 (depends on 1)

The method of claim 1, wherein transferring the fencing notification comprises transferring the fencing notification to the controller module though a redundant controller module in communication over a sideband communication link with the controller module.

### Claim 6 (depends on 1)

The method of claim 1, wherein revoking the connection comprises at least revoking a remote direct memory access (RDMA) connection associated with the first host node to block connection requests from the first host node for the controller module.

### Claim 7 (depends on 1)

The method of claim 1, wherein prior to the trigger event, the first host node handles storage transactions with respect to the client node; and
wherein subsequent to the trigger event, the second host node handles further storage transactions with respect to the client node.

### Claim 8 (depends on 1)

The method of claim 1, comprising:
responsive to the trigger event, attempting to recover operation of the first host node while the first host node is fenced.

### Claim 9 (depends on 8)

The method of claim 8, comprising:
responsive to the first host node recovering operational status, transferring a fencing removal notification to the controller module for the set of storage drives, wherein the controller module removes the fencing for the first host node with respect to the set of storage drives; and
alerting the client node communicating with the second host node that the first host node is handling communication with the set of storage drives.

### Claim 10 (depends on 1)

The method of claim 1, wherein alerting the client node comprises transferring a notification for network addressing to reach the set of storage drives, wherein the network addressing corresponds to changing to a network address of the second host node.

### Claim 11 (depends on 1)

The method of claim 1, wherein the first host node, the second host node, and the controller module are coupled over a communication fabric.

### Claim 12

An apparatus, comprising:
one or more computer readable storage media; and
program instructions stored on the one or more computer readable storage media that, based on being executed by a processing system, direct the processing system to at least:
initiate fencing of a first host node by at least detection of a trigger event for the first host node monitored by at least a second host node and transferring a fencing notification to a controller module for a set of storage drives assigned to the first host node; and
responsive to the fencing notification:
prevent the first host node from communicating with the set of storage drives by at least revoking a connection between the controller module and the first host node to block future connection requests with respect to the first host node; and
alert a client node communicating with the first host node that the second host node is handling communication with the set of storage drives, wherein subsequent to the trigger event, the second host node handles further storage transactions with respect to the client node.

### Claim 13 (depends on 12)

The apparatus of claim 12, wherein the trigger event corresponds to one or more conditions being satisfied with regard to operational status of the first host node as monitored by at least the second host node.

### Claim 14 (depends on 12)

The apparatus of claim 12, wherein several redundant host nodes, including the second host node, monitor operation of the first host node and transfer associated fencing notifications to the controller module; and
wherein the second host node is selected by the controller module among the several redundant host nodes based at least on a prioritization scheme.

### Claim 15 (depends on 12)

The apparatus of claim 12, comprising further program instructions that, based on being executed by the processing system, direct the processing system to at least:
transfer the fencing notification by at least transferring the fencing notification to the controller module though a redundant controller module in communication over a sideband communication link with the controller module.

### Claim 16 (depends on 12)

The apparatus of claim 12, comprising further program instructions that, based on being executed by the processing system, direct the processing system to at least:
revoke the connection by at least revoking a remote direct memory access (RDMA) connection associated with the first host node to block connection requests from the first host node for the controller module.

### Claim 17 (depends on 12)

The apparatus of claim 12, comprising further program instructions that, based on being executed by the processing system, direct the processing system to at least:
responsive to the trigger event, attempt to recover operation of the first host node while the first host node is fenced.

### Claim 18 (depends on 17)

The apparatus of claim 17, comprising further program instructions that, based on being executed by the processing system, direct the processing system to at least:
responsive to the first host node recovering operational status, transfer a fencing removal notification to the controller module for the set of storage drives, wherein the controller module removes the fencing for the first host node with respect to the set of storage drives; and
alert the client node communicating with the second host node that the first host node is handling communication with the set of storage drives, wherein subsequent to the fencing removal notification, the first host node handles subsequent storage transactions with respect to the client node.

### Claim 19 (depends on 18)

The apparatus of claim 18, comprising further program instructions that, based on being executed by the processing system, direct the processing system to at least:
alert the client node by at least transferring a notification for network addressing to reach the set of storage drives, wherein the network addressing corresponds to changing to a network address of the second host node.

### Claim 20

A storage system, comprising:
a first host node, a second host node, and a storage input/output module coupled over a communication fabric;
the first host node configured to handle storage transactions for a client node with respect to an assigned set of storage drives managed by the storage input/output module;
the second host node configured to monitor the first host node for a failure event;
responsive to detection of the failure event for the first host node, the second host node configured to initiate fencing of the first host node by at least transferring a fencing notification to the storage input/output module;
the storage input/output module configured to prevent the first host node from communicating with the set of storage drives by at least revoking a connection between the controller module and the first host node to block future connection requests with respect to the first host node; and
the second host node configured to alert the client node that the second host node is handling subsequent storage transactions with the set of storage drives.
