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

Conference noted::dnu_osi

Title:DECnet/OSI for {ULTRIX,OSF/1}
Notice:Indicate version and platform when writing...see #2 for kits
Moderator:BULEAN::CARR
Created:Wed Sep 25 1991
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2187
Total number of notes:10469

2160.0. "dna_decdns_createns fails V3.2B" by CHEFS::DAVIDSONS () Wed Apr 09 1997 20:46

    Following script shows that dna_decdns_createns fails.
    This sequence of 'decnetsetup advanced' followed by
    'dna_decdns_createns' on DNS server worked OK with DNU V3.2A
    
    (DNU V3.2A subsets were deleted before V3.2B installed, also
    contents of /var/dss/dns removed)
    
    Any ideas?
    
    Stuart.
    
    Environment: DU V3.2D, DNU V3.2B
    
omc4# uname -a
OSF1 omc4 V3.2 41 alpha
omc4# decnetsetup advanced

	DECnet/OSI for Digital UNIX V3.2B-0
	DECnet/OSI Configuration Procedure.

There will be a pause while this procedure gathers some
information from your system.

Copyright (c) Digital Equipment Corporation. 1993-1995. All Rights Reserved.

What is the Phase V node name? [LOCAL:.osi.ods_lan.omc4]:

What is the Phase IV compatible synonym? [omc4]: ""

What is the Phase IV compatible node address? [0]:

Will this system autoconfigure its network addresses? [n]:
Enter a zero (0) if you have less than three NET values to enter.

This system's current Node ID is: 08-00-2b-9b-bb-5c

Enter a Network Entity Title [47:0027:814e4c44014459594f4f:4f4d434f0011:00]
(Enter 0 to continue):

Enter a Network Entity Title [0]
(Enter 0 to continue):

There will be a pause while this procedure determines what network
controllers are available on the system.

Enter the list of communications devices on which you will be
running the DECnet Phase V software.  If there is more than
one device, separate them by spaces.  [ln0 fta0 ln1 ]: fta0

Will this system be configured as a DTSS clerk only? (y/n) [y]:

Will this system be configured as a DECnet-Internet Gateway? (y/n) [n]

Do you want to configure DECnet over TCP/IP? [y]: n

Do you want this system to service MOP requests? (y/n) [n]

Please review the following information which you have supplied, and if
it is correct enter "Continue", which will start the DECnet software
and complete the configuration.  If there is incorrect information, or
you wish to change a particular value, enter "Restart" to begin the
setup again.  If the information is correct, but you do not wish to
complete the configuration at this time, enter "Stop".  This will save
the values you have entered, which will appear as defaults when you rerun
this procedure.  You may enter "Quit" to abort this procedure, without
saving the answers.

Nodename:		LOCAL:.osi.ods_lan.omc4
Node Synonym:
Network Devices:	fta0
Set of NET's:
			47:0027:814e4c44014459594f4f:4f4d434f0011:00
This system will be a DTSS clerk.
This system will use the Local Namespace

Do you wish to complete this DECnet/OSI configuration? [continue]
Modifying defaults file.
Creating Initialization NCL scripts
Modifying /sbin/decnetstartup
Updating /var/dna/dna_version
Modifying /sbin/decnetshutdown
Event Logging ...

Configuring "CTF Collector Components " (CTABASE150)

Ensuring all underlying dependencies are configured.
++++++++++++++++++++++++++++++

Configuring "Digital UNIX WAN Utilities " (ZZAUTIL130)
ZZAUTIL130 configured as loadable.
------------------------------
CTABASE150 configured as loadable.
Creating /var/dss/dns/dns-names

Starting DECnet/OSI

ncl>> create fddi

Node 0 FDDI
AT 1997-04-09-18:13:28.131+02:00I-----

FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class

REASON: Already Exists
Description: Already Exists


ncl>> create fddi station fddi-1 communication port fta0

Node 0 FDDI Station fddi-1
AT 1997-04-09-18:13:28.173+02:00I-----

FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class

REASON: Already Exists
Description: A Station with this name already exists

Datalink ... Routing ... NSP ... OSI Transport ... Session Control ...

Local Namespace successfully configured.
Creating /var/dss/dns/dns-names
Node name reset to LOCAL:.osi.ods_lan.omc4
Setting Session Control attributes
DTSS ... Node Enabled ... Event Logging
Event Logging ...

DECnet/OSI RFC 1006 (OSI over TCP) has been enabled.

rfc1006setup completed successfully.


Node 0 OSAK
AT 1997-04-09-18:14:10.649+02:00I-----

FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class

REASON: Entity Exists
Description: OSAK entity already exists

 FTAM... VT... done.
Initializing the Local Namespace
Using the existing database /var/dna/dna_local_name_database_nam.dir

Directory Service: Local name file

Registering the node: local:.osi.ods_lan.omc4



The configuration of DECnet/OSI is completed.

You can test DECnet functionality with the utility /usr/sbin/dnet_check .
This performs various local and remote functions, and requires an
account (and password) on this system and one other DECnet node.
After verifying that the system is operating properly with DECnet
installed you may wish to remove the following saved files:
    - /var/dna/scripts/start_*.ncl.sav[n]

The DECnet/OSI for Digital UNIX (formerly DEC OSF/1) on-line release notes may
be found at:

	/usr/share/dna/DECnet_release_notes

Note: This node has been configured to use the Local Namespace.
      If you wish to add, modify, or delete a node or its
      associated addressing information, you should use the
      utility /usr/sbin/decnet_register to add or change definitions.
      You may also use the /usr/sbin/update_nodes utility
      to copy a Phase IV nodes database or Phase V LNO load
      file from a remote system, as in the following example:

            /usr/sbin/update_nodes -dlocal 4.1002

      This command will copy a DECnet address file from the remote
      system, and automatically populate the local naming file.
      Please refer to the installation guide for further details.

You may run /usr/sbin/osiapplsetup to configure the
OSI Applications (FTAM and Virtual Terminal).
CTF: Error, another CTF Daemon is already running

decnetsetup completed successfully.

omc4# ncl sjpoho node 0

Node 0
AT 1997-04-09-18:14:23.386+02:00I-----

Identifiers

    Name                              = LOCAL:.osi.ods_lan.omc4
    Address                           =
        {
            (
                [ DNA_CMIP-MICE ] ,
                [ DNA_SessionControlV3 , number=19 ] ,
                [ DNA_OSItransportV1 , 'DEC0'H ] ,
                [ DNA_OSInetwork ,
47:0027:81-4E-4C-44-01-44-59-59-4F-4F:4F-4D-43-4F-00-11:21
(LOCAL:.osi.ods_lan.omc4) ]
            ) ,
            (
                [ DNA_CMIP-MICE ] ,
                [ DNA_SessionControlV3 , number=19 ] ,
                [ DNA_NSP ] ,
                [ DNA_OSInetwork ,
47:0027:81-4E-4C-44-01-44-59-59-4F-4F:4F-4D-43-4F-00-11:20
(LOCAL:.osi.ods_lan.omc4) ]
            )
        }

omc4# dna_decdns_createns


There will be a pause while this procedure gathers some
information from your system.

  Do you wish to create a new namespace? (y/n) [n] y

The namespace nickname is the name given to the collection of
data stored among the distributed DECdns servers.  Please enter
the name of the DECdns namespace you wish to create.

  What is your namespace nickname? [No Default]: MADAP_ONL

The clearinghouse contains all the data stored by the DECdns server.
It must be given a name, and this name will itself be stored in
the namespace as an object in the root directory.  You may accept
the default clearinghouse name offered below, or enter a namee
of your own choosing.

  Enter a name for the clearinghouse: [root_ch]

