<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> FYI - everything worked as I expected. I put a second interface in each host and configured it for another network. Then, I configured the resources for this 2nd network and created a separate service specifically for the resources on this network. So I have a service for nfs exports to our 91.0 network and another for exports to our 20.0 network. Using different nfs client resources, I can mount rw on one network and ro on the other, for example. I figured it would work this way, but I hadn't tested it yet. I must admit I sweating a bit until I actually saw it work. Thanks, Randy Brian Kroth wrote: <blockquote cite="mid:20080312175438.GH18229@wisc.edu" type="cite"> <pre wrap="">OK, poorly thought out example. FYI, in heartbeat you can specify which interface to use for the service IP, though like rgmanager, you generally don't have to: <a class="moz-txt-link-freetext" href="http://www.linux-ha.org/HeartbeatResourceAgent/IPaddr2">http://www.linux-ha.org/HeartbeatResourceAgent/IPaddr2</a> <a class="moz-txt-link-freetext" href="http://www.linux-ha.org/v2/Examples/Simple">http://www.linux-ha.org/v2/Examples/Simple</a> Alex Kompel <a class="moz-txt-link-rfc2396E" href="mailto:barbos@gmail.com"><barbos@gmail.com></a> 2008-03-12 10:39: </pre> <blockquote type="cite"> <pre wrap="">You will still need some way to tell the system through which interface you want to route outgoing packets for each target. You can achieve the same with greater ease by splitting the network in 2 subnets and assigning each to a single interface. It all depends on the problem you are trying to solve. If you want redundancy - use active-passive bonding, you want throughput - use active-active bonding (if your switch supports link aggregation), if you want security and isolation - use separate subnets. -Alex 2008/3/12 Brian Kroth <a class="moz-txt-link-rfc2396E" href="mailto:bpkroth@wisc.edu"><bpkroth@wisc.edu></a>: </pre> <blockquote type="cite"> <pre wrap="">This is a hypothetical, but what if you have two interfaces on the same network and want to force one service IP to one interface and the other to a different interface? I think what everyone is wondering is how much control one has over the service IP placement. Thanks, Brian Finnur Örn Guðmundsson - TM Software <a class="moz-txt-link-rfc2396E" href="mailto:fog@t.is"><fog@t.is></a> 2008-03-12 14:36: </pre> <blockquote type="cite"> <pre wrap="">Hi, </pre> </blockquote> <pre wrap=""> > > I see no reason why you could not have 3 diffrent interfaces, each connected to the networks you are trying to serve the NFS requests to/from. RG Manager will add the floating interfaces to the "correct" interface, that is, if your floating ip is 1.2.3.4 and you have a interface with the IP address 1.2.3.3 he will add the IP to that interface. > > > Bgrds, > Finnur > > -----Original Message----- > From: <a class="moz-txt-link-abbreviated" href="mailto:linux-cluster-bounces@redhat.com">linux-cluster-bounces@redhat.com</a> [<a class="moz-txt-link-freetext" href="mailto:linux-cluster-bounces@redhat.com">mailto:linux-cluster-bounces@redhat.com</a>] On Behalf Of <a class="moz-txt-link-abbreviated" href="mailto:gordan@bobich.net">gordan@bobich.net</a> > Sent: 12. mars 2008 14:10 > To: linux clustering > Subject: Re: [Linux-cluster] Two node NFS cluster serving multiple networks > > Sounds very similar to what I'm trying to achieve (see the other thread > about binding failover resources to interfaces). I've not seen a response > yet, so I'm most curious to see if you'll get any. > > Gordan > > On Wed, 12 Mar 2008, Randy Brown wrote: > > > I am using a two node cluster with Centos 5 with up to date patches. We have > > three different networks to which I would like to serve nfs mounts from this > > cluster. Can this even be done? I have interfaces available for each > > network in each node? > > -- > Linux-cluster mailing list > <a class="moz-txt-link-abbreviated" href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> > <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a> > > -- > Linux-cluster mailing list > <a class="moz-txt-link-abbreviated" href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> > <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a> -- Linux-cluster mailing list <a class="moz-txt-link-abbreviated" href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a> </pre> </blockquote> <pre wrap="">-- Linux-cluster mailing list <a class="moz-txt-link-abbreviated" href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a> </pre> <pre wrap=""> <hr size="4" width="90%"> -- Linux-cluster mailing list <a class="moz-txt-link-abbreviated" href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a></pre> </blockquote> </blockquote> </body> </html>