750096T-PowerAlert Software CD These Release Notes are for Tripp Lites PowerAlert 12 These notes are prepared by the members of Tripp Lites Software Development Team. Thank you for using Tripp Lites PowerAlert 12 software package. This Readme file contains important information regarding this release. We strongly recommend that you read the entire document. ************************* WHAT'S IN THIS FILE -Supported Operating Systems -System Requirments -Know Issues -PowerAlert Version History -Contacting Tripp Lites Technical Support -Operating install directions (Sun Solaris,AIX and SCO) *************************** SUPPORTED OPERATING SYSTEMS *************************** PowerAlert 12.04.0030 Note: PowerAlert is a 32bit application that will run on the noted 64bit Operating Systems. All 64bit supported operating systems have been tested on AMD64 and Intel EM64T platforms only. WINDOWS- Windows 2000 Professional Windows 2000 Server Windows XP Home Edition Windows XP Professional (32 & 64 bit) PowerAlert 12.04.0019 Note: PowerAlert is a 32bit application that will run on the noted 64bit Operating Systems. All 64bit supported operating systems have been tested on AMD64 and Intel EM64T platforms only. WINDOWS- Windows 2000 Professional Windows 2000 Server Windows XP Home Edition Windows XP Professional (32 & 64 bit) Windows 2003 (32 & 64 bit) Linux- RedHat 4 enterprise (32 & 64 bit) Fedora Core 3(32 & 64 bit) Fedora Core 4 (32 & 64 bit) Ubuntu 5.1 (Breezy Badger) (32 & 64 bit) SUSE 9.3 (32 & 64 bit) SUSE 10.0 (32 & 64 bit) Unix- AIX 5.1,5.2 and 5.3 SCO 6.0 Sun Solaris (Intel) 10 Sun Solaris (Sparc) 8,9,and 10 ************************** SYSTEM REQUIRMENTS ************************** -Internet Explorer 4.0 and above, Netscape 4.2 and above and FireFox 1.0.07 and above. -TCP/IP Protocol support -J2SE 1.4.1 or above. -20 megabytes (MB) of hard disk space. -64 MB of RAM. -100 megahertz processor or higher -CD-ROM drive. ************************* Known ISSUES ************************* PowerAlert 12.04.0030 - On Microsoft Vista using the following configuration generates a PA.exe error upon an event shutdown USB connection to SMART2200RMXL2U or SMX2200RMXL2U (protocol 3012) and running PowerAlert in Business scheme - On Microsoft Vista installation of PowerAlert must be performed once for each user that will be using the PC -PowerAlert installation on Microsoft Vista does not support silent installation -SMARTONLINE outlet control commands are not working when connected via USB -Autorestart options are not changeable on SMART2200RMXL2U or SMX2200RMXL2U (protocol 3012) -Cycle command from the Actions-Control menu always shows a max value of 8 instead of the actual number of controllable outlets ************************** PowerAlert version History (Notes for latest release at bottom of section) ************************** PowerAlert 12.01.0030 -One unique install for all OS Platforms. -One common interface for all OS Platforms. -Multi-Device support- PowerAlert 12 has the ability to manage muliple devices at a time. -New User Interface Tripp Lites PowerAlert 12 new interface is now simpler than ever to use. -Java applet that intigrates into Microsoft IIS. -Java based application and applet. -SNMP v.1 based communications. -WatchDog- a unique Hardware/Software solution that enables the cycling upon a loss of communication. PowerAlert 12.01.0030b -Modified install set that changes the way serial ports are detected PowerAlert 12.01.0030c -Modified install set to correct serial port detection to meet Microsoft’s standard PowerAlert 12.01.0030d -Modified the installation set to correct a problem with the PowerAlert Applet not working on Windows 2003 systems. PowerAlert 12.01.0031(750096TrevE) -Add support for contact closure UPSes -Add ability to manually add a UPS -Add support for HID UPS systems -Add support for 3004 protocol UPS systems Build-12.01.0006 ( 750096revF) -Changed logging from an ODBC connection to a binary file named palog.dat -Control commands executed are now logged into the event log file -Changed the help file look from an XP look and feel to standard HTML to allow for compatibility on Linux -Support for Linux RedHat 9 added -Fixed a bug when when two UPSes and then the first one becomes inactive when I stop and restart the Engine and then launch the console and go to Control-Load the page is greyed out -Added support for 1002 protocol. UPS systems. BC4918, BC4919, BC4920, BC4921, BC4922 -Fixed bug that required a console to be restarted before displaying changes to the device name and location were displayed on the status panel. -Added support for silent installation. “setup.exe –silent” -Added support for custom installation. Place the (padvcext.dat) and user files (pausrext.dat) in the same directory as the setup file and then run the installation in silent mode which then copies the files to the engine directory as templates. The files are renamed whereby "ext" is replaced with "tpl". -Changed the default install directory to TrippLite\PowerAlert instead of Tripp Lite\PowerAlert to support Linux. Build 12.01.0012 (750096RevG) -Added support for using user authentication when sending email notifications. -Added support for a global on/off setting for broadcasting. Settable in the settings-system menu. -Added support for protocol 3005. -Added support for Tripp Lite 3-phase UPS systems. -Fixed bug where sometimes the PowerAlert Engine process could utilize 100% of processor when installed on system utilizing a wireless keyboard and mouse. -Fixed bug were an invalid warning message would pop up if you unchecked an event actions in the settings-events menu. -Fixed bug were new events were being appended to the bottom of the event log. -Fixed some reporting issues when PowerAlert was communicating with a 3-phase UPS -Fixed a problem with logging that was caused by corrupting the database. If the logging database becomes corrupted, PowerAlert now regenerates the database and logging continues. -The settings-system menu screen was reconfigured to add tabs to improve usability. -The active menu and sub-menu text is now green. Modified the fonts to improve readability. -Fixed a bug were sometimes PowerAlert would not detect an OS shutdown and if WatchDog was enabled in the UPS the UPS would reboot. Build 12.02.0004 -Fixed memory leak -Modified the install set to allow for the disabling of logview and status console at startup on Microsoft OS’s. -Modified the install set to recognize Java J2SE version 1.5 Build 12.02.0012 -Fixed bug when two UPS were being monitored the settings for the second device were not being saved. -Added support for Tripp HID Power Device compliant UPS systems -Added support for protocol 1003 -Added support for protocol 1004 -Added support for protocol 2005 -Added support for protocol 3101 -Added support for protocol 3009 -Fixed bug when trying to monitor two HID Power Device compliant UPS PowerAlert would only show one. Build 12.03.0010 Implemented Remote Monitoring Agent support. Allowing for monitoring of a UPS over the network. Build 12.04.0003(760096Rev J) -Add Remote Monitoring Agent support on Linux platforms -Fixed problem with email not being sent -Added support for SCO 6 -Added support for AIX 5.1,5.2 and 5.3 (no remote monitor) -Added support for Sun Solaris (intel) 10 -Added support for Sun Solaris (Sparc) 8,9 and 10 (no remote monitor) -Added support for Remote Monitoring of SNMPWEBCARD (Gen 3). Compatible with FW version 12.03.0024 of SNMPWEBCARD Build 12.04.0014 (760096Rev K) -Modified Remote Monitoring Agent initialization process. 12.04.0014 Remote Monitoring Agents will not be backward compatible with prior versions. -Added protocol support for protocol 3008 -Added protocol support for protocol 3010 -Added protocol support for protocol 4002 (split-phase UPS systems) Build 12.04.0019 (760096 Rev L) -Added support to Remote Monitoring Agent to connect up to and display data from a SNMPWEBCARD with an EnviroSense monitoring probe. -Added support for APC serial SMARTUPS protocol. -Fixed a problem where adding a remote device on a system that was also monitoring a local device to drop the local device. -Support for 3011 protocol -Fixed a problem with SNMP traps sending the wrong OID string -Modified Remote Monitoring support of SNMPWEBCARDs. PowerAlert 12.04.0019 is not compatible with SNMPWEBCAD version 12.03.0024. -SNMPWEBCARD must have FW version of 12.04.0019 or later. Build 12.04.0019b (760096 Rev M) -Support 3012 protocol Build 12.04.0030 (760096 Rev N) -Added support for Microsoft Vista -Added support for data logging to PowerAlert's internal log or to a seperate ASCII comma-delimited text file -Added support for protocol 5001 -Added support for configuration of load shedding and ramping on autonomous devices. Available autonomous devices Device Series number SMART2200RMXL2U AGSM5389 SMX2200RMXL2U AGSM5392 PDUMH15AT AGAC5558 PDUMH15ATNET AGAC5558 PDUMH20AT AGAC5559 PDUMH20ATNET AGAC5559 -On any of autonomous devices utilizing a SNMPWEBCARD, disconnect the network cable before utilizing the RS232 connection on the UPS. -Modified the SNMP trap structures to to differentiate a SNMP set event and a SNMP clear event -Added a button on the Settings-System menu to write configuration file. This file paconfig.ini is loacated in the the program files\tripplite\poweralert\engine directory. Place this file in the same directory as the installation file setup.exe and then type setup -silent to install PowerAlert and the preset configuration. -On Microsoft Vista no system tray application is installed. Launch the PowerAlert console from the start menu-program files-poweralert 12-poweralert console. To start and stop the PowerAlert Engine use Microsoft Vista's service manager. **************************************** Contacting Tripp Lites Technical Support **************************************** Customer Support (773) 869-1234 ****************************************************** OPERATING INSTALL INSTRUCTIONS (Sun Solaris,AIX and SCO) ****************************************************** ------------ SUN SOLARIS ------------ Note: please review requirments before proceeding ************ Installation ************ -Download PowerAlert 12 for Solaris Sparc gz file from Tripp Lite -Extract PowerAlert 12 from the download gz file -From the directory in which the gz file was downloaded type “gzip –d .gz" -Run the installation file which will by typing pkgadd –d -Hit enter to select the default answers for questions that are presented during installation -PowerAlert will be installed in the /opt/TrippLite/PowerAlert directory -PowerAlert can be controlled from a terminal window by typing the following pa start (will start PowerAlert) pa stop (will stop PowerAlert) pa status ( will show if PowerAlert is running or not) pa console ( will launch the PowerAlert java console) ********* Uninstall ********* -From a terminal window type pa stop to stop PowerAlert -Type pkgrm TrippLite which will uninstall PowerAlert ------ AIX ------ Note: please review requirments before proceeding ************ Installation ************ -Set up the 'inittab' to allow PowerAlert to start up on boot The following is one possible method to set up the inittab: create an /etc/inittab entry mkitab -i rcnfs "rclocal:2:wait:/etc/rc.local > /dev/console 2>&1" touch /etc/rc.local chmod 700 /etc/rc.local Put start-up command lines in /etc/rc.local as shown below: #!/bin/ksh export PATH=/opt/TrippLite/PowerAlert:/home/java/jre/bin:$PATH export TRIPPLITE_PA_HOME=/opt/TrippLite/PowerAlert /opt/TrippLite/PowerAlert/pa start -Verify that the correct PowerAlert file is available: File Name: AIX_52_tar_file.Z Size of file: 6115523 /bin/sum of file: 51995 5973 -The following are the instructions to load PowerAlert on AIX 5.2 and AIX 5.3 1. Open a terminal session as root 2. Create a temporary directory mkdir /load_install 3. Change to the directory created cd /load_install 4. Move the AIX_52_tar_file.Z file from E-mail to this directory NOTE: If the file name is not exactly as shown above use the UNIX 'mv' command to move the file to one with a name as shown above. The name must end with a capital Z in order for the UNIX uncompress command to work properly. 5. Verify that the file is correctly listed in the directory ls -l AIX_52_tar_file.Z should appear Size of the file will be provided with the E-mail 6. Verify that the checksum is correct /bin/sum AIX_52_tar_file.Z Checksum will be provided with the E-mail 7. Uncompress the file uncompress AIX_52_tar_file.Z The same file name should appear without the .Z suffix 8. Extract all the files and directories from the 'tarball' file tar xvf AIX_52_tar_file 9. Check that files and directories exist in the directory ls -l sample.profile,sample.rc_local,install.aix.sh,opt should appear NOTE: opt that appears is NOT /opt but rather /load_install/opt 10. Refer to sample.rc_local for suggestions on how to set up the rc.local file to automatically start up PowerAlert on your system. Customize per your requirements. 11. Refer to sample.profile for suggestions on how to set up root's .profile for the proper environment variables. Customize per your system's requirements. 12. Execute the install script to move the files from the temporary /load_install directory to the /opt directory. ./install.aix.sh 13. Verify that PowerAlert is running ps -ef | grep -v grep | grep pa -PowerAlert can be controlled from a terminal window by typing the following pa start (will start PowerAlert) pa stop (will stop PowerAlert) pa status ( will show if PowerAlert is running or not) pa console ( will launch the PowerAlert java console) ********* Uninstall ********* -From the desktop shut down the PowerAlert console application -From a terminal window type pa stop to stop PowerAlert -Remove all PowerAlert files as follows (assumes PowerAlert is under /opt) cd /opt rm -fr ./TrippLite ------ SCO ------ Note: please review requirments before proceeding ************ Installation ************ -Verify that the correct PowerAlert file is available: File Name: tarball.PowerAlert.SCO.Z Size of file: 4231209 /bin/sum of file: 64618 8265 -The following are the instructions to load PowerAlert on SCO 6.0 1. Open a terminal session as root 2. Change to the directory /opt cd /opt 3. Move the tarball.PowerAlert.SCO.Z file from E-mail to this directory NOTE: If the file name is not exactly as shown above use the UNIX 'mv' command to move the file to one with a name as shown above. The name must end with a capital Z in order for the UNIX uncompress command to work properly. 4. Verify that the file is correctly listed in the directory ls -l tarball.PowerAlert.SCO.Z should appear Size of the file will be provided with the E-mail 5. Verify that the checksum is correct /bin/sum tarball.PowerAlert.SCO.Z Checksum will be provided with the E-mail 6. Uncompress the file uncompress tarball.PowerAlert.SCO.Z The same file name should appear without the .Z suffix 7. Extract all the files and directories from the 'tarball' file tar xvf tarball.PowerAlert.SCO 8. Check that the following files and directories exist in the /opt directory cd TrippLite cd PowerAlert cd install ls -l files sample___.profile and sample___etc_rc.d_8_userdef should appear 9. Refer to sample___etc_rc.d_8_userdef for suggestions on how to set up the /etc/rc.d/8/userdef file to automatically start up PowerAlert on your system. Customize per your requirements. 10. Refer to sample___.profile for suggestions on how to set up root's .profile for the proper environment variables. Customize per your system's requirements. 11. Start up the PowerAlert engine with pa start 12. Verify that the PowerAlert engine is running ps -ef | grep -v grep | grep pa -PowerAlert can be controlled from a terminal window by typing the following pa start (will start PowerAlert) pa stop (will stop PowerAlert) pa status ( will show if PowerAlert is running or not) pa console ( will launch the PowerAlert java console) ********* Uninstall ********* -From the desktop shut down the PowerAlert console application -From a terminal window type pa stop to stop PowerAlert -Remove all PowerAlert files as follows (assumes PowerAlert is under /opt) cd /opt rm -fr ./TrippLite LICENSE ISSUES ============== The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org. OpenSSL License --------------- /* ==================================================================== * Copyright (c) 1998-2002 The OpenSSL Project. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. All advertising materials mentioning features or use of this * software must display the following acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit. (http://www.openssl.org/)" * * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to * endorse or promote products derived from this software without * prior written permission. For written permission, please contact * openssl-core@openssl.org. * * 5. Products derived from this software may not be called "OpenSSL" * nor may "OpenSSL" appear in their names without prior written * permission of the OpenSSL Project. * * 6. Redistributions of any form whatsoever must retain the following * acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit (http://www.openssl.org/)" * * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED * OF THE POSSIBILITY OF SUCH DAMAGE. * ==================================================================== * * This product includes cryptographic software written by Eric Young * (eay@cryptsoft.com). This product includes software written by Tim * Hudson (tjh@cryptsoft.com). * */ Original SSLeay License ----------------------- /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) * All rights reserved. * * This package is an SSL implementation written * by Eric Young (eay@cryptsoft.com). * The implementation was written so as to conform with Netscapes SSL. * * This library is free for commercial and non-commercial use as long as * the following conditions are aheared to. The following conditions * apply to all code found in this distribution, be it the RC4, RSA, * lhash, DES, etc., code; not just the SSL code. The SSL documentation * included with this distribution is covered by the same copyright terms * except that the holder is Tim Hudson (tjh@cryptsoft.com). * * Copyright remains Eric Young's, and as such any Copyright notices in * the code are not to be removed. * If this package is used in a product, Eric Young should be given attribution * as the author of the parts of the library used. * This can be in the form of a textual message at program startup or * in documentation (online or textual) provided with the package. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * "This product includes cryptographic software written by * Eric Young (eay@cryptsoft.com)" * The word 'cryptographic' can be left out if the rouines from the library * being used are not cryptographic related :-). * 4. If you include any Windows specific code (or a derivative thereof) from * the apps directory (application code) you must include an acknowledgement: * "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" * * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * The licence and distribution terms for any publically available version or * derivative of this code cannot be changed. i.e. this code cannot simply be * copied and put under another distribution licence * [including the GNU Public Licence.] */ In addition to the base install, the "AIX Toolbox for Linux Applications" is required to include the required Gnu 3.3.2 compilers and runtime libraries. This toolkit is also a prerequisite for any machine running the PA software