[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

2367.0. "DNA4 Autoconfig ACCVIO" by HAZARD::BAKER (Paul Baker, UK Product and Technology Group - 844 3311) Wed Feb 19 1992 09:05

I attempted a DNA4 autoconfig for area 63, and experienced the following
problems. Can anyone offer any suggestions, please.

The system is a VS3100 M38 with 24Mb memory, VMS V5.4-3, DECmcc T1.2.4 with ELM
AM installed and is using the local namespace.

Paul.

-------------------------------------------------------------------------------

Extracts from DNA4 autoconfig session:

%NCP-F-CONNEC, unable to connect to listener
-SYSTEM-F-LINKEXIT, network partner exited
uvdem2$dkb0:[sys0.syscommon.][s - Node 63.240 did not respond.
Results from 63.240, 0 circuits, 0 adjacencies, Q size 42...

%NCP-F-CONNEC, unable to connect to listener
-SYSTEM-F-LINKEXIT, network partner exited
uvdem2$dkb0:[sys0.syscommon.][s - Node 63.252 did not respond.
Results from 63.252, 0 circuits, 0 adjacencies, Q size 41...

%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FFC1278C,PC
=0004E975, PSL=03C00000
  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00010658
        Name   = 0000000C                00000000
                 00000001                00000000
                 FFC1278C                2FFC0000
                 0004E975                7FF10574
                 03C00000                7FF10548
                                         0001590C
                                         00000001
                                         00010658
                                         0000DA00
 
        Register dump

        R0 = 00000001  R1 = 0001065C  R2 = 0000F9F9  R3 = 00000014
        R4 = 000017F7  R5 = 00000000  R6 = 00000000  R7 = 00010654
        R8 = 00024603  R9 = 00010660  R10= 0001A235  R11= 00010668
        AP = 7FF104B8  FP = 7FF10478  SP = 7FF104F4  PC = 0004E975
        PSL= 03C00000

uvdem2$dkb0:[sys0.syscommon.][s - Node 63.72 did not respond.
Results from 63.72, 0 circuits, 0 adjacencies, Q size 40...

%NCP-F-CONNEC, unable to connect to listener
-SYSTEM-F-LINKEXIT, network partner exited
uvdem2$dkb0:[sys0.syscommon.][s - Node 63.407 did not respond.
Results from 63.407, 0 circuits, 0 adjacencies, Q size 39...

Results from 63.575, 1 circuits, 1 adjacencies, Q size 38...

%NCP-F-CONNEC, unable to connect to listener
-SYSTEM-F-LINKEXIT, network partner exited
uvdem2$dkb0:[sys0.syscommon.][s - Node 63.401 did not respond.
Results from 63.401, 0 circuits, 0 adjacencies, Q size 37...

Results from 63.108, 1 circuits, 1 adjacencies, Q size 36...
%NCP-F-CONNEC, unable to connect to listener
-SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node
uvdem2$dkb0:[sys0.syscommon.][s - Node 63.588 did not respond.
Results from 63.588, 0 circuits, 0 adjacencies, Q size 35...

%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FFC1278C,
PC=0004E975, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents
       Signal arguments              Stack contents

        Number = 00000005                00010658
        Name   = 0000000C                00000000
                 00000001                00000000
                 FFC1278C                2FFC0000
                 0004E975                7FF10574
                 03C00000                7FF10548
                                         0001590C
                                         00000001
                                         00010658
                                         0000DA00
        Register dump

        R0 = 00000001  R1 = 0001065C  R2 = 0000F9FA  R3 = 00000014
        R4 = 000017F7  R5 = 00000000  R6 = 00000000  R7 = 00010654
        R8 = 00024603  R9 = 00010660  R10= 0001A235  R11= 00010668
        AP = 7FF104B8  FP = 7FF10478  SP = 7FF104F4  PC = 0004E975
        PSL= 03C00000

uvdem2$dkb0:[sys0.syscommon.][s - Node 63.583 did not respond.
Results from 63.583, 0 circuits, 0 adjacencies, Q size 34...
 
            .....and then, at the end.....

Results from 63.625, 1 circuits, 1 adjacencies, Q size 0...
uvdem2$dkb0:[sys0.syscommon.][s - data collection complete
uvdem2$dkb0:[sys0.syscommon.][s - Time out excepting data from node 0.0


Running DECnet Phase IV Autoconfiguration data formatting utility...


uvdem2$dkb0:[sys0.syscommon.][s

uvdem2$dkb0:[sys0.syscommon.][s

 debug flag = 1
 data file name = sys$sysdevice:[nms_demo.dna4.dsd]dsd.cf
 Horizontal Backbone orientation
 node density = 6.000000
 Starting OID = 25000
 decnet root OID = 9902
%SYSTEM-F-FLTDIV_F, arithmetic fault, floating divide by zero at PC=00001DED,PS
L=03C00000
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

MCC_AC_WAN4_MAP load_position_data               3768      00000605  00001DED
MCC_AC_WAN4_MAP main                             2852      00000369  000005B1
%NONAME-W-NOMSG, Message number 00000000
 ...... Failure in formatting DECnet Phase IV Autoconfiguration data.
 ... Exiting under error conditions
Press RETURN to exit>



    
T.RTitleUserPersonal
Name
DateLines
2367.1Is this reproducible?TOOK::FIGWERUlla Figwer LKG2-2/T2 x226-7858Wed Feb 19 1992 17:1416
Hello Paul,

The collection algorithm used by DNA4 Autoconfiguration has changed
since the field test software was released.  I am running a test now
on area 63 using the new software.  I'll let you know the results.

I am puzzled about the output you posted.  I would have expected the
software to stop collecting data after the first access violation.
i.e. not to continue with Q size 40, 39...

I am curious whether this problem is reproducible.  Could you try
collecting for area 63 again and let me know what happens?

Thank you.

Ulla Figwer
2367.2I'll try it againHAZARD::BAKERPaul Baker, UK Product and Technology Group - 844 3311Mon Feb 24 1992 08:4110
    Hi Ulla,
    
    re .1
    
    I was also surprised that the access violation didn't stop the
    autoconfig. I will try the operation again the next time I get on the
    system, which will be Wednesday, and let you know the results.
    
    Paul.
    
2367.3Same the second time aroundHAZARD::BAKERPaul Baker, UK Product and Technology Group - 844 3311Wed Feb 26 1992 15:538
    
    Ulla,
    
    I tried the autoconfig proceedure again for area 63 today and got
    exactly the same results.
    
    Paul.
      
2367.4Hidden areas are not supportedTOOK::FIGWERUlla Figwer LKG2-2/T2 x226-7858Wed Mar 11 1992 18:0518
    
    Hello Paul,
    
    Sorry for my late response.
    
    Area 63 is a hidden area, so when I test the software here with
    area 63, I am testing with a different area than you are trying
    to map.  My oversight.
    
    Altogether, the DECnet Phase IV Autoconfiguration does not work well
    when trying to map hidden areas.  When specifying collection criteria,
    hidden areas should be excluded from the search.
    
    Sorry I cannot give you a better answer.
    
    Ulla