Skip to main content
NetApp Knowledge Base

Upgrade to ONTAP 9.11.1 or later fails to complete due to aborted Normalize Initiator Names task

Views:
1,202
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
SAN
Last Updated:

Applies to

  • 9.11.1 or later
  • Automated Non-Disruptive Upgrade (ANDU)

Issue

  • Upgrade might fail with errors about being unable to normalize initiator names when upgrading to ONTAP 9.11.1 on a cluster with initiators that contain upper case characters. These initiators might show up as  not logged in  when using the CLI command: igroup show -v 

 

  • After a node reboots on the newer ONTAP version, the ANDU pauses due to the upgrade not completing.
 
::>cluster image show-upgrade-progress
Summary:
Upgrade failed to complete.
failed Error: Upgrade of node "ntap-clus01-node01-hapairA-firstnode" failed to complete.
Action: Use the (privilege: advanced)command "system node upgrade-revert show -node <nodename>" to check the upgrade status.
 
  • Running ::>system node upgrade-revert show, a task shows "aborted":
Node: ntap-clus01-node01-hapairA-firstnode                             Status: aborted

Status Message: The upgrade aborted in the "post-apps" phase on task "Normalize Initiator Names Upgrade Revert Task". Contact support personnel for the upgrade repair procedure.

Vers Phase      Status   Upgrade Phase Status Message
---- ---------- -------- ------------------------------------------------------
1400 pre-root   applied  No upgrade is required for this phase.
1400 pre-apps   applied  Upgrade successful.
1400 post-apps  applied  Upgrade successful.
1800 pre-root   applied  No upgrade is required for this phase.
1800 pre-apps   applied  No upgrade is required for this phase.
1800 post-apps  aborted  A duplicate initiator was found after normalizing initiator names to lower case characters. Verify the configuration of the initiator using the "lun mapping show -initiator 20:00:00:25:B5:15:1B:01|20:00:00:25:b5:15:1b:01" and "igroup show -initiator 20:00:00:25:B5:15:1B:01|20:00:00:25:b5:15:1b:01" commands. The same igroup or LUN map must not contain the same initiator more than once regardless of character case. Different Vservers refering to the same initiator must use the same character case. Resolve any conflicts and then resume the upgrade.
6 entries were displayed.

You may also see the following Status Message for the aborted task:
  • You may also see the following Status Message for the aborted task:
Duplicate initiators are mapped to the same LUN. Do not try to fix this problem. Using either the 'lun mapping delete' command or the 'lun igroup remove' command could
lead to an outage. Contact technical support for assistance.

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.

 

  • Was this article helpful?