Reserve memory for global zone

Hello,
Is there a way / method to reserve certain amount of RAM only for the global zone?
I have a server (Solaris 10 10/08) with 5 zones on it and instead of setting memory caps on each zone, I would like to reserver some memory for the global zone exclusively.
Sorry if the question has already been asked. Please point me to the thread.

Similar Messages

Not all non-global zones updated for DST

We have one server with Solaris 10 and four non-global zones. I installed patch 122032-03 to the global zone and it installed successfull, according to the log. With the DST change on 3/11, TWO of the non-global zones and the global zone updated correctly to daylight time, but the other TWO non-global zone DID NOT. Does anyone know what would cause this?
I have also tried to manually change the time on the two non-global zones and have not been able to; as root I get the message "not owner"
ainsworth:hughesm> su -
Password:
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
You have mail.
# date
Tue Mar 13 12:02:45 PST 2007
# date -u
Tue Mar 13 20:03:16 GMT 2007
# date
Tue Mar 13 12:04:31 PST 2007
# date 0313130007
date: Not owner
usage: date [-u] mmddHHMM[[cc]yy][.SS]
date [-u] [+format]
date -a [-]sss[.fff]
Fortunately, these were just test zones. They were set up by a previous admin to be used for pgpftp, so I'm wondering if there are some special configurations for security that is preventing the time change.

