[c-nsp] Upgrading from 3.0.6 to Denali-16.3.5b

[Tristan Gulyas]

Hi,

On 3850 multigigabit switches (12X48U, 24XS or 24XU), I'm seeing around 20 minutes from reboot to restoration of service, even on stacks.  I seem to recall the 24U models run quicker as they have less ASIC resources for programming.  This seems fairly consistent.  Are you using TFTP/SCP to transfer files? I've found that some transfers go at a glacial speed (at the point where they will time out occasionally); Cisco's recommendation to copy to local flash first improves the situation, but makes this a three step process (copy, reboot, clean).

We upgraded a test/QAT model last week that caused every switch in that layer 2 domain (~30 building distribution stacks) to learn EVERY MAC address on the network, which exceeded the 3750X MAC address table limits...

Downgrading the code made the issue disappear. 

We're still on a 3.7.x engineering release and targeting 16.3.5b for improvements in stacking stability and auto-upgrade features we specifically requested.

Cheers,
Tristan

> On 18 Jan 2018, at 7:59 am, Christina Klam <cklam at ias.edu> wrote:
> 
> All,
> 
> This is the second Cat3850 that I have tried to upgrade to Denali-16.3.5b.  Both take hours to go from expanding the files to finishing.  I am on hour two for the second switch.  Except for interface status messages about my management port (Gig 0/0), there is nothing going over the console.  I am just assuming that the upgrading is indeed happening.  When I did the first switch, it took hours as well, so I will be patient.  But I am not happy.
> 
> Fortunately, I have the luxury that these two switches were/are not in production at the time of their upgrades.  However, I will not have the luxury for the other 3850s.
> 
> What is your experience with upgrading to Denali or Everest?   This is beyond ridiculous.  
> 
> Regards,
> Christina
> _______________________________________________
> 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/