Screen OS

 View Only
last person joined: 8 months ago 

This is a legacy community with limited Juniper monitoring.
  • 1.  High Memory utilization

    Posted 11-30-2008 22:51

    Hi,

     

    I've noticed during high memory we have been asked some logs.

     

    get clock

    get mem

    get mem pool

    get mem ipc

    get mem chunk

    get mem ker

    get mem debug

    get mem used

    get os task

    get net-pak

    get net-pak s

    get net-b

     

     

    What the last three command output means?


    pop3



  • 2.  RE: High Memory utilization

    Posted 12-01-2008 00:10

    You can find a good explanations here:

    http://kb.juniper.net/KB5834

    http://kb.juniper.net/KB9237

     

    Hope this helps,

    Nadia

    Message Edited by Nadia on 12-01-2008 09:11 AM


  • 3.  RE: High Memory utilization

    Posted 12-01-2008 00:19

    Thanks Nadia,

     

    I could able to find first KB you mentioned which i've already gone through before.

     

    search for second KB gave error.

    Article not found or
    * Your access level is not sufficiently high enough.



  • 4.  RE: High Memory utilization

    Posted 12-01-2008 00:21

    It probably requires you to login in order to view it.

    Does the article answer your questions or do you need more information?

     

    Thanks,

    Nadia



  • 5.  RE: High Memory utilization

    Posted 12-01-2008 00:38

    Hi Nadia,

     

    I'm using Juniper Partner login and viewing many article and case in Juniper. 

    My question was regarding output of those 3 commands 🙂 . The article which you mentinoed first i have already went through.

     

    pop3



  • 6.  RE: High Memory utilization
    Best Answer

    Posted 12-01-2008 00:49

    Ah okay sorry my bad 🙂

    This is an extract from the KB article:

    ns5200 -> get net-pak s
         total memory: 18985408, default size: 1792, max size: 16384, fail: 0
         name        memory      total bufsize   free    max        hit       miss
         tiny        0f5fb9e0   409664     256    800    800    5482014    1782660
         small       0f484920  1536064     512   2000   2000    1809058      80911
         median      0ecb4860  8192064     768   8000   8000     227431          0
         big         0e5ac7a0  7372864    1792   3600   3600     220302          0
         large       0e4d7ee0   870464    4096    200    200          0          0
         huge        0e485620   337984    8192     40     40          0          0
         giant       0e444560   266304   16384     16     16          0          0
         in: maxlen: 8192, len: 0, full: 0
         out: maxlen: 8192, len: 0, full: 0
         loopback: maxlen: 256, len: 0, full: 0

       where:

         "total memory:" - total system memory in byte allocated for net-pak pools.
         "default size:" - default net-pak pool to use if a pak length is unknown.
         "max size:" - max net-pak size available.
         "fail:" - number of times when no free net-pak can be allocated for any tasks.
         "name" - names of net-pak pools.
         "memory" - starting memory location of each net-pak pool.
         "total" - net-pak pool size in byte (plus some other system data structure overheads).
         "bufsize" - net-pak size in byte in a given net-pak pool.
         "free" - number of net-paks currently available in a given net-pak pool.
         "max" - total number of net-paks in a given net-pak pool.
         "hit" - number of sucessful net-pak allocation in a given net-pak pool.
         "miss" - number of failed net-pak allocation in a given net-pak pool.
         "in:" - net-pak incoming queue.
         "out:" - net-pak outgoing queue.
         "loopback:" - net-pak loopback queue.
         "maxlen:" - max queue size.
         "len:" - current queue length.
         "full:" - number of in/out/loopback queue being full.

     

    (KB3589)

     

    Thanks,

    Nadia