Hi @hyoung ho
In AHV, we need to update the interface which we want in that bond so that means it will remove the non-required interface.
Here is the command
nutanix@CVM$ manage_ovs --bridge_name <bridge> --interfaces <interfaces> --require_link=false update_uplinks
Please refer following AHV networking guide for more detail
https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2071-AHV-Networking:BP-2071-AHV-Networking
I have a question.
1. Isn't the manage_ovs command a command that needs to be included in cluster?
2. Is there a way to remove the bond sub-interface from ahv rather than by connecting to cvm from ahv?
3. What should I do if I need to configure ovs before being included in the cluster?
Hi @hyoung ho
In AHV, we need to update the interface which we want in that bond so that means it will remove the non-required interface.
Here is the command
nutanix@CVM$ manage_ovs --bridge_name <bridge> --interfaces <interfaces> --require_link=false update_uplinks
Please refer following AHV networking guide for more detail
https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2071-AHV-Networking:BP-2071-AHV-Networking
I have a question.
1. Isn't the manage_ovs command a command that needs to be included in cluster?
2. Is there a way to remove the bond sub-interface from ahv rather than by connecting to cvm from ahv?
3. What should I do if I need to configure ovs before being included in the cluster?
Hi @hyoung ho
There is a way to do but its not best practice to change from AHV itself that's the reason in guide the steps are mentioned to change from CVM through manage_ovs.
manage_ovs is included in the CVM and not in AHV.
Hello @hyoung ho there is another flag in manage_ovs called --host that may help you here. You can run manage_ovs from a CVM already in the cluster and specify the --host you’d like the operation to execute on.
You could use ovs-vsctl as a last resort if you can’t get manage_ovs to work for you, but you should use caution there and make sure the configuration matches our best practices.
We’re adding a feature in the future that will allow you to configure new nodes automatically as they are added to the cluster from the GUI, so keep an eye out for that in a future release.
Whenever you are doing such type of operation ensure you have IPMI up and running. This way you do not have to visit physical location if host is inaccessible.