veritas cluster with kernel patch update


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications High Performance Computing veritas cluster with kernel patch update
# 1  
Old 07-09-2008
veritas cluster with kernel patch update

hi all,

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

It would be nice if it's in detail.

Thanks in advance.
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

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)
Discussion started by: Skmanojkum
1 Replies

2. Solaris

Cannot mount Veritas volumes after cluster patch.

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)
Discussion started by: buggin
2 Replies

3. Solaris

Sun cluster and Veritas cluster question.

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)
Discussion started by: sparcguy
5 Replies

4. Solaris

Veritas Cluster

Can I make a veritas cluster on Sun vertual box or Vmwere. Please help me. (4 Replies)
Discussion started by: saga499
4 Replies

5. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

6. Linux

kernel patch update how to

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
Login or Register to Ask a Question
scversions(1M)						  System Administration Commands					    scversions(1M)

NAME
scversions - Sun Cluster version management SYNOPSIS
scversions [-c] DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no arguments, the scversions command prints a message indicating whether a commitment is needed. OPERANDS
The following operands are supported: -c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality. When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor- rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and some new functionality introduced in the upgrade might be unavailable. When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func- tionality becomes available and any administrative restrictions are removed. If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the command has no effect because the cluster is already running at the highest possible level of functionality. If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam- ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver- sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster. EXIT STATUS
0 Success non-zero Failure ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
scinstall(1M) Sun Cluster 3.2 17 Aug 2007 scversions(1M)