Skip to main content
NetApp Knowledge Base

Volume Path Errors Triggered by Link Flaps

Views:
4
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

Applies to

  • E-Series
  •  Fibre channel

Issue

Volumes intermittently report path errors and are not on their preferred paths. Volume transfers are triggered unexpectedly due to link flaps. This results in I/O shipping and VNOPP (Volume Not On Preferred Path) errors.
SANtricity major event log shows repeated occurrences of link flaps shortly before I/O shipping events:
A:5/20/25, 2:22:01 PM (14:22:01) 77462 210a Controller cache not enabled or was internally disabled - Shelf 99, Bay A - Event: Cache Reconfigure Sync-54
B:5/20/25, 2:22:02 PM (14:22:02) 77461 2044 IO shipping implicit volume transfer - Volume Volumename - Shipped/Owned IOs: 92/4, Host ID: 38
B:5/20/25, 2:22:02 PM (14:22:02) 77460 212c Write-back caching fully restored - Shelf 99, Bay B
B:5/20/25, 2:22:02 PM (14:22:02) 77459 210a Controller cache not enabled or was internally disabled - Shelf 99, Bay B - Event: Give Volume Ownership-54
A:5/20/25, 2:17:14 PM (14:17:14) 77458 1018 Fibre channel link up - Host-side: controller in bay A, port 6
A:5/20/25, 2:17:14 PM (14:17:14) 77457 1017 Fibre channel link down - Host-side: controller in bay A, port 6

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.