Steve Davidson has a few scripts which will detect an IP address change, reconfigure the link and reboot the system. Assuming the IP only changes 'once in a while' this is a fairly painless solution.
Mark.
On 27/12/11 12:08, Peter Lothberg wrote:
On 26/12/2011 18:39, Mark Benson wrote:
On 26 Dec 2011, at 16:00, Bob Armstrong wrote:
I assumed (perhaps stupidly) that as long as Chrissie's machines are
bridged onto HECnet somewhere using Johnny's bridge,
She's not using the bridge, though. ROOSTA has a multinet connection to
LEGATO (which I don't mind, but as Johnny said, isn't going to work).
Okay, well STAR69 has Multinet on it but as for tunnelling between them
I ain't got a clue, chief, and again I can't guarantee 100% uptime on the
link if it is opened.
So can you set up a multinet link to chrissie.homelinux.net (warning IP
address may change ... though it doesn't do it very often and Steve
Davidson can let you know when it does) and let me know your IP address
and I'll set up a multinet link here. That should do.
If it does down sometimes we'll just have to live with the consequences ;-)
Chrissie
Someone had "magic" to deal with changing adresses?
Sure I can set up a link, and I'll suggest metric 5..
The VAXen with multinet is 192.108.200.211.
-P
On 27/12/2011 12:36, Mark Benson wrote:
On 27 Dec 2011, at 12:00, Chrissie Caulfield wrote:
$ multinet conf/decnet
MultiNet DECNET Circuit Configuration Utility V5.2(10)
[Reading in configuration from MULTINET:DECNET-CIRCUITS.COM]
DECNET-CONFIG>add
[Adding new configuration entry for DECnet circuit "TCP-0-3"]
Destination IP Address: 80.6.148.150
DECnet circuit cost: [1] 3
DECnet hello timer (in seconds): [300]
[TCP-0-3 => 213.123.127.24 (Cost=3, Hello Timer=300)]
DECNET-CONFIG>^Z
[Writing configuration to MULTINET:DECNET-CIRCUITS.COM]
$ reboot
Okay, done. Assuming that was the right IP, we'll see what
happens :)
Hmm nothing is showing up at my end. Doe you have a firewall blocking
port 700/udp ?
Though I think you said you already had multinet running to other nodes,
so that sounds unlikely.
Chrissie
On 27 Dec 2011, at 12:00, Chrissie Caulfield wrote:
$ multinet conf/decnet
MultiNet DECNET Circuit Configuration Utility V5.2(10)
[Reading in configuration from MULTINET:DECNET-CIRCUITS.COM]
DECNET-CONFIG>add
[Adding new configuration entry for DECnet circuit "TCP-0-3"]
Destination IP Address: 80.6.148.150
DECnet circuit cost: [1] 3
DECnet hello timer (in seconds): [300]
[TCP-0-3 => 213.123.127.24 (Cost=3, Hello Timer=300)]
DECNET-CONFIG>^Z
[Writing configuration to MULTINET:DECNET-CIRCUITS.COM]
$ reboot
Okay, done. Assuming that was the right IP, we'll see what
happens :)
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
On 27/12/2011 10:57, Mark Benson wrote:
On 27 Dec 2011, at 10:43, Chrissie Caulfield wrote:
So can you set up a multinet link to chrissie.homelinux.net (warning IP
address may change ... though it doesn't do it very often and Steve
Davidson can let you know when it does) and let me know your IP address
and I'll set up a multinet link here. That should do.
I honestly haven't the first clue how.
My IP is 213.123.127.24 if you want to set your end up.
It's pretty easy, just type the following on the VAX when logged in as SYSTEM (typing is in bold, if you can see that)
$ multinet conf/decnet
MultiNet DECNET Circuit Configuration Utility V5.2(10)
[Reading in configuration from MULTINET:DECNET-CIRCUITS.COM]
DECNET-CONFIG>add
[Adding new configuration entry for DECnet circuit "TCP-0-3"]
Destination IP Address: 80.6.148.150
DECnet circuit cost: [1] 3
DECnet hello timer (in seconds): [300]
[TCP-0-3 => 213.123.127.24 (Cost=3, Hello Timer=300)]
DECNET-CONFIG>^Z
[Writing configuration to MULTINET:DECNET-CIRCUITS.COM]
$ reboot
Chrissie
On 26/12/2011 18:39, Mark Benson wrote:
On 26 Dec 2011, at 16:00, Bob Armstrong wrote:
I assumed (perhaps stupidly) that as long as Chrissie's machines are
bridged onto HECnet somewhere using Johnny's bridge,
She's not using the bridge, though. ROOSTA has a multinet connection to
LEGATO (which I don't mind, but as Johnny said, isn't going to work).
Okay, well STAR69 has Multinet on it but as for tunnelling between them
I ain't got a clue, chief, and again I can't guarantee 100% uptime on the
link if it is opened.
So can you set up a multinet link to chrissie.homelinux.net (warning IP
address may change ... though it doesn't do it very often and Steve
Davidson can let you know when it does) and let me know your IP address
and I'll set up a multinet link here. That should do.
If it does down sometimes we'll just have to live with the consequences ;-)
Chrissie
Someone had "magic" to deal with changing adresses?
Sure I can set up a link, and I'll suggest metric 5..
The VAXen with multinet is 192.108.200.211.
-P
Isn't the problem similar to what happens if there would have been two active bridges between two ethernet segments?
------Origineel bericht------
Van: Peter Lothberg
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] ROOSTA routing problem
Verzonden: 27 december 2011 18:43
Hmmm.. LEGATO can't talk to ROOSTA ("remote node not currently reachable")
even though there's a direct Multinet link to ROOSTA (and yes, the link is
UP and working).
I think the problem is that ROOSTA is in area 6, and the area router for 6
is STAR69. Trouble is, STAR69 doesn't have a path to ROOSTA and doesn't
know how to send it packets.
(It doesn't help that STAR69 still thinks that ROOSTA is 3.34 - it moved
to 6.134 a while ago - but I don't think that's causing the problem.)
Multinet links metric 5
Bridged ethernet metric 10
Set all multinet-link nodes Level2-Area-Routers
--P
On 27 Dec 2011, at 10:43, Chrissie Caulfield wrote:
So can you set up a multinet link to chrissie.homelinux.net (warning IP
address may change ... though it doesn't do it very often and Steve
Davidson can let you know when it does) and let me know your IP address
and I'll set up a multinet link here. That should do.
I honestly haven't the first clue how.
My IP is 213.123.127.24 if you want to set your end up.
If it does down sometimes we'll just have to live with the consequences ;-)
You mean like when I woke up this morning to find my HP Microserver was off.
No idea why. I must live in the Twilight Zone... or I leant on the power button
yesterday.
Unless ROOSTA is an area router, that link makes no sense.
I won't argue with you about that... I can't fix it from here, though.
But does DECnet allow two different area routers, with different subsets of
reachable nodes, for the same area??
as long as ALL area routers in an area talks to eachother and the
transit nodes are all L2 area routers in the same area.
--P
Well that is a good summary Johnny.
The application are compatible, phone and sethost work well between nodes.
I think phase V maintains a lot more information so the management software might return error messages because the phase V node doesn't understand the incoming request. IIRC phase V nodes still have a small NCP database so that remote phase IV nodes can interrogate (a subset of) executor parameters.
Hans
-----Original Message-----
From: Johnny Billquist <bqt at softjar.se>
Sender: owner-hecnet at Update.UU.SE
Date: Tue, 27 Dec 2011 10:20:27
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] ROOSTA routing problem / NIKKEL
On 2011-12-27 09.35, hvlems at zonnet.nl wrote:
That's what I meant :-) sorry for the obscure language. More precisely: phase IV has no clue about phase V. It is possible to get information from a phase IV node while running ncl.
I'll boot a phase IV area router this evening. Everything is shutdown right now except the bridge program.
Well, phase V is supposed to be backwards compatible with phase IV,
meaning a phase IV node can talk with a phase V node, as far as phase IV
functionality goes. NCP (and NCL, which I assume is the phase V tool for
manipulating things) are just the local tool. When you give commands
over the network, you talk a protocol called NICE, which is a known
object in DECnet. Phase IV or phase V shouldn't make a difference, since
the NICE protocol is still the same (or should be). It would appear the
made some incompatible change after all, which atleast makes RSX
machines not happy with the response from a NICE server on a phase V node.
Oh well... Not that important, I guess.
Johnny
-----Original Message-----
From: Johnny Billquist<bqt at softjar.se>
Sender: owner-hecnet at Update.UU.SE
Date: Tue, 27 Dec 2011 09:23:22
To:<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] ROOSTA routing problem / NIKKEL
On 2011-12-26 23.26, H Vlems wrote:
Could that be ncl talking back to your ncp?
Not sure what you mean by that.
But the fact that it's a phase V node might be the reason. Slightly
incompatible with phase IV sometimes...
Johnny
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: maandag, december 2011 22:29
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] ROOSTA routing problem / NIKKEL
On 2011-12-26 18.46, H Vlems wrote:
Johnny, what is wrong with NIKKEL as seen from your end?
Sorry. I should really have told that one...
.ncp tell nikkel sho exec
NCP -- Show failed, oversized Management command message
Johnny
Hans
PS Ni is a phase V decnet node
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: maandag, december 2011 15:37
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] ROOSTA routing problem
On 2011-12-26 15.24, Johnny Billquist wrote:
On 2011-12-26 15.07, Bob Armstrong wrote:
Hmmm.. LEGATO can't talk to ROOSTA ("remote node not currently
reachable") even though there's a direct Multinet link to ROOSTA (and
yes, the link is UP and working).
I think the problem is that ROOSTA is in area 6, and the area router for
6 is STAR69. Trouble is, STAR69 doesn't have a path to ROOSTA and
doesn't know how to send it packets.
Unless ROOSTA is an area router, that link makes no sense. You cannot
have (usable) links between different areas unless both ends are area
routers...
It would appear something is more broken currently. I can't talk to SG1
from MIM either, and thus nothing beyond it. And SG1 is currently acting
as the next hop for a whole bunch of areas, as seen from area 1.
Also, while I'm at it: NIKKEL - There is some issue with that machine
too. Can others talk with it?
Johnny
Hmmm.. LEGATO can't talk to ROOSTA ("remote node not currently reachable")
even though there's a direct Multinet link to ROOSTA (and yes, the link is
UP and working).
I think the problem is that ROOSTA is in area 6, and the area router for 6
is STAR69. Trouble is, STAR69 doesn't have a path to ROOSTA and doesn't
know how to send it packets.
(It doesn't help that STAR69 still thinks that ROOSTA is 3.34 - it moved
to 6.134 a while ago - but I don't think that's causing the problem.)
Multinet links metric 5
Bridged ethernet metric 10
Set all multinet-link nodes Level2-Area-Routers
--P
