Netbooting and setting up Data ONTAP on the new controller module

You must perform a specific sequence of steps to boot and install the operating system on the new controller module.

About this task

This procedure includes initializing disks. The amount of time you need to initialize the disks depends on the size of the disks.

If your system does not use disk partitioning, the system automatically assigns two disks to the new controller module.

Physical Storage Management Guide

ONTAP 9 Disks and Aggregates Power Guide

Steps

  1. If you are running Data ONTAP 8.2.x or earlier, set the following boot environment variable at the LOADER prompt (LOADER>, LOADER-A>, or LOADER-B>) on the target node console: setenv bootarg.init.boot_clustered true
    Note: This step applies only to systems running Data ONTAP.
  2. Configure the IP address of the new controller module at the LOADER prompt:
    If DHCP is... Then enter...
    Available ifconfig e0M -auto
    Not available 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 DNS (Domain Name System) 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.
  3. Perform netboot at the LOADER prompt: netboot http://path_to_web-accessible_directory/netboot/kernel
  4. Select the Install new software first option from the displayed menu.
  5. Enter y when prompted regarding the installation of the alternate software, from which the node is not running currently.
  6. Enter the path to the image.tgz file when prompted.
    Example
    What is the URL for the package?
    http://path_to_web-accessible_directory/image.tgz
  7. Enter n to skip the backup recovery when prompted:
    Example
    ****************************************************************
    *             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 the SSH server.  Refer to the Boot Device Replacement  *
    *  guide for more details.                                     *
    *  Choose No to skip the backup recovery and return to the     *
    *  boot menu.                                                  *
    ****************************************************************
    
    Do you want to restore the backup configuration
    now? {y|n} n
  8. Reboot by entering y when prompted to do so.
    The node must be rebooted to start using the newly installed software. Do you want to
    reboot now? {y|n}y
  9. If necessary, select the option to Clean configuration and initialize all disks after the node has booted.
    Because you are configuring a new controller module and the disks for the new controller module are empty, you can respond y when the system warns you that selecting this option erases data in all of the disks.
    Note: The amount of time needed to initialize the disks depends on the size of your disks and configuration.
  10. Respond to the applicable wizard:
    If you are running ... Then...
    Data ONTAP 8.2.x or earlier The Cluster Setup wizard starts after the disks are initialized:
    1. Enter the node management information, as prompted by the wizard.
    2. Go to step 11.
    ONTAP 8.3 or later The Node Setup wizard starts after the disks are initialized:
    1. Enter the node management LIF information on the console, as shown in the following example:
      Welcome to node setup.
      
      You can enter the following commands at any time:
        "help" or "?" - if you want to have a question clarified,
        "back" - if you want to change previously answered questions, and
        "exit" or "quit" - if you want to quit the cluster setup wizard.
           Any changes you made before quitting will be saved.
      
      To accept a default or omit a question, do not enter a value.
      
      This system will send event messages and weekly reports to NetApp 
      Technical Support. To disable this feature, enter "autosupport 
      modify -support disable" within 24 hours. Enabling AutoSupport can 
      significantly speed problem determination and resolution should 
      a problem occur on your system.
      For further information on AutoSupport, please see:
      http://support.netapp.com/autosupport/
      
      
      Type yes to confirm and continue{yes}: yes
      
      Enter the node management interface port [e0M]:
      Enter the node management interface IP address: 10.98.230.86  
      Enter the node management interface netmask: 255.255.240.0
      Enter the node management interface default gateway: 10.98.224.1
      A node management interface on port e0c with IP address 10.98.230.86 has been created.
      
      This node has its management address assigned and is ready for cluster setup.
      
      To complete cluster setup after all nodes are ready, download and run the System Setup utility from the 
      NetApp Support Site and use it to discover the configured nodes.
      
      For System Setup, this node's management address is: 10.98.230.86
    2. Manually enter the admin login ID when prompted to do so.
    3. Manually start the Cluster Setup wizard at the prompt: cluster setup
  11. With the Cluster Setup wizard running, join the node to the cluster: join
    Example
    Welcome to the cluster setup wizard.
    
    You can enter the following commands at any time:
      "help" or "?" - if you want to have a question clarified,
      "back" - if you want to change previously answered questions, and
      "exit" or "quit" - if you want to quit the cluster setup wizard.
         Any changes you made before quitting will be saved.
    
    You can return to cluster setup at any time by typing "cluster setup".
    To accept a default or omit a question, do not enter a value.
    
    
    Do you want to create a new cluster or join an existing cluster? {create, join}: join
    Note: The cluster join fails if the existing node is configured for a two-port cluster and in some cases when the new node uses the default port (8040, 8060, and 8080 systems, which have four cluster ports by default). You need to exit cluster setup, and then run the network port modify -ipspace command so that only the ports intended for the cluster network are checked during setup.
  12. Respond yes when prompted to set storage failover to HA mode.
    Example
    Non-HA mode, Reboot node to activate HA
    
    Warning: Ensure that the HA partner has started disk initialization before
    rebooting this node to enable HA.
    Do you want to reboot now to set storage failover (SFO) to HA mode?
    {yes, no} [yes]: yes
    
    Rebooting now
    
    After the node reboots, the Cluster Setup wizard displays "Welcome to node setup" and prompts you to complete the node setup.
  13. Respond to the remaining prompts as appropriate for your site.
    The Clustered Data ONTAP Software Setup Guide for your version of ONTAP contains additional details.
  14. If the system is a two-node switchless cluster configuration, create the cluster interfaces on the existing node to create cluster LIFs on the cluster ports: network interface create
    Example
    The following example shows how to create a cluster LIF on one of the node's cluster ports. The -auto parameter configures the LIF to use a link-local IP address:
    cluster1::> network interface create -vserver Cluster -lif clus1 -role cluster -home-node node0 -home-port e1a -auto true
  15. After setup is complete, verify that the node is healthy and eligible to participate in the cluster: cluster show
    Example
    The following example shows a cluster after the second node (cluster1-02) has been joined to it:
    cluster1::> cluster show
    Node                  Health  Eligibility
    --------------------- ------- ------------
    cluster1-01           true    true
    cluster1-02           true    true
    
    You can access the Cluster Setup wizard to change any of the values that you entered for the admin Storage Virtual Machine (SVM) or node SVM by using the cluster setup command.