Boot node2 with the AFF A900 controller module and NVRAM module

Contributors netapp-pcarriga

Node2 with the AFF A900 controller module and NVRAM module is now ready for upgrade. Upgrading from an AFF A700 to an AFF A900 by swapping the controller module and NVRAM module involves moving only the console and management connections. This section provides the steps required to boot node2 with the AFF A900 controller module and NVRAM module.

Steps
  1. If NetApp Storage Encryption (NSE) is in use on this configuration, the setenv bootarg.storageencryption.support command must be set to true, and the kmip.init.maxwait variable must be set to off to avoid a boot loop after the node2 configuration is loaded:

    setenv bootarg.storageencryption.support true

    setenv kmip.init.maxwait off

  2. Boot the node into boot_menu:

    boot_ontap menu

  3. The node stops at the boot menu. Enter "22/7" and select the hidden option boot_after_controller_replacement. To reassign the AFF A700 node1 disks to AFF A900 node1, at the prompt, enter the actual node name of node2. Use the following example as a reference:

    LOADER-A> boot_ontap menu
    .
    .
    <output truncated>
    .
    All rights reserved.
    *******************************
    *                             *
    * Press Ctrl-C for Boot Menu. *
    *                             *
    *******************************
    .
    <output truncated>
    .
    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)? 22/7
    
    (22/7)                          Print this secret List
    (25/6)                          Force boot with multiple filesystem disks missing.
    (25/7)                          Boot w/ disk labels forced to clean.
    (29/7)                          Bypass media errors.
    (44/4a)                         Zero disks if needed and create new flexible root volume.
    (44/7)                          Assign all disks, Initialize all disks as SPARE, write DDR labels
    .
    .
    <output truncated>
    .
    .
    (wipeconfig)                        Clean all configuration on boot device
    (boot_after_controller_replacement) Boot after controller upgrade
    (boot_after_mcc_transition)         Boot after MCC transition
    (9a)                                Unpartition all disks and remove their ownership information.
    (9b)                                Clean configuration and initialize node with partitioned disks.
    (9c)                                Clean configuration and initialize node with whole disks.
    (9d)                                Reboot the node.
    (9e)                                Return to main boot menu.
    
    
    
    The boot device has changed. System configuration information could be lost. Use option (6) to restore the system configuration, or option (4) to initialize all disks and setup a new system.
    Normal Boot is prohibited.
    
    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)? boot_after_controller_replacement
    
    This will replace all flash-based configuration with the last backup to disks. Are you sure you want to continue?: yes
    
    .
    .
    <output truncated>
    .
    .
    Controller Replacement: Provide name of the node you would like to replace:<nodename of the node being replaced>
    Changing sysid of node node1 disks.
    Fetched sanown old_owner_sysid = 536940063 and calculated old sys id = 536940063
    Partner sysid = 4294967295, owner sysid = 536940063
    .
    .
    <output truncated>
    .
    .
    varfs_backup_restore: restore using /mroot/etc/varfs.tgz
    varfs_backup_restore: attempting to restore /var/kmip to the boot device
    varfs_backup_restore: failed to restore /var/kmip to the boot device
    varfs_backup_restore: attempting to restore env file to the boot device
    varfs_backup_restore: successfully restored env file to the boot device wrote key file "/tmp/rndc.key"
    varfs_backup_restore: timeout waiting for login
    varfs_backup_restore: Rebooting to load the new varfs
    Terminated
    <node reboots>
    
    System rebooting...
    
    .
    .
    Restoring env file from boot media...
    copy_env_file:scenario = head upgrade
    Successfully restored env file from boot media...
    Rebooting to load the restored env file...
    .
    System rebooting...
    .
    .
    .
    <output truncated>
    .
    .
    .
    .
    WARNING: System ID mismatch. This usually occurs when replacing a boot device or NVRAM cards!
    Override system ID? {y|n} y
    .
    .
    .
    .
    Login:
    Note

    In the preceding console output example, ONTAP will prompt you for the partner node name if the system uses Advanced Disk Partitioning (ADP) disks.

    The system IDs shown in the preceding example are example IDs. The actual system IDs of the nodes that you are upgrading will be different.

    Between entering node names at the prompt and the login prompt, the node reboots a few times to restore the environment variables, update firmware on the cards in the system, and for other ONTAP updates.