Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Buffer failure and

Buffer elements:
     687 in free list (1119 max allowed)
     4135521862 hits, 0 misses, 619 created

Public buffer pools:
Small buffers, 104 bytes (total 88, permanent 50, peak 188 @ 5w0d):
     80 in free list (20 min, 150 max allowed)
     883963156 hits, 9594 misses, 9592 trims, 9630 created
     966 failures (0 no memory)
Middle buffers, 600 bytes (total 59, permanent 25, peak 132 @ 5w4d):
     57 in free list (10 min, 150 max allowed)
     526479077 hits, 17815 misses, 4055 trims, 4089 created
     4542 failures (0 no memory)
Big buffers, 1536 bytes (total 70, permanent 50, peak 171 @ 5w0d):
     68 in free list (5 min, 150 max allowed)
     904789854 hits, 4662 misses, 5172 trims, 5192 created
     1589 failures (0 no memory)
VeryBig buffers, 4520 bytes (total 10, permanent 10, peak 14 @ 5w4d):
     10 in free list (0 min, 100 max allowed)
     406367 hits, 468 misses, 43 trims, 43 created
     466 failures (0 no memory)
Large buffers, 5024 bytes (total 1, permanent 0, peak 3 @ 5d21h):
     1 in free list (0 min, 10 max allowed)
     44 hits, 422 misses, 370 trims, 371 created
     422 failures (0 no memory)
Huge buffers, 18024 bytes (total 1, permanent 0, peak 3 @ 5d21h):
     1 in free list (0 min, 4 max allowed)
     72031 hits, 392 misses, 373 trims, 374 created
     391 failures (0 no memory)

Interface buffer pools:
Syslog ED Pool buffers, 600 bytes (total 132, permanent 132):
     100 in free list (132 min, 132 max allowed)
     415 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 840, permanent 840):
     840 in free list (420 min, 1680 max allowed)
     0 hits, 0 fallbacks, 0 trims, 0 created
     0 failures (0 no memory)

SRT-RTR-MPLS-P#show int tu6

Tunnel6 is up, line protocol is up

  Hardware is Tunnel

  Description: *** Fiber Link Tunnel to CNG 3Floor RTR ***

  Internet address is XXXXXX

  MTU 17916 bytes, BW 100000 Kbit/sec, DLY 50000 usec,

     reliability 255/255, txload 3/255, rxload 2/255

  Encapsulation TUNNEL, loopback not set

  Keepalive set (10 sec), retries 3

  Tunnel source XXXXXX, destination XXXXXX

  Tunnel protocol/transport GRE/IP

    Key disabled, sequencing disabled

    Checksumming of packets disabled

  Tunnel TTL 255

  Fast tunneling enabled

  Tunnel transport MTU 1476 bytes

  Tunnel transmit bandwidth 8000 (kbps)

  Tunnel receive bandwidth 8000 (kbps)

  Last input 00:00:01, output 00:00:00, output hang never

  Last clearing of "show interface" counters 15:37:30

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1403

  Queueing strategy: fifo

  Output queue: 0/0 (size/max)

  30 second input rate 835000 bits/sec, 320 packets/sec

  30 second output rate 1493000 bits/sec, 327 packets/sec

     11407405 packets input, 3238501135 bytes, 0 no buffer

     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

     17878300 packets output, 3930711759 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 unknown protocol drops

     0 output buffer failures, 0 output buffers swapped out

SRT-RTR-MPLS-P#

1 ACCEPTED SOLUTION

Accepted Solutions
Super Bronze

Re: Buffer failure and

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

Why are you using a GRE tunnel if you have a fiber link?

If you must continue to use the GRE tunnel, does you equipment allow for jumbo Ethernet across your physical, so that you can run standard Ethernet across the tunnel without the need to fragment?

Are you using mss-adjust 1436, ip mtu 1476 and PMTUD on the tunnel interface?  (Likely won't help with your video traffic, but may help with any concurrent TCP traffic.)

Have you tried increasing both your ingress and/or egress queue depths?

4 REPLIES
Community Member

Buffer failure and

Hi ,

i am facing intermitend drops in my tunnel interface , i have cleared the counters and within 1 hour its increased to 250 ...

the issue i am facing thet there is sudden video packet drops observed in VC traffic . I have fiber link betweel twe location and have a tunnel configured. please suggest , as i am not able to see any input output drops in Physical interface.

Community Member

Buffer failure and

Output of Physical interface where m observing  flushes drop in physical interface

sh interfaces Gi0/0

GigabitEthernet0/0 is up, line protocol is up

  Hardware is BCM1125 Internal MAC, address is 001b.2ae2.7fa0 (bia 001b.2ae2.7fa0)

  Description: LAN INTERFACE 101.2

  Internet address is XXXXX

  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,

     reliability 255/255, txload 1/255, rxload 3/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 1000Mb/s, media type is RJ45

  output flow-control is XON, input flow-control is XON

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:00, output 00:00:00, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/15629 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  30 second input rate 13402000 bits/sec, 2399 packets/sec

  30 second output rate 7088000 bits/sec, 2133 packets/sec

     1405006976 packets input, 4193770059 bytes, 0 no buffer

     Received 2352683 broadcasts, 0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 6646593 multicast, 0 pause input

     0 input packets with dribble condition detected

     161988396 packets output, 2982389828 bytes, 0 underruns

     3 output errors, 0 collisions, 3 interface resets

     1 unknown protocol drops

     0 babbles, 0 late collision, 0 deferred

     3 lost carrier, 0 no carrier, 0 pause output

     0 output buffer failures, 0 output buffers swapped out

Super Bronze

Re: Buffer failure and

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

Why are you using a GRE tunnel if you have a fiber link?

If you must continue to use the GRE tunnel, does you equipment allow for jumbo Ethernet across your physical, so that you can run standard Ethernet across the tunnel without the need to fragment?

Are you using mss-adjust 1436, ip mtu 1476 and PMTUD on the tunnel interface?  (Likely won't help with your video traffic, but may help with any concurrent TCP traffic.)

Have you tried increasing both your ingress and/or egress queue depths?

Community Member

Buffer failure and

Now my problem seems to be resolved , i have changed the MTU size to 1500 which eliminated the OQD , and the L3  interface where OQD drops wehe observed that port was a trunk port and restricted only the required VLAN's which limited the traffic load on interface.

269
Views
0
Helpful
4
Replies
CreatePlease to create content