1. So easy your mom could administer it
ZFS is administered by two commands, zpool and zfs. Most tasks typically require a single command to accomplish. And the commands are designed to make sense. For example, check out the commands to place a quota on its size.

2. Honkin’ big filesystems
How big do filesystems need to be? In a world where 640KB is certainly not enough for computer memory, current filesystems have reached or are reaching the end of their usefulness. A 64-bit filesystem would meet today’s need, but estimate of the lifetime of a 64-bit filesystem is about 10 years. Extending to 128-bits gives ZFS an expected lifetime of 30 years (UFS, for comparison, is about 20 years old). So how much data can you squeeze into a 128-bit filesystem? 16 exabytes or 18 million terabytes. How many files can you cram into a ZFS filesystem? 200 million million.

Could anyone use a filesystem that large? No, not really. The topic has roused discussions about boiling the oceans if a real life storage unit that size was powered on. It may not be necessary to have 128 bits, but it doesn’t hurt and we won’t have to worry about running out of addressable space.

3. Filesystem, heal thyself
ZFS employs 256 bit checksums end-to-end to validate data stored under its protection. Most filesystems (and you know who you are) depend on the underlying hardware to detect corrupted data and then can only nag about it if they get such a message. Every block in a ZFS filesystem has a checksum associated with it. If ZFS detects a checksum mismatch on a raidz or mirrored filesystem, it will actively reconstruct the block from the available redundancy and go on about its job.

4. fsck off, fsck
fsck has been voted out of the house. We don’t need it anymore. Because ZFS data are always consistent on disk, don’t be afraid to yank out those power cords if you feel like it. Your ZFS filesystems will never require you to enter the superuser password for maintenance mode.

5. Compress to your heart’s content
I’ve always been a proponent of optional and appropriate compression in filesystems. There are some data that are well suited to compression such as server logs. Many people get ruffled up over this topic, although I suspect that they were once burned by double space munching up an important document. When thoughtfully used, ZFS compression can improve disk I/O which is a common bottleneck. ZFS compression can be turned on for individual filesystems or hierarchies with a very easy single command.

6. Unconstrained architecture
UFS and other filesystems use a constrained model of fixed partitions or volumes, each filesystem having a set amount of available disk space. ZFS uses a pooled storage model. This is a significant departure from the traditional concept of filesystems. Many current production systems may have a single digit number of filesystems and adding or manipulating existing filesystems in such an environment is difficult.

In ZFS, mounted in different places in the host filesystem.

7. Grow filesystems without green thumb
If your pool becomes overcrowded, you can grow it. With one command. On a live production system. Enough said.

8. Dynamic striping
On by default, dynamic striping automatically includes all devices in a pool in writes simultaneously (stripe width spans all the available media). This will speed up the I/O on systems with multiple paths to storage by load balancing the I/O on all of the paths.

9. The term “raidz” sounds so l33t
The new RAID-Z redundant storage model replaces RAID-5 and improves upon it. RAID-Z does not suffer from the “write hole” in which a stripe of data becomes corrupt because of a loss of power during the vulnerable period between writing the data and the parity. RAID-Z, like RAID-5, can survive the loss of one disk. A future release is planned using the keyword raidz2 which can tolerate the loss of two disks. Perhaps the best feature is that creating a raidz pool is crazy simple.

10. Clones with no ethical issues
The simple creation of restored to the original filesystem to return to the previous state. Snapshots can be written to other storage (disk, tape), transferred to another system, and converted back into a filesystem.

* Root user is not able to telnet remotely?
Ans. -: By Default remote console login is disabled for root, you need to manually comment this line.
# /etc/default/login
CONSOLE=/dev/console (comment to this line)

* Root user is not able to FTP remotely?
Ans. -: By Default FTP login is disabled for root user, you need to manually comment this line.
# /etc/ftpd/ftpusers
Root (comment to root user)

