Conference azur::mcc

1989.0. "AutoConfig and V1.2 IMPM edits" by TELALL::WOODCOCK () Tue Dec 24 1991 15:54

Hi there,

I just got done running Auto-config for a single DECnet Area and I've got
a few comments about this feature and IMPM map edits and creating views
of the network.

First, I like it! It produced an accurate map with a minimum of effort
once I figured out the glitches.

The one major problem I did find is that MCC didn't properly handle entities
already registered. In looking at the log files MCC recognized an entity
already existed and stated so in the log on the failed registration. Therefore
all previously registered entities not under .dna_node had to be changed in
both scripts (registration and map). Any user who has an existing NS, either
from MCC V1.1 or other uses, who doesn't use .dna_node is in for a lot of
work. So much so it may not be worth the effort using the utility if they
have to figure out where all the nodes belong in the NS structure and edit
accordingly.

A future enhancement to consider may be the following: 

	Before building the line in the scripts make a call to DNS for the
	synonym. If it doesn't exist put the entity in .dna_node for both
	scripts. If it DOES exist use the soft link to determine the full-
	name. Then use the current full name in the scripts. This respects
	the user NS structure and provides for the addition of other entities.
        The is very important for maintain backward compatability to V1.1
	implementations.

IMPM MAP edits and views:

A major shortcoming of the map drawn is that it does not take advantage of
V1.2 features. Specifically it should place the line on the map as the
child entities it depicts (circuits) of each end point connected in the 
middle. Otherwise all the lines need to be changed to do front line 
monitoring of the network in V1.2. While we are on the subject of putting
child entities as lines on the map I have a request. In the past it has been
discussed to only show the right-most portion of the full name on the map.
This requirement still applies but I'd also like to add that the ability to
turn OFF the text is also needed. When putting the lines on the maps there
is far too much text visible. So much so that I'll probably have a 'trash'
can to place all the circuit names into for V1.2. Messy...

While autoconfig produces a good working map the IMPM editting functions now
fall short for what is needed in V1.2. In V1.1 everything was done manually
for maps and needless to say users made very few mistakes to depict the view
they wanted. But with AutoConfig MCC doesn't know what the user wants and
can only make a best guess when putting things into domains. Therefore having
the ability to push and pull entities in and out of domains is a *CRITICAL*
function needed (like MSU) in IMPM editting. Because of this MCC is probably
not well suited for a 'topology' manager trying to produce an overall view
of a large WAN from an Area->Area or Site->Site viewpoint.

kind regards,
brad...