Conference azur::mcc

1942.0. "EFT/VMS T012 MCC_AC_MAP module failure" by BAGELS::ALAGAPPAN (Kandha Digital Services) Fri Dec 13 1991 16:55

    Can Someone tell what's wrong with creating autoconfiguration choosing
    option 9 from the Ph IV Autoconfiguration window
    
    The error occured in MCC_AC_MAP module...
    
    The log file is attached..
    
    Thanks
    Kandha
    

* * * * * * * * * *  Starting DECnet Phase IV Autoconfiguration * * * * * * * *

The autoconfiguration process consists of the following steps:

        1.  Specification of configuration criteria

        2.  Gathering of data using the chosen configuration

        3.  Generation of MCC Iconic Map files and MCC registration scripts

        4.  Execution of MCC registration scripts

Note that step 4 can be executed independently from 1-3 if the MCC
registration files for the current domain have already been generated.
To execute step 4 only, choose option 'R' from the main menu.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Press RETURN to continue>
Autoconfiguration will use the directory "USER$:[ALAGAPPAN]" as the top director
y.
Please specify a domain (10 characters or less) > four

Autoconfiguration will proceed with the domain "FOUR"
Enter Q to Quit
Is this the correct domain?[y]
                                                                                      Do you wish to:

        [A] Specify configuration criteria
            Run the DECnet Phase IV Autoconfiguration utility
            Register the entities found and EXIT.

        [R] Execute existing registration scripts for this domain and EXIT.

        [Q] Quit.

 Answer [A] > a

Starting collection of configuration criteria...


   DECnet Phase IV Autoconfiguration Search Parameters.  The discovery process
   can take a long time.  The time is dependent on the number of nodes to be
   discovered and the speed of the connections between this node and the nodes
   to be discovered.  DECnet Phase IV Autoconfiguration has a node limit of
   2000 nodes.  This limit should be considered when selecting the range of
   the discovery search.

       [1] All DECnet Phase IV nodes
       [2] All DECnet Phase IV nodes in selected area(s)
       [3] All DECnet Phase IV nodes in a LAN
       [4] All level 1 and level 2 DECnet Phase IV routers
       [5] ALL level 1 and level 2 DECnet Phase IV routers in selected area(s)
       [6] ALL level 1 and level 2 DECnet Phase IV routers on the LAN

       [7] All level 2 DECnet Phase IV routers
       [8] All level 2 DECnet Phase IV routers in selected area(s)
       [9] All level 2 DECnet Phase IV routers in the LAN

       [Q] Quit

        Enter Choice [2]: 9

   DECnet Phase IV Autoconfiguration will start collecting data from the local
   node.  This can be modified to start data collection at any node.  If the
   local area will not be included in the data collection, the starting node
   should be a node in an area that will be included in the data collection.
   If the seed node is not reachable then the autoconfiguration program will
   exit.

   Multiple seed nodes can be entered. This is done when a router does not
   support NICE network management protocol.  The seed nodes should be picked
   on each side of the router.'

Enter the starting node/s for the configuration search [4.131]:
Additional starting node/s for the configuration search [4.131]: 4.100
Additional starting node/s for the configuration search [4.131 4.100]: 4.200
Additional starting node/s for the configuration search [4.131 4.100 4.200]: 4.3
00
Additional starting node/s for the configuration search [4.131 4.100 4.200 4.300
]: 4.400
Additional starting node/s for the configuration search [4.131 4.100 4.200 4.300
 4.400]: 4.500
Additional starting node/s for the configuration search [4.131 4.100 4.200 4.300
 4.400 4.500]:

        Backbone placement

        [H] horizontal
        [V] vertical

        [Q] Quit

Enter Backbone placement [H]: h
Done collecting configuration criteria...

Running DECnet Phase IV Autoconfiguration data collection utility...
        This may take a while...


%NCP-F-CONNEC, unable to connect to listener
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
raaji$dkb0:[sys0.syscommon.][sy - Error contacting Seed node
raaji$dkb0:[sys0.syscommon.][sy - error contacting seed nodes, pick a new seed n
ode

Running DECnet Phase IV Autoconfiguration data formatting utility...


raaji$dkb0:[sys0.syscommon.][sy

 debug flag = 1
 data file name = user$:[alagappan.dna4.four]four.cf
 Horizontal Backbone orientation
 node density = 6.000000
 Starting OID = 25000
 decnet root OID = 9902

Generating registration scripts and map files...

%SYSTEM-F-FLTDIV_F, arithmetic fault, floating divide by zero at PC=0000246F, PS
L=03C00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

MCC_AC_MAP      main                             6676      0000222F  0000246F
 ...... Failed to generat registration scripts and map files
%NONAME-W-NOMSG, Message number 00000000
 ...... Failure in generating registration scripts and map files.
 ... Exiting under error conditions
Press RETURN to exit>
                                                                                

       Thanks for trying Autoconfig utility. I am sorry I took some time in
       getting back to you. 
	
       Yup you did exposed a bug in the DNA4 Autoconfig command procedure. I
       was truncating the seed address inappropriatly. I have fixed this bug
       in the kits that went out to the EFT. Can I request you to try to use
       the latest kit and see if you have a better luck? :-) Thanks,

	Anil Navkal