Netbooting the new controller modules

If the new controller modules have a different version of ONTAP from the version on the surviving controller modules, you must netboot the new controller modules.

1. Download the appropriate ONTAP software from the software download section of the Lenovo Support Site and store the <ontap_version>_image.tgz file on a web-accessible directory.
   The <ontap_version>_image.tgz file is used for performing a netboot of your system.
2. Extract the contents of the <ONTAP version>_image.tgz file to the target direction: tar —zxvf <ONTAP version>_image.tgz
3. Align the end of the controller module with the opening in the chassis, and then gently push the controller module into the system.
4. Display the attributes of a switchless cluster from the surviving site: network options switchless-cluster show
5. If your node is in a switchless cluster, set the switchless cluster environment variable at the LOADER prompt on the impaired node console: setenv bootarg.init.switchless_cluster.enable true

   Note

   This is an advanced privilege command.
6. If you are using AFA controller modules, set the flash optimized boot environment variable: setenv bootarg.init.flash_optimized true
7. Depending on your network configuration, execute one of the following commands at the LOADER prompt:

   If you...	Then...
   Have DHCP enabled	Use the following command: ifconfig e0M -auto
   Do not have DHCP enabled	Use the following command: ifconfig e0M -addr=filer_addr -mask=netmask -gw=gateway -dns=dns_addr -domain=dns_domain filer_addr is the IP address of the storage system. netmask is the network mask of the storage system. gateway is the gateway for the storage system. dns_addr is the IP address of a name server on your network. dns_domain is the Domain Name System (DNS) domain name. If you use this optional parameter, you do not need a fully qualified domain name in the netboot server URL; you need only the server’s host name. Note Other parameters might be necessary for your interface. For details, use the help ifconfig command at the LOADER prompt.

8. At the LOADER prompt, netboot the new node: netboot http://web_server_ip/path_to_web-accessible_directory/netboot/kernel
9. Select the Install new software first option from the displayed menu.

   This menu option downloads and installs the new ONTAP image to the boot device.

   • You should enter y when prompted with the message that this procedure is not supported for nondisruptive upgrade on an HA pair.

   • You should enter y when warned that this process replaces the existing ONTAP software with new software.

   • You should enter the path as follows when prompted for the URL of the image.tgz file: http://path_to_the_web-accessible_directory/image.tgz

10. Complete the following substeps:
    1. Enter n to skip the backup recovery when prompted.

       **************************************************************
       *             Restore Backup Configuration                   *
       *  This procedure only applies to storage controllers that   *
       *  are configured as an HA pair.                             *
       *                                                            *
       *  Choose Yes to restore the 'varfs' backup configuration    *
       *  from a TFTP server.  Refer to the Boot Device Replacement *
       *  guide for more details.                                   *
       *  Choose No to skip the back up recovery and return to the  *
       *  boot menu.                                                *
       **************************************************************
       
       Do you want to restore the backup configuration
       now? {y|n} <kbd className="ph userinput nolinebreak">n</kbd>
       
       
    2. Reboot the node by entering y when prompted.

       The node must be rebooted to start using the newly installed
       software. Do you want to reboot now? {y/n} <kbd className="ph userinput nolinebreak">y</kbd>
       
       

       After reboot, if prompted to update firmware and BIOS, enter y to accept.

       The controller module displays the Boot menu because the boot device was reformatted and the configuration data needs to be restored.

11. From the Boot menu, select option 5 to enter Maintenance mode.
12. If you have a four-node MetroCluster configuration, repeat this procedure on the other controller module.