This content has been marked as final. Show 7 replies
With LDOM you can assign virtual interfaces to the guest domain. You can't assign IPMP groups to guests!
You need to build the IPMP group inside your guest. Another solution is using Link Aggregation in the
Control Domain, but this needs to be supported by your network environment.
Highly recommended to use a management tool and not do all this manually ...
Are all forms of IPMP supported in guest ldom's, as in link based or probe based? Can't remember if there are others. Been a while.
The reason I ask is because I wonder how a guest ldom truly knows about the link level access of ethernet through a vsw0 at the service / io domain level.
Which setups have you used that works in a guest ldom with 2 vnet's
Thank you all.
there's link-based and probe-based IPMP. We use link-based IPMP (in the primary domain and in the guest LDOMs).
For the guest LDOMs you have to set the phys-state linkprop on the vnets if you want to use link-based IPMP:
ldm set-vnet linkprop=phys-state vnetX ldom-name
If you want to use IPMP with vsw interfaces in the primary domain, you have to set the phys-state linkprop in the vswitch:
ldm set-vswitch linkprop=phys-state net-dev=<phys_iface_e.g._igb0> <vswitch-name>
Hi there. The IPMP worked perfectly. Found a resource that shows how to setup a split or dual IO domain with IPMP in the guest domains.
and the guest network config
I setup my systems almost the same as these example and it worked great. Still working on the live migration. Should get that working shortly. Great technology.
Thanks for the feedback