As long as it is a layer two bridge with no layer 3 (router) capabilities for decnet then the should be no issue.
Area routers exist to connect machines in different decnet areas (level 2 inter area) but you also have Level 1 intra area routers for connecting nodes in the same area together across wide area links or multiple local area networks.
Bridging would be easiest and would allow LAT traffic to pass as well.
Mark
On 10 Oct 2013, at 09:19, Mark Wickens <mark at wickensonline.co.uk> wrote:
Even though I think I know the answer to this question, I'll ask it any way...
Is it OK to run machines that are in the same area on different subnets? For example, passing traffic between SLAVE:: and RIPLEY:: both on DECnet area 4 but on different subnets connected via a bridge?
I think it is and that the bridge is transparent, but for some reason in the back of my mind I have the concept of 'area router' and that doesn't fit with this model.
Thanks, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/#!/%40urbancamo
Even though I think I know the answer to this question, I'll ask it any way...
Is it OK to run machines that are in the same area on different subnets? For example, passing traffic between SLAVE:: and RIPLEY:: both on DECnet area 4 but on different subnets connected via a bridge?
I think it is and that the bridge is transparent, but for some reason in the back of my mind I have the concept of 'area router' and that doesn't fit with this model.
Thanks, Mark.
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/#!/%40urbancamo
On 10/10/2013 08:17, Daniel Soderstrom wrote:
Has anyone tries this? Running my Vaxstation non-stop reminds me how much noise these old drives make.
Has anyone tried SSD drives? Must be good for the PSU it terms of heat and current draw.
Daniel
Sent from my iPhone
There has been very little success with IDE to SCSI converters on this age of machine.
Remember also that even 4000/90 vintage VAXstations generally have an upper limit of 18GB.
I don't recall anyone even getting an IDE drive to work, let alone an SSD.
Would love to be proved wrong however! I'm surprised someone hasn't written a software based SCSI drive emulator the same way that you get floppy emulators.
Consider running the machine diskless, booted off the network with off-node disks.
Mark
--
http://www.wickensonline.co.ukhttp://hecnet.euhttp://declegacy.org.ukhttp://retrochallenge.nethttps://twitter.com/#!/%40urbancamo
Has anyone tries this? Running my Vaxstation non-stop reminds me how much noise these old drives make.
Has anyone tried SSD drives? Must be good for the PSU it terms of heat and current draw.
Daniel
Sent from my iPhone
NU2.COM gets around that, and other issues.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Cory Smelosky
Sent: Wednesday, October 09, 2013 5:14 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
On Wed, 9 Oct 2013, Ian McLaughlin wrote:
On Oct 9, 2013, at 1:56 PM, Sampsa Laine <sampsa at mac.com> wrote:
As far as I'm concerned, MIM has the canonical (and most up-to-date)
node database of HECnet. Is this assumption correct?
If it's not in MIM::, then it doesn't exist, as far as I'm concerned
;) (even if it's on my own network)
My nodes are often in MIM::. Sometimes multiple times!
Ian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Yes, that is why NU2.COM uses nodename.dat.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:56 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
On 2013-10-09 22:35, Steve Davidson wrote:
That can/will trash a cluster DECnet node database. Do NOT do it
that way. Others on this have already been burned when running
clusters.
I assume that is because you have nodename information locally that is
not known at MIM, in which case yes, you might get burned.
I try to register all my node name/number allocations with BQT, seems
like the sensible thing to do, have them in a central database
somewhere.
As far as I'm concerned, MIM has the canonical (and most up-to-date)
node database of HECnet. Is this assumption correct?
NU2.COM parses NETNODES.DAT for you already. That is how it works. You always have the latest DECnet database to work with.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Wednesday, October 09, 2013 4:50 PM
To: hecnet at Update.UU.SE
Cc: Hans Vlems
Subject: Re: [HECnet] Nodelist errors from MIM::
On 2013-10-09 22:27, Hans Vlems wrote:
$ mc ncp copy known nodes from sgc to both
Should give the same errors, assuming SGC has an up to date nodename
database.
The problem is when node names gets moved to new addresses. Old
information is not cleared out by an NCP COPY command, so you might get
duplicate information in that case.
There is a MIM::US:[DECNET]FIX.COM which will do the right thing on a
VMS system for you. And it gets updated whenever the nodename database
is updated, so VMS users could always use that, if they just want the
same nodename database as MIM.
An alternative is also to suck down MIM::US:[DECNET]NODENAMES.DAT and
parse it yourself, and do whatever you want to.
Johnny
*Van: *Steve Davidson
*Verzonden: *woensdag 9 oktober 2013 22:07
*Aan: *hecnet at Update.UU.SE
*Beantwoorden: *hecnet at Update.UU.SE
*Onderwerp: *RE: [HECnet] Nodelist errors from MIM::
$ Copy sgc::nu2.com *.*
$ @nu2
Be careful that your SCSSYSTEMID and DECnet node number are the same or
it will be a mess. You have been warned!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
Refresh my memory, how do I invoke that?
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:
Sampsa,
As long as your SCSSYSTEMID and your DECnet node number are in sync
you
can use NetUpdate from SGC:: or SG
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 2:57 PM
To: hecnet at Update.UU.SE
Subject: [HECnet] Nodelist errors from MIM::
When I tried to update my nodelist just now on CHIMPY, I got a few
errors in Area 9.
Any ideas?
--- SNIP ----
CHIMPY$ mcr ncp copy known node from mim to both
%NCP-W-INVPVA, Invalid parameter value , Address
%NCP-W-INVPVA, Invalid parameter value , Address
Remote node = 9.1 (GEWT)
%NCP-W-INVPVA, Invalid parameter value , Address
%NCP-W-INVPVA, Invalid parameter value , Address
Remote node = 9.2 (MANDY)
%NCP-W-INVPVA, Invalid parameter value , Address
%NCP-W-INVPVA, Invalid parameter value , Address
Remote node = 9.4 (MINDY)
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
I've never trashed anything with that command. Served me well.
Van: Steve Davidson
Verzonden: woensdag 9 oktober 2013 22:35
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] Nodelist errors from MIM::
That can/will trash a cluster DECnet node database. Do NOT do it that way. Others on this have already been burned when running clusters.
-Steve
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Hans Vlems
Sent: Wednesday, October 09, 2013 4:27 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
$ mc ncp copy known nodes from sgc to both
Van: Steve Davidson
Verzonden: woensdag 9 oktober 2013 22:07
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] Nodelist errors from MIM::
$ Copy sgc::nu2.com *.*
$ @nu2
Be careful that your SCSSYSTEMID and DECnet node number are the same or
it will be a mess. You have been warned!
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Wednesday, October 09, 2013 4:04 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist errors from MIM::
Refresh my memory, how do I invoke that?
sampsa <sampsa at mac.com>
mobile +358 40 7208932
On 9 Oct 2013, at 22:02, Steve Davidson <jeep at scshome.net> wrote:
> Sampsa,
>
> As long as your SCSSYSTEMID and your DECnet node number are in sync
you
> can use NetUpdate from SGC:: or SG
>
> -----Original Message-----
> From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
> Behalf Of Sampsa Laine
> Sent: Wednesday, October 09, 2013 2:57 PM
> To: hecnet at Update.UU.SE
> Subject: [HECnet] Nodelist errors from MIM::
>
> When I tried to update my nodelist just now on CHIMPY, I got a few
> errors in Area 9.
>
> Any ideas?
>
> --- SNIP ----
>
> CHIMPY$ mcr ncp copy known node from mim to both
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.1 (GEWT)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.2 (MANDY)
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
>
>
>
> %NCP-W-INVPVA, Invalid parameter value , Address
> Remote node = 9.4 (MINDY)
>
>
>
>
On Wed, 9 Oct 2013, Ian McLaughlin wrote:
On Oct 9, 2013, at 1:56 PM, Sampsa Laine <sampsa at mac.com> wrote:
As far as I'm concerned, MIM has the canonical (and most up-to-date) node database of HECnet. Is this assumption correct?
If it's not in MIM::, then it doesn't exist, as far as I'm concerned ;) (even if it's on my own network)
My nodes are often in MIM::. Sometimes multiple times!
Ian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Oct 9, 2013, at 1:56 PM, Sampsa Laine <sampsa at mac.com> wrote:
As far as I'm concerned, MIM has the canonical (and most up-to-date) node database of HECnet. Is this assumption correct?
If it's not in MIM::, then it doesn't exist, as far as I'm concerned ;) (even if it's on my own network)
Ian
