Viewing Network Configuration with CONFIG_NET...

[Daiyu Hurst]

... doesn't seem to work with the demo systems. And the configuration file itself it binary, and so doesn't lend itself to the revealing of clues to the configuration (which was probably good idea back in the day):

OK, config_net
[CONFIG_NET Rev. 20.2.3 Copyright (c) 1987, Prime Computer, Inc.]


Create, Edit, Quit, Save, List, or Help? list
What object would you like to list
(ALL, RINGS, FDX, HDX, PDNS, NODES, <node or network name>): all


Create, Edit, Quit, Save, List, or Help? q
OK,

I want to be able to view it in preparation for creating a new network for my systems. The most significant change would be different node names; I don't anticipate any others at this time.

I do see that much of this information is viewable through DSM's various LIST_@@ commands.

Any and all help would be appreciated.

-Dai

[Andrew Marlow]

what does list_lan_nodes -host report?

[Jim Wilcoxson]

On Sunday, July 18, 2021 at 8:51:48 PM UTC-4, Daiyu Hurst wrote:
> ... doesn't seem to work with the demo systems.

Folks, before assuming things are broken, please keep in mind that back in the day there was usually a designated staff member(s) whose job was to configure these systems. Prime published *stacks* of documentation on how to configure and use them, but the software was not designed for non-technical users like software today usually is, so it's much harder to get anywhere without reading manuals. You can't easily just poke around and try things like with today's phones and tablets.

For CONFIG_NET, here is a clue:

OK, config_net -help

[CONFIG_NET Rev. 20.2.3 Copyright (c) 1987, Prime Computer, Inc.]

Usage: CONFIG_NET { [treename] [-TTP TTY/PT45/PST100/FOX/OWL] [-NO_WAIT] }
{ -HELP }

Let's try with a treename that doesn't exist:

OK, config_net jimmy>x

[CONFIG_NET Rev. 20.2.3 Copyright (c) 1987, Prime Computer, Inc.]

Not found. JIMMY>X (Config_Net)
ER!

Hmm... So to create a new config file that doesn't exist, you can't use a treename:

OK, config_net
CONFIG_NET Rev. 20.2.3 Copyright (c) 1987, Prime Computer, Inc.]


Create, Edit, Quit, Save, List, or Help? list
What object would you like to list
(ALL, RINGS, FDX, HDX, PDNS, NODES, <node or network name>): all

[NOTE: nothing is listed because the new config hasn't had anything added to it]

Create, Edit, Quit, Save, List, or Help? q

Try it with an existing config file:

OK, config_net primenet*>primenet.config

[CONFIG_NET Rev. 20.2.3 Copyright (c) 1987, Prime Computer, Inc.]


Create, Edit, Quit, Save, List, or Help? list
What object would you like to list
(ALL, RINGS, FDX, HDX, PDNS, NODES, <node or network name>): all

Node EM19
pre-rev-19.3
Ring RING1 Ring Node ID: 1
Access from node EM19
Node EM20 RFA/No-Validation Remote Login enabled
Node-Node password: PRIME
Node EM21 RFA/No-Validation Remote Login enabled
Node-Node password: PRIME
Node EM22 RFA/No-Validation Remote Login enabled
Node-Node password: PRIME
Node EM23 RFA/No-Validation Remote Login enabled
Node-Node password: PRIME
Node EM24 RFA/No-Validation Remote Login enabled
Node-Node password: PRIME
Node EM18 RFA/No-Validation Remote Login enabled
Node-Node password: PRIME

Node EM20
Compatibility Address: 99990407287461
Ring RING1
---MORE---

[Dennis Boone]

> what does list_lan_nodes -host report?

Note that a number of things like BRMS and DSM have significant Y2K
issues, and you may have to set your system date back to get them to
work.

De

[Daiyu Hurst]

On Saturday, August 7, 2021 at 6:06:57 AM UTC-4, Andrew Marlow wrote:
> On Monday, 19 July 2021 at 01:51:48 UTC+1, Daiyu Hurst wrote:

> what does list_lan_nodes -host report?

Andrew, it says this:

r! r list_lan_nodes
[LIST_LAN_NODES Rev. 23.4.0.R48 Copyright (c) 1993, Computervision Corporation]

** SHADOW ** There is no information satisfying the command line conditions.

And I guess here's why:

Er! help list_lan_nodes

LIST_LAN_NODES Displays all nodes on LAN300 networks
November 1989
LIST_LAN_NODES [ lan names ]
[ -HOST ]
[ -LTS ]

The LIST_LAN_NODES command displays information about the configured
LAN300 local area networks.

The "lan names" argument enables users to specify a list of LAN
names. Each node can be connected to more than one LAN300
network, each of which has a LAN name. Wildcarding is possible.
Options:

-HOST Allows you to specify that LAN300 hosts only are to be displayed.

-LTS Allows you to specify that only LTSs are to be displayed.

General SIM options are described in the general HELP information for SIM.
To display this information, type HELP SIM.

For further information, see the DSM User's Guide, and the NTS User's Guide.
(Q)uit (U)p (R)efresh (N)ext (P)revious (D)ive (X)refs (H)elp :More -->[N]

We don't have an emulated LAN300 adapter. We can only do Primenet Node Controller rings right now.

-Dai

[Daiyu Hurst]

On Saturday, August 7, 2021 at 10:19:13 AM UTC-4, Jim Wilcoxson wrote:
> On Sunday, July 18, 2021 at 8:51:48 PM UTC-4, Daiyu Hurst wrote:
> > ... doesn't seem to work with the demo systems.
> Folks, before assuming things are broken, please keep in mind that back in the day there was usually a designated staff
> member(s) whose job was to configure these systems. Prime published *stacks* of documentation on how to configure
> and use them, but the software was not designed for non-technical users like software today usually is, so it's much harder
> to get anywhere without reading manuals. You can't easily just poke around and try things like with today's phones and
> tablets.

Thanks, Jim. Didn't think anything was broken, I was pretty sure I wasn't holding my mouth the right where.

-Dai