[c-nsp] Nexus 7k Upgrade Path

[Randy]

To OP:
My 2 cents: If at all possible, use traditional-upgrade.

Personal-experience attempting ISSU on 65xx, 7ks, 9ks:
Mixed-Bag - some went flawlessely and others; sideways(outage). I have also experienced the *sideways* upgrade after a few months: vendor's recommendation was to "reload"
./Randy




________________________________
From: Bradley Ordner <bradinusa at hotmail.com>
To: Hunter Fuller <hf0002 at uah.edu> 
Cc: cisco-nsp NSP <cisco-nsp at puck.nether.net>
Sent: Friday, February 23, 2018 5:27 PM
Subject: Re: [c-nsp] Nexus 7k Upgrade Path



I’ll be honest I was pretty confident after reading the config guide on the website. This was going to happen this weekend but I wanted more time to prepare. 

The config guide does say ‘one command does it all’ which sounded great! I wasn’t aware of some of the issues people have seen such as config missing. 

It’s impossible to take this thing out of service as well so I need a good outage to perform this work at two data centres. Device has been online for almost two years as well. 

My only small concern was Cisco’s recommended and stable release is 6.x. I thought they would have had some thing closer to 8.

Brad Ordner 

Sent from my iPhone

> On 24 Feb 2018, at 10:17 am, Hunter Fuller <hf0002 at uah.edu> wrote:
> 
> On Fri, Feb 23, 2018 at 8:06 AM Justin M. Streiner <streiner at cluebyfour.org>
> wrote:
> 
>> Vendors also sometimes conflate "ISSU" and "hitless", or their
>> documentation doesn't always make it clear that an ISSU carries the
>> potential of outages.
> 
> 
> For what it is worth - there is a NX-OS command for checking whether an
> ISSU will be hitless: "show install all impact ?" will show you what you
> need to know.
> 
> We don't run much Nexus stuff, but we did upgrade our Nexus 7010 from
> version 4.something all the way to 7.2 with only ISSU. We had to do some
> careful planning, and some ISSU did fail, but the failure and rollback was
> just as hitless as the successes, and it told us what needed to be
> corrected for the future.
> 
> So far so good, with this strategy. I am very surprised to hear people
> talking about their problems with the ISSU process. I could not be happier
> with it.
> 
> # show system uptime
> System start time:          Sat Dec 20 17:54:34 2014
> System uptime:              1161 days, 4 hours, 36 minutes, 22 seconds
> 
> -- 
> 
> --
> Hunter Fuller
> Network Engineer
> VBH Annex B-5
> +1 256 824 5331
> 
> Office of Information Technology
> The University of Alabama in Huntsville
> Systems and Infrastructure
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/