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

Conference noted::decnis

Title: DEC Network Integration Server (DECNIS)
Notice:Please read note 1 to use this conference effectively
Moderator:MARVIN::WELCH
Created:Wed Sep 18 1991
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3660
Total number of notes:15082

3627.0. "NCL compile error after upgrade V3.1 to V4.0?" by HTSC19::KENNETH () Wed May 07 1997 06:02

Hi,

One of my customer just upgrade their DECnis from V3.1 to V4.0 ECO4 in 
order to use the MPC III card.  

After the upgrade, the customer follow the post installation procedure on
the release notes, @sys$manager:nis$host_config update fix, then use the
NIS$DECNIS_CONFIG to create new ncl and new cmip.

However, while compiling the new generated ncl (configuration remain unchanged)
there are errors:

create session control known tower LOCAL:.AMHTD1 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-04:AA-00-04-00-04-10:20 } }    }
Create Node LOCAL:.x Session Control Known Tower LOCAL:.AMHTD1
 at 1997-05-07-09:57:46.42000 + 00:00 I 28147497.67107

Command failed due to:
 process failure
 

and 

!
!  Commands to set up MOP loop back on Device: L601-3-0
!
create mop circuit L601-3-0   type csma-cd
%SYSTEM-F-ABORT, abort
%DCL-W-SKPDAT, image data (records not beginning with "$") ignored
%SYSTEM-F-ABORT, abort

Does anyone knows why?  

Finially, the customer use the old ncl, generated from V3.1 and it pass, no
errors report.


Furthermore, one more question, when the customer type the following command
in the ncl> will get:

NCL>set routing phaseiv maximum hops 32

Node amhns1 Routing
at 1997-05-07-19:56:15.480+08:00Iinf

command failed due to:
 set list error

Characteristics
    invalid attribute value: PhaseIV Maximum Hops = 32.


Is there anyone knows why?


System information:

VAX VMS and DECnet/OSI V6.2.  DECnis 500 V4.0.4B.


Thanks for your help in advance.

Kenneth Leung
T.RTitleUserPersonal
Name		DateLines
3627.1Node synonyme vs full name ?LEMAN::SCHEIDEGGERRaymond @GEO - DTN 821-5236Wed May 07 1997 09:032
    1. For the control session tower, try to use the node synonyme instead
    of the full name.
3627.2Extra LOCAL:.AMHTD1 towers created by V4.0HTSC19::KENNETHThu May 08 1997 05:3558
Hi,

Thanks for your help.  I found that on the old ncl script (created by V3.1)
has no "create session control known tower LOCAL:.AMHTD1 towers"

NCL script created by DECnis V3.1:
---------------------------------

!
!       Create the Towers for Gateway Clients and Security Nodes
!
!
create session control known tower 4.4 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-04:AA-00-04-00-04-10:20 } }    -
    }
create session control known tower 4.5 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-04:AA-00-04-00-05-10:20 } }    -
    }





NCL script created by DECnis V4.0:
----------------------------------

create session control known tower AMHTD1 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-04:AA-00-04-00-04-10:20 } }    }
create session control known tower AMHTD2 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-04:AA-00-04-00-05-10:20 } }    }
create session control known tower LOCAL:.AMHTD1 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-04:AA-00-04-00-04-10:20 } }    }


The "LOCAL:.AMHTD1 towers" is created by the DECnis V4.0.  Why it need to
do so?  May I command out that part?


Any ideas on the other problems we encountered?

Thanks again for your help.

Kenneth Leung
3627.3Where does the LOACL:.AMHTD1 comes from?HTSC19::KENNETHMon May 19 1997 05:2230
Hi,

I have copied the customer file in mom$load and back to our system for
testing.  It is very strange.  If I create a brand new configuration
there is no problem.  However, using the customer's NCL and generate 
a new CMIP will get the same problem as the customer.  

When I delete the "Gateway Clients and Security Nodes" AMHTD1 and AMHTD2
using NIS$DECNIS_CONFIG.COM and add them again I can only see the AMHTD1.
Why???  Where is AMHTD2?  May I know which option from the NIS$DECNIS_CONFIG
generate the NCL command below?  Am I do something wrong?

!
!
!       Create the Towers for Gateway Clients and Security Nodes
!
!
create session control known tower LOCAL:.AMHTD1 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-04:AA-00-04-00-04-10:20 } }    }
!
!
!  Commands to set up MOP loop back on Device: L601-3-0

 
Thanks again for your help.

Kenneth Leung
3627.4More informationHTSC19::KENNETHWed May 21 1997 05:3133
Hi,

I don't know why, if I create a testing configuration on my testing system
running DECnis V4.0, there is no problem, no extract "LOCAL....."

create session control known tower hgcs24 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-16:AA-00-04-00-DC-5B:20 -
    } }  ,    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-16:AA-00-04-00-DC-5B:20 } }    }
create session control known tower htsc19 towers  -
    {  -
    { {%X0113},  -
    {DNA$ProtID$SessCtlV2  Number = 25 }, {dna$protid$nsp},  -
     {DNA$ProtID$RoutingV3  49::00-16:AA-00-04-00-EF-5B:20 } }    

However, with the customer's nis_xxx.dat, I can get an extra 
"create session control know tower Local:.." and this ncl generate the
CMIP error.

Is there anything wrong or should I need to raise an IPMT?

If anyone there are interested, you can copy the files below and try :

 HTSC19::DSA4:[FAL$SERVER]NIS_AMHNS1.DAT;12 and 
HTSC19::DSA4:[FAL$SERVER]NIS_HOST_CONFIG.DAT

Thanks for your help in advance

Kenneth Leung
3627.5What hardware is the VMS system?MARVIN::MUNSLOWFrom the pain come the dream, from the dream come the visionTue May 27 1997 07:0630
    
    Hi,
    
    	Some questions - What hardware is VMS running on? Alpha or VAX.
    
    	This matters since we use different cmip compilers.
    
    	What is the machine name the configurator is running on?
    	What event dispatcher sinks configured?
    	what gateway clients configured?
    	In upgrading from v3.1 to v4.0 was anything else upgraded on this
    	system? (VMS? etc)
    
    	
    	If the host configurator system is an Alpha Then LOCAL:. is not
    	going to be accepted by the compiler only 0:. or the the full
    	NSCTS will be accepted. If the LOCAL:. appeared because of the 
    	upgrade, on an Alpha system, then this is a bug so IPMT.
    
    	If the system is a VAX then local:. is fine and should be accepted
    	but the LOCAL:. NSCTS will have to exist in the dns cache, check by
    	the following command ( ncl> show dns clerk known name LOCAL all).
    
    	I shall go and have a look in the code to see if I can find
    	in the upgrade path the addition of The LOCAL:. session entry.
    
    
    	regards
    	Andrew Munslow