04-22-2016
Quote:
Originally Posted by
agent.kgb
1. make an HACMP snapshot before migration/mksysb.
2. I personally would do server and IP migration separately. Either first IP migration and cluster reconfiguration and then server migration or vice versa, but not all at the same time.
Many changes at once - too many points of failures and too much troubleshooting in case of a problem.
I thought about that, but here is the issue;
Both networks have restrictions. I cannot put old IP (172.X) on the new hardware as it connect to the new network and vice versa, that is what makes it so complicated.
10 More Discussions You Might Find Interesting
1. Linux
i'm a grad student taking a UNIX course and a networks course (i have a background in C++ and JAVA). i'm trying to combine the two classes.
My questions stems from a networks programming homework assignment below:
"Using the operating system and language of your choice, develop a program to... (5 Replies)
Discussion started by: trostycp
5 Replies
2. Solaris
I realise this is an odd request - but I need advice please..
I have two server - in different geographical locations..
The have 2 local 72gb disks which are mirrored. I need to get storage added to increase both to 300gb in total each and this needs to be mirrored in case of failure. The... (2 Replies)
Discussion started by: frustrated1
2 Replies
3. AIX
Hi,
redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages.
- My system is ML11 :
oslevel –r
4330-11
- But xlC.rte is on wrong version :
lslpp -L xlC.rte
xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies
4. Linux
Evening all,
Im trying to get a script that will:
Select the most 3 recent files in a specific directory
Run a command on them (like chmod)
Ask of you would like to continue
Copy the files to another directory
If a linux guru could help me out, it would be very much appreciated.
Thanks... (2 Replies)
Discussion started by: Wiggins
2 Replies
5. Hardware
Hi all,
I've got an issue with my PC and was wondering what you thought might be the issue.
The problem manifests it'self in two ways (at least I'm assuming it's related).
1. I turn the power on at the wall and press the on button, but nothing happens. I have to wait for several seconds to... (3 Replies)
Discussion started by: DougyC
3 Replies
6. Hardware
If anyone here is successfully running Linux Mint and PC-BSD on two dedicated hard disk drives, (no emulator or partitioning stuff), using Phenom II or Athlon II CPU, I'd like to ask your help to pick hardware! (5 Replies)
Discussion started by: Varsel
5 Replies
7. Solaris
We have hardware RAID configured on our T6320 server and two LDOMs are running on this server. One of our disk got failed and replaced. After replacemnt the newly installed disk not detected by RAID controlled so Oracle suggested to upgrade the REM firmware. As this is the standalone production... (0 Replies)
Discussion started by: rock123
0 Replies
8. HP-UX
Hi guys,
I'm moving some vPars from BL860c I2 and BL870c I2 using the DRD clone and relocation. In some case, as instance to upgrade to BL870c I2, the ERRATA document reports some additional driver to be added to the image made by the DRD and then recompile the kernel before the move to the... (0 Replies)
Discussion started by: cecco16
0 Replies
9. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
10. Shell Programming and Scripting
I am working on UNIX AIX to Linux migration.
Does anybody know the good site for doing this?
Thanks for contribution (4 Replies)
Discussion started by: digioleg54
4 Replies
LEARN ABOUT DEBIAN
ocf_heartbeat_xen
OCF_HEARTBEAT_XEN(7) OCF resource agents OCF_HEARTBEAT_XEN(7)
NAME
ocf_heartbeat_Xen - Manages Xen unprivileged domains (DomUs)
SYNOPSIS
Xen [start | stop | monitor | migrate_to | migrate_from | meta-data | validate-all]
DESCRIPTION
Resource Agent for the Xen Hypervisor. Manages Xen virtual machine instances by mapping cluster resource start and stop, to Xen create and
shutdown, respectively.
A note on names
We will try to extract the name from the config file (the xmfile attribute). If you use a simple assignment statement, then you should be
fine. Otherwise, if there's some python acrobacy involved such as dynamically assigning names depending on other variables, and we will try
to detect this, then please set the name attribute. You should also do that if there is any chance of a pathological situation where a
config file might be missing, for example if it resides on a shared storage. If all fails, we finally fall back to the instance id to
preserve backward compatibility.
Para-virtualized guests can also be migrated by enabling the meta_attribute allow-migrate.
SUPPORTED PARAMETERS
xmfile
Absolute path to the Xen control file, for this virtual machine. (required, string, no default)
name
Name of the virtual machine. (optional, string, no default)
shutdown_timeout
The Xen agent will first try an orderly shutdown using xm shutdown. Should this not succeed within this timeout, the agent will
escalate to xm destroy, forcibly killing the node. .sp If this is not set, it will default to two-third of the stop action timeout. .sp
Setting this value to 0 forces an immediate destroy. .sp
(optional, string, no default)
allow_mem_management
This parameter enables dynamic adjustment of memory for start and stop actions used for Dom0 and the DomUs. The default is to not
adjust memory dynamically. (optional, boolean, default 0)
node_ip_attribute
In case of a live migration, the system will default to using the IP address associated with the hostname via DNS or /etc/hosts. .sp
This parameter allows you to specify a node attribute that will be queried instead for the target node, overriding the IP address. This
allows you to use a dedicated network for live migration traffic to a specific node. .sp Warning: make very sure the IP address does
point to the right node. Or else the live migration will end up somewhere else, greatly confusing the cluster and causing havoc.
(optional, string, no default)
reserved_Dom0_memory
In case memory management is used, this parameter defines the minimum amount of memory to be reserved for the dom0. The default minimum
memory is 512MB. (optional, string, default 512)
monitor_scripts
To additionally monitor services within the unprivileged domain, add this parameter with a list of scripts to monitor. (optional,
string, no default)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 60.
stop
Stops the resource. Suggested minimum timeout: 40.
migrate_from
Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 120.
migrate_to
Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 120.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10.
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 Xen resource using the crm(8) shell:
primitive p_Xen ocf:heartbeat:Xen
params
xmfile=string
meta allow-migrate="true"
op monitor depth="0" timeout="30" interval="10"
SEE ALSO
http://www.linux-ha.org/wiki/Xen_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_XEN(7)