TTA0 to Lat port settings..

[Volker Halle]

Nigel,

if the server is loaded via MOP and you can connect from the DECserver to your VMS system, the network seems to be o.k.

You need to set up the NODE name in your LATCP database:

$ MC LATCP SET PORT LTA888:/NODE=DS2D9B/PORT=PORT_2

Then check with Local> SHOW SERVER that the server name is set correctly. And check PORT_2 for access=remote. If you would plug in your VT to Port 2, then you should see on the screen, whatever you (successfully) copy to LTA888: from your VMS system.

Volker.

[Steve-Thompson]

Hi again Nigel

If you can connect to a LAT service SOMEWHERE on the net then thats a very good start. You have incoming connectivity.
We can assume then, your VT connects to the VAX in question!

So you should continue with the suggestions you already have to get the required "outging" connectivity.

Start with the LATCP checks, Port config, and the cable too!

Steven

[Ian Miller.]

Note that to do NCP CONNECT then your LAN has to allow the MOP-RC protocol. This is a different ethernet protocol type than LAT.

[Nigel Wright_1]

Another node boots the DECServer.

I have now defined the node in NCP and now get:-
> MC LATCP SHOW PORT LTA888:

Local Port Name: _LTA888: Local Port Type: Application (Queued)
Local Port State: Inactive
Connected Link:

Target Port Name: PORT_2 Actual Port Name:
Target Node Name: DS2D9B Actual Node Name:
Target Service Name: Actual Service Name:

>

We also have on the node with LTA88 try to do the comms link:-

> mc ncp sho node DS2D9B


Node Volatile Summary as of 11-JUN-2007 13:38:12

Node State Active Delay Circuit Next node
Links

4.209 (DS2D9B) 1.103 (xxxx)
>

> mc latcp sho port lta888

Local Port Name: _LTA888: Local Port Type: Application (Queued)
Local Port State: Inactive
Connected Link:

Target Port Name: PORT_2 Actual Port Name:
Target Node Name: DS2D9B Actual Node Name:
Target Service Name: Actual Service Name:

>

This happens:-

> mc ncp sho know cir


Known Circuit Volatile Summary as of 11-JUN-2007 13:40:13

Circuit State Loopback Adjacent
Name Routing Node

ISA-0 on

> mc ncp CONN VIA ISA-0 PHY ADDR 08-00-2B-1D-F6-2F
%SYSTEM-F-ILLCNTRFUNC, illegal ACP control function
>

Still trying to connect remotely as it is very difficult visit where it is as it is in a production area screened off to visitors.

Thanks Nigel.

[Steve-Thompson]

.... connect to the node that does the MOP load of the DS in question and try
$mc ncp conn via....
from there???

[Volker Halle]

Nigel,

defining the DECserver in the DECnet node database, does NOT help at all with LAT connectivity. Now that you've defined the node for LTA888:, what does the COPY file LTA888: command report ?

The ILLCNTRFUNC error may indicate, that you're running DECnet-OSI on that node. If so, you would need the SET HOST/MOP command.

Volker.

[Nigel Wright_1]

Thanks to everyone for their detailed replies - I am busy now, but I will get back to everyone about this tomorrow.

Many Thanks again for the excellent response.

Nigel.

[Dean McGorrill]

Hi Nigel,
if its phase V, connecting to the terminal server would look something like..

$ SET HOST/MOP/CIR=CSMACD-0/ADDRESS=08-00-2B-XX-XX-XX

..I used to go to the server to enter
port settings. I've included some dcl
that creates the commands. edit as needed
or use any of it, if helps you - Dean

[Nigel Wright_1]

Thanks for everyone for help I received in getting the ports working.