Skip to main content
NetApp Knowledge Base

Disk firmware update fails during ONTAP upgrade due to HA configuration conflict

  1. Last updated
  2. Save as PDF
Views:
140
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • single-node configuration

Issue

  • Disk firmware update does not progress during ONTAP upgrade operations.
  • "Number waiting Download" count fluctuates, reaching zero but increasing again repeatedly.
  • ONTAP environment shows a conflict in HA configuration settings between "Chassis HA" and "Controller HA". Disk firmware update process fails to execute successfully.

SP-LATEST-CONSOLE-LOGS
[mgr.boot.unequalDist:error]: Warning: Unequal number of disks will be used for auto-partitioning of the root aggregate on the local system and HA partner. The local system will use 6 disks but the HA partner will use 0 disks. To correct this situation, boot both controllers into maintenance mode and remove the ownership of all disks.
[cf.fm.notkoverClusterDisable:error]: Failover monitor: takeover disabled (restart)
[cf.fsm.backupMailboxError:error]: Failover monitor: partner mailbox error detected.
[cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of partner disabled (Controller Failover takeover disabled).
[cf.fm.notkoverBadMbox:notice]: Failover monitor: uninitialized backup mailbox data detected
Chassis is in "ha" configuration, controller is in "ha" configuration, and the HA mode is "disabled". Cannot determine whether configuration should be HA, non-HA, MetroCluster, or MetroCluster 2-node. Boot into Maintenance mode by rebooting the node and selecting the maintenance mode option (5) on the boot menu. Then run the "ha-config modify" command to set the controller and chassis configuration as appropriate. Setting the wrong configuration might lead to data loss. For further assistance, contact technical support.
[haosc.config.unknown.ls:ALERT]: Cannot determine whether the configuration should be stand-alone or HA. Chassis is in ha configuration, controller is in ha configuration, and the HA mode is disabled.
[clam.invalid.config:error]: Local node (name=unknown, id=0) is in an invalid configuration for providing CLAM functionality. CLAM cannot determine the identity of the HA partner.

  • sysconfig -a shows a single-node configuration

NetApp Release 9.5P19: 
    System ID: 0537109631 (Node-01)
    System Serial Number: ******* (Node-01)
    System Rev: B1
    System Storage Configuration: Mixed-Path
    System ACP Connectivity: Inband Active
    SAS2/SAS3 Mixed Stack Support: all
    All-Flash Optimized: false
    Capacity Optimized: false
    Backplane Part Number: DS21212
    Backplane Rev: 
    Backplane Serial Number: 031738001255
    slot 0: System Board 1.9 GHz (System Board XXII B1)
                Model Name: FAS2620

  • The CLUSTER-HA log displays "HA Configured false"

CLUSTER-HA
HA Configured    false
Backend HA MBX configured

  • In maintenance mode, the ha-config show command displays the actual ha settings.

*> ha-config show
   Chassis HA configuration: ha
   Controller HA configuration: ha

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.