DECnet set host SCSSyetemID

[Michael LaRoche]

I have a systems that people are trying to do a set host scssystemid and for some of the systems it works others it doesn't. However they enter set host hostname and that connects through alright. Just wondering what could prevent certain systems from connecting via scsid?. tia.

[Michael LaRoche]

Forgot to mention that the from system is using DECnet osi 7.1

[Duncan Morris]

Hi Michael,

for a starter - Alpha or Vax?

Are the systems which are unreachable all in the same area?

Do the reachable and unreachable nodes use Phase IV or Phase V addressing?

What routers exist on the network, and are they routing Phase IV or V, or interphase?

Regards,

Duncan

[Volker Halle]

Michael,

there are various ways DECnet-OSI can come up with the NSAP address for a system given it's name (local namespace, DECdns, TCPIP DNS).

What you refer to as the 'SCSSYSTEMID' should be the DECnet area number and node number in a decimal representation (area*1024+node).

Try to find out, which 'numbers' don't work. Then try to connect using the area.node address (e.g. 1.1 instead of 1025). Does that work ?

Volker.

[Michael LaRoche]

Okay in answer, these are Alphas that system is using phase IV, the routers I believe have interphase running.

[Michael LaRoche]

Volker,

No that way doesn't work either.

Mike

[Aaron Sakovich]

Check the naming search path -- if it's trying to use TCP/IP (DNS) before DECnet for the host lookup, it might be getting confused on the hosts that don't work. It would be useful to compare the 2.

NCL Show session control naming search path

[Volker Halle]

Michael,

try to find out from DECnet_Register, how those nodes are defined. They may not be defined in the local namespace and implicitly use DECnet-over-IP (though DNS name resolution).

Volker.

[Michael LaRoche]

Aaron,

here's the ncl display:

TSCPSS> mcr NCL Show session control naming search path

Node 0 Session Control
at 2007-05-03-12:58:28.740-04:00Iinf

Characteristics

Naming Search Path =
{
[
Directory Service = Local ,
Template = "*"
] ,
[
Directory Service = Local ,
Template = "local:*"
] ,
[
Directory Service = Local ,
Template = "local:.tscpss.secure.*"
] ,
[
Directory Service = Domain ,
Template = "*"
] ,
[
Directory Service = Domain ,
Template = "*.my.com"
] ,
[
Directory Service = Domain ,
Template = "*.my2.com"
]
}

[Michael LaRoche]

Volker,

They appear in the decnet registry:
both below are from the TSCPSS system I'm trying to go from to the MYDEV1 system

The to system:

Node name: LOCAL:.MYDEV1
Phase IV synonym: MYDEV1

Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-02:AA-00-04-00-01-08:20 (2.1)

Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_OSItransportV1 (TP4)
DE C0
Routing: DNA_OSInetwork (CLNS)
49::00-02:AA-00-04-00-01-08:21 (2.1)


From SYSTEM:


Node name: LOCAL:.TSCPSS.SECURE.CHASE
Phase IV synonym: TSCPSS

Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-24:AA-00-04-00-09-90:20 (36.9)

[Aaron Sakovich]

Michael,

How does that output compare with a system where the scssystemid works? The output you shared does not look unusual at first glance.

Aaron

[Michael LaRoche]

Aaron,

The data looks about the same, here's a to system that it works fine with:


Node name: LOCAL:.dev1ax
Phase IV synonym: DEV1AX

Address tower protocol and selector values:
Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_NSP (NSP)
(no selector value)
Routing: DNA_OSInetwork (CLNS)
49::00-2C:AA-00-04-00-66-B0:20 (44.102)

Session: DNA_SessionControlV2 (SC2)
00 13
Transport: DNA_OSItransportV1 (TP4)
DE C0
Routing: DNA_OSInetwork (CLNS)
49::00-2C:AA-00-04-00-66-B0:21 (44.102)

[Aaron Sakovich]

Michael,

You said "it doesn't work" (paraphrasing). What error and/or symptoms does the user see when it doesn't work? Does it fail immediately, or timeout? Is there a message returned?

Aaron

[Volker Halle]

Michael,

to the system, which doesn't work, can you try to connect with both NSP and OSI transport:

$ set host net$490002AA000400010820 ! NSP

$ set host net$490002AA000400010821 ! TP4

Volker.

[Michael LaRoche]

It fails immediately with:

%SYSTEM-F-UNREACHABLE, remote node is not currently reachable


Volker I tried both and they return the above error too.

[Andreas Vollmer]

Bonjour Michel,

Some questions:
- Did this setup ever worked?
- If yes, when occured this problem?
- Do you know about changes within the network?
- Do you know if CISCO routers involved?
- Does these router do the DECnet routing?
- Do you use DECdns?
- Do you use DECnet of IP?

Could be there a problem with the routing?
Or with the local DECnet database (where you register all nodes including the node it self)?
The system MYDEV1 is using the address 2.1 and TSCPSS 36.9 and DEV1AX is using 44.102.

Try to flush the session control cache:
MCR NCL FLUSH SESSION CONTROL NAMING CACHE ENTRY "*"
Then try again to establish a DECnet connection.

Volker, what do you think?

Regards
Andreas

[Volker Halle]

Michael,

this seems to be a complex network involving area routing.

If the information provided is complete and correct, I cannot currently imagine, why a SET HOST node works, whereas a SET HOST x.x doesn't.

Does a SET HOST LOCAL:.MYDEV1 work from TSCPSS ?

Volker.

[Michael LaRoche]

Volker,

I tried the LOCAL:.Mydev1 same result

%SYSTEM-F-UNREACHABLE, remote node is not currently reachable

[Volker Halle]

Michael,

this seems to imply, that SET HOST MYDEV1 may not be using DECnet transport, but DECnet-over-IP !

Try $ SET HOST MYDEV1 and login. Then issue $ UCX SHOW DEV - do you see a connection to local port 399 from the IP address of TSCPSS ?

Volker.

[Michael LaRoche]

Volker,

Here's what I see for Port 399

bg6822 STREAM 399 49505 176.26.116.9

[Volker Halle]

Michael,

is 176.26.116.9 the IP address of TSCPSS ? Does UCX SHOW DEV on TCPSS show an outgoing session from local port 49505 ?

If not, it could be someone else using DECnet-over-IP to MYDEV1 currently...

Volker.

[Michael LaRoche]

Volker,

That is the IP for TSCPSS.

I checked on tscpss and see:

bg9009 STREAM 49507 399 10.17.10.63

which is the IP of mydev1

[Volker Halle]

Michael,

so this explains, why you cannot SET HOST scssystemid or SET HOST x.x to mydev1, as this system only seems to be reachable via DECnet-over-IP and NOT via DECnet routing !!!

When you use the address, DECnet has not chance but to use NSP or TP4. If you use the name, DECnet - maybe after trying NSP and TP4 - can also transparently use DECnet-over-IP.

Problem solved.

Except if you think, that DECnet routing should work between those 2 nodes. Then you have to find all the routers involved in the path between those 2 nodes.

Volker.

[Hoff]

Are these (working) node names logical names?

[Michael LaRoche]

The problem is with the routers between the systems. Thanks to all who responded and sorry to be assigning points late.