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

更换 Cisco Nexus 9336C-x2 共享交换机

贡献者

您可以更换有故障的Nexus 9336C-x2共享交换机。这是无中断操作步骤 (NDU)。

您需要的内容

在执行交换机更换之前、请确保:

  • 在现有集群和网络基础架构中:

    • 现有集群已通过验证可完全正常运行、并且至少有一个完全连接的集群交换机。

    • 所有集群端口均为*启动*。

    • 所有集群逻辑接口(LIF)均为*启动*并位于其主端口上。

    • ONTAP cluster ping-cluster -node node1 命令必须指示所有路径上的基本连接以及大于 PMTU 的通信均成功。

  • 对于Nexus 9336C-x2更换交换机:

    • 替代交换机上的管理网络连接正常工作。

    • 可以通过控制台访问替代交换机。

    • 节点连接为端口 1/1 到 1/34 :

    • 端口1/35和1/36上的所有交换机间链路(ISL)端口均已禁用。

    • 所需的参考配置文件(Reference Configuration File、RCF)和NX-OS操作系统映像交换机将加载到此交换机上。

    • 之前的任何站点自定义设置,例如 STP , SNMP 和 SSH ,都应复制到新交换机。

关于示例

您必须执行命令,从托管集群 LIF 的节点迁移集群 LIF 。

此操作步骤中的示例使用以下交换机和节点命名:

  • 现有 Nexus 9336C-f2 交换机的名称是 SH1SH2

  • 新 Nexus 9336C-fx2 交换机的名称是 newsh1newsh2

  • 节点名称为 node1node2

  • 每个节点上的集群端口均名为 e3Ae3b

  • 集群 LIF 名称是 node1 的 node1_clus1node1_clus2 , node2 的 node2_clus1node2_clus2

  • 对所有集群节点进行更改的提示为 cluster1 ::: * > 。

    备注 以下操作步骤基于以下网络拓扑:
显示示例拓扑
cluster1::*> network port show -ipspace Cluster

Node: node1
                                                                        Ignore
                                                  Speed(Mbps)  Health   Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
--------- ------------ ---------------- ---- ---- ------------ -------- ------
e3a       Cluster      Cluster          up   9000  auto/100000 healthy  false
e3b       Cluster      Cluster          up   9000  auto/100000 healthy  false

Node: node2
                                                                        Ignore
                                                  Speed(Mbps)  Health   Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
--------- ------------ ---------------- ---- ---- ------------ -------- ------
e3a       Cluster      Cluster          up   9000  auto/100000 healthy  false
e3b       Cluster      Cluster          up   9000  auto/100000 healthy  false
4 entries were displayed.


cluster1::*> network interface show -vserver Cluster
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
            node1_clus1  up/up    169.254.209.69/16  node1         e3a     true
            node1_clus2  up/up    169.254.49.125/16  node1         e3b     true
            node2_clus1  up/up    169.254.47.194/16  node2         e3a     true
            node2_clus2  up/up    169.254.19.183/16  node2         e3b     true
4 entries were displayed.

cluster1::*> network device-discovery show -protocol cdp
Node/       Local  Discovered
Protocol    Port   Device (LLDP: ChassisID)  Interface         Platform
----------- ------ ------------------------- ----------------  ----------------
node2      /cdp
            e3a    sh1                       Eth1/2            N9K-C9336C
            e3b    sh2                       Eth1/2            N9K-C9336C

node1      /cdp
            e3a    sh1                       Eth1/1            N9K-C9336C
            e3b    sh2                       Eth1/1            N9K-C9336C
4 entries were displayed.

sh1# show cdp neighbors
Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater,
                  V - VoIP-Phone, D - Remotely-Managed-Device,
                  s - Supports-STP-Dispute
Device-ID          Local Intrfce  Hldtme Capability  Platform      Port ID
node1              Eth1/1         144    H           FAS2980       e3a
node2              Eth1/2         145    H           FAS2980       e3a
sh2                Eth1/35        176    R S I s     N9K-C9336C    Eth1/35
sh2 (FDO220329V5)   Eth1/36       176    R S I s     N9K-C9336C    Eth1/36
Total entries displayed: 4

sh2# show cdp neighbors
Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater,
                  V - VoIP-Phone, D - Remotely-Managed-Device,
                  s - Supports-STP-Dispute
