開始使用
本繁體中文版使用機器翻譯，譯文僅供參考，若與英文版本牴觸，應以英文版本為準。
更換Cisco Nexus 9336C-FX2叢集交換器
貢獻者
建議變更
PDF
請依照下列步驟、在叢集網路中更換故障的Nexus 9336C-FX2交換器。這是不中斷營運的程序（NDU）。
檢閱要求
更換交換器之前、請確定：
-
在現有的叢集和網路基礎架構上：
-
現有的叢集已通過驗證、完全正常運作、至少有一個完全連接的叢集交換器。
-
所有叢集連接埠均為* up*。
-
所有叢集邏輯介面（l生命）都是* up *及其主連接埠。
-
使用指令《叢集ping叢集節點節點1》必須指出、所有路徑上的基本連線能力和大於PMTU的通訊都會成功。ONTAP
-
-
在Nexus 9336C-FX2替換交換器上：
-
替換交換器上的管理網路連線功能正常。
-
更換交換器的主控台存取已就緒。
-
節點連線為連接埠1/1至1/34。
-
所有交換器間連結（ISL）連接埠在連接埠1/35和1/36上都會停用。
-
所需的參考組態檔（RCF）和NX-OS作業系統映像交換器會載入交換器。
-
交換器的初始自訂完成、如所述 "設定9336C-FX2叢集交換器"。
任何先前的站台自訂（例如STP、SNMP和SSH）都會複製到新交換器。
-
-
您已執行命令、從裝載叢集LIF的節點移轉叢集LIF。
更換交換器
關於範例
本程序中的範例使用下列交換器和節點命名法：
-
現有Nexus 9336C-FX2交換器的名稱為CS1和CS2。
-
新Nexus 9336C-FX2交換器的名稱為newcs2。
-
節點名稱為node1和node2。
-
每個節點上的叢集連接埠名稱為e0a和e0b。
-
叢集LIF名稱為node1_clus1、node1_clus2為node1、node2_clus1為node2_clus2、node2_clus2為node2。
-
對所有叢集節點進行變更的提示為cluster1：：*>
關於這項工作
下列程序以下列叢集網路拓撲為基礎：
顯示範例
cluster1::*> network port show -ipspace Cluster
Node: node1
Ignore
Speed(Mbps) Health Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status
--------- ------------ ---------------- ---- ---- ----------- -------- ------
e0a Cluster Cluster up 9000 auto/10000 healthy false
e0b Cluster Cluster up 9000 auto/10000 healthy false
Node: node2
Ignore
Speed(Mbps) Health Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status
--------- ------------ ---------------- ---- ---- ----------- -------- ------
e0a Cluster Cluster up 9000 auto/10000 healthy false
e0b Cluster Cluster up 9000 auto/10000 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 e0a true
node1_clus2 up/up 169.254.49.125/16 node1 e0b true
node2_clus1 up/up 169.254.47.194/16 node2 e0a true
node2_clus2 up/up 169.254.19.183/16 node2 e0b true
4 entries were displayed.
cluster1::*> network device-discovery show -protocol cdp
Node/ Local Discovered
Protocol Port Device (LLDP: ChassisID) Interface Platform
----------- ------ ------------------------- ---------------- ----------------
node2 /cdp
e0a cs1 Eth1/2 N9K-C9336C
e0b cs2 Eth1/2 N9K-C9336C
node1 /cdp
e0a cs1 Eth1/1 N9K-C9336C
e0b cs2 Eth1/1 N9K-C9336C
4 entries were displayed.
cs1# 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 e0a
node2 Eth1/2 145 H FAS2980 e0a
cs2 Eth1/35 176 R S I s N9K-C9336C Eth1/35
cs2(FDO220329V5) Eth1/36 176 R S I s N9K-C9336C Eth1/36
Total entries displayed: 4
cs2# 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 e0b
node2 Eth1/2 124 H FAS2980 e0b
cs1 Eth1/35 178 R S I s N9K-C9336C Eth1/35
cs1 Eth1/36 178 R S I s N9K-C9336C Eth1/36
Total entries displayed: 4
步驟1：準備更換
-
如果AutoSupport 此叢集啟用了「支援」功能、請叫用AutoSupport 下列訊息來禁止自動建立案例：
「系統節點AutoSupport 不完整地叫用節點*-type all -Message MAn=xh」
其中x是維護時段的持續時間（以小時為單位）。
此資訊可通知技術支援人員執行此維護工作、以便在維護期間抑制自動建立案例。AutoSupport -
在交換器newcs2上安裝適當的RCF和映像、並進行必要的站台準備。
如有必要、請針對新交換器驗證、下載及安裝適當版本的RCF和NX-OS軟體。如果您已確認新交換器已正確設定、而且不需要更新RCF和NX-OS軟體、請繼續執行步驟2。
-
請前往NetApp支援網站上的_NetApp叢集與管理網路交換器參考組態檔案說明頁面_。
-
按一下_叢集網路與管理網路相容性對照表_的連結、然後記下所需的交換器軟體版本。
-
按一下瀏覽器的返回箭號以返回「Description（說明）」頁面、按一下*繼續*、接受授權合約、然後前往「Download（下載）」頁面。
-
請依照下載頁面上的步驟、針對ONTAP 您要安裝的版本的更新軟體、下載正確的RCF和NX-OS檔案。
-
-
在新交換器上、以admin身分登入、並關閉所有連接至節點叢集介面的連接埠（連接埠1/1至1/34）。
如果您要更換的交換器無法正常運作且已關機、請前往步驟4。叢集節點上的LIF應已容錯移轉至每個節點的其他叢集連接埠。
顯示範例
newcs2# config Enter configuration commands, one per line. End with CNTL/Z. newcs2(config)# interface e1/1-34 newcs2(config-if-range)# shutdown
-
確認所有叢集生命體均已啟用自動還原：
「網路介面show -vserver叢集-功能 變數自動回復」
顯示範例
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. -
驗證所有叢集lifs是否都能通訊：
「叢集ping叢集」
顯示範例
cluster1::*> cluster ping-cluster node1 Host is node2 Getting addresses from network interface table... Cluster node1_clus1 169.254.209.69 node1 e0a Cluster node1_clus2 169.254.49.125 node1 e0b Cluster node2_clus1 169.254.47.194 node2 e0a Cluster node2_clus2 169.254.19.183 node2 e0b 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)
步驟2：設定纜線和連接埠
-
關閉Nexus 9336C-FX2交換器CS1上的ISL連接埠1/35和1/36。
顯示範例
cs1# configure Enter configuration commands, one per line. End with CNTL/Z. cs1(config)# interface e1/35-36 cs1(config-if-range)# shutdown cs1(config-if-range)#
-
從Nexus 9336C-FX2 CS2交換器拔下所有纜線、然後將其連接至Nexus C9336C-FX2 newcs2交換器上的相同連接埠。
-
在CS1和newcs2交換器之間啟動ISL連接埠1/35和1/36、然後驗證連接埠通道作業狀態。
連接埠通道應指示PO1（SU）、而成員連接埠應指示eth1/35（P）和eth1/36（P）。
顯示範例
此範例可啟用ISL連接埠1/35和1/36、並在交換器CS1上顯示連接埠通道摘要：
cs1# configure Enter configuration commands, one per line. End with CNTL/Z. cs1(config)# int e1/35-36 cs1(config-if-range)# no shutdown cs1(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) cs1(config-if-range)# -
確認所有節點上的連接埠e0b都已開啟：
「網路連接埠顯示IPSpace叢集」
顯示範例
輸出應類似於下列內容：
cluster1::*> network port show -ipspace Cluster Node: node1 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ----- ----------- -------- ------- e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false Node: node2 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ----- ----------- -------- ------- e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/auto - false 4 entries were displayed. -
在上一步所用的同一個節點上、使用network interface revert命令、還原上一步中與連接埠相關聯的叢集LIF。
顯示範例
在此範例中、如果Home值為true且連接埠為e0b、則節點1上的LIF node1_clus2會成功還原。
下列命令會將「node1」上的LIF「node1_clus2」傳回主連接埠「e0a」、並顯示兩個節點上的lifs相關資訊。如果兩個叢集介面的「是主節點」欄均為真、而且它們顯示正確的連接埠指派、則在節點1上的「e0a」和「e0b」範例中、啟動第一個節點就會成功。
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 e0a true node1_clus2 up/up 169.254.49.125/16 node1 e0b true node2_clus1 up/up 169.254.47.194/16 node2 e0a true node2_clus2 up/up 169.254.19.183/16 node2 e0a false 4 entries were displayed. -
顯示叢集中節點的相關資訊：
「叢集展示」
顯示範例
此範例顯示此叢集中節點1和節點2的節點健全狀況為真：
cluster1::*> cluster show Node Health Eligibility ------------- ------- ------------ node1 false true node2 true true
-
驗證所有實體叢集連接埠是否正常運作：
「網路連接埠顯示IPSpace叢集」
顯示範例
cluster1::*> network port show -ipspace Cluster Node node1 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ----------- ----------------- ----- ----- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false Node: node2 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ----- ----- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false 4 entries were displayed. -
驗證所有叢集lifs是否都能通訊：
「叢集ping叢集」
顯示範例
cluster1::*> cluster ping-cluster -node node2 Host is node2 Getting addresses from network interface table... Cluster node1_clus1 169.254.209.69 node1 e0a Cluster node1_clus2 169.254.49.125 node1 e0b Cluster node2_clus1 169.254.47.194 node2 e0a Cluster node2_clus2 169.254.19.183 node2 e0b 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)
-
確認下列叢集網路組態：
「網路連接埠展示」
顯示範例
cluster1::*> network port show -ipspace Cluster Node: node1 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ----------- ---------------- ---- ----- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false Node: node2 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 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 e0a true node1_clus2 up/up 169.254.49.125/16 node1 e0b true node2_clus1 up/up 169.254.47.194/16 node2 e0a true node2_clus2 up/up 169.254.19.183/16 node2 e0b true 4 entries were displayed. cluster1::> network device-discovery show -protocol cdp Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ---------------- ---------------- node2 /cdp e0a cs1 0/2 N9K-C9336C e0b newcs2 0/2 N9K-C9336C node1 /cdp e0a cs1 0/1 N9K-C9336C e0b newcs2 0/1 N9K-C9336C 4 entries were displayed. cs1# 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 e0a node2 Eth1/2 145 H FAS2980 e0a newcs2 Eth1/35 176 R S I s N9K-C9336C Eth1/35 newcs2 Eth1/36 176 R S I s N9K-C9336C Eth1/36 Total entries displayed: 4 cs2# 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 e0b node2 Eth1/2 124 H FAS2980 e0b cs1 Eth1/35 178 R S I s N9K-C9336C Eth1/35 cs1 Eth1/36 178 R S I s N9K-C9336C Eth1/36 Total entries displayed: 4
步驟3：驗證組態
-
對於更新版本的支援、請使用下列命令啟用乙太網路交換器健全狀況監視器記錄收集功能、以收集交換器相關的記錄檔ONTAP ：
「系統交換器乙太網路記錄設定密碼」和「系統交換器乙太網路記錄啟用-收集」
顯示範例
cluster1::*> system switch ethernet log setup-password Enter the switch name: <return> The switch name entered is not recognized. Choose from the following list: cs1 cs2 cluster1::*> system switch ethernet log setup-password Enter the switch name: cs1 RSA key fingerprint is e5:8b:c6:dc:e2:18:18:09:36:63:d9:63:dd:03:d9:cc Do you want to continue? {y|n}::[n] y Enter the password: <enter switch password> Enter the password again: <enter switch password> cluster1::*> system switch ethernet log setup-password Enter the switch name: cs2 RSA key fingerprint is 57:49:86:a1:b9:80:6a:61:9a:86:8e:3c:e3:b7:1f:b1 Do you want to continue? {y|n}:: [n] y Enter the password: <enter switch password> Enter the password again: <enter switch password> cluster1::*> system switch ethernet log enable-collection Do you want to enable cluster log collection for all nodes in the cluster? {y|n}: [n] y Enabling cluster switch log collection. cluster1::*>
如果這些命令中有任何一個出現錯誤、請聯絡NetApp支援部門。 -
針對發行9.5P16、9.6P12及9.7P10及更新版本的修補程式、請使用下列命令啟用乙太網路交換器健全狀況監視器記錄收集功能、以收集交換器相關的記錄檔ONTAP ：
「系統叢集交換器記錄設定密碼」和「系統叢集交換器記錄啟用收集」
顯示範例
cluster1::*> system cluster-switch log setup-password Enter the switch name: <return> The switch name entered is not recognized. Choose from the following list: cs1 cs2 cluster1::*> system cluster-switch log setup-password Enter the switch name: cs1 RSA key fingerprint is e5:8b:c6:dc:e2:18:18:09:36:63:d9:63:dd:03:d9:cc Do you want to continue? {y|n}::[n] y Enter the password: <enter switch password> Enter the password again: <enter switch password> cluster1::*> system cluster-switch log setup-password Enter the switch name: cs2 RSA key fingerprint is 57:49:86:a1:b9:80:6a:61:9a:86:8e:3c:e3:b7:1f:b1 Do you want to continue? {y|n}:: [n] y Enter the password: <enter switch password> Enter the password again: <enter switch password> cluster1::*> system cluster-switch log enable-collection Do you want to enable cluster log collection for all nodes in the cluster? {y|n}: [n] y Enabling cluster switch log collection. cluster1::*>
如果這些命令中有任何一個出現錯誤、請聯絡NetApp支援部門。 -
如果您禁止自動建立個案、請叫用AutoSupport 下列訊息來重新啟用：
「系統節點AutoSupport 不完整地叫用節點*-type all -most MAn=end」