Conference azur::mcc

5206.0. "Notification.log severity level become to "Indeterminate" " by TKTVFS::KOBAYASHI_S (Seiki Kobayashi, Network support/JAPAN) Wed Jun 16 1993 02:17

Hello,

MCC severity level is different between IMPM Notification window and 
mcc_notification.log. Severity of All event messages in mcc_notification.log
become to "Indeterminate", if I select the logging format to full. 
When I select the logging format to brief, then MCC output the right severity
level to mcc_notification.log.

Setup:
	1) @MCC_STARTUP_DNA4_EVL.COM on mcc node(TKTV40)
	2) Event sink set up at remote node(Node name EWBV06).

	  NCP> set log monitor event 0.9 sink node TKTV40(mcc node)

	3) Set up the notify request.

	  MCC> Notify domain test entity list=(node4 ewbv06 circuit *),
	        event=(any event) ! severity=major

	4) Set up the notification logging format to full on notification 
	   window.

MCC displays the event to notification window and outputs the event to 
mcc_notification.log, if I try to do the following command at remote 
node(EWBV06).

	$ MC NCP ZERO CIRCUIT BNA-0

However MCC severity level is different between IMPM Notification window and 
mcc_notification.log.

Notification window displays:

  ^
  | Major  1  Node4 EWBV06 Circuit BNA-0 Counters Zeroed  1-JUN-1993 17:52:52
    ^^^^^
	
Mcc_notification.log is:

%%%%%%%%%%%%%% Event,  1-JUN-1993 17:52:52 %%%%%%%%%%%%%% [11,45]
Domain: LOCAL_NS:.test                                Severity: Indeterminate
								^^^^^^^^^^^^^
Notification Entity: Node4 LOCAL_NS:.dna_node.ewbv06 Circuit BNA-0
Event Source: Node4 LOCAL_NS:.dna_node.ewbv06 Circuit BNA-0
Event: Counters Zeroed
 Circuit counters zeroed
              Seconds Since Last Zeroed = 244 Seconds
           Terminating Packets Received = 20 Packets
               Originating Packets Sent = 21 Packets
                                    .
                                    .
                User Buffer Unavailable = 0 Errors

When I select the logging format to brief, then MCC output the right severity
level to mcc_notification.log.

TV40> ty MCC_NOTIFICATION.LOG;4
Event:  major   Node4 EWBV06 Circuit BNA-0      Counters Zeroed 1-JUN-1993 16:42
        ^^^^^
:01.52  Domain LOCAL_NS:.test      [9,33]

Can anyone please explain this ?

Regards and thanks,
Seiki Kobayashi
CSC Tokyo

    You have found a bug.  Thanks for the problem report.  I have QARd this as
    QAR 573 in the MCC013_INT database (see note 7).
    
    I suggest that you use targeting to re-target the severities of those
    notifications you are interested in instead of overriding the severity
    by using the notify request, for example:
    
    MCC> assign target domain x -
    _MCC> Event Source = Node4 * Circuit *, -
    _MCC> Event = any event, -
    _MCC> target severity = major
    
    The notifications will then arrive at the IMPM with the correct
    severity and will be logged with the correct severity.