HA heartbeat y pacemaker -> Problem with floating ip

[sebd44]

Hello

i have a little and the same time huge doubt, because we mounted a HA
with two servers with elastix installed

i installed drbd y heartbeat

1.-here is the configuration from the drbd :

#
# please have a a look at the example configuration file in
# /usr/share/doc/drbd83/drbd.conf
#
global { usage-count no; }
resource repdata {
protocol C;
startup { wfc-timeout 10; degr-wfc-timeout 30; }
disk { on-io-error detach; }
net {
after-sb-0pri discard-younger-primary;
after-sb-1pri discard-secondary;
after-sb-2pri call-pri-lost-after-sb;
}
syncer { rate 10M; }
# set the above to 10M - single network card or 100M if using a
# dedicated (second) network card for DRBD
# make sure the name below matches your host name
on pbx-1 {
device /dev/drbd0;
disk /dev/hdb2;
# if using a second network card - make sure that this is the IP
# of the second card on Node 1 Server
address 130.0.20.221:7788;
meta-disk internal;
}
# make sure the name below matches your host name
on pbx-2 {
device /dev/drbd0;
disk /dev/hdb2;
address 130.0.20.222:7788;
# if using a second network card - make sure that this is the IP
# of the second card on Node 2 server
meta-disk internal;
}
}

###########################################################
in both nodes
###########################################################

this is the the files from the heartbeat service

::ha.cf

GNU nano 1.3.12 File: /etc/ha.d/ha.cf

debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility local0
keepalive 2
deadtime 30
warntime 10
initdead 120
udpport 694
bcast eth0
auto_failback on
node pbx-1
node pbx-2
crm yes


::haresources -> in just one line

pbx-2 drbddisk::repdata Filesystem::/dev/drbd0::/repdata::ext3 IPaddr::130.0.20.223/24/eth0:0/130.0.20.255 asterisk elastixportknock elastix-updaterd


And when i do the command

::crm_mon -> i get this result,


Refresh in 12s...

============
Last updated: Wed Aug 12 14:16:52 2015
Current DC: pbx-2 (ea16bc2c-40ea-4c65-9edc-f836f95d9791)
2 Nodes configured.
0 Resources configured.
============

Node: pbx-2 (ea16bc2c-40ea-4c65-9edc-f836f95d9791): online
Node: pbx-1 (c8bef1aa-eb12-4ed8-a4e6-ee7141e9ea2a): online




But here is when the problem occurs, because the floating ip doesn't show
neither of node 1 or two, in the config -> pbx-1 y pbx-2


So my doubt is:

heartbeat creates the virtual ip?
i have to create manually?
someone has donde this before, because the ha with heartbeat and drbd is old stuff, but i have not found
information about this problem...


Thanks for your time!
Best regards

[aks]

crm makes the virtual IP and is responsible for the gratutious arp.
Perhaps have a look at http://www.server-world.info/en/note?os ... emaker&f=2 (it may be a little out of date though).

[sebd44]

hey men thanks for the help, for the type of cluster with drbd and heartbeat that command doesn't work,
but i found the command for heartbeat

/etc/ha.d/resource.d/Ipaddr

bu i still have a problem, because when i reboot the primary, the secondary doesn't takes his place
or it can not take the floating ip for it self

[aks]

The last time I saw the symptoms you describe was because the attached network switches did not support gratuitous ARP. Is that the case?

[aks]

I guess it's time to capture the packets to see what's going on.