My Network Lab

Friday, June 3, 2022

Cisco Nexus 5000 Switch Virtual PortChannel (vPC) Configuration

Here's a nice link on how to configure a Virtual Port Channel (vPC) in a Cisco Nexus switch. This link is also comprehensive resource regarding vPC toplogy, design and configuration.

N5K-1# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

N5K-1(config)# feature lacp // ENABLE FEATURES FOR VPC

N5K-1(config)# feature vpc

N5K-1(config)#

N5K-1(config)# vpc ?

bind-vrf Bind vrf

domain Specify domain

nve Nve

N5K-1(config)# vpc domain ?

<1-1000> Domain id

N5K-1(config)# vpc domain 1 // NEXUS SWITCH CAN ONLY BE IN A SINGLE VPC DOMAIN

N5K-1(config-vpc-domain)# ?

auto-recovery VPC settings to enable auto recovery if peer is

presumed non-operational

delay Initialization delay

dual-active Configuration when peer link is down but peer is

alive

graceful Enable graceful features

ip Configure IP features

ipv6 Configure IPv6 features

layer3 Enable layer 3 functionality

no Negate a command or set its defaults

peer-config-check-bypass Ignore type checks on primary, when MCT is down

peer-gateway Enable L3 forwarding for packets destined to peer's

gateway mac-address

peer-keepalive Keepalive/Hello with peer switch

peer-switch Enable peer switch on vPC pair switches

role Role related configuration

shutdown Suspend vpc locally

system-mac Configure system mac address

system-priority Configure system priority

track Tracking object to suspend vPC if object goes down

end Go to exec mode

exit Exit from command interpreter

pop Pop mode from stack or restore from name

push Push current mode to stack or save it under name

where Shows the cli context you are in

N5K-1(config-vpc-domain)# role ?

priority Configure priority to be used during vPC role (primary/secondary)

election

N5K-1(config-vpc-domain)# role priority ?

<1-65535> Specify priority value

N5K-1(config-vpc-domain)# role priority 10 // FORCE N5K-1 TO ACT AS PRIMARY; LOWER IS PREFERRED

Warning:

!!:: vPCs will be flapped on current primary vPC switch while attempting role change ::!!

Note:

--------:: Change will take effect after user has re-initd the vPC peer-link ::--------

N5K-1(config-vpc-domain)#

N5K-1(config-vpc-domain)# peer-keepalive ?

destination Specify destination ip address of peer switch

N5K-1(config-vpc-domain)# peer-keepalive destination ?

<CR>

A.B.C.D IPv4 address (A.B.C.D) of destination

A:B::C:D IPv6 address of destination

hold-timeout Hold timeout to ignore stale peer alive messages

interval Enter interval in milleseconds

precedence Precedence

source Source interface for hello

tos Type of Service(IPV4)/Traffic Class(IPV6)

tos-byte Type of Service Byte(IPv4)/Traffic Class Octet(IPv6)

udp-port Enter UDP port number used for hello

vrf Vrf to be used for hello messages

N5K-1(config-vpc-domain)# peer-keepalive destination 10.10.2.9 ?

<CR>

hold-timeout Hold timeout to ignore stale peer alive messages

interval Enter interval in milleseconds

precedence Precedence

source Source interface for hello

tos Type of Service(IPV4)/Traffic Class(IPV6)

tos-byte Type of Service Byte(IPv4)/Traffic Class Octet(IPv6)

udp-port Enter UDP port number used for hello

vrf Vrf to be used for hello messages

N5K-1(config-vpc-domain)# peer-keepalive destination 10.10.2.9 source 10.10.2.8 ?

<CR>

hold-timeout Hold timeout to ignore stale peer alive messages

interval Enter interval in milleseconds

precedence Precedence

tos Type of Service(IPV4)/Traffic Class(IPV6)

tos-byte Type of Service Byte(IPv4)/Traffic Class Octet(IPv6)

udp-port Enter UDP port number used for hello

vrf Vrf to be used for hello messages

N5K-1(config-vpc-domain)# peer-keepalive destination 10.10.2.9 source 10.10.2.8 vrf ?

WORD Vrf to be used for hellos

