Steps needed for bond config
sandeep.kumar
10 Posts
December 24, 2025, 12:52 pmQuote from sandeep.kumar on December 24, 2025, 12:52 pmHello Team,
Tried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration. Please do the needful ASAP
Hello Team,
Tried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration. Please do the needful ASAP
admin
3,054 Posts
December 25, 2025, 8:49 pmQuote from admin on December 25, 2025, 8:49 pmPlease see reply to your other post:
https://www.petasan.org/forums/?view=thread&id=1507
Please see reply to your other post:
https://www.petasan.org/forums/?view=thread&id=1507
sandeep.kumar
10 Posts
January 2, 2026, 5:37 pmQuote from sandeep.kumar on January 2, 2026, 5:37 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 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 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.
sandeep.kumar
10 Posts
January 6, 2026, 1:20 pmQuote from sandeep.kumar on January 6, 2026, 1:20 pmTried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration detail steps. Please do the needful ASAP
Tried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration detail steps. Please do the needful ASAP
admin
3,054 Posts
January 6, 2026, 11:22 pmQuote from admin on January 6, 2026, 11:22 pmBonds and other setups are done using the Deployment Wizard web ui during cluster creation, they apply to all nodes as well as future nodes to be added in the future.
If you wish to modify after cluster creation, edit:
/opt/petasan/config/cluster_info.json
The format is self explanatory, but it is best if you create a 1 node test vm, deploy it and create a cluster and grab the config file. no need to actually deploy a second node.
Bonds and other setups are done using the Deployment Wizard web ui during cluster creation, they apply to all nodes as well as future nodes to be added in the future.
If you wish to modify after cluster creation, edit:
/opt/petasan/config/cluster_info.json
The format is self explanatory, but it is best if you create a 1 node test vm, deploy it and create a cluster and grab the config file. no need to actually deploy a second node.
uduggireddy
6 Posts
January 7, 2026, 8:14 amQuote from uduggireddy on January 7, 2026, 8:14 amWe have got the option to select bonds for interfaces, we have selected active-passive bond for management interfaces and LACP bond for backend and data interfaces.
Main query is we have NFS client in various jf vlans for example vlan2, vlan3, vlan4 etc. NFS client in one vlan cannot mount NFS from other vlan NFS IP.
For example NFS client in vlan2 cannot mount NFS using NFS IP in vlan4.
In NFS settings we are getting option to select or add set of IP's from only one vlan (for example vlan2). We would like to know if there is possibility that we can add IP's to NFS from vlan3 , vlan4 also so we can mount NFS on respective vlan clients
We have got the option to select bonds for interfaces, we have selected active-passive bond for management interfaces and LACP bond for backend and data interfaces.
Main query is we have NFS client in various jf vlans for example vlan2, vlan3, vlan4 etc. NFS client in one vlan cannot mount NFS from other vlan NFS IP.
For example NFS client in vlan2 cannot mount NFS using NFS IP in vlan4.
In NFS settings we are getting option to select or add set of IP's from only one vlan (for example vlan2). We would like to know if there is possibility that we can add IP's to NFS from vlan3 , vlan4 also so we can mount NFS on respective vlan clients
Steps needed for bond config
sandeep.kumar
10 Posts
Quote from sandeep.kumar on December 24, 2025, 12:52 pmHello Team,
Tried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration. Please do the needful ASAP
Hello Team,
Tried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration. Please do the needful ASAP
admin
3,054 Posts
Quote from admin on December 25, 2025, 8:49 pmPlease see reply to your other post:
https://www.petasan.org/forums/?view=thread&id=1507
Please see reply to your other post:
https://www.petasan.org/forums/?view=thread&id=1507
sandeep.kumar
10 Posts
Quote from sandeep.kumar on January 2, 2026, 5:37 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 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 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.
sandeep.kumar
10 Posts
Quote from sandeep.kumar on January 6, 2026, 1:20 pmTried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration detail steps. Please do the needful ASAP
Tried configuring the bond details in /etc/network/interface file, network is not coming up.
Need detailed steps for configuring bond on PetaSAN 4.0 cluster. We have multiple JF VLAN's wanted to configure multiple bond using those VLAN's.
We have 2 25G NIC's, we will use them for bond configuration detail steps. Please do the needful ASAP
admin
3,054 Posts
Quote from admin on January 6, 2026, 11:22 pmBonds and other setups are done using the Deployment Wizard web ui during cluster creation, they apply to all nodes as well as future nodes to be added in the future.
If you wish to modify after cluster creation, edit:
/opt/petasan/config/cluster_info.json
The format is self explanatory, but it is best if you create a 1 node test vm, deploy it and create a cluster and grab the config file. no need to actually deploy a second node.
Bonds and other setups are done using the Deployment Wizard web ui during cluster creation, they apply to all nodes as well as future nodes to be added in the future.
If you wish to modify after cluster creation, edit:
/opt/petasan/config/cluster_info.json
The format is self explanatory, but it is best if you create a 1 node test vm, deploy it and create a cluster and grab the config file. no need to actually deploy a second node.
uduggireddy
6 Posts
Quote from uduggireddy on January 7, 2026, 8:14 amWe have got the option to select bonds for interfaces, we have selected active-passive bond for management interfaces and LACP bond for backend and data interfaces.
Main query is we have NFS client in various jf vlans for example vlan2, vlan3, vlan4 etc. NFS client in one vlan cannot mount NFS from other vlan NFS IP.
For example NFS client in vlan2 cannot mount NFS using NFS IP in vlan4.
In NFS settings we are getting option to select or add set of IP's from only one vlan (for example vlan2). We would like to know if there is possibility that we can add IP's to NFS from vlan3 , vlan4 also so we can mount NFS on respective vlan clients
We have got the option to select bonds for interfaces, we have selected active-passive bond for management interfaces and LACP bond for backend and data interfaces.
Main query is we have NFS client in various jf vlans for example vlan2, vlan3, vlan4 etc. NFS client in one vlan cannot mount NFS from other vlan NFS IP.
For example NFS client in vlan2 cannot mount NFS using NFS IP in vlan4.
In NFS settings we are getting option to select or add set of IP's from only one vlan (for example vlan2). We would like to know if there is possibility that we can add IP's to NFS from vlan3 , vlan4 also so we can mount NFS on respective vlan clients