Operating System - HP-UX
1829587 Members
2074 Online
109992 Solutions
New Discussion

System reboot for DST patches

 
Nishan Douglas
New Member

System reboot for DST patches

We plan to install the following patches for Ext. DST but have some concerns about the reboot causing High Availability to believe that there was a failure and move applications to the backup server. Is there any way to avoid the reboot or to stop the autoreboot and allow manual reboot?

PHCO_34668
PHKL_29243
PHSS_33944
PHSS_35379
sdk14_14212_pa.depot
sdk14aa_14212_pa.depot
2 REPLIES 2
Steven E. Protter
Exalted Contributor

Re: System reboot for DST patches

Shalom,

You can do one of the following plans.

Build a custom depot that includes all the above patches and at the proper time swinstall -x reboot=true install.

That lets you choose the time of reboot.

You can also use swinstall -i on the same custom depot and defer the reboot until you are ready.

swcopy is used to create a custom depot containing a combination of patches and software depots.

To simply, read the patch notes of each patch and identify which ones require reboot. Install those that do not require reboot earlier and save the reboot patches for the time you want to boot. You may find there is only one patch that requires reboot.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
A. Clay Stephenson
Acclaimed Contributor

Re: System reboot for DST patches

Your problems extend beyond simply how to prevent the autoreboot. Any patching on a high-availability cluster should be done ONLY by someone with HA experience and knowledge of your specific packages.

Normally, the thing that you would want to do is to move all the packages on a given node to other nodes in the cluster and then halt the node. Apply your patches and then allow the node to rejoin the cluster. At that point, you might choose to move the packages back to the original node.

In any event, if you aren't familiar with commands like cmhaltpkg, cmrunpkg, cmhaltnode, cm* --- then you aren't the one that needs to be applying ANY patches.
If it ain't broke, I can fix that.