Skip to main content
NetApp Knowledge Base

Node panic during  MetroCluster IP back-end switch replacement

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

Applies to

  • ONTAP 9
  • MetroCluster IP
  • Node panic
  • Back-end switch upgrade

Issue

  • Node ports, connected to the new switches, don't come up
  • Node panic reported ~30 minutes into the replacement procedure with string:

Process vldb unresponsive for 243 seconds in process nodewatchdog on release 9.11.1P8 (C)

 

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.