Skip to main content
Se proporciona el idioma español mediante traducción automática para su comodidad. En caso de alguna inconsistencia, el inglés precede al español.

Instale o actualice el software NX-OS

Colaboradores netapp-yvonneo netapp-jolieg

Siga este procedimiento para instalar o actualizar el software NX-OS en los conmutadores de clúster Nexus 9336C-FX2 y 9336C-FX2-T.

Antes de comenzar, complete el procedimiento en"Prepárese para instalar NX-OS y RCF." .

Nota NetApp recomienda que primero completes cualquier actualización del software ONTAP y luego realices la actualización del software de tus switches.

Requisitos de revisión

Antes de empezar

Asegúrate de hacer lo siguiente:

  • Ejecuta el comando show install all impact nxos bootflash:<image_name>.bin en el switch para revisar el impacto de instalar o actualizar la nueva imagen de software NX-OS. Verifica la integridad de la imagen, revisa si son necesarios reinicios, evalúa la compatibilidad del hardware y confirma que hay suficiente espacio.

  • Revisa las notas de la versión del software NX-OS de destino para ver si hay algún requisito específico.

  • Verifica que tienes una copia de seguridad actual de la configuración del conmutador.

  • Verifica que tienes un clúster que funciona completamente (sin errores en los registros ni problemas similares).

Documentación sugerida
Acerca de los ejemplos

Los ejemplos de este procedimiento utilizan la siguiente nomenclatura de interruptores y nodos:

  • Los nombres de los dos switches de Cisco son cs1 y cs2.

  • Los nombres de los nodos son cluster1-01, cluster1-02, cluster1-03 y cluster1-04.

  • Los nombres LIF del clúster son cluster1-01_clus1, cluster1-01_clus2, cluster1-02_clus1, cluster1-02_clus2, cluster1-03_clus1, cluster1-03_clus2, cluster1-04_clus1 y cluster1-04_clus2.

  • El cluster1::*> El indicador muestra el nombre del clúster.

Instala el software

En este procedimiento, usa los comandos de ONTAP, salvo que se especifique un comando del switch Cisco Nexus 9000 Series.

Pasos
  1. Conecte el conmutador del clúster a la red de administración.

  2. Utilice el comando ping para verificar la conectividad con el servidor que aloja el software NX-OS y el RCF.

    ping <IP address> vrf management

    Mostrar ejemplo

    Este ejemplo verifica que el switch puede alcanzar el servidor en la dirección IP 172.19.2.1:

    cs2# ping 172.19.2.1 vrf management
    Pinging 172.19.2.1 with 0 bytes of data:
    
    Reply From 172.19.2.1: icmp_seq = 0. time= 5910 usec.
  3. Muestra los puertos del clúster en cada nodo que están conectados a los conmutadores del clúster:

    network device-discovery show

    Mostrar ejemplo
    cluster1::*> network device-discovery show
    Node/       Local  Discovered
    Protocol    Port   Device (LLDP: ChassisID)  Interface         Platform
    ----------- ------ ------------------------- ----------------- --------------
    cluster1-01/cdp
                e0a    cs1                       Ethernet1/7       N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/7       N9K-C9336C-FX2
    cluster1-02/cdp
                e0a    cs1                       Ethernet1/8       N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/8       N9K-C9336C-FX2
    cluster1-03/cdp
                e0a    cs1                       Ethernet1/1/1     N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/1/1     N9K-C9336C-FX2
    cluster1-04/cdp
                e0a    cs1                       Ethernet1/1/2     N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/1/2     N9K-C9336C-FX2
    cluster1::*>
  4. Verifique el estado administrativo y operativo de cada puerto del clúster.

    1. Verifique que todos los puertos del clúster estén activos y en buen estado:

      network port show -ipspace Cluster

      Mostrar ejemplo
      cluster1::*> network port show -ipspace Cluster
      
      Node: cluster1-01
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
      --------- ------------ ---------------- ---- ---- ------------ -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy  false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy  false
      
      Node: cluster1-02
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
      --------- ------------ ---------------- ---- ---- ------------ -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy  false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy  false
      
      Node: cluster1-03
      
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
      --------- ------------ ---------------- ---- ---- ------------ -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy  false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy  false
      
      Node: cluster1-04
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
      --------- ------------ ---------------- ---- ---- ------------ -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy  false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy  false
      cluster1::*>
    2. Verifique que todas las interfaces del clúster (LIF) estén en el puerto principal:

      network interface show -vserver Cluster

      Mostrar ejemplo
      cluster1::*> network interface show -vserver Cluster
                  Logical            Status     Network            Current             Current Is
      Vserver     Interface          Admin/Oper Address/Mask       Node                Port    Home
      ----------- ------------------ ---------- ------------------ ------------------- ------- ----
      Cluster
                  cluster1-01_clus1  up/up      169.254.3.4/23     cluster1-01         e0b     true
                  cluster1-01_clus2  up/up      169.254.3.5/23     cluster1-01         e0b     true
                  cluster1-02_clus1  up/up      169.254.3.8/23     cluster1-02         e0b     true
                  cluster1-02_clus2  up/up      169.254.3.9/23     cluster1-02         e0b     true
                  cluster1-03_clus1  up/up      169.254.1.3/23     cluster1-03         e0b     true
                  cluster1-03_clus2  up/up      169.254.1.1/23     cluster1-03         e0b     true
                  cluster1-04_clus1  up/up      169.254.1.6/23     cluster1-04         e0b     true
                  cluster1-04_clus2  up/up      169.254.1.7/23     cluster1-04         e0b     true
      cluster1::*>
    3. Verifique que el clúster muestre información para ambos conmutadores del clúster:

      system cluster-switch show -is-monitoring-enabled-operational true

    Mostrar ejemplo
    cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true
    Switch                      Type               Address          Model
    --------------------------- ------------------ ---------------- --------------
    cs1                         cluster-network    10.233.205.90    N9K-C9336C-FX2
         Serial Number: FOCXXXXXXGD
          Is Monitored: true
                Reason: None
      Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                        9.3(5)
        Version Source: CDP
    
    cs2                         cluster-network    10.233.205.91    N9K-C9336C-FX2
         Serial Number: FOCXXXXXXGS
          Is Monitored: true
                Reason: None
      Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                        9.3(5)
        Version Source: CDP
    cluster1::*>
  5. Desactive la reversión automática en los LIF del clúster. Las LIF del clúster realizan la conmutación por error al conmutador del clúster asociado y permanecen allí mientras se realiza el procedimiento de actualización en el conmutador de destino:

    network interface modify -vserver Cluster -lif * -auto-revert false

  6. Descarga e instala el software NX-OS y la imagen EPLD. Los pasos pueden variar en función de tu versión actual de NX-OS y la versión de NX-OS de destino.

    Selecciona la pestaña que se ajuste a tu situación:

    • Actualizar a 10.4(5)(M)

    • Actualizar de 10.4(5)(M) o anterior a 10.5(3)(F) o posterior

    • Actualizar de 10.5(3)(F) a una versión posterior

Actualizar a 10.4(5)(M)
  1. Copia el software NX-OS y las imágenes EPLD en el switch Nexus 9336C-FX2.

    copy <protocol>: bootflash: vrf management

    Ejemplo
    cs2# *copy sftp: bootflash: vrf management*
    Enter source filename: */code/nxos.10.4.5.M.bin*
    Enter hostname for the sftp server: *172.19.2.1*
    Enter username: *user1*
    
    Outbound-ReKey for 172.19.2.1:22
    Inbound-ReKey for 172.19.2.1:22
    user1@172.19.2.1's password:
    sftp> *progress*
    Progress meter enabled
    sftp> *get /code/nxos.10.4.5.M.bin /bootflash/nxos.10.4.5.M.bin*
    /code/nxos.10.4.5.M.bin  100% 1261MB   9.3MB/s   02:15
    sftp> *exit*
    Copy complete, now saving to disk (please wait)...
    Copy complete.
    
    
    cs2# *copy sftp: bootflash: vrf management*
    Enter source filename: */code/n9000-epld.10.4.5.M.img*
    Enter hostname for the sftp server: *172.19.2.1*
    Enter username: *user1*
    
    Outbound-ReKey for 172.19.2.1:22
    Inbound-ReKey for 172.19.2.1:22
    user1@172.19.2.1's password:
    sftp> *progress*
    Progress meter enabled
    sftp> *get /code/n9000-epld.10.4.5.M.img /bootflash/n9000-epld.10.4.5.M.img*
    /code/n9000-epld.10.4.5.M.img  100%  161MB   9.5MB/s   00:16
    sftp> *exit*
    Copy complete, now saving to disk (please wait)...
    Copy complete.
  2. Verifique la versión en ejecución del software NX-OS:

    show version

    Ejemplo
    cs2# *show version*
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (C) 2002-2020, Cisco and/or its affiliates.
    All rights reserved.
    The copyrights to certain works contained in this software are
    owned by other third parties and used and distributed under their own
    licenses, such as open source.  This software is provided "as is," and unless
    otherwise stated, there is no warranty, express or implied, including but not
    limited to warranties of merchantability and fitness for a particular purpose.
    Certain components of this software are licensed under
    the GNU General Public License (GPL) version 2.0 or
    GNU General Public License (GPL) version 3.0  or the GNU
    Lesser General Public License (LGPL) Version 2.1 or
    Lesser General Public License (LGPL) Version 2.0.
    A copy of each such license is available at
    http://www.opensource.org/licenses/gpl-2.0.php and
    http://opensource.org/licenses/gpl-3.0.html and
    http://www.opensource.org/licenses/lgpl-2.1.php and
    http://www.gnu.org/licenses/old-licenses/library.txt.
    
    Software
      BIOS: version 08.38
      NXOS: version 10.3(5)
      BIOS compile time:  05/29/2020
      NXOS image file is: bootflash:///nxos.10.3.5.bin
      NXOS compile time:  4/28/2020 21:00:00 [04/29/2020 02:28:31]
    
    
    Hardware
      cisco Nexus9000 C9336C-FX2 Chassis
      Intel(R) Xeon(R) CPU E5-2403 v2 @ 1.80GHz with 8154432 kB of memory.
      Processor Board ID FOC20291J6K
    
      Device name: cs2
      bootflash:   53298520 kB
    Kernel uptime is 0 day(s), 0 hour(s), 3 minute(s), 42 second(s)
    
    
    Last reset at 157524 usecs after Mon Nov  2 18:32:06 2020
      Reason: Reset Requested by CLI command reload
      System version: 9.3(4)
      Service:
    
    plugin
      Core Plugin, Ethernet Plugin
    
    Active Package(s):
    
    
    cs2#
  3. Instale la imagen NX-OS.

    La instalación del archivo de imagen provoca que este se cargue cada vez que se reinicie el switch.

    install all nxos bootflash:<bin_file_name>

    Ejemplo
    cs2# *install all nxos bootflash:nxos.10.4.5.M.bin*
    
    Installer will perform compatibility check first. Please wait.
    Installer is forced disruptive
    
    Verifying image bootflash:/nxos.10.4.5.M.bin for boot variable "nxos".
    [] 100% -- SUCCESS
    
    Verifying image type.
    [] 100% -- SUCCESS
    
    Preparing "nxos" version info using image bootflash:/nxos.10.4.5.M.bin.
    [] 100% -- SUCCESS
    
    Preparing "bios" version info using image bootflash:/nxos.10.4.5.M.bin.
    [] 100% -- SUCCESS
    
    Performing module support checks.
    [] 100% -- SUCCESS
    
    Notifying services about system upgrade.
    [] 100% -- SUCCESS
    
    
    Compatibility check is done:
    Module  Bootable  Impact          Install-type  Reason
    ------  --------  --------------- ------------  ---------
      1     yes       Disruptive      Reset         Default upgrade is not hitless
    
    
    Images will be upgraded according to following table:
    
    Module   Image    Running-Version(pri:alt)                 New-Version         Upg-Required
    ------- --------- ---------------------------------------- ------------------- ------------
      1      nxos     10.3(5)                                   10.4.5(M)              yes
      1      bios     v08.37(01/28/2020):v08.23(09/23/2015)    v08.38(05/29/2020)      yes
    
    
    Switch will be reloaded for disruptive upgrade.
    
    Do you want to continue with the installation (y/n)? [n] *y*
    
    Install is in progress, please wait.
    
    Performing runtime checks.
    [] 100% -- SUCCESS
    
    Setting boot variables.
    [] 100% -- SUCCESS
    
    Performing configuration copy.
    [] 100% -- SUCCESS
    
    Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
    Warning: please do not remove or power off the module at this time.
    [] 100% -- SUCCESS
    
    Finishing the upgrade, switch will reboot in 10 seconds.
  4. Verifique la nueva versión del software NX-OS después de que el switch se haya reiniciado:

    show version

    Ejemplo
    cs2# *show version*
    
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (C) 2002-2020, Cisco and/or its affiliates.
    All rights reserved.
    The copyrights to certain works contained in this software are
    owned by other third parties and used and distributed under their own
    licenses, such as open source.  This software is provided "as is," and unless
    otherwise stated, there is no warranty, express or implied, including but not
    limited to warranties of merchantability and fitness for a particular purpose.
    Certain components of this software are licensed under
    the GNU General Public License (GPL) version 2.0 or
    GNU General Public License (GPL) version 3.0  or the GNU
    Lesser General Public License (LGPL) Version 2.1 or
    Lesser General Public License (LGPL) Version 2.0.
    A copy of each such license is available at
    http://www.opensource.org/licenses/gpl-2.0.php and
    http://opensource.org/licenses/gpl-3.0.html and
    http://www.opensource.org/licenses/lgpl-2.1.php and
    http://www.gnu.org/licenses/old-licenses/library.txt.
    
    Software
      BIOS: version 05.33
      NXOS: version 10.4.5(M)  BIOS compile time:  09/08/2018
      NXOS image file is: bootflash:///nxos.10.4.5.M.bin
      NXOS compile time:  11/4/2018 21:00:00 [11/05/2018 06:11:06]
    
    
    Hardware
      cisco Nexus9000 C9336C-FX2 Chassis
      Intel(R) Xeon(R) CPU E5-2403 v2 @ 1.80GHz with 8154432 kB of memory.
      Processor Board ID FOC20291J6K
    
      Device name: cs2
      bootflash:   53298520 kB
    Kernel uptime is 0 day(s), 0 hour(s), 3 minute(s), 42 second(s)
    
    Last reset at 277524 usecs after Mon Nov  2 22:45:12 2020
      Reason: Reset due to upgrade
      System version: 10.4.5(M)
      Service:
    
    plugin
      Core Plugin, Ethernet Plugin
    
    Active Package(s):
  5. Actualice la imagen EPLD y reinicie el switch.

    show version module 1 epld

    install epld bootflash:<image_file_name> module all

    Ejemplo
    cs2# *show version module 1 epld*
    
    EPLD Device                     Version
    ---------------------------------------
    MI   FPGA                        0x7
    IO   FPGA                        0x17
    MI   FPGA2                       0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
    
    cs2# *install epld bootflash:n9000-epld.10.4.5.M.img module all*
    Compatibility check:
    Module  Type      Upgradable        Impact      Reason
    ------  --------- ----------------- ----------- -----------
         1  SUP       Yes               disruptive  Module Upgradable
    
    Retrieving EPLD versions.... Please wait.
    Images will be upgraded according to following table:
    Module  Type   EPLD              Running-Version   New-Version  Upg-Required
    ------- ------ ----------------- ----------------- ------------ ------------
         1  SUP    MI FPGA           0x07              0x07         No
         1  SUP    IO FPGA           0x17              0x19         Yes
         1  SUP    MI FPGA2          0x02              0x02         No
    The above modules require upgrade.
    The switch will be reloaded at the end of the upgrade
    Do you want to continue (y/n) ?  [n] *y*
    
    Proceeding to upgrade Modules.
    
    Starting Module 1 EPLD Upgrade
    
    Module 1 : IO FPGA [Programming] : 100.00% (     64 of      64 sectors)
    Module 1 EPLD upgrade is successful.
    Module   Type  Upgrade-Result
    -------- ----- --------------
         1   SUP   Success
    
    EPLDs upgraded.
    
    Module 1 EPLD upgrade is successful.
  6. Tras reiniciar el switch, vuelva a iniciar sesión y verifique que la nueva versión de EPLD se haya cargado correctamente.

    show version module 1 epld

    Ejemplo
    cs2# *show version module 1 epld*
    
    EPLD Device                     Version
    ---- -------------------------- -------
    MI   FPGA                        0x7
    IO   FPGA                        0x19
    MI   FPGA2                       0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
