Conference azur::mcc

1424.0. "Changed line names require reregistration" by SUBURB::SMYTHI (Ian Smyth 830-3869) Fri Aug 30 1991 09:17

	Here's something I noticed recently.

	If you have a Node4 registered with all it's lines and 
circuits name SYN-* and somebody renames those line to something 
more understandable, the Node4 needs to be reregistered before the 
line speeds can be added. eg


show node4 olort1 line syn-0 all char

Node4 41.71 Line syn-0 
AT 30-AUG-1991 13:06:52 Characteristics

No such entity: Node4 olort1 Line syn-0 
                         Unknown Entity = Node4 olort1 Line syn-0 

show node4 olort1 line reo   all char

Node4 41.71 Line reo 
AT 30-AUG-1991 13:07:04 Characteristics

Examination of Attributes shows:
                                 Device = SYN-0
                        Receive Buffers = 64
                             Controller = Normal
                                 Duplex = Full
                               Protocol = DDCMP Point
                                  Clock = External
                          Service Timer = 20000 Milliseconds
                       Retransmit Timer = 3000 Milliseconds

set node4 olort1 line reo line speed 256000

Node4 41.71 Line reo 
AT 30-AUG-1991 13:07:28 Characteristics

Internal error in DECnet Phase IV AM.
                              MCC Error = %MCC-E-NOENTITY,  no corresponding 
                                          entity instance exists 

set node4 olort1 line syn-0 line speed 256000

Node4 41.71 Line syn-0 
AT 30-AUG-1991 13:07:38 Characteristics

Modifications completed successfully
                             Line Speed = 256000

register node4 .DNA_Node.OLORT1

Node4 UKHUB_NS:.DNA_Node.OLORT1 
AT 30-AUG-1991 13:09:31 

The requested operation cannot be completed
                  Entity Existence Info = Entity Exists

set node4 olort1 line reo line speed 256000

Node4 41.71 Line reo 
AT 30-AUG-1991 13:09:48 Characteristics

Internal error in DECnet Phase IV AM.
                              MCC Error = %MCC-E-NOENTITY,  no corresponding 
                                          entity instance exists 

deregister node4 olort1

Node4 41.71 
AT 30-AUG-1991 13:10:09 

Deregistration Successful

register node4 .DNA_Node.OLORT1

Node4 UKHUB_NS:.DNA_Node.OLORT1 
AT 30-AUG-1991 13:10:27 

Registration Successful

set node4 olort1 line reo line speed 256000

Node4 41.71 Line reo 
AT 30-AUG-1991 13:11:13 Characteristics

Modifications completed successfully
                             Line Speed = 256000

set node4 olort1 line syn-0 line speed 256000

Node4 41.71 Line syn-0 
AT 30-AUG-1991 13:11:22 Characteristics

Internal error in DECnet Phase IV AM.
                              MCC Error = %MCC-E-NOENTITY,  no corresponding 
                                          entity instance exists 

use logging off

unluckily that is correct. It is a side effect to how registration is
done, and to how the NODE4 lines are defined. In short, it is my understanding
that what happens is that the dynamic child entities, are queried, and their
idents are stored at registration time. It is this process which forces
you to reregister before being able to store the line speed (which is not
a "real" attribute and is therfore stored in the MIR along with the identifier).

    
    We try to keep a little bit of information about entities which will
    not frequently change (non-dynamic) in the namespace.  We use both
    circuit and line children to store orphaned attributes related to their
    management.
    
    Yeah, regretably, you have to register the node4 again, or,
    alternatively, you can hand register the 'new' line:
    
    	MCC> register node4 .node line reo
    
    Most (or all) of the child entities of node4 support the registration
    directive and can be registered against their global parent.
    
    In this case, you can have your cake and eat it too, because we won't
    automatically deregister the syn-0 line.  It will still be available
    with its orphaned line speed as well.   Yes, they can get
    unsynchronized, because we don't know that you're talking about the
    same line both ways.  So, if you want to get rid of syn-0, you can
    just deregister it using:
    
    	MCC> deregister node4 .node line SYN-0
    
    One last note (or point of interest, perhaps).  The DNA4-AM won't SHOW
    you any orphaned information about any lines or circuits that the node4
    doesn't report in on.  That is, we display information (real,
    synthesized, and orphaned data) only for child entities that the node4
    query reports on, so leaving it there won't be visible unless you
    change the name back....
    
    -Jim
    

	Thanks for the replies.


	Having to deregister and re-register the node4s again wasn't
too much of a problem. Modifying the alarms etc on the changed
circuits was more time-consuming. 


Ian.