In my 2 node cluster (sun cluster3.2) running on x86 VMs. One of my nodes VM1 does not have the global devices populated due to which i cannot failover my file system to node VM1 , what could be the reason for this and how can i rectify it ?
I need to change the boot slice on a Sun box, more specifically the alias of "disk". When I do a printenv from the ok prompt, it lists "boot-device disk net", but when it boots, it is looking at the wrong slice on "disk" (3 Replies)
I watched this done a long time ago, but cannot find it anywhere. I need to alias the boot device "disk" to /sbus@7,0/QLGC,isp@0,10000/sd@c,0
I think I need to set "use-nvramrc?" to true, and then create an alias within the nvramrc to point disk to the boot disk, but this is the step I cannot... (3 Replies)
Hello,
This is a 2 node sun cluster 3.2 on solaris 10(x86)
I am using an unique ~512M disk (c0d1) on each node and slice 6 on this disk for globaldevices. While everything looks like fine, the 'Fail' is bothering me.
@ tommy_sun1
@tommy_sun
-bash-3.00# cldevice refresh... (10 Replies)
Hi All ,
I would like to know the procedure for increasing shared volume space in sun cluster .
Currently the configuration is like these .
Main stripe
oradb1/d91 2 1 /dev/did/rdsk/d35s0 1 /dev/did/rdsk/d36s0 =Total 49 Gb
oradb1/d94 -p oradb1/d91 -o 88080480 -b 14680064 ==Total 7 GB... (4 Replies)
I'm trying to configure sun cluster 3.2 on vmware server 2.0 on windows xp host with solaris 10x86 guests VM3 and VM4 and i 'm running scinstall from VM4 .. it fails with following error
Initializing cluster name to "laptop" ... done
Initializing authentication options ... done
Initializing... (0 Replies)
I want to configure Sun Cluster3.2 with Oracle10g ... i created 4 resources namely , logical host, sotrage, oracle -server & Listener .. all work fine butoracle resource does not come up .. though i can bring up the oracle outside sun cluster.
node1:/>clrg online ora-rg
clrg: (C450598) On... (1 Reply)
Hi,
I have just installed RHEL 5.4 on a BL430c-class server and I am attempting to connect to the network only when I try and start eth0, I get the following error?
"Bringing up Interface eth0: hp device eth0 does not seem to be present, delaying initialization."
I am using a HP... (18 Replies)
Hi All
Please find my zone configuration after add emcpower0a device
zonecfg -z zone1 export
create -b
set zonepath=/zone/zone1
set autoboot=true
set ip-type=shared
add net
set address=192.168.1.11/24
set physical=nxge2
set defrouter=192.168.1.1
end
add device
set... (4 Replies)
Hi
I am new to this forum & oracle DBA also, I would like to know that can we add Oracle ASM in failover mode in sun cluster 3.3 or 4.0 means that if suppose oracle is running along with ASM on node1 & this node went down due to hardware issue then both oracle along with ASM must move to... (1 Reply)
Discussion started by: hb00
1 Replies
LEARN ABOUT DEBIAN
groupd
GROUPD(8) cluster GROUPD(8)NAME
groupd - compatibility daemon for fenced, dlm_controld and gfs_controld
SYNOPSIS
groupd [OPTIONS]
DESCRIPTION
The groupd daemon and libgroup library are used by the fenced, dlm_controld and gfs_controld daemons when they are operating in clus-
ter2-compatible mode to perform a rolling cluster upgrade from cluster2 to cluster3.
See cman(5) for more information on the upgrading configuration option needed to perform a rolling upgrade.
When the upgrading option is enabled, cman adds the following to the online configuration:
<group groupd_compat="1"/>
This setting causes the cman init script to start the groupd daemon, and causes the groupd, fenced, dlm_controld and gfs_controld daemons
to operate in the old cluster2 mode so they will be compatible with cluster2 nodes in the cluster that have not yet been upgraded.
The upgrading setting, including the groupd_compat setting, cannot be changed in a running cluster. The entire cluster must be taken off-
line to change these because the new cluster3 default modes are not compatible with the old cluster2 modes. The upgrading/compat settings
cause the new cluster3 daemons to run the old cluster2 code and protocols.
OPTIONS
Command line options override a corresponding setting in cluster.conf.
-D Enable debugging to stderr and don't fork.
-L Enable debugging to log file.
-g num groupd compatibility mode, 0 off, 1 on. Default 0.
-h Print a help message describing available options, then exit.
-V Print program version information, then exit.
SEE ALSO cman(5), fenced(8), dlm_controld(8), gfs_controld(8)cluster 2009-01-19 GROUPD(8)