Thank you for your help, where to get the information below?
Throttle - Number of times the interface has flushed the buffers it
Able to service wasn't fast enough or gets overwhelmed. Very
distruptive in nature.
Ignored - Number of received packets ignored by That Get the interface
because it ran low on internal buffers.
Kaio Vilar
2011/6/6 Christian Hunter <stasis416_at_gmail.com>
> Well your counters have never been cleared on your interface, so it's
> going by whatever your system uptime is in show version. I.e. Last
> clearing of "show interface" counters never
> So hard to know exactly how often your seeing this problem. There is
> peak counters on small/middle buffers, 6 days ago for small and 1 week
> for middle. This is probably why you see the misses/trims and could
> relate to your ignored/throttles.
>
> You can tweak small and middle, you need to clear your counters to get
> a better feel if that's your issue.
>
> Consider:
>
> buffers small permanent 132
> buffers small min-free 172
> buffers small max-free 303
> buffers middle permanent 40
> buffers middle min-free 51
> buffers middle max-free 150
>
>
> Please do your homework before implementation. I do not know your
> environment, these are only suggestions.
>
> Throttle - Number of times the interface has flushed buffers as it
> wasn't able to service fast enough or gets overwhelmed. Very
> distruptive in nature.
>
> Ignored - Number of received packets that get ignored by the interface
> because it ran low on internal buffers.
>
> Hopefully this will put your on the correct path to resolution.
>
> -Christian
>
> On Mon, Jun 6, 2011 at 3:32 PM, Kaio Vilar <kaiovilar_at_gmail.com> wrote:
> > Internet_#sh buffers
> > Buffer elements:
> >      1118 in free list (1119 max allowed)
> >      1538583 hits, 0 misses, 619 created
> >
> > Public buffer pools:
> > Small buffers, 104 bytes (total 100, permanent 100, peak 109 @ 6d02h):
> >      99 in free list (30 min, 150 max allowed)
> >      1093593 hits, 153 misses, 158 trims, 158 created
> >      0 failures (0 no memory)
> > Middle buffers, 600 bytes (total 30, permanent 30, peak 45 @ 1w0d):
> >      28 in free list (15 min, 150 max allowed)
> >      35161 hits, 7 misses, 21 trims, 21 created
> >      0 failures (0 no memory)
> > Big buffers, 1536 bytes (total 50, permanent 50):
> >      49 in free list (5 min, 150 max allowed)
> >      681568 hits, 0 misses, 0 trims, 0 created
> >      0 failures (0 no memory)
> > VeryBig buffers, 4520 bytes (total 10, permanent 10):
> >      10 in free list (0 min, 100 max allowed)
> >      0 hits, 0 misses, 0 trims, 0 created
> >      0 failures (0 no memory)
> > Large buffers, 5024 bytes (total 0, permanent 0):
> >      0 in free list (0 min, 10 max allowed)
> >      0 hits, 0 misses, 0 trims, 0 created
> >      0 failures (0 no memory)
> > Huge buffers, 18024 bytes (total 0, permanent 0):
> >      0 in free list (0 min, 4 max allowed)
> >      0 hits, 0 misses, 0 trims, 0 created
> >      0 failures (0 no memory)
> >
> > Interface buffer pools:
> > Syslog ED Pool buffers, 600 bytes (total 150, permanent 150):
> >      118 in free list (150 min, 150 max allowed)
> >      279 hits, 0 misses
> > CD2430 I/O buffers, 1536 bytes (total 0, permanent 0):
> >      0 in free list (0 min, 0 max allowed)
> >      0 hits, 0 fallbacks
> > IPC buffers, 4096 bytes (total 2, permanent 2):
> >      2 in free list (1 min, 8 max allowed)
> >      0 hits, 0 fallbacks, 0 trims, 0 created
> >      0 failures (0 no memory)
> >
> > Header pools:
> > Header buffers, 0 bytes (total 768, permanent 768):
> >      256 in free list (128 min, 1024 max allowed)
> >      512 hits, 0 misses, 0 trims, 0 created
> >      0 failures (0 no memory)
> >      512 max cache size, 512 in cache
> >      19860 hits in cache, 0 misses in cache
> >
> > Particle Clones:
> >  --More--              1024 clones, 0 hits, 0 misses
> >  --More--
> >  --More--         Public particle pools:
> >  --More--         F/S buffers, 256 bytes (total 768, permanent 768):
> >  --More--              256 in free list (128 min, 1024 max allowed)
> >  --More--              512 hits, 0 misses, 0 trims, 0 created
> >  --More--              0 failures (0 no memory)
> >  --More--              512 max cache size, 512 in cache
> >  --More--              0 hits in cache, 0 misses in cache
> >  --More--         Normal buffers, 1548 bytes (total 768, permanent 768):
> >  --More--              768 in free list (128 min, 1024 max allowed)
> >  --More--              0 hits, 0 misses, 0 trims, 0 created
> >  --More--              0 failures (0 no memory)
> >  --More--         CRYPTO_HW buffers, 1548 bytes (total 1536, permanent
> > 1536):
> >  --More--              0 in free list (0 min, 1536 max allowed)
> >  --More--              1536 hits, 0 misses
> >  --More--              1536 max cache size, 1024 in cache
> >  --More--              512 hits in cache, 0 misses in cache
> >  --More--
> >  --More--         Private particle pools:
> >  --More--         IDS SM buffers, 240 bytes (total 128, permanent 128):
> >  --More--              0 in free list (0 min, 128 max allowed)
> >  --More--              128 hits, 0 fallbacks
> >  --More--              128 max cache size, 128 in cache
> >  --More--              0 hits in cache, 0 misses in cache
> >  --More--         GigabitEthernet0/0 buffers, 1536 bytes (total 384,
> > permanent 384):
> >  --More--              0 in free list (0 min, 384 max allowed)
> >  --More--              384 hits, 0 fallbacks
> >  --More--              384 max cache size, 256 in cache
> >  --More--              73779053 hits in cache, 0 misses in cache
> >  --More--         GigabitEthernet0/1 buffers, 1536 bytes (total 384,
> > permanent 384):
> >  --More--              0 in free list (0 min, 384 max allowed)
> >  --More--              384 hits, 0 fallbacks
> >  --More--              384 max cache size, 256 in cache
> >  --More--              40861168 hits in cache, 0 misses in cache
> >  --More--         Serial0/0/0 buffers, 1536 bytes (total 64, permanent
> 64):
> >  --More--              0 in free list (0 min, 64 max allowed)
> >  --More--              64 hits, 0 fallbacks
> >  --More--              64 max cache size, 32 in cache
> >  --More--              44508807 hits in cache, 0 misses in cache
> >  --More--         Serial0/0/1 buffers, 1536 bytes (total 64, permanent
> 64):
> >  --More--              0 in free list (0 min, 64 max allowed)
> >  --More--              64 hits, 0 fallbacks
> >  --More--              64 max cache size, 32 in cache
> >  --More--              32 hits in cache, 0 misses in cache
> >
> > 2011/6/6 Kaio Vilar <kaiovilar_at_gmail.com>
> >>
> >> I'm using FIFO, Buffers'll check.
> >>
> >> 2011/6/6 Kaio Vilar <kaiovilar_at_gmail.com>
> >>>
> >>> I checked with the ISP and it is also configured with speed / duplex
> >>> manually. This problem is intermittent sometimes happens in the morning
> >>> other afternoon. So I believe it might be something related to the
> buffer,
> >>> the same amount of errors appears in PE. The connection between them is
> >>> fiber.
> >>>
> >>> 2011/6/6 Haroon <itguy.pro_at_gmail.com>
> >>>>
> >>>> what happens if you let ISP router set the speed and duplex? auto
> >>>> negotiate?
> >>>>
> >>>> On Mon, Jun 6, 2011 at 2:56 PM, Kaio Vilar <kaiovilar_at_gmail.com>
> wrote:
> >>>>>
> >>>>> I set the speed / duplex at one week but the problem continues.
> >>>>>
> >>>>> GigabitEthernet0/1 is up, line protocol is up
> >>>>>   Hardware is MV96340 Ethernet,
> >>>>>   Internet address is
> >>>>>   MTU 1500 bytes, BW 10000 Kbit/sec, DLY 100 usec,
> >>>>>      reliability 255/255, txload 7/255, rxload 66/255
> >>>>>   Encapsulation ARPA, loopback not set
> >>>>>   Keepalive set (10 sec)
> >>>>>   Full-duplex, 100Mb/s, media type is T
> >>>>>   output flow-control is XON, input flow-control is XON
> >>>>>   ARP type: ARPA, ARP Timeout 04:00:00
> >>>>>   Last input 00:02:29, output 00:00:00, output hang never
> >>>>>   Last clearing of "show interface" counters never
> >>>>>   Input queue: 0/75/29/0 (size/max/drops/flushes); Total output
> drops:
> >>>>> 0
> >>>>>   Queueing strategy: fifo
> >>>>>   Output queue: 0/40 (size/max)
> >>>>>   30 second input rate 2612000 bits/sec, 340 packets/sec
> >>>>>   30 second output rate 303000 bits/sec, 261 packets/sec
> >>>>>      40998728 packets input, 1239892515 bytes, 0 no buffer
> >>>>>      Received 0 broadcasts, 0 runts, 0 giants, 27 throttles
> >>>>>      563 input errors, 0 CRC, 0 frame, 0 overrun, 563 ignored
> >>>>>      0 watchdog, 0 multicast, 20950 pause input
> >>>>>      0 input packets with dribble condition detected
> >>>>>      32475632 packets output, 3246818112 bytes, 0 underruns
> >>>>>      0 output errors, 0 collisions, 2 interface resets
> >>>>>      0 unknown protocol drops
> >>>>>      0 babbles, 0 late collision, 0 deferred
> >>>>>      0 lost carrier, 0 no carrier, 0 pause output
> >>>>>      0 output buffer failures, 0 output buffers swapped out
> >>>>> RInternet_A#exit
> >>>>>
> >>>>> 2011/6/6 Jeferson Guardia <jefersonf_at_gmail.com>
> >>>>>>
> >>>>>> As I said, only cross connecting inside DC scenarios :-)
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 06/06/2011, at 15:37, Haroon <itguy.pro_at_gmail.com> wrote:
> >>>>>>
> >>>>>> Jeferson,
> >>>>>> Why wouldn't you peer with ISP using ethernet? We've doine that in
> our
> >>>>>> data center and haven't had any issues.... please let me know if
> I've missed
> >>>>>> something?
> >>>>>> Regards,
> >>>>>> Haroon
> >>>>>> On Mon, Jun 6, 2011 at 2:25 PM, Jeferson Guardia <
> jefersonf_at_gmail.com>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Sh int XXX counters err
> >>>>>>>
> >>>>>>> Dont let it auto negotiate, make sure You manually set speed with
> the
> >>>>>>> provider.
> >>>>>>>
> >>>>>>> Make sure that broadcast you are using is private , for you and the
> >>>>>>> provider. In case you are sharing that segment with others,
> collisions might
> >>>>>>> happen thus you'll likely end up retransmitting it but not because
> of a l1
> >>>>>>> issue but the way the segment is saturated.. Btw, I wouldn't peer
> with an
> >>>>>>> ISP using Ethernet, only on some DC scenarios.
> >>>>>>>
> >>>>>>> Best luck
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On 06/06/2011, at 15:17, Christian Hunter <stasis416_at_gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>> > Post a sh int fa0/0
> >>>>>>> >
> >>>>>>> > Different errors mean different things.
> >>>>>>> >
> >>>>>>> > On Mon, Jun 6, 2011 at 2:13 PM, Kaio Vilar <kaiovilar_at_gmail.com>
> >>>>>>> > wrote:
> >>>>>>> >> Hi masters,
> >>>>>>> >>
> >>>>>>> >> I'm having a little problem, I have a link of 10Mbps in a 2800
> >>>>>>> >> router, the
> >>>>>>> >> interface f0 / 0 is generating many "Input Errors" but no CRC.
> My
> >>>>>>> >> ISP has
> >>>>>>> >> checked the circuit and found no problem. I'm thinking maybe the
> >>>>>>> >> interface
> >>>>>>> >> buffer problem, what do you think? have any command that I can
> >>>>>>> >> verify this?
> >>>>>>> >>
> >>>>>>> >> Regards,
> >>>>>>> >> Kaio Vilar
> >>>>>>> >>
> >>>>>>> >>
> >>>>>>> >> Blogs and organic groups at http://www.ccie.net
> >>>>>>> >>
> >>>>>>> >>
> >>>>>>> >>
> _______________________________________________________________________
> >>>>>>> >> Subscription information may be found at:
> >>>>>>> >> http://www.groupstudy.com/list/CCIELab.html
> >>>>>>> >
> >>>>>>> >
> >>>>>>> > Blogs and organic groups at http://www.ccie.net
> >>>>>>> >
> >>>>>>> >
> >>>>>>> >
> _______________________________________________________________________
> >>>>>>> > Subscription information may be found at:
> >>>>>>> > http://www.groupstudy.com/list/CCIELab.html
> >>>>>>>
> >>>>>>>
> >>>>>>> Blogs and organic groups at http://www.ccie.net
> >>>>>>>
> >>>>>>>
> >>>>>>>
> _______________________________________________________________________
> >>>>>>> Subscription information may be found at:
> >>>>>>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Mon Jun 06 2011 - 17:12:45 ART
This archive was generated by hypermail 2.2.0 : Fri Jul 01 2011 - 06:24:27 ART