-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sukumar, this is not actually a linecard, this is the supervisor itself (SUP720-3BXL) hence only two gigabit ports and none spare :(
I will ask the TAC to consider an RMA, many thanks for your help. Dave. Sukumar Subburayan (sukumars) wrote: > David, > > Unfortunately, there is no publicly available doc to interpret this data, as > much of these are very Hardware (ASIC) centric information, which cannot make > sense unless one has the ASIC specification. > > The Pinnacle ASIC register dump you did was the right one. If you see those > errors incrementing in large number (these are clear on read), you should > consider replacing the LC. > > Not sure what exact Linecard type you have. > > As a workaround, you can try moving the physical port to any other ports > other than what is controlled by port asic 0, as that is what is picking up > these errors. > > > sukumar > (sent from Good mail) > > -----Original Message----- > From: David Freedman [mailto:[EMAIL PROTECTED] > Sent: Monday, June 23, 2008 04:48 AM Pacific Standard Time > To: Sukumar Subburayan (sukumars) > Cc: Rubens Kuhl Jr.; Jeff Fitzwater; [email protected] > Subject: Re: [c-nsp] 12.2(33)SXH > > Sukumar, I opened a TAC case already about this but nobody has come back > to me yet. > > Can you point me to a document which explains how to interpret this > data? is it publically available? > > Also, I do not know how to get this information any other way, > This is all I have: > > From the 6500: > > 6500#sh int g7/1 | in rror|drop|throt > Input queue: 1/2000/53/53 (size/max/drops/flushes); Total output drops: 0 > 0 runts, 352555400 giants, 0 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > 10 output errors, 0 collisions, 1 interface resets > 6500#sh int g7/2 | in rror|drop|throt > Input queue: 0/2000/902/901 (size/max/drops/flushes); Total output > drops: 0 > 0 runts, 1429767336 giants, 1 throttles > 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored > 0 output errors, 0 collisions, 1 interface resets > 6500#remote command switch show plat hard asicreg PINNACLE Slot 7 port 1 > error-counters print-non-zero > PINNACLE 7/1 > 0158: PI_PN_S_CRC_ERR_CNT_REG = 00FF > PINNACLE 7/1 > 016F: PI_CI_S_CBL_DROP_REG = 0001 > > 6500#remote command switch show plat hard asicreg PINNACLE Slot 7 port 2 > error-counters print-non-zero > > > > > From the remote partner (GSR1) with link G7/1: > > GSR1# sh int g1/1/8 | in rror|drop|throt > Output queue 0/40, 0 drops; input queue 0/2000, 0 drops > Received 18 broadcasts, 0 runts, 3958399257 giants, 0 throttles > 0 input errors, 10 CRC, 10 frame, 0 overrun, 0 ignored > 0 output errors, 0 collisions, 0 interface resets > > From the remote partner (GSR2) with link G7/2: > > GSR2#sh int g1/1/7 | in rror|drop|throt > Output queue 0/40, 0 drops; input queue 0/2000, 0 drops > Received 13 broadcasts, 0 runts, 1464946843 giants, 0 throttles > 104 input errors, 0 CRC, 104 frame, 0 overrun, 0 ignored > 0 output errors, 0 collisions, 0 interface resets > > > Regards, > > Dave. > > > Sukumar Subburayan (sukumars) wrote: >> I might have missed the original post from David Freedman on : >> >> "CONST_DIAG-SP-4-ERROR_COUNTER_WARNING" >> >> Actually, printing this syslog is not a bug. In 12.2(33)SXH onwards, we >> added 'LinkErrorMonitoring' feature, where >> Diagnostics proactively checks for various ASIC/port related errors >> periodically, and would print a syslog when these error >> Counters exceed threshold. That is exactly what the customer we are >> seeing in the case below. >> >> In this particular case, the error indicates, that there was 3484 Count >> of Packet with CRC Error when packet was >> Transmitted on the network from a port belonging to port ASIC (Pinnacle) >> 0. >> >> A TAC case is in order, to investigate further if any issues are seen in >> the network related to this. I am sure the customer >> would have seen these errors even in SXF code, but simply diagnostics >> was not monitoring and reporting these errors in that release. >> >> CSCsm84257 fix should be in SXH3, scheduled tentatively for release end >> of next month. >> >> >> sukumar >> >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Rubens Kuhl Jr. >> Sent: Monday, June 23, 2008 6:48 AM >> To: Jeff Fitzwater >> Cc: [email protected] >> Subject: Re: [c-nsp] 12.2(33)SXH >> >> "CONST_DIAG-SP-4-ERROR_COUNTER_WARNING - SXH problems?" >> http://www.gossamer-threads.com/lists/cisco/nsp/89241?do=post_view_threa >> ded >> >> "SXH2a broken with non-MDT SAFI peers" >> http://puck.nether.net/pipermail/cisco-nsp/2008-May/050891.html >> >> Add to those the one from Oliver Gorwits today: >> "CSCsm84257 (enabling NetFlow causes reload) on SXH2 on 6500 platform" >> >> >> Rubens >> >> >> On Sun, Jun 22, 2008 at 8:57 PM, Jeff Fitzwater <[EMAIL PROTECTED]> >> wrote: >>> Rubens, what issues do you mean? I am running H2a on 5 720-cxls. >>> >>> Very interested! >>> >>> >>> >>> Jeff Fitzwater >>> OIT Network Systems >>> Princeton University >>> >>> >>> On Jun 22, 2008, at 6:20 PM, Rubens Kuhl Jr. wrote: >>> >>>> After less than enthusiastic responses to 12.2(33)SXH2a (see the two >>>> messagens in the cisco-nsp archives about it), have anyone got a >>>> timetable to SXH3 or SXH2b ? >>>> >>>> >>>> Rubens >>>> _______________________________________________ >>>> 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/ >> > > - -- David Freedman Group Network Engineering Claranet Limited http://www.clara.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIX5U4tFWeqpgEZrIRAs4zAJoCd+r+vCSQoeESVPjr8fNzPtSg7gCfXYNj sCHiwy1GoupKeGD8kEyiHF4= =90TL -----END PGP SIGNATURE----- _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
