Need some clarification regarding NFS network configuration
sandeep.kumar
10 Posts
January 2, 2026, 6:03 pmQuote from sandeep.kumar on January 2, 2026, 6:03 pmWe are currently in the process of evaluating PetaSAN 4.0.0 as part of a migration from our existing Dell Isilon environment and would like Need some clarification regarding NFS network configuration.
In our current Isilon setup, we are using approximately 15 VLANs, with each VLAN mapped to a separate SmartConnect IP. This allows us to segregate traffic and present NFS exports over multiple networks/VLANs as per application requirements.
While configuring NFS in PetaSAN 4.0.0, we observed that the UI allows us to associate only a single VLAN under the NFS settings. We did not find an option to configure multiple VLANs or networks for NFS access similar to our Isilon design.
Could you please help clarify:
Whether PetaSAN 4.0.0 supports multiple VLANs or networks for NFS access.
If this is supported, what is the recommended approach or configuration method (UI or CLI).
If not currently supported, are there any workarounds or roadmap plans to support multi-VLAN NFS configurations in future releases.
This information will help us finalize our network and migration design.
We are currently in the process of evaluating PetaSAN 4.0.0 as part of a migration from our existing Dell Isilon environment and would like Need some clarification regarding NFS network configuration.
In our current Isilon setup, we are using approximately 15 VLANs, with each VLAN mapped to a separate SmartConnect IP. This allows us to segregate traffic and present NFS exports over multiple networks/VLANs as per application requirements.
While configuring NFS in PetaSAN 4.0.0, we observed that the UI allows us to associate only a single VLAN under the NFS settings. We did not find an option to configure multiple VLANs or networks for NFS access similar to our Isilon design.
Could you please help clarify:
Whether PetaSAN 4.0.0 supports multiple VLANs or networks for NFS access.
If this is supported, what is the recommended approach or configuration method (UI or CLI).
If not currently supported, are there any workarounds or roadmap plans to support multi-VLAN NFS configurations in future releases.
This information will help us finalize our network and migration design.
admin
3,054 Posts
January 4, 2026, 10:10 amQuote from admin on January 4, 2026, 10:10 amIn PetaSAN each network (backend, nfs, s3, smb, iscsi1, isci2) can have a separate vlan.
All ips used in nfs would use the same nfs vlan, the different nfs ips (server ips) are used for load balancing nfs load across the different nfs servers in active/active setup and not intended to segregate traffic.
i am not sure if what you want can be achieved by switch configuration or some other methods which allows vlan translation at the ethernet packet level.
Maybe if this is something required in the future we can add it in our feature list, however sometimes we get feedback to reduce the requirements for different networks rather than create additional segregation.
In PetaSAN each network (backend, nfs, s3, smb, iscsi1, isci2) can have a separate vlan.
All ips used in nfs would use the same nfs vlan, the different nfs ips (server ips) are used for load balancing nfs load across the different nfs servers in active/active setup and not intended to segregate traffic.
i am not sure if what you want can be achieved by switch configuration or some other methods which allows vlan translation at the ethernet packet level.
Maybe if this is something required in the future we can add it in our feature list, however sometimes we get feedback to reduce the requirements for different networks rather than create additional segregation.
Last edited on January 4, 2026, 10:10 am by admin · #2
sandeep.kumar
10 Posts
January 6, 2026, 12:52 pmQuote from sandeep.kumar on January 6, 2026, 12:52 pmWe understand that in PetaSAN each service (backend, NFS, S3, SMB, iSCSI, etc.) can be mapped to a dedicated VLAN, and that multiple NFS server IPs are primarily intended for load balancing in an active/active model rather than traffic segregation.
We have NFS client from different vlans, so want to bound multiple vlans to NFS services
Please suggest PetaSAN currently does not support multiple VLANs bound directly to NFS services?
We understand that in PetaSAN each service (backend, NFS, S3, SMB, iSCSI, etc.) can be mapped to a dedicated VLAN, and that multiple NFS server IPs are primarily intended for load balancing in an active/active model rather than traffic segregation.
We have NFS client from different vlans, so want to bound multiple vlans to NFS services
Please suggest PetaSAN currently does not support multiple VLANs bound directly to NFS services?
Need some clarification regarding NFS network configuration
sandeep.kumar
10 Posts
Quote from sandeep.kumar on January 2, 2026, 6:03 pmWe are currently in the process of evaluating PetaSAN 4.0.0 as part of a migration from our existing Dell Isilon environment and would like Need some clarification regarding NFS network configuration.
In our current Isilon setup, we are using approximately 15 VLANs, with each VLAN mapped to a separate SmartConnect IP. This allows us to segregate traffic and present NFS exports over multiple networks/VLANs as per application requirements.
While configuring NFS in PetaSAN 4.0.0, we observed that the UI allows us to associate only a single VLAN under the NFS settings. We did not find an option to configure multiple VLANs or networks for NFS access similar to our Isilon design.
Could you please help clarify:
Whether PetaSAN 4.0.0 supports multiple VLANs or networks for NFS access.
If this is supported, what is the recommended approach or configuration method (UI or CLI).
If not currently supported, are there any workarounds or roadmap plans to support multi-VLAN NFS configurations in future releases.
This information will help us finalize our network and migration design.
We are currently in the process of evaluating PetaSAN 4.0.0 as part of a migration from our existing Dell Isilon environment and would like Need some clarification regarding NFS network configuration.
In our current Isilon setup, we are using approximately 15 VLANs, with each VLAN mapped to a separate SmartConnect IP. This allows us to segregate traffic and present NFS exports over multiple networks/VLANs as per application requirements.
While configuring NFS in PetaSAN 4.0.0, we observed that the UI allows us to associate only a single VLAN under the NFS settings. We did not find an option to configure multiple VLANs or networks for NFS access similar to our Isilon design.
Could you please help clarify:
Whether PetaSAN 4.0.0 supports multiple VLANs or networks for NFS access.
If this is supported, what is the recommended approach or configuration method (UI or CLI).
If not currently supported, are there any workarounds or roadmap plans to support multi-VLAN NFS configurations in future releases.
This information will help us finalize our network and migration design.
admin
3,054 Posts
Quote from admin on January 4, 2026, 10:10 amIn PetaSAN each network (backend, nfs, s3, smb, iscsi1, isci2) can have a separate vlan.
All ips used in nfs would use the same nfs vlan, the different nfs ips (server ips) are used for load balancing nfs load across the different nfs servers in active/active setup and not intended to segregate traffic.
i am not sure if what you want can be achieved by switch configuration or some other methods which allows vlan translation at the ethernet packet level.
Maybe if this is something required in the future we can add it in our feature list, however sometimes we get feedback to reduce the requirements for different networks rather than create additional segregation.
In PetaSAN each network (backend, nfs, s3, smb, iscsi1, isci2) can have a separate vlan.
All ips used in nfs would use the same nfs vlan, the different nfs ips (server ips) are used for load balancing nfs load across the different nfs servers in active/active setup and not intended to segregate traffic.
i am not sure if what you want can be achieved by switch configuration or some other methods which allows vlan translation at the ethernet packet level.
Maybe if this is something required in the future we can add it in our feature list, however sometimes we get feedback to reduce the requirements for different networks rather than create additional segregation.
sandeep.kumar
10 Posts
Quote from sandeep.kumar on January 6, 2026, 12:52 pmWe understand that in PetaSAN each service (backend, NFS, S3, SMB, iSCSI, etc.) can be mapped to a dedicated VLAN, and that multiple NFS server IPs are primarily intended for load balancing in an active/active model rather than traffic segregation.
We have NFS client from different vlans, so want to bound multiple vlans to NFS services
Please suggest PetaSAN currently does not support multiple VLANs bound directly to NFS services?
We understand that in PetaSAN each service (backend, NFS, S3, SMB, iSCSI, etc.) can be mapped to a dedicated VLAN, and that multiple NFS server IPs are primarily intended for load balancing in an active/active model rather than traffic segregation.
We have NFS client from different vlans, so want to bound multiple vlans to NFS services
Please suggest PetaSAN currently does not support multiple VLANs bound directly to NFS services?