Skip to content

Latest commit

 

History

History
81 lines (66 loc) · 3.49 KB

install_boot_node3.adoc

File metadata and controls

81 lines (66 loc) · 3.49 KB
Raw
sidebar permalink keywords summary
sidebar
upgrade-arl-auto/install_boot_node3.html
install, boot, node3 relocation, nodes, V-series, storage disks
Install and boot node3 and install ONTAP software when upgrading controllers running ONTAP 9.5 to 9.7 by using `system controller replace` commands.

Install and boot node3

  1. 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 entering the following command at the boot environment prompt:
    ifconfig e0M -auto

    Not running

    Manually configure the connection by entering 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 (mandatory).
    netmask is the network mask of the storage system (mandatory).
    gateway is the gateway for the storage system. (mandatory).
    dns_addr is the IP address of a name server on your network (optional).
    dns_domain is the Domain Name Service (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. Enter help ifconfig at the firmware prompt for details.

  1. If you have NetApp Storage Encryption (NSE) drives installed, perform the following steps.

    Note
    		 If you have not already done so earlier in the procedure, see the Knowledge Base article How to tell if a drive is FIPS certified to determine the type of self-encrypting drives that are in use.

    1. Set bootarg.storageencryption.support to true or false:

      If the following drives are in use… Then…

      NSE drives that conform to FIPS 140-2 Level 2 self-encryption requirements

      setenv bootarg.storageencryption.support true

      NetApp non-FIPS SEDs

      setenv bootarg.storageencryption.support false
      Note

      You cannot mix FIPS drives with other types of drives on the same node or HA pair.
      You can mix SEDs with non-encrypting drives on the same node or HA pair.

    2. Contact NetApp Support for assistance with restoring the onboard key management information.

  2. Boot node into boot menu:

    boot_ontap menu

    If you do not have an FC or UTA/UTA2 configuration, perform Check and configure UTA/UTA2 ports on node4, Step 15 so that node4 can recognize node2’s disks.

  3. For a MetroCluster configuration, V-Series systems and systems with FlexArray Virtualization software connected to storage arrays,
    go to Check and configure UTA/UTA2 ports on node3, Step 15.