Device-ID          Local Intrfce  Hldtme Capability  Platform      Port ID
node1              Eth1/1         139    H           FAS2980       eb
node2              Eth1/2         124    H           FAS2980       eb
sh1                Eth1/35        178    R S I s     N9K-C9336C    Eth1/35
sh1                Eth1/36        178    R S I s     N9K-C9336C    Eth1/36
Total entries displayed: 4
步骤
  1. 如果在此集群上启用了 AutoSupport ,则通过调用 AutoSupport 消息禁止自动创建案例:

    ssystem node AutoSupport invoke -node * -type all -message MAINT=xh

    其中 x 是维护时段的持续时间,以小时为单位。

  2. 可选:在交换机 newsh2 上安装相应的 RCF 和映像,并进行必要的站点准备。

    1. 如有必要,请验证,下载并安装适用于新交换机的 RCF 和 NX-OS 软件的相应版本。如果您已确认新交换机设置正确,并且不需要更新 RCF 和 NX-OS 软件,请继续执行 第 3 步

    2. 转至 NetApp 支持站点上的 NetApp 集群和管理网络交换机参考配置文件问题描述页面。

    3. 单击 "Cluster Network and Management Network Compatibility Matrix (集群网络和管理网络兼容性表) " 的链接,然后记下所需的交换机软件版本。

    4. 单击浏览器的后退箭头以返回到问题描述页面,单击继续,接受许可协议,然后转到下载页面。

    5. 按照下载页面上的步骤下载与您要安装的 ONTAP 软件版本对应的正确 RCF 和 NX-OS 文件。

  3. 在新交换机上,以 admin 身份登录并关闭将连接到节点集群接口(端口 1/1 到 1/34 )的所有端口。如果要更换的交换机无法正常工作并已关闭电源,请转至 第 4 步。集群节点上的 LIF 应已故障转移到每个节点的另一个集群端口。

    显示示例
    newsh2# config
    Enter configuration commands, one per line. End with CNTL/Z.
    newsh2(config)# interface e1/1-34
    newsh2(config-if-range)# shutdown
  4. 【第 4 步】验证所有集群 LIF 是否均已启用自动还原。

    network interface show - vserver Cluster -fields auto-revert

    显示示例
    cluster1::> network interface show -vserver Cluster -fields auto-revert
                 Logical
    Vserver      Interface     Auto-revert
    ------------ ------------- -------------
    Cluster      node1_clus1   true
    Cluster      node1_clus2   true
    Cluster      node2_clus1   true
    Cluster      node2_clus2   true
    4 entries were displayed.
  5. 验证远程集群接口的连接:

ONTAP 9.9.1及更高版本

您可以使用 network interface check cluster-connectivity 命令启动集群连接的可访问性检查、然后显示详细信息:

network interface check cluster-connectivity startnetwork interface check cluster-connectivity show

cluster1::*> network interface check cluster-connectivity start

*注:*请等待几秒钟、然后再运行 `show`命令以显示详细信息。

cluster1::*> network interface check cluster-connectivity show
                                  Source           Destination      Packet
Node   Date                       LIF              LIF              Loss
------ -------------------------- ---------------- ---------------- -----------
node1
       3/5/2022 19:21:18 -06:00   node1_clus2      node2-clus1      none
       3/5/2022 19:21:20 -06:00   node1_clus2      node2_clus2      none
node2
       3/5/2022 19:21:18 -06:00   node2_clus2      node1_clus1      none
       3/5/2022 19:21:20 -06:00   node2_clus2      node1_clus2      none
所有ONTAP版本

对于所有ONTAP版本、您还可以使用 cluster ping-cluster -node <name> 用于检查连接的命令:

cluster ping-cluster -node <name>

