|
RE: Question regarding multi-homed clients: msg#00093file-systems.lustre.user
options lnet networks="tcp0(eth0)" ...will make LNET always uses interface eth0 to construct a NID (i.e. <ip address of eth0>@tcp0). Cheers, Eric ________________________________ From: lustre-discuss-bounces-KYPl3Ael/zSakBO8gow8eQ@xxxxxxxxxxxxxxxx [mailto:lustre-discuss-bounces-KYPl3Ael/zSakBO8gow8eQ@xxxxxxxxxxxxxxxx] On Behalf Of Mustafa A. Hashmi Sent: 30 April 2007 10:48 AM To: lustre-discuss-KYPl3Ael/zSakBO8gow8eQ@xxxxxxxxxxxxxxxx Subject: [Lustre-discuss] Question regarding multi-homed clients 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 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Question regarding multi-homed clients: 00093, Mustafa A. Hashmi |
|---|---|
| Next by Date: | Re: Question regarding multi-homed clients: 00093, rishi pathak |
| Previous by Thread: | Question regarding multi-homed clientsi: 00093, Mustafa A. Hashmi |
| Next by Thread: | Re: Question regarding multi-homed clients: 00093, rishi pathak |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |