Skip to main content
NetApp Knowledge Base

ISCSI sessions are not re-established post ontap upgrade

  1. Last updated
  2. Save as PDF
Views:
333
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • Ontap 9.x
  • Iscsi Protocol
  • Windows Host

Issue

  • ISCSI sessions are not re-established post upgrading the Ontap from 9.12.1p3 to 9.12.1p4 for the windows hosts.
  • Post upgrade, for some of the initiators, the sessions are established on just Node:1 and for some only on node:2.
  • san.initiator.login.missing events are logged in ems:

Tue Jul 11 13:12:20  0530 [Node1: bcomd: san.initiator.login.missing:notice]: Initiator "iqn.1991-xx.com.microsoft:xyz-xx5.niit-xx.com" is not logged in to any LIFs on this node for Vserver "svm", portset "-". Access to LUNs might be disrupted if a failover occurs.
Tue Jul 11 13:12:20  0530 [Node1: bcomd: san.initiator.login.missing:notice]: Initiator "iqn.1991-xx.com.microsoft:xyz-xx5.niit-xx.com" is not logged in to any LIFs on this node for Vserver "svm", portset "-". Access to LUNs might be disrupted if a failover occurs.

 

 

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.