Skip to main content
NetApp Knowledge Base

Modifying management LIFs disrupts database operations

  1. Last updated
    Apr 4, 2025
  2. Save as PDF
Views:
424
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:
4/4/2025, 12:53:06 PM

Applies to

  • ONTAP 9
  • SCSI SAN
  • Microsoft Windows Server 

Issue

  • Database disruption after changes to cluster, node, or vserver management LIF  IP address or “management-https” of  network interface service-policy

Note: This symptom is also triggered even only modify “management-https” of a completely unused network interface service policy, or create new policy with https service

  • Windows log:

Event 152 - The logical block provisioning type for disk  has changed
Event 140 - The system failed to flush data to the transaction log corruption may occur in volume id devicename :
(The I/O device reported an I/O error )

  • Linux messages.log:

kernel: sd 8:0:2:2: Inquiry data has changed

  • ESXi vmkernel.log:

qlnativefc: vmhba2(3d:0.0): qlnativefcStatusEntry:1995:Inquiry Data Changed, rediscover DIF capability : senseKey = 0x6 : asc = 0x3f : ascq = 0x3

 

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.