Requirements and Restrictions

Consider the following points when you plan the importing of installed zones into an existing zone cluster or into a new zone cluster:

When you import an installed zone into a new zone cluster, zone properties such as zonepath, ip-type, and brand must be defined in the zone cluster configuration before you run the import-zone command.
The import-zone command can be executed only in the node scope.
The physical host must be specified in the node scope before running the import-zone command.
The local:rad SMF service, svc:/system/rad:local must be online on the physical host hosting the zone to be imported.
The zone to be imported must be in an installed state.
You cannot import an Oracle Solaris Zone that has zone properties such as zonepath, ip-type, and brand that are different from the zone cluster, unless you move the zone to the zone-cluster path using the Oracle Solaris zoneadm move command. See Moving a Non-Global Zone.
The zone to be imported cannot be on a shared storage.
The zone to be imported cannot be configured as a failover highly available zone.
The zone to be imported cannot be part of another zone cluster configuration.
The Oracle Solaris Zone that is imported will be renamed to the zone cluster's name. You will be prompted to accept the renaming of the zone.
When you run the import-zone command in the non-interactive mode, you will need to set an additional flag in order to rename the zone. For example:
```
add node
set physical-host=phost_name
import-zone -y zonename=zone_name
set hostname=host
end
```