Skip to main content
NetApp Knowledge Base

Panic when converting a 4-Node Fabric MetroCluster to Non-MetroCluster HA

  1. Last updated
  2. Save as PDF
Views:
148
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • AFF-A400
  • Non MetroCluster HA

Issue

  • Node in a panic loop after converting a 4-Node Fabric MetroCluster to Non-MetroCluster HA.
  • The panic occurs at very early stage at the  boot process and does not allow to reach the boot menu or even the maintenance mode. 

Starting SW iWARP kmod module...
Starting MCC kmod module...
rlib_rport_alloc: enabling unsafe global rkey
rlib_rport_alloc: enabling unsafe global rkey
PANIC  : rlib_port_ipspace_assign: port e0a could not be moved to HA ipspace
[err=92]
version: 9.10.1RC1: Tue Oct 26 22:46:19 EDT 2021
conf   : x86_64.optimize.nodar
cpuid = 19

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.