Using Ipmi To Conserve Server Resources - Coyote Point Systems E350GX Installation And Administration Manual

Chapter 6: Administering Virtual Clusters

Using IPMI to Conserve Server Resources

Smart Events with IPMI functions can be used for power management of server resources. For example, let's say we
have a cluster whose traffic can be handled during non-peak hours by two non-IPMI enabled servers -- these servers
are always powered on. During peak operating periods, one additional (IPMI-enabled) server is required to handle
increased traffic, and is always powered on with the
Using Smart Events, the additional server can be brought online during peak traffic periods and powered down when
the traffic is being handled by the two non-IPMI servers. Smart Rules will also provide a dynamic hot spare: should
one or both of the non-IPMI servers become unavailable, the IPMI-enabled server will be powered up -- and
powered down once the server that went down is available again.
If we assume a cluster with two non-IPMI servers (
of the events is shown in the table below:
Event peak-on-ipmi01:
If the number active connections to
both above some threshold:
• Power on and log a message.
ipmi01
• Set a wait timer on server
will affect the server for the duration of the timer.
At a minimum, set the timer to the time it takes
to boot and be available to handle traffic.
ipmi01
• Set the event timer on
enable it.
• Set a long event timer on this event (such as
864000, or 10 days), so that it does not continually
fire while the trigger conditions are true.
Event spare-on-ipmi01:
If the dynamic weights of either
below 1, then:
• Power on and log a message.
ipmi01
• Set a wait timer on server
will affect the server for the duration of the timer.
At a minimum, set the timer to the time it takes
to boot and be available to handle traffic.
ipmi01
• Set the event timer on
enable it.
• Set a long event timer on this event (such as
864000, or 10 days), so that it does not continually
fire while the trigger conditions are true.
For our example, note the following:
• We'll use 1000 connections as the number of connections on
reached a peak operating period.
• When they both go below 100 connections, the peak period has ended.
172
hot spare
sv01
and are
sv01 sv02
, so that no events
ipmi01
to 0 to
peak-off-ipmi01
or are
sv01 sv02
, so that no events
ipmi01
to 0 to
spare-off-ipmi01
server option enabled.
and ) and one IPMI-enabled server (
sv02
Event peak-off-ipmi01:
If the number active connections to
both below some threshold:
• Power off and log a message.
ipmi01
• Set a wait timer on server
will affect the server for the duration of the timer.
At a minimum, set the timer to the time it takes
to shut down completely.
ipmi01
• Set the event timer on
enable it.
• Set a long event timer on this event (such as
864000, or 10 days), so that it does not continually
fire while the trigger conditions are true.
Event spare-off-ipmi01:
If the dynamic weights of both
greater than 0 and there are no active connections to
, then:
ipmi01
• Power off and log a message.
ipmi01
• Set a wait timer on server
will affect the server for the duration of the timer.
At a minimum, set the timer to the time it takes
to shut down completely.
ipmi01
• Set the event timer on
enable it.
• Set a long event timer on this event (such as
864000, or 10 days), so that it does not continually
fire while the trigger conditions are true.
or
sv00 sv01
Equalizer Installation and Administration Guide
), the logic
ipmi01
and
sv01 sv02
, so that no events
ipmi01
to 0 to
peak-on-ipmi01
and are
sv01 sv02
, so that no events
ipmi01
to 0 to
spare-on-ipmi01
that tells us that they have
are