[Lustre-discuss] Fwd: question about routing between subnets
cliffw at whamcloud.com
Tue Jan 25 09:36:33 PST 2011
The MGS can be behind an lnet router. So, provided you have LNET routing set
A and B, the MGS should be okay with only a subnet A address, clients on B
routing configuration should be fine.
The address on net C is thus immaterial.
On Tue, Jan 25, 2011 at 6:51 AM, Bob Ball <ball at umich.edu> wrote:
> Hi, no response on this the first time I sent it around. Can anyone help
> me on this?
> -------- Original Message -------- Subject: [Lustre-discuss] question
> about routing between subnets Date: Fri, 21 Jan 2011 15:48:25 -0500 From:
> Bob Ball <ball at umich.edu> <ball at umich.edu> To: Lustre discussion
> <lustre-discuss at lists.Lustre.org> <lustre-discuss at lists.Lustre.org>
> Our lustre 1.8.4 system sits primarily on subnet A. However, we also
> have a small number of clients that sit on subnet B. In setting up the
> subnet B clients, we provided lnet router machines that have addresses
> on both subnet A and on subnet B, the MGS machine has addresses on both
> subnet A and subnet B, and all the OSS have lnet routing that lets this
> work. Our world is a happy place.
> Now, due to other factors, we have to change the MGS subnet B address to
> instead be on subnet C. Subnet C will be set up to have the usual IP
> routing to find subnet B, but what will happen to the clients that exist
> only on subnet B? Is there a way for them to find the MGS at boot time,
> or are they going to stop working once this network change is effected?
> Thanks much,
> Lustre-discuss mailing listLustre-discuss at lists.lustre.orghttp://lists.lustre.org/mailman/listinfo/lustre-discuss
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lustre-discuss