I'm setting up several "example" Clusters whith vmware.
The problem I have is that I don,t have a generic fencing tool.
If I give a demo to management ;-), my "very important" xclock service does
not recover after a killed server.
(I need to take manual actions :-(
What I need would be fencing command that does following:
- send an alert. (ex "mail -s Cluster operating@xxxxxxxxxxx")
- Wait for defined time ("sleep 15")
- Do some confirmation check.
- Execute a "Kill server" script, that doesn't stop
- Continue cluster and start de service on a working node.
If you have something like that or a part of it.....
If I'm doing something wrong, please correct me
(Or even correct way to disable fencing.)
Frank Weyns
Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op
te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid
voor schade die voortvloeit uit de inhoud en/of de verzending van dit bericht
This e-mail and any attachments are confidential and is solely intended for the
addressee only. If you are not the intended recipient, please notify the sender
and delete and/or destroy this message and any attachments immediately. It is
prohibited to copy, to distribute, to disclose or to use this e-mail and any
attachments in any other way. Ordina N.V. and/or its group companies do not
accept any responsibility nor liability for any damage resulting from (the
content of) the transmission of this message.
Thread at a glance:
Previous Message by Date:
click to view message preview
Re: failover domain ip address hidden?
Greg,
I had the very same doubt as you had.
After digging into the manual, I could find a paragraph that instructed
me to issue the following command to check the virtual IP addresses in
the kernel:
ip addr list
Looking at the "ip" man page, I found that there is possible to make a
"label" appear when you type "ifconfig", but for some reason the
virtual IP scripts don't make use of this.
For the developers: how about adding a text field where the user could
type a short descriptive label for using together with the "ip addr add
x.x.x.x dev INTERFACE label LABEL"? This way the label would appear
when the user typed "ifconfig", right?
Best regards,
Celso.
Greg Forte escreveu:
Can
anyone explain to me how failover ip addresses are bound to interfaces
in the kernel, or why they don't seem to show up in 'ifconfig' output?
I've got one configured and it worked like a charm first try (unlike my
fencing setup, heh), I'm just confused as to why it doesn't appear in
ifconfig.
-g
Greg Forte
gforte@xxxxxxxx
IT - User Services
University of Delaware
302-831-1982
Newark, DE
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Celso Kopp
Webber
celso@xxxxxxxxxxxxxxxx
Webbertek - Opensource Knowledge
(41)
8813-1919
(41) 3284-3035
Next Message by Date:
click to view message preview
GFS6.1 and CS4.0 fencinfg RSA II
Hi.
CS 3 and GFS 6.0 fencing ibm servers with RSA II adapter
was done with fence_xcat, in CS 4.0 and GFS 6.1 there is no fence_xcat command.
Is there some other mechanism to fence nodes which have RSA II adapters.
Thanks for advance.
...................................................................
Luukku Plus paketilla pääset eroon tila- ja turvallisuusongelmista.
Hanki Luukku Plus ja helpotat elämääsi. http://www.mtv3.fi/luukku
Previous Message by Thread:
click to view message preview
Basic question on CLVMD / GFS
Hi,
I am confused about the usage of clvmd. On a blank 80 GB disk I created
a logical volume using the following commands (after the cluster was
started with "ccsd; cman_tool join; fence_tool join" on all nodes):
# overwrite a former partition table:
dd if=/dev/zero of=/dev/hdb bs=512 count=1
# initialize the physical volume:
pvcreate /dev/hdb
# create a volume group "vg301":
vgcreate vg301 /dev/hdb
# create a 40 GB logical volume "lvol0" inside vg301:
lvcreate -L 40G vg301
# start clvmd
clvmd
# mark the volume group as "clustered" (there are no other vg's):
vgchange -cy
# activate the volume group with/without cluster locking
vgchange -aey ...or... vgchange -aly
vgchange prints a notice if on some other node of the cluster clvmd is
not running and activates the logical volume.
Is this enough to use "vg301" or "vg301/lvol0" on the other nodes? If
yes, how do I access vg301 from another (than the local) node? vgscan,
executed on the other nodes, does not report anything.
Distributing the local vg301/lvol0 (with GFS on it) with GNBD 'nearly'
worked: At some point, the I/O was blocked on nodes accessing a specific
directory.
gfs_mkfs -p lock_dlm -t Isabella:lvol0_301 -j 4 /dev/vg301/lvol0
gnbd_export -v -e exp301_0 -d /dev/vg301/lvol0
Is there any information / documentation about clvmd? The lvm-HOWTO does
not cover this topic :-(
Many thanks!
--
Michael Weitzel
Next Message by Thread:
click to view message preview
Cluster Suite v3 software watchdog
Hello,
I'm having some difficulties with the software watchdog feature when
configuring a Red Hat Cluster Suite v3 with Dell hardware.
Notably I had problems with Dell PowerEdges 2650 and 2850. After
setting up the cluster nodes and selecting the "enable software
watchdog" check box under every member of the "Members" tab, I can run
the cluster with no problems, but the machines reboot from time to time.
I've tried passing the following parameters to the kernel by editing
grub.conf:
nmi_watchdog=1
Does anyone has had this issue before? Or am I missing any step on
configuring the software watchdog feature?
Another question for the Red Hat people on the list: does this
"software watchdog" works ok? I ask because it's enabled by default
when you add a new member to the cluster. The Cluster Suite v3 manual
tells nothing about this resource either.
I could only find some information about soft watchdog in the Cluster
Suite v2.1 manual, but that version seems to be somewhat different from
v3 and v4.
Thanks in advance.
Regards,
Celso.
--
Celso Kopp
Webber