> > 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 > ---------------------- > > Questions: > > 1. I imagine that with vanity naming, this step will be replaced by > something like: > > # dladm rename-link e1000g0 bge0 > > Is this correct? > This could work. But I think the recommended steps would be:
a. when you configure your first zone, you rename the link to something meaningful: # dladm rename bge0 link0 Then when you configure your first zone, it is something like: zonecfg:my-zone> add net zonecfg:my-zone> set physical=link0 b. So when you migrate to another system, the only need to be done is: # dladm rename e1000g0 link0 and the zone configuration doesn't need to be adjusted. > 3. I suppose this is no longer your area, but in case you know the > answer, I'll go ahead and ask. It looks like zone configurations are > done within the zonecfg service, zonecfg:my-zone. Then within that > service, you can specify "subservice" depending on the zone device > you're working on. For example, for network configuration, you go into > the "net" subservice. > > So if you're adding a network device for the first time, you specify > within the zone-cfg:my-zone service the following command: > > zone-cfg:my-zone>add net > zone-cfg:my-zone:net>set physical=bge0 > > Should the dladm rename-link be required to be within the > zone-cfg:my-zone:net service? If yes, how do you switch to that > service so that you can run dladm? 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. Thanks - Cathy
