|Skip Navigation Links|
|Exit Print View|
|System Administration Guide: Oracle Solaris Zones, Oracle Solaris 10 Containers, and Resource Management Oracle Solaris 11 Express 11/10|
Depending on the services performed by the original system, the global administrator or a user granted the appropriate authorizations might need to manually customize the zone after it has been installed. For example, the privileges assigned to the zone might need to be modified. This is not done automatically. Also, because not all system services work inside zones, not every Oracle Solaris 10 system is a good candidate for migration into a zone.
To begin, examine the source system and collect needed information.
Obtain the hostname:
Obtain the host ID:
Also see Host ID in Zones.
Obtain the RPC domainname:
Obtain the root password.
View the software being run on the system:
# ps -eaf
Check the networking utilized on the system:
# ifconfig -a
View the storage utilized, for example, by viewing the contents of /etc/vfstab.
View the amount of local disk storage in use, which determines the size of the archive:
# df -k
Determine the packages and patches that are on the system. To use the Oracle Solaris 10 package and patch tools in your Oracle Solaris 10 Container, ensure that patch 119254-75 (SPARC) or 119255-75 (x86/x64) has been installed on your Solaris 10 system before the image is created.
Examine the contents of /etc/system to view the update level of the Oracle Solaris 10 system.
Note - If there are any native non-global zones on the system to be migrated, these zones must either be deleted, or be archived and moved into zones on the new target system first. For a sparse root zone, the archive must be made with the zone in the ready state. For additional information on migration, see Chapter 29, (Optional) Migrating an Oracle Solaris 10 native Non-Global Zone Into an Oracle Solaris 10 Container. For additional information on sparse root zones, see Zones Overview in the Oracle Solaris 10 documentation.