[SunHELP] A discussion about patch policy

Dieter Montanez dietermontanez at bellsouth.net
Tue Jun 14 11:56:32 CDT 2005

We do normally not install a cluster provided by SUN. We
run "smpatch" utility from SUNWppro and determine the
really required patches for every individual system.
Since the systems in question are to run on high
availability environments (Fossil and Nuclear power plants)
we carefully review each patch to asses any impact on the
applicatioon software. We than first install the patches on
staging machines and run them for a while there before we
proceed to install them on the actual production systems.
All our systems are run on a redundant basis, so we normally
first patch the "stand by" units and than make a failover to
them to proceed to install on the peer systems. All patching
is done on "single user mode" remotely via terminal console
servers using a modified version of the "instalcluster" script
but with our own patch_order patchlist.


-----Original Message-----
From: sunhelp-bounces at sunhelp.org [mailto:sunhelp-bounces at sunhelp.org]On
Behalf Of Grindell, Joan M.
Sent: Tuesday, June 14, 2005 8:46 AM
To: 'The SunHELP List'; 'Solaris-Users mailinglist'
Subject: [SunHELP] A discussion about patch policy

Good Morning,

	We are having a discussion about cluster patch policy and i was
hoping to get input from these lists.

	Sun recommends that cluster patches be installed in single user
mode.  Some folks here prefer to install the patches remotely and reboot
remotely.  What policies do other admins take and why?  What are the dangers
if any of installing remotely?

Many thanks,
SunHELP maillist  -  SunHELP at sunhelp.org

More information about the SunHELP mailing list