[nsp] 12.0(22)S2 / 12.0(23)S1

[Hank Nussbacher]

At 09:11 AM 18-03-03 -0800, Steven W. Raymond wrote:
>Hello,
>What makes you say fixed in 12.0(23)S1?  Personal experience?  Looking
>at the bug ID CSCin15495 does not specifically say anything about
>12.0(23)S1.

My Cisco Gold Partner informed me that the TAC case he opened stated that 
this release fixed the problem.  No other confirmation.   -Hank

>We are currently evaluating 12.0(23)S2.  Anyone know if the snmp-counter
>bug is fixed in 12.0(23)S2?  For that matter, can anyone confirm if the
>counter bug seems fixed in _any_ version?  Can't believe the bug id
>report CSCin15495- it claims fixed in 12.0(21)S5 which is simply not
>true
>Thanks!
>
>
>Hank Nussbacher wrote:
> >
> > At 03:36 PM 06-12-02 -0800, you wrote:
> >
> > CSCin15495 - fixed in 12.0(23)S1
> >
> > -Hank
> >
> > >Anyone got a bug id for the SNMP counter failure?  Please help me
> > >understand- it seems to affect 12.0(21)S5?
> > >Thanks
> > >
> > >
> > >Hank Nussbacher wrote:
> > > >
> > > > At 10:11 PM 04-12-02 -0700, Pete Kruckenberg wrote:
> > > >
> > > > Yup.  Running 12.0(21)S4, after about 2 weeks the SNMP data for POS 
> drops
> > > > to zero first, then about a week later, 2 FEs drop to zero as well.  I
> > > > suspect it has to do with cumulative traffic.  'sho in' shows the 
> numbers
> > > > working fine, just snmp mib data is FUBARed.  We have a TAC case 
> open on
> > > > this and as a workaround they recommend we use the following MIBs that
> > > do work:
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>http://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/