| My guess is that the problem is NOT the Bridge AM leaking memory (95% certain,
based on information Tom supplied to me recently).
The problem is probably one of resource consumption on the part of:
1. Bridge AM - The Bridge AM requires on the order of 55 pages
of stack per instantiation. Due to the way DECmcc handles
stack, the Alarms FM must pre-allocate at least that much
stack memory per Bridge Rule before calling the Bridge AM.
Multiply 55 pages by the number of rules to determine
how much stack memory Alarms FM requires BEFORE BRIDGE AM
is called.
2. MCC_EA Exec Common Routines - The Bridge AM uses the Exec Common Routine
MCC_EA_Request_Enet_Packet to access the wire. It turns
out that MCC_EA creates two threads per request, eack of
which (for V1.0) took the default stack size (64 pages!).
So for every poll that the Alarms FM does, touching the
wire consumes another 128 pages of stack memory (we have
cut this to something like 4 pages for X1.1.1, a V1.1
Base Level, but obviously you don't have V1.1). Since multiple
threads from the Bridge (and Ethernet) AM can stall in the
MCC_EA waiting for $QIOs to complete, we could be talking
mucho pages of memory. This fact means that active alarms
reduce the number of enabled alarms by something like two-
thirds.
The Alarms Team spent alot of time characterizing DECmcc from the standpoint
of the Alarms FM, and published some of their findings in the V1.0 Release
Notes.
Assuming that this is the problem, increasing pagefilequota for the process
running DECmcc should increase the number of Bridge Alarm Rules possible.
The other "workaround" would be to split the Alarm Rules across multiple
processes.
|
| <<< Note 374.0 by TAZBOY::ZIGLER "Tom Zigler, DTN 432-7541" >>>
> -< Alarms START ETHERNET DEVICE FAILURE - HELP! >-
>
>I am currently running the DECmcc BMS EFT Update (T1.0.1) software on a
>VAXstation 3100 model 30 running VMS V5.3. When attempting to enable MCC
>Alarms, each with a polling rate of 5 minutes, for approximately 25 LAN Bridges
>(mixture of 100s, 150s, and 200s), we get the following error message
>consistently whenever more than 18 Alarms are enabled interactively:
>
> MCC-F-STRTDEVERROR, START ETHERNET DEVICE FAILED
> SYSTEM-F-EXQUOTA, EXCEEDED QUOTA
> :
> :
>Any ideas?
I have come accross the same problem not too long ago. My page file was 10,000
blocks. I extended it to 40,000 blocks and the prblem went away. Can you again
check and let us know what is the size of your page file?
I have tried ~50 bridge rules with 1 minute interval in a VAX3800. Every thing
ran fine for atleast 1 hr. So it got to be the page file. Let us know if you
need more help.
- Anil Navkal
|