* How to check Solaris Installed Packages?
Ans. -: # pkginfo | grep package name (ftp/bash)
# pkgchk –v SUNWapchr
-v -: To list the files contained in a software package

* How to install Software Packages?
Ans. -: # pkgadd –d package named
# pkgadd -d . (For entire packages those are belong to current working directory)

* How to check Physical Memory?
Ans. -: To check the physical memory and system configuration
1) prtconf
2) prtdiag

* How to check Physical Memory Bank size or Socket status?
Ans. -: # /usr/sbin/prtdiag
# /usr/platform/sun4u/sbin/prtdiag
===============Memory Configuration ===============
Logical Logical Logical
MC Bank Bank Bank DIMM Interleave Interleaved
Brd ID num size Status Size Factor with
—- — —- —— ———– —— ———- ———–
CA 0 0 1024MB no_status 512MB 2-way 0
CA 0 2 1024MB no_status 512MB 2-way 0
===========================================

* What is means Prtdiag?
A simple command will provide detailed information about the specific memory configuration of a Sun server, information such as the sizes and locations of memory banks. This can prevent cracking open the case and the associated downtime
The prtdiag command displays useful information about the processors, IO devices, and memory attached to the system. The only trick is finding the program. It lives under the /usr/platform directory in a subdirectory corresponding to the hardware platform on which it is running. If you change directory to /usr/platform and look at the directory listing, you’ll see a product catalog of Sun hardware and some generic platform types (like sun4u). Identify the platform you are on (uname -i will work nicely), change into that directory, and then into the sbin subdirectory there. For example, on a Sun V210, the path would be /usr/platform/SUNW, Sun-Fire-V210/sbin

* How to understand Solaris OS Kernel & hardware parameters stuffs?
Ans. -: # uname
-a Prints basic information currently available
from the system.
-i Prints the name of the platform.
-m Prints the machine hardware name (class). Use of this option is is courage. Use uname -p instead. See NOTES section below.
-n Prints the nodename (the nodename is the name by which the system is known to a communications network).
-p Prints the current host’s ISA or processor type.
-r Prints the operating system release level.
-s Prints the name of the operating system.
This is the default.

* How to see following parameters?

(Hostname, host id, release, kernel architecture, hardware provider, kernel version)

Ans. -: # /usr/bin/showrev

Hostname: sh2sol8

Hostid: 8316e021

Release: 5.8

Kernel architecture: sun4u

Application architecture: sparc

Hardware provider: Sun_Microsystems

Domain: sharedsvrs

Kernel version: SunOS 5.8 Generic 117350-49 Jul 2007

* How to see Patch and package revision Information?

Ans. -: # /usr/bin/showrev –p

-p -: Print only the revision information about Patches.

It will show result in following format.

Patch: 120846-03 Obsoletes: 121906-01, 123355-03 Requires:  Incompatibles:  Packages: SUNWcsu, SUNWcsr, SUNWcsl, SUNWhea

Patch -:

Obsoletes -:

Requires -:

Incompatibles -:

Packages -:

* How to see command revision Information?

Ans. -:  # /usr/bin/showrev –c

-c -: Print the revision information about command.

Example -:  # showrev -c /usr/sbin/showmount

PATH is:

/usr/sbin:/usr/bin

PWD is:

/export/home

LD_LIBRARY_PATH is not set in the current environment

________________________________________________________________________

File: /usr/sbin/showmount

=========================

File type: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, stripped

Command version: SunOS 5.10 Generic January 2005

File mode: r-xr-xr-x

User owning file: root

Group owning file: bin

Library information:

        librpcsvc.so.1 =>        /lib/librpcsvc.so.1

        libnsl.so.1 =>   /lib/libnsl.so.1

        libc.so.1 =>     /lib/libc.so.1

        libmp.so.2 =>    /lib/libmp.so.2

        libmd5.so.1 =>   /lib/libmd5.so.1

        libscf.so.1 =>   /lib/libscf.so.1

        libdoor.so.1 =>  /lib/libdoor.so.1

        libuutil.so.1 =>         /lib/libuutil.so.1

        libm.so.2 =>     /lib/libm.so.2

Sum: 44186

* What is LSB in above examples?

Ans. -: LSB (Linux Standard Base)

By enabling this functionality, code-named Project Janus, administrators can create an environment for running a range of Linux applications at near-native speeds. Sun is offering Project Janus as an optional kernel service of the Solaris OS, enabling administrators to run Linux applications in a new and unique way on x86 platforms. In keeping with Sun’s long-standing support of industry standards, Project Janus is designed for compliance with the Linux Standard Base specification.

* How to see detailed information about package?

Ans. -: # pkginfo – l PackageName

To show detailed information about a patch. It will show in following format.

# pkginfo – l SUNWapchr

   PKGINST:  SUNWapchr

      NAME:  Apache Web Server (root)

  CATEGORY:  system

      ARCH:  i386

   VERSION:  11.10.0, REV=2005.01.08.01.09

   BASEDIR:  /

    VENDOR:  Sun Microsystems, Inc.

      DESC:  The Apache HTTP server program (1.3.x) (root components)

    PSTAMP:  sfw10-patch-x20060908084658

  INSTDATE:  Jul 09 2007 17:59

   HOTLINE:  Please contact your local service provider

    STATUS:  completely installed

     FILES:      302 installed pathnames

                  11 shared pathnames

                   5 linked files

                  23 directories

                   3 executables

                 669 blocks used (approx)

* How to monitor system Load?

Ans. -: # vmstat 1

The 1 specifies the number of seconds between updates

To get a quick feel for the system load, look at the last and first columns. The last column is the CPU idle (larger is better); a very busy system will show zero. The first column is the number of processes waiting for the CPU. The uptime load is an average of this value over periods of time. The number of waiting processes should be less than 4 times the number of processors in the system for optimal load.

The swap and memory columns display the amount of free swap space and physical memory in KB. The pi and po columns show the number of KB pages in and out of memory, respectively. If these values are consistently very high, they may indicate a need for more physical memory.
The columns under the disk category show the number of disk operations per second. The s columns represent different disks on the system.

* How to check Solaris running process?

Ans. -: # prstat    

Prstat will list all the UNIX process in order of which are using the most CPU time first.

Sort the processes by which process are using the most memory.

# prstat – s size

* How to see processor status?

Ans. -: # psrinfo

It will show status of the processor like online and how much count will be there.

-v -: display additional information about processor.

# psrinfo -v

Status of processor 0 as of: 05/20/08 17:35:09

  Processor has been on-line since 05/05/08 19:05:39.

  The sparcv9 processor operates at 750 MHz,

        and has a sparcv9 floating point processor.

Status of processor 1 as of: 05/20/08 17:35:09

  Processor has been on-line since 05/05/08 19:05:41.

  The sparcv9 processor operates at 750 MHz,

        and has a sparcv9 floating point processor.

* How to see processor statistic and individual CPU usage?

Ans. -: # mpstat

CPU minf mjf xcal  intr ithr  csw icsw migr smtx  srw syscl  usr sys  wt idl

  0   20   0  345  1191  514  207   29   13   15    0   563    3   1   1  95

  1   18   0   59   357  340  203   27   13   15    0   571    3   2   1  94

minf            minor faults

mjf             major faults

xcal            inter-processor cross-calls

intr            interrupts

ithr            interrupts as threads  (not  counting  clock interrupt)

csw             context switches

icsw            involuntary context switches

migr            thread migrations (to another processor)

smtx            spins on mutexes (lock not acquired on first try)

srw             spins  on  readers/writer  locks  (lock  not acquired on first try)

syscl           system calls

wt              the I/O wait time is no longer calculated as a percentage of CPU time, and this                      statistic will always return zero.

