[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

2511.0. "Autoconfigure Errors" by TROOA::BALDOCK (Chris Baldock) Fri Mar 06 1992 16:15

    
    I'm installing the DECmcc BMS V1.2.4 on a VAXstation 3100 under VMS
    V5.5.  I select the "Autoconfigure Phase IV" option from the menu
    and specify Autoconfigure all nodes (option 1).  Shortly thereafter
    I get the following error messages:
    
    Running DECnet Phase IV Autoconfiguration data collection utility...
    	    This may take a while...
    
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2 -
     Time out while expecting data from node 0.0
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2 -
     Cancel mailbox error
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2 -
     Cancel Mailbox error
    %NONAME-W-NOMSG, Message number 00000000
     ...... Failure in gathering DECnet Phase IV Autoconfiguration data.
     ... Exiting under error conditions
    Press RETURN to exit>
    
    
    Can anyone help with this?  Why is it looking for node 0.0?  Have
    I missed an intermediate step?
    
    Thanks.
    
    
    Chris
T.RTitleUserPersonal
Name		DateLines
2511.1TOOK::MINTZErik Mintz, DECmcc Development, dtn 226-5033Fri Mar 06 1992 17:032
Are you running DECnet/OSI wave I or II?
2511.2TROOA::BALDOCKChris BaldockMon Mar 09 1992 08:395
    
    No, we are running DECnet Phase IV.  Is that what you mean?
    
    
    Chris
2511.3TROOA::BALDOCKChris BaldockTue Mar 10 1992 10:499
    
    I've tried all combinations including adjacency search, searching
    all nodes, excluding area 0, etc.  Autoconfiguration still doesn't
    work.  Do I need a routing node?
    
    Thanks.
    
    
    Chris
2511.4TOOK::MINTZErik Mintz, DECmcc Development, dtn 226-5033Tue Mar 10 1992 11:116
I have forwarded your note to the autoconfig developers, but they
are very busy trying to complete their V1.2 work, so a response may
not be immediate.

-- Erik
2511.5Which starting node(s) are you using?TOOK::FIGWERUlla Figwer LKG2-2/T2 x226-7858Wed Mar 11 1992 18:0916
    
    Hello Chris,
    
    Sorry for my late response.
    
    I suspect that the Autoconfiguration software is having trouble
    contacting the starting node you specified.  Are there any other
    messages printed between "This may take a while..." and
    the errors about node 0.0?
    
    Which node(s) are you specifying as starting node(s)?
    
    Thanks,
    
    Ulla
2511.6TROOA::BALDOCKChris BaldockThu Mar 12 1992 08:2947
    
    No other messages are printed out in this instance.  I specify
    node 1.45 (the local node) as the seed.
    
    I've also tried node 1.8 (the boot node for the cluster) but the results
    are the same.
    
    I've tried another satellite node and the results are as follows:
    
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2
    data file = sys$common:[mcc.dna4.test]mcc_test.cf
    debug flag = 1
    collecting all nodes
    
    Seed Nodes
     1.2
    areas to include
     1
    
     areas to exclude
    
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2 -
      Data collection complete
    
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_mapper.exe;2
    
     debug flag = 1
     data file name = sys$common:[mcc.dna4.test]mcc_test.cf
     Horizontal Backbone orientation
     node density = 6.000000
     Starting OID = 25000
     decnet root OID = 9902
    
     oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_mapper.exe;2 -
      Node HELIUM is not placed on the map, no connections found
    
    
    Note that the above message is contained in the exceptions file in
    sys$common:[mcc.dna4.test].
    
    Could I be running into a quota problem or is a system parameter not
    set properly?
    
    
    Chris
2511.7TROOA::BALDOCKChris BaldockThu Mar 12 1992 08:3816
    
    Oops!  I have received another set of errors at times:
    
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2 -
     Time out while expecting data from node 0.0
    
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2 -
     Error contacting seed node
    
    oxygen$dkb500:[sys11.syscommon.][syslib]mcc_ac_wan4_collector.exe;2 -
     Error contacting seed nodes; Pick a new seed node
    
    All of the nodes in the network are up and running and communicating
    with each other.
    
    Chris
2511.8TOOK::R_SPENCENets don't fail me now...Fri Mar 13 1992 09:467
    Do the nodes permit network management actions?
    
    FOr example can you do a MCR NCP TELL <node> SHOW EXEC and have it work?
    	replace <node> with your seed node
    
    s/rob