Please review the following information which you have supplied, and if
it is correct enter "Continue", which will invoke the DECdns server
software and create the namespace.  If there is incorrect information,
or you wish to change a particular value, enter "Quit" and rerun this
procedure.

Namespace Nickname:		MADAP_ONL

Clearinghouse Name:		root_ch

  Do you wish to complete this configuration? [continue]
Creating the MADAP_ONL namespace.

Your default namespace nickname is MADAP_ONL.

Create Group error: Cannot display detailed error text.

dnsCreateGrp call failed - please submit an SPR.
Arch error = 536864024, Local status = 0


Having created a new namespace, the initial directories will be
created.  You will be informed of any additional tasks to perform,
which can be done after this procedure is completed.
Disabling and re-enabling the dns server.  May take a couple minutes.

Create the initial namespace directories.
Press Control-D at any question to cancel the initialization.

* Will any Phase IV nodes participate in the network [y/n, Def=y]: n

The DECdns namespace groups and directories will now be created.  This might
take up to 4 minutes or more, depending on the speed of the DECdns
server system and the amount of traffic on the network.

Creating the MADAP_ONL:.DNA_Registrar group.
Error on entity: MADAP_ONL:.DNA_Registrar
Unable to communicate with any DECdns server
Function: dnsCreateGrp

Creating the MADAP_ONL:.DNA_BackTranslation directory.
Error on entity: MADAP_ONL:.DNA_BackTranslation
Unable to communicate with any DECdns server
Function: dnsCreateDir

Note - If the directory creation error was due to insufficient access
       rights, ensure that the correct access is set on both the parent
       directory and on the appropriate clearinghouse, using the DECdns
       control program commands:

           add directory access
           add clearinghouse access

Creating the MADAP_ONL:.DNA_NodeSynonym directory.
Error on entity: MADAP_ONL:.DNA_NodeSynonym
Unable to communicate with any DECdns server
Function: dnsCreateDir

Note - If the directory creation error was due to insufficient access
       rights, ensure that the correct access is set on both the parent
       directory and on the appropriate clearinghouse, using the DECdns
       control program commands:

           add directory access
           add clearinghouse access

Creating the MADAP_ONL:.DTSS_GlobalTimeServers directory.
Error on entity: MADAP_ONL:.DTSS_GlobalTimeServers
Unable to communicate with any DECdns server
Function: dnsCreateDir

Note - If the directory creation error was due to insufficient access
       rights, ensure that the correct access is set on both the parent
       directory and on the appropriate clearinghouse, using the DECdns
       control program commands:

           add directory access
           add clearinghouse access


DECdns namespace initialization for DECnet use is complete.

* Press RETURN to continue

If this is the first time you have initialized the namespace for DECnet
use, use decnet_dns_register to:

  - Create any directories you need for node names that should be registered
    immediately, according to your transition plan.  This includes the node
    you are currently running on.

  - Register the local node.

* Press RETURN to continue

Continue to use decnet_dns_register to:

  - Create any additional directories you need for node names, as you add
    new nodes to the network according to your transition plan.

  - Register new nodes as they are brought up on the network.

  - Add members to the MADAP_ONL:.DNA_Registrar access control group.

Additionally, you can use the DECdns control utility to:

  -  Add specific access control to individual directories, objects, and
     soft links.

  -  Create replicas of directories.

* Press RETURN to continue

The following creations failed:

     Group:       MADAP_ONL:.DNA_Registrar
     Directory:   MADAP_ONL:.DNA_BackTranslation
     Directory:   MADAP_ONL:.DNA_NodeSynonym
     Directory:   MADAP_ONL:.DTSS_GlobalTimeServers

* Press RETURN to continue


dna_decdns_createns completed successfully.

omc4#
T.RTitleUserPersonal
Name
DateLines
2160.1QAR 479CHEFS::DAVIDSONSFri Apr 11 1997 19:021