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)
Discussion started by: itik
2 Replies
LEARN ABOUT CENTOS
crm_diff
PACEMAKER(8) System Administration Utilities PACEMAKER(8)NAME
Pacemaker - Part of the Pacemaker cluster resource manager
SYNOPSIS
crm_diff original_xml operation [options]
DESCRIPTION
crm_diff - A utility for comparing Pacemaker configurations (XML format)
The tool produces a custom (diff-like) output which it can also apply like a patch
OPTIONS
-?, --help
This text
-$, --version
Version information
-V, --verbose
Increase debug output
Original XML:
-o, --original=value
XML is contained in the named file
-O, --original-string=value
XML is contained in the supplied string
Operation:
-n, --new=value
Compare the original XML to the contents of the named file
-N, --new-string=value
Compare the original XML to the contents of the supplied string
-p, --patch=value
Patch the original XML with the contents of the named file
Additional Options:
-c, --cib
Compare/patch the inputs as a CIB (includes versions details)
-f, --filter
Suppress irrelevant differences between the two inputs
EXAMPLES
Obtain the two different configuration files by running cibadmin on the two cluster setups to compare:
# cibadmin --query > cib-old.xml
# cibadmin --query > cib-new.xml
Calculate and save the difference between the two files:
# crm_diff --original cib-old.xml --new cib-new.xml > patch.xml
Apply the patch to the original file:
# crm_diff --original cib-old.xml --patch patch.xml > updated.xml
Apply the patch to the running cluster:
# cibadmin --patch patch.xml
AUTHOR
Written by Andrew Beekhof
REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org
Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)
