[c-nsp] CT3IP counters followup ?

[Rodney Dunn]

While waiting on a CT3IP to show up I did a
bug search and found:

CSCeb81930
Externally found moderate defect: Resolved (R)
c7500 displaying incorrect input/output rate in 12.3(1a)

Symptoms:
C7513 running 12.3(1a) displays incorrect input/output rate on a PA-CT3IP.
Workaround:
No workaround is avaiable at this time.


Can someone confirm they are still seeing this problem on
an image with this fix?

Rodney


On Mon, Nov 15, 2004 at 08:30:08AM -0500, Rodney Dunn wrote:
> I'm willing to take some time and try to set it up in the
> lab if someone will give me the information I ask for.
> I believe you there is a problem.
> 
> What I need is more information to keep a recreate 
> attempt time down to something I can manage on my
> free time.  Trying every possibly permutation of 
> switching paths on this box in the lab without
> knowing full feature combinations isn't something
> feasible for me.
> 
> The main thing I want is:
> 
> clear counters
> 
> Every 30 seconds for 2 minutes for an interface having
> a problem:
> 
> sh int <blah>
> sh int <blah> stat
> 
> I want to know what switching path packets in/out this
> interface are taking.
> 
> I'm working to get a card.  All the ones in my lab are
> MCT3's.
> 
> Rodney
> 
> 
> On Sun, Nov 14, 2004 at 03:20:10PM -0800, Chris Cappuccio wrote:
> > Using 12.2(18)S4 or 12.2(25)S1 on rsp4, the ct3ip's counters under 'show
> > interface' are totally inaccurate (Bandwidth utilization in the tens
> > of megabits for channelized T1 interfaces!) but it was reported here that the
> > snmp counters are still accurate.  This happens for incoming and outgoing
> > traffic on the ct3ip channelized interfaces, and does not affect the
> > ethernet or other pieces in other vip2-50 blades in the same 7507 chassis.
> > Very easy to reproduce.
> > 
> > Rodney Dunn [rodunn at cisco.com] wrote:
> > > Can you refresh my /*failing*/ memory on which counter
> > > wasn't working?
> > > 
> > > Can you post a:
> > > sh ver
> > > sh diag
> > > sh int
> > > sh run int <blah> on the ingress and egress interfaces in the path
> > > sh int <blah> stat 30 seconds after you clear the counters
> > > 
> > > I'll see if I happen to have one to put in the lab and give
> > > it a quick try in my setup if I can find time today.
> > > 
> > > Rodney
> > > 
> > > 
> > > On Fri, Nov 12, 2004 at 12:41:54AM -0800, joe mcguckin wrote:
> > > > We're seeing this problem also. Has anyone tried a newer IOS to see if it
> > > > fixes the problem?
> > > > 
> > > > Thanks,
> > > > 
> > > > Joe
> > > > 
> > > > -- 
> > > > 
> > > > Joe McGuckin
> > > > 
> > > > ViaNet Communications
> > > > 994 San Antonio Road
> > > > Palo Alto, CA  94303
> > > > 
> > > > Phone: 650-213-1302
> > > > Cell:  650-207-0372
> > > > Fax:   650-969-2124
> > > > 
> > > > 
> > > > _______________________________________________
> > > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > 
> > -- 
> > The past cannot be changed.  The future cannot be guaranteed.