Thanks for replying.
I rebooted from the global zone. All the zones have the same uptime as the global zone, except one that was rebooted more recently.
Quick question - how do I tell if it's a sparse zone or full zone?
One of the zones that the time change worked on:
$ zdump -v US/Pacific | grep 2007
US/Pacific Tue Mar 13 22:37:59 2007 UTC = Tue Mar 13 15:37:59 2007 PDT isdst=1
US/Pacific Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0
US/Pacific Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1
US/Pacific Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1
US/Pacific Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0
tsbackup:hughesm> cd /usr/share/lib/zoneinfo; ls -al | grep Pac
drwxr-xr-x 2 root bin 1024 Jan 19 11:19 Pacific
cathedral:hughesm> cd /usr/share/lib/zoneinfo; ls -al | grep Pac (the global zone)
drwxr-xr-x 2 root bin 1024 Jan 19 11:19 Pacific
One zone that didn't work: (the other one that did not work is the same)
# zdump -v US/Pacific | grep 2007
US/Pacific Tue Mar 13 22:45:33 2007 UTC = Tue Mar 13 14:45:33 2007 PST isdst=0
US/Pacific Sun Apr 1 09:59:59 2007 UTC = Sun Apr 1 01:59:59 2007 PST isdst=0
US/Pacific Sun Apr 1 10:00:00 2007 UTC = Sun Apr 1 03:00:00 2007 PDT isdst=1
US/Pacific Sun Oct 28 08:59:59 2007 UTC = Sun Oct 28 01:59:59 2007 PDT isdst=1
US/Pacific Sun Oct 28 09:00:00 2007 UTC = Sun Oct 28 01:00:00 2007 PST isdst=0
# uname -a
SunOS albina 5.10 Generic_118822-02 sun4u sparc SUNW,Ultra-4
# cd /usr/share/lib/zoneinfo (non-global zone that did not update)
# ls -al | grep Pac
drwxr-xr-x 2 root bin 1024 Apr 20 2005 Pacific
I was thinking of trying to apply the patch within the zone itself, but when I tried smpatch analyze, it didn't list it:
# smpatch analyze
120900-04 SunOS 5.10: libzonecfg Patch
121133-02 SunOS 5.10: zones library and zones utility patch
119254-27 SunOS 5.10: Install and Patch Utilities Patch
119574-02 SunOS 5.10: su patch
121453-02 SunOS 5.10: Sun Update Connection Client Foundation
121118-08 SunOS 5.10: Sun Update Connection System Client 1.0.8
121081-05 SunOS 5.10: Connected Customer Agents 1.1.0
122231-01 SunOS 5.10 Sun Connection agents, transport certificate update
I attempted to add the patch using smpatch, but I've never run it here before so it's probably not configured right:
# smpatch update -i 122032-03
122032-03 cannot be validated.
com.sun.patchpro.model.PatchProRuntimeException: Unexpected throwable
at com.sun.patchpro.cli.PatchServices.waitForThread(PatchServices.java:1284)
at com.sun.patchpro.cli.PatchServices.installPatches(PatchServices.java:1121)
at com.sun.patchpro.cli.PatchServices.main(PatchServices.java:510)
Caused by:
java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
at com.sun.patchpro.model.PatchProModel$InnerDownloadPatchThread.downloadPatchFailed(PatchProModel.java:2855)
at com.sun.patchpro.server.GroupPatchDownloader.dispatchFailedEvent(GroupPatchDownloader.java:384)
at com.sun.patchpro.server.GroupPatchDownloader.downloadPatchFailed(GroupPatchDownloader.java:335)
at com.sun.patchpro.server.ServerPatchServiceProvider.dispatchFailedEvent(ServerPatchServiceProvider.java:2577
at com.sun.patchpro.server.ServerPatchServiceProvider.validatePatchBundle(ServerPatchServiceProvider.java:2196
at com.sun.patchpro.server.ServerPatchServiceProvider.requestDownload(ServerPatchServiceProvider.java:1780)
at com.sun.patchpro.server.ServerPatchServiceProvider.performDownloadPatches(ServerPatchServiceProvider.java:1
2)
at com.sun.patchpro.server.ServerPatchServiceProvider.downloadPatches(ServerPatchServiceProvider.java:860)
at com.sun.patchpro.server.PatchServerProxy.downloadPatches(PatchServerProxy.java:142)
at com.sun.patchpro.server.GroupPatchDownloader.downloadPatches(GroupPatchDownloader.java:124)
at com.sun.patchpro.model.PatchProModel.performPatchDownload(PatchProModel.java:1932)
at com.sun.patchpro.model.PatchProStateMachine$10.run(PatchProStateMachine.java:526)
at com.sun.patchpro.util.State.run(State.java:266)
at java.lang.Thread.run(Thread.java:595)
So then I attempted to add the patch using patchadd:
# patchadd 122032-03
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Global patches.
0 Patch 122032-03 is for global zone only - cannot be installed on local zone.
No patches to install.
under /var/sadm/patch/122032-03 on the Global zone, the log shows:
-rw-r--r-- 1 root root 2666 Jan 19 11:19 log
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /usr/share/lib/zoneinfo/Africa/Timbuktu <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Argentina/ComodRivadavia <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Indiana/Indianapolis <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Indianapolis <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Kentucky/Louisville <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Louisville <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/CST6CDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST5EDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Europe/Belfast <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/HST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST7MDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/PST8PDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Pacific/Yap <no longer a regular file>
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /usr/share/lib/zoneinfo/Africa/Timbuktu <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Argentina/ComodRivadavia <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Indiana/Indianapolis <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Indianapolis <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/America/Kentucky/Louisville <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/America/Louisville <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/CST6CDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/EST5EDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Europe/Belfast <no longer a regular file>
WARNING: /usr/share/lib/zoneinfo/HST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/MST7MDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/PST8PDT <no longer a linked file>
WARNING: /usr/share/lib/zoneinfo/Pacific/Yap <no longer a regular file>
Installation of <SUNWcsu> was successful.
On the non-global zones, either there is nothing under /var/sadm/patch or there isn't even a patch directory under /var/sadm. Is there somewhere else to look?
Thanks.

Can't install 121118-12 on global zone

Hi, after our first round of patching, we're starting again. So, I've had to upgrade my external LPS to latest patches to get it to work at all. It is now on 119788-09 and 121118-12. The patchsvr has been reconfigured to point to getupdates1.sun.com without the trailing "solaris/".
So, I then tried to get my internal LPS working...proxy isn't running. smpatch pointed to the external (DMZ) LPS without a trailing "solaris/". Has patch revisions 119788-07 and 121118-08. Note, when I use the trailing "solaris/" then I get the "no patches" message. Without that, I now get a list of 40 patches (tho' I'm expecting about 190-odd as my external LPS is at the same patch levels otherwise and smpatch which points direct to Sun comes back with 196 patches).
Just to confirm, my current.zip (/var/sadm/spool/cache/Database/http....***...current.zip) gives me a patchlist.delimited file that is 9419 lines long. That seems about right.
So I thought - gosh! I really hope that this isn't going to be a 2-step patch process (currently running kernel rev 118833-24 and have seen a few warnings about going up to the mid-30s) so maybe I have to install the latest UC client patch for this to see that it needs more patches.
But trying to run "smpatch add -i 121118-12" barfs and finishes with the following message;
Patch 121118-12 failed to install due to a failure produced by pkgadd.
WARNING: patchadd returned <5> for global zone
pkgadd: ERROR: The package <SUNWppror> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <SUNWppror> cannot be installed on this system/zoneSo, dutifully, I go to run (after unzip'ing my jar file); "patchadd -G 121118-12". The first time it says much like below, but to check the log file which says the bit above. Any subsequent attempts give up on telling you to look at the logfile because you should've already and just tell you this;
# patchadd -G 121118-12
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Global patches.
0 Patch 121118-12 is for global zone only - cannot be installed on non-global zone.
No patches to install.Funnily enough, I am running on my global zone, but patchadd and smpatch just can't seem to tell. Has there been a major update to patchadd that I've missed or is there some other reason that I can't install this patch? Do I really need to remove it all before patching again? If so, how is that affected by 119788 which also patches SUNWppror?
Thanks for any help,
Sally.

Yes, there are relevant packages in that file;
server # grep SUNW gz*
# Last modified by <pkgadd> to <add> package <SUNWpkgcmdsu>
SUNWapch2d
SUNWapch2r
SUNWapch2u
SUNWexplo
SUNWexplu
SUNWexted
SUNWnbcpp
SUNWnbide
SUNWpkgcmdsu
SUNWppror
SUNWpprou
SUNWpsvrr
SUNWpsvru
SUNWsneep
server # Does this file get updated whenever patchadd/pkgadd -G is used? If so, I would've only installed the update connection proxy server patches on the global zone alone as it is not supported within local zones and I would've seen no reason to install it on a local zone (waste of time).
Also, when I was testing applying patches on zones, I would've run "patchadd -G" for some patches to see what the difference is, but I wouldn't have suspected that this would change the action of the patch forever more.
Or have these packages gotten in there another way.
Within one of my local zones, there are no SUNW packages in the /var/sadm/install/gz-only-packages file and yet the zone cannot remove the patch;
myzone # patchrm 121118-12
Validating patches...
Loading patches installed on the system...
Done!
Checking patches that you specified for removal.
Done!
Global patches.
0 Patch 121118-12 is for global zone only - cannot be removed on non-global zone.
No patches to remove.
myzone #but I guess that is because it is checking on the global zone at that stage. On that point, does a local zone know the name of the server its global zone is on? Can this be determined without being on the global zone?
Thanks,
Sally.

Resource Requirement for a global zone

Hi All,
We are going to deploy Solaris container in our environment. However, we hope know if there any guideline for the resource requirement for setup the global zone. In other words, what are the min cpu / memory should be set assigned to the global zone?
Thanks in advance.
Regards

You don't need to worry about defending the global zone. The design of the pool_default pool includes safeguards that prevent starvation by other pools. The most obvious is the zone strategy itself; there's no way to allocate all the physical memory to a zone before the kernel itself has pinned down what it needs.
I think it would make better sense to allocate some (large) percentage of memory to the Oracle container and adjust as needed, rather than try and lock every bit of it. Maybe 14 GB and see how that works. I can think of any number of annoyances you might encounter by trying to lock down more memory than is actually available.

FilesystemMountPoints for ufs disks mounted to non-global zones

Hello,
I have a SAN ufs disk to be used as a failover storage, mounted to non-global zones (NGZ).
Solaris 10 nodes using Cluster 3.2
I'm looking for the correct value for the property FilesystemMountPoints and the vfstab entry required for a failover disk mounted to a NGZ.
Should the path NOT include the NGZ root path?
From the man page for SUNW.HAStoragePlus, for the property FilesystemMountPoints:
You can specify both the path in a non-global zone and the path in a global zone, in this format:
Non-GlobalZonePath:GlobalZonePath
The global zone path is optional. If you do not specify a global zone path, Sun Cluster assumes that the path in
the non-global zone and in the global zone are the same. If you specify the path as
Non-GlobalZonePath:GlobalZonePath, you must specify Global-ZonePath in the global zone's /etc/vfstab.
The default setting for this property is an empty list.
You can use the SUNW.HAStoragePlus resource type to make a file system available to a non-global zone. To enable
the SUNW.HAStoragePlus resource type to do this, you must create a mount point in the global zone and in the
non-global zone. The SUNW.HAStoragePlus resource type makes the file system available to the non-global zone
by mounting the file system in the global zone. The resource type then performs a loopback mount in the
non-global zone.
Each file system mount point should have an equivalent entry in /etc/vfstab on all cluster nodes and in all
global zones. The SUNW.HAStoragePlus resource type does not check /etc/vfstab in non-global zones.
SUNW.HAStoragePlus resources that specify local file systems can only belong in a failover resource group
with affinity switchovers enabled. These local file systems can therefore be termed failover file systems. You
can specify both local and global file system mounts points at the same time.
Any file system whose mount point is present in the FilesystemMountPoints extension property is assumed to
be local if its /etc/vfstab entry satisfies both of the following conditions:
1. The non-global mount option is specified.
2. The "mount at boot" field for the entry is set to "no."
In my situation, I want to mount the disk to /mysql_data on the NGZ called ftp_zone. So, which is the correct setup?
a. FilesystemMountPoints=/mysql_data:/zones/ftp_zone/root/mysql_data
Global zone vfstab entry /dev/md/ftpabin/dsk/d110 /dev/md/ftpabin/rdsk/d110 /zones/ftp_zone/root/mysql_data ufs 1 no logging
NGZ mount point /mysql_data
OR
b. FilesystemMountPoints=/mysql_data:/mysql_data (can be condensed to simply /mysql_data)
Global zone vfstab entry /dev/md/ftpabin/dsk/d110 /dev/md/ftpabin/rdsk/d110 /mysql_data ufs 1 no logging
NGZ mount point /mysql_data
Should the path NOT include the NGZ root path?
And should the fsck pass # be 1 or 2?
Looking at this example from p. 26 of
http://wikis.sun.com/download/attachments/24543510/820-4690.pdf
This example doesn't mention the entry in vfstab.
Create a resource group that can holds services in nodea zonex and nodeb zoney
nodea# clresourcegroup create -n nodea:zonex,nodeb:zoney test-rg
Make sure the HAStoragePlus resource is registered
nodea# clresourcetype register SUNW.HAStoragePlus
Now add a UFS [or VxFS] fail-over file system: mount /bigspace1 to failover/export/install in NGZ
nodea# clresource create -t SUNW.HAStoragePlus -g test-rg \
-p FilesystemMountPoints=/fail-over/export/install:/bigspace1 \
ufs-hasp-rs
Thank you!

Hi,
/zones/oracle-z is my root directory of the zone.
* add the device to the zone :
root@mpbxapp1 # zonecfg -z oracle-z
zonecfg:oracle-z> add device
zonecfg:oracle-z:device> set match=/dev/global/dsk/d12s0
zonecfg:oracle-z:device> end
zonecfg:oracle-z> add device
zonecfg:oracle-z:device> set match=/dev/global/rdsk/d12s0
zonecfg:oracle-z:device> end
zonecfg:oracle-z> exit
* add FS to NGZ's /etc/vfstab : ( You may omit this step, I don't know why but it works without this step :) )
root@mpbxapp1 # vi /zones/oracle-z/root/etc/vfstab
/dev/global/dsk/d12s0 /dev/global/rdsk/d12s0 /global/oracle ufs 1 no logging
* add FS to global zone's /etc/vfstab :
root@mpbxapp1 # vi /etc/vfstab
/dev/global/dsk/d12s0 /dev/global/rdsk/d12s0 /zonefs/oracle ufs 1 no logging
* set the FilesystemMountPoints property :
root@mpbxapp1 # /usr/cluster/bin/clresource set -p FilesystemMountPoints=/global/oracle:/zonefs/oracle oracle-hastp
Whit this configuration you may ensure that the FS is not directly accessible from master zone. Actually, it's accessible but with a different PATH. For example, for Oracle, from the master zone Oracle can not be started/stopped because the controlfile can not be accessed. :)
Hope this helps,
Murat

Separate private ip addresses for non-global zones

I'm testing zones on one of our administrative servers and I'm wondering about the following scenario.
Zones can easily run away with a lot of ip addresses and I decided to try this. The machine has, in its global zone, a standard private address in the admin (192.168.129.0) segment on hme0. I have also given it another address, 192.168.229.1, configured on hme0:1 which I intend to be the defaultrouter for non-global zones.
Zone 1 has as its primary address 192.168.229.10, and I have tried to set the default router to 192.168.229.1 by various methods based on what I have read in here., including adding that address to the defaultrouter file in the global zone.
Zone 2 has 192.168.229.20 as its primary address and is intended to have the same default of 192.168.229.1.
So far I've not been able to make this work . Am I barking up the wrong tree?
TIA

Sorry for the late reply.
So if I understand correctly, you want to put all your zones in a dedicated IP network (192.168.229.0/24).
To do this, you don't need to configure the global zone as default gateway for the zones (which doesn't work, as you noticed). You want to indicate to the zones that they can reach the other network (192.168.129.0/24) just by sending packets on hme0. To do so, you need to create interface routes in every zone:
# route add net 192.168.129.0/24 192.168.229.10 -interface(same for Zone 2, etc.)
The global zone then needs to advertise itself as gateway for the 192.168.229.0/24 network to the other hosts. I think in.routed(1M) can do this using special configuration in the gateways(4) file, but I don't know how. Otherwise, if you can administer the real router that the other hosts use, you can add a static route: destination 192.168.229.0/24, gateway [global zone IP].
hope this helps,
Blaise

