On 2012-05-30, at 3:27 AM, Phil Mayers wrote: > On 05/29/2012 11:49 PM, Jason Lixfeld wrote: >> Hi Piotr, >> >> Both linecards (including DFCs), chassis and power supplies were >> replaced. >> >> The only common element left is the Supervisor. The standby >> Supervisor was replaced on a prior RMA, but there has been no >> (obvious) indication on either the part of TAC or myself to suggest >> the active Supervisor is somehow responsible. >> >> The chassis was rebooted this most recent time and has cleared the >> error and it hasn't resurfaced in the few days since, but that >> doesn't give me much comfort. >> > > It could easily just be a software bug; I'm a bit surprised TAC didn't > suggest such. Similar (but different) TCAM mis-programming errors were > endemic on early 12.2(33)SX releases on the 6500 (same hardware).
Indeed. I'm still waiting to hear back on what their findings are; whether we should RMA more hardware or whether someone can find a bug somewhere. > Do you have any upgrade/downgrade options available? We're running 15.2(2)S and has been highly touted by my account team as being pretty stable and having a long lifecycle. > With regards deciding if hardware is faulty; have you run a full (including > all the disruptives) GOLD diag set? 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. > _______________________________________________ > 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/
