Cisco Buffers

Discussion in 'Cisco' started by skeeney, Jul 19, 2007.

  1. skeeney

    skeeney

    Joined:
    Jul 11, 2007
    Messages:
    5
    Likes Received:
    0
    Hiya

    We have 34meg link at work, keeps taking hits after extensive testing I think i may have found the fault but desperately need your help understanding a couple of things.

    Seems that the hit, usually 20 seconds.. is exactly the same time of buffer failure. Can someone please explain the results of the show buffer failures as there is no information on this on the web. Is the caller the dram memory address? If so this is the same in all the below examples, could this mean a fault on the DRAM, or would the buffer refer to the card?

    BGP state = Established, up for 3d04h

    router#sh buffers failures
    Caller Pool Size When
    0x60645934 Small 60 3d04h
    0x60645934 Middle 60 3d04h
    0x60645934 Small 60 3d04h
    0x60645934 Middle 60 3d04h
    0x60645934 Small 60 3d04h
    0x60645934 Middle 60 3d04h
    0x60645934 Small 60 3d04h
    0x60645934 Middle 60 3d04h
    0x60645934 Small 60 3d04h
    0x60645934 Middle 60 3d04h

    Below is the full output from a sh buffer command


    router#sh buffer
    Buffer elements:
    499 in free list (500 max allowed)
    216067975 hits, 0 misses, 0 created

    Public buffer pools:
    Small buffers, 104 bytes (total 50, permanent 50, peak 71 @ 3d04h):
    46 in free list (20 min, 150 max allowed)
    17564421 hits, 52 misses, 24 trims, 24 created
    31 failures (0 no memory)
    Middle buffers, 600 bytes (total 31, permanent 25, peak 52 @ 3w3d):
    30 in free list (10 min, 150 max allowed)
    437623 hits, 70 misses, 123 trims, 129 created
    20 failures (0 no memory)
    Big buffers, 1536 bytes (total 50, permanent 50):
    50 in free list (5 min, 150 max allowed)
    418746 hits, 0 misses, 0 trims, 0 created
    0 failures (0 no memory)
    VeryBig buffers, 4520 bytes (total 10, permanent 10, peak 18 @ 3w0d):
    10 in free list (0 min, 100 max allowed)
    404348 hits, 20 misses, 40 trims, 40 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 2, permanent 0, peak 2 @ 00:43:08):
    2 in free list (0 min, 4 max allowed)
    3 hits, 1 misses, 0 trims, 2 created
    0 failures (0 no memory)

    Interface buffer pools:
    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 561, permanent 256, peak 561 @ 1w3d):
    305 in free list (256 min, 1024 max allowed)
    445 hits, 123 misses, 0 trims, 305 created
    0 failures (0 no memory)
    256 max cache size, 256 in cache
    51257346 hits in cache, 274 misses in cache

    Particle Clones:
    1024 clones, 0 hits, 0 misses

    Public particle pools:
    F/S buffers, 128 bytes (total 512, permanent 512):
    0 in free list (0 min, 512 max allowed)
    512 hits, 0 misses
    512 max cache size, 512 in cache
    0 hits in cache, 0 misses in cache
    Normal buffers, 512 bytes (total 2048, permanent 2048):
    2048 in free list (1024 min, 4096 max allowed)
    0 hits, 0 misses, 0 trims, 0 created
    0 failures (0 no memory)

    Private particle pools:
    Serial1/0 buffers, 512 bytes (total 256, permanent 256):
    0 in free list (0 min, 256 max allowed)
    256 hits, 0 fallbacks
    256 max cache size, 132 in cache
    475251162 hits in cache, 0 misses in cache
    10 buffer threshold, 0 threshold transitions
    FastEthernet0/1 buffers, 768 bytes (total 529, permanent 400):
    129 in free list (128 min, 1200 max allowed)
    357 hits, 43 misses, 34943 trims, 35072 created
    0 failures (0 no memory)
    400 max cache size, 272 in cache
    51059735 hits in cache, 0 misses in cache
    14 buffer threshold, 0 threshold transitions
    FastEthernet0/0 buffers, 768 bytes (total 657, permanent 400):
    129 in free list (128 min, 1200 max allowed)
    9059 hits, 7870 misses, 40493 trims, 40750 created
    12 failures (0 no memory)
    400 max cache size, 397 in cache
    4276017737 hits in cache, 8714 misses in cache
    14 buffer threshold, 196 threshold transitions

    Kit is as below:
    Type:(C7200-JS-M),Version:12.2(13b),Image:disk0:c7200-js-mz.122-13b.bin,Sysflash:0 Kb,Bootflash:0 Kb,Memory:114688 Kb
    Slot 0,Dual FastEthernet (RJ-45) I/O Card Port adapter 2 ports
    Slot 1,E3 PA Port adapter 1 port
     
    skeeney, Jul 19, 2007
    #1
    1. Advertisements

  2. skeeney

    skeeney

    Joined:
    Jul 11, 2007
    Messages:
    5
    Likes Received:
    0
    Hiya, in continuation.. correct me if i'm wrong, but have just run the address through a show region address and got the below. Does this mean that this failure was located in itext? itext is located on the dram? Is this a faulty DRAM?

    ab45-r10-002#sh region address 0x60645934
    Address 0x60645934 is located physically in :

    Name : text
    Class : IText
    Media : R/O
    Start : 0x60008940
    End : 0x6168A10B
    Size : 0x016817CC
     
    skeeney, Jul 19, 2007
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.