DECNET how to change adjacent node

[Juan M. Lazaro]

Hi to all,

There is any way to change the adjacent node in a decnet network?

My executor configuration is:

NCP>sho exec char


Node Volatile Characteristics as of 16-AUG-2022 09:55:50

Executor node = 30.107 (NODO1)

Identification = HP DECnet for OpenVMS Alpha
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 256
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = routing IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Segment buffer size = 1498
Buffer size = 1498
Default access = incoming and outgoing
Pipeline quota = 14980
Alias maximum links = 32
Path split policy = Normal
Maximum Declared Objects = 31

And the circuit information is :

NCP>sho k circ char


Known Circuit Volatile Characteristics as of 16-AUG-2022 09:50:36

Circuit = EIA-0

State = on
Service = enabled
Designated router = 30.107 (NODO1)
Cost = 8
Maximum routers allowed = 33
Router priority = 64
Hello timer = 15
Type = Ethernet
Adjacent node = 30.10 (NODO3)
Listen timer = 45

I want to change the adjacent node from 30.10 (NODO3) to 30.20 (NODO4), I am looking for information on how to do that, but I don't see the way, anyone can help me?

Many thanks in advance.

Juan

[Robert Gezelter]

Juan,

I may not be understanding your question, but DECnet routing works dynamically, there is no need to declare a node in advance.

In DECnet, node names are essentially conventions (with the exception of how various applications use them, or their doppelgangers, eg. SCSNODE).

That said, there are very few situations where you would need to declare a node number in advance, most network related functionality is dynamic.

What is the precise reason for wanting to change the node name? What exactly is being done?

- Bob Gezelter, http://www.rlgsc.com

[Juan M. Lazaro]

Hi Robert,

The problem is that we hav 6 Open VMS hosts, 3 of them are in place A, and other 3 in place B, we hav an application running on them, and the communication is via decnet, the problem is that one of the nodes in place A, have an adjacent node of place B, and the application has some timeout errors, for those I want try to put an adjacent noce prom place A.

Excuse my english, hope you understand it.

Many thanks.
Juan

[Volker Halle]

Juan,

the MC NCP SHOW KNOWN CIRC CHAR command you issued on a DECnet phase IV routing node should show ALL adjacent DECnet nodes in the LAN segment associated with the circuit, from which the local node has received DECnet hello messages.

There is also a designated router shown on your LAN (with address 30.107), make sure that it can see the desired nodes (mc ncp tell 30.107 show known nodes).

You're running DECnet IV on an OpenVMS Alpha system configured as a routing node. As far as I remember, DECnet IV on OpenVMS Alpha only supports to be run as END node.

Volker.

[Robert Gezelter]

Juan,

First, a small note. The time of year setting is clearly incorrect. Look at the year.

What is your actual network topology? To be specific, what is visible on the ethernet segment that EIA-0 is connected to.

- Bob Gezelter, http://www.rlgsc.com

[Juan M. Lazaro]

Hi Volker, the output I print is from the TEST environment, Robert, for those we have a different year, because I haven't direct connection with the production environment, I must go to another place to type the commands, get the output in a flash memory and copy/paste here, anyway I attached a file with the production outputs.

The configuration is:

PLACE A
SYS11A
SYS11B
SYS11D

PLACE B
SYS11C
SYS11E

I have OpenVMS 8.2

Thanks in advance...

Juan

[Volker Halle]

Juan,

this looks straightforward: 5 DECnet nodes on the LAN(s) connected via EIA-0 and EIA-2. All visible from the local node and reachable from the designated router. This is the test environment. Are EIA-0 and EIA-2 connected to the SAME network segment or different/parallel LAN segments ?

Do you expect your production environment to look the same ?

How are the nodes located (at which sites) in your production environment ? From your initial output, it looks like only NOD01 and NOD03 can see each other via the LAN. Are those 2 nodes at the same site ? Are the other 3 nodes at the 'other' site ? Can they see NOD01 and NOD03 - I assume no.

Volker.

[Volker Halle]

JUan,

after re-reading your posts, I realize that I might have mixed up the test and production environment.

SYS11x = production - everything o.k.
NOD0x = test - problem between sites

Please confirm.

Volker.

[Juan M. Lazaro]

Hi Volker, EIA-0 and EIA-2 are diferent LAN segments.

Forgot the first information I post, that was the test environment, the last is the correct environment, I have the problem in production mode and the configuration is how I post before:

PLACE A
SYS11A
SYS11B
SYS11D

PLACE B
SYS11C
SYS11E

Thanks...

Juan

[Juan M. Lazaro]

Yes Volker, SYS11X is the production mode and where I have the problem.

Thanks again.

Juan