Atualize a versão do RCF - Cisco Nexus 9808
Você atualiza a versão do arquivo de configuração de referência (RCF) em seus switches Cisco Nexus 9808 para oferecer suporte a novo hardware, uma nova versão do ONTAP ou para alinhar com uma nova versão do NX-OS na configuração do seu sistema AFX 2K.
|
|
Não atualize nem faça downgrade da sua versão do RCF para uma versão não suportada. |
-
Você deve ter lido a página "Visão geral da instalação ou atualização do RCF".
-
Você precisa estar conectado aos switches usando o console serial ou ter preservado as informações básicas de configuração. Isso ocorre porque o procedimento de atualização do RCF exige que você apague as configurações do switch e execute uma configuração básica.
-
Certifique-se de ter um backup atual da configuração do switch.
-
Verifique se o seu cluster está totalmente funcional, ou seja, se não há erros nos logs ou problemas semelhantes.
-
Você precisa ter a versão atual do RCF.
-
Você precisa de uma configuração de inicialização no RCF que reflita as imagens de inicialização desejadas.
Se precisar alterar a configuração de inicialização para refletir as imagens de inicialização atuais, você deve fazê-lo antes de reaplicar o RCF para que a versão correta seja instanciada em reinicializações futuras.
-
A atualização do RCF em ambos os switches é um procedimento não disruptivo.
-
Não é necessário um link operacional entre switches (ISL) durante este procedimento. Isso é intencional porque alterações na versão do RCF podem afetar temporariamente a conectividade do ISL. Para garantir a operação ininterrupta do cluster, este procedimento faz com que você migre todas as LIFs do cluster para o switch parceiro operacional enquanto executa as etapas no switch de destino.
-
Este procedimento consiste em atualizar o RCF no primeiro switch (cs1) e depois repetir os passos para o segundo switch (cs2).
-
-
Este procedimento requer o uso de comandos ONTAP e comandos dos switches Cisco Nexus 9000 Series, as etapas indicam qual CLI você está usando para inserir os comandos.
-
Os exemplos neste procedimento utilizam a seguinte nomenclatura de interruptor e nó:
-
Os nomes dos dois switches Cisco são cs1 e cs2.
-
Os nomes dos nós são node1-01, node1-02, node1-03 e node1-04.
-
Os nomes do cluster LIF são:
-
node1-01_clus1 e node1-01_clus2 para node1-01
-
node1-02_clus1 e node1-02_clus2 para node1-02
-
node1-03_clus1 e node1-03_clus2 para node1-03
-
node1-04_clus1 e node1-04_clus2 para node1-04
-
-
O
cluster1::*>O prompt indica o nome do cluster.
-
Etapa 1: Prepare-se para a atualização
Você insere os comandos para as etapas a seguir a partir da CLI do ONTAP.
-
Se o AutoSupport estiver ativado neste cluster, suprima a criação automática de casos invocando uma mensagem do AutoSupport :
system node autosupport invoke -node * -type all -message MAINT=xhonde x é a duração da janela de manutenção em horas.
-
Altere o nível de privilégio para avançado, digitando y quando solicitado a continuar:
set -privilege advancedA mensagem avançada (*>) é exibida.
-
Exiba as portas em cada nó que estão conectadas aos switches:
network device-discovery showMostrar exemplo
cluster1::*> network device-discovery show Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ---------------- ---------------- node1-01/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/5 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/14 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/7 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/16 N9K-C9808 e2a cs1(FOXXXXXXXXX) Ethernet1/3 N9K-C9808 e2b cs2(FOXXXXXXXXX) Ethernet1/12 N9K-C9808 node1-01/lldp e10a cs1 (ec:bb:78:9e:c7:e8) Ethernet1/5 - e10b cs2 (ec:bb:78:9e:c8:0c) Ethernet1/14 - e8a cs1 (ec:bb:78:9e:c7:f0) Ethernet1/7 - e8b cs2 (ec:bb:78:9e:c8:14) Ethernet1/16 - e1a cs1 (ec:bb:78:9e:c7:d8) Ethernet1/1 - e1b cs2 (ec:bb:78:9e:c7:fc) Ethernet1/10 - e2a cs1 (ec:bb:78:9e:c7:e0) Ethernet1/3 - e2b cs2 (ec:bb:78:9e:c8:04) Ethernet1/12 - node1-02/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/6 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/15 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/8 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/17 N9K-C9808 e2a cs1(FOXXXXXXXXXX) Ethernet1/2 N9K-C9808 e2b cs2(FOX3005Q66Q) Ethernet1/13 N9K-C9808 node1-02/lldp e10a cs1 (ec:bb:78:9e:c7:ec) Ethernet1/6 - e10b cs2 (ec:bb:78:9e:c8:10) Ethernet1/15 - e8a cs1 (ec:bb:78:9e:c7:f4) Ethernet1/8 - e8b cs2 (ec:bb:78:9e:c8:18) Ethernet1/17 - e1a cs1 (ec:bb:78:9e:c7:dc) Ethernet1/2 - e1b cs2 (ec:bb:78:9e:c8:00) Ethernet1/11 - e2a cs1 (ec:bb:78:9e:c7:e4) Ethernet1/4 - e2b cs2 (ec:bb:78:9e:c8:08) Ethernet1/13 - . . . -
Verifique o status administrativo e operacional de cada porto.
-
Portas de cluster
-
Verifique se todas as portas do cluster estão ativas e com status íntegro:
network port show -ipspace ClusterMostrar exemplo
cluster1::*> network port show -ipspace Cluster Node: node1-01 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-02 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-03 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-04 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false -
Verifique se todas as interfaces de cluster (LIFs) estão na porta principal:
network interface show -role clusterMostrar exemplo
cluster1::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ------------------ ---------- ----------------- ------------ ------- ---- Cluster node1-01_clus1 up/up 169.254.3.4/23 node1-01 e2a true node1-01_clus2 up/up 169.254.3.5/23 node1-01 e2b true node1-02_clus1 up/up 169.254.3.8/23 node1-02 e2a true node1-02_clus2 up/up 169.254.3.9/23 node1-02 e2b true node1-03_clus1 up/up 169.254.1.3/23 node1-03 e2a true node1-03_clus2 up/up 169.254.1.1/23 node1-03 e2b true node1-04_clus1 up/up 169.254.1.6/23 node1-04 e2a true node1-04_clus2 up/up 169.254.1.7/23 node1-04 e2b true -
Verifique se o cluster exibe informações para ambos os switches:
system cluster-switch show -is-monitoring-enabled-operational trueMostrar exemplo
cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true Switch Type Address Model --------------------------- ------------------ ---------------- --------------- cs2(FDOXXXXXXXX) cluster-network 10.228.137.233 N9K-C9808 Serial Number: FDOXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.5(3)(F) Version Source: CDP/ISDP cs1(FOXXXXXXXXX) cluster-network 10.228.137.234 N9K-C9808 Serial Number: FOXXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.5(3)(F) Version Source: CDP/ISDP
-
-
Portas HA
-
Verifique se todas as portas HA estão ativas e com status íntegro:
ha interconnect status show -node <node-name>Mostrar exemplo
cluster1::*> ha interconnect status show -node node1-01 (system ha interconnect status show) Node: node1-01 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE cluster1::*> ha interconnect status show -node node1-02 (system ha interconnect status show) Node: node1-02 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE . . . -
Verifique se todas as portas HA estão configuradas corretamente e se o tipo de interconexão é RoCE:
ha interconnect config showMostrar exemplo
cluster1::*> ha interconnect config show (system ha interconnect config show) Node: node1-01 Interconnect Type: RoCE Local System ID: 542023071 Partner System ID: 542022984 Connection Initiator: local Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.111 0x0 e1b-18 169.254.18.242 0x0 Node: node1-02 Interconnect Type: RoCE Local System ID: 542022984 Partner System ID: 542023071 Connection Initiator: partner Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.208 0x0 e1b-18 169.254.18.169 0x0 . . .
-
-
Portas de armazenamento
-
Verifique se todas as portas de armazenamento estão ativas e com status íntegro:
storage port show -port-type ENETMostrar exemplo
cluster1::*> storage port show -port-type ENET Speed Node Port Type Mode (Gb/s) State Status ------------------ ---- ----- ------- ------ -------- ----------- node1-01 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-02 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-03 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-04 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline
-
-
Portas de prateleira de armazenamento
-
Verifique se todas as portas da prateleira de armazenamento estão ativas e com status íntegro:
storage shelf port showMostrar exemplo
cluster1::*> storage shelf port show Shelf ID Module State Internal? ----- -- ------ ------------ --------- 1.0 0 A connected false 1 A connected false 2 A connected false 3 A connected false 4 A connected false 5 A connected false 6 A connected false 7 A connected false 8 B connected false 9 B connected false 10 B connected false 11 B connected false 12 B connected false 13 B connected false 14 B connected false 15 B connected false -
Verifique se todas as portas da prateleira de armazenamento estão ativas e com status íntegro:
storage shelf port show -fields remote-device,remote-port,connector-stateMostrar exemplo
cluster1::*> storage shelf port show -fields remote-device,remote-port,connector-state shelf id connector-state remote-port remote-device ----- -- --------------- -------------- ----------------- 1.1 0 connected Ethernet1/17/1 cs1(FOXXXXXXXXX) 1.1 1 connected Ethernet1/15/1 cs2(FDOXXXXXXXX) 1.1 2 connected Ethernet1/17/2 cs1(FOXXXXXXXXX) 1.1 3 connected Ethernet1/15/2 cs2(FDOXXXXXXXX) 1.1 4 connected Ethernet1/17/3 cs1(FOXXXXXXXXX) 1.1 5 connected Ethernet1/15/3 cs2(FDOXXXXXXXX) 1.1 6 connected Ethernet1/17/4 cs1(FOXXXXXXXXX) 1.1 7 connected Ethernet1/15/4 cs2(FDOXXXXXXXX) 1.1 8 connected Ethernet1/19/1 cs1(FOXXXXXXXXX) 1.1 9 connected Ethernet1/17/1 cs2(FDOXXXXXXXX) 1.1 10 connected Ethernet1/19/2 cs1(FOXXXXXXXXX) 1.1 11 connected Ethernet1/17/2 cs2(FDOXXXXXXXX) 1.1 12 connected Ethernet1/19/3 cs1(FOXXXXXXXXX) 1.1 13 connected Ethernet1/17/3 cs2(FDOXXXXXXXX) 1.1 14 connected Ethernet1/19/4 cs1(FOXXXXXXXXX) 1.1 15 connected Ethernet1/17/4 cs2(FDOXXXXXXXX)
-
-
-
Desative a reversão automática nas LIFs do cluster. As LIFs do cluster farão failover para o switch do cluster parceiro e permanecerão lá enquanto você executa este procedimento no switch de destino:
network interface modify -vserver Cluster -lif * -auto-revert false
Etapa 2: Configurar portas
-
Utilizando a CLI do switch, no switch cs1, desligue as portas conectadas a todas as portas dos nós para cada line card.
O exemplo a seguir mostra os comandos para desligar todas as portas na placa de linha 1
e1,e1-1/1-18,e1/19/1-4,e1/20/1-4………e1/35/1-4. Repita os comandos para cada placa de linha no switch.cs1# config terminal Enter configuration commands, one per line. End with CNTL/Z. cs1(config)# interface e1/1-18 cs1(config-if-range)# shutdown cs1(config)# interface e1/19/1-4,e1/20/1-4,e1/21/1-4,e1/22/1-4,e1/23/1-4,e1/24/1-4,e1/25/1-4,e1/26/1-4,e1/27/1-4,e1/28/1-4,e1/29/1-4,e1/30/1-4,e1/31/1-4,e1/32/1-4,e1/33/1-4,e1/34/1-4,e1/35/1-4 cs1(config-if-range)# shutdown cs1(config-if-range)# exit cs1(config)# exit
Certifique-se de desativar todas as portas conectadas para evitar problemas de conexão de rede. Consulte o artigo da Knowledge Base "Nó fora do quorum durante a migração do LIF do cluster na atualização do sistema operacional." para obter mais detalhes. -
Usando a CLI do ONTAP, verifique se as LIFs do cluster foram transferidas para as portas hospedadas no switch cs1. Isso pode levar alguns segundos.
network interface show -role clusterMostrar exemplo
cluster1::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- --------------- ---------- ------------------ ----------- ------- ---- Cluster node1-01_clus1 up/up 169.254.36.44/16 node1-01 e2a true node1-01_clus2 up/up 169.254.7.5/16 node1-01 e2b true node1-02_clus1 up/up 169.254.197.206/16 node1-02 e2a true node1-02_clus2 up/up 169.254.195.186/16 node1-02 e2b true node1-03_clus1 up/up 169.254.192.49/16 node1-03 e2a true node1-03_clus2 up/up 169.254.182.76/16 node1-03 e2b true node1-04_clus1 up/up 169.254.59.49/16 node1-04 e2a true node1-04_clus2 up/up 169.254.62.244/16 node1-04 e2b true 8 entries were displayed. -
Usando a ONTAP CLI, verifique se o cluster está íntegro:
cluster showMostrar exemplo
cluster1::*> cluster show Node Health Eligibility Epsilon ----------------- ------- ------------ ------- node1-01 true true false node1-02 true true false node1-03 true true true node1-04 true true false
-
Caso ainda não o tenha feito, utilizando a CLI do switch, salve uma cópia da configuração atual do switch copiando a saída do seguinte comando para um arquivo de texto:
show running-config-
Use o
show diff running-configcomando para comparar com o arquivo RCF salvo na bootflash. Caso contrário, use uma ferramenta de comparação/diff de terceiro.
-
-
Salve os detalhes básicos de configuração em
write_erase.cfgarquivo no bootflash.Certifique-se de configurar o seguinte:
-
Nome de usuário e senha
-
Endereço IP de gerenciamento
-
Gateway padrão
-
Nome do interruptor
Se o
write_erase.cfg`arquivo já existir, renomeie-o para `write_erase_old.cfg, da seguinte forma:cs1# move bootflash:write_erase.cfg write_erase_old.cfgcs1# show run | i "username admin password" > bootflash:write_erase.cfgcs1# show run | section "vrf context management" >> bootflash:write_erase.cfgcs1# show run | section "interface mgmt0" >> bootflash:write_erase.cfgcs1# show run | section "switchname" >> bootflash:write_erase.cfgConsulte o artigo da Knowledge Base "Como limpar a configuração de um switch de interconexão Cisco mantendo a conectividade remota" para obter mais detalhes.
-
-
Utilizando a CLI do switch, verifique se o arquivo
write_erase.cfgfoi preenchido conforme o esperado:show file bootflash:write_erase.cfg -
Utilizando a CLI do switch, execute o comando
write erasepara apagar a configuração salva atual:cs1# write eraseWarning: This command will erase the startup-configuration.Do you wish to proceed anyway? (y/n) [n] y -
Utilizando a CLI do switch, copie a configuração básica previamente salva para a configuração de inicialização.
cs1# copy bootflash:write_erase.cfg startup-config -
Utilizando a CLI do switch, reinicialize o switch:
cs1# reloadThis command will reboot the system. (y/n)? [n] y -
Após o endereço IP de gerenciamento estar acessível novamente, faça login no switch via SSH.
Você pode precisar atualizar as entradas do arquivo hosts relacionadas às chaves SSH.
-
Utilizando a CLI do switch, copie o RCF para a bootflash do switch cs1 usando um dos seguintes protocolos de transferência: FTP, TFTP, SFTP ou SCP.
Para obter mais informações sobre os comandos da Cisco, consulte o guia apropriado nos "Guia de Comandos do Cisco Nexus Série 9000 NX-OS" guides.
copy <protocol>: bootflash: vrf managementMostrar exemplo
Este exemplo mostra o TFTP sendo usado para copiar um arquivo RCF para a memória flash de inicialização no switch cs1:
cs1# copy tftp: bootflash: vrf management Enter source filename: RCF-v10.1-NX9808-CL1-ST1.txt Enter hostname for the tftp server: 172.22.201.50 Trying to connect to tftp server......Connection to Server Established. TFTP get operation was successful Copy complete, now saving to disk (please wait)...
-
Utilizando a CLI do switch, aplique o RCF previamente baixado ao bootflash.
Para obter mais informações sobre os comandos da Cisco, consulte o guia apropriado nos "Guia de Comandos do Cisco Nexus Série 9000 NX-OS" guides.
Este exemplo mostra o RCF
RCF-v10.1-NX9808-CL1-ST1.txtsendo instalado no switch cs1:cs1# copy RCF-v10.1-NX9808-CL1-ST1.txt running-config echo-commands
Certifique-se de ler atentamente as seções Notas de instalação, Notas importantes e banner do seu RCF. Você deve ler e seguir estas instruções para garantir a configuração e operação corretas do switch.
-
Utilizando a CLI do switch, verifique se o RCF é a versão mais recente correta:
show running-configAo verificar a saída para confirmar se você tem o RCF correto, certifique-se de que as seguintes informações estejam corretas:
-
A bandeira da RCF
-
Configurações de nó e porta
-
Personalizações
O resultado varia de acordo com a configuração do seu site. Verifique as configurações da porta e consulte as notas de versão para quaisquer alterações específicas do RCF que você instalou.
-
-
Reaplique quaisquer personalizações anteriores à configuração do switch.
Se seus switches estiverem executando o RCF 10.1 ou posterior, você pode "alterar a configuração de velocidade da porta" se necessário.
-
Usando a CLI do switch, após verificar se as versões do RCF, as adições personalizadas e as configurações do switch estão corretas, copie o
running-configarquivo para ostartup-configarquivo.Para obter mais informações sobre os comandos da Cisco, consulte o guia apropriado nos "Guia de Comandos do Cisco Nexus Série 9000 NX-OS" guides.
cs1# copy running-config startup-config[] 100% Copy complete -
Usando a CLI do switch, reinicialize o switch cs1. Você pode ignorar os alertas de "cluster switch health monitor" e os eventos de "cluster ports down" relatados nos nós enquanto o switch reinicializa.
cs1# reloadThis command will reboot the system. (y/n)? [n] y -
Utilizando a CLI do ONTAP, verifique a integridade de todas as portas no cluster.
-
Portas de cluster
-
Verifique se as portas do cluster estão ativas e funcionando corretamente em todos os nós do cluster:
network port show -ipspace ClusterMostrar exemplo
cluster1::*> network port show -ipspace Cluster Node: node1 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-02 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-03 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false Node: node1-04 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ------------ -------- ------ e2a Cluster Cluster up 9000 auto/400000 healthy false e2b Cluster Cluster up 9000 auto/400000 healthy false -
Verifique o estado de saúde do switch no cluster.
network device-discovery show -protocol cdpsystem cluster-switch show -is-monitoring-enabled-operational trueMostrar exemplo
cluster1::*> network device-discovery show -protocol cdp Node/ Local Discovered Protocol Port Device (LLDP: ChassisID) Interface Platform ----------- ------ ------------------------- ---------------- ---------------- node1-01/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/5 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/14 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/7 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/16 N9K-C9808 e2a cs1(FOXXXXXXXXX) Ethernet1/3 N9K-C9808 e2b cs2(FOXXXXXXXXX) Ethernet1/12 N9K-C9808 node1-02/cdp e10a cs1(FOXXXXXXXXX) Ethernet1/6 N9K-C9808 e10b cs2(FDOXXXXXXXX) Ethernet1/15 N9K-C9808 e8a cs1(FOXXXXXXXXX) Ethernet1/8 N9K-C9808 e8b cs2(FDOXXXXXXXX) Ethernet1/17 N9K-C9808 e2a cs1(FOXXXXXXXXXX) Ethernet1/2 N9K-C9808 e2b cs2(FOX3005Q66Q) Ethernet1/13 N9K-C9808 . . . cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true Switch Type Address Model --------------------------- ------------------ ---------------- --------------- cs2(FDOXXXXXXXX) cluster-network 10.228.137.233 N9K-C9808 Serial Number: FDOXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.6(3)(F) Version Source: CDP/ISDP cs1(FOXXXXXXXXX) cluster-network 10.228.137.234 N9K-C9808 Serial Number: FOXXXXXXXXX Is Monitored: true Reason: None Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 10.6(3)(F) Version Source: CDP/ISDP
-
-
Portas HA
-
Verifique se todas as portas HA estão ativas e com status íntegro:
ha interconnect status show -node <node-name>Mostrar exemplo
cluster1::*> ha interconnect status show -node node1-01 (system ha interconnect status show) Node: node1-01 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE cluster1::*> ha interconnect status show -node node1-02 (system ha interconnect status show) Node: node1-02 Link 0 Status: up Link 1 Status: up Is Link 0 Active: true Is Link 1 Active: true IC RDMA Connection: up Slot: 0 Debug Firmware: no Interconnect Port 0 : Port Name: e1a-17 MTU: 4096 Link Information: ACTIVE Interconnect Port 1 : Port Name: e1b-18 MTU: 4096 Link Information: ACTIVE . . . -
Verifique se todas as portas HA estão configuradas corretamente e se o tipo de interconexão é RoCE:
ha interconnect config showMostrar exemplo
cluster1::*> ha interconnect config show (system ha interconnect config show) Node: node1-01 Interconnect Type: RoCE Local System ID: 542023071 Partner System ID: 542022984 Connection Initiator: local Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.111 0x0 e1b-18 169.254.18.242 0x0 Node: node1-02 Interconnect Type: RoCE Local System ID: 542022984 Partner System ID: 542023071 Connection Initiator: partner Interface: external Port IP Address Flags ------ ----------------- ----------- e1a-17 169.254.17.208 0x0 e1b-18 169.254.18.169 0x0 . . .
-
-
Portas de armazenamento
-
Verifique se todas as portas de armazenamento estão ativas e com status íntegro:
storage port show -port-type ENETMostrar exemplo
cluster1::*> storage port show -port-type ENET Speed Node Port Type Mode (Gb/s) State Status ------------------ ---- ----- ------- ------ -------- ----------- node1-01 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-02 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-03 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline node1-04 e10a ENET - 400 enabled online e10b ENET - 0 enabled offline e8a ENET - 400 enabled online e8b ENET - 0 enabled offline
-
-
Portas de prateleira de armazenamento
-
Verifique se todas as portas da prateleira de armazenamento estão ativas e com status íntegro:
storage shelf port showMostrar exemplo
cluster1::*> storage shelf port show Shelf ID Module State Internal? ----- -- ------ ------------ --------- 1.0 0 A connected false 1 A connected false 2 A connected false 3 A connected false 4 A connected false 5 A connected false 6 A connected false 7 A connected false 8 B connected false 9 B connected false 10 B connected false 11 B connected false 12 B connected false 13 B connected false 14 B connected false 15 B connected false -
Verifique o status da conexão de todas as portas da prateleira de armazenamento:
storage shelf port show -fields remote-device,remote-port,connector-stateMostrar exemplo
cluster1::*> storage shelf port show -fields remote-device,remote-port,connector-state shelf id connector-state remote-port remote-device ----- -- --------------- -------------- ----------------- 1.1 0 connected Ethernet1/17/1 cs1(FOXXXXXXXXX) 1.1 1 connected Ethernet1/15/1 cs2(FDOXXXXXXXX) 1.1 2 connected Ethernet1/17/2 cs1(FOXXXXXXXXX) 1.1 3 connected Ethernet1/15/2 cs2(FDOXXXXXXXX) 1.1 4 connected Ethernet1/17/3 cs1(FOXXXXXXXXX) 1.1 5 connected Ethernet1/15/3 cs2(FDOXXXXXXXX) 1.1 6 connected Ethernet1/17/4 cs1(FOXXXXXXXXX) 1.1 7 connected Ethernet1/15/4 cs2(FDOXXXXXXXX) 1.1 8 connected Ethernet1/19/1 cs1(FOXXXXXXXXX) 1.1 9 connected Ethernet1/17/1 cs2(FDOXXXXXXXX) 1.1 10 connected Ethernet1/19/2 cs1(FOXXXXXXXXX) 1.1 11 connected Ethernet1/17/2 cs2(FDOXXXXXXXX) 1.1 12 connected Ethernet1/19/3 cs1(FOXXXXXXXXX) 1.1 13 connected Ethernet1/17/3 cs2(FDOXXXXXXXX) 1.1 14 connected Ethernet1/19/4 cs1(FOXXXXXXXXX) 1.1 15 connected Ethernet1/17/4 cs2(FDOXXXXXXXX)
-
-
-
Usando a ONTAP CLI, verifique se o cluster está íntegro:
cluster showMostrar exemplo
cluster1::*> cluster show Node Health Eligibility Epsilon ----------------- -------- ------------- ------- node1-01 true true false node1-02 true true false node1-03 true true true node1-04 true true false 4 entries were displayed.
-
Repita os passos 4 a 18 no switch cs2.
-
Utilizando a ONTAP CLI, habilite a reversão automática nas LIFs do cluster.
network interface modify -vserver Cluster -lif * -auto-revert true
Etapa 3: Verifique a configuração de rede do cluster e a integridade do cluster.
-
Usando a CLI do switch, verifique se as portas do switch conectadas às portas do cluster estão ativas.
show interface briefMostrar exemplo
cs1# show interface brief | grep up -------------------------------------------------------------------------------- Ethernet VLAN Type Mode Status Reason Speed Port Interface Ch # -------------------------------------------------------------------------------- Eth1/1 1 eth trunk up none 400G(D) -- Eth1/2 1 eth trunk up none 400G(D) -- Eth1/3 1 eth trunk up none 400G(D) -- Eth1/4 1 eth trunk up none 400G(D) -- Eth1/5 1 eth trunk up none 400G(D) -- Eth1/6 1 eth trunk up none 400G(D) -- Eth1/7 1 eth trunk up none 400G(D) -- Eth1/8 1 eth trunk up none 400G(D) -- Eth1/9 1 eth trunk down XCVR not inserted auto(D) -- Eth1/10 1 eth trunk up none 400G(D) -- Eth1/11 1 eth trunk up none 400G(D) -- Eth1/12 1 eth trunk up none 400G(D) -- Eth1/13 1 eth trunk up none 400G(D) -- Eth1/14 1 eth trunk up none 400G(D) -- Eth1/15 1 eth trunk up none 400G(D) -- Eth1/16 1 eth trunk up none 400G(D) -- Eth1/17 1 eth trunk up none 400G(D) -- Eth1/18 1 eth trunk down XCVR not inserted auto(D) -- Eth1/19/1 1 eth trunk up none 100G(D) -- Eth1/19/2 1 eth trunk up none 100G(D) -- Eth1/19/3 1 eth trunk up none 100G(D) -- Eth1/19/4 1 eth trunk up none 100G(D) -- Eth1/20/1 1 eth trunk up none 100G(D) -- Eth1/20/2 1 eth trunk up none 100G(D) -- Eth1/20/3 1 eth trunk up none 100G(D) -- Eth1/20/4 1 eth trunk up none 100G(D) -- . . . Eth1/30/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/30/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/30/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/30/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/31/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/32/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/33/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/34/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/1 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/2 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/3 1 eth trunk down XCVR not inserted auto(D) -- Eth1/35/4 1 eth trunk down XCVR not inserted auto(D) -- Eth1/36 1 eth trunk down XCVR not inserted auto(D) 1 ------------------------------------------------------------------------------------ Port-channel VLAN Type Mode Status Reason Speed Protocol Interface ------------------------------------------------------------------------------------ Po1 1 eth trunk down No operational members auto(D) lacp Po998 1 eth access down Administratively down auto(I) none Po999 1 eth access down Administratively down auto(I) none
-
Utilizando a CLI do switch, verifique se os nós esperados ainda estão conectados:
show cdp neighborsshow lldp neighborsMostrar exemplo
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 cs1 Eth1/3 179 H AFX-2K e7a cs2 Eth1/4 123 H AFX-2K e7a cs1 Eth1/5 179 H AFX-2K e10a cs2 Eth1/6 123 H AFX-2K e10a cs1 Eth1/7 179 H AFX-2K e11a cs2 Eth1/8 123 H AFX-2K e11a cs1 Eth1/12 179 H AFX-2K e7b cs2 Eth1/13 123 H AFX-2K e7b cs1 Eth1/14 179 H AFX-2K e10b cs2 Eth1/15 123 H AFX-2K e10b cs1 Eth1/16 179 H AFX-2K e11b cs2 Eth1/17 123 H AFX-2K e11b cs1# show lldp neighbors Capability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other Device ID Local Intf Hold-time Capability Port ID cs1 Eth1/1 121 S e1a cs2 Eth1/2 121 S e1a cs1 Eth1/3 121 S e7a cs2 Eth1/4 121 S e7a cs1 Eth1/5 121 S e10a cs2 Eth1/6 121 S e10a cs1 Eth1/7 121 S e11a cs2 Eth1/8 121 S e11a cs1 Eth1/10 121 S e1b cs2 Eth1/11 121 S e1b cs1 Eth1/12 121 S e7b cs2 Eth1/13 121 S e7b cs1 Eth1/14 121 S e10b cs2 Eth1/15 121 S e10b cs1 Eth1/16 121 S e11b cs2 Eth1/17 121 S e11b 952551000983 Eth1/19/1 120 S e1a 952551000983 Eth1/19/2 120 S e3a 952551000983 Eth1/19/3 120 S e1a 952551000983 Eth1/19/4 120 S e3a 952551000983 Eth1/20/1 120 S e2a 952551000983 Eth1/20/2 120 S e4a 952551000983 Eth1/20/3 120 S e2a 952551000983 Eth1/20/4 120 S e4a . . . -
Utilizando a CLI do switch, verifique se os nós do cluster estão em suas VLANs corretas usando os seguintes comandos:
show vlan briefshow interface trunkMostrar exemplo
cs1# show vlan brief VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Po1, Po998, Po999, Eth1/1 Eth1/2, Eth1/3, Eth1/4, Eth1/5 Eth1/6, Eth1/7, Eth1/8, Eth1/9 Eth1/10, Eth1/11, Eth1/12 Eth1/13, Eth1/14, Eth1/15 Eth1/16, Eth1/17, Eth1/18 Eth1/36, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 . . Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 17 VLAN0017 active Eth1/1, Eth1/2, Eth1/3, Eth1/4 Eth1/5, Eth1/6, Eth1/7, Eth1/8 Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 Eth1/20/2, Eth1/20/3, Eth1/20/4 Eth1/21/1, Eth1/21/2, Eth1/21/3 . . Eth1/30/4, Eth1/31/1, Eth1/31/2 Eth1/31/3, Eth1/31/4, Eth1/32/1 Eth1/32/2, Eth1/32/3, Eth1/32/4 Eth1/33/1, Eth1/33/2, Eth1/33/3 Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 18 VLAN0018 active Eth1/1, Eth1/2, Eth1/3, Eth1/4 Eth1/5, Eth1/6, Eth1/7, Eth1/8 Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 . . Eth1/30/1, Eth1/30/2, Eth1/30/3 Eth1/30/4, Eth1/31/1, Eth1/31/2 Eth1/31/3, Eth1/31/4, Eth1/32/1 Eth1/32/2, Eth1/32/3, Eth1/32/4 Eth1/33/1, Eth1/33/2, Eth1/33/3 Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 30 VLAN0030 active Eth1/1, Eth1/2, Eth1/3, Eth1/4 Eth1/5, Eth1/6, Eth1/7, Eth1/8 Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/19/1, Eth1/19/2 Eth1/19/3, Eth1/19/4, Eth1/20/1 Eth1/20/2, Eth1/20/3, Eth1/20/4 . . Eth1/33/1, Eth1/33/2, Eth1/33/3 Eth1/33/4, Eth1/34/1, Eth1/34/2 Eth1/34/3, Eth1/34/4, Eth1/35/1 Eth1/35/2, Eth1/35/3, Eth1/35/4 40 VLAN0040 active Po1, Eth1/1, Eth1/2, Eth1/3 Eth1/4, Eth1/5, Eth1/6, Eth1/7 Eth1/8, Eth1/9, Eth1/10, Eth1/11 Eth1/12, Eth1/13, Eth1/14 Eth1/15, Eth1/16, Eth1/17 Eth1/18, Eth1/36, Eth1/19/1 Eth1/19/2, Eth1/19/3, Eth1/19/4 Eth1/20/1, Eth1/20/2, Eth1/20/3 Eth1/20/4, Eth1/21/1, Eth1/21/2 Eth1/21/3, Eth1/21/4, Eth1/22/1 Eth1/22/2, Eth1/22/3, Eth1/22/4 Eth1/23/1, Eth1/23/2, Eth1/23/3 Eth1/23/4, Eth1/24/1, Eth1/24/2 Eth1/24/3, Eth1/24/4, Eth1/25/1 Eth1/25/2, Eth1/25/3, Eth1/25/4 Eth1/26/1, Eth1/26/2, Eth1/26/3 Eth1/26/4, Eth1/27/1, Eth1/27/2 Eth1/27/3, Eth1/27/4, Eth1/28/1 . . Eth1/34/2, Eth1/34/3, Eth1/34/4 Eth1/35/1, Eth1/35/2, Eth1/35/3 Eth1/35/4 cs1# show interface trunk -------------------------------------------------------------------------------- Port Native Status Port Vlan Channel -------------------------------------------------------------------------------- Eth1/1 1 trunking -- Eth1/2 1 trunking -- Eth1/3 1 trunking -- Eth1/4 1 trunking -- Eth1/5 1 trunking -- Eth1/6 1 trunking -- Eth1/7 1 trunking -- Eth1/8 1 trunking -- Eth1/9 1 trunking -- Eth1/10 1 trunking -- . . . Eth1/30/1 1 trunking -- Eth1/30/2 1 trunking -- Eth1/30/3 1 trunking -- Eth1/30/4 1 trunking -- Eth1/31/1 1 trunking -- Eth1/31/2 1 trunking -- Eth1/31/3 1 trunking -- Eth1/31/4 1 trunking -- Eth1/32/1 1 trunking -- Eth1/32/2 1 trunking -- Eth1/32/3 1 trunking -- Eth1/32/4 1 trunking -- Eth1/33/1 1 trunking -- Eth1/33/2 1 trunking -- Eth1/33/3 1 trunking -- Eth1/33/4 1 trunking -- Eth1/34/1 1 trunking -- Eth1/34/2 1 trunking -- Eth1/34/3 1 trunking -- Eth1/34/4 1 trunking -- Eth1/35/1 1 trunking -- Eth1/35/2 1 trunking -- Eth1/35/3 1 trunking -- Eth1/35/4 1 trunking -- Eth1/36 1 trnk-bndl Po1 Po1 1 not-trunking -- -------------------------------------------------------------------------------- Port Vlans Allowed on Trunk -------------------------------------------------------------------------------- Eth1/1 1,17-18,30,40 Eth1/2 1,17-18,30,40 Eth1/3 1,17-18,30,40 Eth1/4 1,17-18,30,40 Eth1/5 1,17-18,30,40 Eth1/6 1,17-18,30,40 Eth1/7 1,17-18,30,40 Eth1/8 1,17-18,30,40 Eth1/9 1,17-18,30,40 Eth1/10 1,17-18,30,40 Eth1/11 1,17-18,30,40 . . . Eth1/30/1 1,17-18,30,40 Eth1/30/2 1,17-18,30,40 Eth1/30/3 1,17-18,30,40 Eth1/30/4 1,17-18,30,40 Eth1/31/1 1,17-18,30,40 Eth1/31/2 1,17-18,30,40 Eth1/31/3 1,17-18,30,40 Eth1/31/4 1,17-18,30,40 Eth1/32/1 1,17-18,30,40 Eth1/32/2 1,17-18,30,40 Eth1/32/3 1,17-18,30,40 Eth1/32/4 1,17-18,30,40 Eth1/33/1 1,17-18,30,40 Eth1/33/2 1,17-18,30,40 Eth1/33/3 1,17-18,30,40 Eth1/33/4 1,17-18,30,40 Eth1/34/1 1,17-18,30,40 Eth1/34/2 1,17-18,30,40 Eth1/34/3 1,17-18,30,40 Eth1/34/4 1,17-18,30,40 Eth1/35/1 1,17-18,30,40 Eth1/35/2 1,17-18,30,40 Eth1/35/3 1,17-18,30,40 Eth1/35/4 1,17-18,30,40 Eth1/36 1,40 Po1 1,40 -------------------------------------------------------------------------------- Port Vlans Err-disabled on Trunk -------------------------------------------------------------------------------- Eth1/1 none Eth1/2 none Eth1/3 none Eth1/4 none Eth1/5 none Eth1/6 none Eth1/7 none Eth1/8 none Eth1/9 none Eth1/10 none . . . Eth1/30/1 none Eth1/30/2 none Eth1/30/3 none Eth1/30/4 none Eth1/31/1 none Eth1/31/2 none Eth1/31/3 none Eth1/31/4 none Eth1/32/1 none Eth1/32/2 none Eth1/32/3 none Eth1/32/4 none Eth1/33/1 none Eth1/33/2 none Eth1/33/3 none Eth1/33/4 none Eth1/34/1 none Eth1/34/2 none Eth1/34/3 none Eth1/34/4 none Eth1/35/1 none Eth1/35/2 none Eth1/35/3 none Eth1/35/4 none Eth1/36 none Po1 none -------------------------------------------------------------------------------- Port STP Forwarding -------------------------------------------------------------------------------- Eth1/1 1,17-18,30,40 Eth1/2 1,17-18,30,40 Eth1/3 1,17-18,30,40 Eth1/4 1,17-18,30,40 Eth1/5 1,17-18,30,40 Eth1/6 1,17-18,30,40 Eth1/7 1,17-18,30,40 Eth1/8 1,17-18,30,40 Eth1/9 none Eth1/10 1,17-18,30,40 . . . Eth1/30/1 none Eth1/30/2 none Eth1/30/3 none Eth1/30/4 none Eth1/31/1 none Eth1/31/2 none Eth1/31/3 none Eth1/31/4 none Eth1/32/1 none Eth1/32/2 none Eth1/32/3 none Eth1/32/4 none Eth1/33/1 none Eth1/33/2 none Eth1/33/3 none Eth1/33/4 none Eth1/34/1 none Eth1/34/2 none Eth1/34/3 none Eth1/34/4 none Eth1/35/1 none Eth1/35/2 none Eth1/35/3 none Eth1/35/4 none Eth1/36 none Po1 none -------------------------------------------------------------------------------- Port Vlans in spanning tree forwarding state and not pruned -------------------------------------------------------------------------------- Eth1/1 Feature VTP is not enabled 1,17-18,30,40 Eth1/2 Feature VTP is not enabled 1,17-18,30,40 Eth1/3 Feature VTP is not enabled 1,17-18,30,40 Eth1/4 Feature VTP is not enabled 1,17-18,30,40 Eth1/5 Feature VTP is not enabled 1,17-18,30,40 Eth1/6 Feature VTP is not enabled 1,17-18,30,40 Eth1/7 Feature VTP is not enabled 1,17-18,30,40 Eth1/8 Feature VTP is not enabled 1,17-18,30,40 Eth1/9 Feature VTP is not enabled 1,17-18,30,40 Eth1/10 Feature VTP is not enabled 1,17-18,30,40 . . . Eth1/30/1 Feature VTP is not enabled none Eth1/30/2 Feature VTP is not enabled none Eth1/30/3 Feature VTP is not enabled none Eth1/30/4 Feature VTP is not enabled none Eth1/31/1 Feature VTP is not enabled none Eth1/31/2 Feature VTP is not enabled none Eth1/31/3 Feature VTP is not enabled none Eth1/31/4 Feature VTP is not enabled none Eth1/32/1 Feature VTP is not enabled none Eth1/32/2 Feature VTP is not enabled none Eth1/32/3 Feature VTP is not enabled none Eth1/32/4 Feature VTP is not enabled none Eth1/33/1 Feature VTP is not enabled none Eth1/33/2 Feature VTP is not enabled none Eth1/33/3 Feature VTP is not enabled none Eth1/33/4 Feature VTP is not enabled none Eth1/34/1 Feature VTP is not enabled none Eth1/34/2 Feature VTP is not enabled none Eth1/34/3 Feature VTP is not enabled none Eth1/34/4 Feature VTP is not enabled none Eth1/35/1 Feature VTP is not enabled none Eth1/35/2 Feature VTP is not enabled none Eth1/35/3 Feature VTP is not enabled none Eth1/35/4 Feature VTP is not enabled none Eth1/36 Feature VTP is not enabled none Po1 Feature VTP is not enabled nonePara obter detalhes específicos sobre o uso de portas e VLANs, consulte a seção de avisos e notas importantes no seu RCF. -
Utilizando a CLI do switch, verifique se o ISL entre cs1 e cs2 está funcional:
show port-channel summaryMostrar exemplo
cs1# 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(SD) Eth LACP Eth1/36(D) 998 Po998(SD) Eth NONE -- 999 Po999(SD) Eth NONE -- -
Utilizando a ONTAP CLI, verifique se as LIFs do cluster retornaram à sua porta inicial:
network interface show -role clusterMostrar exemplo
cluster1::*> network interface show -role cluster Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- --------------- ---------- ------------------ ----------- ------- ---- Cluster node1-01_clus1 up/up 169.254.36.44/16 node1-01 e2a true node1-01_clus2 up/up 169.254.7.5/16 node1-01 e2b true node1-02_clus1 up/up 169.254.197.206/16 node1-02 e2a true node1-02_clus2 up/up 169.254.195.186/16 node1-02 e2b true node1-03_clus1 up/up 169.254.192.49/16 node1-03 e2a true node1-03_clus2 up/up 169.254.182.76/16 node1-03 e2b true node1-04_clus1 up/up 169.254.59.49/16 node1-04 e2a true node1-04_clus2 up/up 169.254.62.244/16 node1-04 e2b trueSe alguma LIF do cluster não tiver retornado às suas portas originais, reverta-as manualmente a partir do nó local:
network interface revert -vserver vserver_name -lif <lif-name> -
Usando a ONTAP CLI, verifique se o cluster está íntegro:
cluster showMostrar exemplo
cluster1::*> cluster show Node Health Eligibility Epsilon ----------------- ------- ------------- ------- node1-01 true true false node1-02 true true false node1-03 true true true node1-04 true true false
-
Usando a ONTAP CLI, verifique a conectividade das interfaces do cluster remoto:
-
Você pode usar o
network interface check cluster-connectivity showComando para exibir os detalhes de uma verificação de acessibilidade para conectividade de cluster:network interface check cluster-connectivity showMostrar exemplo
cluster1::*> network interface check cluster-connectivity show Source Destination Packet Node Date LIF LIF Loss ------ -------------------------- ---------------- --------------- ----------- node1-01 6/4/2025 03:13:33 -04:00 node1-01_clus2 node1-02_clus1 none 6/4/2025 03:13:34 -04:00 node1-01_clus2 node1-02_clus1 none node1-02 6/4/2025 03:13:33 -04:00 node1-02_clus2 node1-01_clus1 none 6/4/2025 03:13:34 -04:00 node1-02_clus2 node1-01_clus2 none . . . -
Alternativamente, você pode usar o
cluster ping-cluster -node <node-name>comando para verificar a conectividade:cluster ping-cluster -node <node-name>Mostrar exemplo
cluster1::*> cluster ping-cluster -node local Host is node1-04 Getting addresses from network interface table... Cluster node1-01_clus1 169.254.36.44 node1-01 e7a Cluster node1-01_clus2 169.254.7.5 node1-01 e7b Cluster node1-02_clus1 169.254.197.206 node1-02 e7a Cluster node1-02_clus2 169.254.195.186 node1-02 e7b Cluster node1-03_clus1 169.254.192.49 node1-03 e7a Cluster node1-03_clus2 169.254.182.76 node1-03 e7b Cluster node1-04_clus1 169.254.59.49 node1-04 e7a Cluster node1-04_clus2 169.254.62.244 node1-04 e7b Local = 169.254.59.49 169.254.62.244 Remote = 169.254.36.44 169.254.7.5 169.254.197.206 169.254.195.186 169.254.192.49 169.254.182.76 Cluster Vserver Id = 4294967293 Ping status: ............ Basic connectivity succeeds on 12 path(s) Basic connectivity fails on 0 path(s) ................................................ Detected 9000 byte MTU on 12 path(s): Local 169.254.59.49 to Remote 169.254.182.76 Local 169.254.59.49 to Remote 169.254.192.49 Local 169.254.59.49 to Remote 169.254.195.186 Local 169.254.59.49 to Remote 169.254.197.206 Local 169.254.59.49 to Remote 169.254.36.44 Local 169.254.59.49 to Remote 169.254.7.5 Local 169.254.62.244 to Remote 169.254.182.76 Local 169.254.62.244 to Remote 169.254.192.49 Local 169.254.62.244 to Remote 169.254.195.186 Local 169.254.62.244 to Remote 169.254.197.206 Local 169.254.62.244 to Remote 169.254.36.44 Local 169.254.62.244 to Remote 169.254.7.5 Larger than PMTU communication succeeds on 12 path(s) RPC status: 6 paths up, 0 paths down (tcp check) 6 paths up, 0 paths down (udp check)
-
Depois de atualizar o RCF em seus switches, você "Verifique o SSH para coleta de logs".