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 <[email protected]> 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 [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
