08-14-2014
Quote:
Originally Posted by
bakunin
Interesting. This should not be the case. I remove volumes and change volume groups actually all the time, in 6.x-clusters as well as in 7.x-clusters. To have one disk remain constant in a VG and do "learning import" (importvg -L) on the other node is usually all it takes.
I usually even replace disks completely by: adding the new disk, mirror, importvg on the passive node, then unmirror, reducevg, another importvg on the passive node. Not even a takeover or application touchdown is necessary that way.
You're probably right, I think removing the cluster definition wouldn't have been necessary had I known it was the Fc adapter holding onto the volume. Of course in the process of narrowing it down it just turned out to be the way I did it. Since it was the only physical volume in the VG (and concurrent) I felt it was the safest way to go about it.
For my scenario I will need to do this (redefine the cluster) anyway due to a complete IP schema change. I may even try out the cluster snapshot feature going forward. Thanks again for the follow-up!
8 More Discussions You Might Find Interesting
1. AIX
hi all
we upgraded hacmp(powerha) from 5.2 to 5.4 recently .
during the failover testing, we found a strange network issue. after standby node took service ip address (172.15.100.8) online at standby NIC, we were able to log in the standby node by telnet 172.15.100.8 which stays at... (1 Reply)
Discussion started by: rs6000er
1 Replies
2. AIX
Around a month ago we suffered a prolonged power outage, due to circumstances the servers and storage arrays were still in use when the UPS dropped. One of the servers was running a flash copy on the database while batch processing had commenced. This is the only server that suffered any further... (2 Replies)
Discussion started by: gull04
2 Replies
3. Shell Programming and Scripting
Hi,
At first I have to say that I know nothing about Linux :(
But I am looking for solution how to copy one file from internal Lowrnace HDS flash memory.
Lowrance HDS is Linux based device.
Here is the link for firmware update files for this unit.
At the end of main firmware file there... (62 Replies)
Discussion started by: PouchX
62 Replies
4. SuSE
I have noticed that when I copy files to flash disk and in UI I see message copy completed in notification area on task bar, usually copy is not completed. So, if I eject the media I loose data.
It is very serious problem because may cause loss of valuable and even critical data.
Moreover, when... (2 Replies)
Discussion started by: netwalker
2 Replies
5. AIX
Looking to find PowerHA with 3rd node used for communication (voting node) only. Does anyone use such configuration with IBM products? (2 Replies)
Discussion started by: gogogo
2 Replies
6. AIX
hello
ive installed powerha 7.1.3 on two servers aix 6.1.9 6100-09-03-1415
work with dmx4 EMC storgae.
after sync cluster ( terminate with OK ) ive see that the repository disk upper only in one machine :
hdiskpower60 00c7f6b59fc60d9d caavg_private active... (1 Reply)
Discussion started by: ariec
1 Replies
7. AIX
I have created a VxVM disk group in AIX7.1. I have tried to added this VxVM disk group in powerHA 6.1. But in cluster VxVM DGs are not listing. Is there any other procedure to add vxvm diskgroup to hacmp.
Please share me steps for adding vxvm diskgroup to hacmp. (6 Replies)
Discussion started by: sunnybee
6 Replies
8. AIX
Hi All,
As per the IBM upgrade/support matrix
IBM Techdocs Technote: PowerHA for AIX Version Compatibility Matrix
we can't do online upgrade or rolling migration from powerha v7.1.0 to v7.1.3. on AIX61_TL9_SP4, So we are following the steps as below ...
1 ) Bring down the cluster
2 )... (2 Replies)
Discussion started by: linux.amrit
2 Replies
LEARN ABOUT CENTOS
crm_node
PACEMAKER(8) System Administration Utilities PACEMAKER(8)
NAME
Pacemaker - Part of the Pacemaker cluster resource manager
SYNOPSIS
crm_node command [options]
DESCRIPTION
crm_node - Tool for displaying low-level node information
OPTIONS
-?, --help
This text
-$, --version
Version information
-V, --verbose
Increase debug output
-Q, --quiet
Essential output only
Stack:
-A, --openais
Only try connecting to an OpenAIS-based cluster
-H, --heartbeat
Only try connecting to a Heartbeat-based cluster
Commands:
-n, --name
Display the name used by the cluster for this node
-N, --name-for-id=value
Display the name used by the cluster for the node with the specified id
-e, --epoch
Display the epoch during which this node joined the cluster
-q, --quorum
Display a 1 if our partition has quorum, 0 if not
-l, --list
Display all known members (past and present) of this cluster (Not available for heartbeat clusters)
-p, --partition
Display the members of this partition
-i, --cluster-id
Display this node's cluster id
-R, --remove=value
(Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches
In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster
Additional Options:
-f, --force
AUTHOR
Written by Andrew Beekhof
REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org
Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)