Instale o actualice el software NX-OS
Sugerir cambios
PDF
Siga este procedimiento para instalar o actualizar el software NX-OS en el switch de cluster Nexus 9336C-FX2.
Antes de comenzar, complete el procedimiento en "Prepare la instalación de NX-OS y RCF".
Revise los requisitos
-
Una copia de seguridad actual de la configuración del switch.
-
Un clúster en pleno funcionamiento (sin errores en los registros o problemas similares).
-
"Página del switch Cisco Ethernet"
Consulte en la tabla de compatibilidad del switch las versiones ONTAP y NX-OS compatibles.
-
"Guías de actualización y degradación de software"
Consulte las guías de software y actualización correspondientes disponibles en el sitio web de Cisco para obtener documentación completa sobre los procedimientos de actualización y degradación del conmutador Cisco.
-
"Matriz de ISSU y actualización de Cisco Nexus 9000 y 3000"
Proporciona información sobre actualización/degradación disruptiva para software Cisco NX-OS en los switches de la serie Nexus 9000 en función de tus versiones actuales y objetivo.
En la página, selecciona Actualización disruptiva y selecciona tu versión actual y la versión de destino de la lista desplegable.
Los ejemplos de este procedimiento utilizan la nomenclatura de conmutador y nodo siguiente:
-
Los nombres de los dos switches de Cisco son cs1 y cs2.
-
Los nombres de nodo son cluster1-01, cluster1-02, cluster1-03 y cluster1-04.
-
Los nombres de las 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.
-
La
cluster1::*>prompt indica el nombre del clúster.
Instale el software
Para ello, es necesario utilizar tanto comandos de la ONTAP como comandos de la serie Cisco Nexus 9000; los comandos de la ONTAP se usan a menos que se indique lo contrario.
-
Conecte el switch de clúster a la red de gestión.
-
Utilice el comando ping para verificar la conectividad con el servidor que aloja el software NX-OS y el RCF.
Muestra el ejemplo
Este ejemplo verifica que el switch puede llegar al servidor en la dirección IP 172.19.2.1:
cs2# ping 172.19.2.1 Pinging 172.19.2.1 with 0 bytes of data: Reply From 172.19.2.1: icmp_seq = 0. time= 5910 usec.
-
Muestre los puertos del clúster en cada nodo que están conectados a los switches de clúster:
network device-discovery showMuestra el 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 e0d cs2 Ethernet1/7 N9K-C9336C-FX2 cluster1-02/cdp e0a cs1 Ethernet1/8 N9K-C9336C-FX2 e0d 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::*> -
Compruebe el estado administrativo y operativo de cada puerto del clúster.
-
Compruebe que todos los puertos del clúster están up con un estado correcto:
network port show -role clusterMuestra el ejemplo
cluster1::*> network port show -role 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 e0d 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 e0d Cluster Cluster up 9000 auto/100000 healthy false 8 entries were displayed. Node: cluster1-03 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false Node: cluster1-04 Ignore Speed(Mbps) Health Health Port IPspace Broadcast Domain Link MTU Admin/Oper Status Status --------- ------------ ---------------- ---- ---- ----------- -------- ------ e0a Cluster Cluster up 9000 auto/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 healthy false cluster1::*> -
Compruebe que todas las interfaces del clúster (LIF) están en el puerto de inicio:
network interface show -role clusterMuestra el ejemplo
cluster1::*> network interface show -role 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 e0a true cluster1-01_clus2 up/up 169.254.3.5/23 cluster1-01 e0d true cluster1-02_clus1 up/up 169.254.3.8/23 cluster1-02 e0a true cluster1-02_clus2 up/up 169.254.3.9/23 cluster1-02 e0d true cluster1-03_clus1 up/up 169.254.1.3/23 cluster1-03 e0a 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 e0a true cluster1-04_clus2 up/up 169.254.1.7/23 cluster1-04 e0b true 8 entries were displayed. cluster1::*> -
Compruebe que el clúster muestra información de ambos switches de clúster:
system cluster-switch show -is-monitoring-enabled-operational true
Muestra el 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::*> -
-
Deshabilite la reversión automática en las LIF del clúster. Los LIF de clúster conmutan al switch del clúster asociado y permanecen allí mientras realiza el procedimiento de actualización en el switch de destino:
network interface modify -vserver Cluster -lif * -auto-revert false -
Copie las imágenes del software NX-OS y EPLD en el switch Nexus 9336C-FX2.
Muestra el ejemplo
cs2# copy sftp: bootflash: vrf management Enter source filename: /code/nxos.9.3.5.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.9.3.5.bin /bootflash/nxos.9.3.5.bin /code/nxos.9.3.5.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.9.3.5.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.9.3.5.img /bootflash/n9000-epld.9.3.5.img /code/n9000-epld.9.3.5.img 100% 161MB 9.5MB/s 00:16 sftp> exit Copy complete, now saving to disk (please wait)... Copy complete.
-
Compruebe la versión que se está ejecutando del software NX-OS:
show versionMuestra el 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 9.3(4) BIOS compile time: 05/29/2020 NXOS image file is: bootflash:///nxos.9.3.4.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#
-
Instale la imagen NX-OS.
La instalación del archivo de imagen hace que se cargue cada vez que se reinicia el conmutador.
Muestra el ejemplo
cs2# install all nxos bootflash:nxos.9.3.5.bin Installer will perform compatibility check first. Please wait. Installer is forced disruptive Verifying image bootflash:/nxos.9.3.5.bin for boot variable "nxos". [] 100% -- SUCCESS Verifying image type. [] 100% -- SUCCESS Preparing "nxos" version info using image bootflash:/nxos.9.3.5.bin. [] 100% -- SUCCESS Preparing "bios" version info using image bootflash:/nxos.9.3.5.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 9.3(4) 9.3(5) 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.
-
Compruebe la nueva versión del software NX-OS una vez que se haya reiniciado el switch:
show versionMuestra el 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 9.3(5) BIOS compile time: 09/08/2018 NXOS image file is: bootflash:///nxos.9.3.5.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):
-
Actualice la imagen de EPLD y reinicie el switch.
Muestra el 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.9.3.5.img module 1 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. -
Tras reiniciar el conmutador, vuelva a iniciar sesión y compruebe que la nueva versión de EPLD se ha cargado correctamente.
Muestra el 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
-
Compruebe el estado de los puertos del clúster en el clúster.
-
Compruebe que los puertos del clúster estén en buen estado en todos los nodos del clúster:
network port show -role clusterMuestra el ejemplo
cluster1::*> network port show -role 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/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 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/10000 healthy false e0b Cluster Cluster up 9000 auto/10000 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 e0d 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 e0d Cluster Cluster up 9000 auto/100000 healthy false 8 entries were displayed. -
Compruebe el estado del switch del clúster.
network device-discovery show -protocol cdp
Muestra el 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 e0d cs2 Ethernet1/7 N9K-C9336C-FX2 cluster01-2/cdp e0a cs1 Ethernet1/8 N9K-C9336C-FX2 e0d 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.Puede observar la siguiente salida en la consola del conmutador cs1 dependiendo de la versión RCF cargada previamente en el conmutador:
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.
-
-
Compruebe que el clúster esté en buen estado:
cluster showMuestra el 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::*>
-
Repita los pasos 6 a 13 para instalar el software NX-OS en el interruptor CS1.
-
Habilite la reversión automática en las LIF del clúster.
network interface modify -vserver Cluster -lif * -auto-revert true -
Compruebe que las LIF del clúster han vuelto a su puerto de inicio:
network interface show -role clusterMuestra el ejemplo
cluster1::*> network interface show -role 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 e0d true cluster1-01_clus2 up/up 169.254.3.5/23 cluster1-01 e0d true cluster1-02_clus1 up/up 169.254.3.8/23 cluster1-02 e0d true cluster1-02_clus2 up/up 169.254.3.9/23 cluster1-02 e0d 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 8 entries were displayed. cluster1::*>Si alguna LIF de clúster no ha regresado a sus puertos raíz, revertirla manualmente desde el nodo local:
network interface revert -vserver Cluster -lif <lif_name>