idl             percent idle time

sze             number of processors in the  requested  processor set

* How to see virtual Memory statistic?

Ans. -: # vmstat

Vmstat reports virtual memory statistics regarding kernel thread, virtual memory, and disk, trap, and CPU activity.

* How to check nfs statistic?

Ans. -: # nfsstat

Nfsstat displays statistical information about the NFS and RPC (Remote Procedure Call), interfaces to the kernel.

* What is the use of cfgadm command?

Ans. -:  # cfgadm

The cfgadm command provides configuration administration operations on dynamically reconfigurable hardware resources.

* How to configure Virtual IP in Solaris?

Ans. -:

1) Create /etc/hostname.<interfacename> :< n> containing the hostname of the virtual IP
   #/etc/hostname.hme0:1
2) Add the hostname and virtual IP to /etc/hosts
3) Use the following commands to configure the interface:
   ifconfig <interfacename>:<n> plumb
   # ifconfig hme0:1 plumb
   ifconfig <interfacename>:<n> <IP address> netmask <netmask> broadcast + up
  # Ifconfig hme0:1 192.168.0.100 netmask 255.255.255.0 broadcast + up

* How to check following parameters or system drivers?

(Hardware devices, pseudo devices, system devices, loadable modules and kernel Tunable parameters)

Ans. -: # sysdef

* Where & How to set PATH in solaris (permanently)?

Ans. -: Set path in /etc/profile file

 # vi /etc/profile

PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin

export  PATH  

* How to check solaris Opened Ports and listen, established connection?

Ans. -: # netstat -a 

It will show you network statics 

* How to see default routes in solaris?

Ans. -: # netstat -rn

* How to see which Interface is used for network traffic?

Ans. -: # netstat -ia

-i -: Show the state of the interfaces that are  used  for  IP traffic. Normally this shows statistics for the physical interfaces. When combined with the -a option, this  will also  report information for the logical interfaces.

* How to check available disk?

Ans. -: # format

                  # iostat – en

                  # cfgadm -a

format enables you to  format,  label,  repair  and  analyze disks  on your system.

cfgadm command provides you configuration information about hardware resources.

* What is solaris volume manager?

Ans. -: Solaris Volume Manager is a software product that lets you manage large numbers of disks and the data on those disks. Although there are many ways to use Solaris Volume Manager, most tasks include the following:

• Increasing storage capacity
• Increasing data availability
• Easing administration of large storage devices

In some instances, Solaris Volume Manager can also improve I/O performance.

Solaris Volume Manager uses virtual disks to manage physical disks and their associated data. In Solaris Volume Manager, a virtual disk is called a volume. Solaris Volume Manager Volumes are built from disk slices or from other Solaris Volume Manager volumes

* How to see hardware information?

(CPU, Memory Information, IO cards)

Ans. -: # prtdiag

prtdiag displays system configuration and diagnostic information

The diagnostic information lists any failed field replaceable units (FRUs) in the system.

* How to reconfigure devices without reboot?

Ans. -: # devfsadm

The default operation is to attempt to load every driver in the system and attach to all possible device instances. Next, devfsadm creates logical links to device nodes in /dev and /devices and loads the device policy.

Devfsadmd is the daemon version of devfsadm. The daemon is started during system startup and is responsible for handling both reconfiguration boot processing and updating /dev and /devices in response to dynamic reconfiguration event notifications from the kernel.

* Purpose of “/reconfigure” file?

Ans. -: When adding or removing hardware in a Solaris system, it may be necessary to perform a reconfiguration boot. During this boot, the system discovers new hardware and recreates the file /etc/path_to_inst which contains mappings of physical devices to logical instance numbers.

To perform a reconfiguration boot from a Solaris prompt, create a file called reconfigure in the root filesystem. As root, run:

                # touch /reconfigure

* How to do hardware reconfiguration from ok prompt?

Ans. -: If you are at the OpenBoot Prompt (ok), you can issue the following command to perform a reconfiguration boot: 

                # boot -r

* Boot Machine in single user mode?

Ans. -: Some problems cannot be fixed through the operating system, for example not remembering the root password or changes to configuration files that prevent the system from booting. Solaris allows booting from the CD-ROM into single user mode which will allow you to mount your filesystems and repair the problem.

To boot into single user mode from CD-ROM, from the ok (bootprom) prompt:

                # boot cdrom -s

This will give you a root prompt (#) with a functional but limited Solaris filesystem from the cdrom. To access your filesystems, you need to mount them. For example, if your root filesystem is c0t0d0s0, use:

                # mount /dev/dsk/c0t0d0s0 /mnt

* How to check disk usage of all users on a filesystem?

Ans. -: # quot /usr

                /dev/rdsk/c0t0d0s3:
                851637  root
                690088 bin
                25828 daemon
                16880 #5115
                10025 #317
                8568 mailsrv
                6326 qmchenry
                767 uucp
                295 adm
                202 nobody
                46 lp  

The quot command provides a quick measure of the disk usage of multiple users on a filesystem

The quote command must be run as or with the privileges of root.          

In this output, the raw device of the filesystem is shown first. The username is provided if known. The numeric uids 5115 and 317 own files but are unassociated with a username in /etc/passwd as is common when files are untarred from another system.

The -a option can be used in place of the filesystem to check (/usr in that example) and will make quot iterate through all mounted filesystems. The -f option will add a middle column containing the number of files owned by each user.

The quot command could be very useful when a filesystem fills suddenly as it can quickly determine what user to flog or which application has to be checked.

* How to see Physical, Logical, Instance device Names? 

Ans. -: 1) /devices contain all the physical device names.

2) /dev contains all the logical device names it’s pointed to /devices for physical devices.

3) /etc/path_to_inst -: This file records each devices physical device names to instance names.

4) Using prtconf command you can see all the instance names but here physical name is not mapped.

5) Format utility also displays physical name and logical name of disk.

* What is the use of disk Label?

Ans. -: The disk label is the area set asides for storing information about the disk’s controller, geometry and slices.

                 To label a disk means to write slice information onto the disk. If failed to label the disk after defining the slices, the slices information is lost.

                An important part of the disk label is the partition table, which identifies a disk slices, the slices boundaries in cylinders, and the total size of the slices.  

                Another term is used to describe a disk label is the volume table of contains (VTOC).

* What is the use of tmpfs filesystem?

Ans. -: The Temporary filesystem stores files in memory, which avoids the overhead of writing to disk-based filesystem. The “tmpfs” filesystem is created and destroyed every time the system is rebooted.     

* Solaris OE filesystem?

Ans. -: 1) Disk-Based filesystem

                 2) Distributed filesystem

                 3) pseudo filesystem

1) Disk-Based filesystem -:

                a) ufs

                b) hsfs

                c) pcfs

                d) udfs

2) Distributed filesystem -:

                a) NFS

3) Pseudo filesystem -:

                a) tmpfs

                b) swapfs

                c) fdfs

                d) procfs

                e) mntfs

* What is means VTOC?

Ans. -: VTOC means volume table of contents.

The VTOC contains the partition table for the disk. The vtoc resides in the first disk sector (512 bytes block). Only the first disk slices contains a VTOC.

* What is a limit of ufs filesystem?

Ans. -: The maximum size of ufs filesystem is limited to 1 TB due to the maximum address space of 32 bits for the device drivers.

* What is the use of fsck command?

Ans. -: fsck command is used for checking consistency for following parameters

1)      superblock

2)      cylinder group block

3)      inode

4)      Data block

5)      Lost+found directory -: fsck puts the files and directories that are allocated but unreferenced in this directory. 

* How many fields are there in vfstab file?

