I would respectfully disagree.

pNFS does not stripe data across controllers. Data is distributed, not striped.

Every node is a metadata server and will redirect the client process to the node directly holding the volume. No striping.

Maybe you are confusing pNFS with FlexGroups which distributes files across nodes.

A very long time ago in ONTAP GX, there >>was<< an ability to stripe data across controllers. That feature was removed upon going to ONTAP 8.0

--tmac

Tim McCarthy, Principal Consultant

Proud Member of the #NetAppATeam

I Blog at TMACsRack

On Mon, Aug 16, 2021 at 9:36 AM Michael Bergman via Toasters <toasters@teaparty.net> wrote:

---------- Forwarded message ----------
From: Michael Bergman <michael.bergman@ericsson.com>
To: Toasters <toasters@teaparty.net>
Cc:
Bcc:
Date: Mon, 16 Aug 2021 13:34:17 +0000
Subject: Re: pNFS not working on vserver when several lifs with different Vlans available
On 2021-08-16 15:13, Florian Schmid wrote:
> Is this really the case? Is the pNFS process really not Vlan aware and
> sends any IP from that node where volume is located, even when the IP is
> in a different network than the client IP?

Yes. That's how pNFS is supposed to work. That's the whole point one can
say, of pNFS. It's striping of the data traffic (not metadata) across
several nodes, all at once.

In that respect, the setup you say you have, this:

"On the vServer, we have several different Vlans and each Vlans has an
interface for each node there. Our storage network is completely switched,
so no routing between Vlans possible."

is totally wrong for pNFS. In such a set up you definitely do not want pNFS.

/M

---------- Forwarded message ----------
From: Michael Bergman via Toasters <toasters@teaparty.net>
To: Toasters <toasters@teaparty.net>
Cc:
Bcc:
Date: Mon, 16 Aug 2021 14:34:25 +0100
Subject:
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
https://www.teaparty.net/mailman/listinfo/toasters