SDN Private Network on bonded interface?
-
Greetings,
I'm trying to test out the SDN feature during my trial. I have 2 hosts set up the same with 3 connected interfaces each. One 1G interface where Management is and two 25G interfaces that I created a bond at the Pool level. The bond is working fine for my guests.
When I create a new network, if I immediately select the interface dropdown, I see bond0 as an option. If I choose the Private Network toggle, the only option available for interface is eth0, the 1G interface.
Is this expected behavior? Why wouldn't the bond be an available option?
If this is not expected, the one weirdness that I can think of is that I initially created this cluster on XO and set up the bond. I then wanted to play with XOA and imported the cluster. So, maybe there is some weirdness there and I need to remove and recreate the bond interface to get XOA to properly see it.
Any other ideas?
Thanks!
-
Question for @Team-XAPI-Network
-
@dcskinner No this is not intend, I just ran some tests, my host has a bond for management, which showed up in the dropdown.
Then I created a second bond, it did not show in the dropdown until I actually configure it. When creating it, it was actually created by default with "mode=none" so I went to the host's network tab, chose static and assigned an IP to it and it was then showing in the dropdown. Are you sure your bond is properly configured?
-
Hopefully the palm print on my forehead isn't visible from where you are sitting.
Of course the interface needs an IP address.
In my defense, normally for something like this, I wouldn't put it on the bonded interface with all the trunked VLAN's for guest traffic (we don't give that one an IP) and it would go on the other bonded interface that isn't trunked and does get an IP, but these are test hosts and I didn't set up the other bond, so it is pulling double duty.
I was able to set the IP's and get SDN working.
Thanks!
