|
Question regarding multi-homed clients: msg#00092file-systems.lustre.user
Hi all, We're running a few clients who have multiple IPs assigned to them which are not broadcast. These however are picked up by the Lustre client and the MDS evicts the client in question after bringing it up. A way around this is to ensure that only the primary interface is up when Lustre is bought up on the client. Is there however any way to restrict the client to only communicate via, say eth0? Thanks, -- Mustafa A. Hashmi mahashmi-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx _______________________________________________ Lustre-discuss mailing list Lustre-discuss-KYPl3Ael/zSakBO8gow8eQ@xxxxxxxxxxxxxxxx https://mail.clusterfs.com/mailman/listinfo/lustre-discuss |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Fsck downtime estimates: 00092, Peter Grandi |
|---|---|
| Next by Date: | RE: Question regarding multi-homed clients: 00092, Eric Barton |
| Previous by Thread: | Fsck downtime estimatesi: 00092, Andrei Maslennikov |
| Next by Thread: | RE: Question regarding multi-homed clients: 00092, Eric Barton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |