Controller hardware upgrade for AFF and FAS systems resolution guide

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 4,000

Visibility:: Public

Votes:: 3

Category:: aff-series

Specialty:: hw

Last Updated:

Applies to

ONTAP 9
Controller Hardware Upgrade
- Headswap
- Head Upgrade
AFF systems
FAS systems
MetroCluster
Systems with FlexArray Virtualization Software

Description

This guide describes how to upgrade controller hardware of an AFF system or a FAS system in a cluster by moving storage or volumes.

The hardware upgrade procedures have been simplified in ONTAP 9.8 with the introduction of the automatic port placement feature.
When you are upgrading a system running ONTAP 9.8 and later, use the correct procedure to account for the port placement feature.

Upgrade procedures

Review the following table to see the available upgrade procedures. See each guide for additional details to determine if the procedure is appropriate.

For MetroCluster-specific procedures, see Select the upgrade procedure for your MetroCluster configuration

Hardware Upgrade Method	Location
Upgrade by moving aggregates on systems running ONTAP 9.8 or later	Use "system controller replace" commands (AFF A700 to AFF A900) Use "system controller replace" commands (most systems) Use manual commands
Upgrade by moving aggregates on systems running ONTAP 9.7 or earlier	Use “system controller replace” commands (most systems) Use manual commands
Upgrade by moving storage or volumes (most systems)	Upgrade by moving volumes or storage

Resolution Guide

Review the following table to see known issues that may arise during your upgrade:

Known Issues	Resolution

Compatibility issues
Controller model of node "node_name" is not supported for controller replacement operation	Controller model of node "node_name" is not supported for controller replacement operation
FAS8300 does not support 10GBe links on any of the onboard ports	Unable to bring up cluster links during a headswap from a FAS8200 to FAS8300 Cluster ring offline after headswap from FAS8020 to FAS8300
Network Config issues
`Cannot run this command because the system is not fully initialized.`	'Mapping Ports' step during headswap fails with "Error: Cannot run this command because the system is not fully initialized."
Cluster LIFs are missing from `network interface show` output Cluster SVM is missing from `vserver show` output Attempting to migrate cluster LIFs to new platform ports while in this state using `network interface migrate` results in error: `Error: command failed: LIF "node1_clus1" on Vserver "Cluster" could not be found in database (database vifids is not open). Contact technical support for assistance.`	Cluster applications fail to come online after controller upgrade procedure
`Error: command failed: Cannot remove port that is a failover target for a LIF. To list LIFs containing a failover target, use the "network interface show -failover-targets <targetname>" command.`	Unable to delete network port after Controller Hardware upgrade Unable to delete VLAN and ifgrp configuration from node during controller replace
HA interconnect down after FAS8300 head swap	HA INTERCONNECT DOWN after the head-swap from FAS80x0 to FAS8300 PANIC : rlib_port_ipspace_assign: port e0a could not be moved to HA ipspace
Failover issues
Takeover is not possible after controller upgrade `Takeover is not possible: Storage failover mailbox disk state is invalid, Storage failover is disabled on the partner node, Storage failover interconnect error, NVRAM log not synchronized, Disk inventory not exchanged`	Takeover is not possible after controller upgrade
Attempting to add 2 new AFF A250 nodes to an existing cluster with CN1610 cluster network switches.	Controller Hardware Upgrade: Adding AFF A250 nodes to existing cluster report HA interconnect errors and cannot perform takeover
Storage Access issues
	Root aggregate is missing after a Head Upgrade After a Head Upgrade data access across the cluster is failing New LUNs are showing 0 bytes in size on the hosts
Upgrade Issues
`::*> system controller replace show-details` `Error on node cluster1-02. Reason: Error in modifying bootarg.head.ontapupgrade`	Error in modifying bootarg.head.ontapupgrade during controller upgrade
`mgmtgwd.var.recovery:EMERGENCY]: Part of the /var boot directory is missing.`	System Configuration Restore: Part of the /var boot directory is missing

Additional Information

N/A

Applies to

Description

Upgrade procedures

Hardware Upgrade Method

Resolution Guide

Compatibility issues

Network Config issues

Failover issues

Storage Access issues

Upgrade Issues

Additional Information