Tripp Lite SV20KM1P1B Users Guide for PowerAlert Network Shutdown Agent PANSA - Page 4

2. Windows Implementation After entering the IP addresses and community names to search, click "OK" to initiate the network autodiscovery process. Autodiscovery will detect SNMP-enabled Tripp Lite devices on the local network that PANSA is able to monitor. The results window (Figure 2.3.3) will list compatible devices detected by the autodiscovery process. If no devices are detected, confirm the devices have been configured with the firewall and other settings listed earlier. Note: Discovery errors will be logged in the C:\Program Files (x86)\TrippLite\PowerAlert\log directory in the PANMSdiscoveryerror.log file. This file can be viewed using a standard text editor such as Notepad. Figure 2.3.3 Select either one or two systems to be monitored by PANSA, then click "OK" to return to the main console window. The device or devices selected will be displayed in the "Monitored UPS" fields. Each device's IP address, community name, model, location and status will be shown. The Status field shows whether the monitored device is currently accessible. If the monitored device is offline, PANSA will attempt to reconnect to the monitored device continuously for 15 minutes, then once every 15 minutes. You can add devices by running the autodiscovery process again. Devices can also be deleted from the console, resulting in PANSA de-registering itself from the device. 2.3.1 Event Settings After selecting one or two systems to monitor, you should define which monitored event(s) will prompt PANSA to either shut down your computer or execute a command. The list of events is dynamic, and includes items such as "Battery Low," "On Battery" and "Temperature High," as well as events that may be specific to the monitored device; supported events vary from device to device. For a complete list of events supported by a specific device, launch the PowerAlert Console for that device and examine the Events module. Highlight one or more events in the list, then choose to enable shutdown and/or command execution when the selected event(s) is (are) detected. Events that are not selected will be ignored. Use the delay dials to set the amount of time PANSA will wait for the event to clear before shutting down the computer or executing a command. 2.3.2 Shutdown When PANSA is triggered to act, it will perform either a shutdown or hibernation based upon the selected Shutdown Type. "Hibernate" will be an available choice only if the hibernation feature is supported by your computer's operating system. If it is supported, "Hibernate" will be the default setting. 2.3.3 Command Execution PANSA manages and monitors the selected system(s) and can execute a command upon receiving a critical event, such as a power outage. It can also execute a command when the event clears, such as returning to utility power. The command can be used to launch an executable or to execute a batch file. Typically, the command execution is used to spawn a batch file that instructs other external systems to shut down, such as VMware servers. Refer to Section 4 for more information on executing commands and scripts for VMware. Warning! Any user with access to PANSA can change which script will be executed. It is not recommended to use the Command Execution feature to run an executable file that interacts with the desktop. Windows Session 0 Isolation will prevent the Graphical User Interface (GUI) or popup called in the script from appearing on the Windows desktop and may lead to the script not executing in the same manner as when it is manually called. Examples of executables that interact with the desktop are: notepad.exe and putty.exe. 4