Coyote Point Systems E350GX, Руководство по установке и администрированию

Страница: 173 / 344

Configuring Smart Events
Equalizer Installation and Administration Guide 173
• We’ll assume that
ipmi-server
can start serving traffic 180 seconds after it is powered on, and that it takes
the same number of seconds to shut down completely, and use 180 seconds for the wait timer on
ipmi01
in
the event actions. These times could be adjusted (i.e., increased) in a production environment to prevent
ipmi-server
from bouncing up and down during high traffic spikes. Low server wait times relative to the
wait set on the event timers (see the next bullet) should be used, however, since in this example the server
wait timer is not explicitly set to 0 by any event action.
• Each event will also set an event timer on itself so that it does not re-fire until its associated event has fired,
and will clear the event timer on its associated event (see the last two bullet items in each event description,
above).
To create the peak* and spare* events shown in the table above, do the following:
1. Right-click on the cluster name, and select
Add Event
from the popup menu:
a. Type
peak-on-ipmi01
into the
Event Name
text box and click the next icon (
>
).
b. Construct the
Event Trigger
shown below using the expression editor controls:
Click the next icon (
>
).
c. Construct the
Event Action
shown below using the expression editor controls:
Click the next icon (
>
).
d. Click
commit
to create the
peak-on-ipmi01
event. The object tree at left refreshes to display the new event.
e. Click on the new event name and open the
Action
tab in the right frame. Use the expression editor to add
an event wait timer for this event, as shown below:
f. Click
commit
.
2. Right-click on the cluster name, and select
Add Event
from the popup menu:
a. Type
peak-off-ipmi01
into the
Event Name
text box and click the next icon (
>
).
b. Construct the
Event Trigger
shown below using the expression editor controls: