All RHEL cluster deployments with CLX require an architecture review performed jointly by HP and Red
Hat. All questions regarding architectural concepts, stretched cluster configurations, architecture
reviews, and support issues should be directed to HP through your HP sales or support contacts, and
should not be directed to Red Hat.
For additional information pertaining to Red Hat, see the following Red Hat Knowledgebase article:
Is HP StorageWorks CLX (Continuous Access) supported with Red Hat Enterprise Linux Cluster and
High Availability?
https://access.redhat.com/kb/docs/DOC-62648
For additional information pertaining to HP, see the following HP web page:
HP Cluster Extension Software - Overview and Features
http://www.hp.com/go/clx
HP Serviceguard to RHEL cluster migration
Serviceguard to RHEL cluster migration guides are available on Red Hat's Knowledgebase through the
Red Hat Customer Portal. Access to the guides is password protected and requires a Customer Portal
account. They are intended to help Serviceguard users who want to move to RHEL 5.3 clusters. (The
main guide also references RHEL 5.2, which has some serious limitations for fencing with SCSI-3
persistent reservations; RHEL 5.3 or later is preferred.) Red Hat is not aware of any changes through
RHEL 5.7 that would make content in these guides obsolete, so they are useful for migration to more
recent versions of RHEL5 clusters as well.
Although not written with RHEL6 clusters in mind, large portions of these guides might still be useful
when migrating to RHEL6. However, some product enhancements have rendered some content
obsolete. Here are a few of the more notable changes:
• As of RHEL 6.0, both IPv4 and IPv6 are fully supported for cluster networking, including
cluster heartbeats.
• As of RHEL 6.0, freeze and unfreeze operations are supported; these can be used to perform
maintenance on a service (see section 8.3.2 of the Cluster Administration guide). Also, freeze
and unfreeze operations were added to RHEL5 in the 5.3 release.
• As of RHEL 6.1, additional watchdog integration allows a node to reboot itself when it loses
quorum.
• As of RHEL 6.2, the RHEL watchdog code has been integrated with fence_scsi so the
watchdog service can automatically reboot a node after it has been fenced.
The migration guides include:
Migrating an HP Serviceguard for Linux (SGLX) Cluster to Red Hat Cluster Suite (RHCS)
https://access.redhat.com/knowledge/refarch/2009-migrating-hp-serviceguard-linux-sglx-cluster-red-hat-
cluster-suite-rhcs
This provides the most general information and should be read first if you are not familiar with the
migration process. It describes a procedure to migrate an HP Serviceguard for Linux (SGLX)
cluster to a cluster running Red Hat Cluster Suite software. (Red Hat Cluster Suite is the RHEL5
term for the RHEL6 High Availability Add-On and its associated products.) It discusses differences
between the two clusters, including differences pertaining to membership, quorum, fencing to
prevent data corruption, and application failover control. A step-by-step process describes how to
use configuration information from an existing SGLX cluster to quickly create a cluster from RHCS
components. The guide lists features that exist in SGLX that have no comparable Red Hat Cluster
Suite counterpart. Many of those differences can be managed by users through custom scripts,
and examples are provided.
Migrating an HP Serviceguard for Linux (SGLX) Oracle Toolkit to Red Hat Cluster Suite (RHCS) for
Red Hat Enterprise Linux 5
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais