Conference azur::mcc

5772.0. "Notification problem with part. registered node." by COPCLU::EBC () Thu Dec 02 1993 10:10

How does DECmcc notification obtain the entity name when an event is received ?
It seems to do it differently for explicitly named nodes and wildcarded nodes.

In the following log, when SDN1 sends an adjacency down event for node WFLTR1,
the impm notification display's WFLTR1's decnet-address and a severity of
indeterminate and the targeting does not work.
When SDN1 sends an adjacency up event for node WFLTR1, the impm notification
display's WFLTR1's node-name and a severity of clear (as specified).

The relevant notify request and target assignments are shown below.
The target assignment for the adjacency down event is node specific, because
notification is only wanted for specific nodes.
The target assignment for the adjacency up event is wildcarded, because
this is easier, and it is okay to do a clear no matter what node it is.

Node WFLTR1 is a Wellfleet router, which routes decnet, but which can only
be partially registered in DECmcc as a decnet phase 4 node.
It is also registered as SNMP Heimdahl.
The partial registration seem to be cause of the problem.

Notify Domain .SDN Entity List = (Node4 *), Events = (Any Events)

ASSIGN TARGET Domain SDN event source=Node4 SDN1 Circuit ISA-0 -
Adjacent Node WFLTR1, MANAGED OBJECT="Node4 #1 Circuit #2 Adjacent Node #3",
EVENT NAME="Adjacency Down", TARGET ENTITY="SNMP Heimdahl",TARGET SEVERITY=major

ASSIGN TARGET Domain SDN event source=Node4 SDN1 Circuit ISA-0 -
Adjacent Node *, MANAGED OBJECT="Node4 #1 Circuit #2 Adjacent Node #3", -
EVENT NAME="Adjacency Up", TARGET ENTITY="Node4 #3",TARGET SEVERITY=clear



%%%%%%%%%%%%%% Event, 29-NOV-1993 15:00:52 %%%%%%%%%%%%%% [5,3]
Domain: SDN_NS:.SDN                                   Severity: Indeterminate
Notification Entity: Node4 SDN_NS:.dna_node.SDN1 Circuit ISA-0 Adjacent 
Node 60.730 
Event Source: Node4 SDN_NS:.dna_node.SDN1 Circuit ISA-0 Adjacent Node 60.730 
Event: Adjacency Down
 Adjacency Down 
                                 Reason = Adjacency listener receive timeout
                  Adjacent Node Address = 60.730
                     Adjacent Node Name = WFLTR1


%%%%%%%%%%%%%% Event, 29-NOV-1993 15:01:27 %%%%%%%%%%%%%% [5,4]
Domain: SDN_NS:.SDN                                   Severity: Clear
Notification Entity: Node4 60.730 
Event Source: Node4 SDN_NS:.dna_node.SDN1 Circuit ISA-0 Adjacent Node 60.730 
Event: Adjacency up
 Adjacency Up 
                  Adjacent Node Address = 60.730
                     Adjacent Node Name = WFLTR1

Erik B. Christensen
MCS-COMMS
Copenhagen
    

    Forcing a partial registration (by specifying action:plan) seemed to do
    the trick.
    
    Erik