[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3808.0. "BRIDGE AM alarm rule yields -memory allocation failure-" by CUJO::HILL (Dan Hill-Net.Mgt.-Customer Resident) Mon Sep 28 1992 05:34

    I have been using the following alarm rule expression to determin
    bridge reachability on the network:
    
      (BRIDGE * DEVICE STATE <> OPERATING, AT EVERY 00:05:00)
    
    During the polling of one of the bridges, I received the following
    notification message:
    
    	The requested operation cannot be
    	completed<EOS>%MCC-E-MEM_ALLOC_FAILE, 
        memory allocation failure
    
    The severity was listed as being INDETERMINATE.  The next alarm poll
    worked just fine, and the node was cleared.
    
    Any ideas??
    
    -Dan
T.RTitleUserPersonal
Name
DateLines
3808.1An error return to Alarms from the Bridge AMMOLAR::ROBERTSKeith Roberts - Network Management ApplicationsMon Sep 28 1992 12:3622
>    	The requested operation cannot be
>    	completed<EOS>%MCC-E-MEM_ALLOC_FAILE, 
>       memory allocation failure

  Dan,

  This appears to be an error directly returned to Alarms from the Bridge AM.

  Memory usage is very dynamic.  It is possible that one command yields
  an out-of-memory error, and yet the next command does not.

  What were the conditions while this rule was running?  Were there a lot
  of other rules executing too?  Do you have any idea how much memory the
  entire process was using at the time?

  Use 'show proce/cont/id=<pid-number>' and watch the process virtual page
  count.  If it is approaching the 'virtualpagcnt' sysgen parameter then
  you were indeed running out of memory.  Otherwise, ... Can someone from
  the bridge team give an indication as to why the Bridge AM would return
  this error ?

  /keith
3808.2VIRTUALPAGECNT parameter is OK, but lots of rules firingCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentWed Sep 30 1992 04:0421
    Keith,
    This occurred on a VAXstation 3100/38 with 32MB memory. 
    VIRTUALPAGECNT=100000.  Process had 18000 page working set out of 32000
    possible.  Virtual pages in use were 48000.  User PGFLQUO=120000.
    
    Alarm rules were enabled in a separate FCL window for testing purposes
    instead of via batch.  I was not monitoring the FCL "alarms" window, so
    it could be that this process was running out of resources, though it
    had exactly the same default set-ups as IMPM startup process.
    
    Three global alarm rules were enabled.  One did bridge reachability,
    one did ipReachability, and the other tested Station entities.  20
    bridges were being polled every 5 minutes, as were 7 stations and 200
    ip nodes.
    
    I have noticed a few other items that should possibly be increased
    based on what I am doing.  I'll make the changes and let you know if
    the problem persists.
    
    Thanks,
    Dan
3808.3Parameters look reasonableMOLAR::ROBERTSKeith Roberts - Network Management ApplicationsWed Sep 30 1992 12:3023
RE: .2

  Dan,

  Your parameters look reasonable:

>    This occurred on a VAXstation 3100/38 with 32MB memory. 
>    VIRTUALPAGECNT=100000.  Process had 18000 page working set out of 32000
>    possible.  Virtual pages in use were 48000.  User PGFLQUO=120000.

  And you don't appear to have 'too many' things going on to eat up all
  that memory.

>    I have noticed a few other items that should possibly be increased
>    based on what I am doing.  I'll make the changes and let you know if
>    the problem persists.

  Great.  In the mean time .. can the BRIDGE team give any reasons why
  this error (MCC-E-MEM_ALLOC_FAILE) might be returned.  This could even
  be coming from the Kernel Ethernet Access routines too, I imagine.

  /keith