ing that a reboot of the global is required to make FSS active.
For that matter, there should be a warning message on zone boot that FSS is not
active and the configured zone.cpu-shares value will be ignored.
Phil
Phil Freund
Lead Systems and Storage Administrator
Kichler Lighting
This
rades. (Rather
like the maintenance addresses in an IPMP configuration.) If this is true, are
the only places that would need the changes implemented the zone xml file and
the entries in the zones /etc/hosts (and hostname.xxx) files?
Advice?
TIA,
Phil
Phil Freund
Lead Systems and Storage Administ
. (So far 5 servers migrated
with 18 zones created on 4 new servers - 5 zones were from migration, the rest
handle new requirements... sigh)
Phil
Phil Freund
Lead Systems and Storage Administrator
Kichler Lighting
This message posted from opensolari
If you are going to backup a zone using the NetBackup client from within the
zone and you want to get all the filesystems automatically, you have to do the
following NetBackup policy setup:
In the NetBackup policy:
1. Enable the Follow NFS option
2. Enable the Cross mount points option
3. Leave
I have hit a problem with zones in relation to doing Solaris upgrades - I can’t
do them currently. I have expended considerable effort in trying to be
positioned to do upgrades but they do not work for me as currently implemented.
I’ll provide a summary of my situation and then make suggestions
Update: I was off base with my assumption about the upgrade problem not being
related to MPXIO (Traffic Manager). That is exactly where the problem lies.
I finally had a chance to try doing an upgrade on a server with a SAN-based
zone root without MPXIO and the upgrade worked with no problems.
Thanks. I tried that and it will show all the mappings except for the LUNs
added dynamically after the last reboot. Those do show up once you do a reboot.
(I'm not sure if a reconfiguration reboot is required though.)
I was told by Sun Support to try "luxadm display /dev/rdsk/cxtxd0s2"
The blastwave.org Samba distribution doesn't have this issue: its shutdown
(/etc/init.d/cswsamba stop) uses the pid IDs for smbd, nmbd, and winbindd
stored in /opt/csw/var/locks/.
A quick FYI on using the blastwave distribution: If you are using sparse zones
and need to run Samba with winbind,
You can also remove a LOFS mounted filesystem from a running zone with no
problem. I do it all the time.
To do it, logon to the global zone and umount the filesystem with:
umount
Phil
This message posted from opensolaris.org
___
zones-discuss mai
Hi Jeff,
Thanks for posting this info. I had to look real hard to find it in the Release
Notes even knowing it existed. The link within the FAQ goes to a blank page.
I looked at the notes both from the link in the message and in the Release
Notes and still need some clarification about the lofs
I have started using resource pools to limit the number of CPUs available to a
zone. I'm trying to find a way to track the pool assignment info and have the
following questions:
Is there a command that will tell me which pools my zones are assigned to or do
I have to check in each zone config f
Thanks for the info. It's kind of what I expected but not what I wanted to
hear. Just out of curiosity, are any of these things visible in SMC Container
Manager? I keep meaning to find time to try that to see what it would provide
but time ...
I think that it's getting critical to be able to di
When is it necessary to patch whole root zones directly?
I was trying to make sure that I had all of my zones ready to be updated with
DST patch 122034-04 so I made sure to install patch utilities patch 119254-34
on all of the global zones. I never thought to install it on the whole root
zones
Hi Enda,
I have attached the /var/sadm/"patchid"/log files for all three patches.
Here’s the output from patchadd -p:
For the kernel patch:
clv1udw11:root> zlogin cludsim001 patchadd -p | grep 119254-34
clv1udw11:root>
For the patch utilities patch:
Cludsim001:root> patchadd -p|grep "h: 1192
This week has been a scramble for me as well - DST patches.
All of these patches except 119254-34 were applied in single-user. 119254-34
was applied with all zones booted.
Phil
This message posted from opensolaris.org
___
zones-discuss mailing list
Enda,
I'll get an explorer for you and send it on Thursday - I've just been eaten
alive with DST preparation/implementation and subsequent NetBackup issues.
I'll send you patchadd logs if you tell me where they are stored. I did all of
the patchadds from single-user on the console so if they do
Enda,
All of the zones were booted to milestone all when 119254-34 was applied. Since
the patch didn't require a reboot, I did it with all zones and global fully
operational.
Phil
This message posted from opensolaris.org
___
zones-discuss mailing
Just a reminder that QuickIO is only supported in a global zone. It uses a
special device that can't be created in a non-global zone. It should be a
fairly moot issue anyway since QuickIO is only useful for Oracle 8i and lower
releases, none of which are still supported. QuickIO is still support
Are you still able to do a ps -ef from the global zone without it hanging up?
If not, you may have run into a known kernel bug (Bug ID 6469395) related to
page retire. There is an IDR for that bug but no permanent patch yet. We ran
into this a couple of weeks ago on a T2000 server and have seen
Hi Gael,
I went through thinking about this situation almost a year ago and came to the
conclusion that the zone root filesystems have to be UFS so they can be
upgraded. I have turned on MPxIO to give me multipathing support for the zone
roots which are all setup on separate SAN LUNs. I can onl
I have scripted out my zone builds for consistency and to make site specific
additions to the new zones post install. Assuming the zone root filesystem is
on a different disk from the OS, it takes about 15 minutes to create a sparse
zone and 25 minutes to create a whole root zone on an E2900. Th
I just ran across an odd issue. I have a default network printer I setup for
all of my zones. I added that printer to the zone I use as a source for cloning
new zones with no problem and it prints fine. I can create new zones from the
source zone that has the printer defined in it with no proble
Let's try this again. Maybe someone won't hijack this thread this time.
I just ran across an odd issue. I have a default network printer I setup for
all of my zones. I added that printer to the zone I use as a source for cloning
new zones with no problem and it prints fine. I can create new zone
That explains where the problem lies with cloning the zone: The cloning
function doesn't correctly update the content of the printers.conf file so that
those entries which reference the source zone name get changed to the new clone
name. That's a bug. Until it gets fixed, I'll just have to make
That seems reasonable to me too but it would require a change in the lpadmin
command to setup the printers.conf entries with localhost instead of the
server name - or of course, manually editing printers.conf once the printers
are built. I'd have to test to see if using localhost would break pr
I have a couple of servers that are still running U1 but I'd still like to use
zonestat to get as much info as I can.
I get the following output when I run zonestat 1.4.1 with debug turned on:
root> zonestat -l -N
/usr/sbin/prtconf
/bin/pagesize
/bin/echo 'pages_pp_maximum/D;segspt_minfree/D' |
Jeff,
Those lines were already commented out. It looks like the problem is in these
lines:
500 # Get amount and cap of memory locked by processes in each zone.
501 $kstat->update();
502 my $zh = $kstat->{caps};
503 foreach my $z (keys(%$zh)) {
504($lkd_use[$z], $lkd_cap[$z])
27 matches
Mail list logo
