- HECnet - lists @ Update

by ian＠platinum.net

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

15 years, 7 months

1
0
0 0

DECnet area router configuration

by Paul_Koning＠Dell.com

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.

15 years, 7 months

1
0
0 0

DECnet area router configuration

by sampsa＠mac.com

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.

15 years, 7 months

1
0
0 0

DECnet area router configuration

by sampsa＠mac.com

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.

15 years, 7 months

1
0
0 0

DECnet area router configuration

by ian＠platinum.net

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.

15 years, 7 months

1
0
0 0

DECnet area router configuration

by gerry77＠mail.com

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.

15 years, 7 months

1
0
0 0

DECnet area router configuration

by ian＠platinum.net

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.

15 years, 7 months

1
0
0 0