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

使用替換的系統模組來啟動 node1

貢獻者
PDF

節點 1 及替換模組現已準備好開機。支援的替換模組列於"支援的系統對照表"中。

註

更換控制器模組時，請將所有連線從舊連接移至更換的控制器模組。

更換控制器和 NVRAM 模組時，請僅移動主控台和管理連線。
步驟

  1. （僅限 AFF A250 ， AFF C250 ， AFF A800 或 AFF C800 升級）在 Loader 提示下，進入維護模式：

    Boot_ONTAP maint

    1. `y`請選擇混合式平台確認提示。

    2. 回答 yes 確認提示。

    3. 顯示 100GbE 介面的狀態：

      storage port show。

      所有連接至 NS224 機櫃或儲存交換器的 100GbE 連接埠都應報告為 storage 連接埠、如下面的輸出範例所示。

    *> storage port show
Port Type Mode    Speed(Gb/s) State    Status  VLAN ID
---- ---- ------- ----------- -------- ------- -------
e8a  ENET storage 100 Gb/s    enabled  online  30
e8b  ENET storage 100 Gb/s    enabled  online  30
e11a ENET storage 100 Gb/s    enabled  online  30
e11b ENET storage 100 Gb/s    enabled  online  30

    1. 結束維護模式：

      《停止》

  2. 如果您安裝了 NetApp 儲存加密（ NSE ）磁碟機、請執行下列步驟。

    註 如果您尚未在程序中稍早完成此作業、請參閱知識庫文章 "如何判斷磁碟機是否已通過 FIPS 認證" 以判斷使用中的自我加密磁碟機類型。

    1. 設定 bootarg.storageencryption.support 至 true 或 false：

      如果下列磁碟機正在使用中… 然後…

      符合 FIPS 140-2 第 2 級自我加密要求的 NSE 磁碟機

      setenv bootarg.storageencryption.support true

      NetApp非FIPS SED

      setenv bootarg.storageencryption.support false
      註

      您無法在同一個節點或HA配對上混用FIPS磁碟機與其他類型的磁碟機。您可以在同一個節點或HA配對上混合使用SED與非加密磁碟機。

    2. 前往特殊開機功能表並選取選項 (10) Set Onboard Key Manager recovery secrets。

      輸入您先前記錄的複雜密碼和備份資訊。請參閱 "使用 Onboard Key Manager 管理儲存加密"。

  3. 將節點開機至開機功能表：

    Boot_ONTAP功能表

  4. 輸入「 22/7 」並選取隱藏選項、將舊的 node1 磁碟重新指派給更換的 node1 boot_after_controller_replacement 當節點停止在開機功能表時。

    短暫延遲之後、系統會提示您輸入要取代的節點名稱。如果有共享磁碟（也稱為進階磁碟分割（ADP）或分割磁碟）、系統會提示您輸入HA合作夥伴的節點名稱。

    這些提示可能會被隱藏在主控台訊息中。如果您未輸入節點名稱或輸入不正確的名稱、系統會提示您再次輸入名稱。

    註

    如果「[localhost:disk.encrectNoSupport:alert]：偵測到FIPS認證的加密磁碟機」、或「[localhost:diskown。errordiningio:error]：發生磁碟錯誤時發生錯誤3（磁碟故障）、請執行下列步驟：

    1. 在載入程式提示下停止節點。

    2. 檢查並重設中提及的儲存加密 步驟2設備。

    3. 在載入程式提示下、開機：

      Boot_ONTAP

    您可以使用下列範例做為參考：

    展開主控台輸出範例 
    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:
    註

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

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