本繁體中文版使用機器翻譯,譯文僅供參考,若與英文版本牴觸,應以英文版本為準。

使用AFF FASA900或FAS9500控制器和NVRAM模組來開機節點2

貢獻者

節點2搭配AFF EscoreA900或FAS9500控制器和NVRAM模組、現在已準備好升級。透過交換控制器和NVRAM模組、將「從A 700升級至e a 900」或「FAS9000升級至FAS9500」只需移動主控台和管理連線即可。AFF AFF本節提供使用AFF E4A900或FAS9500控制器和NVRAM模組來開機節點2所需的步驟。

步驟
  1. 如果此組態正在使用NetApp儲存加密(NSE)、則必須將「setenv bootarg.storageEncryption.support’命令設定為「true」、並將「kmip.init.maxwait`變數」設定為「Off」、以避免在節點2組態載入後發生開機迴圈:

    「etenv bootarg.storageencryption。支援true」

    「kmip.init.maxwait關」

  2. 將節點開機至「boot_menu」:

    Boot_ONTAP功能表

  3. 節點會在開機功能表停止。輸入「22/7」、然後選取隱藏選項「boot_after控制器置換」。若要重新指派AFF EscoreA700或FAS9000節點1磁碟到AFF EsceA900或FAS9500節點1、請在提示字元下輸入節點2的實際節點名稱。請參考下列範例:

    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:
    附註

    在前述主控台輸出範例中、ONTAP 如果系統使用進階磁碟分割(ADP)磁碟、則會提示您輸入合作夥伴節點名稱。

    上例所示的系統ID為範例ID。您要升級之節點的實際系統ID會有所不同。

    在提示輸入節點名稱與登入提示之間、節點會重新開機數次、以還原環境變數、更新系統卡上的韌體、以及進行其他ONTAP 的更新。