Installing Patches to a global container with zones (containers)

Just want to make sure:
I'm going to patch a server (global) that contain 2 zones (containers).  Do i need to log into the individual zones to shut them down individually or can i do that from the global level?
This is what i was going to do:
1. Log into zone 1
2. List zones
    zoneadm list –v

3. Shutdown zone
    zoneadm -z zonename shutdown

4. Log into zone 2
5. List zones
    zoneadm list –v

6. Shutdown zone
    zoneadm -z zonename shutdown

7. Log into global
8. Perform patching and reboot
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

it is strongly recommended (and often required) that you do the patching in single user mode. This automatically implies that all non-global zones are shutdown and you don't have to do this manually.

(Solaris Live upgrade can be used to patch a live system, but that's a different topic)
Joseph GanSystem AdminCommented:
You did not mention what version of your Solaris in global zone and in containers. If they are the same, then apply one in globe zone in single-suer mode should be fine. Otherwise you need to apply patches separately.
The same procedure to the Live patching, see this for live patching in the global zone here:
sajmf0408Author Commented:
Hello all,
I successfully installed the patches.  I halted the non-global zones:
zoneadm -z zonename halt

confirmed the halt:
zoneadm list -cv (the "-" indicating halt status)

ran the patches, rebooted.  The zones came back up automatically and that was it. Thanks for all of your help.

Btw, we're using Solaris10
For future reference, you should never issue a zoneadm halt, because this is not a clean shutdown of the zone. Zoneadm halt kills of all processes and can be bad if you run a database.

It is also recommended to boot into single user mode when applying certain patches. This way you're sure your zones are not running and certain patches also require that the global zone is in single user mode.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sajmf0408Author Commented:
i tried to "shutdown" but it didn't like that command so that's when i used halt. I will take that into consideration in the future.  Thanks.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.