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

[Cisco Geek Rotation]

At 03:50 PM 3/14/2003 -0800, Steven W. Raymond wrote:
>Well, I am very sorry to report that I seem to now be seeing the SNMP
>counter bug on 12.0(21)S5 on 7500s after at least 4 weeks of uptime
>(including serial DS3s, HSSIs, and T1 interfaces).  Does the amount of
>time have to do with something about the capacity of the counters?  Is
>it just my imagination or was there a 32-bit v. 64-bit counter
>conversation which discussed this problem?
>Am particularly frustrated by this problem, thought that 12.0(21)S5
>would work for us but the counter problem is a show-stopper.


Hey what's the deal with the S train anyway?  Why run that instead of the T 
train?

Chris



>Sean Crocker wrote:
> >
> > >Anyone got a bug id for the SNMP counter failure?  Please help me
> > >understand- it seems to affect 12.0(21)S5?
> > >Thanks
> >
> > Sounds like CSCin15495, but that was supposedly fixed in (21)S5.
> >
> > Sean
> >
> > >
> > >
> > >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:
> > >>
> > >> For Packet counts :
> > >> 
> iso.org.dod.internet.private.enterprises.cisco.local.linterfaces.lifTable.lifEntry.locIfFastOutPkts
> > >> 
> iso.org.dod.internet.private.enterprises.cisco.local.linterfaces.lifTable.lifEntry.locIfFastInPkts
> > >>
> > >> For Octets counts :
> > >> 
> iso.org.dod.internet.private.enterprises.cisco.local.linterfaces.lifTable.lifEntry.locIfFastOutOctets
> > >> 
> iso.org.dod.internet.private.enterprises.cisco.local.linterfaces.lifTable.lifEntry.locIfFastInOctets
> > >>
> > >> -Hank
> > >>
> > >> >I have been running 12.0(21)S5 on 7500 (two different
> > >> >7507's) and found what looks like a counter bug on POS
> > >> >interfaces. It doesn't appear to affect other interfaces.
> > >> >
> > >> >SNMP polling of the POS (OC-3) interface consistently shows
> > >> >nothing outbound. Inbound measures normal.
> > >> >
> > >> >On the RP, a "show interface" shows both in-bound and
> > >> >out-bound at normal levels.
> > >> >
> > >> >Running "show interface" on the line-card itself (via the
> > >> >undocumented command "if-con X" (http://boerland.com/dotu/),
> > >> >it showed normal in-bound traffic, but nothing out-bound. I
> > >> >guess SNMP polls directly off the line-card, not the RP.
> > >> >
> > >> >This seemed to happen after the routers had been up about a
> > >> >week.
> > >> >
> > >> >Anyone else seen this, or seen something different?
> > >> >
> > >> >12.0(21)S5 also has a distributed multicast bug (on 7500 POS
> > >> >interfaces) that surfaced in 12.0(21)S3 (CSCdx36692). This
> > >> >was supposed to be fixed in 12.0(21)S5, but my experience is
> > >> >that it is exactly as broken as it was in 12.0(21)S3.
> > >> >
> > >> >Pete.
> > >_______________________________________________
> > >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/
> > >
> > _______________________________________________
> > 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/
>_______________________________________________
>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/