[HECnet] Re: Topology 28-Dec-2011

[Steve Davidson]

The file can handle multiple machines.   Just look at SLAVE::INFO.TXT or
LEGATO::INFO.TXT or even SGC::INFO.TXT.   Each of these files contains an
entire DECnet area of machines.

-Steve

-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, December 30, 2011 8:55 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011

On 2011-12-31 02.48, Steve Davidson wrote:
Johnny,

You are talking about the INFO.TXT file that is located in the default
DECnet directory.

Right. I even have one on MIM::
I just couldn't remember the name or format of the file, but figured 
someone else probably would. Little did I realized that others had 
already responded with the same information. :-)
The one "problem" with it, is that machines that aren't online also 
can't be queried for that file, so it might be a bit limited from that 
point of view.

	Johnny


-Steve


-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, December 30, 2011 8:46 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011

Someone (I don't remember who) had a suggestion a year or two ago,
that
machines should have a file in the default DECnet directory, with some
basic information about the node in a defined format, and the file
with
a defined name, so that anyone could easily extract and figure out
information about atleast running nodes.

Maybe that idea could be expanded upon?
Seems very tedious for people to constantly mail updates... Although I
could of course take additional information as I'm already keeping a
nodename database in Datatrieve. No big deal to add additional
information if we'd like that... Then I can generate any kind of
reports

based on this. As can others (if they can get remote Datatrieve to
work
against RSX.)

	Johnny

On 2011-12-30 15.59, hvlems at zonnet.nl wrote:
Rok, the spreadsheet that I distributed also has a sheet called
'hosts'.
I'm willing to expand that list though I have the basty feeling it's
going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a
relevant command but if so my ncl is *very* rusty and it seems I'm
pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char)
commands only tell you the os name. For vms it tells you what
platform.

The excel file contains this information for each node in a single
cell:

<address>-<name>-<hardware>-<os name>

Mark the hyphens: that way I can manipulate the csv file easily on
vms
with f$element ;-)

So anyone who mails me node data in the format listed gets data
included in the file.   What do you think?
Hans
-----Original Message-----
From: Rok Vidmar<rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To:<hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology
28-Dec-2011

    Sorry, I'm confused.   Is it your plan to keep a manually updated
list of
all of HECnet?   Are you looking for data on all known nodes, even
end
nodes
and ones that don't normally run 24x7?   And how much data do you
want
for
each node?   OS? Hardware type?   Geographic location?

    That's fine with me and I'm not complaining in the least if
that's
the
case!   OTOH, I thought you were making a list of the active routing
nodes,
which is an entirely different matter.

        Well, both. I generated list of active nodes and I believe it
will
not be too
    hard to manually update it from time to time.
        I can add whatever interesting information and I can add any
number of
    editors. Any volunteers? Hans?
    --
    Regards, Rok