Saturday, March 15, 2014
How to convert a Data ONTAP node from one operating Mode to the other?
Ephraim Iverson: How to convert a Data ONTAP node from one operating Mode to the other?
https://kb.netapp.com/support/index?page=content&id=1013517&cat=DATA_ONTAP_8_CLUSTER_MODE&actp=LIST
Here are the detail if you can not get into the link. Taken from NetApp's Knowledge-base
Description
This article describes the procedure that should be followed to convert the operation of a storage controller from 7-Mode to Cluster-Mode or from Cluster-Mode to 7-Mode.
Note: Data ONTAP 7-Mode and Clustered Data ONTAP licenses are different. Please contact your sales team to obtain new licenses.
Warning: On-disk data is not preserved when using this procedure. All data will be lost.
Procedure
Prerequisites:
The controller must have attached disk shelves.
The disk shelves must be HA-cabled across the HA-pair (multipath HA cabling is recommended).
This procedure will work for a single node as well, that is not part of an HA pair.
Refer to the System Configuration Guides for the version and Mode of Data ONTAP that you will be using to ensure the hardware and slots used are supported.
There must be a bootable image on the boot device.
If converting from Cluster-Mode to 7-Mode, the node(s) of the Cluster-Mode must be unjoined from the cluster if the cluster remains active and only a node or HA-Pair will be converted to 7-Mode. See the article, 1013966: How to unjoin a node in Data ONTAP 8.1.x Cluster-Mode
Data on the attached disk shelves is not critical and can be recovered from an alternate source, if needed
Note: All Data will be lost when following this procedure to convert from one Mode to the other.
If Data ONTAP 8.x is not on the boot device or new shelves are added as part of this process, see article 1010549: How to build a Data ONTAP 8.x system from the beginning.
Perform the following steps to convert from Data ONTAP 7-Mode to Data ONTAP 8.0X Cluster-Mode
Disable 'Cluster Failover' and reboot the node to the LOADER prompt. Do not perform a takeover.
Boot each node to the LOADER prompt and ensure that the following variables are set:
To convert from 7-Mode to Cluster-Mode:
LOADER> set-defaults
LOADER> setenv bootarg.init.boot_clustered true
LOADER> setenv bootarg.bsdportname <node-mgmt_port_name>
Boot the node with this command:
boot_ontap
When the nodes are booting, press CTRL+C to enter the Boot menu.
At the Boot menu, select wipeconfig on each node.
*******************************
* Press Ctrl-C for Boot Menu. *
*******************************
How would you like to continue booting?
(normal) Normally
(install) Install new software first
(password [user]) Change root/user password
(setup) Run setup first
(init) Initialize disks and create flexvol
(maint) Boot into maintenance mode
(syncflash) Update flash from backup config
(reboot) Reboot node
Please make a selection: wipeconfig
After the wipeconfig completes, boot back to the Boot menu and select setup.
*******************************
* Press Ctrl-C for Boot Menu. *
*******************************
How would you like to continue booting?
(normal) Normally
(install) Install new software first
(password [user]) Change root/user password
(setup) Run setup first
(init) Initialize disks and create flexvol
(maint) Boot into maintenance mode
(syncflash) Update flash from backup config
(reboot) Reboot node
Please make a selection: setup
Enter the node configuration information for each node during the setup script.
Hostname
Location
IP address for mgmt LIF on the mgmt port/Netmask/DefaultGwy
DNS domain name/DNS nameserver IP(s)
After the setup script completes, boot back to the Boot menu and select init.
*******************************
* Press Ctrl-C for Boot Menu. *
*******************************
How would you like to continue booting?
(normal) Normally
(install) Install new software first
(password [user]) Change root/user password
(setup) Run setup first
(init) Initialize disks and create flexvol
(maint) Boot into maintenance mode
(syncflash) Update flash from backup config
(reboot) Reboot node
Please make a selection: init
The init process can take a long time (hours depending on the number and size of the disks) as the disks are zeroed and initialized.
Once the init process has completed, the node will boot Data ONTAP and the login prompt will be available.
At this time, a new Cluster can be created or these nodes can be joined to an already existing cluster. The steps for creating or joining a cluster are available in the Data ONTAP Administration guides. See the article, 1010920: How to configure a pair of clean nodes and join them to an existing cluster
Perform the following steps to convert from Data ONTAP 7-Mode to Data ONTAP 8.1 (and later versions) Cluster-Mode
Disable 'Storage Failover' or 'Cluster Failover' and reboot the node to the LOADER prompt. Do not perform a takeover.
At the LOADER prompt, run the following commands:
To convert from 7-Mode to Cluster-Mode:
LOADER> set-defaults
LOADER> setenv bootarg.init.boot_clustered true
LOADER> setenv bootarg.bsdportname <node-mgmt_port_name>
LOADER> boot_ontap
Stop the boot process at the special Boot menu and select option 4.
The node automatically performs a wipeconfig, zeroes the disks and creates a 3-disk root aggregate with a FlexVol root volume.
Perform the node setup.
Perform the following steps to convert from Data ONTAP Cluster-Mode to Data ONTAP 7-Mode
Disable 'Storage Failover' and reboot the node to the LOADER prompt. Do not perform a takeover.
At the LOADER prompt, run the following commands:
To convert from Cluster-Mode to 7-Mode:
LOADER> set-defaults
LOADER> boot_ontap
Stop the boot process at the special Boot menu and select option 4.
The node automatically performs a wipeconfig, zeroes the disks and creates a 3-disk root aggregate with a FlexVol root volume.
Perform the node setup.
Subscribe to:
Post Comments (Atom)
To move the actual data consider using NDMPcopy to move the data from 7-mode to CDOT.
ReplyDeleteAlso use snapmirror TDP to move non-SAN data. You may have to use either NDMPcopy or other SAN 2 SAN migration methods.
ReplyDeleteCaveats I found:
ReplyDeleteDescription
This article describes the procedure that should be followed to convert the operation of a Data ONTAP 8.x storage controller from 7-Mode to clustered Data ONTAP.
Note: Data ONTAP 7-Mode and clustered Data ONTAP licenses are different. Contact your sales team to obtain new licenses.
Warning:
• On-disk data is not preserved when using this procedure. All data will be lost.
• This procedure should only be performed by a NetApp employee or a Netapp partner performing an installation.
• You must be running a minimum OS version of Data ONTAP 8.1.y 7-Mode to convert to clustered Data ONTAP. Do not attempt a conversion while running Data ONTAP 8.0.y 7-Mode.
-
Prerequisites:
• This procedure only works with Data ONTAP 8.x
• Data on the attached disk shelves will be erased.
• The controller must have attached disk shelves.
• The disk shelves must be HA-cabled across the HA-pair (multipath HA cabling is recommended).
• This procedure will work for a single node as well, that is not part of an HA pair.
• Refer to the System Configuration Guides for the version and Mode of Data ONTAP that you will be using to ensure the hardware and slots used are supported.
• There must be a bootable image on the boot device.
Steps to convert from Data ONTAP 8.0.x 7-Mode to Data ONTAP 8.1.y or 8.2.y clustered Data ONTAP:
Warning: You must be running a minimum OS version of Data ONTAP 8.1.y 7-Mode to convert to clustered Data ONTAP. Do not attempt a conversion while running Data ONTAP 8.0.y 7-Mode.
Note: If this is an HA pair, it is safe to perform the following operation at the same time on both storage controllers.
Perform the following steps:
1. Run software update command to upgrade Data ONTAP from 8.0.x 7-Mode to 8.1.x or 8.2.x 7-Mode
controller> software update http://path_to_web_accessible_diretory/image.tgz -f
2. Once the upgrade is complete, proceed with the following procedure below to convert 8.1.x or 8.2.x 7-Mode to 8.1.y or 8.2.y C-Mode
Note: The ONTAP upgrade to 8.1.x or 8.2.x 7-Mode must complete before continuing. The ONTAP node must boot fully and allow login before considering the upgrade complete.
Steps to convert from Data ONTAP 8.1.x or 8.2x 7-Mode to Data ONTAP 8.1.y or 8.2.y Clustered Data ONTAP:
Note:
• A node runing Data ONTAP 8.1.x 7-Mode at a minimum is required to perform this procedure.
• Do not upgrade Data ONTAP during this procedure. If an ONTAP ugprade is desired as part of the conversion of 7-Mode to cDOT, either perform the complete upgrade while running 7-Mode or perform the upgrade after the conversion has completed AND after the node has joined or created a new cluster.
• If this is an HA pair, it is safe to perform the following operation at the same time on both storage controllers.
1. Disable 'Cluster Failover:'
controller> cf status
controller> cf disable
2. Run the cf status command to verify that 'Cluster Failover' is disabled, and shut down the storage controller to the LOADER prompt:
controller> cf status
controller> halt -f
3. Run the set-defaults command to clear any existing bootargs, and then set the following bootargs at the LOADER prompt:
LOADER> set-defaults
LOADER> setenv AUTOBOOT false
LOADER> setenv bootarg.init.bootmenu true
4. Validate the above 2 bootargs are correctly set to their respective values. After bootargs are verified, enter 'boot_ontap' at the LOADER prompt:
LOADER> printenv AUTOBOOT
LOADER> printenv bootarg.init.bootmenu
LOADER> boot_ontap
5. At the Boot Menu, enter 'wipeconfig'
If Boot Menu is not presented, stop and go to Step 2.