Administration file for non-global zones

I want to install package in global zone. What attributes can I set in administration file? I use administration file for relocating packages by altering basedir. In global zone package is relocated, but installation continues for non-global zones in package basedir.
Is it possible to specify pkgadd -G parameter (install only in current zone) in administration file?
Regards
Jezz

We use the CDE login mechanism. From the CDE login screen on the global zone:
[] Select Options, Remote Login, Enter Host Name from the CDE login screen.
[] Enter the hostname (not the zone name!) of the non-global zone in the Enter the host name box.
[] Click OK.
[] Once the CDE login screen appears with the hostname of the non-globalzone listed at the top, log in as sysadmin.
Notes: If the non-global zone or the system was recently booted, wait a few minutes and check to make sure that the cde-login service is running using the command:
svcs -a | grep cde-login
Also, if you have restricted /etc/Xaccess, you'll need to add your non-global zone to it.
Message was edited by:
r2ad
Message was edited by:
r2ad, http://www.r2ad.com

GUI interface for non-global zones

My Goal:
Create multiple zones, each running different services thus eliminating the need for multiple servers w/out using VMware.
What I'm realizing:
Everything I've read points back to non-global zones being only a console based environment. Does anyone know if it's possible to login to non-global zones with a GUI interface?
Thanks,
Rick

