Skip to main content
简体中文版经机器翻译而成，仅供参考。如与英语版出现任何冲突，应以英语版为准。

使用替代系统模块启动node1

贡献者
PDF

包含替代模块的node1现在可启动。本节介绍了在以下升级配置中使用替代模块启动node1所需的步骤：

现有node1控制器 更换node1系统模块

AFF A800

AFF A90或AFF A70 1

配置为ASA的AFF A220

AFF A150控制器模块1

AFF A220
AFF A200
AFF C190

AFF A150控制器模块1

FAS2620
FAS2720

FAS2820控制器模块1

配置为ASA的AFF A700

ASA A900控制器和NVRAM模块2

AFF A700

AFF A900控制器和NVRAM模块2

FAS9000

FAS9500控制器和NVRAM模块2

1更换控制器模块时、您需要将所有连接从旧控制器模块移至更换控制器模块。

2在更换控制器和NVRAM模块时、只需移动控制台和管理连接即可。

步骤

  1. (仅限AFF A800升级)在加载程序提示符处、进入维护模式：

    boot_ontap maint

    1. 回答 yes 确认提示。

    2. 显示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. 退出维护模式：

      halt

  2. 如果您安装了NetApp存储加密(NSE)驱动器、请执行以下步骤。

    备注 如果您之前尚未在操作步骤 中执行此操作、请参见知识库文章 "如何判断驱动器是否已通过FIPS认证" 确定正在使用的自加密驱动器的类型。

    1. 设置 bootarg.storageencryption.support to 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。

      输入先前记录的操作步骤 密码短语和备份信息。请参见 "使用板载密钥管理器管理存储加密"。

  3. 将节点启动至启动菜单：

    boot_ontap 菜单

  4. 输入"22/7"并选择隐藏选项、将旧的node1磁盘重新分配给替代node1 boot_after_controller_replacement 节点停留在启动菜单处。

    经过短暂延迟后、系统将提示您输入要替换的节点的名称。如果存在共享磁盘(也称为高级磁盘分区(Advanced Disk Partitioning、ADP)或分区磁盘)、系统将提示您输入HA配对节点的节点名称。

    这些提示可能会被埋在控制台消息中。如果未输入节点名称或输入的名称不正确、系统将提示您重新输入此名称。

    备注

    如果` localhost：disk.encryptNoSupport：aler]：检测到FIPS认证的加密驱动器`和、或`、则执行以下步骤：localhost：diskown.errorDuringIO：error]：disk` error 3 (disk failed) on disk error occur、则执行以下步骤：

    1. 在LOADER提示符处暂停节点。

    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 更新。