cluster1::*> cluster ping-cluster -node local
Host is node2
Getting addresses from network interface table...
Cluster node1_clus1 169.254.209.69 node1 e3a
Cluster node1_clus2 169.254.49.125 node1 e3b
Cluster node2_clus1 169.254.47.194 node2 e3a
Cluster node2_clus2 169.254.19.183 node2 e3b
Local = 169.254.47.194 169.254.19.183
Remote = 169.254.209.69 169.254.49.125
Cluster Vserver Id = 4294967293
Ping status:
....
Basic connectivity succeeds on 4 path(s)
Basic connectivity fails on 0 path(s)
................
Detected 9000 byte MTU on 4 path(s):
Local 169.254.47.194 to Remote 169.254.209.69
Local 169.254.47.194 to Remote 169.254.49.125
Local 169.254.19.183 to Remote 169.254.209.69
Local 169.254.19.183 to Remote 169.254.49.125
Larger than PMTU communication succeeds on 4 path(s)
RPC status:
2 paths up, 0 paths down (tcp check)
2 paths up, 0 paths down (udp check)
  1. 【第 6 步】关闭 Nexus 9336C-x2 交换机 SH1 上的 ISL 端口 1/35 和 1/36 。

    显示示例
    sh1# configure
    Enter configuration commands, one per line. End with CNTL/Z.
    sh1(config)# interface e1/35-36
    sh1(config-if-range)# shutdown
  2. 【第 7 步】从 Nexus 9336C-x2 SH2 交换机上拔下所有缆线,然后将其连接到 Nexus C9336C-Fx2 newsh2 交换机上的相同端口。

  3. 启动 SH1 和 newsh2 交换机之间的 ISL 端口 1/35 和 1/36 ,然后验证端口通道操作状态。

    端口通道应指示 PO1 ( SU ),成员端口应指示 Eth1/35 ( P )和 Eth1/36 ( P )。

    显示示例

    此示例将启用 ISL 端口 1/35 和 1/36 ,并显示交换机 SH1 上的端口通道摘要。

    sh1# configure
    Enter configuration commands, one per line. End with CNTL/Z.
    sh1 (config)# int e1/35-36
    sh1 (config-if-range)# no shutdown
    sh1 (config-if-range)# show port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            b - BFD Session Wait
            S - Switched    R - Routed
            U - Up (port-channel)
            p - Up in delay-lacp mode (member)
            M - Not in use. Min-links not met
    --------------------------------------------------------------------------------
    Group Port-       Type     Protocol  Member       Ports
          Channel
    --------------------------------------------------------------------------------
    1     Po1(SU)     Eth      LACP      Eth1/35(P)   Eth1/36(P)
    
    sh1 (config-if-range)#
  4. 【第9步】验证所有节点上的端口e3b是否已启动:

    network port show -ipspace cluster

    显示示例

    输出应如下所示:

    cluster1::*> network port show -ipspace Cluster
    
    Node: node1
                                                                             Ignore
                                                       Speed(Mbps)  Health   Health
    Port      IPspace      Broadcast Domain Link MTU   Admin/Oper   Status   Status
    --------- ------------ ---------------- ---- ----- ---------- - - -------- ----
    e3a       Cluster      Cluster          up   9000  auto/100000  healthy  false
    e3b       Cluster      Cluster          up   9000  auto/100000  healthy  false
    
    Node: node2
                                                                             Ignore
                                                       Speed(Mbps)  Health   Health
    Port      IPspace      Broadcast Domain Link MTU   Admin/Oper   Status   Status
    --------- ------------ ---------------- ---- ----- ----------- -  -------- ----
    e3a       Cluster      Cluster          up   9000  auto/100000  healthy  false
    e3b       Cluster      Cluster          up   9000  auto/auto    -        false
    4 entries were displayed.
  5. 在上一步使用的同一节点上,使用 network interface revert 命令还原上一步中与端口关联的集群 LIF 。

    在此示例中,如果 Home 值为 true 且端口为 e3b ,则 node1 上的 LIF node1_clus2 将成功还原。

    以下命令会将 node1 上的 LIF node1_clus2 返回到主端口 E3a ,并显示有关两个节点上的 LIF 的信息。如果两个集群接口的 "Is Home" 列均为 * true * ,并且显示正确的端口分配,则可以成功启动第一个节点,在此示例中, node1 上的 E3a 和 e3b 。

    显示示例
    cluster1::*> network interface show -vserver Cluster
    
                Logical      Status     Network            Current    Current Is
    Vserver     Interface    Admin/Oper Address/Mask       Node       Port    Home
    ----------- ------------ ---------- ------------------ ---------- ------- -----
    Cluster
                node1_clus1  up/up      169.254.209.69/16  node1      e3a     true
                node1_clus2  up/up      169.254.49.125/16  node1      e3b     true
                node2_clus1  up/up      169.254.47.194/16  node2      e3a     true
                node2_clus2  up/up      169.254.19.183/16  node2      e3a     false
    4 entries were displayed.
  6. 【第11步】显示集群中节点的相关信息:

    cluster show

    显示示例

    此示例显示此集群中 node1 和 node2 的节点运行状况为 true :

    cluster1::*> cluster show
    Node          Health  Eligibility
    ------------- ------- ------------
    node1         false   true
    node2         true    true
  7. 【第12步】验证所有物理集群端口是否均已启动:

    network port show -ipspace cluster

    显示示例
    cluster1::*> network port show -ipspace Cluster
    
    Node node1                                                                Ignore
                                                        Speed(Mbps)  Health   Health
    Port      IPspace     Broadcast Domain  Link  MTU   Admin/Oper   Status   Status
    --------- ----------- ----------------- ----- ----- ------------ -------- ------
    e3a       Cluster     Cluster           up    9000  auto/100000  healthy  false
    e3b       Cluster     Cluster           up    9000  auto/100000  healthy  false
    
    Node: node2
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
    Port      IPspace      Broadcast Domain Link  MTU   Admin/Oper   Status   Status
    --------- ------------ ---------------- ----- ----- ------------ -------- ------
    e3a       Cluster      Cluster          up    9000  auto/100000  healthy  false
    e3b       Cluster      Cluster          up    9000  auto/100000  healthy  false
    4 entries were displayed.
  8. 验证远程集群接口的连接:

