[nsp] Strange IOS behaviour

[Burns, Keith]

Hmmm, (yet) another Cisco developer who doesn't know how to display a signed
integer perhaps??? i.e. DON'T display as unsigned.

Keith Burns
Principal Network Architect
ICG Telecommunications
IP Ph: 303-414-5385
Cell:   303-912-3777 

"The dogs may bark, but the caravan rolls on...."


> -----Original Message-----
> From: Wim De Houwer [mailto:wdehouwer at be.tiscali.com]
> Sent: Thursday, January 08, 2004 9:51 AM
> To: cisco-nsp at puck.nether.net
> Subject: [nsp] Strange IOS behaviour
> 
> 
> Hello All,
> 
> I seem to have a strange 'thing' going on on one of my 
> 7500's, there are error counters that are not increasing but 
> Decreasing!!
> 
> This is the reduced info from the 'show ver':
> --------------------------------------------------------------
> --------------------------------------------------------------
> -----------------
> IOS (tm) RSP Software (RSP-PV-M), Version 12.0(25)S1, EARLY 
> DEPLOYMENT RELEASE SOFTWARE (fc1)
> 
> cisco RSP4 (R5000) processor with 262144K/2072K bytes of memory.
> R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache
> 123K bytes of non-volatile configuration memory.
> 20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
> 8192K bytes of Flash internal SIMM (Sector size 256K).
> --------------------------------------------------------------
> --------------------------------------------------------------
> -----------------
> controller E1 2/1/0
>  framing no-crc4
>  channel-group 0 timeslots 1-24
>  channel-group 1 timeslots 25-28
>  channel-group 2 timeslots 29-31
> !
> interface Serial2/1/0:0
>  ip unnumbered Loopback0
>  no ip directed-broadcast
>  encapsulation ppp
> !
> interface Serial2/1/0:1
>  ip unnumbered Loopback0
>  no ip directed-broadcast
>  encapsulation ppp
> !
> interface Serial2/1/0:2
>  ip unnumbered Loopback0
>  no ip directed-broadcast
>  encapsulation ppp
> --------------------------------------------------------------
> --------------------------------------------------------------
> -----------------
> bfr#sh int Serial2/1/0:0 | i protocol|error
> Serial2/1/0:0 is up, line protocol is up
>      4294966630 input errors, 4294966630 CRC, 0 frame, 0 
> overrun, 0 ignored, 0 abort
>      0 output errors, 0 collisions, 0 interface resets
> bfr#sh int Serial2/1/0:1 | i protocol|error
> Serial2/1/0:1 is up, line protocol is up
>      4294966636 input errors, 4294966636 CRC, 0 frame, 0 
> overrun, 0 ignored, 0 abort
>      0 output errors, 0 collisions, 0 interface resets
> bfr#sh int Serial2/1/0:2 | i protocol|error
> Serial2/1/0:2 is up, line protocol is up
>      4294966639 input errors, 4294966639 CRC, 0 frame, 0 
> overrun, 0 ignored, 0 abort
>      0 output errors, 0 collisions, 0 interface resets
> 
> bfr#sh int Serial2/1/0:0 | i protocol|error
> Serial2/1/0:0 is up, line protocol is up
>      4294966624 input errors, 4294966624 CRC, 0 frame, 0 
> overrun, 0 ignored, 0 abort
>      0 output errors, 0 collisions, 0 interface resets
> bfr#sh int Serial2/1/0:1 | i protocol|error
> Serial2/1/0:1 is up, line protocol is up
>      4294966630 input errors, 4294966630 CRC, 0 frame, 0 
> overrun, 0 ignored, 0 abort
>      0 output errors, 0 collisions, 0 interface resets
> bfr#sh int Serial2/1/0:2 | i protocol|error
> Serial2/1/0:2 is up, line protocol is up
>      4294966633 input errors, 4294966633 CRC, 0 frame, 0 
> overrun, 0 ignored, 0 abort
>      0 output errors, 0 collisions, 0 interface resets
> 
> So if anyone has any good ideas on how to resolve this as 
> it's driving my monitoring software nuts...
> 
> Thanks,
> 
> Wim
> 
> _______________________________________________
> 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/
>