Actualizar de 10.4(5)(M) o anterior a 10.5(3)(F) o posterior
  1. Copia el software NX-OS y la imagen EPLD en el conmutador Nexus 9336C-FX2.

    copy <protocol>: bootflash: vrf management

    Ejemplo
    cs2# *copy sftp: bootflash: vrf management*
    Enter source filename: */code/nxos.10.5.3.F.bin*
    Enter hostname for the sftp server: *172.19.2.1*
    Enter username: *user1*
    
    Outbound-ReKey for 172.19.2.1:22
    Inbound-ReKey for 172.19.2.1:22
    user1@172.19.2.1's password:
    sftp> *progress*
    Progress meter enabled
    sftp> *get /code/nxos.10.5.3.F.bin /bootflash/nxos.10.5.3.F.bin*
    /code/nxos.10.5.3.F.bin  100% 1261MB   9.3MB/s   02:15
    sftp> *exit*
    Copy complete, now saving to disk (please wait)...
    Copy complete.
    
    
    cs2# *copy sftp: bootflash: vrf management*
    Enter source filename: */code/n9000-epld.10.5.3.F.img*
    Enter hostname for the sftp server: *172.19.2.1*
    Enter username: *user1*
    
    Outbound-ReKey for 172.19.2.1:22
    Inbound-ReKey for 172.19.2.1:22
    user1@172.19.2.1's password:
    sftp> *progress*
    Progress meter enabled
    sftp> *get /code/n9000-epld.10.5.3.F.img /bootflash/n9000-epld.10.5.3.F.img*
    /code/n9000-epld.10.5.3.F.img  100%  161MB   9.5MB/s   00:16
    sftp> *exit*
    Copy complete, now saving to disk (please wait)...
    Copy complete.
  2. Verifique la versión en ejecución del software NX-OS:

    show version

    Ejemplo
    cs2# *show version*
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (C) 2002-2020, Cisco and/or its affiliates.
    All rights reserved.
    The copyrights to certain works contained in this software are
    owned by other third parties and used and distributed under their own
    licenses, such as open source.  This software is provided "as is," and unless
    otherwise stated, there is no warranty, express or implied, including but not
    limited to warranties of merchantability and fitness for a particular purpose.
    Certain components of this software are licensed under
    the GNU General Public License (GPL) version 2.0 or
    GNU General Public License (GPL) version 3.0  or the GNU
    Lesser General Public License (LGPL) Version 2.1 or
    Lesser General Public License (LGPL) Version 2.0.
    A copy of each such license is available at
    http://www.opensource.org/licenses/gpl-2.0.php and
    http://opensource.org/licenses/gpl-3.0.html and
    http://www.opensource.org/licenses/lgpl-2.1.php and
    http://www.gnu.org/licenses/old-licenses/library.txt.
    
    Software
      BIOS: version 08.38
      NXOS: version 10.5.3(F)
      BIOS compile time:  05/29/2020
      NXOS image file is: bootflash:///nxos.10.5.3.F.bin
      NXOS compile time:  4/28/2020 21:00:00 [04/29/2020 02:28:31]
    
    
    Hardware
      cisco Nexus9000 C9336C-FX2 Chassis
      Intel(R) Xeon(R) CPU E5-2403 v2 @ 1.80GHz with 8154432 kB of memory.
      Processor Board ID FOC20291J6K
    
      Device name: cs2
      bootflash:   53298520 kB
    Kernel uptime is 0 day(s), 0 hour(s), 3 minute(s), 42 second(s)
    
    
    Last reset at 157524 usecs after Mon Nov  2 18:32:06 2020
      Reason: Reset Requested by CLI command reload
      System version: 9.3(4)
      Service:
    
    plugin
      Core Plugin, Ethernet Plugin
    
    Active Package(s):
    
    cs2#
  3. Instala las imágenes de NX-OS y EPLD.

