Sponsored Content
Operating Systems AIX PowerHA, same subnet for persistent and service ip Post 302586332 by zxmaus on Sunday 1st of January 2012 12:30:22 AM
Old 01-01-2012
I assume the only thing is that you cannot guarantee that the traffic that is meant to come in via the service IP really comes through the 'service' adapter and vice versa - it will rather be random. Anything else should work just fine.

Regards
zxmaus
 

10 More Discussions You Might Find Interesting

1. IP Networking

Migrating existing Subnet to a new subnet and changing ip addresses in UNIX

Hi, My project needs to migrate the existing Subnet (255.255.255.0) to a new subnet and change the ipaddresses (currently C class). How can I do that. I need some information. John (0 Replies)
Discussion started by: johnmarsh
0 Replies

2. AIX

strange route issue in powerha 5.4?

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

3. AIX

PowerHA - assistant can't find network

I've configured multiple clusters using PowerHA 5.5, but never using the 'Two-node cluster configuration assistant'. I removed all the clusters, clean setup, and gave the assistant a try. I've filled in all the necessary options: Communication Path to Takeover Node Application Server ... (11 Replies)
Discussion started by: Koen87
11 Replies

4. AIX

PowerHA Disk on VIO Server

Hello AIX GURU's Can anybody tell me the steps to crate shared VG (enhanced concurent) for my Lpars from VIO server? my questions are: 1. Should I crate Enhanced Concurent VG in VIO and map it using virtual Scsi to Lpar? or 2. Can I just create virtual SCSI in VIO and map to Lpar and... (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies

5. AIX

PowerHA HACMP on VIOS servers

Few questions regarding Power HA ( previously known as HACMP) and VIOS POWERVM IVM ( IBM Virtualization I/O Server ) Is it possible to create HACMP cluster between two VIOS servers Physical Machine_1 VIOS_SERVER_1 LPAR_1 SHARED_DISK_XX VIOS_SERVER_2 Physical Machine_2 LPAR_2... (6 Replies)
Discussion started by: filosophizer
6 Replies

6. AIX

Powerha on AIX 6.1.9

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

VXVM in POWERHA 6.1

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

PowerHA; Import flash copy of VG?

Hey guys, wondering if this is possible to accomplish. PowerHA SystemMirror7.1 active/passive cluster. Restored a clustered system in test and upgraded to the latest version of PowerHA. Things are working great. However in the interest of time during cut over to the new system, I was hoping to... (4 Replies)
Discussion started by: j_aix
4 Replies

9. AIX

PowerHa 7.1 Migration check failed

Hello Guys, I was trying to upgrade the PowerHA from 6.1.0.9 to 7.1.3 in prod cluster. Have snapshot migration and run climgcheck. 1. Run climgcheck on node1(kul1pqcmur01) and it success 2. Upgrade the cluster sw 3. Run climgcheck on node2(kul1pqcmur02) and it failed with below errors ... (6 Replies)
Discussion started by: novaothers
6 Replies

10. AIX

Upgrading PowerHA from 7.1.0 to 7.1.3

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
clusvcadm(8)						       Red Hat Cluster Suite						      clusvcadm(8)

NAME
clusvcadm - Cluster User Service Administration Utility SYNOPSIS
clusvcadm [-d <service> ] [-e <service> ] [-l] [-u] [-S] [-m <member> ] [-r <service> ] [-R <service> ] [-M <service> ] [-Z <service> ] [-U <service> ] [-s <service> ] [-v] DESCRIPTION
The clusvcadm command allows an administrator to enable, disable, relocate, and restart user services in a cluster. In order to perform cluster service operations, the cluster daemons must be running (and have quorum) on the member system on which the command is invoked. OPTIONS
-d <service> Stops and disables the user service named service -e <service> Enables and starts the user service named service -l Lock services in preparation for cluster shutdown. This should only be used if the administrator intends to perform a global, clus- ter wide shutdown. This prevents services from starting (but not stopping, like -Z does). Once the cluster quorum is dissolved, this state is reset. If a new instance of rgmanager boots while others are locked, the behavior is undefined. -u Unlock resource group managers. This allows services to start again. -S Display whether the resource group managers are locked or not. This can be used to verify the correct operation of the -l and -u options, but is only useful for debugging. -m <member> When used in conjunction with either the -e or -r options, this specifies the preferred target member on which to start the service. -r <service> Relocates the user service named service to another cluster member. -R <service> Restarts the user service named service on the cluster member on which it is currently running. -M <service> Use a special "migration" operation to move the user service named service to another cluster member. Currently, this is only use- ful for virtual machines. Use of migration usually requires special configuration of the local virtual machine manager in order to work correctly. -Z <service> Freezes the service named service on the cluster member on which it is currently running. This will prevent status checks of the service as well as failover in the event the node fails or rgmanager is stopped. -U <service> Unfreezes the user service named service on the cluster member on which it is currently running. This will re-enable status checks. -s <service> Stops the service named service until a member transition or until it is enabled again. -v Display version information and exit. NOTES
Executing -U (unfreeze) on a service which was frozen in the started state while the service owner is offline results in an undefined (and possibly dangerous) condition. Manually ensure all resources are clear before doing this. SEE ALSO
clustat(8) Jan 2005 clusvcadm(8)
All times are GMT -4. The time now is 05:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy