Conference azur::mcc

2958.0. "ELMS autopology problem" by ESMAIL::SHETHAR () Thu May 07 1992 15:19

	Greetings,
	
	I have been experimenting with the LAN Autopology feature of MCC.
	I have run into a problem that I can't figure out.  I searched the
	notes with a couple different key words, but found no reference to
	what I have encountered.  So here goes.

	Am running DECmcc version 1.2.4 with ELMS T1.2.4 on a uVAX 3900 with
	32 meg of memory (VMS 5.4).  I open up a new domain called AUTOTOP
	that is not part of any hierarchy (not nested). Then I can select 
	Applications -->Spanning Tree Map --->Automap (with Autoregister=false)
	and I get a very nice map snapshot to the spanning tree, which 
	consists of about 15 DEC LANbridges.  In the namespace, the bridges 
	were previously	registered as follows:

		.BRIDGE.LB200AC
		.BRIDGE.LB100DE
		.BRIDGE.LB150AB
		   (etc)

	Like I said, everything looks good with the above-mentioned bridges
	integrated into the map snapshot.

	However, when I repeat the Automap operation with Autoregister=true,
	I get quite a different result. At first, I got no map but only a
	picture of the default bridge and domain icons.  Realizing that
	the map file created by the autopology FM was probably not in MCC_
	MAPS, I put it there and re-opened the domain autotop.  A map is 
	drawn, but now I get a separate window telling me that there were 
	"entites found in the domain but not in the map file" and "entities 
	found in the map file but not in domain" (the window that displays
	the message/list then never goes away!!). The map itself shows a 
	spanning tree without any of the bridges present, only the "LAN"
	domains.  The lines and associated port numbers are there too.  But
	the bridges that were in the map snapshot are now autoplaced (with
	default bridge icons) off to the lower left corner.  By repeating
	the Automap operation with and without autoregistration, I noticed
	that the Automap (with autoregister=false) labels a bridge .LB200AC
	instead of .BRIDGE.LB200AC.  It seems as though automap (with auto-
	register=true) doesn't recognize the full registered name of the
	bridge, and therefore autoplaces it outside of the map (as "entities
	found in domain but not in map file). Yet automap cannot map .LB200AC
	because it is an "entity found in map file but not in domain".

	A few lines from mcc_stm_autotop_autoreg.com:

	 $MANAGE/ENTERPRISE
	 CREATE DOMAIN CASHEW_NS:.AUTOTOP MEMBER CASHEW_NS:.BRIDGE.LB100AC
	 CREATE DOMAIN CASHEW_NS:.AUTOTOP MEMBER CASHEW_NS:.BRIDGE.LB100DE
	 CREATE DOMAIN CASHEW_NS:.AUTOTOP MEMBER CASHEW_NS:.BRIDGE.LB100AB
		(etc)

	The log file (mcc-stm_autopo_autoreg.log) indicates that, by default, 
	all bridges found by the listener are registered as .BRIDGE.<bridge>.
	Like the release notes say, the duplicate identifiers are found and
	so the error messages I get are understandable. The messages log 
	(mcc_stm_messages.log) shows proper operation too.

	Any ideas?

	Two suggestions:

	1.) Autoregister option should give the user the option of viewing/
	    editing its contents before being run.

	2.) Map file created should be automatically moved to MCC_MAPS

	
	Thanks for any help...
    
    	Alan

    
    This is a bug in the T1.2.4 version of ths STM FM.  It has been 
    fixed in version T1.2.7.   The problem is that the map file
    doesn't have the the entire bridge names so the IMPM thinks they
    are different bridges.  The T1.2.7 version uses the entire name
    of the bridge.   Give this version a try.  It has alot of 
    improvements over T1.2.4.
    
    
    >	1.) Autoregister option should give the user the option of viewing/
    >	    editing its contents before being run.

    This is a good suggestion.  You can accomplish this now with the
    following steps.
    
    1. Run the STM FM  automap command with autoregister=false.
    This will generate an autoregistration script called:
    mcc_stm_<domain_name>_autoreg.com.
    
    2.  Edit the script to change the bridge names (don't change the
    LAN segment names) and run the script.
    
    3. Run the STM FM automap command with autoregister=true using
    the same domain as in step. 1.
      
    
 >	2.) Map file created should be automatically moved to MCC_MAPS
    
    This is done in STM FM T1.2.7
    
    
    Thank you for your suggestions,
    
    Bob
    

    
    
    Bob,
    
    Thank you for the reply.  I'll look for version T1.2.7...
    
    Alan

See notes 3.149 and 3.150 for ELM T1.2.7

Bob