Re: Best way to simulate a failure
- From: Mike <n00spam@xxxxxxxxxxx>
- Date: Mon, 21 Jan 2008 08:13:19 -0800 (PST)
On Jan 13, 12:24 am, Cydrome Leader <prese...@xxxxxxxxxxxxxx> wrote:
Mike <n00s...@xxxxxxxxxxx> wrote:
I need to test a client's customized HA setup. I want to simulate the
failure of a single box running Solaris. As I understand it, a
poweroff issues a sync command which sends a FIN to all the network
connections. A real failure wouldn't be so accommodating. On the
other hand, I don't want to cause a real failure by pulling the power
cord too many times during a test.
Any suggestions? Does it matter what specific boxes I use? There are
several setups, each involving different hardware generations. A
general solution is preferred.
crashing/corrupting/unplugging the machine is most accurate.
You can pull network cables, but that never screws up the
machine you just removed. Even better, pull drives out. That will generate
some great errors and the machine will still be on the network.
A machine falling off the network doesn't really simulate a half broken
machine that's still limping along, possibly causing more problems. That's
a real test right there.
Sigh. I agree that the best way to test HA is to actually fail the
hardware. However, I am not allowed to really break the existing
boxes. Management wants a different solution and is pushing for
poweroff. However, as I said, poweroff does a sync which is, to my
mind, way too polite. I looking for the closest thing to pulling the
power cord that doesn't put the system at a real risk of not powering
--Thank you, Mike Jr.
- Prev by Date: Re: Best way to simulate a failure
- Next by Date: Re: 72g drives in Ultra 60
- Previous by thread: Re: Best way to simulate a failure
- Next by thread: Re: Best way to simulate a failure