Sponsored Content
Full Discussion: PowerHA6
Operating Systems AIX PowerHA6 Post 302752011 by MichaelFelt on Saturday 5th of January 2013 08:45:51 AM
Old 01-05-2013
You should be thinking in terms of boot IP address.

Since HACMP/PowerHA 5.X the correct term has been service/non-service IP addresses (when using IP aliasing, versus the HACMP 4.X and earlier standard of IP address "replacement".

The difference between a persistent address and a service address is that a persistent address is node bound while a service is not node bound - a service address is resource group bound.

Using/documenting a PowerHA cluster using the term "boot" only leads to confusion.

Yes, you can create etherchannels - but do not let an adapter become a SPOF (maybe I read wrong, but I am unsure if you have 2 NIC with 2 ports each per server, or 2 servers with 1 NIC and 2 ports each. If 2 NICS per server, 2x etherchannel is fine (great even!), otherwise - not advised -- Just make sure it is one port each from each NIC.

Hope this helps!
 
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 08:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy