| 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 |
A customer is still on V1.1 of DECmcc . he is unable to do the upgrade yet because he has lots of Translan bridges which is currently managed by the Translan_AM. All V1.1 patches has been applied. The MCC_DNA4_EVL process regularly dies. The process may be restarted but OCCURS alarm rules nolonger fires. I have checked that process MCC_DNA4_EVL is running, object MCC_DNA4_EVL exist and links for EVL and MCC_DNA4_EVL exists. When the event occurs, OPCOM reports the event but the rule does not fire. The only way that seems to clear the problem is a reboot. I have noticed that the restarted MCC_DNA4_EVL process seems to stay in COM state. I know there were problems with MCC_DNA4_EVL in V1.1 , is this one of them ? Are there any workaround ? The customer does not feel that rebooting is a good solution. The log file that show the process exits is attached. $ manage/enter/presen=mcc_dna4_evl Network object MCC_DNA4_EVL is declared, Status = 52854793 Waiting for the event message from EVL..... The connection with EVL is established. ** Unable to connect to NMCC ** 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... |----what does this mean ? Ready to read the next event message... V A fatal error occurred when sending event = 418 to MCC event manager! The EVL sink is terminated! OPS_DNA4_STOP_SINK_MONITOR Failed at step 5, status = 52877226 STOP_SINK_MONITOR is terminated, thread id = 65539, status=52854793 Andrew Sydney, CSC
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4204.1 | command file + 1.2 | COMICS::MISTRY | Tue Dec 08 1992 04:22 | 10 | |
Hi, Regarding this, for 1.1 there was a batch job that ran every so often and checked the state of MCC_DNA4_EVL process. First of all can someone give me a pointer to where this command file is and secondly the problem still exist in 1.2 and i believe T1.3. If this is true i assume i can still use the afor mentioned command file. Bipin | |||||
| 4204.2 | do you have a heavy-load system | TOOK::JEAN_LEE | Fri Dec 11 1992 11:46 | 41 | |
reply to .0.
>>$ manage/enter/presen=mcc_dna4_evl
>>Network object MCC_DNA4_EVL is declared, Status = 52854793
>>Waiting for the event message from EVL.....
>>The connection with EVL is established.
>>** Unable to connect to NMCC **
>>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... |----what does this mean ?
>>Ready to read the next event message... V
>>A fatal error occurred when sending event = 418 to MCC event manager!
^^^^^ ^^^^^ ^^^^^^^^^^^
| means event 4.18
V
This error is caused from either "Insufficient event pool memory" or
"Event Manage internal error".
This is a known problem in V1.1. Event Manager did not handle well the
situation of an over-loaded system that monitor busy events. When this
occurs, users should stop all MCC processes on the system and start over
again. HOwever, if this happens frequently, users should consider a long
term solution, perhaps to upgrade hardware or improve system configuration.
If this over-loading situation does not happen frequently, I would definitely
upgrade DECmcc to the latest and the greatest version V1.3. It has much
better handle on over-load system that uses DECmcc event monitor.
Hope this helps.
Jean
| |||||
| 4204.3 | one more thing | TOOK::JEAN_LEE | Fri Dec 11 1992 11:59 | 8 | |
add to .2.
There is a good piece of information in mcc-tools notes(noted::mcc-tools)
file,, #13. It talks about Event Manager.
Jean
| |||||