[gpfsug-discuss] Not recommended, but why not?

[Bryan Banister]

Sure, many ways to solve the same problem, just depends on where you want to have the controls.  Having a separate VLAN doesn't give you as fine grained controls over each network workload you are using, such as metrics collection, monitoring, GPFS, SSH, NFS vs SMB, vs Object, etc.

But it doesn't matter how it's done as long as you ensure GPFS has enough bandwidth to function, cheers,
-Bryan

-----Original Message-----
From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Jonathan Buzzard
Sent: Saturday, May 05, 2018 3:57 AM
To: gpfsug-discuss at spectrumscale.org
Subject: Re: [gpfsug-discuss] Not recommended, but why not?

Note: External Email
-------------------------------------------------

On 04/05/18 18:30, Bryan Banister wrote:
> You also have to be careful with network utilization… we have some very
> hungry NFS clients in our environment and the NFS traffic can actually
> DOS other services that need to use the network links.  If you configure
> GPFS admin/daemon traffic over the same link as the SMB/NFS traffic then
> this could lead to GPFS node evictions if disk leases cannot get
> renewed.  You could limit the amount that SMV/NFS use on the network
> with something like the tc facility if you’re sharing the network
> interfaces for GPFS and CES services.
>

The right answer to that IMHO is a separate VLAN for the GPFS
command/control traffic that is prioritized above all other VLAN's. Do
something like mark it as a voice VLAN. Basically don't rely on some OS
layer to do the right thing at layer three, enforce it at layer two in
the switches.

JAB.

--
Jonathan A. Buzzard                         Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

________________________________

Note: This email is for the confidential use of the named addressee(s) only and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you are hereby notified that any review, dissemination or copying of this email is strictly prohibited, and to please notify the sender immediately and destroy this email and any attachments. Email transmission cannot be guaranteed to be secure or error-free. The Company, therefore, does not make any guarantees as to the completeness or accuracy of this email or any attachments. This email is for informational purposes only and does not constitute a recommendation, offer, request or solicitation of any kind to buy, sell, subscribe, redeem or perform any type of transaction of a financial product.