Dec-Net Plus setup

[robert70]

Hi,

I have an RX2800i running VMS8.4 with DECnet Plus installed -

I am trying to copy and backup data from an Alpha DS20E running VMS8.3 with DecNet Plus installed.

I have configure both boxes with the net$configure command as below...............

$ @net$configure
Copyright 2007 Hewlett-Packard Development Company, L.P.

        DECnet-Plus for OpenVMS network configuration procedure

    This procedure will help you create or modify the management scripts
    needed to operate DECnet on this machine. You may receive help about
    most questions by answering with a question mark '?'.

     Configuration last run by SYSTEM on 15-FEB-2012 12:47:48.35

        Configuration Options for Node EDDY

        [0]     Exit this procedure

        [1]     Perform an entire configuration
        [2]     Change naming information
        [3]     Configure Devices on this machine
        [4]     Configure Transports
        [5]     Configure Timezone Differential Factor
        [6]     Configure Event Dispatcher
        [7]     Configure Application database
        [8]     Configure MOP Client database
        [9]     Configure Cluster Alias
        [10]    Replace MOP Client configuration

* Which configuration option to perform?                 [1] :
* Enter the directory services to use on the system  [LOCAL] :
* Enter the full name for directory service LOCAL [LOCAL:.EDDY] :
* What is the synonym name for this node?             [EDDY] :
* What type of node (Endnode or Router)?           [ENDNODE] :
* Enter PhaseIV Address                                [1.1] :
%NET$CONFIGURE-I-SCANCONFIG, scanning device configuration - please wait

        Since you are using the BASIC option, if you answer YES to
        the next question, the NSP transport will be reconfigured
        using the default values which are:

        Maximum number of logical links:            200
        Maximum Transmit and Receive Window:         20
        Maximum Receive Buffers:                   4000
        Flow Control Policy:       Segment Flow Control

        If you intend to customize the transports, then use
        the ADVANCED option instead.

* Do you want to replace the existing NSP transport script? [NO] :

        Since you are using the BASIC option, if you answer YES to
        the next question, the OSI transport will be reconfigured
        using the default values which are:

        Maximum number of logical links:            200
        Maximum Transmit and Receive Window:         20
        Maximum Receive Buffers:                   4000
        OSI applications over TCP/IP:           Enabled
        DECnet applications over TCP/IP:        Enabled
        DECnet/OSI over TCP/IP interface(s):        ALL

        If you intend to customize the transports, then use
        the ADVANCED option instead.

* Do you want to replace the existing OSI transport script? [NO] :
%NET$CONFIGURE-W-NOPWIP, DECnet over IP requires the PWIP driver to be enabled
%NET$CONFIGURE-W-NODOMAIN, DECnet over IP requires DOMAIN in the directory services list
%NET$CONFIGURE-I-EVDFND, Event Dispatcher NCL script already exists
* Replace Event Dispatcher NCL script file?             [NO] :
%NET$CONFIGURE-I-APPLICATIONFND, application NCL script already exists
* Replace application script file?                      [NO] :
* Load MOP on this system?                              [NO] :
%NET$CONFIGURE-I-MOPCLIENTFND, MOP client NCL script already exists
* Replace MOP Client script file?                       [NO] :

        Summary of Configuration

 Node Information:

        Directory Services Chosen:      LOCAL
        Primary Directory Service:      LOCAL
        Local Full name:                LOCAL:.EDDY
        Node Synonym:                   EDDY
        Phase IV Address:               1.1
        Phase IV Prefix:                49::
        DECdns Node Type:       Clerk
        Session Control Address Update Interval:        10
        Routing Node Type:              ENDNODE
        Autoconfiguration of Network Addresses: Enabled
        Routing ESHello Timer:  600
        Routing ES Cache Size:  512

 Device Information:

        Device: EIA0 (EI/82558):
                Data Link name: CSMACD-0
                Routing Circuit Name:   CSMACD-0

        Device: EIB0 (EI/82558):
                Data Link name: CSMACD-1
                Routing Circuit Name:   CSMACD-1

        Device: EIC0 (EI/82558):
                Data Link name: CSMACD-2
                Routing Circuit Name:   CSMACD-2

        Device: EID0 (EI/82558):
                Data Link name: CSMACD-3
                Routing Circuit Name:   CSMACD-3

 Transport Information:

        NSP Transport:                    Configured
           Maximum number of logical links:     200
           Maximum Transmit and Receive Window: 20
           Maximum Receive Buffers:             4000
           Flow Control Policy:                 Segment Flow Control

        OSI Transport:                    Configured
           Maximum number of logical links:     200
           Maximum Transmit and Receive Window: 20
           Maximum Receive Buffers:             4000
           OSI applications over TCP/IP:        Enabled
           DECnet applications over TCP/IP:     Enabled
           DECnet/OSI over TCP/IP interface(s): ALL

        Congestion Avoidance Disabled

 Event Dispatcher Configuration:

        Sinks:            local_sink
        Outbound Streams: local_stream
        Phase IV Relay:   Enabled

