BLOGS HOME PRODUCTS & SERVICES DOWNLOADS SUPPORT PARTNERS COMMUNITIES ABOUT Login

Giri Mandalika's Repository

Something to share

« Oracle Business... | Main | Oracle Business... » About

Benchmark announcements,
Solaris 10: Zone Creation for Dummies HOW-TOs, Tips and
By Giri Mandalika on Jul 19, 2009 Troubleshooting

(Reproducing the three and half year old blog entry, a top 5 one, "as is" from my other blog hosted on blogger.
Search
Source URL: http://technopark02.blogspot.com/2006/02/solaris-10-zone-creation-for-dummies.html)
Enter search term:
About Zones
In its simple form, a zone is a virtual operating system environment created within a single instance of the Solaris Search only this blog
operating system. Efficient resource utilization is the main goal of this technology.
Solaris 10's zone partitioning technology can be used to create local zones that behave like virtual servers. All local Recent Posts
zones are controlled from the system's global zone. Processes running in a zone are completely isolated from the C, Solaris & SPARC M7: Get Defensive
rest of the system. This isolation prevents processes that are running in one zone from monitoring or affecting with Few Techniques .. Part 1/3
processes that are running in other zones. Note that processes running in a local zone can be monitored from global
[Solaris] Memory Leak Checking with
zone; but the processes running in a global zone or even in another local zone cannot be monitored from a local libumem
zone.
New Article on OTN: Oracle Solaris
As of now, the upper limit for the number of zones that can be created/run on a system is 8192; of course, depending Tools for Locality Observability
on the resource availability, a single system may or may not run all the configured zones effectively. Programming in C: Few Tidbits #7
Global Zone Solaris API for Locality Group
Observability
When we install Solaris 10, a global zone gets installed automatically; and the core operating system runs under Solaris 11: Few Random Commands
global zone. To list all the configured zones, we can use zoneadm command: Programming in C: Few Tidbits #6
[Solaris] Clock Synchronization, Max
% zoneadm list -v Username Length, Removable Media
ID NAME STATUS PATH [Solaris] Memory Blacklisting, Duplicate
0 global running / IP Address & Recovery, Group
Package Installations, ..
Solaris: Identifying EFI disks
Global zone is the only one:
bootable from the system hardware Top Tags
to be used for system-wide administrative control, such as physical devices, routing, or dynamic
11.2 analysis analytics benchmark
reconfiguration (DR). ie., global zone is the only zone that is aware of all devices and all file systems
best bi business c c++ certification
from which a non-global zone can be configured, installed, managed, or uninstalled. ie., global zone is the only
zone that is aware of the existence of non-global (local) zones and their configurations. It is not possible to cmt consolidation crm data
create local zones, within a local zone database ebs enterprise f5100 flash
intelligence java locality+group m4000
Steps to create a Local Zone mysql mysqlnd nfs opensolaris
Prerequisites: oracle payroll peoplesoft
performance php practices
Plenty of disk space to hold the newly installed zone. It needs at least 2G space to copy the essential files to programming rdbms server
the local zone, and of course the disk space needed by the application(s) you are planning to run, in this zone;
siebel solaris sparc studio sun
and
t4 t5440 tidbits tips troubleshooting
A dedicated IP for network connectivity
tuning ultrasparc ultrasparct2plus
Basic Zone creation steps with examples: virtualization
1. Check the disk space & network configuration
Categories
Benchmarks
% df -h /
Filesystem size used avail capacity Mounted on Best Practices
/dev/dsk/c1t1d0s0 29G 22G 7.1G 76% / CMT
Enterprise
% ifconfig -a Fix
lo0: flags=2001000849 mtu 8232 index 1
Generic
inet 127.0.0.1 netmask ff000000
eri0: flags=1000843 mtu 1500 index 2 How-To
inet 192.168.74.217 netmask fffffe00 broadcast 192.168.75.255 Java
MySQL
2. Since there is more than 5G free space, I've decided to install a local zone under /zones. Oracle
Performance

converted by W eb2PDFConvert.com
 % mkdir /zones Programming
Solaris
3. Next step is to define/create the zone root. This is the path to zone's root directory that is relative to the Sun
global zone's root directory. Zone root must be owned by root user with the mode 700. This will be used Tips
in setting the zonepath property, during the zone creation process Tools
Troubleshooting
% cd /zones Workaround
% mkdir appserver
% chmod 700 appserver Archives

% ls -l « November 2016
total 2 Sun Mon Tue Wed Thu Fri Sat
drwx------ 2 root root 512 Feb 17 12:46 appserver 1 2 3 4 5
6 7 8 9 10 11 12
4. Create & configure a new 'sparse root' local zone, with root privileges 13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30
% zonecfg -z appserv
appserv: No such zone configured
Use 'create' to begin configuring a new zone. Today
zonecfg:appserv> create
zonecfg:appserv> set zonepath=/zones/appserver Bookmarks
zonecfg:appserv> set autoboot=true ISV Engineering
zonecfg:appserv> add net
Java home
zonecfg:appserv:net> set physical=eri0
zonecfg:appserv:net> set address=192.168.175.126 My External Blog
zonecfg:appserv:net> end MySQL DevZone
zonecfg:appserv> add fs OpenSolaris
zonecfg:appserv:fs> set dir=/repo2 Sun Developer Network
zonecfg:appserv:fs> set special=/dev/dsk/c2t40d1s6
zonecfg:appserv:fs> set raw=/dev/rdsk/c2t40d1s6 Menu
zonecfg:appserv:fs> set type=ufs
zonecfg:appserv:fs> set options noforcedirectio Blogs Home
zonecfg:appserv:fs> end Weblog
zonecfg:appserv> add inherit-pkg-dir Login
zonecfg:appserv:inherit-pkg-dir> set dir=/opt/csw
zonecfg:appserv:inherit-pkg-dir> end Feeds
zonecfg:appserv> info
zonepath: /zones/appserver RSS
autoboot: true All
pool: /Benchmarks
inherit-pkg-dir: /Best Practices
dir: /lib
/CMT
inherit-pkg-dir:
dir: /platform /Enterprise
inherit-pkg-dir: /Fix
dir: /sbin /Generic
inherit-pkg-dir: /How-To
dir: /usr
/Java
inherit-pkg-dir:
dir: /opt/csw /MySQL
net: /Oracle
address: 192.168.175.126 /Performance
physical: eri0
/Programming
zonecfg:appserv> verify
zonecfg:appserv> commit /Solaris
zonecfg:appserv> exit /Sun
/Tips
Sparse Root Zone Vs Whole Root Zone(Updated 05/07/2008) /Tools
/Troubleshooting
In a Sparse Root Zone, the directories /usr, /sbin, /lib and /platform will be mounted as
loopback file systems. That is, although all those directories appear as normal directories under the /Workaround
sparse root zone, they will be mounted as read-only file systems. Any change to those directories in the Comments
global zone can be seen from the sparse root zone. Atom
All
However if you need the ability to write into any of those directories listed above, you may need to
configure a Whole Root Zone. For example, softwares like ClearCase need write permissions to /usr /Benchmarks
directory. In that case configuring a Whole Root Zone is the way to go. The steps for creating and /Best Practices
configuring a new 'Whole Root' local zone are as follows: /CMT
/Enterprise
% zonecfg -z appserv /Fix

converted by W eb2PDFConvert.com
 appserv: No such zone configured /Generic
Use 'create' to begin configuring a new zone. /How-To
zonecfg:appserv> create /Java
zonecfg:appserv> set zonepath=/zones/appserver
/MySQL
zonecfg:appserv> set autoboot=true
zonecfg:appserv> add net /Oracle
zonecfg:appserv:net> set physical=eri0 /Performance
zonecfg:appserv:net> set address=192.168.175.126 /Programming
zonecfg:appserv:net> end
/Solaris
zonecfg:appserv> add inherit-pkg-dir
zonecfg:appserv:inherit-pkg-dir> set dir=/opt/csw /Sun
zonecfg:appserv:inherit-pkg-dir> end /Tips
zonecfg:appserv> remove inherit-pkg-dir dir=/usr /Tools
zonecfg:appserv> remove inherit-pkg-dir dir=/sbin /Troubleshooting
zonecfg:appserv> remove inherit-pkg-dir dir=/lib
/Workaround
zonecfg:appserv> remove inherit-pkg-dir dir=/platform
zonecfg:appserv> info Comments
zonepath: /zones/appserver
autoboot: true
pool:
inherit-pkg-dir:
dir: /opt/csw
net:
address: 192.168.175.126
physical: eri0
zonecfg:appserv> verify
zonecfg:appserv> commit
zonecfg:appserv> exit

Brief explanation of the properties that I added:

\* zonepath=/zones/appserver
Local zone's root directory, relative to global zone's root directory. ie., local zone will have all the bin,
lib, usr, dev, net, etc, var, opt etc., directories physically under /zones/appserver directory
\* autoboot=true
boot this zone automatically when the global zone is booted
\* physical=eri0
eri0 card is used for the physical interface
\* address=192.168.175.126
192.168.175.126 is the IP address. It must have all necessary DNS entries
[Added 08/25/08] The whole add fs section adds the file system to the zone. In this example, the file
system that is being exported to the zone is an existing UFS file system.
\* set dir=/repo2
/repo2 is the mount point in the local zone
\* set special=/dev/dsk/c2t40d1s6 set raw=/dev/rdsk/c2t40d1s6
Grant access to the block (/dev/dsk/c2t40d1s6) and raw (/dev/rdsk/c2t40d1s6) devices so the
file system can be mounted in the non-global zone. Make sure the block device is not mounted
anywhere right before installing the non-global zone. Otherwise, the zone installation may fail with
ERROR: file system check </usr/lib/fs/ufs/fsck> of </dev/rdsk/c2t40d1s6> failed:
exit status <33>: run fsck manually. In that case, unmount the file system that is being
exported, uninstall the partially installed zone (zoneadm -z <zone> uninstall) then install the zone
from the scratch (no need to re-configure the zone, just do a re-install).
\* set type=ufs
The file system is of type UFS
\* set options noforcedirectio
Mount the file system with the option noforcedirectio[/Added 08/25/08]
\* dir=/opt/csw
read-only path, will be lofs'd (loop back mounted) from global zone. Note: it works for sparse root zone
only -- whole root zone cannot have any shared file systems
zonecfg commands verify and commit, verifies and commits the zone configuration for the zone,
respectively. Note that it is not necessary to commit the zone configuration; it will be done automatically
when we exit from zonecfg tool. info displays information about the current configuration

converted by W eb2PDFConvert.com
5. Check the state of the newly created/configured zone

% zoneadm list -cv

ID NAME STATUS PATH
0 global running /
- appserv configured /zones/appserver

6. Next step is to install the configured zone. It takes a while to install the necessary packages

% zoneadm -z appserv install

/zones must not be group writable.
could not verify zonepath /zones/appserver because of the above errors.
zoneadm: zone appserv failed to verify

% ls -ld /zones
drwxrwxr-x 3 root root 512 Feb 17 12:46 /zones

Since /zones must not be group writable, let's change the mode to 700.

% chmod 700 /zones

% ls -ld /zones
drwx------ 3 root root 512 Feb 17 12:46 /zones

% zoneadm -z appserv install

Preparing to install zone .
Creating list of files to copy from the global zone.
Copying <2658> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1128> packages on the zone.
Initialized <1128> packages on zone.
Zone is initialized.
Installation of these packages generated errors:
Installation of <2> packages was skipped.
Installation of these packages generated warnings: <CSWbdb3 CSWtcpwrap
CSWreadline CSWlibnet CSWlibpcap CSWjpeg CSWzlib CSWcommon CSWpkgget SMCethr CSWxpm
SMClsof SMClibgcc SMCossld OpenSSH SMCtar SUNWj3dmx CSWexpat CSWftype2 CSWfconfig
CSWiconv CSWggettext CSWlibatk CSWpango CSWpng CSWtiff CSWgtk2 CSWpcre CSWlibmm
CSWgsed CSWlibtool CSWncurses CSWunixodbc CSWoldap CSWt1lib CSWlibxml2 CSWbzip2
CSWlibidn CSWphp>
The file contains a log of the zone installation.

7. Verify the state of the appserv zone, one more time

% zoneadm list -cv

ID NAME STATUS PATH
0 global running /
- appserv installed /zones/appserver

8. Boot up the appserv zone. Let's note down the ifconfig output to see how it changes after the local zone
boots up. Also observe that there is no answer from the server yet, since it is not up

% ping 192.168.175.126
no answer from 192.168.175.126

% ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
eri0: flags=1000843 mtu 1500 index 2
inet 192.168.74.217 netmask fffffe00 broadcast 192.168.75.255
ether 0:3:ba:2d:0:84

% zoneadm -z appserv boot

zoneadm: zone 'appserv': WARNING: eri0:1: no matching subnet found in netmasks(4) for 192.168.175.126;
using default of 255.255.0.0.

converted by W eb2PDFConvert.com
 % zoneadm list -cv
ID NAME STATUS PATH
0 global running /
1 appserv running /zones/appserver

% ping 192.168.175.126
192.168.175.126 is alive

% ifconfig -a
lo0: flags=2001000849 mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
lo0:1: flags=2001000849 mtu 8232 index 1
zone appserv
inet 127.0.0.1 netmask ff000000
eri0: flags=1000843 mtu 1500 index 2
inet 192.168.74.217 netmask fffffe00 broadcast 192.168.75.255
ether 0:3:ba:2d:0:84
eri0:1: flags=1000843 mtu 1500 index 2
zone appserv
inet 192.168.175.126 netmask ffff0000 broadcast 192.168.255.255

Observe that the zone appserv has it's own virtual instance of lo0, the system's loopback interface and
the zone's IP address is also being served by the eri0 network interface
9. Login to the Zone {console} and performing the internal zone configuration. zlogin utility can be used
to enter a zone. The first time we log in to the console, we get a chance to answer a series of questions
for the desired zone configuraton. -C option of zlogin can be used to log in to the Zone console.

% zlogin -C -e [ appserv
[Connected to zone 'appserv' console]

Select a Language

0. English
1. es
2. fr

Please make a choice (0 - 2), or press h or ? for help: 0

Select a Locale

0. English (C - 7-bit ASCII)

1. Canada (English) (UTF-8)
2. Canada-English (ISO8859-1)
3. U.S.A. (UTF-8)
4. U.S.A. (en_US.ISO8859-1)
5. U.S.A. (en_US.ISO8859-15)
6. Go Back to Previous Screen

Please make a choice (0 - 6), or press h or ? for help: 0

...

Enter the host name which identifies this system on the network. The name
must be unique within your domain; creating a duplicate host name will cause
problems on the network after you install Solaris.

A host name must have at least one character; it can contain letters,
digits, and minus signs (-).

Host name for eri0:1 appserv v440appserv

...
...

System identification is completed.

...

rebooting system due to change(s) in /etc/default/init

[NOTICE: Zone rebooting]

converted by W eb2PDFConvert.com
 SunOS Release 5.11 Version snv_23 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: v440appserv

v440appserv console login: root

Password:
Feb 17 15:15:30 v440appserv login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 snv_23 October 2007

That is all there is in the creation of a local zone. Now simply login to the newly created zone, just like connecting to
any other system in the network.
[New 08/27/2008] Mounting file systems in a non-global zone
Sometimes it might be necessary to export file systems or create new file systems when the zone is already running.
This section's focus is on exporting block devices and the raw devices in such situations i.e., when the local zone is
already configured.
Exporting the Raw Device(s) to a non-global zone
If the file system does not exist on the device, raw devices can be exported as they are, so the file system can be
created inside the non-global zone using the normal newfs command.
The following example shows how to export the raw device to a non-global zone when the zone is already configured.

# zonecfg -z appserv
zonecfg:appserv> add device
zonecfg:appserv:device> set match=/dev/rdsk/c5t0d0s6
zonecfg:appserv:device> end
zonecfg:appserv> verify
zonecfg:appserv> commit
zonecfg:appserv> exit

In this example /dev/rdsk/c5t0d0s6 is being exported.

After the zonecfg step, reboot the non-global zone to make the raw device visible inside the non-global zone. After the
reboot, check the existence of the raw device.

# hostname
v440appserv

# ls -l /dev/rdsk/c5t0d0s6
crw-r----- 1 root sys 118, 126 Aug 27 14:33 /dev/rdsk/c5t0d0s6

Now that the raw device is accessible within the non-global zone, we can use the regular Solaris commands to
create any file system like UFS.
eg.,

# newfs -v c5t0d0s6
newfs: construct a new file system /dev/rdsk/c5t0d0s6: (y/n)? y
mkfs -F ufs /dev/rdsk/c5t0d0s6 1140260864 -1 -1 8192 1024 251 1 120 8192 t 0 -1 8 128 n
Warning: 4096 sector(s) in last cylinder unallocated
/dev/rdsk/c5t0d0s6: 1140260864 sectors in 185590 cylinders of 48 tracks, 128 sectors
556768.0MB in 11600 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
...............................................................................
...............................................................................
.........................................................................
super-block backups for last 10 cylinder groups at:
1139344160, 1139442592, 1139541024, 1139639456, 1139737888, 1139836320,
1139934752, 1140033184, 1140131616, 1140230048

Exporting the Block Device(s) to a non-global zone

If the file system exists on the device, block devices can be exported as they are, so the file system can be mounted
inside the non-global zone using the normal Solaris command, mount.

converted by W eb2PDFConvert.com
The following example shows how to export the block device to a non-global zone when the zone is already
configured.

# zonecfg -z appserv
zonecfg:appserv> add device
zonecfg:appserv:device> set match=/dev/dsk/c5t0d0s6
zonecfg:appserv:device> end
zonecfg:appserv> verify
zonecfg:appserv> commit
zonecfg:appserv> exit

In this example /dev/dsk/c5t0d0s6 is being exported.

After the zonecfg step, reboot the non-global zone to make the block device visible inside the non-global zone. After
the reboot, check the existence of the block device; and mount the file system within the non-global zone.

# hostname
v440appserv

# ls -l /dev/dsk/c5t0d0s6
brw-r----- 1 root sys 118, 126 Aug 27 14:40 /dev/dsk/c5t0d0s6

# fstyp /dev/dsk/c5t0d0s6
ufs

# mount /dev/dsk/c5t0d0s6 /mnt

# df -h /mnt
Filesystem size used avail capacity Mounted on
/dev/dsk/c5t0d0s6 535G 64M 530G 1% /mnt

Mounting a file system from the global zone into the non-global zone
Sometimes it is desirable to have the flexibility of mounting a file system in the global zone or non-global zone on-
demand. In such situations, rather than exporting the file systems or block devices into the non-global zone, create
the file system in the global zone and mount the file system directly from the global zone into the non-global zone.
Make sure to unmount that file system in the global zone if mounted, before attempting to mount it in the non-global
zone.
eg.,
In the non-global zone:

# mkdir /repo1

In the global zone:

# df -h /repo1
/dev/dsk/c2t40d0s6 134G 64M 133G 1% /repo1

# umount /repo1

# ls -ld /zones/appserv/root/repo1
drwxr-xr-x 2 root root 512 Aug 27 14:45 /zones/appserv/root/repo1

# mount /dev/dsk/c2t40d0s6 /zones/appserv/root/repo1

Now go back to the non-global zone and check the mounted file systems.

# hostname
v440appserv

# df -h /repo1
Filesystem size used avail capacity Mounted on
/repo1 134G 64M 133G 1% /repo1
To unmount the file system from the non-global zone, run the following command from the global zone.

# umount /zones/appserv/root/repo1

converted by W eb2PDFConvert.com
Removing the file system from the non-global zone
eg.,
Earlier in the zone creation step, the block device /dev/dsk/c2t40d1s6 was exported and mounted on the mount
point /repo2 inside the non-global zone. To remove the file system completely from the non-global zone, run the
following in the global zone.

# zonecfg -z appserv
zonecfg:appserv> remove fs dir=/repo2
zonecfg:appserv> verify
zonecfg:appserv> commit
zonecfg:appserv> exit

Reboot the non-global zone for this setting to take effect.

Shutting down and booting up the local zones (Updated 01/15/2008)
1. To bring down the local zone:

% zlogin appserv shutdown -i 0

2. To boot up the local zone:

% zoneadm -z appserv boot

Just for the sake of completeness, the following steps show how to remove a local zone.
Steps to delete a Local Zone
1. Shutdown the local zone

% zoneadm -z appserv halt

% zoneadm list -cv

ID NAME STATUS PATH
0 global running /
- appserv installed /zones/appserver

2. Uninstall the local zone -- remove the root file system

% zoneadm -z appserv uninstall

Are you sure you want to uninstall zone appserv (y/[n])? y

zoneadm list -cv

ID NAME STATUS PATH
0 global running /
- appserv configured /zones/appserver

3. Delete the configured local zone

% zonecfg -z appserv delete

Are you sure you want to delete zone appserv (y/[n])? y

zoneadm list -cv

ID NAME STATUS PATH
0 global running /

[New: 07/14/2009]
Cloning a Non-Global Zone
The following instructions are for cloning a non-global zone on the same system. The example shown below clones
the siebeldb zone. After the cloning process, a brand new zone oraclebi emerges as a replica of siebeldb zone.
eg.,

# zoneadm list -cv

converted by W eb2PDFConvert.com
 ID NAME STATUS PATH BRAND IP
0 global running / native shared
- siebeldb installed /zones/dbserver native excl

1. Export the configuration of the zone that you want to clone/copy

# zonecfg -z siebeldb export > /tmp/siebeldb.config.cfg

2. Change the configuration of the new zone that differ from the existing one -- for example, IP address,
data set names, network interface etc. To make these changes, edit /tmp/siebeldb.config.cfg
3. Create the zone root directory for the new zone being created

# mkdir /zones3/oraclebi
# chmod 700 /zones3/oraclebi
# ls -ld /zones3/oraclebi
drwx------ 2 root root 512 Mar 12 15:41 /zones3/oraclebi

4. Create a new (empty, non-configured) zone in the usual manner with the edited configuration file as an
input

# zonecfg -z oraclebi -f /tmp/siebeldb.config.cfg

# zoneadm list -cv

ID NAME STATUS PATH BRAND IP
0 global running / native shared
- siebeldb installed /zones/dbserver native excl
- oraclebi configured /zones3/oraclebi native excl

5. Ensure that the zone you intend to clone/copy is not running

# zoneadm -z siebeldb halt

6. Clone the existing zone

# zoneadm -z oraclebi clone siebeldb

Cloning zonepath /zones/dbserver...

This step takes at least 5 minutes to clone the whole zone. Larger zones may take longer to complete
the cloning process.
7. Boot the newly created zone

# zoneadm -z oraclebi boot

Bring up the halted zone (the source zone) as well, if wish.

8. Login to the console of the new zone to configure IP, networking, etc., and you are done.

# zlogin -C oraclebi

[New: 07/15/2009]
Migrating a Non-Global Zone from One Host to Another
Keywords: Solaris, Non-Global Zone, Migration, Attach, Detach
The following instructions demonstrate how to migrate the non-global zone, orabi to another server with examples.

# zoneadm list -cv

ID NAME STATUS PATH BRAND IP
0 global running / native shared
4 siebeldb running /zones/dbserver native excl
- orabi installed /zones3/orabi native shared

converted by W eb2PDFConvert.com
1. Halt the zone to be migrated, if running

# zoneadm -z orabi halt

2. Detach the zone. Once detached, it will be in the configured state

# zoneadm -z orabi detach

# zoneadm list -cv

ID NAME STATUS PATH BRAND IP
0 global running / native shared
4 siebeldb running /zones/dbserver native excl
- orabi configured /zones3/orabi native shared

3. Move the zonepath for the zone to be migrated from the old host to the new host.
Do the following on the old host:

# cd /zones3
# tar -Ecf orabi.tar orabi
# compress orabi.tar

# sftp newhost
Connecting to newhost...
sftp> cd /zones3
sftp> put orabi.tar.Z
Uploading orabi.tar.Z to /zones3/orabi.tar.Z
sftp> quit

On the newhost:

# cd /zones3
# uncompress orabi.tar.Z
# tar xf orabi.tar

4. On the new host, configure the zone.

Create the equivalent zone orabi on the new host -- use the zonecfg command with the -a option and
the zonepath on the new host. Make any required adjustments to the configuration and commit the
configuration.

# zonecfg -z orabi
orabi: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:orabi> create -a /zones3/orabi
zonecfg:orabi> info
zonename: orabi
zonepath: /zones3/orabi
brand: native
autoboot: false
bootargs:
pool:
limitpriv: all,!sys_suser_compat,!sys_res_config,!sys_net_config,!sys_linkdir,!sys_devices,!sys_config,!proc_zone,!dtrace_k
scheduling-class:
ip-type: shared
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
net:
address: IPaddress
physical: nxge1
defrouter not specified
zonecfg:orabi> set capped-memory

converted by W eb2PDFConvert.com
 zonecfg:orabi:capped-memory> set physical=8G
zonecfg:orabi:capped-memory> end
zonecfg:orabi> commit
zonecfg:orabi> exit

5. Attach the zone on the new host with a validation check and update the zone to match a host running
later versions of the dependent packages

# ls -ld /zones3
drwxrwxrwx 5 root root 512 Jul 15 12:30 /zones3
# chmod g-w,o-w /zones3
# ls -ld /zones3
drwxr-xr-x 5 root root 512 Jul 15 12:30 /zones3

# zoneadm -z orabi attach -u

Getting the list of files to remove
Removing 1740 files
Remove 607 of 607 packages
Installing 1878 files
Add 627 of 627 packages
Updating editable files
The file within the zone contains a log of the zone update.

# zoneadm list -cv

ID NAME STATUS PATH BRAND IP
0 global running / native shared
- orabi installed /zones3/orabi native shared

Note:
It is possible to force the attach operation without performing the validation. You can do so with the help
of -F option

# zoneadm -z orabi attach -F

Be careful when using this option because it could lead to an incorrect configuration; and an incorrect
configuration could result in undefined behavior
[New: 07/19/2009]
Tip: How to find out whether connected to the primary OS instance or the virtual instance?
If the command zonename returns global, then you are connected to the OS instance that was booted from the
physical hardware. If you see any string other than global, you might have connected to the virtual OS instance.
Alternatively try running prstat -Z or zoneadm list -cv commands. If you see exactly one non-zero Zone ID, it is
an indication that you are connected to a non-global zone.
Suggested reading:
System Administration Guide: Solaris Containers-Resource Management and Solaris Zones
Zones and Containers FAQ at opensolaris.org
Zones : Unofficial FAQ

Category: Solaris ::: Tags: containers how-to solaris virtualization zones :::
Permanent link to this entry :::

« Oracle Business... | Main | Oracle Business... »

C o m m e n t s :

Great post and draw. Thank you for sharing.!!@!

Posted by links of london on November 25, 2009 at 10:28 AM PST #

Hey,
I want to install TOP package.

converted by W eb2PDFConvert.com
When I logon to these zone server can I install TOP and have it working?

Thanks, Joe

Posted by Joe on June 10, 2010 at 11:47 AM PDT #

Hi dear,

thanks for the nice tutorial.

now I need to implement.

- Kiran. N.

00 91 800 888 3643.

Posted by Kiran on July 08, 2010 at 05:42 PM PDT #

how come when i reset the server my local zones loose their Ethernet ports and they have to be plumbed at
the global level before they can boot?

Posted by guest on October 05, 2011 at 12:47 AM PDT #

This tutorial is really nice..!! It helped a lot.. Many many thanks.

Posted by Saurabh on March 26, 2012 at 11:54 PM PDT #

great and well explicit post..thanks for sharing this knowledge...

Posted by guest on January 16, 2013 at 06:44 AM PST #

Good information you have shared. Thanks a Lot!!

Posted by guest on February 13, 2014 at 08:40 PM PST #

Very nice, informative, to the point and implementable post. Would appreciate if you can have a similar post
for installing oracle cluster 4.0 for implementing a two node oracle RAC DB with ZFS filessystem on single
physical machine using two non-global zones...or even if you can re-direct me to any good
posts/documentation explaining the same as I couldn't find any satisfactory resource on this topic.

Thanks a ton.

Posted by guest on July 18, 2014 at 02:59 PM PDT #

Pertaining to the following section:

Exporting the Raw Device(s) to a non-global zone

I found that I could not newfs the device partition in the zone if the block device was not presented.

# newfs /dev/rdsk/c1t30s0
newfs: construct a new file system /dev/rdsk/c1t3d0s0: (y/n)? y
can't check mount point; can't stat
#

The following more accurately addresses the procedure

bash-3.2# zonecfg -z zone1

zonecfg:zone1> add device
zonecfg:zone1:device> set match=/dev/dsk/c1t3d0s6
zonecfg:zone1:device> end
zonecfg:zone1> add device
zonecfg:zone1:device> set match=/dev/rdsk/c1t3d0s6
zonecfg:zone1:device> end
zonecfg:zone1> verify
zonecfg:zone1> commit

converted by W eb2PDFConvert.com
zonecfg:zone1> exit
bash-3.2#

This would coincide with:

System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones
How to Import Raw and Block Devices by Using zonecfg
http://docs.oracle.com/cd/E19455-01/817-1592/z.admin.task-11/index.html

Posted by Paul Buckley on July 29, 2014 at 09:27 AM PDT #

P o s t a C o m m e n t :
Name:
guest
E-Mail:

URL:

Notify me by email of new comments

Remember Information?
Your Comment:

HTML Syntax: NOT allowed

Please answer this simple math question

5 + 96 =

Preview Post

The views expressed on this blog are those of the author and do not necessarily reflect the views of Oracle. Terms of Use | Your Privacy Rights | Cookie Preferences

converted by W eb2PDFConvert.com