We use the CDE login mechanism. From the CDE login screen on the global zone:
[] Select Options, Remote Login, Enter Host Name from the CDE login screen.
[] Enter the hostname (not the zone name!) of the non-global zone in the Enter the host name box.
[] Click OK.
[] Once the CDE login screen appears with the hostname of the non-globalzone listed at the top, log in as sysadmin.
Notes: If the non-global zone or the system was recently booted, wait a few minutes and check to make sure that the cde-login service is running using the command:
svcs -a | grep cde-login
Also, if you have restricted /etc/Xaccess, you'll need to add your non-global zone to it.
Message was edited by:
r2ad
Message was edited by:
r2ad, http://www.r2ad.com

Update packages for newbie in a non-global zone

Hi,
I'm new on this forum and i'm a newbie. Recently, I have install OpenSolaris and I have install a non-global zone (big-zone). So, I can install new packages manually in my non-global zone with a terminal but i don't know if it's possible to use the package manager (same tool when i'm log on my global zone in a gnome-session).
I don't know if it's possible to install gnome in a non-global zone because it's more easy to me to use the package manager tool in a graphical mode. It's very long to write a command for each package that i want update.
Thanks a lot in advance and sorry for my english.
jaymachine

I know of patchadd -G, it is used when one has downloaded the pathch already. I was looking for an automated patch procedure. I use the java gui upadate manager in the global zone but it will not patch the Java Communications Suite installed in a sparse zone.
Sparse zones are more than really cool. I have entire comms suite installed in a zone with SMF for all the components, anything siezes up and it's a few minutes to reboot, piece of cake. Allows me to use one host server whilst all webserver / application instances are on port 80.

Oracle 10g install is not working on Global zone

We installed Solaris 10 (below) in a T2000 using the same standards we have for many other hosts.After the installation was finished, three zones were exported from a M5000 class machine and imported into this T2000. From inside the zones we can call the Oracle10g installer and the graphical screen is presented. When executing the installed from the Global zone, we can see a java process running, using 100% of a thread, but no graphical interface is presented at all. Checking truss, we see a lot of pollsys being called. Any ideas?
# uname -a
SunOS wgsst2k01 5.10 Generic_127127-11 sun4v sparc SUNW,SPARC-Enterprise-T2000
# memconf -v
memconf: V2.6 06-May-2008 http://www.4schmidts.com/unix.html
hostname: wgsst2k01
banner: SPARC Enterprise T2000 (8-core quad-thread UltraSPARC-T1 1000MHz)
manufacturer: Sun Microsystems, Inc.
model: SPARC-Enterprise-T2000
Sun development codename: Ontario
Sun Family Part Number: SEB
Solaris 10 5/08 s10s_u5wos_10 SPARC, 64-bit kernel, SunOS 5.10
1 8-core quad-thread UltraSPARC-T1 1000MHz cpu, system freq: 200MHz
socket MB/CMP0/CH0/R0/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH0/R0/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH1/R0/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH1/R0/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH2/R0/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH2/R0/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH3/R0/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH3/R0/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH0/R1/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH0/R1/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH1/R1/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH1/R1/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH2/R1/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH2/R1/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH3/R1/D0 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
socket MB/CMP0/CH3/R1/D1 has a 1024MB (1GB) DIMM (address 0x000800000-0x4007fffff)
empty sockets: None
total memory = 16384MB (16GB)Cheers
Andreas

This pretty much says it all:
No connection could be made because the target machine actively refused it.What version of Vista?
What version of the agent? ... 10g is not a version number it is a marketing label
Did you check to see if the agent is compatible with your operating system?
My recommendation would be to get a real operating system: Either Oracle Linux or XP.

PHP in Solaris 10 and Non-Global Zones: Problem of performance?

Hi friends
We are feeling a poor performance with applications developed with PHP in Solaris 10, with non-global and global zones, while Intel platform (Xeon and Pentium), performance is very good. Difference between both platforms is about 200% aprox, one second in Intel to 9, 12 or 20 seconds in Solaris depending of model.
Our tests were developed in:
1. SF T2000 server Solaris 10 global zone
2. SF T2000 server Solaris 10 non-global zone
3. SF280R server Solaris 10 non-global zone
4. V240 server with 1 GB memory, 1*US III-i 1.0 GHz and Solaris 9 (really this version for test and comparisons)
5. V240 server with 8GB memory, 2*US III-i 1.5Ghz and Solaris 9 (really this version for test and comparisons too)
Intel platforms were:
1. Intel Pentium 4 2GHz 2GB memory, Linux Fedora and PHP 4.4.4
2. Intel Xeon 2 core, 2.33GHz 2GB memory, Linux Fedora and PHP 4.4.3
Versions of products are:
1. Solaris 9 or Solaris 10
2. PHP 4.4.7 downloaded from http://www.php.net/downloads.php
3. Apache 2.0.59
4. MySQL 4.1.15-log
Our php compilation and installation were:
./configure --prefix=/usr/local/php-4.4.7 \
--with-pear \
--with-openssl=/usr/local/ssl \
--with-gettext \
--with-ldap=/usr/local \
--with-iconv \
--enable-ftp \
--with-dom \
--with-mime-magic \
--enable-mbstring \
--with-zlib \
--enable-track-vars \
--enable-sigchild \
--disable-ctype \
--disable-overload \
--disable-tokenizer \
--disable-posix \
--with-gd \
--with-apxs2=/usr/local/apache2.0.53/bin/apxs \
--with-mysql \
--with-pgsql \
--with-oci8=/oracle/product/9.2.0 \
--with-oracle=/oracle/product/9.2.0 \
--with-png-dir=/usr/local \
--with-zlib-dir=/usr/local \
--with-freetype-dir=/usr/local \
--with-jpeg-dir=/usr/local
make
make install
Questions:
Is there any problem of PHP with SunFire T2000 servers or 64-bits platforms?
Is there any flag of PHP would be use to compilarion PHP in 64-bits or multithread?
I wait for any comments or suggestions about our problem with PHP compilation and performance in Solaris 10. Thanks a lot.
Sergio.

I presume you compiled php on the Sun server, was this done using gcc or the Sun One C compiler.
If the latter then you can also use the flag: --enable-nonportable-atomics when you run configure

Capped zones not getting discovered automatically after global zone discovr

On solaris 10.
We have global zones with capped and uncapped zones.
Zones which are uncapped getting discovered under global zone.
But zones which are capped are not getting discovered.
As per all documents:http://docs.oracle.com/cd/E27363_01/doc.121/e27511/ftr_zones_mgmt.htm
All the non-global zones in the selected global zone are automatically discovered
Edited by: vtadmin on Aug 25, 2012 9:46 PM

The most common reason this usually occurs is because the of the shared memory issue with the Sun MC database. Looks like this issue has been passed on to 4.0. Please try doing the following:
When installing a Server in a whole-root Zone, edit /etc/project to set the shared memory setting first.
Change the "default:3:::" entry to look like this:
default:3::::project.max-shm-memory=(privileged,1073741824,deny)
...where 1073741824 indicates a 1GB setting (you may tune it lower). For more details, go here:
http://docs.sun.com/app/docs/doc/819-5418/6n7gk6ilo?a=view
Mostly this is a problem in whole root zones, but sometimes also applies to the global zones.

Failing to install pkg on non-global zone

(root)@syslog1:~# pkgadd -d . SUNWant
Processing package instance <SUNWant> from </home/iqbala>
Jakarta ANT(sparc) 11.10.0,REV=2005.01.08.05.16
WARNING: Stale lock installed for pkgrm, pkg SUNWaspell quit in remove-initial state.
Removing lock.
Using </> as the package base directory.
## Processing package information.
ERROR: Cannot allocate memory for package object array.
pkgadd: ERROR: memory allocation failure
pkgadd: ERROR: unable to process pkgmap
Installation of <SUNWant> failed (internal error).
No changes were made to the system.
(root)@syslog1:~#
(root)@syslog1:~# zonename
syslog
This non-global zone is capped to 1G phy memory out of 2G total of the T1000
(root)@syslog-global:~# uname -a
SunOS syslog-global 5.10 Generic_137137-09 sun4v sparc SUNW,Sun-Fire-T1000
(root)@syslog-global:~# zoneadm list
global
syslog
(root)@syslog-global:~# zonename
global
(root)@syslog-global:~# zonecfg -z syslog info
zonename: syslog
zonepath: /syslog
brand: native
autoboot: true
bootargs: -m verbose
pool:
limitpriv: default,sys_time
scheduling-class: FSS
ip-type: shared
inherit-pkg-dir:
     dir: /lib
inherit-pkg-dir:
     dir: /platform
inherit-pkg-dir:
     dir: /sbin
inherit-pkg-dir:
     dir: /usr
fs:
     dir: /var/logs
     special: /var/logs
     raw not specified
     type: lofs
     options: []
fs:
     dir: /usr/local
     special: /syslog-local/usr/local
     raw not specified
     type: lofs
     options: []
net:
     address: 192.168.0.114
     physical: aggr1
     defrouter: 192.168.0.1
dedicated-cpu:
     ncpus: 1-8
     importance: 10
capped-memory:
     physical: 1G
     [swap: 512M]
attr:
     name: comment
     type: string
     value: "syslog server"
rctl:
     name: zone.max-swap
     value: (priv=privileged,limit=536870912,action=deny)
(root)@syslog-global:~# prstat -Z
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
13118 root 7184K 5952K sleep 1 0 52:00:54 0.5% nco_p_syslog/10
11730 root 162M 123M sleep 59 0 38:51:35 0.1% splunkd/22
7324 root 12M 8280K sleep 59 0 0:58:06 0.0% syslogd/25
266 root 97M 24M sleep 49 0 31:45:02 0.0% poold/8
209 daemon 8104K 3080K sleep 59 0 24:39:56 0.0% rcapd/1
29553 root 2496K 2024K cpu4 59 5 0:00:00 0.0% splunk-optimize/1
21578 root 38M 36M sleep 59 0 0:01:10 0.0% puppetd/2
29554 root 6088K 3712K cpu0 49 0 0:00:00 0.0% prstat/1
24244 root 5760K 3104K sleep 49 0 0:00:00 0.0% bash/1
1024 noaccess 171M 96M sleep 59 0 8:41:32 0.0% java/18
27771 noaccess 189M 100M sleep 1 0 4:44:36 0.0% java/18
274 daemon 3192K 496K sleep 59 0 0:00:00 0.0% statd/1
279 daemon 2816K 576K sleep 60 -20 0:00:00 0.0% nfs4cbd/2
326 root 2304K 40K sleep 59 0 0:00:00 0.0% cimomboot/1
151 root 2576K 344K sleep 59 0 0:00:00 0.0% drd/2
ZONEID NPROC SWAP RSS MEMORY TIME CPU ZONE
3 47 465M 513M 25% 99:54:00 0.7% syslog
0 42 391M 466M 23% 71:04:39 0.1% global
Total: 89 processes, 386 lwps, load averages: 0.21, 0.26, 0.26
Am I hitting a bug?

If your pkg wants to be installed in /usr or another inherit-pkg-dir, it can't because they are share as read-only.
Verify wherer the pkg copies its files.

How to share Global zone CPUs to non global zones

Okay we have a server with 8 CPU`s and 32Gig RAM running Solaris 10 11/06 release.
We have 2 full zones setup in addition to the default global zone. Each of these 2 zones has 3 CPU`s assigned to it leaving 2 CPU`s only used by the gloabl zone so if we were to loose one we would not loose the zones etc.
Now is it possible under Solaris 10 11/06 release to have the 2 non gobal zones have the 3 dedicated CPU`s each and also share 1 CPU each from the 2 CPU`s used by the global zone? All the documentaion I have seen and read does not make this clear but I have read that the new Solaris 10 08/07 release have several new zone commands available?
I know there is FSS but I do not think that can do what we want.
Has anyone done anything like this or able to offer any help.

Yes, there are new features in 08/07 you should consider useful in your configuration. Especially the possibility to restrict physical and virtual memory are important to everyone cause a bad process in zone can consume all the memory of the system, leaving all the zones unusable.
But when it comes to your problem, there is no real help, cause you cannot split cpus, only a much simplified configuration.
A pset still cannot share a cpu with another pset.
What you can do:
You can however make use of the dynamic resource manager in Solaris 10. He can dynamically bind a cpu to either zones on the fly if they need one.
pset.poold.objectives "utilization > 30; utilization < 80;" for eg means if the pset and its cpus is used more the 80% for some time, the a free unbound cpu will be added to the pset on the fly.
Read: http://docs.sun.com/app/docs/doc/817-1592/rmconfig-3?l=en&a=view
In Solaris 07/08 this is easy to configure:
freom [zones-discuss] http://mail.opensolaris.org/pipermail/zones-discuss/2006-August/005105.html
{color:#3366ff}_Dedicated CPUs_
Many existing resource management features have a new, simplified user
interface. For example,
"<a href="http://docs.sun.com/app/docs/doc/817-1592/6mhahuooo?l=en&a=view#gepsd">dedicated-cpus</a>"
re-use the existing
Dynamic
Resource Pools features. But instead of needing many
commands to configure them, configuration can be as simple as:
global# zonecfg -z myzone
zonecfg:myzone> add dedicated-cpu
zonecfg:myzone:dedicated-cpu> set ncpus=1-3
zonecfg:myzone:dedicated-cpu> end
zonecfg:myzone> exit
After using that command, when that Container boots, Solaris:
{color}<ol><li>{color:#3366ff}removes a CPU from the default pool
     {color}</li>
<li>{color:#3366ff}assigns that CPU to a newly created temporary pool
     {color}</li>
<li>{color:#3366ff}associates that Container with that pool, i.e. only schedules
     that Container's processes on that CPU
     {color}</li>
</ol>
{color:#3366ff}
Further, if the load on that CPU
exceeds a default threshold and another CPU can be moved from another
pool, Solaris will do that, up to the maximum configured amount of three CPUs.
Finally, when the Container is stopped, the temporary pool is destroyed
and its CPU(s) are placed back in the default pool.
{color:#000000}
Hope this helps,{color}
{color:#000000}Konstantin Gremliza{color}
{color}

X Sessions to a non global zone

I am trying to enable a direct cde login to my local zone.
Since installing the zone I have looked for the cde-login.xml svc script under /var/svc/manifest/application/graphical-login, but it is only available in my global zone.
Is it safe to copy this to my local zone and start the service using "svcadm enable svc:/application/graphical-login/cde-login" or will this cause my global zone issues?

Hi Darren,
There is an error message in the log file regarding cde-login.xml but why, the file is identical as the ones all all the other servers, I have listed our cde-login.xml below
Thanks again
Neil
pkgadd: ERROR: source path </var/sadm/pkg/SUNWdtlog/save/pspool/SUNWdtlog/reloc/
var/svc/manifest/application/graphical-login/cde-login.xml> is corrupt
pathname does not exist
ERROR: attribute verification of </zones/saturn/root/var/svc/manifest/applicatio
n/graphical-login/cde-login.xml> failed
pathname does not exist
Installation of <SUNWdtlog> on zone <saturn> partially failed.
<?xml version="1.0"?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">

<service_bundle type='manifest' name='SUNWdtdte:dtlogin'>
<service
name='application/graphical-login/cde-login'
type='service'
version='1'>
<single_instance />
<dependency name='multi-user'
grouping='require_all'
restart_on='error'
type='service'>
<service_fmri value='svc:/milestone/multi-user:default'/>
</dependency>
<dependency name='sysconfig'
grouping='require_all'
restart_on='none'
type='service'>
<service_fmri value='svc:/milestone/sysconfig'/>
</dependency>
<exec_method
type='method'
name='start'
exec='lib/svc/method/svc-dtlogin'
timeout_seconds='60' />
<exec_method
type='method'
name='stop'
exec=':kill'
timeout_seconds='60' />
<exec_method
type='method'
name='refresh'
exec='/usr/dt/config/dtlogin.rc reset'
timeout_seconds='60' />
<property_group name='startd'
type='framework'>

<propval name='ignore_error'
type='astring' value='core,signal' />
</property_group>

<property_group name='general' type='framework'>
<propval name='action_authorization' type='astring'
value='solaris.smf.manage.dt.login' />
</property_group>

<property_group name='dtlogin' type='application'>
<propval name='debug_level' type='count' value='0' />
<propval name='debug_log' type='astring' value='' />
<propval name='args' type='astring' value='' />
<propval name='value_authorization' type='astring'
value='solaris.smf.value.cde.login' />
</property_group>
<instance name='default' enabled='false'>
</instance>
<stability value='Unstable' />
<template>
<common_name>
<loctext xml:lang='C'>
CDE login
</loctext>
</common_name>
<documentation>
<manpage title='dtlogin' section='1'
manpath='/usr/dt/share/man' />
</documentation>
</template>
</service>
</service_bundle>

Reserve memory for global zone

Similar Messages

Maybe you are looking for