Forum
Welcome, Guest
Username: Password: Remember me
This is the optional category header for the Suggestion Box.
  • Page:
  • 1

TOPIC:

Restart only on reboot. 8 years 9 months ago #472

  • VolaTiming
  • VolaTiming's Avatar Topic Author
  • Offline
  • Posts: 1
Hello,

I'm new to XenServer and i'm trying HA-Lizard without SAN on two nodes, wich, from my point of view can be a better solution for HA for virtual appliance than any other solution for small business.

But, in my test lab, i tried a configuration with two same server with only one physical NIC for each. So no bounded network...

So for installation and configuration everything works very well.
I install a Win10 x64 OS as virtual client to play with it.

To simulate a crash i first type reboot in the master console.
Server reboot and in less than 5 seconds the W10 was already restarted on the slave :) Amazing !!!

But now, i unplug the network cable from master server, and here start the problem...

The slave doesn't start the VM :
if i try ha-cfg status on the slave, nothing happens, it hangs here.
if i try ha-cfg log, nothing happens, it hangs here.
After 1 minutes the salve reboot !!!

Maybe the system MUST have the bonded dedicated link, but in the documentation i understand that it is a best recommandation not a need.

So, can it be work with only one NIC ? or do i miss something else in my configuration ?

At least, let say if a first node crash, the second one restart VMs...
But after restoring the first node, does HA-Lizard return at the first state (VMs originally started on first node are stopped on the second and restarted on the first ?)

Thanks a lot for sharing this project !!!

Please Log in or Create an account to join the conversation.

Restart only on reboot. 8 years 9 months ago #473

  • Salvatore Costantino
  • Salvatore Costantino's Avatar
  • Offline
  • Posts: 722
For test purposes, one link should suffice.
Your slave is rebooting itself in your test because it has self fenced. This occurs when the slave cannot reach the master's management interface AND the slave cannot reach the hearistic IP adddress. In this case the slave will reboot one time and enter a suspended HA state where it is prohibited from starting any VMs (see documenetation for more on this suibject)

Chances are that you have configured a hearisistc IP address that the slave cannot reach which will prevent it from recovering any failed services.

You should also perform an "ha-cfg status" on the slave. It will notify you if the slave is in a suspended HA state and instruct on how to fix it.

Please Log in or Create an account to join the conversation.

  • Page:
  • 1