08-20-2010
Patching zone
Hi everyone,
I have a container which includes 5 zones. I would like to patch only 2 of them with the latest recommended patch bundle.
1) Could it be done by installing Recommended Patch Cluster on those 2 zones? And after rebooting them?
2) May patching only those 2 zones affect the global zone or other zones? I remember them as all inheriting some main directories from the global zone.
3) Is it better to patch the global zone with all non-global zones? How to do that?
4) Is there anyone who has experienced some difficulties after patching a zone?
thanks for help...
9 More Discussions You Might Find Interesting
1. Solaris
Hi Greetings...
I have an issue in connecting the zone from outside the network and it is because of default gateway. I can ping default gateway from inside the zone and not able to ping from global zone due to different VLAN issue. If i add two different gateways and restart network services,... (2 Replies)
Discussion started by: vvpotugunta
2 Replies
2. Solaris
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
3. Solaris
what are prerequisites or precautions we take before we install a patch in a zone.what if zone fails to boot after patching.How to recover form this situation.?
Thanks in advance..:) (1 Reply)
Discussion started by: ravijanjanam12
1 Replies
4. Solaris
Hi All,
Below is the configuration of my sun cluster.
root@glob-one # clzc status
=== Zone Clusters ===
--- Zone Cluster Status ---
Name Node Name Zone HostName Status Zone Status
---- --------- ------------- ------ -----------
data ... (0 Replies)
Discussion started by: milindphanse604
0 Replies
5. Solaris
can some one help me out as it is showing 2 different time zones in global zone and nonglobal zone .In global zone it is showing in GMT while in nonglobal zone i it showing as PDT.
System in running with solaris 10 (3 Replies)
Discussion started by: ravijanjanam12
3 Replies
6. UNIX for Advanced & Expert Users
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
Discussion started by: custos
2 Replies
7. Solaris
Hi All,
I had installed an agent in one of the zones and it was working fine. After few days, we had patched that server and once the server came up and zone was up, The agent script and its files are missing. Though we can restore it from backup, we are unable to understand how the files went... (4 Replies)
Discussion started by: Rockyc3400
4 Replies
8. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
9. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
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)