Cathy Zhou wrote:
>
>>
>> In the procedure to migrate zone, one step is to switch network device
>> in case the zone is migrated to a system that has a different device
>> from the host where the zone was originally set up. The step is as
>> follows:
>>
>> ----------------------
>> Step 8: (Optional) Make any required adjustments to the configuration.
>>
>> For example, the network physical device might be different on the new
>> host, or devices that are part of the configuration might have
>> different names on the new host.
>>
>> zonecfg:my-zone> select net physical=bge0
>> zonecfg:my-zone:net> set physical=e1000g0
>> zonecfg:my-zone:net> end
>>
>> (NOTE: The original device of the zone is bge0. The device in the
>> destination host is e1000g0
>> ----------------------
Cathy and Raoul,
where does the above text come from?
I don't think it works when there is IPv6 i.e. there are two net
resources that would match the "select net physical=bge0".
So we should get that text fixed.
> Do you mean rename-link in a zone? My understanding is, at this time,
> zone interfaces are really just logical interfaces, so that a
> system-unique link name should suffice. So that we only need to rename
> links in the global zone using dladm. In the future, after stack
> instance and VNICs are there, it is possible that zone-unique link name
> is needed - but we need to know more what's the usage model for that
> before we support that capability.
There aren't any current plans to introduce per-zone names for network
interfaces. Thus dladm would manage the global set of link names.
(Folks have suggested that it would be nice to be able to give each zone
a fixed name, but that means the global zone admin has to track the
mapping between the global names and the per-zone names.)
Erik
