Sponsored Content
Operating Systems HP-UX ServiceGuard cluster & volume group failover Post 302253471 by Wotan31 on Friday 31st of October 2008 04:51:15 PM
Old 10-31-2008
Ok, I just got a chance to test this. Here's what I had to do:

primary node: vgchange -a n vgname
secondary node: vgchange -a n vgname
primary node: vgchange -c y vgname
primary node: vgchange -a e vgname

And now it's failing over properly! yay!

thx again!
 

10 More Discussions You Might Find Interesting

1. HP-UX

HP Serviceguard failover - what doesn't get moved across?

Excuse the basic nature of the question, I've zero experience with regards to this and I'm just looking for a little clarity... When using serviceguard for a failover from one machine to another, what doesn't get taken from one machine to the other? For example, I was told that OS users and... (1 Reply)
Discussion started by: stefcha
1 Replies

2. High Performance Computing

sun Cluster resource group cant failover

I have rcently setup a 4 node cluster running sun cluster 3.2 and I have installed 4 zones on each node. when installing the zones I had to install the zone on all nodes the on the last node do a zlogin -C <zonename> this worked ok. theni I tried to siwitch the zone to node a thei work... (14 Replies)
Discussion started by: lesliek
14 Replies

3. HP-UX

Serviceguard Cluster Questions..

Hi, I'm fairly new to HP-UX. I am trying to find out if it is possible to create a cluster with 3 active nodes and 1 passive node. Everything I have found online so far just describes active/active and active/passive. Is it possible to have 3 active nodes and 1 passive node in a cluster? If... (2 Replies)
Discussion started by: DtbCollumb
2 Replies

4. AIX

backup & restore a volume group

Dear All, I would like to ask about saving & restoring a user defined volume group. i have a user defined volume group, named as datavg. i want to save it & to restore it into different size of physical volume. currently, datavg consist of 4 pv, three fisrt pv size are 100GB & one pv size is... (1 Reply)
Discussion started by: donybangetgitu
1 Replies

5. Solaris

Sun Cluster 3.1 failover

Hi, We have two sun SPARC server in Clustered (Sun Cluster 3.1). For some reason, System 1 failed over to System 2. Where can I find the logs which could tell me the reason for this failover? Thanks (5 Replies)
Discussion started by: Mack1982
5 Replies

6. Gentoo

How to failover the cluster ?

How to failover the cluster ? GNU/Linux By which command, My Linux version 2008 x86_64 x86_64 x86_64 GNU/Linux What are the prerequisites we need to take while failover ? if any Regards (3 Replies)
Discussion started by: sidharthmellam
3 Replies

7. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

8. UNIX for Dummies Questions & Answers

How to create a volume group, logical volume group and file system?

hi, I want to create a volume group of 200 GB and then create different file systems on that. please help me out. Its becomes confusing when the PP calculating PP. I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies

9. Linux

Volume is mounted on two ServiceGuard nodes

Hey! I'm running a HP ServiceGuard cluster with three nodes. One of the packages was moved (not by me) from one node to another a few weeks ago. I just noticed that one of the volume groups is still mounted on the old node. Oops! When I run df, less space is used on the old node than the new. ... (0 Replies)
Discussion started by: tobiasvl
0 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
cmgetconf(1m)															     cmgetconf(1m)

