Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 Managing Serviceguard Fifteenth Edition > Appendix E Software Upgrades

Performing a Rolling Upgrade
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

Limitations of Rolling Upgrades

The following limitations apply to rolling upgrades:

  • During a rolling upgrade, you should issue Serviceguard commands (other than cmrunnode and cmhaltnode) only on a node containing the latest revision of the software. Performing tasks on a node containing an earlier revision of the software will not work or will cause inconsistent results.

  • You cannot modify the hardware configuration—including the cluster’s network configuration—during rolling upgrade.

  • You cannot modify the cluster or package configuration until the upgrade is complete.

    If you need to modify the configuration (for example, to take advantage of new features), upgrade all nodes to the new release, then modify the configuration file and copy it to all the nodes.

    NOTE: This means that you cannot migrate to the HP-UX 11i v3 agile addressing scheme for device files during a rolling upgrade if cluster lock disks are used as a tie-breaker, because that involves changing the cluster configuration. See “Updating the Cluster Lock Configuration” for instructions in this case. See “About Device File Names (Device Special Files)” for more information about agile addressing.

  • None of the features of the newer release of Serviceguard are allowed until all nodes have been upgraded.

  • Binary configuration files may be incompatible between releases of Serviceguard. Do not manually copy configuration files between nodes.

  • No more than two versions of Serviceguard can be running in the cluster while the rolling upgrade is in progress.

  • Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or HP-UX within the cluster. HP strongly recommends that you upgrade all cluster nodes as quickly as possible to the new release level.

  • You cannot delete Serviceguard software (via swremove) from a node while a rolling upgrade is in progress.

Before You Start

Make sure you plan sufficient system capacity to allow moving the packages from node to node during the process without an unacceptable loss of performance.

Running the Rolling Upgrade

  1. Halt the node you want to upgrade. You can do this in Serviceguard Manager, or use the cmhaltnode command. This will cause the node’s packages to start up on an adoptive node

  2. Edit the /etc/rc.config.d/cmcluster file to include the following line:

    AUTOSTART_CMCLD = 0

  3. Upgrade the node to the new HP-UX release, including Serviceguard. You can perform other software or hardware upgrades if you wish (such as installation of Veritas Volume Manager software), provided you do not detach any SCSI cabling. See the section on hardware maintenance in the “Troubleshooting” chapter.

  4. Edit the /etc/rc.config.d/cmcluster file to include the following line:

    AUTOSTART_CMCLD = 1

  5. If the Event Monitoring Service (EMS) is configured, restart it as follows:

    1. Kill all EMS monitors.

    2. Stop EMS clients.

    3. Kill all registrar processes.

    4. Kill the p_client demon.

    The p_client process restart immediately. The EMS registrar and monitor processes will be restarted automatically when they are needed.

    For more information, see “Using the Event Monitoring Service ”.

  6. Restart the cluster on the upgraded node. You can do this in Serviceguard Manager: from the System Management Homepage (SMH) choose Tools -> Serviceguard Manager, then select the node and choose Administration -> Run Node... Or, on the Serviceguard command line, issue the cmrunnode command.

  7. Repeat this process for each node in the cluster.

If the cluster fails before the rolling upgrade is complete (because of a catastrophic power failure, for example), you can restart the cluster by entering the cmruncl command from a node which has been upgraded to the latest version of the software.

Keeping Kernels Consistent

If you change kernel parameters as a part of doing an upgrade, be sure to change the parameters to the same values on all nodes that can run the same packages in case of failover.

Migrating cmclnodelist entries from A.11.15 or earlier

Information in the cmclnodelist file is migrated to the new Access Control Policy form. All the hostname username pairs from the cmclnodelist file are now triplets in the cluster configuration file, and all have the role of Monitor. If you want to grant administration roles to non-root users, add more entries in the configuration file.

“Controlling Access to the Cluster” for more information about access control policies.



Guidelines for Rolling Upgrade
  		 


Example of a Rolling Upgrade  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.