Didn't think about that actually :) I just figured it would be better to dedicate interfaces and a VLAN to clustering. The HECnet bridge doesn't bridge clustering traffic I hope? Sampsa On 29 Sep 2009, at 20:44, Zane H. Healy wrote: Why would this leave CHIMPY wihtout an ethernet-based TCP/IP connection? You can use an ethernet interface for clustering, DECnet, and TCP/IP at the same time. Zane On Tue, 29 Sep 2009, Sampsa Laine wrote: 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