You can do it one of two ways.
1. Have ipMonitor reboot the system if its temperature has exceeded a certain threshold for more than a certain number of tests/failures. In order to accomplish this, simply open the Alert which is already associated with the Monitor and add a Reboot Server Action. Set the Alert Range as needed. For instance, if you want it to reboot the server after 15 minutes of exceeded temperatures and the Monitor is set with the default timing values of 300 all around and "Accumulated Failures per Alert" of 3, you would set the Alert Range at 1. You can use the DownTime Simulator feature to see when the Action gets Triggered.
2. Have ipMonitor reboot the system immediately if an extreme temperature has been reached. For this, you would need a second Temperature Monitor with a higher threshold and a second Alert with the Reboot Server Action. The difference is the 2nd Monitor woul be set with an "Accumuated Failures per Alert" of 1.
In the second scenario, if the first Temperature Monitor fails, it will send you an email. If the second Temperature Monitors fails, it reboots the server.
NOTE: In order for the Reboot Server Action to work, the Monitor's "Recovery Parameters" section must be populated with the Name/IP address of the system to reboot and Credential to use in order to reboot the system.
If you need clarification on any of this, get back to me.
Chris Foley - SolarWinds - Support Specialist
Support: 866.530.8040 | Fax: 512.857.0125
network management simplified | solarwinds.com
Appreciate the quick follow up, I actually need to shutdown the servers, if the temp in our server room reaches a critical point, we want them off so that we don't have disk, proc failes, etc. Any recommendations?
We are monitoring a remote site using Virtual IP and Port mapping. For exampe, to monitor server 10.1.1.10, we are monitoring it through an public IP and port through 220.127.116.11:1161. How can we set recovery action in such a scenario, as we do not have the real IP of the target server?