[c-nsp] NCS4200 - re-badged ASR920 / ASR900 ?

[CiscoNSP List]

Specific interest here also....we are about to purchase a heap of 5501's, and ASR920's as PEs....now this NCS4200 has thrown a spanner in the works lol....XR across the board would be much nicer....but if its BU split/politics, then it will be interesting times ahead.


________________________________
From: cisco-nsp <cisco-nsp-bounces at puck.nether.net> on behalf of quinn snyder <snyderq at gmail.com>
Sent: Wednesday, 26 April 2017 6:23 AM
To: Gert Doering
Cc: cisco-nsp
Subject: Re: [c-nsp] NCS4200 - re-badged ASR920 / ASR900 ?


> On Apr 25, 2017, at 12:36 PM, Gert Doering <gert at greenie.muc.de> wrote:
>
> Now the interesting question is, of course, *which* NCS code... as there
> seem to be a number of different "NCS*" families.
>
> An ASR920-style device with IOS XR on it, and actually doing all the
> nice XR things, I'd love to see that.  Even if software upgrades would
> suck.

digging through my notes from the service provider partner vt meeting from last summer:

(*) ncs4200 positioned as tdm-to-ethernet conversion box to ease the movement from legacy networks to ethernet
(*) not considered a replacement for legacy dacs —- cost per port too high
(*) initial market meant to be larger carriers — “ncs” moniker helps with positioning in transport teams
(*) initial release will have parity with asr900-series (903/907/920) — including running ios-xe
(*) movement towards ios-xr expected sometime within 18 months of platform release; not in “ec” yet
(*) module parity between ncs4200 and asr900s at fcs
(*) modules may be developed in either platform that may not necessarily be absorbed into the other (think b/u split here)

thats all i could find.
we’re taking specific interest in this platform — as we’re deploying within several customer networks.

q.

--
quinn snyder | snyderq at gmail.com