Netboot node1

Contributors netapp-pcarriga

After swapping the corresponding AFF A900 node1 controller module and NVRAM module, you must netboot node1. The term netboot means that you are booting from an ONTAP image stored on a remote server. When preparing for netboot, you must add a copy of the ONTAP 9 boot image onto a web server that the system can access.

It is not possible to check the version of ONTAP installed on the boot media of an AFF A900 controller module unless it is installed in a chassis and powered ON. The ONTAP version on the AFF A900 boot media must be same as the ONTAP version running on the AFF A700 system that is being upgraded and both the primary and backup boot images must match. You can configure the images by performing a netboot followed by the wipeconfig command from the boot menu. If the controller module was previously used in another cluster, the wipeconfig command clears any residual configuration on the boot media.

Before you begin
  • Verify that you can access a HTTP server with the system.

  • Download the necessary system files for your system and the correct version of ONTAP from the NetApp Support Site. Refer to References to link to the NetApp Support Site.

About this task

You must netboot the new controllers if they do not have the same version of ONTAP 9 installed on them that is installed on the original controllers. After you install each new controller, you boot the system from the ONTAP 9 image stored on the web server. You can then download the correct files to the boot media device for subsequent system boots.

Steps
  1. Refer to References to link to the NetApp Support Site to download the files used for performing the netboot of the system.

  2. Download the appropriate ONTAP software from the software download section of the NetApp Support Site and store the <ontap_version>_image.tgz file on a web-accessible directory.

  3. Change to the web-accessible directory and verify that the files you need are available.

  4. Your directory listing should contain <ontap_version>_image.tgz.

  5. Configure the netboot connection by choosing one of the following actions.

    Note You must use the management port and IP as the netboot connection. Do not use a data LIF IP or a data outage might occur while the upgrade is being performed.
    If Dynamic Host Configuration Protocol (DHCP) is…​ Then…​

    Running

    Configure the connection automatically by using the following command at the boot environment prompt:
    ifconfig e0M -auto

    Not running

    Manually configure the connection by using the following command at the boot environment prompt:
    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. This parameter is optional.
    <dns_domain> is the Domain Name Service (DNS) domain name. This parameter is optional.

    Note Other parameters might be necessary for your interface. Enter help ifconfig at the firmware prompt for details.
  6. Perform netboot on node1:

    netboot http://<web_server_ip/path_to_web_accessible_directory>/netboot/kernel

    Note Do not interrupt the boot.
  7. Wait for the node1 now running on the AFF A900 controller module to boot and display the boot menu options as shown below:

    Please choose one of the following:
    
    (1)  Normal Boot.
    (2)  Boot without /etc/rc.
    (3)  Change password.
    (4)  Clean configuration and initialize all disks.
    (5)  Maintenance mode boot.
    (6)  Update flash from backup config.
    (7)  Install new software first.
    (8)  Reboot node.
    (9)  Configure Advanced Drive Partitioning.
    (10) Set Onboard Key Manager recovery secrets.
    (11) Configure node for external key management.
    Selection (1-11)?
  8. From the boot menu, select option (7) Install new software first.

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

    Note

    Disregard the following message: This procedure is not supported for Non-Disruptive Upgrade on an HA pair. This note applies to nondisruptive ONTAP software upgrades, and not controller upgrades.

    Always use netboot to update the new node to the desired image. If you use another method to install the image on the new controller, the wrong image might install. This issue applies to all ONTAP releases.

  9. If you are prompted to continue the procedure, enter y, and when prompted for the package, enter the URL:
    http://<web_server_ip/path_to_web-accessible_directory>/<ontap_version>_image.tgz

    The <path_to_the_web-accessible_directory> should lead to where you downloaded the <ontap_version>_image.tgz in Step 2.

  10. Complete the following substeps to reboot the controller module:

    1. Enter n to skip the backup recovery when you see the following prompt:

      Do you want to restore the backup configuration now? {y|n}
    2. Enter y to reboot when you see the following prompt:

      The node must be rebooted to start using the newly installed software. Do you want to reboot now? {y|n}

      The controller module reboots but stops at the boot menu because the boot device was reformatted, and the configuration data must be restored.

  11. At the prompt, run the wipeconfig command to clear any previous configuration on the boot media:

    1. When you see the message below, answer yes:

      This will delete critical system configuration, including cluster membership.
      Warning: do not run this option on a HA node that has been taken over.
      Are you sure you want to continue?:
    2. The node reboots to finish the wipeconfig and then stops at the boot menu.

  12. Select option 5 to go to maintenance mode from the boot menu. Answer yes to the prompts until the node stops at maintenance mode and the command prompt *>.

  13. Verify that the controller and chassis are configured as ha:

    ha-config show

    The following example shows the output of the ha-config show command:

    Chassis HA configuration: ha
    Controller HA configuration: ha
  14. If the controller and chassis are not configured as ha, use the following commands to correct the configuration:

    ha-config modify controller ha

    ha-config modify chassis ha

  15. Verify the ha-config settings:

    ha-config show

    Chassis HA configuration: ha
    Controller HA configuration: ha
  16. Halt node1:

    halt

    Node1 should stop at the LOADER prompt.

  17. On node2, check the system date, time, and time zone:

    date

  18. On node1, check the date by using the following command at the boot environment prompt:

    show date

  19. If necessary, set the date on node1:

    set date <mm/dd/yyyy>

    Note Set the corresponding UTC date on node1.
  20. On node1, check the time by using the following command at the boot environment prompt:

    show time

  21. If necessary, set the time on node1:

    set time <hh:mm:ss>

    Note Set the corresponding UTC time on node1.
  22. Set the partner system ID on node1:

    setenv partner-sysid <node2_sysid>

    You can obtain the node2 system ID from the node show -node <node2> command output on node2.

    1. Save the settings:

      saveenv

  23. On node1, at the LOADER prompt, verify the partner-sysid for node1:

    printenv partner-sysid

    For node1, the partner-sysid must be that of node2.