08-13-2013
Since HACMP 5.X the cluster manager gets started automatically - that is why it is in the inittab.
There are three kinds of resource groups and each have their own startup (node just coming up) and recovery policy.
So, to be to the point: HACMP v4 and earlier did not have HACMP in inittab as best practice - because the cluster manager was not always active. Starting with HACMP v5 the cluster manager is always active, so the daemons (not the resource groups) are always (meant to be) activated when the node/server starts.
Hope this helps.
10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Recently i faced problem starting oracle application on my galaxy cluster on one node.In the log i found that the CRS demon was not started after the booting of the node , so i manually tried to start it but faced some error.
So here are the work around that i had done and the CRS services got... (0 Replies)
Discussion started by: amitranjansahu
0 Replies
2. AIX
Hello,
Running AIX 6.1, AIX machine is HACMP node.
Recently I set up ntp service. Started xntpd by hand - everythig is OK. Configured xntpd to start after reboot and rebooted the machine. After reboot checked xntpd:
# lssrc -a|grep ntp
xntpd tcpip ... (5 Replies)
Discussion started by: vilius
5 Replies
3. AIX
This post just as a follow-up for thread https://www.unix.com/aix/115548-hacmp-5-4-aix-5300-10-not-working.html: there was a bug in the clcomdES that would cause the Two-Node-Cluster-Configuration-Assistant to fail even with a correct TCP/IP adapter setup. That affected HACMP 5.4.1 in combinatin... (0 Replies)
Discussion started by: shockneck
0 Replies
4. AIX
Hi
What is the procedure to upgrade the MQ from 6 to 7 in aix hacmp cluster. Do i need to bring down the cluster
services running in both the nodes and then give #smitty installp in both the nodes separately. Please assist... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
5. AIX
Hi all,
I was wondering if someone direct me in how to Make system backup for 2 nodes HACMP cluster ( system image ) .
What are the consideration for this task (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies
6. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
7. AIX
As i have updated a lot of HACMP-nodes lately the question arises how to do it with minimal downtime. Of course it is easily possible to have a downtime and do the version update during this. In the best of worlds you always get the downtime you need - unfortunately we have yet to find this best of... (4 Replies)
Discussion started by: bakunin
4 Replies
8. AIX
Hi,
A customer I'm supporting once upon a time broke their 2 cluster node database servers so they could use the 2nd standby node for something else. Now sometime later they want to bring the 2nd node back into the cluster for resilance. Problem is there are now 3 VG's that have been set-up... (1 Reply)
Discussion started by: elcounto
1 Replies
9. Shell Programming and Scripting
Hi,
I just started working on a script. After my research, i found a command which can help me:
AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2.
So my script has to... (4 Replies)
Discussion started by: draghun9
4 Replies
10. AIX
I have troubles making clstat work. All the "usual suspects" have been covered but still no luck. The topology is a two-node active/passive with only one network-interface (it is a test-setup). The application running is SAP with DB/2 as database. We do not use SmartAssists or other gadgets.
... (8 Replies)
Discussion started by: bakunin
8 Replies
LEARN ABOUT CENTOS
ocf_heartbeat_lvm
OCF_HEARTBEAT_LVM(7) OCF resource agents OCF_HEARTBEAT_LVM(7)
NAME
ocf_heartbeat_LVM - Controls the availability of an LVM Volume Group
SYNOPSIS
LVM [start | stop | status | monitor | meta-data | validate-all]
DESCRIPTION
Resource script for LVM. It manages an Linux Volume Manager volume (LVM) as an HA resource.
SUPPORTED PARAMETERS
volgrpname
The name of volume group.
(required, string, no default)
exclusive
If set, the volume group will be activated exclusively. This option works one of two ways. If the volume group has the cluster
attribute set, then the volume group will be activated exclusively using clvmd across the cluster. If the cluster attribute is not set,
the volume group will be activated exclusively through the use of the volume_list filter in lvm.conf. In the filter scenario, the LVM
agent verifies that pacemaker's configuration will result in the volume group only being active on a single node in the cluster and
that the local node's volume_list filter will prevent the volume group from activating outside of the resource agent. On activation
this agent claims the volume group through the use of a unique tag, and then overrides the volume_list field in a way that allows the
volume group to be activated only by the agent. To use exclusive activation without clvmd, the volume_list in lvm.conf must be
initialized. If volume groups exist locally that are not controlled by the cluster, such as the root volume group, make sure those
volume groups are listed in the volume_list so they will be allowed to activate on bootup.
(optional, boolean, default false)
tag
If "exclusive" is set on a non clustered volume group, this overrides the tag to be used.
(optional, string, default "pacemaker")
partial_activation
If set, the volume group will be activated even only partial of the physical volumes available. It helps to set to true, when you are
using mirroring logical volumes.
(optional, string, default "false")
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 30.
stop
Stops the resource. Suggested minimum timeout: 30.
status
Performs a status check. Suggested minimum timeout: 30.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10.
methods
Suggested minimum timeout: 5.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a LVM resource using the crm(8) shell:
primitive p_LVM ocf:heartbeat:LVM
params
volgrpname=string
op monitor depth="0" timeout="30" interval="10"
SEE ALSO
http://www.linux-ha.org/wiki/LVM_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_LVM(7)