| With starting up the same rules today, I found the following entries in the
errorlogfile:
>>> 18-NOV-1991 11:51:24.27 MCC 0 ALARMS RULE Pacf_Form_Err_VX0001
Expression = (OCCURS(NODE4 .VX0001 circ * Packet Format Error))
Status = %MCC-E-INV_HANDLE_STAT, software error: invalid handle state
MCC 0 ALARMS RULE Pack_Form_Err_VX0001
AT 18-NOV-1991 11:51:24
>>> 18-NOV-1991 11:51:29.63 MCC 0 ALARMS RULE Adjac_Dwn_VX0003
Expression = (OCCURS(NODE4 .VX0003 circ * Adjacent node * Adjacency Down))
Status = %MCC-E-INV_HANDLE, software error: invalid handle parameter
>>> 18-NOV-1991 11:51:31.94 MCC 0 ALARMS RULE Adjac_Up_VX0003
Expression = (OCCURS(NODE4 .VX0003 circ * Adjacent node * Adjacency Up))
Status = %MCC-E-INV_HANDLE, software error: invalid handle parameter
MCC 0 ALARMS RULE Adjac_Up_VX0003
AT 18-NOV-1991 11:51:31
>>> 18-NOV-1991 11:51:35.25 MCC 0 ALARMS RULE Node_Reach_Change_VX0001
Expression = (OCCURS(NODE4 .VX0001 remote node * Node Reachability Change))
Status = %MCC-E-INV_HANDLE, software error: invalid handle parameter
MCC 0 ALARMS RULE Node_Reach_Change_VX0001
AT 18-NOV-1991 11:51:35
>>> 18-NOV-1991 11:56:35.50 MCC 0 ALARMS RULE Dev_Stat_On__DBR01
Expression = (BRIDGE ._DBR01 Device State = Operating, AT EVERY =00:10:00)
Status = %MCC-F-EVENTINTERNERR, Event Manager internal error
MCC 0 ALARMS RULE Dev_Stat_On__DBR01
AT 18-NOV-1991 11:56:35
>>> 18-NOV-1991 11:57:21.07 MCC 0 ALARMS RULE Line_Byte_Sent_VX0001
Expression = (CHANGE_OF(NODE4 .VX0001 LINE BNA-0 Bytes Sent,*,*),
AT EVERY =00:10:00)
Status = %MCC-F-EVENTINTERNERR, Event Manager internal error
MCC 0 ALARMS RULE Line_Byte_Sent_VX0001
AT 18-NOV-1991 11:57:21
>>> 18-NOV-1991 11:57:38.19 MCC 0 ALARMS RULE Line_Byte_Sent_VX0002
Expression = (CHANGE_OF(NODE4 .VX0002 LINE BNA-0 Bytes Sent,*,*),
AT EVERY =00:10:00)
Status = %MCC-F-EVENTINTERNERR, Event Manager internal error
MCC 0 ALARMS RULE Line_Byte_Sent_VX0002
AT 18-NOV-1991 11:57:38
>>> 18-NOV-1991 11:58:02.73 MCC 0 ALARMS RULE Line_Byte_Sent_VX0003
Expression = (CHANGE_OF(NODE4 .VX0003 LINE MNA-0 Bytes Sent,*,*),
AT EVERY =00:10:00)
Status = %MCC-F-EVENTINTERNERR, Event Manager internal error
MCC 0 ALARMS RULE Line_Byte_Sent_VX0003
AT 18-NOV-1991 11:58.02
>>> 18-NOV-1991 11:58:20.06 MCC 0 ALARMS RULE Line_Byte_Sent_VX0004
Expression = (CHANGE_OF(NODE4 .VX0004 LINE MNA-0 Bytes Sent,*,*),
AT EVERY =00:10:00)
Status = %MCC-F-EVENTINTERNERR, Event Manager internal error
MCC 0 ALARMS RULE Line_Byte_Sent_VX0004
AT 18-NOV-1991 11:58:20
After rebooting the system and enabling the same set of rules, it seems to be
working again, there are no entries in the log file so far.
|
| There is a great hesitancy to spend time on problems like these for two
reasons. First, we are working all out to get V1.2 out the door.
Second, and more important, the MCC Event Manager has undergone major
reconstructive surgery (under the skillful hands of Dr T. Hupper). It
is essentially new code, the chances of these sorts of problems are
much less likely.
But nonetheless, there are some things you can try. The problem with
with running Alarms in Batch is that there is no elegant way to stop
the process. You CANNOT issue a $STOP/ID=xxxxxx and expect the MCC
V1.1 Event Manager to handle that. There are alternatives, documented
elsewhere in this notesfile (I haven't the foggiest idea which notes).
Also, you could define the logical MCC_EVENT_LOG to 1, this will trace
Event Manager Internal Errors, and give us a better idea of exactly
what is getting corrupted, or breaking. Do you have any other MM's
enrolled other than the ones that came on the kit? What machine are
you running on (4000?)?
-Matt.
|
| This is found with in the MCC_DNA4_EVL.LOG
$ manage/enter/presen=mcc_dna4_evl
Network object MCC_DNA4_EVL is declared, Status = 52854793
Waiting for event message from EVL.....
Tracing error paths in Event Manager
The connection with EVL is esthablished
** Unable to connect to NMCC **
Ready to read next event message...
Ready to read next event message...
Event Put could not Lock an Event Request:
%NONAME-W-NOMSG, Message number 00000000
Error Deleting AHS in Event Put:
%MCC-E-INV_HANDLE_STAT, software error: invalid handle state
Failed to Put an Event due to...
%NONAME-W-NOMSG, Message number 00000000
A fatal error occurred when sending event = 418 to MCC event manager!
The EVL sink is terminated!
EDQ_DEQW_SUBSCR_EVENT found alert termination request
Get Event was Alerted
OPS_DNA4_STOP_SINK_MONITOR Failed at step 5, status = 52877226
STOP_SINK_MONITOR is terminated, thread id = 65539, status=52854793
SYSTEM job terminated at 29-NOV-1991 12:49:07.13
Accounting information:
Buffered I/O count: 153 Peak working set size: 1566
Direct I/O count: 90 Peak page file size: 6987
Page faults: 2977 Mounted volumes: 0
Charged CPU time: 0 00:00:05.30 Elapsed time 0 00:45:18.63
In the errorlog file in mcc_common every change_of rule is logged with the
status %SYSTEM-F-IVLOCKID, invalid lock id or %SYSTEM-E-DEADLOCK, deadlock
detected, but the rule which should handle 4.18 event isn't in there.
The system is running VMS 5.4-2 with DECmcc BMS version 1.1 and the SNMP AM.
Only about 150 alarm rules are enabled from 1500 rules registered, with no
recording or exporting running on a VAXSTATION 3100/76 with 24 MB memory.
This is what I found in the logfile,
Adrie Timmermans.
|