[c-nsp] ME3600x-cx 153-3.S any major pitfalls?

Wed Oct 2 00:29:47 EDT 2013

BU would also recommend 15.3(3)S1 if you are planning to upgrade to 15.3(3)S code base.

Best Regards,

[http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg]

Waris Sagheer
Technical Marketing Manager
Service Provider Access Group
waris at cisco.com<mailto:waris at cisco.com>
Phone: +1 408 853 6682
Mobile: +1 408 835 1389

CCIE - 19901

<http://www.cisco.com/>

[Think before you print.] Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html

From: Jason Lixfeld <jason at lixfeld.ca<mailto:jason at lixfeld.ca>>
Date: Monday, September 30, 2013 3:27 AM
To: adam vitkovsky <adam.vitkovsky at swan.sk<mailto:adam.vitkovsky at swan.sk>>
Cc: "cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>" <cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>>
Subject: Re: [c-nsp] ME3600x-cx 153-3.S any major pitfalls?

What is the bug?

15.3(3)S is considered a long-live release, so it will get support for a long time; it's definitely the train to be on.  It is miles ahead of 15.2 and 15.1 in terms of features and stability, from my perspective.

That said, I've been working with engineering and the BU for the last ~5 months getting bugs identified and fixed (most from pre-15.3).  As such, I might try to convince you to wait for at least 15.3(3)S1 depending on features:

PI code for BGP signaled VPLS cause label mismatch, multiple ports in egress SPAN cause packet loss, a lockup issue triggered by v4/v6 combo traffic, packet loss across the ASICs on some HW revisions, packet loss < 468 byte packets, IGMP snooping, shared CPU queue between ARP and RP being way too shallow and one or two other issues are still persistent in, or fresh for in 15.3(3)S.

If you run v6 and/or egress ACLs and have had odd and unexplainable box lookups (console works, however), maybe even wait for 15.3(3)S2 (or plan an upgrade for 1Q14 when it's released).

Sent from my iPhone

On Sep 30, 2013, at 5:44 AM, Adam Vitkovsky <adam.vitkovsky at swan.sk<mailto:adam.vitkovsky at swan.sk>> wrote:
Hi folks,
Unfortunately we have hit a serious bug and the fix is available only in
153-3.S.
So I'd like to ask whether there's anyone running 153-3.S in production and
what are your thoughts so far?
Thanks
adam
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at 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 at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/