Zone creation

Hi,
My machine is x86 , OS is winxp
Iam using solaris10 running on VMware player. I have created a test zone on solaris10 using solaris9 container and down loaded solaris9-image.flar and saved on Apps folder. But iam unable to install solaris9-image.flar to test zone.
#zonecfg -z testzone info
zonepath: /zones/testzone
autoboot:true
pool:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
net:
address:
Physical:
#zoneadm -z testzone install -u -a /Apps/solaris9-image.flar
-u: illegal option --u
usage: install
install the configuration on to the system
As iam new in solaris can anyone help on regard this......Thanks in advance.
Arunii2

one more thing, I just noticed, that you are using X86 solaris. so have a look at this:
"A Solaris 9 branded zone (solaris9) is a complete runtime environment for Solaris 9 applications on *SPARC* machines running the Solaris 10 8/07 Operating System or later."
http://docs.sun.com/app/docs/doc/820-4490/gfjbk?a=view
so, you won't be able to test those things on x86 machine.
Laszlo

Similar Messages

Will zones inherit security/hardening settings made prior to zone creation?

Hi guys.
So the scenario is I've just finished hardening Solaris 10: disabling of services, configuring tcp wrappers and the such. I would now like to create a zone or zones but there are a few things I would like to make sure of, before proceeding.
The questions are:
i) After creating a zone, whether it's sparse or whole, will the non-global zone inherit the hardening settings that I have setup prior? Or is it a seperate entity that requires me to harden it.
ii)I understand that patching the global zone will patch the rest of the other zones. Does this include whole-root zone since it does not mount any filesystem outside its zone.
Thank you.
N.

No, except for the packages that get installed at zone creation time, they're separate.
Patches are applied to all zones. A zone may be temporarily booted just to apply a patch. Even though a whole-root zone may not mount external filesystems, that doesn't mean that it's independent. For instance, it's kernel files aren't actually loaded, since it doesn't have an independent kernel. When the global zone's kernel is patched, all others are as well. So the files within the zone will be patched as well to maintain consistency.
Darren

Removing Packages "added" by zone creation

The search feature on these forums is limited. Scrolling back about 8 months I think I know the answer to this question, but I would like to be certain.
I have a solaris 10 global zone with SUNWut (sunray services) installed.
When I create my non-global zones, Solaris is "kind" enough to install the sunray services into the non-global zones as they get created. This leads to multiple instance of the sunray software running.
When I created the non global zones the first time, I went into the non--global zones and I removed the SUNWut packages using pkgrm.
Is there a way to tell the zone creation to not install the SUNWut package when the non global zone is created? I have to rebuild this machine and I would love to create the zones in a more efficient manner.
Looking through the posts I saw that people were dealing with my problem the same way I did. Once the non global zone is running, go in and do a pkgrm on it.
I just want to verify that this is the way other people are handling it.
Thanks,
Eric

