Skip to main content
NetApp Knowledge Base

MetroCluster node can't boot after ONTAP upgrade

Views:
80
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • Fabric MetroCluster
  • Upgrading to ONTAP 9.8 and above
  • One or more FCVI adapters down

Issue

When upgrading to ONTAP 9.8 or above whilst one FCVI port is down, the system repeatedly panics

Example:

PANIC  : prod/common/nv/flexlog/nv_flexlog.c:1887: Assertion failure.
version: version: 9.10.1P7: Tue Aug  2 04:59:50 EDT 2022
conf   : x86_64
bsdver : 12.0
cpuid = 0
KDB: stack backtrace:
vpanic() at vpanic+0x6ec/frame 0xfffff70000009740
panic() at panic+0x43/frame 0xfffff700000097a0
sk_panic() at sk_panic+0x63/frame 0xfffff70000009800
fatal() at fatal+0x39/frame 0xfffff70000009810
ontap_assert_() at ontap_assert_+0x4a/frame 0xfffff70000009840
flxlog_init() at flxlog_init+0x7a3/frame 0xfffff70000009880
sysinit_thread() at sysinit_thread+0x1ab/frame 0xfffff70000009a70
fork_exit() at fork_exit+0x110/frame 0xfffff70000009ab0
fork_trampoline_sk() at fork_trampoline_sk+0xe/frame 0xfffff70000009ab0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

 

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.