La imagen EPLD no se actualiza automáticamente al actualizar a NX-OS 10.5(3)(F) y versiones posteriores. Después de que completes la actualización y el switch se reinicie, debes ejecutar el mismo comando de actualización install all otra vez.

  • En la segunda ronda de actualización se comprueba, pero se omite la actualización de NX-OS; solo se actualiza la imagen del EPLD.

  • Si ya has actualizado a NX-OS 10.5(3)(F) o una versión posterior, ambas imágenes se actualizan al mismo tiempo.

+ La instalación del archivo de imagen provoca que este se cargue cada vez que se reinicie el switch.

+ El siguiente paso muestra una actualización de NX-OS 10.4(5)(M) a 10.5(3)(F). La primera pasada realiza la actualización de NX-OS y la segunda pasada realiza la actualización de la imagen EPLD.

+ install all nxos bootflash:<nxos_image.bin>

+ .Ejemplo

Details
cs2# *install all nxos bootflash:nxos.10.5.3.F.bin*   <---- 1st pass updates NX-OS only

Installer will perform compatibility check first. Please wait.
Installer is forced disruptive

Verifying image bootflash:/nxos.10.5.3.F.bin for boot variable "nxos".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Preparing "nxos" version info using image bootflash:/nxos.10.5.3.F.bin.
[####################] 100% -- SUCCESS

Preparing "bios" version info using image bootflash:/nxos.10.5.3.F.bin.
[####################] 100% -- SUCCESS

Performing module support checks.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS


Compatibility check is done:
Module  Bootable  Impact          Install-type  Reason
------  --------  --------------- ------------  ---------
1       yes       Disruptive      Reset         Default upgrade is not hitless


Images will be upgraded according to following table:

Module   Image    Running-Version(pri:alt)                 New-Version          Upg-Required
------- --------- ---------------------------------------- -------------------- ------------ 
1        nxos     10.4(5)(M)                                10.5(3)(F)            yes
1        bios     v05.47(04/28/2022):v05.47(04/28/2022)    v05.53(01/22/2025)     yes

Switch will be reloaded for disruptive upgrade.

Do you want to continue with the installation (y/n)? [n] *y*

Install is in progress, please wait.

Performing runtime checks.
[####################] 100% -- SUCCESS

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS
[####################] 100% -- SUCCESS

Finishing the upgrade, switch will reboot in 10 seconds.


cs2# *install all nxos bootflash:nxos.10.5.3.F.bin*   <---- 2nd pass updates EPLD image only
 
Installer will perform compatibility check first. Please wait. 
Installer is forced disruptive
 
Verifying image bootflash:/nxos.10.5.3.F.bin for boot variable "nxos".
[####################] 100% -- SUCCESS
 
Verifying EPLD/FPGA image //bootflash/nxos.10.5.3.F.bin.
[####################] 100% -- SUCCESS
 
Verifying image type.
[####################] 100% -- SUCCESS
 
Preparing "nxos" version info using image bootflash:/nxos.10.5.3.F.bin.
[####################] 100% -- SUCCESS
 
Preparing "bios" version info using image bootflash:/nxos.10.5.3.F.bin.
[####################] 100% -- SUCCESS

Performing module support checks.
[####################] 100% -- SUCCESS
 
Notifying services about system upgrade.
[####################] 100% -- SUCCESS
 

Compatibility check is done:
Module  bootable  Impact          Install-type  Reason
------  --------  --------------  ------------  ------
1       yes       disruptive      reset         default upgrade is not hitless
27      yes       disruptive      none          default upgrade is not hitless
 
 
Images will be upgraded according to following table:
Module    Image                  Running-Version(pri:alt)              New-Version         Upg-Required
--------  ---------------------  ------------------------------------- -----------------  ------------
27        nxos                   10.4(5)(M)                            10.5(3)(F)             no
27        bios                   v05.53(01/22/2025):v05.47(04/28/2022) v05.53(01/22/2025)    no
 
 
FPGA microcode will be upgraded according to following table:
Module  Type  EPLD               Running-Version  Flashed-Version*   New-Version  Upg-Required
------  ----  -----------------  ---------------  ----------------   -----------  ------------
27      SUP   MI FPGA            0x5              0x5                0x5          No
27      SUP   IO FPGA            0x17             0x17               0x18         Yes

If Running-Version and Flashed-Version are different it implies that the system has not yet been reloaded for the new version to take effect.
 
EPLD Upgrade may result in multiple modules going offline.
 
 
Switch will be reloaded for disruptive upgrade.
 
Do you want to continue with the installation (y/n)?  [n] *y*
 
Install is in progress, please wait.

Setting boot variables.
[####################] 100% -- SUCCESS
 
Performing configuration copy.
[####################] 100% -- SUCCESS
Performing configuration copy.
[####################] 100% -- SUCCESS
 
Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.

Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS
 
Module 27: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.

Module 27: Refreshing compact flash and upgrading bios/loader/bootrom.
Warning: please do not remove or power off the module at this time.
[####################] 100% -- SUCCESS
 
EPLD/FPGA upgrade can take up to 4 mins.

Performing EPLD/FPGA upgrade.
[####################] 100% -- SUCCESS
 
Install has been successful.
  1. Verifique la nueva versión del software NX-OS después de que el switch se haya reiniciado:

    show version

    Ejemplo
    cs2# *show version*
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (C) 2002-2020, Cisco and/or its affiliates.
    All rights reserved.
    The copyrights to certain works contained in this software are
    owned by other third parties and used and distributed under their own
    licenses, such as open source.  This software is provided "as is," and unless
    otherwise stated, there is no warranty, express or implied, including but not
    limited to warranties of merchantability and fitness for a particular purpose.
    Certain components of this software are licensed under
    the GNU General Public License (GPL) version 2.0 or
    GNU General Public License (GPL) version 3.0  or the GNU
    Lesser General Public License (LGPL) Version 2.1 or
    Lesser General Public License (LGPL) Version 2.0.
    A copy of each such license is available at
    http://www.opensource.org/licenses/gpl-2.0.php and
    http://opensource.org/licenses/gpl-3.0.html and
    http://www.opensource.org/licenses/lgpl-2.1.php and
    http://www.gnu.org/licenses/old-licenses/library.txt.
    
    Software
      BIOS: version 05.33
      NXOS: version 10.5.3(f)
      BIOS compile time:  09/08/2018
      NXOS image file is: bootflash:///nxos.10.5.3.F.bin
      NXOS compile time:  11/4/2018 21:00:00 [11/05/2018 06:11:06]
    
    
    Hardware
      cisco Nexus9000 C9336C-FX2 Chassis
      Intel(R) Xeon(R) CPU E5-2403 v2 @ 1.80GHz with 8154432 kB of memory.
      Processor Board ID FOC20291J6K
    
      Device name: cs2
      bootflash:   53298520 kB
    Kernel uptime is 0 day(s), 0 hour(s), 3 minute(s), 42 second(s)
    
    Last reset at 277524 usecs after Mon Nov  2 22:45:12 2020
      Reason: Reset due to upgrade
      System version: 9.3(4)
      Service:
    
    plugin
      Core Plugin, Ethernet Plugin
    
    Active Package(s):
  2. Tras reiniciar el switch, vuelva a iniciar sesión y verifique que la nueva versión de EPLD se haya cargado correctamente.

    show version module 1 epld

    Ejemplo
    cs2# *show version module 1 epld*
    
    EPLD Device                     Version
    ---------------------------------------
    MI   FPGA                        0x7
    IO   FPGA                        0x19
    MI   FPGA2                       0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
    GEM  FPGA                        0x2
  1. Copia la imagen de NX-OS y EPLD en el primer conmutador.

    copy <protocol>: bootflash: vrf management

    El ejemplo usa sftp.

    Ejemplo
    cs2# *copy sftp: bootflash: vrf management*
    Enter source filename: *nxos64-cs.10.5.4.M.bin*
    Enter hostname for the sftp server: *172.19.2.1*
    Enter username: *user1*
    
    Outbound-ReKey for 172.19.2.1:22
    Inbound-ReKey for 172.19.2.1:22
    user1@172.19.2.1's password:
    sftp> *progress*
    Progress meter enabled
    sftp> *get /code/nxos64-cs.10.5.4.M.bin /bootflash/nxos64-cs.10.5.4.M.bin*
    /code/nxos64-cs.10.5.4.M.bin  100% 1261MB   9.3MB/s   02:15
    sftp> *exit*
    Copy complete, now saving to disk (please wait)...
    Copy complete.
  2. Verifica la versión de NX-OS que se está ejecutando:

    show version

    Ejemplo
    cs2# *show version*
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (C) 2002-2025, Cisco and/or its affiliates.
    All rights reserved.
    The copyrights to certain works contained in this software are
    owned by other third parties and used and distributed under their own
    licenses, such as open source.  This software is provided "as is," and unless
    otherwise stated, there is no warranty, express or implied, including but not
    limited to warranties of merchantability and fitness for a particular purpose.
    Certain components of this software are licensed under
    the GNU General Public License (GPL) version 2.0 or
    GNU General Public License (GPL) version 3.0  or the GNU
    Lesser General Public License (LGPL) Version 2.1 or
    Lesser General Public License (LGPL) Version 2.0.
    A copy of each such license is available at
    http://www.opensource.org/licenses/gpl-2.0.php and
    http://opensource.org/licenses/gpl-3.0.html and
    http://www.opensource.org/licenses/lgpl-2.1.php and
    http://www.gnu.org/licenses/old-licenses/library.txt.
    
    
    Software
      BIOS: version 01.14
      NXOS: version 10.5(3)(F) [Feature Release]
      Host NXOS: version 10.5(3)(F)
      BIOS compile time:  11/25/2024
      NXOS image file is: bootflash:///nxos.10.5.3.F.bin
      NXOS compile time:  02/27/2026 12:00:00 [03/14/2026 05:25:50]
      NXOS boot mode: LXC
    
    
    Hardware
      cisco  Nexus9000 C9336C-FX2 Chassis
      Intel(R) Xeon(R) CPU D-1633N @ 2.50GHz with 32802156 kB of memory.
      Processor Board ID FLMXXXXXXXX
      Device name: cs2
      bootflash:  115802886 kB
    
    
    Kernel uptime is 5 day(s), 2 hour(s), 13 minute(s), 21 second(s)
    
    
    Last reset at 3580 usecs after Thu Mar 5 15:55:08 2026
      Reason: Reset Requested by CLI command reload
      System version: 10.5.3(f)
      Service:
    
    
    plugin
      Core Plugin, Ethernet Plugin
    
    
    Active Package(s):
    
    cs2#
  3. Instala la imagen de NX-OS y EPLD.

    La instalación del archivo de imagen provoca que este se cargue cada vez que se reinicie el switch.

    install all nxos bootflash:<nxos_image.bin>

    El ejemplo usa la versión 10.5(4)(M) de NX-OS.

    Ejemplo
    cs2# *install all nxos bootflash:nxos64-cs.10.5.4.M.bin*
    
    Installer will perform compatibility check first. Please wait.
    Installer is forced disruptive
    
    Verifying image bootflash:/nxos64-cs.10.5.4.M.bin for boot variable "nxos".
    [####################] 100% -- SUCCESS
    
    Verifying image type.
    [####################] 100% -- SUCCESS
    
    Preparing "nxos" version info using image bootflash:/nxos64-cs.10.5.4.M.bin.
    [####################] 100% -- SUCCESS
    
    Preparing "bios" version info using image bootflash:/nxos64-cs.10.5.4.M.bin.
    [####################] 100% -- SUCCESS
    
    Performing module support checks.
    [####################] 100% -- SUCCESS
    
    Notifying services about system upgrade.
    [####################] 100% -- SUCCESS
    
    
    Compatibility check is done:
    Module  Bootable  Impact          Install-type  Reason
    ------  --------  --------------- ------------  ---------
      1     yes       Disruptive      Reset         Default upgrade is not hitless
    
    
    Images will be upgraded according to following table:
    
    Module   Image    Running-Version(pri:alt)            New-Version         Upg-Required
    ------- --------- ----------------------------------- ------------------- ------------
      1      nxos     10.5(3)(F)                          10.5(4)(M)          Yes
      1      bios     <current_version>                   <new_version>       No
    
    
    Switch will be reloaded for disruptive upgrade.
    
    Do you want to continue with the installation (y/n)? [n] *y*
    
    Install is in progress, please wait.
    
    Performing runtime checks.
    [####################] 100% -- SUCCESS
    
    Setting boot variables.
    [####################] 100% -- SUCCESS
    
    Performing configuration copy.
    [####################] 100% -- SUCCESS
    
    Module 1: Refreshing compact flash and upgrading bios/loader/bootrom.
    Warning: please do not remove or power off the module at this time.
    [####################] 100% -- SUCCESS
    
    Finishing the upgrade, switch will reboot in 10 seconds.
  4. Comprueba la nueva versión de NX-OS después de que el conmutador se haya reiniciado:

    show version

    Ejemplo
    cs2# *show version*
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (C) 2002-2025, Cisco and/or its affiliates.
    All rights reserved.
    The copyrights to certain works contained in this software are
    owned by other third parties and used and distributed under their own
    licenses, such as open source.  This software is provided "as is," and unless
    otherwise stated, there is no warranty, express or implied, including but not
    limited to warranties of merchantability and fitness for a particular purpose.
    Certain components of this software are licensed under
    the GNU General Public License (GPL) version 2.0 or
    GNU General Public License (GPL) version 3.0  or the GNU
    Lesser General Public License (LGPL) Version 2.1 or
    Lesser General Public License (LGPL) Version 2.0.
    A copy of each such license is available at
    http://www.opensource.org/licenses/gpl-2.0.php and
    http://opensource.org/licenses/gpl-3.0.html and
    http://www.opensource.org/licenses/lgpl-2.1.php and
    http://www.gnu.org/licenses/old-licenses/library.txt.
    
    
    Software
      BIOS: version 01.14
      NXOS: version 10.5(4)(M) [Feature Release]
      Host NXOS: version 10.5(4)(M)
      BIOS compile time:  11/25/2024
      NXOS image file is: bootflash:///nxos64-cs.10.5.4.M.bin
      NXOS compile time:  05/30/2026 12:00:00 [06/14/2026 05:25:50]
      NXOS boot mode: LXC
    
    
    Hardware
      cisco Nexus9000 C9336C-FX2 Chassis
      Intel(R) Xeon(R) CPU D-1633N @ 2.50GHz with 32802156 kB of memory.
      Processor Board ID FLMXXXXXXXX
      Device name: cs2
      bootflash:  115802886 kB
    
    
    Kernel uptime is 5 day(s), 2 hour(s), 13 minute(s), 21 second(s)
    
    
    Last reset at 3580 usecs after Thu Jun 5 15:55:08 2026
      Reason: Reset Requested by CLI command reload
      System version: 10.5(4)(M)
      Service:
    
    
    plugin
      Core Plugin, Ethernet Plugin
    
    
    Active Package(s):
  5. Comprueba que la nueva versión de EPLD se haya cargado correctamente:

    show install epld status

    El ejemplo usa la versión 10.5(4)(M) de EPLD.

    Ejemplo
    cs2# *show install epld status*
    
    1) Module 2 upgraded on Mon May  4 09:17:08 2026 (631239  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Apr 24 19:49:50 2026
    
    Status: EPLD Upgrade was Successful
    
    EPLD                             Curr Ver       Old Ver
    -------------------------------------------------------
    MI FPGA                         0x10014         0x1000b
    IO FPGA                         0x10033         0x10006
    
    2) Module 27 upgraded on Wed Apr  1 15:03:13 2026 (193093  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Mon Mar 16 03:28:47 2026
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    IO FPGA                         0x1002d         0x10020
    
    3) Module 28 upgraded on Wed Apr  1 14:59:53 2026 (843907  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Mon Mar 16 03:28:47 2026
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    IO FPGA                         0x1002d         0x10020
    
    4) Module 27 upgraded on Fri Mar 27 21:55:55 2026 (132290  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    FM-19 FPGA                      0x10006         0x10000
    FM-20 FPGA                      0x10006         0x10000
    FM-21 FPGA                      0x10006         0x10000
    FM-22 FPGA                      0x10006         0x10000
    FM-23 FPGA                      0x10006         0x10000
    FM-24 FPGA                      0x10006         0x10000
    FM-25 FPGA                      0x10006         0x10000
    FM-26 FPGA                      0x10006         0x10000
    
    5) Module 27 upgraded on Fri Mar 27 21:50:16 2026 (  4899  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    FM-19 FPGA                      0x10006         0x10000
    FM-20 FPGA                      0x10006         0x10000
    FM-21 FPGA                      0x10006         0x10000
    FM-22 FPGA                      0x10006         0x10000
    FM-23 FPGA                      0x10006         0x10000
    FM-24 FPGA                      0x10006         0x10000
    FM-25 FPGA                      0x10006         0x10000
    FM-26 FPGA                      0x10006         0x10000
    
    6) Module 27 upgraded on Fri Mar 27 21:44:36 2026 (775397  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    FM-19 FPGA                      0x10006         0x10000
    FM-20 FPGA                      0x10006         0x10000
    FM-21 FPGA                      0x10006         0x10000
    FM-22 FPGA                      0x10006         0x10000
    FM-23 FPGA                      0x10006         0x10000
    FM-24 FPGA                      0x10006         0x10000
    FM-25 FPGA                      0x10006         0x10000
    FM-26 FPGA                      0x10006         0x10000
    
    7) Module 27 upgraded on Fri Mar 27 21:38:58 2026 (330582  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    FM-19 FPGA                      0x10006         0x10000
    FM-20 FPGA                      0x10006         0x10000
    FM-21 FPGA                      0x10006         0x10000
    FM-22 FPGA                      0x10006         0x10000
    FM-23 FPGA                      0x10006         0x10000
    FM-24 FPGA                      0x10006         0x10000
    FM-25 FPGA                      0x10006         0x10000
    FM-26 FPGA                      0x10006         0x10000
    
    8) Module 27 upgraded on Fri Mar 27 21:33:19 2026 (112679  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    FM-19 FPGA                      0x10006         0x10000
    FM-20 FPGA                      0x10006         0x10000
    FM-21 FPGA                      0x10006         0x10000
    FM-22 FPGA                      0x10006         0x10000
    FM-23 FPGA                      0x10006         0x10000
    FM-24 FPGA                      0x10006         0x10000
    FM-25 FPGA                      0x10006         0x10000
    FM-26 FPGA                      0x10006         0x10000
    
    9) Module 27 upgraded on Fri Mar 27 21:27:41 2026 (957182  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    FM-19 FPGA                      0x10006         0x10000
    FM-20 FPGA                      0x10006         0x10000
    FM-21 FPGA                      0x10006         0x10000
    FM-22 FPGA                      0x10006         0x10000
    FM-23 FPGA                      0x10006         0x10000
    FM-24 FPGA                      0x10006         0x10000
    FM-25 FPGA                      0x10006         0x10000
    FM-26 FPGA                      0x10006         0x10000
    
    10) Module 27 upgraded on Fri Mar 27 21:22:03 2026 ( 90303  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    FM-19 FPGA                      0x10006         0x10000
    FM-20 FPGA                      0x10006         0x10000
    FM-21 FPGA                      0x10006         0x10000
    FM-22 FPGA                      0x10006         0x10000
    FM-23 FPGA                      0x10006         0x10000
    FM-24 FPGA                      0x10006         0x10000
    FM-25 FPGA                      0x10006         0x10000
    FM-26 FPGA                      0x10006         0x10000
    
    11) Module 1 upgraded on Fri Mar 27 21:16:24 2026 (240369  us)
    EPLD Install Image: EPLD image file 10.5.4.M. built on Fri Dec 12 11:15:18 2025
    
    Status: EPLD Upgrade was Successful
    
    EPLD                            Curr Ver        Old Ver
    -------------------------------------------------------
    MI FPGA                         0x10014         0x1000b
    IO FPGA                         0x10033         0x10006
  1. Verifica el estado de los puertos del clúster.

    1. Verifique que los puertos del clúster estén activos y en buen estado en todos los nodos del clúster:

      network port show -ipspace Cluster

      Mostrar ejemplo
      cluster1::*> network port show -ipspace Cluster
      
      Node: cluster1-01
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
      --------- ------------ ---------------- ---- ---- ------------ -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy  false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy  false
      
      Node: cluster1-02
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
      --------- ------------ ---------------- ---- ---- ------------ -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy  false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy  false
      
      Node: cluster1-03
                                                                              Ignore
                                                        Speed(Mbps)  Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper   Status   Status
      --------- ------------ ---------------- ---- ---- ------------ -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy  false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy  false
      
      Node: cluster1-04
                                                                             Ignore
                                                        Speed(Mbps) Health   Health
      Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status   Status
      --------- ------------ ---------------- ---- ---- ----------- -------- ------
      e0a       Cluster      Cluster          up   9000  auto/100000 healthy false
      e0b       Cluster      Cluster          up   9000  auto/100000 healthy false
    2. Verifique el estado del switch desde el clúster.

      network device-discovery show -protocol cdp

    Mostrar ejemplo
    cluster1::*> network device-discovery show -protocol cdp
    Node/       Local  Discovered
    Protocol    Port   Device (LLDP: ChassisID)  Interface         Platform
    ----------- ------ ------------------------- ----------------- --------------
    cluster1-01/cdp
                e0a    cs1                       Ethernet1/7       N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/7       N9K-C9336C-FX2
    cluster01-2/cdp
                e0a    cs1                       Ethernet1/8       N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/8       N9K-C9336C-FX2
    cluster01-3/cdp
                e0a    cs1                       Ethernet1/1/1     N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/1/1     N9K-C9336C-FX2
    cluster1-04/cdp
                e0a    cs1                       Ethernet1/1/2     N9K-C9336C-FX2
                e0b    cs2                       Ethernet1/1/2     N9K-C9336C-FX2
    
    cluster1::*> system cluster-switch show -is-monitoring-enabled-operational true
    Switch                      Type               Address          Model
    --------------------------- ------------------ ---------------- --------------
    cs1                         cluster-network    10.233.205.90    N9K-C9336C-FX2
         Serial Number: FOCXXXXXXGD
          Is Monitored: true
                Reason: None
      Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                        9.3(5)
        Version Source: CDP
    
    cs2                         cluster-network    10.233.205.91    N9K-C9336C-FX2
         Serial Number: FOCXXXXXXGS
          Is Monitored: true
                Reason: None
      Software Version: Cisco Nexus Operating System (NX-OS) Software, Version
                        9.3(5)
        Version Source: CDP
    
    2 entries were displayed.

    Dependiendo de la versión de RCF previamente cargada en el switch, es posible que observe la siguiente salida en la consola del switch cs1:

    2020 Nov 17 16:07:18 cs1 %$ VDC-1 %$ %STP-2-UNBLOCK_CONSIST_PORT: Unblocking port port-channel1 on VLAN0092. Port consistency restored.
    2020 Nov 17 16:07:23 cs1 %$ VDC-1 %$ %STP-2-BLOCK_PVID_PEER: Blocking port-channel1 on VLAN0001. Inconsistent peer vlan.
    2020 Nov 17 16:07:23 cs1 %$ VDC-1 %$ %STP-2-BLOCK_PVID_LOCAL: Blocking port-channel1 on VLAN0092. Inconsistent local vlan.
  2. Verifique que el clúster esté en buen estado:

    cluster show

    Mostrar ejemplo
    cluster1::*> cluster show
    Node                 Health   Eligibility   Epsilon
    -------------------- -------- ------------- -------
    cluster1-01          true     true          false
    cluster1-02          true     true          false
    cluster1-03          true     true          true
    cluster1-04          true     true          false
    4 entries were displayed.
    cluster1::*>
  3. Repite los pasos 6 al 8 para instalar el software NX-OS en el switch cs1.

  4. Verifique la conectividad de las interfaces del clúster remoto antes de habilitar la reversión automática en los LIF del clúster:

ONTAP 9.9.1 y posteriores

Puedes usar el network interface check cluster-connectivity comando para iniciar una comprobación de accesibilidad para la conectividad del clúster y luego mostrar los detalles:

network interface check cluster-connectivity start`y `network interface check cluster-connectivity show

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

NOTA: Espere unos segundos antes de ejecutar el programa. show comando para mostrar los detalles.

cluster1::*> network interface check cluster-connectivity show
                                  Source               Destination         Packet
Node   Date                       LIF                  LIF                 Loss
------ -------------------------- -------------------- ------------------- -----------
cluster1-01
       3/5/2022 19:21:18 -06:00   cluster1-01_clus2    cluster1-02-clus1   none
       3/5/2022 19:21:20 -06:00   cluster1-01_clus2    cluster1-02_clus2   none
cluster1-02
       3/5/2022 19:21:18 -06:00   cluster1-02_clus2    cluster1-01_clus1   none
       3/5/2022 19:21:20 -06:00   cluster1-02_clus2    cluster1-01_clus2   none
Todas las versiones de ONTAP

Para todas las versiones de ONTAP , también puede usar el cluster ping-cluster -node <name> comando para comprobar la conectividad:

cluster ping-cluster -node <name>

cluster1::*> cluster ping-cluster -node local
Host is cluster1-02
Getting addresses from network interface table...
Cluster cluster1-01_clus1 169.254.209.69 cluster1-01     e0a
Cluster cluster1-01_clus2 169.254.49.125 cluster1-01     e0b
Cluster cluster1-02_clus1 169.254.47.194 cluster1-02     e0a
Cluster cluster1-02_clus2 169.254.19.183 cluster1-02     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.19.183 to Remote 169.254.209.69
    Local 169.254.19.183 to Remote 169.254.49.125
    Local 169.254.47.194 to Remote 169.254.209.69
    Local 169.254.47.194 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. Activa la reversión automática en las LIF del clúster.

    network interface modify -vserver Cluster -lif * -auto-revert true

  2. Verifique que los LIF del clúster hayan vuelto a su puerto de origen:

    network interface show -vserver Cluster

    Mostrar ejemplo
    cluster1::*> network interface show -vserver Cluster
                Logical            Status     Network            Current             Current Is
    Vserver     Interface          Admin/Oper Address/Mask       Node                Port    Home
    ----------- ------------------ ---------- ------------------ ------------------- ------- ----
    Cluster
                cluster1-01_clus1  up/up      169.254.3.4/23     cluster1-01         e0b     true
                cluster1-01_clus2  up/up      169.254.3.5/23     cluster1-01         e0b     true
                cluster1-02_clus1  up/up      169.254.3.8/23     cluster1-02         e0b     true
                cluster1-02_clus2  up/up      169.254.3.9/23     cluster1-02         e0b     true
                cluster1-03_clus1  up/up      169.254.1.3/23     cluster1-03         e0b     true
                cluster1-03_clus2  up/up      169.254.1.1/23     cluster1-03         e0b     true
                cluster1-04_clus1  up/up      169.254.1.6/23     cluster1-04         e0b     true
                cluster1-04_clus2  up/up      169.254.1.7/23     cluster1-04         e0b     true
    cluster1::*>

    Si los LIF del clúster no han vuelto a sus puertos de origen, restáuralos manualmente desde el nodo local:

    network interface revert -vserver Cluster -lif <lif_name>

¿Que sigue?

Después de haber instalado o actualizado el software NX-OS, puedes "instalar o actualizar el archivo de configuración de referencia (RCF)".