The zones are a typical sparse root model (inherited-pkg-dir's are /lib/ /platform/ /sbin/ and /usr/). There is no nfs mounting or such.
Once the non-global zone is installed, If you go to /opt in the non-global zone the SUNWut directory is there. If you do a ps command you can see that there is a sunray server is running in each zone.
Thinking about it I suppose that the install script for SUNWut may be at fault. Perhaps it is telling the zone install that it is a base package when it is not. This would make sense because I was using a SRSS 3.0 install patched by my sun engineers to install on my sol10 system. Perhaps I will not run into the same issue now that I have the official 3.1 sunray s/w.
Only time will tell. But I appreciate the reply so that I know if it does happen that I am handling the problem in the correct manner (using pkgrm on SUNWut).
I will report back if this issue comes up again when I redo the system.
Thanks,
Eric

Problem with zone creation in Solaris 10 6/06

Hi,
I have configured and installed a non-global zone following the example given in the guide http//www.sun.com/software/solaris/howtoguides/posgresqlhowto.jsp. My zone has the following configuration:
# zonecfg -z pg_zone
zonecfg:pg_zone> info
zonepath: /export/zones/pg_zone
autoboot: true
pool:
fs:
dir: /pg_log
special: /dev/dsk/c1d0s0
raw: /dev/rdsk/c1d0s0
type: ufs
options: []
net:
address: 192.168.10.100/24
physical: bge0
zonecfg:pg_zone> exit
The installation completed but I got the following errors:
# zoneadm -z pg_zone install
Preparing to install zone <pg_zone>.
Creating list of files to copy from the global zone.
Copying <130101> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1059> packages on the zone.
Initialized <1059> packages on zone.
Zone <pg_zone> is initialized.
Installation of these packages generated errors: <SUNWgnome-a11y-libs-share>
Installation of <63> packages was skipped.
The file </export/zones/pg_zone/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
When examined the logs there were several messages like this:
SUNW_PKG_THISZONE=true in the pkginfo file.
*** package <SUNWamutl> was not installed:
The package <SUNWamutl> is registered to be installed in the
global zone only. The package may have been installed in the global
zone using the pkgadd '-G' option, or the package may contain a
request script, or the package may directly set the package attribute
SUNW_PKG_THISZONE=true in the pkginfo file.
*** package <SUNWiimdv> was not installed:
The package <SUNWiimdv> is either not fully installed in the
global zone, or the package contains a request script. Only packages
that are fully installed in the global zone and that do not contain a
request script can be installed when a new zone is created. If this
package does not contain a request script, you can correct this
problem by removing and reinstalling the package in the global zone.
And when I try to boot the zone I get this error:
# zoneadm -z pg_zone boot
zoneadm: zone 'pg_zone': "/usr/lib/fs/lofs/mount -o zonedevfs /export/zones/pg_zone/dev /export/zones/pg_zone/root/dev" failed with exit code 33
zoneadm: zone 'pg_zone': call to zoneadmd failed
Any suggestion how to solve this problem?
thanks

To answer your question wangzh: Yes I did. I actually followed exactly the procedure on the how-to-uides: http://www.sun.com/software/solaris/howtoguides/containersLowRes.jsp.
I think the problem here might reside in the script supplied in the solaris distribution for creating zones. For example, in the default configuration script, the package directories /lib /platform /var and /usr are by default set to be automatically imported. But when I try to create a zone using these defaults settings, it ends up with an mounting error that prevents the installation of the zone. only when I remove manually those directories from the configuration then the installation continues.
And during the installation process there are number of packages that are by default imported via the installation script and this is some of those packages that cause the errors here. I also tried to exclude the offending packages as suggested by henryC but I couldn't find all of them and the creation still fails at the booting.

Failover Zone Creation

Still at the beginning of the learning curve here....
I am looking to create a Solaris 10 failover zone in my 3.2 Cluster.
I see documents claiming both ways that the zone can or cannot have its zonepath on a globally shared file system.
So, do I
Create equivalent zones on the local drives, then add a pointer in the zone to a file system on the global area, then go forward with my cluster resource creation from there
-or-
No, just create the zone on the shared storage area once from node 1, the delete it and create it from node 2, then bring in HAStorageplus, etc.
Thanks.

I've been trying to configure a failover zone on my cluster and I'm having a terrible time. I do remember seeing somewhere that zones needed to be on a local filesystem, but I can't find that now.
I'm following these instructions: http://docs.sun.com/app/docs/doc/819-3059/6n5aafjor?a=view
Everything goes as expected and I have this:
$ clrg status
Cluster Resource Groups ===
Group Name Node Name Suspended Status
nfs-rg stnv240a No Online
stnv240b No Offline
web-rg stnv240a No Online
stnv240b No Online
zone-rg stnv240b No Online
stnv240a No Offline
$ clrs status
Cluster Resources ===
Resource Name Node Name State Status Message
cluster stnv240a Online Online - LogicalHostname online.
stnv240b Offline Offline
nfs-stor stnv240a Online Online
stnv240b Offline Offline
nfs-res stnv240a Online Online - Service is online.
stnv240b Offline Offline
web-stor stnv240a Online Online
stnv240b Online Online
zone-rs stnv240b Online Online
stnv240a Offline Offline
$ zonecfg -z cwm -f cwm-failover.cfg
$ zonecfg -z cwm info
zonename: cwm
zonepath: /global/nfs/zones/cwm
brand: native
autoboot: false
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
net:
     address: 204.155.141.145
     physical: bge0
     defrouter not specified
But then I can't boot. I got a similar error trying to configure a sparse zone. Install fails there, as it can't mount /lib
$ zoneadm -z cwm boot
zoneadm: zone 'cwm': "/usr/lib/fs/lofs/mount -o zonedevfs /global/nfs/zones/cwm/dev /global/nfs/zones/cwm/root/dev" failed with exit code 33
zoneadm: zone 'cwm': call to zoneadmd failed
Any help or ideas here?
Solaris 10 10/08 s10s_u6wos_07b SPARC
Solaris Cluster 3.2 u1 but patched so I have sczonecluster.

Solaris10 branded zone creation error on Solaris 11.1

Hello,
We are having the problem in creating the Solaris10 branded zone on the solaris 11.1 version. We are trying to install this branded zone using the solaris10 VM template. Please can some one through some pointers ?
The installation steps stops at "Waiting for boot to complete" but never successfully boots even waiting for long times. We can see that Zone status in configured only.
root@localhost:~# /home/solaris-10u10-sparc.bin -p /solaris10 -i net0 -a xxx.xxx.xxx.xxx -z zone10
This is an Oracle VM Template for Oracle Solaris Zones.
Copyright Â© 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license
agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly
permitted in your license agreement or allowed by law, you may not
use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any
part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by
law for interoperability, is prohibited.
Checking disk-space for extraction
Ok
Extracting in /root/bootimage.dnaqaD ...
100% [===============================>]
Checking data integrity
Ok
Checking platform compatibility
The host and the image do not have the same Solaris release:
host Solaris release: 5.11
image Solaris release: 5.10
Will create a Solaris 10 branded zone.
IMAGE: /home/solaris-10u10-sparc.bin
ZONE: zone10
ZONEPATH: /solaris10/zone10
INTERFACE: net0
VNIC: vnicZBI6783
MAC ADDR: 2:8:20:5c:92:f5
IP ADDR: xxx.xxx.xxx.xxx
NETMASK: 255.0.0.0
DEFROUTER: # # This file is deprecated. Default routes will be created for any router # addresses specified here, but they will not change when the underlying # network configuration profile (NCP) changes. For NCP-specific static # routes, the '-p' option of the route(1M) command should be used. # # See netcfg(1M) for information about network configuration profiles. #
TIMEZONE: Asia/Kolkata
Checking disk-space for installation
Ok
Installing in /solaris10/zone10 ...
100% [===============================>]
Using a static exclusive-IP
./setupSysidcfgStaticIP[50]: file/sysidcfg.zone10: cannot create [No such file or directory]
cp: cannot access file/sysidcfg.zone10
chmod: WARNING: can't access file/sysidcfg.zone10
Attaching zone10
Booting zone10
zoneadm: zone 'zone10': must be installed before boot.
Waiting for boot to complete
booting...
booting...
booting...
root@localhost:# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
4 zone1 running /zone1 solaris excl
5 zone2 running /zone2 solaris excl
- zone10 configured /solaris10/zone10 solaris10 excl
root@localhost:#
I have installed the package pkg:/system/zones/brand/brand-solaris10 on the system.
# cat /etc/release
Oracle Solaris 11.1 SPARC
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Assembled 19 September 2012

Sorry, please ignore my previous message about the wrong ip address (I assume you entered a valid ip address).
The problem you are facing is related to the defaultrouter, and I assume you are running Solaris 11 update 1.
If so, to workaround the problem for the time being you may edit the /etc/defaultrouter file in the global-zone and enter the ip address of the default router (you can remove this change when the template deployment is completed).
If you have no idea about the default router ip address, just rename /etc/defaultrouter (e.g. to /etc/defaultrouter.orig) so that it cannot be found by the template. Again, you can undo the change when deployment is complete.
Thierry

Whole root zone creation

Hi
I am building a whole root zone running Solaris U9 I noticed the   zone does not get installed with some updated packages from global zone like the openssl installed in global zone does not get installed in the non global zone and it also requires sshd user to be defined This results the ssh not starting in the new zone I want to know if this is the default behaviour of whole root zone installation process and how can we get the zone to be installed with all the currently running packages of the global zone Are there any post installation steps that need to be followed for the zone to boot up correctly. I have run the post post installation configuration steps as well
TIA

Thanks Walter
I was wondering since most of the packages installations at least require one interaction   where it asks for confirmation. how the other packages are getting installed. But mostly that might be the reason
There is also the SUNW_PKG_ALLZONES and other related variables   which control this but since here the packages which are already installed on global zome are getting installed on NG zone , how these parameters can be changed I could not found any of these parameters in any pkginfo file in the global zone

Zone creation(zonecfg) fails

I had created a few zones as root, and now when i try to create zones as a non-root user , it errors out
#/usr/sbin/zonecfg -z zone-appconfig
WARNING: you do not have write access to this zone's configuration file;
going into read-only mode.
zonecfg:zone-appconfig> create
zone-appconfig: cannot create in read-only mode.
#id
uid=150(user) gid=1(other)
Following are the zones that i had created as root
#/usr/sbin/zoneadm list -cv
ID NAME STATUS PATH
0 global running /
1 zone-small running /export/home/zone-small
- zone-whole configured /export/home/zone-whole

Ok..i could reach one more step by doing the following
.../etc/zones wasnt setup as world writable
# ls -l |grep zones
drwxr-xr-x 2 root sys 512 Jan 2 13:25 zones
# chmod g+w zones
# chmod o+w zones
# ls -l |grep zones
drwxrwxrwx 2 root sys 512 Jan 2 13:25 zones
zone-appconfig: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone-appconfig> create
zonecfg:zone-appconfig> set zonepath=/home/abc
zonecfg:zone-appconfig> verify
zonecfg:zone-appconfig> exit
zone-appconfig: Problem updating index file
Configuration not saved; really quit (y/[n])? n
zonecfg:zone-appconfig> commit
zone-appconfig: Problem updating index file
zonecfg:zone-appconfig>
This is probably index file somewhere which isnt writable by my non-user account :(
Any help is appreciated...thx!!

Skipping sys-unconfig on Zone Creation

I guess I haven't created a new zone in awhile, just be using the 5 that I'd had for ages. I recently created a new Zone and fired it up but was supprised when I could log into it. When connecting to the console I was greeted with the familiar CURSES inferface for initial network setup. Are Zones now sys-unconfig'ing themselves during the install or ready phases? Is there a way to avoid having to do this?

I guess I haven't created a new zone in awhile, just
be using the 5 that I'd had for ages. I recently
created a new Zone and fired it up but was supprised
when I could log into it. When connecting to the
console I was greeted with the familiar CURSES
inferface for initial network setup. Are Zones now
sys-unconfig'ing themselves during the install or
ready phases? Is there a way to avoid having to do
this?See sysidcfg(4) -- you can place such a file in the zone (at /path/to/zone/root/etc/sysidcfg) before you boot it for the first time, and the sysid tools will pick up the settings from it.
- jonathan

Open ports in zones

I am encountering a strange behavior in new zones created using zonemgr 2.0.6 (this is the only way I create zones, so I do not know if the issue is more general). When I create a new zone, two strange things are happening:
1. Immediately after the zone is created, no services are running, not even ssh
2. About 10 minutes later, a whole bunch of services are running. Most of these are not running on the global zone.
For reference, nmap output on the global zone is the following:
[dcomsm1@dcomsm1:~] $ nmap t2000
Starting Nmap 5.00 ( http://nmap.org ) at 2010-02-28 20:51 EST
Interesting ports on 131.247.16.134:
Not shown: 991 closed ports
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
2161/tcp open apc-agent
3052/tcp open powerchute
4045/tcp open lockd
32774/tcp open sometimes-rpc11
32775/tcp open sometimes-rpc13
32776/tcp open sometimes-rpc15
32777/tcp open sometimes-rpc17
The new zone is created using the following zonemgr arguments:
[root@t2000:~/zonecfgs] # more ./temp.sh
#!/usr/bin/bash
./zonemgr -a add -n drenkhah -z "/export/zones" -P "root_pw" -I "131.247.16.159|e1000g0|25|drenkhah" -R "/root|/usr/bin/bash" -s "basic|lock"
zone creation output is as follows:
[root@t2000:~/zonecfgs] # ./temp.sh
Checking to see if the zone IP address (131.247.16.159) is already in use...IP is available.
cannot create '/drenkhah': leading slash in name
chmod: WARNING: can't access /export/zones/drenkhah
chown: /export/zones/drenkhah: No such file or directory
Zone drenkhah will be placed in the following directory: /export/zones/drenkhah
Preparing to install zone <drenkhah>.
Creating list of files to copy from the global zone.
Copying <2568> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1042> packages on the zone.
Initialized <1042> packages on zone.
Zone <drenkhah> is initialized.
The file </export/zones/drenkhah/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
Creating the sysidcfg file for automated zone configuration.
Booting zone for the first time.
Waiting for first boot tasks to complete.
Waiting for automatic post-install reboot to complete
Updating netmask information.
Updating /etc/inet/hosts of the global zone with the drenkhah IP information.
Generating ssh host keys. Details in the (/root/.zonemgr/zone28330-ssh.log) file.
svcadm: Pattern 'svc:/network/ssh' doesn't match any instances
Setting the root user's home directory to /root
Setting the root user's shell to /usr/bin/bash
Disabling un-necessary services via basic method for the default services.
Zone drenkhah is complete and ready to use.
nmap output just after creating the zone is as follows:
[dcomsm1@dcomsm1:~] $ nmap drenkhah
Starting Nmap 5.00 ( http://nmap.org ) at 2010-02-28 17:53 EST
All 1000 scanned ports on 131.247.16.159 are closed
Nmap done: 1 IP address (1 host up) scanned in 29.39 seconds
nmap output 17 minutes later is as follows:
[dcomsm1@dcomsm1:~] $ nmap drenkhah
Starting Nmap 5.00 ( http://nmap.org ) at 2010-02-28 18:10 EST
Interesting ports on 131.247.16.159:
Not shown: 986 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
23/tcp open telnet
25/tcp open smtp
79/tcp open finger
111/tcp open rpcbind
513/tcp open login
514/tcp open shell
587/tcp open submission
4045/tcp open lockd
6112/tcp open dtspc
6788/tcp open unknown
6789/tcp open ibm-db2-admin
7100/tcp open font-service
Nmap done: 1 IP address (1 host up) scanned in 29.25 seconds
Note that there are many open ports
# uname -a
SunOS t2000 5.10 Generic_137137-09 sun4v sparc SUNW,Sun-Fire-T200
Thanks
Manish

The Leopard OS X firewall is application based and not port based. Honestly, I haven't played with it enough to know for certain how to answer your question.
But... when you do connection sharing, you're essentially doing a port based NAT for the systems on the other side of your Mac. This pretty much keeps you from initiating anything to the other system even without a local firewall unless you were to configure port forwarding.
As for blocking packets, you would need to use the 'ipfw' command to do things at the port level.

Solaris 10 local zone setup requirement/steps for am/ps 7.0 installation

Hi,
Is there any document available on solaris 10 local zone creation/requirement for am server/ portal server 7.0 install? Any help/pointer is appreciated.
Thanks,

I don't believe there is any specific documentation am/portal in a zone. And as far as I know there are no specific requirements either. I have successfully installed portal in a solaris zone.
A good starter tutorial on zones is here: http://partneradvantage.sun.com/protected/solaris10/adoptionkit/tech/zones/tutorial.html
Hi,
Is there any document available on solaris 10 local
zone creation/requirement for am server/ portal
server 7.0 install? Any help/pointer is
appreciated.
Thanks,

Zone create not installing all zone root files

I'm installing a new T5240 Solaris 10 u6 10/08 with the 10_Recommended patch kit from 09 Dec 2008. The system is jumpstarted with /, /usr, /var, /export/home on SVM mirrored internal 146g drives. When I first got the server up and running, I tested zone creation with a default zone setup:
zonecfg -z test
create -b
set zonepath=/export/home/zones
set autoboot=true
add net
set physical=nxge0
set address=192.168.103.254
end
verify
commit
exit
zoneadm -z test install
Preparing to install zone <test>.
Creating list of files to copy from the global zone.
Copying <139100> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1164> packages on the zone.
This worked, so I removed it and continued with the server configuration:
The nxge0 interface has been configured with 802.1q vlan (nxge103000) and is successfully on the network. I configured MPX/IO on the pair of fp interfaces. I've added a disk from our HP EVA SAN array and created a ZFS pool and filesystem for the zoneroot, mounted at /opt/zones/zoneroots/oraprod1.
Now, when I try to recreate the test zone it now fails to copy all of the required files to the root, puts many errors into the install log about files changed in the global-zone root after installation and won't boot the zone past single-user maintenance mode.
The zone create now shows: (after adjusting the phys net i/f name)
bash-3.00# zoneadm -z test2 install
Preparing to install zone <test2>.
Creating list of files to copy from the global zone.
Copying <78> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1165> packages on the zone.
When I zlogin to the zone after it's booted into maint, it's obvious that many root fs files are missing - including
most of the SMF service manifests.
I've searched for forums, mailing lists and sun support knowledgebase without finding anything similar.
What am I missing?

Yes, I've reproduced the problem with and without the '-b' option on create, on UFS as well as ZFS filesystem and on /export/home/zones on the local drive.
My plan now is to walk thru the configuration process one step at a time, trying to create the zone at each step. I re-jumped the server last night and created the zone correctly. I then removed it, installed patches in single user, rebooted with "-r" and was able to recreate the zone. I've enabled mpxio and i can still create the zone. Next up tonight is to add the 802.1Q configuration, add the ZFS rootzone and run our custom scripts that to server hardening, user setup, etc.
There was one bug report that sounded "interesting" having to do with a patch set that wasn't zone-friendly as it left patch files in place w/o fixing the manifests so when the zone create ran it found files that didn't match the checksums or whatever is used to validate file correctness when copying files into the zone.
I'll keep updating this with my progress and findings.

Solaris Express Zone install error with SUNWiiimr and SUNWcnetr

Hi all,
I got these errors when installing a new zone on a Solaris Express 1/08 (5.11) on a x64 box:
Installation of these packages generated errors: SUNWiiimr
Installation of these packages generated warnings: SUNWcnetr
The zone creation log shows:
*** package -SUNWiiimr- failed to install with fatal errors:
/export/zones/newzone/root/var/sadm/pkg/SUNWiiimr/install/postin stall: /export/zones/newzone/root/lib/postrun: not found
/export/zones/newzone/root/var/sadm/pkg/SUNWiiimr/install/postinstall: /export/zones/newzone/root/lib/postrun: not found
pkgadd: ERROR: postinstall script did not complete successfully
Installation of -SUNWiiimr- on zone -newzone- failed.
*** package -SUNWcnetr- installed with warnings:
pkgadd: ERROR: unable to create package object -/export/zones/newzone/root/etc/dladm-.
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/aggregation.conf- failed
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/linkprop.conf- failed
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/secobj.conf- failed
owner name -dladm- not found in passwd table(s)
Installation of -SUNWcnetr- on zone -newzone- partially failed.
-newzone- was configured to be a whole root zone. Are there any ways to solve these installation errors?
Thanks in advance.

This problem seems some strange - this time with Solaris 10u4, from 10 containers installed on a brand new X2200 (2x cpu) only one do not output those errors, but just this one cannot install the dsee or proxy. This time the errors were from:
Installation of <SUNWxwplr> on zone <dsee-proxy> partially failed.
Installation of <SUNWdtdmr> on zone <dsee-proxy> partially failed.
Installation of <SUNWmconr> on zone <dsee-proxy> partially failed.
Installation of <SUNWrmwbr> on zone <dsee-proxy> partially failed.
Installation of <SUNWlvmr> on zone <dsee-proxy> partially failed.
Installation of <SUNWzebrar> on zone <dsee-proxy> partially failed.
So the machine was, too, just installed. After several hours, anoter atempt to install a zone, this time just this one, returned no errors - and the dsee installed without any complains. All configurations were for whole root zones. Used was Solaris 10u4 with the most recent patch cluster applied.

Windows 2012 adds an incorrect name when creating a PTR Record in a /56 reverse zone using MMC

Hello,
I have created a reverse lookup zone for 2001:bc8:3f83:0200::/56, when I add a PTR record for 2001:bc8:3f83:0200::200:99, the MMC snap-in adds a zero group in my address and adds a record for 2001:bc8:3f83:0200:0000:0000:0000:200:99.
Zone creation :
http://imageshack.com/a/img673/4018/JFf7BX.jpg
PTR creation :
http://imageshack.com/a/img538/9239/bZqaQl.jpg
Result :
a PTR with address 2001:bc8:3f83:0200:0000:0000:0000:200:99 :
http://imageshack.com/a/img673/8793/3EcxOW.jpg
(Sorry for the image links, the forum would not allow me to post images...)

Hi,
According to your description, my understanding is that the name of PTR record(IPv6) displayed as 2001:bc8:3f83:0200:0000:0000:0000:200:99, but when open its Properties, the Host IP address option displayed as 2001:bc8:3f83:0200:0000:0000:200:99.
I have the similar problem on my test device Windows Server 2012, but this problem do not occurred on Windows Server 2012 R2. They have different ways to type the Host IP address. And it is may be related to the prefix digit number – not the integer multiple
of 16.
You may try to update your server to the latest version. Or a work around way to manually add the PTR record of IPv6 by command line:
dnscmd <ServerName> /RecordAdd <ZoneName> <NodeName> [/Aging] [/OpenAcl] [<Ttl>] PTR <HostName>|<DomainName>
Detailed information reference link:
https://technet.microsoft.com/en-us/library/cc844045(v=ws.10).aspx
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Zone private area

I use Sol-10 b54. As for now non-global zone can share some directories with
global zone with read-only permission.
I would like to know:
1. Will it be proposed read-write technology of such share ?
2. What about directories share not only with global zone but with non-global
also ?
3. Now I can create non-global zone with the similar set of packages as in
global one. I don't like it. Is there any work around ideas? I'd like
to see possibility of non-global zone creation with predefined package set.
4. Is ZFS is the answer of all aforementioned questions?

The "inherit-pkg-dir" resource can be used to specify a read-only file system
that is shared or exported by the global zone into another zone.
1. Will it be proposed read-write technology of such share You can do that today by defining a "fs" resource of type "lofs". But be aware
that be doing so you're setting up a channel where the local zone can potentially
affect the global zone (for example, by exhausting the space on the file system).
2. What about directories share not only with global zone but with non-global
also ?Yes, the global admin can set up such a file system, again by creating "fs"
resources of type "lofs" into one or more zones. But again, it does mean that
one zone can potentially affect another zone if such a file system exists in
both read-write.
With respect to #3, we're looking at methods of specifying a subset of
packages to copy into a zone when it's installed. For now, you can specify
some of the affected directories, like /opt, as "inherit-pkg-dir" resources or
in some caes, you can use pkgrm(1M) if they packages came from an
unbundled product.
As for ZFS and zones, stay tuned as there should be some very nice
synergy between these two technologies.

Zone creation

Similar Messages

Maybe you are looking for