Skip to main content
NetApp Knowledge Base

CONTAP-411813: After Giveback, client-data-access from non-local data-LIFs fails

  1. Last updated
    May 28, 2025
  2. Save as PDF
Views:
39
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:
5/28/2025, 4:37:05 PM

Issue

  • after "storage failover giveback" had completed, the "ofnode" reports "aggregate Differences" in vreport for "Blade UUID"
  • vreport difference is WAFL reporting the "fromnode" dblade UUID and VLDB erroneously reporting the "ofnode" dblade UUID for the SFO aggregate that was relocated during the giveback operation. Example:
    ::*> debug vreport show
    aggregate Differences:
    Name Reason Attributes
    -------- ------- ---------------------------------------------------
    aggr1 Present both in VLDB and WAFL with differences
    Node Name: node-01
    Aggregate UUID: c88f874f-9237-4ad9-a0f0-ecd0cb492d96
    Aggregate State: online
    Aggregate Raid Status: raid_dp, mirrored
    Aggregate HA Policy: sfo
    Is Aggregate Root: false
    Aggregate Vol Count: 130
    Is Composite Aggregate: false
    Differing Attribute: Blade UUID
    WAFL Value: a32cf117-8251-11eb-a586-d039ea450084
    VLDB Value: d483d5e0-8250-11eb-a5eb-d039ea45008b

  • for victim volumes hosted on that aggregate, vreport also may report "junction Differences". Example:
    Name Reason Attributes
    -------- ------- ---------------------------------------------------
    mySVM:myVol File Handle for the Parent Volume does not match with Dblade
    Parent Info:
    VolName: myVol
    MSID: 2147484730 DSID: 6583 vsID: 19
    Child:
    VolName: myVol
    MSID: 0 DSID: 6565 vsID: 19

  • client data access for LIFs hosted on "fromnode" fail after Giveback unless they are migrated to "ofnode"
  • if configuration changes had been made while "ofnode" was in-takeover, these changes might remain unknown to the management plane at "ofnode" after giveback, leading to unexpected behavior for operations local on "ofnode" after giveback

 

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.