10 More Discussions You Might Find Interesting
1. AIX
Hello,
I worked on setting up NFSv3 and NFSv4 (novice) shares separately. I was trying to find a way to migrate existing NFSv3 fileshares to NFSv4 as is.
I found a redbook online called "Securing NFS in AIX". It has good info.
I am able to create a new NFSv4 share, do not know how to... (4 Replies)
Discussion started by: System Admin 77
4 Replies
2. AIX
Hi all,
I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 Replies
3. AIX
hey frnds I am trying to migrate a bash script over the AIX machine , but was getting error with ps and read commands, so I make the few changes in script and have also chnaged the shell from bash to ksh
below is my script... (5 Replies)
Discussion started by: sumit_saxena
5 Replies
4. AIX
HI ,
We are in process to migrate from UNIX to AIX 6.1 version . I need to understand differences between commands that are used in UNIX and AIX.
I want to make sure AIX has all command options avaliable from HP Unix.If any mismatch it should be addressed .
Since many commands are used it... (2 Replies)
Discussion started by: Perlbaby
2 Replies
5. AIX
Hi,
I'm able to migrate UNIX users/groups from Solaris to AIX (with same password using 13-char encrypted password from shadow file) but no luck with RHEL 5 to AIX.
I see encrypted password in RHEL 5 is bit lengthier than 13-char. Is there any way to convert encrypted password such that same... (1 Reply)
Discussion started by: reddyr
1 Replies
6. AIX
Guys,
We are planning to upgrade one of our NIM server to AIX 6.1 from 5.3...
Since the server itself is a NIM Server we can't perform it via NIM & I'm choosing to do CD install.. The Install method would be Upgrade installation.
Is there anything special that I need to consider before... (5 Replies)
Discussion started by: kkeng808
5 Replies
7. AIX
:(
Hi Grue, I am very new in AIX/UNIX environment. Please give me answer that during the upgrading or Migrating to 6.1 the AIX Server the applications of this server is accessible to Apps users or not? Thanks (2 Replies)
Discussion started by: Tahniet
2 Replies
8. AIX
Hi All,
I am currently facing new problem of migrating C(c language) application from AIX machine to Linux machine. We are using GCC to compile the source code..
But facing with the compilation issues, with lot of GCC C libs differing between AIX box to Linux box...
Pls help me... (3 Replies)
Discussion started by: karthikc
3 Replies
9. AIX
Hi,
my requirement is to migrate easytrieve running on Z/OS to AIX platform.
can anyone let me know what changes should be made if we do such a migration. (0 Replies)
Discussion started by: rohit510
0 Replies
10. AIX
Hi all,
I was wondering if anyone out there knew if it was possible to migrate users from AIX to Linux.
What we want to do is install OpenLDAP on a Linux machine and port all the users over to LDAP. I've googled around and could only find a few things, such as mrgpwd - but that only comes... (0 Replies)
Discussion started by: djcronos
0 Replies
OCF_HEARTBEAT_VIRTUA(7) OCF resource agents OCF_HEARTBEAT_VIRTUA(7)
NAME
ocf_heartbeat_VirtualDomain - Manages virtual domains through the libvirt virtualization framework
SYNOPSIS
VirtualDomain [start | stop | status | monitor | migrate_to | migrate_from | meta-data | validate-all]
DESCRIPTION
Resource agent for a virtual domain (a.k.a. domU, virtual machine, virtual environment etc., depending on context) managed by libvirtd.
SUPPORTED PARAMETERS
config
Absolute path to the libvirt configuration file, for this virtual domain. (unique, required, string, no default)
hypervisor
Hypervisor URI to connect to. See the libvirt documentation for details on supported URI formats. The default is system dependent.
(optional, string, no default)
force_stop
Always forcefully shut down ("destroy") the domain on stop. The default behavior is to resort to a forceful shutdown only after a
graceful shutdown attempt has failed. You should only set this to true if your virtual domain (or your virtualization backend) does not
support graceful shutdown. (optional, boolean, default 0)
migration_transport
Transport used to connect to the remote hypervisor while migrating. Please refer to the libvirt documentation for details on transports
available. If this parameter is omitted, the resource will use libvirt's default transport to connect to the remote hypervisor.
(optional, string, no default)
migration_network_suffix
Use a dedicated migration network. The migration URI is composed by adding this parameters value to the end of the node name. If the
node name happens to be an FQDN (as opposed to an unqualified host name), insert the suffix immediately prior to the first period (.)
in the FQDN. At the moment Qemu/KVM and Xen migration via a dedicated network is supported. .sp Note: Be sure this composed host name
is locally resolveable and the associated IP is reachable through the favored network. (optional, string, no default)
monitor_scripts
To additionally monitor services within the virtual domain, add this parameter with a list of scripts to monitor. .sp Note: when
monitor scripts are used, the start and migrate_from operations will complete only when all monitor scripts have completed
successfully. Be sure to set the timeout of these operations to accommodate this delay. (optional, string, no default)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 90.
stop
Stops the resource. Suggested minimum timeout: 90.
status
Performs a status check. Suggested minimum timeout: 30. Suggested interval: 10.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10.
migrate_from
Executes steps necessary for migrating the resource away from the node. Suggested minimum timeout: 60.
migrate_to
Executes steps necessary for migrating the resource to the node. Suggested minimum timeout: 120.
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 VirtualDomain resource using the crm(8) shell:
primitive p_VirtualDomain ocf:heartbeat:VirtualDomain
params
config=string
meta allow-migrate="true"
op monitor depth="0" timeout="30" interval="10"
SEE ALSO
http://www.linux-ha.org/wiki/VirtualDomain_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_VIRTUA(7)