[c-nsp] XR 4.3.1 release date please

[Fredrik Vöcks]

I concur on this. We went 4.2.0 and 4.2.1 just after release and we have
had a fair share of very bad bugs causing network outage.

The .0 caused our linecards to reboot randomly and the .1 wrote wrong
routing into the CEF.

And if you are on 4.2.0 and looking to upgrade to any other version, just
look at the mandatory SMU's before you even can upgrade. Plain silly but
thats another discussion.

Fredrik Vöcks
Senior IP Network Engineer



On 2 January 2013 19:10, Mikael Abrahamsson <swmike at swm.pp.se> wrote:

> On Wed, 2 Jan 2013, Jared Mauch wrote:
>
>  If you are waiting for everyone to find the bugs in 4.3.0 and everyone
>> does that there will be nothing fixed for you ... It's always a good idea
>> to load up the code and give it a test.
>>
>
> Considering code quality in 4.2.1 (two forwarding bugs including one CEF
> bug), I'd say it's dubious to go for any .0 or .1 in any near future if one
> values network stability.
>
> I wish they started doing some kind of staggered release where new hw was
> introduced in software that didn't have a lot of other features at the same
> time. If one wanted to run RSP440 immediately, there was no choice but run
> software with a lot of other new features as well.
>
> But I guess it's good to go for .2 or .3 for any new major hardware
> release introduced in .0, because then there will have been other people
> living through 6-9 months of burn-in on the new software (because they
> wanted the new hw immediately) so in .2 a lot of things will have been
> fixed.
>
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
>
> ______________________________**_________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/**mailman/listinfo/cisco-nsp<https://puck.nether.net/mailman/listinfo/cisco-nsp>
> archive at http://puck.nether.net/**pipermail/cisco-nsp/<http://puck.nether.net/pipermail/cisco-nsp/>
>