Skip to main content
NetApp Knowledge Base

MetroCluster nodes reboot during atto bridge firmware updates versions above 3.30 4.30

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

Applies to

  • Fabric MetroCluster
  • ONTAP 9
  • ATTO 7500N/7600N bridges undergoing firmware updates to version above 3.30/4.30

Issue

  • Cluster node(s) reboot unexpectedly during ATTO bridge firmware updates.
  • EMS logs show:

Thu May 25 19:14:13 +0200 [CL01N01: disk_server_1: disk.reservationConflict.key:debug]: Device MC1SW01:7.126L1016 reported SCSI RESERVATION CONFLICT status. 0 milliseconds ago, the reservation key reported by this device was 200306d00000007.
Thu May 25 19:14:13 +0200 [CL01N01: disk_server_1: ha.resvConflictHalt:notice]: A disk reservation conflict was detected on disk MC1SW01:7.126L1016 at %-20s. Typically, this only occurs when the node was taken over by its partner.

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.