On Thu, 3 Dec 2009 10:53:31 -0800, you wrote:
SHOW KNOWN AREAS is showing 9 areas, which is good. SHOW KNOWN NODES isn't
showing any new nodes though. And a TELL 1.400 SHOW KNOWN NODES isn't
showing my nodes yet. (I'm area 42 if you start seeing it in the node list).
I'd have to check the docs, but IIRC the node list doesn't get transmitted
to different areas. Area routers exchange among themselves infos about their
area reachability and answer yes or not to the reachability of any node
under their scope (i.e. in their area), but do not transfer the whole area
contents to other nodes.
To see new nodes in SHOW KNOWN NODES you'll have to do a COPY KNOWN NODES
from a node that already knows the nodes you are interested in, then you'll
see all the nodes on a reachable area marked as reachable (even if the
specific node is powered off).
But do not take for granted this whole theory. :-)
G.
Usual disclaimer: Excuse my English: it's not my native language.
The nodes that I have powered up at the moment are:
42.1 CANADA (the area router)
42.2 DAFFY
I was able to do a COPY KNOWN NODES FROM 1.400 which populated my node list. Is this something I need to do manually, or is this an automatic process that I don't have set up properly?
Ian.
On 2009-12-03, at 10:56 AM, Sampsa Laine wrote:
Well GORVAX can see area 42 but no nodes in it..
CHIMPY$ ncp tell gorvax show known areas
Known Area Volatile Summary as of 3-DEC-2009 19:57:20
Area State Circuit Next node to area
1 reachable 1.400 (GORVAX)
2 reachable TCP-0-0 2.17 (CHARON)
3 reachable TCP-0-0 2.17 (CHARON)
11 reachable QNA-0 11.2 (MAISA)
19 reachable QNA-0 19.11 (AGENA)
42 reachable QNA-0 42.1
51 reachable TCP-0-0 2.17 (CHARON)
59 reachable TCP-0-0 2.17 (CHARON)
60 reachable QNA-0 60.664 (PDXVAX)
On 3 Dec 2009, at 18:53, Ian McLaughlin wrote:
On 2009-12-03, at 10:49 AM, gerry77 at mail.com wrote:
At the moment I cannot remember if @SYS$MANAGER:NETCONFIG.COM asks something
about configuring a node as an area router, but I'm assuming that it doesn't
ask anything, or you wouldn't be here asking for help. :-)
As a starting point you may just type the following:
$ RUN SYS$SYSTEM:NCP
NCP> SET EXECUTOR STATE SHUT
NCP> DEFINE EXECUTOR TYPE AREA
NCP> EXIT
$ @SYS$MANAGER:STARTNET
If I'm not wrong, this should be enough to transform your node into an area
router; then you may want to revise your configuration to tune it better.
You are correct - NETCONFIG doesn't ask about level 1 or 2 - just whether you're a router or not. Your commands (which I'm sure I tried some time during the last 24 hours, but I'm not sure) followed by a reboot seems to have fixed it. Thanks!
SHOW KNOWN AREAS is showing 9 areas, which is good. SHOW KNOWN NODES isn't showing any new nodes though. And a TELL 1.400 SHOW KNOWN NODES isn't showing my nodes yet. (I'm area 42 if you start seeing it in the node list).
At least there's some connectivity. I'll keep working. Thanks for the help.
Ian.
---
Filter service subscribers can train this email as spam or not-spam here
Makes sense, it shows 42.1 as next node (but no name, which is legal though normally you d load names for each defined address).
paul
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Sampsa Laine Sent: Thursday, December 03, 2009 1:58 PM To: hecnet at Update.UU.SE Subject: Re: [HECnet] DECnet area router configuration
I lie - I can do a SET HOST to 42.1.
Sampsa
On 3 Dec 2009, at 18:56, Sampsa Laine wrote:
Well GORVAX can see area 42 but no nodes in it..
CHIMPY$ ncp tell gorvax show known areas
Known Area Volatile Summary as of 3-DEC-2009 19:57:20
Area State Circuit Next node to area
1 reachable 1.400 (GORVAX)
2 reachable TCP-0-0 2.17 (CHARON)
3 reachable TCP-0-0 2.17 (CHARON)
11 reachable QNA-0 11.2 (MAISA)
19 reachable QNA-0 19.11 (AGENA)
42 reachable QNA-0 42.1
51 reachable TCP-0-0 2.17 (CHARON)
59 reachable TCP-0-0 2.17 (CHARON)
60 reachable QNA-0 60.664 (PDXVAX)
On 3 Dec 2009, at 18:53, Ian McLaughlin wrote:
On 2009-12-03, at 10:49 AM, gerry77 at mail.com wrote:
At the moment I cannot remember if @SYS$MANAGER:NETCONFIG.COM asks something about configuring a node as an area router, but I'm assuming that it doesn't ask anything, or you wouldn't be here asking for help. :-) As a starting point you may just type the following: $ RUN SYS$SYSTEM:NCP NCP> SET EXECUTOR STATE SHUT NCP> DEFINE EXECUTOR TYPE AREA NCP> EXIT $ @SYS$MANAGER:STARTNET If I'm not wrong, this should be enough to transform your node into an area router; then you may want to revise your configuration to tune it better.
You are correct - NETCONFIG doesn't ask about level 1 or 2 - just whether you're a router or not. Your commands (which I'm sure I tried some time during the last 24 hours, but I'm not sure) followed by a reboot seems to have fixed it. Thanks!
SHOW KNOWN AREAS is showing 9 areas, which is good. SHOW KNOWN NODES isn't showing any new nodes though. And a TELL 1.400 SHOW KNOWN NODES isn't showing my nodes yet. (I'm area 42 if you start seeing it in the node list).
At least there's some connectivity. I'll keep working. Thanks for the help.
Ian.
I lie - I can do a SET HOST to 42.1.
Sampsa
On 3 Dec 2009, at 18:56, Sampsa Laine wrote:
Well GORVAX can see area 42 but no nodes in it..
CHIMPY$ ncp tell gorvax show known areas
Known Area Volatile Summary as of 3-DEC-2009 19:57:20
Area State Circuit Next node to area
1 reachable 1.400 (GORVAX)
2 reachable TCP-0-0 2.17 (CHARON)
3 reachable TCP-0-0 2.17 (CHARON)
11 reachable QNA-0 11.2 (MAISA)
19 reachable QNA-0 19.11 (AGENA)
42 reachable QNA-0 42.1
51 reachable TCP-0-0 2.17 (CHARON)
59 reachable TCP-0-0 2.17 (CHARON)
60 reachable QNA-0 60.664 (PDXVAX)
On 3 Dec 2009, at 18:53, Ian McLaughlin wrote:
On 2009-12-03, at 10:49 AM, gerry77 at mail.com wrote:
At the moment I cannot remember if @SYS$MANAGER:NETCONFIG.COM asks something
about configuring a node as an area router, but I'm assuming that it doesn't
ask anything, or you wouldn't be here asking for help. :-)
As a starting point you may just type the following:
$ RUN SYS$SYSTEM:NCP
NCP> SET EXECUTOR STATE SHUT
NCP> DEFINE EXECUTOR TYPE AREA
NCP> EXIT
$ @SYS$MANAGER:STARTNET
If I'm not wrong, this should be enough to transform your node into an area
router; then you may want to revise your configuration to tune it better.
You are correct - NETCONFIG doesn't ask about level 1 or 2 - just whether you're a router or not. Your commands (which I'm sure I tried some time during the last 24 hours, but I'm not sure) followed by a reboot seems to have fixed it. Thanks!
SHOW KNOWN AREAS is showing 9 areas, which is good. SHOW KNOWN NODES isn't showing any new nodes though. And a TELL 1.400 SHOW KNOWN NODES isn't showing my nodes yet. (I'm area 42 if you start seeing it in the node list).
At least there's some connectivity. I'll keep working. Thanks for the help.
Ian.
Well GORVAX can see area 42 but no nodes in it..
CHIMPY$ ncp tell gorvax show known areas
Known Area Volatile Summary as of 3-DEC-2009 19:57:20
Area State Circuit Next node to area
1 reachable 1.400 (GORVAX)
2 reachable TCP-0-0 2.17 (CHARON)
3 reachable TCP-0-0 2.17 (CHARON)
11 reachable QNA-0 11.2 (MAISA)
19 reachable QNA-0 19.11 (AGENA)
42 reachable QNA-0 42.1
51 reachable TCP-0-0 2.17 (CHARON)
59 reachable TCP-0-0 2.17 (CHARON)
60 reachable QNA-0 60.664 (PDXVAX)
On 3 Dec 2009, at 18:53, Ian McLaughlin wrote:
On 2009-12-03, at 10:49 AM, gerry77 at mail.com wrote:
At the moment I cannot remember if @SYS$MANAGER:NETCONFIG.COM asks something
about configuring a node as an area router, but I'm assuming that it doesn't
ask anything, or you wouldn't be here asking for help. :-)
As a starting point you may just type the following:
$ RUN SYS$SYSTEM:NCP
NCP> SET EXECUTOR STATE SHUT
NCP> DEFINE EXECUTOR TYPE AREA
NCP> EXIT
$ @SYS$MANAGER:STARTNET
If I'm not wrong, this should be enough to transform your node into an area
router; then you may want to revise your configuration to tune it better.
You are correct - NETCONFIG doesn't ask about level 1 or 2 - just whether you're a router or not. Your commands (which I'm sure I tried some time during the last 24 hours, but I'm not sure) followed by a reboot seems to have fixed it. Thanks!
SHOW KNOWN AREAS is showing 9 areas, which is good. SHOW KNOWN NODES isn't showing any new nodes though. And a TELL 1.400 SHOW KNOWN NODES isn't showing my nodes yet. (I'm area 42 if you start seeing it in the node list).
At least there's some connectivity. I'll keep working. Thanks for the help.
Ian.
On 2009-12-03, at 10:49 AM, gerry77 at mail.com wrote:
At the moment I cannot remember if @SYS$MANAGER:NETCONFIG.COM asks something
about configuring a node as an area router, but I'm assuming that it doesn't
ask anything, or you wouldn't be here asking for help. :-)
As a starting point you may just type the following:
$ RUN SYS$SYSTEM:NCP
NCP> SET EXECUTOR STATE SHUT
NCP> DEFINE EXECUTOR TYPE AREA
NCP> EXIT
$ @SYS$MANAGER:STARTNET
If I'm not wrong, this should be enough to transform your node into an area
router; then you may want to revise your configuration to tune it better.
You are correct - NETCONFIG doesn't ask about level 1 or 2 - just whether you're a router or not. Your commands (which I'm sure I tried some time during the last 24 hours, but I'm not sure) followed by a reboot seems to have fixed it. Thanks!
SHOW KNOWN AREAS is showing 9 areas, which is good. SHOW KNOWN NODES isn't showing any new nodes though. And a TELL 1.400 SHOW KNOWN NODES isn't showing my nodes yet. (I'm area 42 if you start seeing it in the node list).
At least there's some connectivity. I'll keep working. Thanks for the help.
Ian.
On Thu, 3 Dec 2009 10:16:27 -0800, you wrote:
with DECnet Phase IV installed. I've been going through every document I
can find, but I can't find anything that talks about setting up a level 2
(area) router. What do I have to do different from a normal (level 1)
router? I'd appreciate any pointers. Let me know if you'd like to see any
diagnostic output.
At the moment I cannot remember if @SYS$MANAGER:NETCONFIG.COM asks something
about configuring a node as an area router, but I'm assuming that it doesn't
ask anything, or you wouldn't be here asking for help. :-)
As a starting point you may just type the following:
$ RUN SYS$SYSTEM:NCP
NCP> SET EXECUTOR STATE SHUT
NCP> DEFINE EXECUTOR TYPE AREA
NCP> EXIT
$ @SYS$MANAGER:STARTNET
If I'm not wrong, this should be enough to transform your node into an area
router; then you may want to revise your configuration to tune it better.
HTH, :-)
G.
Hello All,
I'm trying to get my VAX network to connect to HECnet. Thanks to Johnny, we've got the bridge set up and there's packets going back and forth. The problem I'm having is configuring my area router. I'm running VAX VMS 7.3 with DECnet Phase IV installed. I've been going through every document I can find, but I can't find anything that talks about setting up a level 2 (area) router. What do I have to do different from a normal (level 1) router? I'd appreciate any pointers. Let me know if you'd like to see any diagnostic output.
Thanks,
Ian.
I forgot to add...
When I am confident of this new version I will send it to Johnny for his
review and possible inclusion of a "sanctioned" release. We will see...
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of gerry77 at mail.com
Sent: Sunday, November 29, 2009 14:26
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Boot VAX from Alpha host Infoserver?
On Fri, 27 Nov 2009 09:19:38 -0500, you wrote:
I would be willing to put my InfoServer-100 (with a six-stack CDROM
drive) up on the HECnet segment. With the new version of the bridge
that we are field testing it might be interesting to see what is
Will that new version be available on Johnny Billquist HECnet website as
an
official new release of the bridge or is a somewhat private fork?
possible. I have just purchased a (real not hobbyist) VMS V7.3-1 kit
for VAXen to try this out on - it should be here sometime next week.
Anyway, IIRC, even a hobbyist CD-ROM would work in the same way, I'm
right?
I can make the system available to any and all who would like to login
to it and play/learn/hack etc. When the VMS kit shows up I will send
additional mail.
Well, I'm very interested in the structure and contents of an InfoServer
system disk as it results from INITIALIZE and UPDATE SYSTEM commands.
When
you'll be ready to share, I hope we'll be able to arrange something to
let
me have a peek at that disk structure! 8-)
Thanks,
G.
My version splits out LAT from MOP, adds SCA (LAVc) and LAST
(InfoServer). The LAT/MOP split has been verified to work. LAVc
support is being tested now. The LAST support testing is pending. What
I have been doing is testing as the central hub. I do not pass along
*anything* new to Update.UU.SE - I don't want the whole of HECnet to
suffer the traffic if this version isn't up to the task.
We know that it successfully builds on NetBSD V04.00 (because that's
what I run) and Ubuntu Linux (32-bit version only) because that's what
has been running on the other end.
My InfoServer-100 (ISIS) will be up later today with an earlier version
of VMS (V5.x I think, depends on what I can find) just for testing.
If you wish to test this version of bridge.c (bridge-2.2.c) contact me
off-list.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of gerry77 at mail.com
Sent: Sunday, November 29, 2009 14:26
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Boot VAX from Alpha host Infoserver?
On Fri, 27 Nov 2009 09:19:38 -0500, you wrote:
I would be willing to put my InfoServer-100 (with a six-stack CDROM
drive) up on the HECnet segment. With the new version of the bridge
that we are field testing it might be interesting to see what is
Will that new version be available on Johnny Billquist HECnet website as
an
official new release of the bridge or is a somewhat private fork?
possible. I have just purchased a (real not hobbyist) VMS V7.3-1 kit
for VAXen to try this out on - it should be here sometime next week.
Anyway, IIRC, even a hobbyist CD-ROM would work in the same way, I'm
right?
I can make the system available to any and all who would like to login
to it and play/learn/hack etc. When the VMS kit shows up I will send
additional mail.
Well, I'm very interested in the structure and contents of an InfoServer
system disk as it results from INITIALIZE and UPDATE SYSTEM commands.
When
you'll be ready to share, I hope we'll be able to arrange something to
let
me have a peek at that disk structure! 8-)
Thanks,
G.
