[Cisco-asr9k-ug] NCS5500 -- was RE: [Marketing Mail] Re: ASR 9k upgrade path from 5.3.x to 6.4.x?
Xander Thuijs (xthuijs)
xthuijs at cisco.com
Thu Oct 11 11:56:48 EDT 2018
We can totally use this mailer group for ncs55 discussions also for my taste!!
xander
On 10/11/18, 11:49 AM, "cisco-asr9k-ug on behalf of german.martinez at orange.com" <cisco-asr9k-ug-bounces at puck.nether.net on behalf of german.martinez at orange.com> wrote:
Here most of our purchases/upgrades are NCS as well.
-----Original Message-----
From: cisco-asr9k-ug [mailto:cisco-asr9k-ug-bounces at puck.nether.net] On Behalf Of Jared Mauch
Sent: Thursday, October 11, 2018 11:00 AM
To: Cameron Byrne
Cc: Kozak, Marcin; cisco-asr9k-ug at puck.nether.net
Subject: Re: [Cisco-asr9k-ug] NCS5500 -- was RE: [Marketing Mail] Re: [EXTERNAL] ASR 9k upgrade path from 5.3.x to 6.4.x?
At Akamai we’re looking at the 5502-SE for some use-cases, but it’s still BCM silicon vs Cisco silicon which is disappointing. I know folks are pushing for low cost, but the lack of chipset diversity in the market is also a big concern of mine.
We’re in the process of decomm’ing most of our 9K’s and won’t be going to 6.x unless it’s on something new. We just don’t have the capacity for maintaining the high operational cost of the platform.
- Jared
> On Oct 11, 2018, at 10:54 AM, Byrne, Cameron <Cameron.Byrne at T-Mobile.com> wrote:
>
> Just to chime in here.
>
> We are capping our 9922 with Tomahawk and HODL for 5.3.4, which we will likely need one more XR upgrade (32bit) before the gear goes EOS.
>
> Ripping out all the commons to get the Lightspeed and this whole 64bit debacle seems like an adventure not worth taking.
>
> So, we are likely banking on Jericho 2 ncs5516s to replace the asr9922, pushing Cisco to pull in the GA date, and then just capping the Tomahawk 9922 in place.
>
> Can we pull in NCS5500 for our scope on this mailer? Worth having a new one for 5500? Thoughts on 5500
>
> CB
>
>
>
> -----Original Message-----
> From: cisco-asr9k-ug <cisco-asr9k-ug-bounces at puck.nether.net> On Behalf Of Kozak, Marcin
> Sent: Saturday, July 28, 2018 7:54 AM
> To: Job Snijders <job at ntt.net>; cisco-asr9k-ug at puck.nether.net
> Subject: [Marketing Mail] Re: [Cisco-asr9k-ug] [EXTERNAL] ASR 9k upgrade path from 5.3.x to 6.4.x?
>
> So we are not moving to 64 bit yet, but I think the only good plan we were able to come up with was multiple upgrades in a rather low maintenance window. We are tentatively planning for 6.1.4 -> 6.5.2 cXR -> 6.5.2 eXR.
>
> I think the most worrisome part of this unified FPD issue for us is the RMA depot sparing. We are working with our Cisco account team to make sure that any sparing depots that would potentially be used for RMA in areas where we will be upgrading to eXR have had some kind of purge of all line cards that have been sitting in the depot for some time and replaced with new ones. Cisco BU did say that all new line cards will be shipped with a code that had unified FPD on it.
>
> On a separate note, is anyone evaluating Lightspeed? Any major issues found in testing that didn't have a committed fix date?
>
>
> Marcin Kozak
> Comcast Network Architecture
> m. 267-312-1221
>
>
>
> On 5/29/18, 7:26 PM, "cisco-asr9k-ug on behalf of Job Snijders" <cisco-asr9k-ug-bounces at puck.nether.net on behalf of job at ntt.net> wrote:
>
> Dear all,
>
> We're trying to figure out how to upgade from 5.3.4 to 6.4.1. Jumping
> that far seems to pose significant challenges. Reviewing documents such
> as and what we discovered during testing there seem to be a few hurdles
> to clear.
>
> https://supportforums.cisco.com/kxiwq67737/attachments/kxiwq67737/4441-docs-service-providers/4768/9/migrate_to_asr9k_64.pdf
>
> 1/ Some in our group suggested to ship management blades (already
> upgraded to 6.4.1) around the world. But it seems we can't stage 6.4.1
> on a management blade, starting with IOS XR 6.1.1 there is this "unified
> FPD" thing. The LCs will not boot without first being upgraded to more a
> recent FPD, which is only possible by upgrading to a recent version of
> cXR.
>
> 2/ there are a few implications to the above. of course it will make the
> upgrade process more painful, but it also effects sparing parts. If a LC
> is shipped out and was previously booted on <= 5.x it wont come up in
> 6.4.1 eXR?
>
> 3/ An upgrade path such as 5.4.3 -> 6.0.1 -> 6.1.1 -> 6.4.1 will take
> too long. We're not in a position to bring routers down for extended
> periods of time for multiple installations (multiple hours), our
> maintenance windows aren't long enough.
>
> 4/ as far as we understand turboboot, it doesn't upgrade the FPD or
> has some restriction related to non-unified -> unified. So similar
> problem as in 1?
>
> 5/ And what is the downgrade process in case something in 6.4.1 isn't to
> your liking and you'd temporary want to back out?
>
> Sooo.... in short - how are y'all doing in terms of upgrading to 64-bit XR? :-)
>
> Kind regards,
>
> Job
>
> ps. Apologies if I'm sharing inaccurate information, corrections welcome.
> _______________________________________________
> cisco-asr9k-ug mailing list
> cisco-asr9k-ug at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-asr9k-ug
>
>
>
> _______________________________________________
> cisco-asr9k-ug mailing list
> cisco-asr9k-ug at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-asr9k-ug
> _______________________________________________
> cisco-asr9k-ug mailing list
> cisco-asr9k-ug at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-asr9k-ug
_______________________________________________
cisco-asr9k-ug mailing list
cisco-asr9k-ug at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-asr9k-ug
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
cisco-asr9k-ug mailing list
cisco-asr9k-ug at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-asr9k-ug
More information about the cisco-asr9k-ug
mailing list