#Best way to wipe cluster and rebuild

1 messages · Page 1 of 1 (latest)

summer thunder
#

What is the best and easiest way to wipe an entire cluster config and install a fresh OnTap 9 cluster? I don't want to spend the time removing 100's of SVM's, lifs, snapmirror relationships from a cluster i am repurposing.

ruby dove
#
  1. connect to the SPs of both nodes and jump into ONTAP with "system console"
  2. halt -node * -inhibit-takeover true
  3. once both nodes are in the LOADER: boot_ontap menu
  4. in the boot-menu where it wants you select 1-8, simply type: wipeconfig
  5. wait until it finished and once you are back in the boot-menu choose (4) Clean configuration and initialize all disks.
  6. Confirm and wait until it finished, it will come up again with a fresh ONTAP and you will need to do the cluster setup (set mgmt-IPs, provide a cluster-name, etc.)
#

Be aware this will also wipe the license keys. So you need to download them again from the NetApp support-site and add them to the cluster.
If you don't have access to the support-site or didn't save the keys before... well you are screwed. There is no way to actually export the keys directly from ONTAP afaik. And without licenses ONTAP is pretty much useless.

grim vine
#

If you want to go deeper, let me know. I use a process that 100% wipes everything including the boot device. The boot device gets reformatted and all drives are cleared

modern sapphire
#

You can wipe the boot device by simply doing a netboot and using boot option 7. When netbooting, that option formats the boot device and installs a fresh ONTAP into both slots (whereas, if you boot normally and use option 7, it only overwrites the inactive slot)

modern mica
#

@grim vine , we've developed our own process to wipe everything but I'd be interested in your process, especially if yours is nice and scripted... Can this be made public?

grim vine
#

I’ll send when I get to my laptop (would rather use a full size , well 88% sized… keyboard to type it out). It’s from documentation. I’ve done it so much it’s engraved in my brain. I do it for all new installs. Give me to end of day

summer thunder
#

@grim vine I am very interested in your documentation. I have an old FAS2554 at my disposal.

grim vine
#
  1. Have a Web server handy. Found it is better if it can communicate on port 80. If not, YMMV
  2. Get the ONTAP release you want to use and place on the WEB SERVER
  3. Depending on the platform, you may have to extract the image (on the web server)
    -> you would need both the extracted version now and the tgz file on the web server later
  4. Get your controller(s) to the LOADER prompt(s)
  5. reset the LOADER variables: set-defaults
  6. Save the environment: saveenv
  7. Set the e0M: ifconfig e0M -addr=192.168.100.101 -mask=255.255.255.0 -gw=192.168.1.1
    -> NOTE: it is import to set the GW even if you do not need it
    -> there is a bug in some versions, where the next phase will not work unless the gw is set
  8. Try to ping the e0M from a client, make sure it is online
  9. NETBOOT the ONTAP image:
    -> netboot http://192.168.100.250/97P22_q_image.tgz
    -> if that fails, netboot http://192.168.100.250/netboot/kernel (this is like the FAS8020/8040/etc)
    -> NOTE: if you are using IIS, you will need to "fix" IIS to allow files without extensions
    -> NOTE: if the NETBOOT panics, try an older version (like 9.6, latest P release, using my 9.7 example here)
    -> I noticed recently that an older version of LOADER would not netboot a current version of ONTAP
  10. This will auto-matically boot to the BOOT MENU
#
  1. Choose option 7 at the Boot Menu.
    -> ONTAP will remember the IP setting from the LOADER here (needs GW filled at ifconfig in or this fails)
  2. Follow prompts and enter the URL to the ONTAP image: http://192.168.100.250/97P22_q_image.tgz
    -> If you had to netboot the kernel, you still use the ONTAP image here, not the kernel
  3. This will fully wipe the boot media, reformat it and place this image in both boot images (image1/image2)
  4. When Prompted: say NO to restore from backup.
    -> if you accidentily answer Y, you will have to repeat the process above.
  5. When prompted: say YES to reboot onto the new image
  6. The system may auto-update firmware at this point. When it is all done, it will boot to and stop at the Boot Menu
  7. At this point, follow the other procedures
    (i.e. choose option 9 on both nodes, then 9a on node 1 and wait, then 9a on node 2 and wait, then 9b on node 1 and wait then 9ab on node 2)
#

I use my Mac as the web server: python3 -m http.server 80

#

@modern mica & @summer thunder -> there you go

summer thunder