On ME3800X/ME3600X/3600X-24CX, I would recommend moving to 15.2(4)S2 or upcoming 15.2(4)S3 release.
Best Regards, Waris Sagheer Technical Marketing Manager Service Provider Access Group [email protected] Phone: +1 408 853 6682 Mobile: +1 408 835 1389 CCIE - 19901 <http://www.cisco.com/> 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 On 1/28/13 6:51 AM, "David Farrell" <[email protected]> wrote: >Just to add my £0.02 worth. > >We've been hit by issues in 15.2(2)S with respect to memory leaks in SSH >and also wacky forwarding behaviour in bridge-domains where >double-tagged frames are involved. > >Not fun, but looking good thus far on 15.2(4)S2. > >David. > >On 28/01/13 14:21, Jason Lixfeld wrote: >> Both are relatively new platforms. 9K a little more mature than the >>ME3600, although terminating a bunch of customers on an ASR9K is >>probably not a wise idea yet, given the fact that ISSU is still not >>there :( >> >> On 2013-01-28, at 3:41 AM, Fredrik Vöcks <[email protected]> >>wrote: >> >>> Yes that seems to solve it. >>> >>> We have invested in ME3600-X and ASR90xx for future scalability. In >>>the big picture its awesome but on a personal level it has made me >>>understand what it felt like being a Windows admin 10 years ago. >>> >>> /F >>> >>> On 27 January 2013 20:27, Jason Lixfeld <[email protected]> wrote: >>> I had the same issue. Seems to be the result of CSCua60395, at least >>>it was in our case. >>> >>> One thing - I'd suggest getting off of 15.2(2)S as soon as possible. >>>I've had numerous issues with this train (including S1) - random >>>lockups of switches (no bug id) requiring power cycle and MPLS issues >>>TAC *thinks* they have identified as CSCtz16622 which is fixed in >>>15.3(1)S, but they aren't sure :| >>> >>> On 2013-01-27, at 4:32 AM, Fredrik Vöcks <[email protected]> >>>wrote: >>> >>>> Hi, >>>> >>>> Im seeing high CPU utilisation on one of our ME3600-X devices. Trying >>>>to >>>> understand what is causing it but my googlefu seems weak. >>>> >>>> Anyone knows what the 'AC Switch' process is responsible for? >>>> >>>> #sh proc cpu sorted >>>> CPU utilization for five seconds: 48%/27%; one minute: 49%; five >>>>minutes: >>>> 50% >>>> PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY >>>>Process >>>> 156 47467992 229585577 206 19.03% 18.44% 18.39% 0 AC >>>>Switch >>>> >>>> >>>> #sh ver >>>> Cisco IOS Software, ME360x Software (ME360x-UNIVERSAL-M), Version >>>> 15.2(2)S1, RELEASE SOFTWARE (fc1) >>>> >>>> Regards, >>>> >>>> /F >>>> _______________________________________________ >>>> 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/ > >_______________________________________________ >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/
