[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

3119.0. "alarm bugs T1.2.7" by ZUR01::FUEGLISTER (Roland Fueglister, 760-2498) Tue Jun 02 1992 16:35

I take care of an official DECmcc/SNA field test site. I have ordered already
an access to the NACqar system, but did not get a response back.
But the alarm problems, I'm experiencing, are really serious. So I describe the
problems on the following lines...

Hardware:	VAX4000 Model 60, 32MB
Software:	VMS 5.5 SSB
		DECmcc BMS T1.2.7
		DECmcc ELM T1.2.7
		DECmcc TSAM T1.2.7
		DECmcc TCP/IP DA T1.2.7
		DECmcc/SNA  V1.0
		DETmcc V1.2
		Local MIR


Alarm rules cannot be disabled correctly after a while

The following output shows, that the rule stays in state = enabled!! But the
rule seems to be disabled, because "time of last evaluation doesn't update
anymore! If I try to enable the rule again, I get the message: already
operating.
If I disable several rules from the iconic map and try to enable it
with this nice new feature Buttom "START ALL", I get the message: "operation
successful for all selected entities" ???


The only workaround to enable the bridge rules again is currently a total system
reboot.


domain LOCAL_NS:.chinf.mcc.decbr rule humb00_l_powerups at 2-jun-1992 08:51:16
all attributes

	name = humb00_l_powerups
	state = enabled
	substate = disable by user action
	disable time = 2-jun-1992 08:41:57.10
	Time of last evaluation = 2-jun-1992 08:39:08.09
	Result of last evaluation = False
	Current severity = clear
	Creation timestamp = 29-May-1992 17:14:07.88
	Evaluation error = 0
	Evaluation True = 0
	Evaluation False = 1050
	Expression = (change_of(bridge .chinf.ba.humb00_l_powerups,*,*),
			at every 00:05:00)
	Description = "bridge was powered down"
	Severity = Warning
	Problem Cause = Unknown
	Target object = bridge LOCAL_NS:.chinf.ba.humb00_l

		

SNMP Alarm rules cease to work after a while:

The following output shows, that suddendly the "Time of last Evaluation" did not
anymore update!! In this example, there is not even an error condition.
At the same time, the bridge alarm rules are continuing to evaluate!!


domain LOCAL_NS:.chinf.mcc.baden rule ipreachability at 29-may-1992 14:29:31
all attributes

	name = ipreachability
	state = enabled
	substate = running
	Time of last evaluation =29-may-1992 13:23:34.67
	Result of last evaluation = True
	Current severity = critical
	Creation timestamp = 29-May-1992 11:07:34.23
	Evaluation error = 0
	Evaluation True = 5
	Evaluation False = 1222
	Expression = (snmp * ipreachability = down, at every 00:01:00)
	Description = "Ping failed"
	Severity = critical
	Problem Cause = Unknown

The only workaround to enable the ipreachability rule again is currently a
total system reboot.

This very serious problem prevents me from implementing SNMP alarming and must
be QARed.

				Regards,

				Roland
T.RTitleUserPersonal
Name
DateLines
3119.1A reboot should not be necessaryNANOVX::ROBERTSKeith Roberts - DECmcc Toolkit TeamTue Jun 02 1992 17:5712
  Roland,

  It appears that somehow the thread which is executing the Rule just dies.
  When it dies, it has no way of updating an internal memory database 
  (which keeps track of the Rule Counters & Status).  There is no fix to
  dead threads that I know of.  Did any errors get printed to the terminal
  window ?

  As far as rebooting.  You should only need to exit MCC, which will stop
  the Alarms and delete the in-memory database.

  /keith
3119.2Alarms Bug reproduced on another systemZUR01::FUEGLISTERRoland Fueglister, 760-2498Tue Jun 16 1992 09:27143
I was able to reproduce the alarm bug on my workstation

Hardware:	Vax3100 Model 30, 24MB
Software:	same as .0

The text below is the output from DETmcc and shows the following:

1. I have enabled rule ifoperstatus_ncc004 at 11-Jun-1992
2. I have disabled rule ifoperstatus_ncc004 at 16-Jun-1992, but the rule stays
	in state= enabled
3. I have killed the process DETmcc
4. I have reenabled rule ifoperstatus_ncc004 at 16-Jun-1992, but the rule stays 
	all the time in state = in progress

Again, this is a serious bug which prevents us from implementing Alarming. This
bug must be QARed and fixed before SSB.

				Best Regards Roland


-------------------DETmcc LOG-------------------------------


show domain .rle.mcc.16_184_0 rule * all attrib
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule ifoperstatus 
!AT 16-JUN-1992 11:08:10 All Attributes
!
!                                   Name = ifoperstatus
!                                  State = Disabled
!                               Substate = Disabled by user action
!                           Disable Time = 11-JUN-1992 15:10:32.49
!                        Error Condition = "No response from entity. 
!                                          "
!                Time of Last Evaluation = 11-JUN-1992 15:10:16.86
!              Result of Last Evaluation = False
!                       Current Severity = Clear
!                           Error Entity = SNMP 
LOCAL_NS:.rle.ip.purzel-zuo-dec-com Interface * 
!                     Creation Timestamp = 11-JUN-1992 14:42:24.95
!                       Evaluation Error = 66
!                        Evaluation True = 1
!                       Evaluation False = 340
!                             Expression = (SNMP * Interface *  ifoperstatus <> 
up, at  every=00:05:00)
!                               Severity = Critical
!                         Probable Cause = Unknown
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule IFOPERSTATUS_NCC004 
!AT 16-JUN-1992 11:08:13 All Attributes
!
!                                   Name = IFOPERSTATUS_NCC004
!                                  State = Enabled
!                               Substate = Running
!                Time of Last Evaluation = 16-JUN-1992 11:08:12.07
!              Result of Last Evaluation = False
!                       Current Severity = Clear
!                     Creation Timestamp = 11-JUN-1992 18:34:09.88
!                       Evaluation Error = 0
!                        Evaluation True = 0
!                       Evaluation False = 13509
!                             Expression = (SNMP .RLE.IP.NCC004 Interface *  
IFOPERSTATUS <> UP, at  every=00:01:00)
!                               Severity = Critical
!                         Probable Cause = Unknown
!
disable domain .rle.mcc.16_184_0 rule * 
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule IFOPERSTATUS_NCC004 
!AT 16-JUN-1992 11:10:37 
!
!Normal operation will be terminated.
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule ifoperstatus 
!AT 16-JUN-1992 11:10:37 
!
!Normal operation previously terminated.
!
show domain .rle.mcc.16_184_0 rule IFOPERSTATUS_NCC004 all attrib
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule IFOPERSTATUS_NCC004 
!AT 16-JUN-1992 11:11:05 All Attributes
!
!                                   Name = IFOPERSTATUS_NCC004
!                                  State = Enabled
!                               Substate = Disabled by user action
!                           Disable Time = 16-JUN-1992 11:10:37.69
!                Time of Last Evaluation = 16-JUN-1992 11:10:12.12
!              Result of Last Evaluation = False
!                       Current Severity = Clear
!                     Creation Timestamp = 11-JUN-1992 18:34:09.88
!                       Evaluation Error = 0
!                        Evaluation True = 0
!                       Evaluation False = 13514
!                             Expression = (SNMP .RLE.IP.NCC004 Interface *  
IFOPERSTATUS <> UP, at  every=00:01:00)
!                               Severity = Critical
!                         Probable Cause = Unknown
!
use logging off
!

$ detMCC/NONINIT/PAST KILL

show domain .rle.mcc.16_184_0 rule ifoperstatus_ncc004 all attrib
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule ifoperstatus_ncc004 
!AT 16-JUN-1992 11:35:11 All Attributes
!
!                                   Name = ifoperstatus_ncc004
!                                  State = Disabled
!The rule Domain LOCAL_NS:.rle.mcc.16_184_0 Rule ifoperstatus_ncc004  was not enabled, and therefore has no counters.
!
!                             Expression = (SNMP .RLE.IP.NCC004 Interface *  IFOPERSTATUS <> UP, at  every=00:01:00)
!                               Severity = Critical
!                         Probable Cause = Unknown
!
enable domain .rle.mcc.16_184_0 rule ifoperstatus_ncc004 
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule ifoperstatus_ncc004 
!AT 16-JUN-1992 11:35:35 
!
!Normal operation has begun.
!
show domain .rle.mcc.16_184_0 rule ifoperstatus_ncc004  all attrib
!
!Domain LOCAL_NS:.rle.mcc.16_184_0 Rule ifoperstatus_ncc004 
!AT 16-JUN-1992 11:38:58 All Attributes
!
!                                   Name = ifoperstatus_ncc004
!                                  State = Enabled
!                               Substate = Running
!              Result of Last Evaluation = In progress
!                       Current Severity = Critical
!                     Creation Timestamp = 16-JUN-1992 11:35:35.80
!                       Evaluation Error = 0
!                        Evaluation True = 0
!                       Evaluation False = 0
!                             Expression = (SNMP .RLE.IP.NCC004 Interface *  IFOPERSTATUS <> UP, at  every=00:01:00)
!                               Severity = Critical
!                         Probable Cause = Unknown
!
!
3119.3QAR #3177ZUR01::FUEGLISTERRoland Fueglister, 760-2498Tue Jun 16 1992 13:404
I have qared the problem (QAR #3177)


				Best Regards	Roland
3119.4could you please try?....TOOK::CALLANDERMCC = My Constant CompanionTue Jun 16 1992 14:2710
thanks for the investigative work. could you do a bit more for me?

could you create a notify command on the domain where this rule exsists,
for events=(any confi events). Once the notify is in a running state
would you then please enable the rule. What I am looking for is to
see if you get the rule enable event from alarms. Once the rule
is enabled then give it a few seconds and disable it; do you get the
rule disable event?

thanks for the input
3119.5new qar #3208ZUR01::FUEGLISTERRoland Fueglister, 760-2498Wed Jun 24 1992 12:427
I have created a new qar for this problem --> qar #3208


				Regards,


				Roland