NAME
cmgetconf - Get cluster or package configuration information SYNOPSIS
cmgetconf [-v {0 | 1 | 2}] [[-K] -c cluster_name] [-p package_name] [output_filename] cmgetconf [-v {0 | 1 | 2}] [[-K] -c cluster_name] [-P dirname] cmgetconf [-v {0 | 1 | 2}] [-K] DESCRIPTION
cmgetconf obtains either the cluster configuration, not including the package configuration, and with or without the volume group informa- tion (-K option), or the specified package's configuration information (-p option), and writes to either the output_filename file, or to stdout. With the -P option, cmgetconf obtains the configuration information for all packages and writes to the directory specified by dirname. This command can be run whether the cluster is up or down. If -c , -p , or -P are not specified, cmgetconf will obtain the local cluster's configuration. Local cluster is the cluster containing the node where the cmgetconf command is issued. If both cluster_name and package_name are specified, the package must be configured in cluster_name, and only the package configuration for package_name will be written to output_filename or to stdout. The dirname parameter is required with the -P option. If cluster_name is specified with the -P option, the configuration of all the packages configured in the cluster_name will be written out to the directory specified by dirname. Each configured package configuration will be written out to the the specified dirname in a separate file named by appending the suffix .ascii to the name of the package. The -K option prevents probing of volume groups, reducing the time to get the cluster configuration file. NOTE: When this command is run by an authorized user who is not the superuser(UID=0), only those entries that match the user running the command and the node where the command is run are displayed. To view cluster or package information, a user must either be superuser(UID=0), or have an access policy of MONITOR allowed in the cluster configuration file, or have an access policy of PACKAGE_ADMIN allowed in one of the cluster package configuration files. See access policy in cmquerycl(1) or cmmakepkg(1). To modify the configuration of an existing cluster, the user needs to have the cluster's corresponding configuration file. To get the cur- rent cluster's configuration file, run cmgetconf first. Once created, the output_filename can be edited to add or delete nodes. The node configuration information should be retrieved from the cmquerycl command. Some cut and paste may be necessary. To modify the configuration of an existing package, the user needs to have the package's corresponding configuration file first. cmgetconf can be used to produce the package configuration file, then edit it to make the desired modifications, e.g. changing the list of nodes that can run the package, changing the subnet, etc. The modified configuration file can then be used in the cmapplyconf command to update either the cluster configuration or the package con- figuration. Options cmgetconf supports the following options: -v 0|1|2 Verbose output will be displayed. The -v option applies only when cmgetconf is used to obtain package configuration infor- mation. It is ignored if used to obtain cluster configuration information. 0 (data_only mode) The package configuration file will include only the configured attribute values. 1 (headline mode) The package configuration file will include the headline description and legal value for each con- figured and configurable attribute for the package. 2 (verbose mode) The package configuration file will include the full description and legal value for each configured and configurable attribute for the package. This is the default. -c cluster_name Name of the cluster for which to query cluster information. -K This option causes the probing of volume groups to be skipped, reducing the time for the command to complete. This option is not available for Linux. Note that if this option is used, cmgetconf will not add the list of cluster-aware volume groups to the resulting cluster configuration file. You must add the cluster-aware volume groups to the cluster configu- ration file before running cmapplyconf, or use the -K option of cmapplyconf when applying the generated configuration file. Failure to do so will result in all volume groups in the cluster being unusable in packages or for the cluster lock. -p package_name Name of an existing package for which to query package information. This option is mutually exclusive to the -P option. -P This option will write all package's configuration information to a specified output_filename. This option is mutually exclusive to the -p option. output_filename If -c and/or -p options are specified, the name of the file into which cmgetconf will copy cluster or package configura- tion information. If this parameter is not specified, the information will be directed to stdout. If the -P option is specified, the name of the directory into which cmgetconf will copy the configuration information for all packages. This parameter is required when -P option is specified. RETURN VALUE
Upon completion, cmgetconf returns one of the following values: 0 Successful completion. 1 Command failed. EXAMPLES
The high availability environment contains the cluster, clusterA , and packages pkg1 and pkg2. To generate the cluster configuration file for clusterA, and store the information in clusterA.conf, do the following: cmgetconf -c clusterA clusterA.conf To generate the cluster configuration file for clusterA, skipping disk probing, and store the information in clusterA.config, do the fol- lowing: cmgetconf -K -c clusterA clusterA.config To generate the package configuration file for pkg1, and store the information in pkg1.conf, do the following: cmgetconf -c clusterA -p pkg1 pkg1.conf To generate the package configuration files for all packages in the cluster, and store the information in the directory /tmp/pkgconfig, do the following: mkdir /tmp/pkgconfig cmgetconf -c clusterA -P /tmp/pkgconfig The directory /tmp/pkgconfig will contain two files, pkg1.ascii and pkg2.ascii. AUTHOR
cmgetconf was developed by HP. SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmdeleteconf(1m), cmquerycl(1m), cmmakepkg(1m). Requires Optional Serviceguard Software cmgetconf(1m)
All times are GMT -4. The time now is 04:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy