| 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 |
Hi!, We have a cust. who sees the following problem intermittently with V1.1 of MCC Currently monitoring is of 2 Decrouter 2000's (with 7 Circuits) for 'Circuit Up' and 'Circuit Down' s ...Mem pool has no expansion and Gblsections =400 ,gblpages=30,000 and Pgflquo = 100,000 for 1 account which starts it up and 50,000 for system-although the problem has been seen when mcc has been started by either account.To clear this a shut down of the session & killing the mcc_dna4_evl process normally allows a clean restart again, BUT occasionally a reboot of the 3100 is neccessary. [He thinks that the 'INSEVTPOOLMEM' occurrs mostly when he sees a repetitive event eg circuit bounce ] ..The following was gathered from the mcc_dna4_evl logfile $Manage/enter/present=mcc_dna4_evl Network Object MCC_DNA_EVL is declared, status = 52854793 Waiting for the event message from EVL..... **Unable to Connect to NMC** Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message.. Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM Ready to read the next event message... Failed to send event = 504 to MCC event manager,INSEVTPOOLMEM etc..... ....DECMCC BMS System Messages say the Source is KERNEL and that there is 'INSUFFICIENT EVENT POOL MEMORY TO POST EVENT"....... 'too many events (in quantity or size) have already been posted' and to 'Submit an SPR' ....Is this problem known ,or currently being worked upon ?? Many Thanks, Sandie.................
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1658.1 | SPR Submitted | KERNEL::MACLEAN | Networks & Comm.s,UK CSC | Tue Oct 22 1991 05:22 | 3 |
The Problem in 1658.0 has now been SPR'd
Regards,
Sandie......................
| |||||
| 1658.2 | thanks for submitting SPR | TOOK::CALLANDER | MCC = My Constant Companion | Thu Oct 24 1991 10:14 | 12 |
I have also forwarded the information you supplied to the developers involved with the event manager. The feedback you provided should help. Please note tht if this is happening with a high frequency you might want to get in touch with Bob (Took::) Merrifield, he might be able to help you get setup with a larger event pool. In the past we have seen these problems in v1.1 only after a large number of events have been processed, but your descriptiong looks like it was more related to the speed in which the events occurred, is that what you have seen? thanks. jill | |||||
| 1658.3 | Thanks for your reply... | KERNEL::MACLEAN | Networks & Comm.s,UK CSC | Fri Oct 25 1991 06:01 | 5 |
From the customer data It Appears to be the speed at which the
events occurred,as he says he is currently monitoring only the 2
Decrouters, with 7 circuits each, for circuit up/down....
Sandie.
| |||||
| 1658.4 | Rate of events received looks to be the problem | KAOT01::S_HYNDMAN | Thu Oct 31 1991 10:13 | 6 | |
Our site was also experiencing this problem and installed the
patch to increase the event manager pool. We no longer see this
problem....one down.
Scott
| |||||
| 1658.5 | Patch location ??? | SNOC01::MISNETWORK | They call me LAT | Fri Dec 20 1991 00:06 | 6 |
I have sent mail to Bob (Took::) Merrifield without a response so far.
Does anyone know where this patch can be found, my alarms are in a dead
state, and they will not come back for an extended period of time.
Cheers,
Louis
| |||||
| 1658.6 | Just got it ! | SNOC01::MISNETWORK | They call me LAT | Sat Dec 21 1991 06:46 | 5 |
Just received the patch from Bob, many thanks.
Cheers,
Louis
| |||||