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

更換Cisco Nexus 9336C-FX2 共用交換機

貢獻者 netapp-yvonneo netapp-jolieg

您可以更換有缺陷的 Nexus 9336C-FX2 共用交換器。這是一個無中斷程式 (NDU)。

開始之前

更換開關之前,請確保:

  • 在現有的集群和網路基礎設施中:

    • 現有集群已驗證功能完全正常,至少有一個完全連接的集群交換器。

    • 叢集所有連接埠均已啟動。

    • 所有群集邏輯介面(LIF)均已啟動並位於其所屬連接埠上。

    • ONTAP叢集 ping-cluster -node node1 指令必須表示所有路徑上的基本連線和大於 PMTU 的通訊均已成功。

  • 適用於 Nexus 9336C-FX2 的替換開關:

    • 替換交換器的管理網路連線功能正常。

    • 已具備對替換開關的控制台存取權限。

    • 節點連接埠為 1/1 至 1/34:

    • 連接埠 1/35 和 1/36 上的所有交換器間連結 (ISL) 連接埠均已停用。

    • 將所需的參考設定檔 (RCF) 和 NX-OS 作業系統映像交換器載入到交換器上。

    • 之前站點的所有自訂設置,如 STP、SNMP 和 SSH,都應該複製到新交換器上。

關於範例

您必須從叢集 LIF 所在的節點執行遷移叢集 LIF 的命令。

本流程中的範例使用以下開關和節點命名規則:

  • 現有的 Nexus 9336C-FX2 交換器的名稱是 sh1sh2

  • 新款 Nexus 9336C-FX2 交換器的名稱是 newsh1newsh2

  • 節點名稱為 node1node2

  • 每個節點上的叢集連接埠分別命名為_e3a_和_e3b_。

  • 集群 LIF 名稱為 `node1_clus1`和 `node1_clus2`對於節點1,以及 `node2_clus1`和 `node2_clus2`對於節點2。

  • 對所有叢集節點進行變更的提示是 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訊息來抑制自動建立案例:

    system node autosupport invoke -node * -type all -message MAINT=xh

    其中 x 為維護窗口的持續時間(小時)。

  2. 選購:在交換器上安裝對應的 RCF 和映像、newsh2,並進行任何必要的站點準備。

    1. 如有必要,請驗證、下載並安裝適用於新交換器的 RCF 和 NX-OS 軟體的相應版本。如果您已確認新交換器設定正確,且無需更新 RCF 和 NX-OS 軟體,請繼續。步驟3

    2. 前往NetApp支援網站上的NetApp叢集和管理網路交換器參考設定檔說明頁面。

    3. 點擊叢集網路和管理網路相容性矩陣的鏈接,然後記下所需的交換器軟體版本。

    4. 點擊瀏覽器後退箭頭返回描述頁面,點擊繼續,接受許可協議,然後前往下載頁面。

    5. 請依照下載頁面上的步驟,下載與您要安裝的ONTAP軟體版本相對應的正確 RCF 和 NX-OS 檔案。

  3. 在新交換器上,以管理員身分登錄,並關閉所有將連接到節點叢集介面的連接埠(連接埠 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. 驗證所有叢集 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 start`和 `network 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. 關閉 Nexus 9336C-FX2 交換器 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. 從 Nexus 9336C-FX2 sh2 交換器上拆下所有電纜,然後將它們連接到 Nexus C9336C-FX2 newsh2 交換器上的相同連接埠。

  3. 在 sh1 和 newsh2 交換器之間啟動 ISL 連接埠 1/35 和 1/36,然後驗證連接埠通道運作狀態。

    Port-Channel 應指示 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,則節點 1 上的 LIF node1_clus2 將成功還原。

    以下命令將節點 1 上的 LIF node1_clus2 返回主連接埠 e3a,並顯示有關兩個節點上 LIF 的資訊。如果兩個叢集介面的「Is Home」欄位都是*true*,且它們顯示正確的連接埠分配(在本例中為節點 1 上的 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. 顯示集群中節點的相關資訊:

    cluster show

    顯示範例

    此範例表明,該叢集中節點 1 和節點 2 的節點健康狀況為真:

    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 start`和 `network 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. 確認以下叢集網路配置:

    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. 步驟18:確認貨架上的電纜連接是否正確:

    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訊息重新啟用該功能:

    system node autosupport invoke -node * -type all -message MAINT=END

下一步是什麼?

更換開關後,您可以 "配置交換器健康監控"