* Do you want to generate NCL configuration scripts?   [YES] :
%NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIG
URE
%NET$CONFIGURE-I-NOTREPLACED, SYS$SPECIFIC:[SYSMGR]NET$APPLICATION_STARTUP.NCL; was not
replaced
%NET$CONFIGURE-I-NOTREPLACED, SYS$SPECIFIC:[SYSMGR]NET$EVENT_STARTUP.NCL; was not replac
ed
%NET$CONFIGURE-I-NOTREPLACED, SYS$SPECIFIC:[SYSMGR]NET$MOP_CLIENT_STARTUP.NCL; was not r
eplaced

sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.

Your default namespace nickname is LOCAL.

Your default namespace NSCTS is 08-00-2B-0D-C0-9D-5F-FA-A9-88-43-46-95-00.

Directory Service: Local name file

Modifying the node: LOCAL:.EDDY
Modifying the node towers

%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to LOCAL:.EDDY
%NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed

        Configuration Options for Node EDDY

        [0]     Exit this procedure

        [1]     Perform an entire configuration
        [2]     Change naming information
        [3]     Configure Devices on this machine
        [4]     Configure Transports
        [5]     Configure Timezone Differential Factor
        [6]     Configure Event Dispatcher
        [7]     Configure Application database
        [8]     Configure MOP Client database
        [9]     Configure Cluster Alias
        [10]    Replace MOP Client configuration

* Which configuration option to perform?                 [0] :
$

Eddy is the node name of the RX2800 and Dave, which was set up the same way as above,is the node name of the Alpha Server

Do I need to add in other config settings to get these 2 nodes to communicate to each other?

Copy and Backup commands not working eg from Eddy to Dave

$ copy dave::dkb1:[000000]*.* *.*
%COPY-E-OPENIN, error opening DAVE::DKB1:[000000]*.*; as input
-RMS-E-FND, ACP file or directory lookup failed
-SYSTEM-F-NOSUCHNODE, remote node is unknown

[Hoff]

Use the decnet_register tool to register the name and address of the DECnet-Plus hosts on each of the hosts.  

You'll want to read the DECnet-Plus introduction to get oriented with that product and (for a chapter with details of the decnet_register tool) the DECnet-Plus Network Management Manual from the DECnet-Plus documentation shelf. 

This decnet_register approach given you're likely not running DECdns and you're probably not connected to DECnet over IP nor to IP DNS.  But in any event, you'll need to become somewhat familiar with decnet_register.  (Put another way, there are other options for configuring the namespaces and acquiring the host names.  But for a small and unchanging network, a static configuration works fine.)

(The DECnet-Plus user interface is unfortunately far too hairly to wing-it; you'll end up reading the docs and running some web searches to get it to work.)

[robert70]

thanks steven yes the configure was done on both individual machines with seperate ip's

[robert70]

Thanks Hoff I will look into all this useful info now - I am trying to basically use Decnet Plus over TCPIP to allow backup and copy between boxes. Thanks - Will update you how I get on

[Duncan Morris]

Then don't forget to address these issues, reported by your configuration.....

%NET$CONFIGURE-W-NOPWIP, DECnet over IP requires the PWIP driver to be enabled
%NET$CONFIGURE-W-NODOMAIN, DECnet over IP requires DOMAIN in the directory services list

[robert70]

Thanks Duncan - sorted the issue with PWIP and Domain Cheers for pointing out

[robert70]

Thanks Steven - yes they are on the same Physical Network