This appears to be the affect of selecting an interface that is a member
of an ipmp group in the global zone.

It is documented here:

The behavior you are seeing is not specifically documented, but it seems
reasonable.  What behavior are you expecting?

-Steve L.

On Tue, May 20, 2008 at 03:20:04PM +0100, Lewis Thompson wrote:
> Hi,
> I have a customer who has a basic IPMP config in his global zone:
>    vnet0 & vnet1 [currently vnet0 has the 'floating' IP]
> In addition he has a zone with ip-type=shared where physical=vnet1
> When the zone boots the zone interface gets created on vnet0 instead of
> vnet1
> I have verified this behaviour on a test system and can confirm that the
> zone interface acts in the same way as the floating IP.  i.e. if I run
> 'if_mpadm -d vnet0', then the zone's IP fails over to vnet1
> Unfortunately I can't find any documentation that discusses this
> behaviour.  Is anybody aware of any documents that explain what we are
> seeing?
> Thanks, Lewis
> _______________________________________________
> zones-discuss mailing list
zones-discuss mailing list

Reply via email to