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=1000843UP,BROADCAST,RUNNING,MULTICAST,IPv4 mtu
On Wed, 2008-05-21 at 15:09 -0700, Erik Nordmark wrote:
Does the initial placement on something different than vnet1 cause a
problem? Or is it just confusing?
Hi Erik,
In this case it is just causing some confusion but functionality is not
impacted.
Thanks,
Lewis
On Tue, 2008-05-20 at 13:56 -0700, Steve Lawrence wrote:
It is documented here:
http://docs.sun.com/app/docs/doc/819-2450/z.admin.task-60?l=koa=viewq=multipathing
The behavior you are seeing is not specifically documented, but it seems
reasonable. What behavior are you expecting?
Hi
In the global zone, do you have two ip addresses (one on vnet0, one on vnet1)
or is vnet1 configured as standby?
Steve L.
On Wed, May 21, 2008 at 09:12:35AM +0100, Lewis Thompson wrote:
On Tue, 2008-05-20 at 13:56 -0700, Steve Lawrence wrote:
It is documented here:
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
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:
http://docs.sun.com/app/docs/doc/819-2450/z.admin.task-60?l=koa=viewq=multipathing
The behavior you are seeing is not specifically documented, but it seems
