[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

5819.0. "Alarm evaluation & exception Question" by KERNEL::WARDJO () Thu Jan 13 1994 07:07

    Hello,
    
    A customer recently created a generic alarm to check on all node4 in a
    domain to see if the send failures goes up.
    
    He is seeing exceptions being fired which appear to be trying to
    evaluate on the rule itself, rather than the node4 send failures and
    thus giving the error below.
    
    Has anyone else seen this or am I missing something simple?
    1.3 of DECmcc (Polycenter Network Manager 400)
    
    
    
    
    !!!!!!!!!!!!!! Alarm, 11-JAN-1994 15:04:13 !!!!!!!!!!!!!! [3,1008]
    Domain: NNNNNNN_NS:.SANDWICH.MCC_DB.VAXES    Severity:Indeterminate
    
    Notification Entity: MCC NNNNNNN_NS:.MCC.SMVX3F_DIRECTOR ALARMS RULE
    NODE4_LINE_SEND_FAILURES
    Event Source: Domain NNNNNN_NS:.SANDWICH.MCC_DB.VAXES Rule
    NODE4_LINE_SEND_FAILURES
    
    Event: OSI Rule Exception
    
                                 Event Type = QualityofServiceAlarm
                                 Event Time = 11-JAN-1994 15:04:12.53
                             Probable Cause = Unknown
                            Additional Info = { (
                               significance = True,
                                 information = "Rule could not be evaluated as
                                               the attribute was not returned 
                                               by the Entity." ),
                                                (
                                   significance = True,
                                    information = "(CHANGE_OF (Node4 * Line*  
                                                  Send Failure, 0, *), at
                                                  every=02:00:00)" ) }
                             Managed Object = MCC 0 ALARMS RULE
                                              NODE4_LINE_SEND_FAILURES
                         Perceived Severity = Indeterminate
                             Additionaltext = " DECnet line send failure rule"
    
    Any help appreciated,
    
    
    Jon

T.R	Title	User	Personal Name	Date	Lines
5819.1	Two things...	RACER::DAVE	Ahh, but fortunately, I have the key to escape reality.	`Thu Jan 13 1994 10:19`	17
	Well, one thing of interest is that the Entity and the event source claim to be in different name spaces. One is <7Ns>_NS: while the other is <6Ns>_NS:. The Domain itself appears to be in both!!!! Not sure what any of this code would do running in two different name spaces. Or is this a case that you feel compelled to hide some information and have edited the output to disguise the source? Assuming that you have some compulsive secrecry desires ( :-) ), it seems to be fairly straightforward, and is functioning as documented. information = "Rule could not be evaluated as the attribute was not returned by the Entity." ), says it all. Hence, the rule is Indeterminate, as there is no way to tell that it changed from 0 to anything else.
5819.2	The N's are due to me.	KERNEL::WARDJO		`Fri Jan 14 1994 13:16`	11
	Thanks for the reply, The N's were edited in by me to replace the customers name - I should have made this clear in my note, plus I need to learn to count properly. I will reread your reply and put a further reply to try & explain what is happening. Jon
5819.3	Managed object is the rule!	COMICS::WARDJ		`Thu Jan 27 1994 10:49`	5
	The main problem I have is that the managed object is the MCC 0 ALARM RULES, rather than the node4. Can anyone explain how this can happen.
5819.4	Help Please	KERNEL::WARDJO		`Tue Feb 08 1994 04:48`	18
	Hello, Can no one explain how the exception managed object can be "MCC 0 ALARMS RULE" when the alarm is on NODE4 LINE * SEND FAILURES. What exactly is this exception telling me? Am I missing something obvious? How can I track where the exception is coming from? If anyone can help I would very much appreciate it. Thanks, Jon
5819.5	some answers	TAEC::FLAUW	Marc Flauw, CEM Technical Office, VBO	`Tue Feb 08 1994 08:50`	38
	Jon, I don't know if I am going to help you much, but I can try ... The rule exception is already giving you quite some info. As .1 was saying : information = "Rule could not be evaluated as the attribute was not returned by the Entity." ), says it all. It means that for one lines of one of the nodes in your domain this attribute is not available. If I remember well, I think that this attribute is only there for Ethernet lines. If so, it means that you have a WAN line where this attribute is not present. A way to check this would be for each node4 in your domain to issue a mcc> show node4 <name> line * Send Failure and you should have at least one node4 line that won't return this attribute. Regarding the Managed Object, the Rule Exception is an event on the rule object itself to tell the user that there was a problem evaluating this rule. It might or it might not be related to a problem with the entity, which is why it is emitted on the rule entity. What seems to be missing here is the instance of the entity (node4 xx line yy) that causes the problem. I don't remember whether the alarm has some form of log file where additional information on error or exception might be logged. Hope this helps, Best regards, Marc.