04-26-2013
Little time - so I shall be quick.
What PowerHA/HACMP (now System Mirror) monitors - traditionally - is the topology - for failures - and based on what has happened, it makes modifications.
1) Disks are a resource, not topology
2) diskhb network is a NON-IP network, so application service is not dependent on that.
3) HACMP does not respond - out of the box - to resource failures. You need to setup an application and/or event notification to respond to that.
Suppose, rather than both fc - you had said both/all ethernet (i.e., IP connectivity) - the result would be the same - HACMP does not move the resource group. This is because HACMP can see both nodes are operational - but NO nodes (there are only two!) can communicate with other. When no nodes can communicate via IP network HACMP concludes a "Global" network failure, and since no nodes can communicate - it does not matter where the application/service is at - no clients could communicate - so nothing is moved.
The short of it - you need to configure an application monitor that "decides", whether to move or not. A simple way to force a move (one that would work "out of the box" is a so-called panic halt (halt -q). Not really recommended of course, but it does, in an educational/test phase help demonstrate what events HACMP responds to, and what events it does not respond to.
Hope this helps.
10 More Discussions You Might Find Interesting
1. AIX
(0 Replies)
Discussion started by: mhenryj
0 Replies
2. AIX
Hello
I am a noobie to HACMP
I have 2 55A servers and a 7031 disk subsystem
For HACMP to work, do I need to have the hdisks on both servers to match the same drives??
The hdisks on each box are currently different:
hdisk0 and hdisk1 are the internal disks and hdisk2-5 are on the D24 on... (1 Reply)
Discussion started by: mhenryj
1 Replies
3. HP-UX
Hi,
Can anybody advice whether it is possible to configure HACMP in HP-UX Server.
To my knowledge HACMP is IBM Solution.
Thanks && Regards,
N. Poorna Chandra Rao. (2 Replies)
Discussion started by: npcrao
2 Replies
4. AIX
Hi,
I needed space on a FS, and when I've added the space on the filesystem, I did it trough the regular smitty fs inteface and not with smitty cl_lvm.
Can someone help me to repair the situat before a faileover happen ?
Thanks for your help,:mad: (13 Replies)
Discussion started by: azzed27
13 Replies
5. AIX
Hi,
Can we use network for heartbeat, I mean can we use different network card for heartbeat. (6 Replies)
Discussion started by: vjm
6 Replies
6. AIX
hi
can anyone explain the concepts of HACMP and configuration (step by step) (2 Replies)
Discussion started by: udtyuvaraj
2 Replies
7. 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
8. AIX
Does anyone has idea about, what is the ibm standard HACMP trip interval?
We have 20 second.
lssrc -ls topsvcs
Subsystem Group PID Status
topsvcs topsvcs 1843200 active
Network Name Indx Defd Mbrs St Adapter ID Group ID
HB Interval =... (7 Replies)
Discussion started by: allwin
7 Replies
9. AIX
Hi.
We have a two node HA cluster.
We got a request to change one of the VG name?
Is there an option to do this online ? If it requires downtime can someone please explain me the steps for doing it ?
Let me know if you need any outputs from the servers (1 Reply)
Discussion started by: newtoaixos
1 Replies
10. AIX
hello
ive 2 nodes aix 6100-04-10-1119 with hacmp 6.1.0.0
my qustion is :
can i add default gateway to one member node with hacmp a live or to do take over to realse one of the members ?
thanks
When it is urgent, then open the thread up in the appropriate subforum next time, thanks. (3 Replies)
Discussion started by: ariec
3 Replies
LEARN ABOUT HPUX
cmdeleteconf
cmdeleteconf(1m) cmdeleteconf(1m)
NAME
cmdeleteconf - Delete either the cluster or the package configuration
SYNOPSIS
cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...]
DESCRIPTION
cmdeleteconf deletes either the entire cluster configuration, including all its packages, or only the specified package configuration. If
neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all its packages. If
the local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration. If
only the package_name is specified, the configuration of package_name in the local cluster is deleted. If both cluster_name and pack-
age_name are specified, the package must be configured in the cluster_name, and only the package package_name will be deleted. cmdelete-
conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the con-
figuration version. The local cluster is the cluster that the node running the cmdeleteconf command belongs to.
Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration.
To delete the cluster configuration, halt the cluster first. To delete a package configuration you must halt the package first, but you do
not need to halt the cluster (it may remain up or be brought down). To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete
all packages with STORAGE_GROUP defined.
While deleting the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration. In
this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster. If
the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config-
uration before doing any other Serviceguard command.
Options
cmdeleteconf supports the following options:
-f Force the deletion of either the cluster configuration or the package configuration.
-v Verbose output will be displayed.
-c cluster_name
Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster.
-p package_name
Name of an existing package to delete from the cluster. The package must be halted already. There should not be any
packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only).
RETURN VALUE
Upon completion, cmdeleteconf returns one of the following values:
0 Successful completion.
1 Command failed.
EXAMPLES
The high availability environment contains the cluster, clusterA , and a package, pkg1.
To delete package pkg1 in clusterA, do the following:
cmdeleteconf -f -c clusterA -p pkg1
To delete the cluster clusterA and all its packages, do the following:
cmdeleteconf -f -c clusterA
AUTHOR
cmdeleteconf was developed by HP.
SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m).
Requires Optional Serviceguard Software cmdeleteconf(1m)