Chapter 3: Using the Web Interface
156
A Note about Infinite Loop
You should avoid building an infinite loop when creating event rules.
The infinite loop refers to a condition where the PDU keeps busy because the action or one of the actions taken for a
certain event triggers an identical or similar event which will result in an action triggering one more event.
Example 1
This example illustrates an event rule which continuously causes the PDU to send out email messages.
Event selected
Action included
Device > Sending SMTP message failed
Send email
Example 2
This example illustrates an event rule which continuously causes the PDU to send out SMTP messages when one of the
selected events listed on the Device menu occurs. Note that <Any sub-event> under the Device menu includes the event
"Sending SMTP message failed."
Event selected
Action included
Device > Any sub-event
Send email
Example 3
This example illustrates a situation where two event rules combined regarding the outlet state changes causes the PDU to
continuously power cycle outlets 1 and 2 in turn.
Event selected
Action included
Outlet > Outlet 1 > Sensor > Outlet State > On/Off > Both
(trigger condition)
Cycle Outlet 2
(Switch outlets --> Cycle Outlet --> Outlet 2)
Outlet > Outlet 2 > Sensor > Outlet State > On/Off > Both
(trigger condition)
Cycle Outlet 1
(Switch outlets --> Cycle Outlet --> Outlet 1)
A Note about Untriggered Rules
In some cases, a measurement exceeds a threshold causing the PDU to generate an alert. The measurement then returns
to a value within the threshold, but the PDU does not generate an alert message for the Deassertion event. Such scenarios
can occur due to the The PDU tracking the PDU uses. For more information, refer to
"To De-assert" and Deassertion The
PDU
in the PDU With RackLink Advanced User Manual at
