Bonding for Management Interface
pedro6161
36 Posts
December 16, 2020, 9:02 pmQuote from pedro6161 on December 16, 2020, 9:02 pmHi,
are possible to create bonding interface special for management interface on first time installation from ISO ?
existing i tried PetaSAN 2.7.0, if i enable LACP from my switch, i cannot open deployment wizard, so i disabled first and then i create bonding from deployment wizard and stop(because on backend script creating bonding for management) so i enable immediately on my switch for LACP and then the deployment wizard can finish (node 1 and 2) but for node 3 until 3 hours never finish deploy so i decide to start again from beginning with management interface without LACP, the rest interface(for services) i create bond
Hi,
are possible to create bonding interface special for management interface on first time installation from ISO ?
existing i tried PetaSAN 2.7.0, if i enable LACP from my switch, i cannot open deployment wizard, so i disabled first and then i create bonding from deployment wizard and stop(because on backend script creating bonding for management) so i enable immediately on my switch for LACP and then the deployment wizard can finish (node 1 and 2) but for node 3 until 3 hours never finish deploy so i decide to start again from beginning with management interface without LACP, the rest interface(for services) i create bond
admin
2,930 Posts
December 16, 2020, 9:30 pmQuote from admin on December 16, 2020, 9:30 pmif you want to bond, safest to use active/backup for management and lacp for backend. Many switch models allow you to connect to an lacp switch port before you setup lacp on your nic, then will enable lacp once it is setup which is negotiated between both ends, look for active/passive lacp setting on the switch if it support this. else use active/backup for management. Management typically does not require any bandwidth so active/backup should be no issue. If you really need and your switch does not support negotiation, you can manually set it either via changing the bond type in /opt/petasan/config/cluster_info.json or through the custom script /opt/petasan/scripts/custom/post_start_network.sh which you can configure network as you wish.
if you want to bond, safest to use active/backup for management and lacp for backend. Many switch models allow you to connect to an lacp switch port before you setup lacp on your nic, then will enable lacp once it is setup which is negotiated between both ends, look for active/passive lacp setting on the switch if it support this. else use active/backup for management. Management typically does not require any bandwidth so active/backup should be no issue. If you really need and your switch does not support negotiation, you can manually set it either via changing the bond type in /opt/petasan/config/cluster_info.json or through the custom script /opt/petasan/scripts/custom/post_start_network.sh which you can configure network as you wish.
Last edited on December 16, 2020, 9:35 pm by admin · #2
pedro6161
36 Posts
December 16, 2020, 9:42 pmQuote from pedro6161 on December 16, 2020, 9:42 pmif use active/passive mode i agree since only single interface active and mostly switch can deploy LACP has ability of feature active/passive
are there is a way to change management interface from single interface to bond after deployment wizard finish ?
if use active/passive mode i agree since only single interface active and mostly switch can deploy LACP has ability of feature active/passive
are there is a way to change management interface from single interface to bond after deployment wizard finish ?
admin
2,930 Posts
December 16, 2020, 9:58 pmQuote from admin on December 16, 2020, 9:58 pmThere is active/backup bond mode, then there is lacp mode which can be configured active/active or active/passive which allows lacp to be negotiated when both ends are up.
yes you can via the cluster_info.json file posted earlier.
There is active/backup bond mode, then there is lacp mode which can be configured active/active or active/passive which allows lacp to be negotiated when both ends are up.
yes you can via the cluster_info.json file posted earlier.
Bonding for Management Interface
pedro6161
36 Posts
Quote from pedro6161 on December 16, 2020, 9:02 pmHi,
are possible to create bonding interface special for management interface on first time installation from ISO ?
existing i tried PetaSAN 2.7.0, if i enable LACP from my switch, i cannot open deployment wizard, so i disabled first and then i create bonding from deployment wizard and stop(because on backend script creating bonding for management) so i enable immediately on my switch for LACP and then the deployment wizard can finish (node 1 and 2) but for node 3 until 3 hours never finish deploy so i decide to start again from beginning with management interface without LACP, the rest interface(for services) i create bond
Hi,
are possible to create bonding interface special for management interface on first time installation from ISO ?
existing i tried PetaSAN 2.7.0, if i enable LACP from my switch, i cannot open deployment wizard, so i disabled first and then i create bonding from deployment wizard and stop(because on backend script creating bonding for management) so i enable immediately on my switch for LACP and then the deployment wizard can finish (node 1 and 2) but for node 3 until 3 hours never finish deploy so i decide to start again from beginning with management interface without LACP, the rest interface(for services) i create bond
admin
2,930 Posts
Quote from admin on December 16, 2020, 9:30 pmif you want to bond, safest to use active/backup for management and lacp for backend. Many switch models allow you to connect to an lacp switch port before you setup lacp on your nic, then will enable lacp once it is setup which is negotiated between both ends, look for active/passive lacp setting on the switch if it support this. else use active/backup for management. Management typically does not require any bandwidth so active/backup should be no issue. If you really need and your switch does not support negotiation, you can manually set it either via changing the bond type in /opt/petasan/config/cluster_info.json or through the custom script /opt/petasan/scripts/custom/post_start_network.sh which you can configure network as you wish.
if you want to bond, safest to use active/backup for management and lacp for backend. Many switch models allow you to connect to an lacp switch port before you setup lacp on your nic, then will enable lacp once it is setup which is negotiated between both ends, look for active/passive lacp setting on the switch if it support this. else use active/backup for management. Management typically does not require any bandwidth so active/backup should be no issue. If you really need and your switch does not support negotiation, you can manually set it either via changing the bond type in /opt/petasan/config/cluster_info.json or through the custom script /opt/petasan/scripts/custom/post_start_network.sh which you can configure network as you wish.
pedro6161
36 Posts
Quote from pedro6161 on December 16, 2020, 9:42 pmif use active/passive mode i agree since only single interface active and mostly switch can deploy LACP has ability of feature active/passive
are there is a way to change management interface from single interface to bond after deployment wizard finish ?
if use active/passive mode i agree since only single interface active and mostly switch can deploy LACP has ability of feature active/passive
are there is a way to change management interface from single interface to bond after deployment wizard finish ?
admin
2,930 Posts
Quote from admin on December 16, 2020, 9:58 pmThere is active/backup bond mode, then there is lacp mode which can be configured active/active or active/passive which allows lacp to be negotiated when both ends are up.
yes you can via the cluster_info.json file posted earlier.
There is active/backup bond mode, then there is lacp mode which can be configured active/active or active/passive which allows lacp to be negotiated when both ends are up.
yes you can via the cluster_info.json file posted earlier.