Ans. -: There are 7 fields available in vfstab file. Those are as per follow.

1)      device to mount

2)      device to fsck

3)      mountpoint

4)      FS type

5)      fsck pass

6)      mount at boot

7)      mount options

* What is the default mount option for mount the filesystem?

Ans. -: following are the by default options for mounting filesystem

1)      read/write

2)      setuid

3)      intr/nointr

4)      nologging

5)      largefiles

6)      xattr

7)      oneerror =action (panic,lock,umount)

Change the zonename

Before changing the zonename & IP address, you have to mark those host has halt and make necessary changes.

# zoneadm -z zonename halt

# zoneadm list -vc
This command will show you how much zones are currently avaliable and how much zone are in running and installed state.

# zonecfg -z zonename (current zonename)
# zonecfg> info (This will give you entire configuration status for zone)
zonecfg> set zonename=newzonename
zonecfg> set zonepath=/zone/newzonepath
zonecfg> verify
zonecfg> commit
zonecfg> exit
# mv /zone/oldzonename /zone/newzonename

Change the IP Address

# zonecfg -z zonename
zonecfg> remove net address=your old Ip address
zonecfg> add net
zonecfg>net> set address=your new IP address
zonecfg>net> set physical=your ethernet contrller
zonecfg>net>end
zonecfg>commit
zonecfg> exit
Boot the zone.

# zoneadm -z zonename boot

How to bind Interface to zone without rebooting the zone?
-: First Add the Network interface and IP to that zone using zonecfg command then perform following procedure

“Ifconfig {interface} addif {ip}…. zone {zonename}…”

ifconfig e1000g0 addif 172.31.6.144 zone bizdirect-xapi01

ifconfig e1000g0:22 plumb

ifconfig e1000g0:22 up

ping 172.31.6.144

How to change zone name in Zone Master (Index file changes)?

-: It’s not supported, although there’s RFE’s in for it. You can do it manually by editing the files in /etc/zones – change the zonename in the .xml file, and the zone name in /etc/zones/index. (I haven’t tried doing it on a running zone, but it works for me if the zone is halted first.)

Please go through the following process for changing the zone name in covad environment.

1) Go to the respective zone master and halt the zone that you want to rename
# zoneadm –z zonename halt

2) # cd /etc/zones

3) # vi index
Change the zone name and his path to the new zone name

4) # cd /etc/zones
In this folder you will find old zone .xml file, rename that zone xml file to new zone name also edit that file and make changes for old zone name to new zone name.

5) Go to the zone path -: /zone
Here you will find old zone folder also rename to this folder to new one

6) Boot the renamed zone.
# zoneadm –z zonename boot

7) Rename the password management file in passwd_mgmt folder.
# /opt/rcs/password_management/data/users

Change the hostname
Login to the renamed zone from zone master.
# Zlogin zonename
(Change hostname in following files)
1) /etc/hosts
2) /etc/nodename (if this file is not available create this file)
3) /etc/inet/ipnodes
4) /etc/sysidecfg

9) Reboot the zone
# zoneadm –z zonename reboot

10) Make changes in DNS

How to remove net address from solaris zone -:
# remove net address=172.31.208.57

* How to change zones IP address -:
# zonecfg -z pmsg
# zonecfg:pmsg> select net address=
# zonecfg:pmsg:net> set address=
# zonecfg:pmsg:net> end
# zonecfg:pmsg> commit

* How to change zones network Interfaces -:
# zonecfg -z pmsgzone5-sol9
# zonecfg:pmsg> select net physical=
# zonecfg:pmsg:net> set physical=
# zonecfg:pmsg:net> end
# zonecfg:pmsg> commit

* Zone Service -:
# svcs | grep zone
STATE STIME FMRI
online Jun_17 svc:/system/zones:default

