HACMP resource group State not STABLE Post: 302491247

Sponsored Content

Operating Systems AIX HACMP resource group State not STABLE Post 302491247 by funksen on Thursday 27th of January 2011 04:34:05 AM

01-27-2011

Registered User

check the lun's reserve policy (lsattr -El hdiskx)

should be set to no_reserve, if not set it

Code:

chdev -l hdiskx -a reserve_policy=no_reserve

it's always a good idea to try out manually what the cluster is doing
normally there is no need to set the vg online, since it should be concurrent passive online, as soon as the cluster starts

when the resource group moves, the vg will be set to concurrent active on one node, and concurrent passive on the other node

ist the vg concurrent capable? (lsvg vgname)

Code:

VOLUME GROUP: xxxvg                 VG IDENTIFIER:  xxxxxx
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      67478 (8637184 megabytes)
MAX LVs:            256                      FREE PPs:       1078 (137984 megabytes)
LVs:                31                       USED PPs:       66400 (8499200 megabytes)
OPEN LVs:           31                       QUORUM:         1 (Disabled)
TOTAL PVs:          34                       VG DESCRIPTORS: 34
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         34                       AUTO ON:        no
Concurrent:         Enhanced-Capable         Auto-Concurrent: Disabled
VG Mode:            Concurrent                               
Node ID:            1                        Active Nodes:       2 
MAX PPs per VG:     131072                   MAX PVs:        1024                                                                                                                                                                            
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no                                                                                                                                                                              
HOT SPARE:          no                       BB POLICY:      relocatable

should look like this
vg state may be active or passive

funksen

View Public Profile for funksen

Find all posts by funksen

8 More Discussions You Might Find Interesting

1. 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...

2. Solaris

Solaris + VCS , move a resource to another group

Hi, I am running Solaris 10 + VCS 5 in one of our environment. Recently one of my colleague configured all resources in a single service group.( ie, one service group which has all resources) ,Usually we create seperate service groups for Hardware & for application. For eg: SYS_HW_GRP, will...

3. AIX

Resource Group Monitoring

Hi, I have a requirement to monitor the HACMP Resource Groups. At present in my environment, if the Resource Groups fail over from preferred node to Secondary node we dont get notification. Can some one help me in creating a scrript. I have more than one RG online. (Max 4 Resource Groups in...

4. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes...

5. AIX

HACMP, NFS cross-mount problem. Can not move resource group

Hi, I'm new to HACMP. Currently I setup a cluster with nfs cross-mount follow this guide: kristijan.org NFS cross-mounts in PowerHA/HACMPMy cluster has two nodes: erp01 and erp02. I'm using nfs4 with filesystem for nfs is: /sapnfs Cluster start without problems. But I cannnot move RG (with...

6. AIX

Adding existing VG to powerHA Resource group

Hello. I am Running AIX 6.1 and PowerHA 6.1 I have an active/active cluster (Prod/Dev) cluster. Each side will failover to the other. I have on my prod side an active volume group with a file system. The VG is imported on both nodes and active (varried on, file system mounted) on the prod...

7. AIX

Power HA 6.1 Bring Resource group online issue

Hi all, I have the following in hacmp.out for bringing Resource group online. Volume groups themselves are Enhanced-Capable and on each node I can varyon and mount filesystems. +main1_rg_01:cl_activate_vgs STATUS=0 +main1_rg_01:cl_activate_vgs typeset -li STATUS +main1_rg_01:cl_activate_vgs...

8. AIX

Sysmirror 7.1.3 Resource Group NFS mounts

Hello all, I'm working to fix a two-node SysMirror cluster that uses NFS mounts from a NetApp appliance as the data repository. Currently all the NFS mounts/unmounts are called from the application controller scripts, and since file collection isn't currently working, (One fight at at time...

LEARN ABOUT OSX

vgimportclone

VGIMPORTCLONE(8)					      System Manager's Manual						  VGIMPORTCLONE(8)

NAME

       vgimportclone - import and rename duplicated volume group (e.g. a hardware snapshot)

SYNOPSIS

       vgimportclone [-n|--basevgname VolumeGroupName] [-i|--import] PhysicalVolume [PhysicalVolume...]

DESCRIPTION

       vgimportclone is used to import a duplicated VG (e.g. hardware snapshot).  Duplicate VG(s) and PV(s) are not able to be used until they are
       made to coexist with the origin VG(s) and PV(s).  vgimportclone renames the VG associated with the specified PV(s) and changes the  associ-
       ated VG and PV UUIDs.

OPTIONS

       See lvm for common options.

       -n|--basevgname VolumeGroupName
	      By  default  the	snapshot  VG  will be renamed to the original name plus a numeric suffix to avoid duplicate naming (e.g. 'test_vg'
	      would be renamed to 'test_vg1').	This option will override the base VG name that is used for all  VG  renames.	If  a  VG  already
	      exists with the specified name a numeric suffix will be added (like the previous example) to make it unique.

       -i|--import
	      Import exported Volume Groups.  Otherwise VGs that have been exported will not be changed (nor will their associated PVs).

ENVIRONMENT VARIABLES

       LVM_BINARY
	      The LVM2 binary to use.  Defaults to "lvm".

EXAMPLES

       The  origin VG vg00 has origin PVs /dev/sda and /dev/sdb and the respective snapshot PVs are /dev/sdc and /dev/sdd.  To rename the VG asso-
       ciated with /dev/sdc and /dev/sdd from vg00 to vg00_snap (and to change associated VG and PV UUIDs) do:

	    vgimportclone --basevgname vg00_snap /dev/sdc /dev/sdd

SEE ALSO

       lvm(8)

Red Hat, Inc.						 LVM TOOLS 2.02.95(2) (2012-03-06)					  VGIMPORTCLONE(8)