• IntervalAfterFailedPing: Determines how often the Ping command will be sent
• PingDelayAfterPNAAction: Determines how long the RPC will wait to send
additional Ping commands, after a Ping-No-Answer Reboot has been initiated.
Typically, this option is used to allow time for a device to fully "wake up" after a
Ping-No-Answer Reboot before attempting to Ping the device again.
• ConsecutiveFailures: Determines how many consecutive failures of the Ping
command must be detected in order to initiate a Ping-No-Answer Reboot. For
example, if this value is set to "3", then after three consecutive Ping failures, a
• Reboot: Enables/Disables the Ping-No-Answer Reboot function for the specified IP
address. When this item is disabled, the RPC will not reboot the specified circuit(s)
when a Ping-No-Answer is detected. However, the RPC can continue to notify you
via Email, Syslog Message and/or SNMP Trap, providing that parameters for these
functions have been defined as described in Section 6.8 and email notification
for the Ping-No-Answer function has been enabled as described in Section 8.4.
• PNAAction: Determines how the RPC will react when the IP address fails to
respond to a ping. The RPC can either continuously reboot the specified circuit(s)
and send notification until the IP address responds and the Ping-No-Answer Reboot
is cleared (Continuous Alarm/Reboot), or the RPC can reboot the specified circuit(s)
and send notification only once each time the Ping-No-Answer Reboot is initially
• CircuitAccess: Determines which circuit(s) will be rebooted when the IP address
for this Ping-No-Answer operation does not respond to a Ping command. Note that
in the Text Interface, Circuit Access is defined via a separate submenu; in the Web
Browser Interface, Circuit Access is defined via a drop down menu, accessed by
clicking on the "plus" sign in the "Configure Circuit Access" field.
• CircuitGroupAccess: Determines which Circuit Group(s) the Ping-No-Answer
Reboot for this IP Address will be applied to. Note that in the Text Interface, Circuit
Group Access is defined via a separate submenu; in the Web Browser Interface,
Circuit Group Access is defined via a drop down menu, which may be accessed by