They aren't supported on Integrity.
Only Ethernet LANs are.
Sampsa Laine wrote:
Hmm, not ideal.
I do have 3 FDDI cards, do you know if the DEFPA cards work on OpenVMS for Integrity boxes?
Sampsa
On 29 Sep 2009, at 19:50, Kari Uusim ki wrote:
Sampsa Laine wrote:
Is it possible to run a cluster over both ethernet and FDDI?
Basically, I'd like to connect Machine A -> B using ethernet and B -> C using FDDI - is this possible?
Sampsa
.
Unfortunately that configuration violates the rule of full connectivity. All cluster members must have direct connectivity to other members.
But if you add a FDDI-Ethernet-bridge, you should get a "legal" configuration.
Kari
.
I've come up with an alternative solution:
I'll use ethernet for the cluster interconnect as I have ethernet ports on all the machines.
However, this leaves CHIMPY without an ethernet-based TCP/IP connection. So my question is this:
Can I hook up two machines (running VMS) with FDDI and have the second machine route packets onto the ethernet segment for me? This wasn't immediately clear from the documentation. I assume if the second machine is set up as a L1 router DECNET over this setup will be possible?
Sampsa
On 29 Sep 2009, at 19:50, Kari Uusim ki wrote:
Sampsa Laine wrote:
Is it possible to run a cluster over both ethernet and FDDI?
Basically, I'd like to connect Machine A -> B using ethernet and B -> C using FDDI - is this possible?
Sampsa
.
Unfortunately that configuration violates the rule of full connectivity. All cluster members must have direct connectivity to other members.
But if you add a FDDI-Ethernet-bridge, you should get a "legal" configuration.
Kari
Hmm, not ideal.
I do have 3 FDDI cards, do you know if the DEFPA cards work on OpenVMS for Integrity boxes?
Sampsa
On 29 Sep 2009, at 19:50, Kari Uusim ki wrote:
Sampsa Laine wrote:
Is it possible to run a cluster over both ethernet and FDDI?
Basically, I'd like to connect Machine A -> B using ethernet and B -> C using FDDI - is this possible?
Sampsa
.
Unfortunately that configuration violates the rule of full connectivity. All cluster members must have direct connectivity to other members.
But if you add a FDDI-Ethernet-bridge, you should get a "legal" configuration.
Kari
Sampsa Laine wrote:
Is it possible to run a cluster over both ethernet and FDDI?
Basically, I'd like to connect Machine A -> B using ethernet and B -> C using FDDI - is this possible?
Sampsa
.
Unfortunately that configuration violates the rule of full connectivity. All cluster members must have direct connectivity to other members.
But if you add a FDDI-Ethernet-bridge, you should get a "legal" configuration.
Kari
Is it possible to run a cluster over both ethernet and FDDI?
Basically, I'd like to connect Machine A -> B using ethernet and B -> C using FDDI - is this possible?
Sampsa
Yeah. Saw that afterwards. I saw that you hadn't specified a port number, but if the problem was when running simh, that detail had not been relevant. :-)
Johnny
Sampsa Laine wrote:
It was a misconfiguration of the bridge, forgot the port number, the bridge tried to open an interface named silverback.sampsa.com which didn'\t work obviously.
Sampsa
On 26 Sep 2009, at 23:18, Johnny Billquist wrote:
Sampsa Laine wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
Not sure what you are doing. Is the problem coming from running simh, or from running the bridge program???
Johnny
--
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
--
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
It was a misconfiguration of the bridge, forgot the port number, the bridge tried to open an interface named silverback.sampsa.com which didn'\t work obviously.
Sampsa
On 26 Sep 2009, at 23:18, Johnny Billquist wrote:
Sampsa Laine wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
Not sure what you are doing. Is the problem coming from running simh, or from running the bridge program???
Johnny
--
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
Sampsa Laine wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
Not sure what you are doing. Is the problem coming from running simh, or from running the bridge program???
Johnny
--
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
Yup, that was it, forgot the port number after the IP. Works now, cheers.
Sampsa
On 26 Sep 2009, at 22:53, gerry77 at mail.com wrote:
On Sat, 26 Sep 2009 22:43:14 +0100, you wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting
the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
If I remember correctly, you must tell it a port number for any remote bridge
or it will consider "silverback.sampsa.com" and such as a local device, which
obviously does not exist. Try appending ":4711" or whatever at the end of the
second line :)
G.
On Sat, 26 Sep 2009 22:43:14 +0100, you wrote:
I'm setting up a VM that runs SIMH-VAX in a Gentoo VM and keep getting
the following error message:
Error opening device.
The relevant part of my bridge.conf reads as follows:
[bridge]
local eth0
sampsa silverback.sampsa.com
Any ideas?
If I remember correctly, you must tell it a port number for any remote bridge
or it will consider "silverback.sampsa.com" and such as a local device, which
obviously does not exist. Try appending ":4711" or whatever at the end of the
second line :)
G.