02-11-2018
Just a small disclaimer, i never worked with solaris 10 branded zones.
But, since it's a whole root zone, upgrade of solaris 11 global zone should have minimal to no effect to such zones.
Actually, no patching should occur for solaris10 zone.
So if the solaris 11 release you are patching support solaris10 branded zones, you should be fine.
I would go with normal attach with using preview switch first -n and examine the output.
If everything goes well in preview, run the normal attach.
Also, Solaris 11 system when doing major patching will create a backup boot environment automatically, followed by patching and activation of patched environment.
After the patching finishes, a reboot should suffice.
pkg subsystem will write that on the console after patching, and you can confirm the same by issuing beadm list after patching.
Depending on the importance of the system in the zone, backup(s) should be made.
This is done using zfs archives or zoneadm command subswitches and, of course, exporting the text configuration of zone using zonecfg.
Hope that helps
Regards
Peasant.
9 More Discussions You Might Find Interesting
1. Solaris
Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies
2. Solaris
Dear all,
we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message:
***The image patch level is downrev for running in a solaris10 branded zone***
The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed.
Does the... (0 Replies)
Discussion started by: xunil321
0 Replies
3. Solaris
I have a T5220 running Solaris 10. I have a application that can only run on Solaris 9. I want to build a branded Solaris 9 zone for this application on the Solaris 10 Server.
What steps would I need to accomplish this? (2 Replies)
Discussion started by: soupbone38
2 Replies
4. Solaris
Hi,
A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well?
Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies
5. Solaris
I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate.
#zonecfg -z <device>
>create -b
>set brand=solaris10
>set zonepath=/zonez/<device>
>set ip-type=exclusive
>add net... (1 Reply)
Discussion started by: aeroforce
1 Replies
6. Solaris
I am trying to get a NFS share on a Solaris 10 branded zone. I have read that this is not possible...but I was hoping someone here could tell me different.
share -F nfs -o ro,anon=0 /dir
This would really surprise me that you cannot do this.
Thanks (2 Replies)
Discussion started by: aeroforce
2 Replies
7. Solaris
All.
I am trying to create a 10 branded zone on a Sol 11.1 T5. The Global is using IPMP...so aggregating is out of the question. Has anyone successfully created a branded zone with IPMP? If they have can you please show me the steps you took to get this to run.
Thanks (4 Replies)
Discussion started by: aeroforce
4 Replies
8. Solaris
Hi,
I want to install branded zone sol 9 in sol 10. I keep getting same error. Please advice me.
Thanks. (12 Replies)
Discussion started by: mzainal
12 Replies
9. Solaris
Hi, hoping someone can help, its been a while since I used Solaris.
After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin)
However, the NGZ cannot access any other netwqork devices, it can't even see the default router
... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
LEARN ABOUT OPENSOLARIS
native
native(5) Standards, Environments, and Macros native(5)
NAME
native - native branded zone
DESCRIPTION
The native brand uses the branded zones framework described in brands(5) to run zones installed with the same software as is installed in
the global zone. The system software must always be in sync with the global zone when using a native brand.
SUB-COMMANDS
The following native brand-specific subcommand options are supported in zoneadm(1M).
attach [-u] [-b patchid]...
For native zones, zoneadm checks package and patch levels on the machine to which the zone is to be attached. If the packages/patches
that the zone depends on from the global zone are different (have different revision numbers) from the dependent packages/patches on
the source machine, zoneadm reports these conflicts and does not perform the attach. If the destination system has only newer dependent
packages/patches (higher revision numbers) than those on the source system, you can use the -u option to update the attached zone to
match the -revision packages and patches that exist on the new system. With -u, as in the default behavior, zoneadm does not perform an
attach if outdated packages/patches are found on the target system.
For native zones, one or more -b options can be used to specify a patch ID for a patch installed in the zone. These patches will be
backed out before the zone is attached or, if -u was also specified, updated.
install [-a archive] | [-d path] [-p] [-s] [-u] [-v] [-b patchid]...
The native brand installer supports installing the zone from either the software already installed on the system or from an image of an
installed system running the same release. This can be a full flash archive (see flash_archive(4)) or a cpio(1) or pax(1) "xustar" ar-
chive. The cpio archive be compressed with gzip or bzip2. The image can also be a level 0 ufsdump(1M), a path to the top-level of a
system's root tree, or a pre-existing zone path.
With no options the zone is installed using same software as is running the global zone.
To install the zone from a system image either the -a or -d is required. Either the -u or -p option is also required in this case.
-a archive
The path to a flash_archive(4), cpio(1), or pax(1) "xustar" archive, or a level0 ufsdump(1M), of an installed system. cpio archives
may be compressed using gzip or bzip2.
-b patchid
One or more -b options can be used to specify a patch ID for a patch installed in the system image. These patches will be backed
out during the installation process.
-d path
The path to the root directory of an installed system. If path is a hyphen (-), the zonepath is presumed to be already populated
with the system image.
-p
Preserve the system configuration after installing the zone.
-s
Install silently.
-u
Run sys-unconfig(1M) on the zone after installing it.
-v
Verbose output from the install process.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Uncommitted |
+-----------------------------+-----------------------------+
SEE ALSO
cpio(1), pax(1), zlogin(1), zonename(1), sys-unconfig(1M), ufsdump(1M), zoneadm(1M), zonecfg(1M), flash_archive(4), attributes(5),
brands(5), privileges(5), zones(5), lx_systrace(7D)
SunOS 5.11 13 Feb 2009 native(5)