Sponsored Content
Operating Systems AIX Question about HACMP for active-active mode Post 302365707 by qiulang on Tuesday 27th of October 2009 10:11:57 PM
Old 10-27-2009
Thanks for the answerd and looks like I have got a lot of reading to do! Man Smilie

BTW my original question was "what is the benefit of running HACMP for an active-active cluster with the same app running" Smilie and it looks like RAC may be the only one in this case, right?

And I did find out another term HACMP uses, "mutual takeover", which seems to be relevant to my question. So my understanding of "mutual takeover" is an active-active cluster with different app running (shared-nothing mode). It makes sense to using HACMP here. (and it also makes sense why they don't use the term "active-active" now). But is my understanding correct or I totally got it wrong ? Smilie
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Active / Non Active users ?

Hey, I have few Questions : 1. How to Check/Find who all are the users accessing the server using their id ? 2. How to Check who is the active user or non active user (whose id exists but the access privileges has been removed) ? I am presently using AIX5.3 as a server. Please suggest... (3 Replies)
Discussion started by: varungupta
3 Replies

2. UNIX for Dummies Questions & Answers

active working

hi! i want to create a list of the active working of the system classified by size and run the list on the monitor in a contolled pattern.Every active work has to appear only once. Any suggestions? also how can i create a list of the active working that does not belong to the user root?thanks (5 Replies)
Discussion started by: battaglia
5 Replies

3. AIX

AIX HACMP Active/Passive Config

I have a HACMP 6.1 configured in a active/passive. I have 1 NIC with 3 IP address on (Boot, Persistent and Service ) . All address are routable. One of the application on the HA cluster is also using Boot Ip to send application data. Question : Since all the traffic is passing thru the same... (3 Replies)
Discussion started by: mk8570
3 Replies

4. Solaris

Link based Active Active IPMP

Hi, I need to configure 4 ip address (same subnet and mask) in one ipmp group (two interfaces) in an active active formation (link based). Can some one provide the steps or a tutorial link. Thanks (2 Replies)
Discussion started by: Mack1982
2 Replies

5. Solaris

Port Active?

Hi, I have recently installed autosys R11 on my a container in solaris 10. the container has solaris 10. I am now trying to configure the autosys workload contol center on a windows VM. but i can not get the contol center to log into the the autosys server. when i try to estiblish a... (4 Replies)
Discussion started by: dshakey
4 Replies

6. Linux

active mode ftp connection from linux

Hi, We have one java client which connects to a windows server through ftp in active mode and gets files. When we run this client on hp-ux, it is able to transfer 100k files. But when we run the same client on Linux server it is able to transfer only 200 files at max and it is hanging there... (1 Reply)
Discussion started by: urspradeep330
1 Replies

7. Shell Programming and Scripting

How do I calculate total number of active and non active hosts?

#!/bin/bash for digit in $(seq 1 10) do if ping -c1 -w2 192.168.1.$digit &> /dev/null then echo "192.168.1.$digit is UP" else echo "192.168.1.$digit is DOWN" fi done (3 Replies)
Discussion started by: fusetrips
3 Replies

8. Solaris

VCS not active

Dear All, My current system run Solaris 9 SPARC 64 bit , and VXVM , VCS 4.1. I check all the node information . ls -l /etc/vx/*.exclude /etc/vx/*.exclude: No such file or directory root@devuardbs01 # vxdctl license All features are available: Mirroring Root Mirroring Concatenation... (0 Replies)
Discussion started by: linux_user
0 Replies
versw(8)						      System Manager's Manual							  versw(8)

NAME
versw - Manages the transition from the active version of the operating system to a new version SYNOPSIS
/usr/sbin/versw [option...] OPTIONS
Checks whether a version switch is pending. The versw utility returns a 1 if a version switch is pending (the active and new versions dif- fer), a 0 if a version switch is not pending (the active and new versions are the same). Sets the versw_transition attribute in the generic kernel subsystem of the member-specific /etc/sysconfigtab file to 0 (zero). Prints the old (previously active), active, and new version IDs, the version transition state, and the version switch state. If a version switch is in progress, the version switch state is the member ID of the cluster member running the versw utility plus 100. Otherwise, the version switch state is 0. Unconditionally sets the active version ID to the new version ID in the generic kernel subsystem of the member-specific /etc/sysconfigtab file and in the member's running kernel. Specifies a directory path to an alternative /etc/sysconfigtab file. By default, the member-specific /etc/sysconfigtab file is used. Sets the new version ID in the generic kernel subsystem of the member-specific /etc/sysconfigtab file and in the running kernel. The installation of the Tru64 UNIX operating system and the cluster software automatically sets these values. Sets the versw_tran- sition attribute in the generic kernel subsystem of the member-specific /etc/sysconfigtab file to 1. When run with the -switch option, the versw utility automatically sets this attribute. Attempts to set the active version ID to the new version ID on a standalone system or on all currently active cluster members. When you install Tru64 UNIX on a standalone system, the installation procedure concludes by using a versw -switch command to set the active version to the new version. When you complete a cluster rolling upgrade, by issuing a clu_upgrade -switch, clu_upgrade automatically issues the versw -switch command to set the active and new versions consistently on all cluster members. Checks the return value from the versw() function. See versw(3) for a description of this function. DESCRIPTION
The versw utility manages the transition from the active version of the operating system to a new version. You must be root to use this utility. The active and new operating system versions are recorded in the act_vers and new_vers attributes, respectively, in the generic kernel sub- system of the /etc/sysconfigtab file (or each member's /etc/sysconfigtab file in a cluster). When you install a new version of the Tru64 UNIX operating system or cluster software, the installation procedure automatically issues the versw -setnew command to establish the new version ID in the /etc/sysconfigtab file and in the running kernel. At installation time, the new version ID must always be higher than the active version ID. When installation completes on a standalone system, the active and new versions will be identical. When you install Tru64 UNIX on a stand- alone system, the installation procedure concludes by using a versw -switch command to set the active version to the new version. During a rolling upgrade of a cluster, the active and new versions will not be the same on each cluster member until the rolling upgrade completes. When you conclude the rolling upgrade, by issuing the clu_upgrade -switch command, clu_upgrade automatically issues the versw -switch command to set the active and new versions equal on all cluster members. After all cluster members have been rebooted with the new active version, all features of the new operating system and cluster software are enabled across all cluster members. When called by the clu_upgrade -switch command in a cluster, the versw utility performs the following operations: Compares the active and new version IDs in each member's running kernel. If new versions of the operating system and cluster software have been installed, the new version ID will be higher than the active version ID. If the IDs are identical or the new version ID is less than that of the active ver- sion, the utility issues a warning and exits. Checks that each member's /etc/sysconfigtab file is accessible. If not, the utility issues a warning and exits. Checks that all members have booted with the new version. If not, the utility issues a warning and you must either reboot the members or run versw -forcesw to continue. Use the clu_get_info command to determine which systems are running at or below their installed version. Checks for blocking conditions. If any exist, the the versw utility prints an error message and exits. If the new soft- ware has introduced a change or enhancement that is incompatible with the active version, the component sets up a condition that blocks the rolling upgrade. Such incompatibilities usually involve changes to configuration files, on-disk structures, or local or remote interface protocols. Operating system components establish a blocking condition by placing files in the /var/adm/versw directory. These text files provide instructions for manually restoring compatibility between installed and new versions: for instance, by editing a configuration file or running a data conversion script. You must follow the directions in these files to proceed with the upgrade. Moving these files to another directory removes the blocking condition. Determines whether all running members are capable of the switch this member is propos- ing. If not, it displays an error and exits. Sets the versw_transition attribute in the generic kernel subsystem in each member's /etc/sysconfigtab file (and in each member's running kernel) to 1. Requests that the connection manager stop new members from joining the cluster until the completion of the version switch. Sets the active version to the new version in the generic kernel subsystem of each cluster member's /etc/sysconfigtab file. Note that, if a member goes down during this stage, the versw utility exits with an error message. All running members clear their versw_transition attributes and restore their /etc/sysconfigtab copies. Sets the versw_transition attribute in the generic kernel subsubsystem of each member's /etc/sysconfigtab file to 0. Sends a clusterwide clu.versw EVM event to sig- nify that the version switch was successful. EXAMPLE
The following example shows how a script might use the versw -check command to enable new features on a cluster member that has completed a version switch: #!/usr/bin/ksh -p # Script example usage of versw command switch # if versw -check ; then echo "Enable new version features" else echo "Disable new version features" fi The following command shows the output of the versw -dump command on a cluster that has completed a roll: # versw -dump Old version = ( 0 , 0 ) Active version = ( 14000800009a1700 , 3b88 ) New version = ( 14000800009a1700 , 3b88 ) Version transition state = 0 Version switch state = 0 FILES
Specifies the command path. Configurable subsystem definition database file, as specified to the -mount option of the versw utility. By default, the /etc/sysconfigtab file is used. In a cluster, /etc/sysconfigtab is a context-dependent symbolic link (CDSL) that references the sysconfigtab file for a member. Rolling upgrade blocking conditions directory. SEE ALSO
Functions: versw(3), clu_is_member(3), clu_get_info(3) versw(8)
All times are GMT -4. The time now is 09:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy