IP-ChangeOver.prog

[Amit]

------------------------------------

	Yes I do agree that a sniffer should not see packets around different
hubs connected to a switch. One of them that does not see traffic on
other hub is

http://sniffit.rug.ac.be/sniffit/sniffit.html

	Although this is my Fav. sniffer but the sniffer I pointed earlier is
able to see traffic on other hubs & is small aswell.

	Please try this sniffer on a your Pc and check if it works on your
switch's/hardware too. Linux binary can be found at:

http://members.xoom.com/samesun/sniffer.bin

------------------------------------

	We can provide both the options in IP-takeover.prog as configurable.

a) Nodes communication using heartbeat circuit.
b) Checking network for Master-IP with sniffer.

These are the advantages I see using sniffer:

· By using sniffer we do not generate traffic but tap the network. In
this we can check network packets to contain source or destination(or
both) to have Master-IP. If it exists that means something is going on
between clients and server. Hence we know the HA-server is working!

· Could use Heartbeat H/W for redundancy i.e. in case eth0 fails or
there is some problem with eth0 then system could use eth1 circuit.


	The problem with me is that I was unable to reach Master-IP from
heartbeat circuit using TCP/IP. (Am only interested in Master-IP and
not the to server nodes communicating) IP-takeover program will get
disk or IP only when it's sure that it's serving people else it should
release resources.(Of course before releasing it will generate traffic
to check if it can  reach clients or router)

------------------------------------

Amit Gupta.


_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com