Re: [c-nsp] Upgrading from 3.0.6 to Denali-16.3.5b
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 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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Upgrading from 3.0.6 to Denali-16.3.5b
Like Tristan - we have not made the Jump to Denali yet either. Most of our 3850's and 3850 stacks are on client sites that do not need the MPLS functionality. I have also no used the rollback command switch at upgrade time -Original Message- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Tristan Gulyas Sent: Thursday, January 18, 2018 8:44 AM To: Christina Klam Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Upgrading from 3.0.6 to Denali-16.3.5b This message originates from outside of your organisation. 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 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@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Upgrading from 3.0.6 to Denali-16.3.5b
Hi, On Wed, Jan 17, 2018, at 22:55, Nick Cutting wrote: > Denali is where they added MPLS, which is a major overhaul in this "slow > part of the upgrade" - the ASIC programming Is that MPLS like "Label Switching" (in which case it looks like a big WOW on Cat3K) or MPLS like "VRF-Lite" ? ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Upgrading from 3.0.6 to Denali-16.3.5b
Big dog mpls multiprocol bgp etc but the fancy stuff is missing Nick Cutting > On Jan 18, 2018, at 5:13 PM, Radu-Adrian FEURDEAN > wrote: > > This message originates from outside of your organisation. > > Hi, > >> On Wed, Jan 17, 2018, at 22:55, Nick Cutting wrote: >> >> Denali is where they added MPLS, which is a major overhaul in this "slow >> part of the upgrade" - the ASIC programming > > Is that MPLS like "Label Switching" (in which case it looks like a big WOW on > Cat3K) or MPLS like "VRF-Lite" ? > ___ > cisco-nsp mailing list cisco-nsp@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
