Seems like a feature. vnet1 is in standby, so the active link in the ipmp group (vnet0) is used for the zones.
Is the desire to have both interfaces used by zones for additional bandwidth? Do the zones need ipmp as well, or is it ok if a link failure takes out some of the zones? I'm guessing zones should be on ipmp. Perhaps someone on the ldoms team can suggest a configuration. My guess would be to configure two more vnets (2 and 3) on the same underlying network interfaces, and create another ipmp group. Something like this: vnet0 -> e1000g0 vnet1 -> e1000g1 vnet2 -> e1000g0 vnet3 -> e1000g1 ipmp group 1 vnet0 -> active vnet1 -> standby ipmp group 2 vnet2 -> standby vnet3 -> active Put some zones in group 1 and other zones in group 2. I don't know if this is possible. I don't know how ldoms map vnets to physical interfaces. -Steve L. On Thu, May 22, 2008 at 03:59:07PM +0100, Lewis Thompson wrote: > On Wed, 2008-05-21 at 12:56 -0700, Steve Lawrence wrote: > > In the global zone, do you have two ip addresses (one on vnet0, one on > > vnet1) > > or is vnet1 configured as standby? > > Hi Steve, > > We have the following global zone config: > > vnet0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 > index 2 > inet 184.108.40.206 netmask ffffff80 broadcast 220.127.116.11 > groupname sldn2680vpgd > ether a0:0:8b:95:28:c8 > vnet0:1: > flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu > 1500 index 2 > inet 18.104.22.168 netmask ffffff80 broadcast 22.214.171.124 > vnet1: > flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER,STANDBY,INACTIVE> > mtu 1500 index 3 > inet 126.96.36.199 netmask ffffff80 broadcast 188.8.131.52 > groupname sldn2680vpgd > ether 0:14:4f:fa:31:5c > > And then on top of this we end up with an addition vnet0 virtual > interfaces per zone. > > A full explorer is available > at /net/cores.uk/export/calls/38083839/explorer > > Thanks, Lewis > > _______________________________________________ > zones-discuss mailing list > firstname.lastname@example.org _______________________________________________ zones-discuss mailing list email@example.com