Setting up the new nodes

During the process of upgrading by moving storage, you power on the new nodes, boot the software image, and configure the new nodes.

Steps

  1. Turn on the power to the first new node, and then immediately press Ctrl-C at the console terminal to access the boot environment prompt (also called the LOADER prompt).
    If you are upgrading to a system with both nodes in the same chassis, the other node also reboots. You can disregard booting the other node for now.
  2. If the new node has a single-chassis configuration (with controllers in the same chassis):
    1. Switch the console cable from the current new node to the other new node.
    2. Turn on the power to the second new node, and then interrupt the boot process by pressing Ctrl-C at the console terminal to access the boot environment prompt.
      The power should already be on if both controllers are in the same chassis.
      Leave the second new node at the boot environment prompt; you return to this procedure and repeat these steps after the first new node is installed.
    3. Switch the console cable back to the first new node.
  3. At the boot environment prompt, enter the following command: set-defaults
  4. At the boot environment prompt, configure the netboot connection for a management LIF:
    If IP addressing is... Then...
    DHCP

    Configure the automatic connection:

    ifconfig e0M -auto
    Static

    Configure the manual connection:

    ifconfig e0M -addr=ip_addr -mask=netmask -gw=gateway -dns=dns_addr -domain=dns_domain
    Note: The -dns= and -domain= arguments are optional when accessing by IP address and not by name.
  5. At the boot environment prompt, perform netboot on the new node: netboot http://path_to_the_web-accessible_directory/netboot/kernel
    The path_to_the_web-accessible_directory is the location of the downloaded netboot.tgz file.
  6. From the boot menu, select option (7) Install new software first to download and install the new software image to the boot device.
    Disregard the following message: "This procedure is not supported for Non-Disruptive Upgrade on an HA pair". It applies to nondisruptive upgrades of software, not to upgrades of controllers.
  7. If you are prompted to continue the procedure, enter y, and when prompted for the package, enter the URL of the image file: http://path_to_the_web-accessible_directory/image.tgz.
    If the system prompts you for the user name, you can press Enter to continue.
  8. Enter n to skip the backup recovery when you see a prompt similar to the following:
    Do you want to restore the backup configuration now? {y|n}
  9. Reboot by entering y when you see a prompt similar to the following:
    The node must be rebooted to start using the newly installed software. Do you want to reboot now? {y|n}
  10. Interrupt the reboot process by pressing Ctrl-C to display the boot menu when the system prompts you to do so.
  11. From the boot menu, select (5) Maintenance mode boot to access Maintenance mode.
  12. If necessary, make changes to the FC or CNA ports on the node, and then reboot the node to Maintenance mode.
  13. From Maintenance mode, verify that the controller and chassis settings have the correct HA state: ha-config show
    You should verify that the command output shows ha:
    *> ha-config show
       Chassis HA configuration: ha
       Controller HA configuration: ha
    

    Systems record in a PROM whether they are in an HA pair or stand-alone configuration. The state must be the same on all components within the stand-alone system or HA pair

    The ha-config modify controller ha command configures ha for the controller setting. The ha-config modify chassis ha command configures ha for the chassis setting.

    ONTAP 9 High-Availability Configuration Guide

    Find the High-Availability Configuration Guide for your version of Data ONTAP 8

  14. If the system asks you whether to destroy the local mailboxes, enter y to confirm.
  15. Exit Maintenance mode: halt
    The system stops at the boot environment prompt.