<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Remove unhealthy nodes from the cluster in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Remove-unhealthy-nodes-from-the-cluster/m-p/467181#M45377</link>
    <description>&lt;P&gt;FAS2750 device, system ONTAP9.16. When controller A node 1 took over controller B node 2, I started the system of node 2 and entered the menu mode to select the fourth option to clear the configuration. During the restart process, there was a waiting for giveback. Then I returned the configuration in node 1 and entered a brand new node system (node 3). In node 1, I recreated the cluster and allowed node 3 to rejoin the cluster. The configuration of cluster IP, node IP, interface lif, vserver, etc. before node 2 is still in place. I want to remove the failed node 2, but the prerequisite is to delete or migrate the vserver lif and other configurations related to node 2. However, I tried modifying the cluster IP, node IP, interface lif, and so on, which showed Error: command failed: RPC: Could't make connection [from mgwd on node]&lt;BR /&gt;"FAS2750-03" (VSID: -1) to vifmgr at 169.254.157.6]，&lt;/P&gt;&lt;P&gt;I use commands&lt;BR /&gt;FAS2750::*&amp;gt; cluster remove-node -node FAS2750-02 -force true&lt;/P&gt;&lt;P&gt;Warning: This command will forcibly remove node "FAS2750-02" from the cluster.&lt;BR /&gt;You must remove the failover partner as well. This will permanently&lt;BR /&gt;remove from the cluster volumes that remain on that node and logical&lt;BR /&gt;interfaces with that node as the home-node. Contact support for&lt;BR /&gt;additional guidance.&lt;BR /&gt;Do you want to continue? {y|n}: y&lt;BR /&gt;[Job 1064] Cleaning cluster database&lt;BR /&gt;Error: command failed: [Job 1064] Job failed: Failed to delete SAN&lt;BR /&gt;configuration for lif with id 1032 from its current node (FAS2750-02):No&lt;BR /&gt;nodes are available to process the command. Verify that all nodes are&lt;BR /&gt;healthy using the "cluster show" command, then try the command again.&lt;/P&gt;&lt;P&gt;And the system alarm displays:&lt;BR /&gt;FAS2750::*&amp;gt; system he al show&lt;BR /&gt;Node: FAS2750-01&lt;BR /&gt;Alert ID: ClusterSwitchlessConfig_Alert&lt;BR /&gt;Resource: FAS2750&lt;BR /&gt;Severity: Major&lt;BR /&gt;Indication Time: Wed May 13 16:39:20 2026&lt;BR /&gt;Suppress: false&lt;BR /&gt;Acknowledge: false&lt;BR /&gt;Probable Cause: No cluster switch is detected and the switchless&lt;BR /&gt;option is not enabled.&lt;BR /&gt;Possible Effect: Communication problems and cluster connectivity issues&lt;BR /&gt;occur.&lt;BR /&gt;Corrective Actions: 1) If the cluster network is configured as a two-node&lt;BR /&gt;switchless cluster (TNSC), enable switchless detection&lt;BR /&gt;by using the "network options detect-switchless-cluster&lt;BR /&gt;modify -enabled true" command. No further action is&lt;BR /&gt;required.&lt;BR /&gt;2) If the cluster network is configured with cluster&lt;BR /&gt;switches, the nodes fail to detect the switches.&lt;BR /&gt;Ensure that the network interfaces on the cluster&lt;BR /&gt;switches connected to the node cluster ports are enabled&lt;BR /&gt;on both sides.&lt;BR /&gt;If the errors are corrected, stop. No further action is&lt;BR /&gt;required. Otherwise, continue to step 3.&lt;BR /&gt;3) Check the physical connections between the nodes and&lt;BR /&gt;the cluster switches. Replace network cables with&lt;BR /&gt;known-good cables. If the errors are corrected, stop.&lt;BR /&gt;No further action is required. Otherwise, continue to step 4.&lt;BR /&gt;4) Ensure that either CDP (for Cisco switches) or ISDP&lt;BR /&gt;(for NetApp CN1610 and Broadcom BES-53248 switches) is&lt;BR /&gt;enabled on the cluster switches.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;FAS2750::*&amp;gt; network options detect-switchless-cluster show&lt;/P&gt;&lt;P&gt;Enable Switchless Cluster Detection: true&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Big shots, please help me take a look and answer my questions. Thank you very much.&lt;/P&gt;</description>
    <pubDate>Wed, 13 May 2026 10:44:33 GMT</pubDate>
    <dc:creator>LearnfromNetApp</dc:creator>
    <dc:date>2026-05-13T10:44:33Z</dc:date>
    <item>
      <title>Remove unhealthy nodes from the cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Remove-unhealthy-nodes-from-the-cluster/m-p/467181#M45377</link>
      <description>&lt;P&gt;FAS2750 device, system ONTAP9.16. When controller A node 1 took over controller B node 2, I started the system of node 2 and entered the menu mode to select the fourth option to clear the configuration. During the restart process, there was a waiting for giveback. Then I returned the configuration in node 1 and entered a brand new node system (node 3). In node 1, I recreated the cluster and allowed node 3 to rejoin the cluster. The configuration of cluster IP, node IP, interface lif, vserver, etc. before node 2 is still in place. I want to remove the failed node 2, but the prerequisite is to delete or migrate the vserver lif and other configurations related to node 2. However, I tried modifying the cluster IP, node IP, interface lif, and so on, which showed Error: command failed: RPC: Could't make connection [from mgwd on node]&lt;BR /&gt;"FAS2750-03" (VSID: -1) to vifmgr at 169.254.157.6]，&lt;/P&gt;&lt;P&gt;I use commands&lt;BR /&gt;FAS2750::*&amp;gt; cluster remove-node -node FAS2750-02 -force true&lt;/P&gt;&lt;P&gt;Warning: This command will forcibly remove node "FAS2750-02" from the cluster.&lt;BR /&gt;You must remove the failover partner as well. This will permanently&lt;BR /&gt;remove from the cluster volumes that remain on that node and logical&lt;BR /&gt;interfaces with that node as the home-node. Contact support for&lt;BR /&gt;additional guidance.&lt;BR /&gt;Do you want to continue? {y|n}: y&lt;BR /&gt;[Job 1064] Cleaning cluster database&lt;BR /&gt;Error: command failed: [Job 1064] Job failed: Failed to delete SAN&lt;BR /&gt;configuration for lif with id 1032 from its current node (FAS2750-02):No&lt;BR /&gt;nodes are available to process the command. Verify that all nodes are&lt;BR /&gt;healthy using the "cluster show" command, then try the command again.&lt;/P&gt;&lt;P&gt;And the system alarm displays:&lt;BR /&gt;FAS2750::*&amp;gt; system he al show&lt;BR /&gt;Node: FAS2750-01&lt;BR /&gt;Alert ID: ClusterSwitchlessConfig_Alert&lt;BR /&gt;Resource: FAS2750&lt;BR /&gt;Severity: Major&lt;BR /&gt;Indication Time: Wed May 13 16:39:20 2026&lt;BR /&gt;Suppress: false&lt;BR /&gt;Acknowledge: false&lt;BR /&gt;Probable Cause: No cluster switch is detected and the switchless&lt;BR /&gt;option is not enabled.&lt;BR /&gt;Possible Effect: Communication problems and cluster connectivity issues&lt;BR /&gt;occur.&lt;BR /&gt;Corrective Actions: 1) If the cluster network is configured as a two-node&lt;BR /&gt;switchless cluster (TNSC), enable switchless detection&lt;BR /&gt;by using the "network options detect-switchless-cluster&lt;BR /&gt;modify -enabled true" command. No further action is&lt;BR /&gt;required.&lt;BR /&gt;2) If the cluster network is configured with cluster&lt;BR /&gt;switches, the nodes fail to detect the switches.&lt;BR /&gt;Ensure that the network interfaces on the cluster&lt;BR /&gt;switches connected to the node cluster ports are enabled&lt;BR /&gt;on both sides.&lt;BR /&gt;If the errors are corrected, stop. No further action is&lt;BR /&gt;required. Otherwise, continue to step 3.&lt;BR /&gt;3) Check the physical connections between the nodes and&lt;BR /&gt;the cluster switches. Replace network cables with&lt;BR /&gt;known-good cables. If the errors are corrected, stop.&lt;BR /&gt;No further action is required. Otherwise, continue to step 4.&lt;BR /&gt;4) Ensure that either CDP (for Cisco switches) or ISDP&lt;BR /&gt;(for NetApp CN1610 and Broadcom BES-53248 switches) is&lt;BR /&gt;enabled on the cluster switches.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;FAS2750::*&amp;gt; network options detect-switchless-cluster show&lt;/P&gt;&lt;P&gt;Enable Switchless Cluster Detection: true&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Big shots, please help me take a look and answer my questions. Thank you very much.&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2026 10:44:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Remove-unhealthy-nodes-from-the-cluster/m-p/467181#M45377</guid>
      <dc:creator>LearnfromNetApp</dc:creator>
      <dc:date>2026-05-13T10:44:33Z</dc:date>
    </item>
    <item>
      <title>Re: Remove unhealthy nodes from the cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Remove-unhealthy-nodes-from-the-cluster/m-p/467202#M45378</link>
      <description>&lt;P&gt;I would open a P1 ASAP.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2026 13:27:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Remove-unhealthy-nodes-from-the-cluster/m-p/467202#M45378</guid>
      <dc:creator>SpindleNinja</dc:creator>
      <dc:date>2026-05-14T13:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: Remove unhealthy nodes from the cluster</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Remove-unhealthy-nodes-from-the-cluster/m-p/467210#M45379</link>
      <description>&lt;P&gt;This is my testing environment, without any business impact. I sincerely request guidance from community experts to help me solve the problem of removing this node&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2026 01:56:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Remove-unhealthy-nodes-from-the-cluster/m-p/467210#M45379</guid>
      <dc:creator>LearnfromNetApp</dc:creator>
      <dc:date>2026-05-15T01:56:00Z</dc:date>
    </item>
  </channel>
</rss>

