lsvg xxx02vg
VOLUME GROUP: xxx02vg VG IDENTIFIER: 00c58aa200004c0000000124fdaf434a
VG STATE: active PP SIZE: 32 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1278 (40896 megabytes)
MAX LVs: 256 FREE PPs: 444 (14208 megabytes)
LVs: 8 USED PPs: 834 (26688 megabytes)
OPEN LVs: 8 QUORUM: 1 (Disabled)
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: no
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
Moderator's Comments:
Please use [code] and [/code] tags when posting code, data or logs etc. to preserve formatting and enhance readability, thanks.
Last edited by zaxxon; 01-31-2011 at 08:16 AM..
Reason: code tags
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)
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... (0 Replies)
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... (2 Replies)
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... (6 Replies)
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... (3 Replies)
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... (3 Replies)
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... (2 Replies)
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... (3 Replies)
Discussion started by: ZekesGarage
3 Replies
LEARN ABOUT CENTOS
ocf_pacemaker_dummy
OCF_PACEMAKER_DUMMY(7) Pacemaker Configuration OCF_PACEMAKER_DUMMY(7)NAME
ocf_pacemaker_Dummy - Example stateless resource agent
SYNOPSIS
OCF_RESKEY_state=string [OCF_RESKEY_fake=string] OCF_RESKEY_op_sleep=string Dummy [start | stop | monitor | reload | migrate_to |
migrate_from | validate-all | meta-data]
DESCRIPTION
This is a Dummy Resource Agent. It does absolutely nothing except keep track of whether its running or not. Its purpose in life is for
testing and to serve as a template for RA writers. NB: Please pay attention to the timeouts specified in the actions section below. They
should be meaningful for the kind of resource the agent manages. They should be the minimum advised timeouts, but they shouldn't/cannot
cover _all_ possible resource instances. So, try to be neither overly generous nor too stingy, but moderate. The minimum timeouts should
never be below 10 seconds.
SUPPORTED PARAMETERS
OCF_RESKEY_state = string [/Dummy-{OCF_RESOURCE_INSTANCE}.state]
State file
Location to store the resource state in.
OCF_RESKEY_fake = string [dummy]
Fake attribute that can be changed to cause a reload
Fake attribute that can be changed to cause a reload
OCF_RESKEY_op_sleep = string [0]
Operation sleep duration in seconds.
Number of seconds to sleep during operations. This can be used to test how the cluster reacts to operation timeouts.
AUTHOR
Andrew Beekhof <andrew@beekhof.net>
Author.
Pacemaker Configuration 06/10/2014 OCF_PACEMAKER_DUMMY(7)
01-31-2011
