Skip to main content
NetApp Knowledge Base

ONTAP Select HA experiences random reboots due to network partitioning caused by a flaky Interconnect

  1. Last updated
  2. Save as PDF
Views:
66
Visibility:
Public
Votes:
0
Category:
ontap-select
Specialty:
ontapselect
Last Updated:

Applies to

  • NetApp ONTAP Select
  • NetApp ONTAP Select Deploy

Issue

  • This OTS HA experiences random reboots due to network partitioning caused by a flaky Interconnect.
  • First ha.netPartition.other can be observed as early as the 20th Sept 2021

Mon Sep 20 18:20:14 +0200 [cluster01-02: nvram_sync: ha.netPartition.other:debug]: Network partition due to other error. Duration 803 msecs, takeover wait 0 msecs; error code 5; status: 0x201081; request id: 162.

  • Problem gradually got more severe leading up to node cluster01-02 being stuck in a boot loop with "Waiting for requisite number of local mailboxes.." -error
  • Node cluster01-01 was used to create a single node cluster for the customer to continue serving data whilst a new cluster is being set up and can be migrated to.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.