* How to check zones information?
Ans. -: Displays information about the current configuration. If resource type is specified, displays only information about resources of the relevant type. If resource id is specified, displays only information about that resource.
# zonecfg -z pmsg
zonecfg:pmsg> info
zonename: pmsg
zonepath: /zones/zone_roots/pmsg
brand: native
autoboot: false
bootargs:
pool:
limitpriv:
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: 10.77.228.71
physical: eri0

How to down the interface –:
-:# ifconfig interface unplumb
# ifconfig bge0 unplumb

How to see all zones Memory/cpu status -:
# prstat -Z

How to find Global zone name from zones -:
# arp -a | grep SP

How to remove Inherit-pkg dir?
# zonecfg:YOUR_ZONE> remove inherit-pkg-dir dir=/lib
# zonecfg:YOUR_ZONE> remove inherit-pkg-dir dir=/usr

Q: What is a global zone? Sparse-root zone? Whole-root zone? Local zone?
A: After installing Solaris 10 on a system, but before creating any zones, all processes run in the global zone. After you create a zone, it has processes that are associated with that zone and no other zone. Any process created by a process in a non-global zone is also associated with that non-global zone.
Any zone which is not the global zone is called a non-global zone. Some people call non-global zones simply “zones.” Others call them “local zones” but this is discouraged.
The default native zone filesystem model is called “sparse-root.” This model emphasizes efficiency at the cost of some configuration flexibility. Sparse-root zones optimize physical memory and disk space usage by sharing some directories, like /usr and /lib. Sparse-root zones have their own private file areas for directories like /etc and /var. Whole-root zones increase configuration flexibility but increase resource usage. They do not use shared filesystems for /usr, /lib, and a few others.
There is no supported way to convert an existing sparse-root zone to a whole-root zone. Creating a new zone is required.

Q: What is a container?
A: A zone which also uses the operating systems resource management facility is then called a container. Many people use the two words ?zone? and ?container? interchangeably.

Q: What types of zones are available?
A: It is possible to create non-global zones that run the same OS as the global zone, which is the OS running on the system. It is also possible to create a non-global zone that runs a different operating environment from the global zone. The branded zone (BrandZ) framework extends the Solaris Zones infrastructure to include the creation of brands that contain alternative sets of runtime behaviors. The following types of non-global zones are available:
• native:
The default SX CE and Solaris 10 non-global zone is the native zone. It has the same characteristics as the Solaris 10 Operating System or SX release that is running in the global zone.
If you have configured your system with Solaris Trusted Extensions, each non-global zone is associated with a level of security, or label. Labeled zones can be configured starting with the Solaris 10 11/06 release. For more information, see Solaris Trusted Extensions Installation and Configuration.
• ipkg:
The ipkg non-global zone is the default on the OpenSolaris release. It has the same characteristics as the OpenSolaris or SX release that is running in the global zone.
• Branded zones that run an environment different that the OS release on the system
o The lx branded zone introduced in the SX DE and Solaris 10 8/07 releases provides a Linux environment for your applications and runs on x86 and x64 machines. For more information, visit the OpenSolaris Community: BrandZ.
o The solaris8 and solaris9 branded zones enable you to migrate a Solaris 8 or Solaris 9 system to a Solaris 8 or Solaris 9 container on a host running the Solaris 10 8/07 Operating System or later S10 release. The solaris8 zone is an environment for Solaris 8 applications on SPARC machines. The solaris9 zone is an environment for Solaris 9 applications on SPARC machines. Now Solaris 8 Containers and Solaris 9 Containers, this product was introduced through Solaris 8 Migration Assistant 1.0, on October 22, 2007. For more information, see System Administration Guide: Solaris 8 Containers and System Administration Guide: Solaris 9 Containers. To download, go to Solaris Containers. [May 2008]
o The Solaris 10 Container is available on OpenSolaris and SX CE as of build 127. These branded zones host Solaris 10 user environments.

http://picasaweb.google.co.in/pradipgudale2000