Tel: (253)371-3040
>
>
> 2800 N Center DrFax: (253)371-4647
>
> DuPont WA 98327 *bob.ha...@intel.com *
>
> ** **
>
> *From:* Cliff White [mailto:cli...@whamcloud.com]
> *Sent:* Wednesday, March 21, 2012 9:28 AM
> *To:* Ha
8 AM
To: Hayes, Bob
Cc: lustre-discuss@lists.lustre.org
Subject: Re: [Lustre-discuss] Seeking LNET router recomendations
Or to put it another way, if your OSS systems can already 'see' both IB and
IPoIB networks the most cost
effective, high performance solution would be to add the necessary
Or to put it another way, if your OSS systems can already 'see' both IB and
IPoIB networks the most cost
effective, high performance solution would be to add the necessary
interface and put your MDS/MGS on both networks also.
No need for routers, no performance impact.
cliffw
On Tue, Mar 13, 2012
- An OSS really can't be a router, an OSS is an endpoint. Topologically,
it shouldn't work, you should re-think network layout.
- routing does place a load on the system, nodes doing routing should be
dedicated to routing.
- Load depends on traffic, basically you would have two hardware network
in
Are there any recommendations or guidelines for sizing a LNET routing facility.
~400 nodes, 8 OSS (dual socket E5 w/48GB RAM), 24 OST (10spindle RAID6 over
SRP), 1 MGS/MDT
How much load does LNET routing put on a system?
If I make the 8 OSS systems do double duty as IB to IPoIB routers, will it ha
