can someone please share their process on how to kernel patch a red hat ent 4 with veritas cluster 5? it's compose of a primary and backup node. the resources are db, disk, nic.
it doesn't need to be detail, just give me the steps like:
login to the backup node and update the kernel
reboot the backup node
check the kernel is updated
failover the cluster and check if the resources are up on the backup node
patch the primary node with the new kernel and reboot
failover it back
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
I am working with a Sun StoredgeTek 6540 disk array connected to two Sun 490 servers. After taking one of the 490 nodes on the cluster down to single user mode I proceeded to install the latest cluster patch from Oracle. After the patch was completed the system rebooted, failed to rejoin the... (2 Replies)
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Hi All,
I need to update my redhatas4 kernel with kernel-2.6.9-67.0.20.EL.src.rpm.
When I run this
# rpm -ivh kernel-2.6.9-67.0.20.EL.src.rpm
warning: user brewbuilder does not exist - using root
warning: group brewbuilder does not exist - using root
warning: user brewbuilder does... (2 Replies)
CRM_DIFF(8) [FIXME: manual] CRM_DIFF(8)NAME
crm_diff - identify changes to the cluster configuration and apply patches to the configuration files
SYNOPSIS
crm_diff [-?|-V] [-o filename] [-O string] [-p filename] [-n filename] [-N string]
DESCRIPTION
The crm_diff command assists in creating and applying XML patches. This can be useful for visualizing the changes between two versions of
the cluster configuration or saving changes so they can be applied at a later time using cibadmin.
OPTIONS --help, -?
Print a help message.
--original filename, -o filename
Specify the original file against which to diff or apply patches.
--new filename, -n filename
Specify the name of the new file.
--original-string string, -O string
Specify the original string against which to diff or apply patches.
--new-string string, -N string
Specify the new string.
--patch filename, -p filename
Apply a patch to the original XML. Always use with -o.
--cib, -c
Compare or patch the inputs as a CIB. Always specify the base version with -o and provide either the patch file or the second version
with -p or -n, respectively.
--stdin, -s
Read the inputs from stdin.
EXAMPLES
Use crm_diff to determine the differences between various CIB configuration files and to create patches. By means of patches, easily reuse
configuration parts without having to use the cibadmin command on every single one of them.
1. Obtain the two different configuration files by running cibadmin on the two cluster setups to compare:
cibadmin -Q > cib1.xml
cibadmin -Q > cib2.xml
2. Determine whether to diff the entire files against each other or compare just a subset of the configurations.
3. To print the difference between the files to stdout, use the following command:
crm_diff -o cib1.xml -n cib2.xml
4. To print the difference between the files to a file and create a patch, use the following command:
crm_diff -o cib1.xml -n cib2.xml > patch.xml
5. Apply the patch to the original file:
crm_diff -o cib1.xml -p patch.xml
FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
SEE ALSO
???
AUTHOR
crm_diff was written by Andrew Beekhof.
[FIXME: source] 07/05/2010 CRM_DIFF(8)