default Known VRF name

management Known VRF name

N5K-1(config-vpc-domain)# peer-keepalive destination 10.10.2.9 source 10.10.2.8 vrf management // LAYER 3 HEARTBEAT; WILL USE management VRF BY DEFAULT

N5K-1(config-vpc-domain)# exit

N5K-1(config)#

N5K-1(config)# interface Eth1/47-48

N5K-1(config-if-range)# switchport mode trunk

N5K-1(config-if-range)# channel-group 10 mode active

N5K-1(config-if-range)# no shut

N5K-1(config-if-range)# exit

N5K-1(config)# interface port-channel10

N5K-1(config-if)# switchport mode trunk

N5K-1(config-if)# spanning-tree port type network

N5K-1(config-if)# vpc ?

<CR>

<1-4096> Specify a Virtual Port Channel number

orphan-port Orphan-port (non-vpc port)

peer-link Specify if this link is used for peer communication

N5K-1(config-if)# vpc peer-link // HIGH-SPEED BACKPLANE

Please note that spanning tree port type is changed to "network" port type on vPC peer-link.

This will enable spanning tree Bridge Assurance on vPC peer-link provided the STP Bridge Assurance

(which is enabled by default) is not disabled.

N5K-1(config-if)# end

N5K-1# show run vpc

!Command: show running-config vpc
!Time: Thu Apr 14 18:43:40 2005

version 7.3(8)N1(1)
feature vpc

vpc domain 1
role priority 10
peer-keepalive destination 10.10.2.9 source 10.10.2.8 vrf management

interface port-channel10
vpc peer-link

N5K-1# show vpc // MAIN VERIFICATION COMMAND

Legend:

(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 1

Peer status : peer link is down // CONFIGURE VPC IN NK5-2

vPC keep-alive status : Suspended (Destination IP not reachable)

Configuration consistency status : failed

Per-vlan consistency status : success

Configuration inconsistency reason: Consistency Check Not Performed

Type-2 inconsistency reason : Consistency Check Not Performed

vPC role : none established

Number of vPCs configured : 0

Peer Gateway : Disabled

Dual-active excluded VLANs : -

Graceful Consistency Check : Disabled (due to peer configuration)

Operational Layer3 Peer-router : Disabled

Auto-recovery status : Enabled (timeout = 240 seconds)

vPC Peer-link status

---------------------------------------------------------------------

id Port Status Active vlans

-- ---- ------ --------------------------------------------------

1 Po10 down -

-----

N5K-2# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

N5K-2(config)# feature lacp

N5K-2(config)# feature vpc

N5K-2(config)# vpc domain 1

N5K-2(config-vpc-domain)# role priority 20 // FORCE NK5-2 TO BE SECONDARY

Warning:

!!:: vPCs will be flapped on current primary vPC switch while attempting role change ::!!

Note:

--------:: Change will take effect after user has re-initd the vPC peer-link ::--------

N5K-2(config-vpc-domain)# peer-keepalive destination 10.10.2.8 source 10.10.2.9 vrf management

N5K-2(config-vpc-domain)# exit

N5K-2(config)# interface Eth1/47-48

N5K-2(config-if-range)# switchport mode trunk

N5K-2(config-if-range)# channel-group 10 mode active

N5K-2(config-if-range)# no shutdown

N5K-2(config-if-range)# exit

N5K-2(config)# interface port-channel10

N5K-2(config-if)# switchport mode trunk

N5K-2(config-if)# spanning-tree port type network

N5K-2(config-if)# vpc peer-link

Please note that spanning tree port type is changed to "network" port type on vPC peer-link.

This will enable spanning tree Bridge Assurance on vPC peer-link provided the STP Bridge Assurance

(which is enabled by default) is not disabled.

N5K-2(config-if)# end

N5K-2# show run vpc

!Command: show running-config vpc
!Time: Thu Apr 14 19:26:29 2005

version 7.3(8)N1(1)
feature vpc

vpc domain 1
role priority 20
peer-keepalive destination 10.10.2.8 source 10.10.2.9

interface port-channel10
vpc peer-link

N5K-2# show vpc

Legend:

(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 1

Peer status : peer link is down

vPC keep-alive status : peer is alive

Configuration consistency status : failed

Per-vlan consistency status : success

Configuration inconsistency reason: Consistency Check Not Performed

Type-2 inconsistency reason : Consistency Check Not Performed

vPC role : none established

Number of vPCs configured : 0

Peer Gateway : Disabled

Dual-active excluded VLANs : -

Graceful Consistency Check : Disabled (due to peer configuration)

Operational Layer3 Peer-router : Disabled

Auto-recovery status : Enabled (timeout = 240 seconds)

vPC Peer-link status

---------------------------------------------------------------------

id Port Status Active vlans

-- ---- ------ --------------------------------------------------

1 Po10 down -

N5K-2# show vpc

Legend:

(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 1

Peer status : peer adjacency formed ok // PEER ADJACENCY FORMED AFTER A FEW SECONDS

vPC keep-alive status : peer is alive

Configuration consistency status : success

Per-vlan consistency status : success

Type-2 consistency status : success

vPC role : secondary

Number of vPCs configured : 0

Peer Gateway : Disabled

Dual-active excluded VLANs : -

Graceful Consistency Check : Enabled

Operational Layer3 Peer-router : Disabled

Auto-recovery status : Enabled (timeout = 240 seconds)

vPC Peer-link status

---------------------------------------------------------------------

id Port Status Active vlans

-- ---- ------ --------------------------------------------------

1 Po10 up 1,99

N5K-2# show vpc role

vPC Role status

----------------------------------------------------

vPC role : secondary

Dual Active Detection Status : 0

vPC system-mac : 00:23:04:ee:be:01

vPC system-priority : 32667

vPC local system-mac : 00:de:fb:78:03:81

vPC local role-priority : 20

NK5-2# show vpc peer-keepalive

vPC keep-alive status : peer is alive

--Peer is alive for : (216) seconds, (223) msec

--Send status : Success

--Last send at : 2005.04.13 21:12:39 711 ms

--Sent on interface : mgmt0

--Receive status : Success

--Last receive at : 2005.04.13 21:12:39 712 ms

--Received on interface : mgmt0

--Last update from peer : (0) seconds, (667) msec

vPC Keep-alive parameters

--Destination : 10.10.2.8 // NK5-1 mgmt0 IP

--Keepalive interval : 1000 msec

--Keepalive timeout : 5 seconds

--Keepalive hold timeout : 3 seconds

--Keepalive vrf : management

--Keepalive udp port : 3200

--Keepalive tos : 192

-----

N5K-1# show vpc

Legend:

(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : 1

Peer status : peer adjacency formed ok

vPC keep-alive status : peer is alive

Configuration consistency status : success

Per-vlan consistency status : success

Type-2 consistency status : success

vPC role : primary

Number of vPCs configured : 0

Peer Gateway : Disabled

Dual-active excluded VLANs : -

Graceful Consistency Check : Enabled

Operational Layer3 Peer-router : Disabled

Auto-recovery status : Enabled (timeout = 240 seconds)

vPC Peer-link status

---------------------------------------------------------------------

id Port Status Active vlans

-- ---- ------ --------------------------------------------------

1 Po10 up 1,99

N5K-1# show vpc role

vPC Role status

----------------------------------------------------

vPC role : primary

Dual Active Detection Status : 0

vPC system-mac : 00:23:04:ee:be:01

vPC system-priority : 32667

vPC local system-mac : 00:de:fb:78:01:bc

vPC local role-priority : 10

N5K-1# show vpc peer-keepalive

vPC keep-alive status : peer is alive

--Peer is alive for : (171) seconds, (879) msec

--Send status : Success

--Last send at : 2005.04.13 20:33:08 941 ms

--Sent on interface : mgmt0

--Receive status : Success

--Last receive at : 2005.04.13 20:33:08 941 ms

--Received on interface : mgmt0

--Last update from peer : (0) seconds, (418) msec

vPC Keep-alive parameters

--Destination : 10.10.2.9 // NK5-2 mgmt0 IP

--Keepalive interval : 1000 msec

--Keepalive timeout : 5 seconds

--Keepalive hold timeout : 3 seconds

--Keepalive vrf : management

--Keepalive udp port : 3200

--Keepalive tos : 192

Tuesday, May 3, 2022

Cisco Nexus 5000 Switch NX-OS and Kickstart Code Upgrade

I upgraded a Cisco Nexus 3000 switch in a previous post. This time, I needed to upgrade a Cisco Nexus 5000 switch to NX-OS 7.3(8)N1(1).

I verified the current NX-OS software of the Nexus 5K switch to be 7.3(1)N1(1) using the show version command.

N5K# show version

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie

s_home.html

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

BIOS: version 2.1.7

Power Sequencer Firmware:

Module 1: v4.0

Fabric Power Sequencer Firmware: Module 1: version v4.0

Microcontroller Firmware: version v0.0.0.15

QSFP Microcontroller Firmware:

Module 1: v2.0.0.0

CXP Microcontroller Firmware:

Module not detected

kickstart: version 7.3(1)N1(1)

system: version 7.3(1)N1(1)

BIOS compile time: 06/16/2016

kickstart image file is: bootflash:///n6000-uk9-kickstart.7.3.1.N1.1.bin

kickstart compile time: 10/5/2016 19:00:00 [10/06/2016 05:19:57]

system image file is: bootflash:///n6000-uk9.7.3.1.N1.1.bin

system compile time: 10/5/2016 19:00:00 [10/06/2016 05:21:39]

Hardware

cisco Nexus 5672UP Chassis ("Nexus 5672UP Supervisor")

Intel(R) Xeon(R) CPU @ 1.80 with 8243284 kB of memory.

Processor Board ID FOC21091234

Device name: N5K

bootflash: 7692288 kB

Kernel uptime is 1 day(s), 15 hour(s), 25 minute(s), 23 second(s)

Last reset at 736681 usecs after Thu Apr 7 05:04:50 2005

Reason: Reset Requested by CLI command reload

System version: 7.3(1)N1(1)

Service:

plugin

Core Plugin, Ethernet Plugin

There's an upgrade path to follow per the Cisco Nexus 7.3(8)N1(1) Release Notes: 7.3(1) > 7.3(2) > 7.3(8). The said code release also list down the supported hardware such as the Nexus switch platforms, line card modules and Fabric Extenders (FEX).

So I upgraded first to 7.3(2)N1(1) and downloaded the main NX-OS and Kickstart image (BIOS).

I deleted some old image files to give space in bootflash using the delete command. It's best practice to keep the previous image in case you need to roll back or downgrade.

N5K# dir bootflash:

4096 Jan 01 00:02:07 2001 .patch/

24 Feb 16 13:02:35 2001 20010216_130235_poap_4722_dhcp.pcap

984128 Feb 16 14:14:59 2001 20010216_130235_poap_4722_init.log

24 Apr 07 05:12:28 2005 20050407_051228_poap_5299_dhcp.pcap

734565 Apr 07 05:32:44 2005 20050407_051228_poap_5299_init.log

35792384 Feb 17 11:25:28 2001 bootflah:

2518 Feb 16 14:37:40 2001 config

630 Jan 01 00:08:06 2001 license_FOC21081234_26_1.lic

4096 Dec 01 06:55:44 2001 lost+found/

37969408 Mar 25 06:53:39 2017 n6000-uk9-kickstart.7.1.0.N1.1b.bin

35792384 Feb 17 11:29:49 2001 n6000-uk9-kickstart.7.3.1.N1.1.bin

310229868 Mar 25 06:54:05 2017 n6000-uk9.7.1.0.N1.1b.bin

324046051 Feb 17 11:29:26 2001 n6000-uk9.7.3.1.N1.1.bin

4096 Feb 17 11:39:26 2001 scripts/

4096 Jan 01 00:02:06 2001 vdc_2/

4096 Jan 01 00:02:06 2001 vdc_3/

4096 Jan 01 00:02:06 2001 vdc_4/

4096 Feb 17 11:35:19 2001 virtual-instance/

4096 Jan 01 00:02:10 2001 virtual-instance-stby-sync/

11352 Apr 07 04:57:37 2005 vlan.dat

1654746 Apr 07 05:03:36 2005 vtp_debug.log

N5K# delete n6000-uk9-kickstart.7.1.0.N1.1b.bin

Do you want to delete "/n6000-uk9-kickstart.7.1.0.N1.1b.bin" ? (yes/no/abort) [y] y

N5K# delete n6000-uk9.7.1.0.N1.1b.bin

Do you want to delete "/n6000-uk9.7.1.0.N1.1b.bin" ? (yes/no/abort) [y] y

N5K# dir

4096 Jan 01 00:02:07 2001 .patch/

24 Feb 16 13:02:35 2001 20010216_130235_poap_4722_dhcp.pcap

984128 Feb 16 14:14:59 2001 20010216_130235_poap_4722_init.log

24 Apr 07 05:12:28 2005 20050407_051228_poap_5299_dhcp.pcap

734565 Apr 07 05:32:44 2005 20050407_051228_poap_5299_init.log

35792384 Feb 17 11:25:28 2001 bootflah:

2518 Feb 16 14:37:40 2001 config

630 Jan 01 00:08:06 2001 license_FOC21081234_26_1.lic

4096 Dec 01 06:55:44 2001 lost+found/

35792384 Feb 17 11:29:49 2001 n6000-uk9-kickstart.7.3.1.N1.1.bin

324046051 Feb 17 11:29:26 2001 n6000-uk9.7.3.1.N1.1.bin

4096 Feb 17 11:39:26 2001 scripts/

4096 Jan 01 00:02:06 2001 vdc_2/

4096 Jan 01 00:02:06 2001 vdc_3/

4096 Jan 01 00:02:06 2001 vdc_4/

4096 Feb 17 11:35:19 2001 virtual-instance/

4096 Jan 01 00:02:10 2001 virtual-instance-stby-sync/

11352 Apr 07 04:57:37 2005 vlan.dat

1654746 Apr 07 05:03:36 2005 vtp_debug.log

Use the copy command to transfer image files with the vrf keyword if using a source VRF.

N5K# copy ftp://ftpuser:ftp123@10.1.1.14/n6000-uk9-kickstart.7.3.2.N1.1.bin bootflash:

Enter vrf (If no input, current vrf 'default' is considered):

N5K# copy ftp://ftpuser:ftp123@10.1.1.14/n6000-uk9-kickstart.7.3.2.N1.1.bin bootflash: vrf ?

default Known VRF name

management Known VRF name

N5K# copy ftp://ftpuser:ftp123@10.1.1.14/n6000-uk9-kickstart.7.3.2.N1.1.bin bootflash: vrf management

Password: // ftp123

[#### ] 4.37MB

***** Transfer of file Completed Successfully *****

Copy complete, now saving to disk (please wait)...

N5K# copy ftp://ftpuser:ftp123@10.1.1.14/n6000-uk9.7.3.2.N1.1.bin bootflash: vrf management

Password:

[######### ] 10.49MB

***** Transfer of file Completed Successfully *****

Copy complete, now saving to disk (please wait)...

N5K# dir

4096 Jan 01 00:02:07 2001 .patch/

24 Feb 16 13:02:35 2001 20010216_130235_poap_4722_dhcp.pcap

984128 Feb 16 14:14:59 2001 20010216_130235_poap_4722_init.log

24 Apr 07 05:12:28 2005 20050407_051228_poap_5299_dhcp.pcap

734565 Apr 07 05:32:44 2005 20050407_051228_poap_5299_init.log

35792384 Feb 17 11:25:28 2001 bootflah:

2518 Feb 16 14:37:40 2001 config

630 Jan 01 00:08:06 2001 license_FOC2108R181_26_1.lic

35792384 Feb 17 11:29:49 2001 n6000-uk9-kickstart.7.3.1.N1.1.bin

35289088 Apr 08 23:42:56 2005 n6000-uk9-kickstart.7.3.2.N1.1.bin

324046051 Feb 17 11:29:26 2001 n6000-uk9.7.3.1.N1.1.bin

343742244 Apr 08 23:47:43 2005 n6000-uk9.7.3.2.N1.1.bin

4096 Feb 17 11:39:26 2001 scripts/

4096 Jan 01 00:02:06 2001 vdc_2/

4096 Jan 01 00:02:06 2001 vdc_3/

4096 Jan 01 00:02:06 2001 vdc_4/

4096 Feb 17 11:35:19 2001 virtual-instance/

4096 Jan 01 00:02:10 2001 virtual-instance-stby-sync/

11352 Apr 07 04:57:37 2005 vlan.dat

1654746 Apr 07 05:03:36 2005 vtp_debug.log

Usage for bootflash://

1220804608 bytes used

6136344576 bytes free

7357149184 bytes total

Verify the MD5 or SHA512 checksum using the show file command for any corruption during the file transfer. Just compare to the MD5 output on the Cisco download site.

N5K# show file bootflash:///n6000-uk9-kickstart.7.3.2.N1.1.bin md5sum

af50c5a3435dd971da57aa44b967598a

N5K# show file bootflash:///n6000-uk9.7.3.2.N1.1.bin md5sum

ef5943379bbef4be2800cb60b13f922b

It's also good practice to verify the new images using the show install command before the actual install or code upgrade.

N5K# show install all impact kickstart bootflash:///n6000-uk9-kickstart.7.3.2.N1.1.bin system bootflash:///n6000-uk9.7.3.2.N1.1.bin

Verifying image bootflash:/n6000-uk9-kickstart.7.3.2.N1.1.bin for boot variable "kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n6000-uk9.7.3.2.N1.1.bin for boot variable "system". // THIS WILL TAKE AROUND 5 MINUTES

[####################] 100% -- SUCCESS

Verifying image type.

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n6000-uk9.7.3.2.N1.1.bin.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.3.2.N1.1.bin.

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n6000-uk9.7.3.2.N1.1.bin.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.3.2.N1.1.bin.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n6000-uk9.7.3.2.N1.1.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 Non-disruptive install not supported if L3 was enabled

2 yes disruptive reset Non-disruptive install not supported if L3 was enabled

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------------- ---------------------- ---------------------- ------------

1 system 7.3(1)N1(1) 7.3(2)N1(1) yes

1 kickstart 7.3(1)N1(1) 7.3(2)N1(1) yes

1 bios v2.1.7(06/16/2016) v2.1.7(06/16/2016) no

1 power-seq v4.0 v4.0 no

1 fabric-power-seq v4.0 v4.0 no

2 power-seq v4.0 v4.0 no

1 microcontroller v0.0.0.15 v0.0.0.15 no

To perform the actual Nexus switch code upgrade, use the install command.

N5K# install all kickstart bootflash:///n6000-uk9-kickstart.7.3.2.N1.1.bin system bootflash:///n6000-uk9.7.3.2.N1.1.bin

Verifying image bootflash:/n6000-uk9-kickstart.7.3.2.N1.1.bin for boot variable "kickstart".

[####################] 100% -- SUCCESS

Verifying image bootflash:/n6000-uk9.7.3.2.N1.1.bin for boot variable "system".

[####################] 100% -- SUCCESS

Verifying image type.

[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n6000-uk9.7.3.2.N1.1.bin.

[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n6000-uk9-kickstart.7.3.2.N1.1.bin.

[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n6000-uk9.7.3.2.N1.1.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 Non-disruptive install not supported if L3 was enabled

2 yes disruptive reset Non-disruptive install not supported if L3 was enabled

Images will be upgraded according to following table:

Module Image Running-Version New-Version Upg-Required

------ ---------------- ---------------------- ---------------------- ------------

1 system 7.3(1)N1(1) 7.3(2)N1(1) yes

1 kickstart 7.3(1)N1(1) 7.3(2)N1(1) yes

1 bios v2.1.7(06/16/2016) v2.1.7(06/16/2016) no

1 power-seq v4.0 v4.0 no

1 fabric-power-seq v4.0 v4.0 no

2 power-seq v4.0 v4.0 no

1 microcontroller v0.0.0.15 v0.0.0.15 no

Switch will be reloaded for disruptive upgrade.

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

Install is in progress, please wait.

Performing runtime checks.

[####################] 100% -- SUCCESS

Setting boot variables.

[####################] 100% -- SUCCESS

Performing configuration copy.

[####################] 100% -- SUCCESS

Finishing the upgrade, switch will reboot in 10 seconds.

N5K# [156233.485298] Shutdown Ports..

[156233.520690] writing reset reason 49,

2005 Apr 9 00:29:48 N5K %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [156233.485298] Shutdown Ports.. - kernel

2005 Apr 9 00:29:48 N5K %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [156233.520690] writing reset reason 49, - kernel

Broadcast message from root (Sat Apr 9 00:29:53 2005):

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 4321) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "statsclient" (PID 4273) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "fs-daemon" (PID 4149) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "vman" (PID 4208) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Radius Daemon" (PID 4460) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Security Daemon" (PID 4249) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "res_mgr" (PID 4217) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "urib" (PID 4258) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "Cert_enroll Daemon" (PID 4251) is forced exit.

Apr 9 00:29:53 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "bios_daemon" (PID 4242) is forced exit.

INIT: Sending processes the KILL signal

Sending all processes the TERM signal...

Apr 9 00:30:00 %LIBSYSMGR-3-SIGTERM_FORCE_EXIT Service "icmpv6" (PID 4321) is forced exit.

Apr 9 00:30:00 %ICMPV6-3-MTS_RECV icmpv6 [4321] Error returned from mts_recv(), errno: Interrupted system call

Apr 9 00:30:00 %ADJMGR-2-MTS_RECV adjmgr [4283] MTS queue receive failed on AM LOW PRI queue: Interrupted system call

Sending all processes the KILL signal...

Unmounting filesystems...

[156252.392985] Resetting board

N5K-C5672UP BIOS v.2.1.7, Fri 06/17/2016, 02:54 PM

N5K-C5672UP BIOS v.2.1.7, Thu 06/16/2016

Booting kickstart image: bootflash:/n6000-uk9-kickstart.7.3.2.N1.1.bin

...............................................................................

.............................Image verification OK

Booting kernel

The Nexus code upgrade took around 7 mintues to complete. Perform similar steps to upgrade to 7.3(8)N1(1).

System is coming up ... Please wait ...

2005 Apr 9 00:36:51 N5K %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online

System is coming up ... Please wait ...

User Access Verification

N5K login: admin

Password:

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

The copyrights to certain works contained in this software are

owned by other third parties and used and distributed under

license. Certain components of this software are licensed under

the GNU General Public License (GPL) version 2.0 or the GNU

Lesser General Public License (LGPL) Version 2.1. A copy of each

such license is available at

http://www.opensource.org/licenses/gpl-2.0.php and

http://www.opensource.org/licenses/lgpl-2.1.php

N5K# show version

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie

s_home.html

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

BIOS: version 2.1.7

Power Sequencer Firmware:

Module 1: v4.0

Fabric Power Sequencer Firmware: Module 1: version v4.0

Microcontroller Firmware: version v0.0.0.15

QSFP Microcontroller Firmware:

Module not detected

SFP Microcontroller Firmware:

Module 1: v1.3.0.0

CXP Microcontroller Firmware:

Module not detected

kickstart: version 7.3(2)N1(1)

system: version 7.3(2)N1(1)

BIOS compile time: 06/16/2016

kickstart image file is: bootflash:///n6000-uk9-kickstart.7.3.2.N1.1.bin

kickstart compile time: 5/12/2017 23:00:00 [05/13/2017 11:15:12]

system image file is: bootflash:///n6000-uk9.7.3.2.N1.1.bin

system compile time: 5/12/2017 23:00:00 [05/13/2017 11:16:49]

Hardware

cisco Nexus 5672UP Chassis ("Nexus 5672UP Supervisor")

Intel(R) Xeon(R) CPU @ 1.80 with 8243276 kB of memory.

Processor Board ID FOC21091234

Device name: N5K

bootflash: 7692288 kB

Kernel uptime is 0 day(s), 0 hour(s), 6 minute(s), 49 second(s)

Last reset at 567632 usecs after Sat Apr 9 00:29:53 2005

Reason: Disruptive upgrade

System version: 7.3(1)N1(1)

Service:

plugin

Core Plugin, Ethernet Plugin

Active Package(s)