ONTAP 9.9.1及更高版本

您可以使用 network interface check cluster-connectivity 命令启动集群连接的可访问性检查、然后显示详细信息:

network interface check cluster-connectivity startnetwork interface check cluster-connectivity show

cluster1::*> network interface check cluster-connectivity start

*注:*请等待几秒钟、然后再运行 `show`命令以显示详细信息。

cluster1::*> network interface check cluster-connectivity show
                                  Source           Destination      Packet
Node   Date                       LIF              LIF              Loss
------ -------------------------- ---------------- ---------------- -----------
node1
       3/5/2022 19:21:18 -06:00   node1_clus2      node2-clus1      none
       3/5/2022 19:21:20 -06:00   node1_clus2      node2_clus2      none
node2
       3/5/2022 19:21:18 -06:00   node2_clus2      node1_clus1      none
       3/5/2022 19:21:20 -06:00   node2_clus2      node1_clus2      none
所有ONTAP版本

对于所有ONTAP版本、您还可以使用 cluster ping-cluster -node <name> 用于检查连接的命令:

cluster ping-cluster -node <name>

cluster1::*> cluster ping-cluster -node local
Host is node2
Getting addresses from network interface table...
Cluster node1_clus1 169.254.209.69 node1 e3a
Cluster node1_clus2 169.254.49.125 node1 e3b
Cluster node2_clus1 169.254.47.194 node2 e3a
Cluster node2_clus2 169.254.19.183 node2 e3b
Local = 169.254.47.194 169.254.19.183
Remote = 169.254.209.69 169.254.49.125
Cluster Vserver Id = 4294967293
Ping status:
....
Basic connectivity succeeds on 4 path(s)
Basic connectivity fails on 0 path(s)
................
Detected 9000 byte MTU on 4 path(s):
Local 169.254.47.194 to Remote 169.254.209.69
Local 169.254.47.194 to Remote 169.254.49.125
Local 169.254.19.183 to Remote 169.254.209.69
Local 169.254.19.183 to Remote 169.254.49.125
Larger than PMTU communication succeeds on 4 path(s)
RPC status:
2 paths up, 0 paths down (tcp check)
2 paths up, 0 paths down (udp check)
  1. 【第14步】确认以下集群网络配置:

    network port show

    显示示例
    cluster1::*> network port show -ipspace Cluster
    
    Node: node1
                                                                            Ignore
                                           Speed(Mbps)             Health   Health
    Port      IPspace     Broadcast Domain Link MTU   Admin/Oper   Status   Status
    --------- ----------- ---------------- ---- ----- ------------ -------- ------
    e3a       Cluster     Cluster          up   9000  auto/100000  healthy  false
    e3b       Cluster     Cluster          up   9000  auto/100000  healthy  false
    
    Node: node2
                                                                            Ignore
                                            Speed(Mbps)            Health   Health
    Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
    --------- ------------ ---------------- ---- ---- ------------ -------- ------
    e3a       Cluster      Cluster          up   9000 auto/100000  healthy  false
    e3b       Cluster      Cluster          up   9000 auto/100000  healthy  false
    4 entries were displayed.
    
    cluster1::*> network interface show -vserver Cluster
                Logical    Status     Network            Current       Current Is
    Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
    ----------- ---------- ---------- ------------------ ------------- ------- ----
    Cluster
                node1_clus1  up/up    169.254.209.69/16  node1         e3a     true
                node1_clus2  up/up    169.254.49.125/16  node1         e3b     true
                node2_clus1  up/up    169.254.47.194/16  node2         e3a     true
                node2_clus2  up/up    169.254.19.183/16  node2         e3b     true
    4 entries were displayed.
    
    cluster1::> network device-discovery show -protocol cdp
    Node/       Local  Discovered
    Protocol    Port   Device (LLDP: ChassisID)  Interface         Platform
    ----------- ------ ------------------------- ----------------  ----------------
    node2      /cdp
                e3a    sh1    0/2               N9K-C9336C
                e3b    newsh2                    0/2               N9K-C9336C
    node1      /cdp
                e3a    sh1                       0/1               N9K-C9336C
                e3b    newsh2                    0/1               N9K-C9336C
    4 entries were displayed.
    
    sh1# show cdp neighbors
    Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                      S - Switch, H - Host, I - IGMP, r - Repeater,
                      V - VoIP-Phone, D - Remotely-Managed-Device,
                      s - Supports-STP-Dispute
    Device-ID            Local Intrfce  Hldtme Capability  Platform      Port ID
    node1                Eth1/1         144    H           FAS2980       e3a
    node2                Eth1/2         145    H           FAS2980       e3a
    newsh2               Eth1/35        176    R S I s     N9K-C9336C    Eth1/35
    newsh2               Eth1/36        176    R S I s     N9K-C9336C    Eth1/36
    Total entries displayed: 4
    
    sh2# show cdp neighbors
    Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge
                      S - Switch, H - Host, I - IGMP, r - Repeater,
                      V - VoIP-Phone, D - Remotely-Managed-Device,
                      s - Supports-STP-Dispute
    Device-ID          Local Intrfce  Hldtme Capability  Platform      Port ID
    node1              Eth1/1         139    H           FAS2980       e3b
    node2              Eth1/2         124    H           FAS2980       eb
    sh1                Eth1/35        178    R S I s     N9K-C9336C    Eth1/35
    sh1                Eth1/36        178    R S I s     N9K-C9336C    Eth1/36
    Total entries displayed: 4
  2. 将存储端口从旧交换机sh2移至新交换机newsh2。

  3. 验证连接到 HA 对 1 共享交换机 newsh2 的存储是否运行正常。

  4. 验证连接到HA对2共享交换机newsh2的存储是否运行正常:

    storage port show -port-type ENET

    显示示例
    storage::*> storage port show -port-type ENET
                                       Speed                            VLAN
    Node    Port    Type    Mode       (Gb/s)      State     Status       ID
    ------- ------- ------- ---------- ----------- --------- --------- -----
    node1
            e3a     ENET    storage          100   enabled   online       30
            e3b     ENET    storage            0   enabled   offline      30
            e7a     ENET    storage            0   enabled   offline      30
            e7b     ENET    storage          100   enabled   online       30
    
    node2
            e3a     ENET    storage          100   enabled   online       30
            e3b     ENET    storage            0   enabled   offline      30
            e7a     ENET    storage            0   enabled   offline      30
            e7b     ENET    storage          100   enabled   online       30
  5. 验证磁盘架布线是否正确:

    storage shelf port show -fields remote- device,remote-port

    显示示例
    cluster1::*> storage shelf port show -fields remote-device,remote-port
    shelf id remote-port  remote-device
    ----- -- ------------ ----------------------------
    3.20  0  Ethernet1/13 sh1
    3.20  1  Ethernet1/13 newsh2
    3.20  2  Ethernet1/14 sh1
    3.20  3  Ethernet1/14 newsh2
    3.30  0  Ethernet1/15 sh1
    3.30  1  Ethernet1/15 newsh2
    3.30  2  Ethernet1/16 sh1
    3.30  3  Ethernet1/16 newsh2
    8 entries were displayed.
  6. 移除旧交换机SH2。

  7. 对交换机 SH1 和新交换机 newsh1 重复上述步骤。

  8. 如果禁止自动创建案例,请通过调用 AutoSupport 消息重新启用它:

    ssystem node AutoSupport invoke -node * -type all -message MAINT=end

下一步是什么?

"配置交换机运行状况监控"(英文)