No. The issue has only repeated once since we replaced the hardware, so until it rears its head again and/or I can reproduce the issue at will, changing software is a little moot.
-- Sent from my mobile device On 2012-05-31, at 8:21 PM, [email protected] wrote: > Have you tried other code to try to rule out a 15S bug? Maybe SRE latest? > > > > On May 31, 2012, at 9:33 AM, Jason Lixfeld <[email protected]> wrote: > >> >> On 2012-05-31, at 9:02 AM, Phil Mayers wrote: >> >>> On 31/05/12 13:56, Jason Lixfeld wrote: >>> >>>> I've run: >>>> >>>> 'diagnostic start module<1-9> test all' to test all the modules. >>>> All seem to have passed. Not sure if there are other diags to run. >>> >>> At one point, those commands ran a sub-set of the diags; not sure if that's >>> changed in recent versions, but a full diag suite is (highly) disruptive to >>> traffic and (very) slow, so if you didn't see an outage, you haven't run >>> them all. >> >> It shut the linecards down, so I'm pretty sure it did what it was supposed >> to :) >> >> This box is isolated, so the tests being disruptive are a non-issue. >> _______________________________________________ >> 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/
