Set the required bootarg (for MetroCluster IP upgrades to systems introduced in ONTAP 9.15.1 or later)
-
PDF of this doc site
-
Install a fabric-attached MetroCluster
-
Cable a fabric-attached MetroCluster configuration
-
Plan and install a MetroCluster configuration with array LUNs
-
-
Install a MetroCluster IP configuration
-
Install a stretch MetroCluster configuration
-
Maintain the MetroCluster components
-
Transition from MetroCluster FC to MetroCluster IP
-
Upgrade, refresh, or expand the MetroCluster configuration
-

Collection of separate PDF docs
Creating your file...
Upgrades to systems introduced in ONTAP 9.15.1 or later require you to set a bootarg before you can proceed with the upgrade.
Step 1: Determine the bootarg you need to set on the old controllers
All supported upgrades to the following systems require you to set a bootarg on the old controllers before performing the controller upgrade:
-
AFF A70, AFF A90, AFF A1K
-
FAS70, FAS90
-
AFF C80
-
AFF A50, AFF A20, AFF A30
-
AFF C30, AFF C60
|
If you are upgrading to any of the systems listed, you must set a required bootarg on the existing system before performing the upgrade. For all other upgrades, you can skip this task and go directly to Prepare the system for upgrade. |
Most upgrades to systems introduced in ONTAP 9.15.1 or later require you to set the hw.cxgbe.toe_keepalive_disable
bootarg on the old controllers. However, certain upgrade paths require you to set the bootarg.siw.interop_enabled
bootarg instead.
Use the following table to determine which bootarg you need to set for your specific upgrade combination.
For this upgrade… | Set the bootarg… |
---|---|
From AFF A250 to AFF A30 |
|
From AFF C250 to AFF C30 |
|
From AFF A150 to AFF A20 |
|
From AFF A220 to AFF A20 |
|
All other supported upgrades to AFF A70, AFF A90, AFF A1K, FAS70, FAS90, AFF C80, AFF A50, AFF A20, AFF A30, AFF C30, or AFF C60 systems |
|
Step 2: Set the required bootarg on the old controllers
This task is only required when you upgrade to an AFF A70, AFF A90, AFF A1K, FAS70, FAS90, AFF C80, AFF A50, AFF A20, AFF A30, AFF C30, or AFF C60 system.
-
Halt one node at each site and allow its HA partner to perform a storage takeover of the node:
halt -node <node_name>
-
Set the required bootarg for your upgrade combination. You already determined the bootarg that you need to set by using the table in determine which bootarg you need to set.
hw.cxgbe.toe_keepalive_disablebootarg.siw.interop_enabledhw.cxgbe.toe_keepalive_disablehw.cxgbe.toe_keepalive_disablebootarg.siw.interop_enabled-
At the
LOADER
prompt of the halted node, enter the following:setenv hw.cxgbe.toe_keepalive_disable 1
saveenv
printenv hw.cxgbe.toe_keepalive_disable
-
At the
LOADER
prompt of the halted node, enter the following:setenv bootarg.siw.interop_enabled 1
saveenv
printenv bootarg.siw.interop_enabled
-
-
Boot the node:
boot_ontap
-
When the node boots, perform a giveback for the node at the prompt:
storage failover giveback -ofnode <node_name>
-
Repeat the steps on each node in the DR group that is being upgraded.