RELEASE NOTES for LANSAFE III (C) Copyright Powerware Corporation 2002 This document contains up-to-date information for LanSafe III version 4.17.3a and previous versions. Last Updated: January 20, 2003 CONTENTS ******************************************************* RELEASE NOTES FOR THE CURRENT VERSION ******************************************************* ================================================== RELEASE NOTES for Version 4.17.3a ================================================== --------------------------------------------- 1.0 New Features and Enhancements in Version 4.17.3a --------------------------------------------- 1.1 Added and Deleted UPS models in UPS Lists 1.2 Extended to 64-bit platform on AIX 1.3 Agent changed to support IBM Director --------------------------------------------- 2.0 Bugs Fixed/Issues Resolved in Version 4.17.3a --------------------------------------------- 2.1 Unable to install LanSafe on SuSE 7.2 or 8.0 2.2 LanSafe daemon on SuSE7.2 or 8.0 not run automatically after reboot/shutdown 2.3 Host IP not resolved with SuSE7.2 or 8.0 2.4 UPS on battery alert is not honoring wink time on Linux 2.5 Unable to install LanSafe tar file on RedHat 8.0 2.6 Console is read-only after correct password entered on Linux 2.7 Warning alert interferes with comm lost alert in Unix Power Monitor window --------------------------------------------- 3.0 Known Issues and Workarounds in Version 4.17.3a --------------------------------------------- 3.1 UPS Group list rebuild may require restart of Console 3.2 UPS Group communication failures cause intermittent loss of communication between Controller and Members ******************************************************* RELEASE NOTES FOR THE PREVIOUS VERSION ******************************************************* ================================================== RELEASE NOTES for Version 4.17.2a ================================================== --------------------------------------------- 1.0 New Features and Enhancements in Version 4.17.2a --------------------------------------------- --------------------------------------------- 2.0 Bugs Fixed/Issues Resolved in Version 4.17.2a --------------------------------------------- 2.1 Netware 6 not working with XCP-protocol UPSs --------------------------------------------- 3.0 Known Issues and Workarounds in Version 4.17.2a --------------------------------------------- 3.1 Netware Group Controller may not shutdown during Low Battery AC Failures if server not rebooted after install 3.2 Low Battery causes unexpected delays in shutdown for Netware Standalone 3.3 OS does not shutdown for Netware during Low Battery if OS is not rebooted after install ******************************************************* RELEASE NOTES FOR THE CURRENT VERSION ******************************************************* ================================================== RELEASE NOTES for Version 4.17.3a ================================================== These release notes cover changes made to LanSafe III since the release notes for version 4.17.2a for LanSafe III were published. --------------------------------------------- 1.0 New Features and Enhancements in Version 4.17.3a --------------------------------------------- 1.1 Added and Deleted UPS models in UPS Lists The following models were deleted from UPS Lists: Powerware 9350 Axxium Tower The following models were added to UPS Lists: Sola 1000 Sola 3010 Sola 4000 Sola 8000 Densei-Lambda 9126 1.2 Extended to 64-bit platform on AIX LanSafe is now compatible with both 32-bit and 64-bit AIX platforms 1.3 Agent changed to support IBM Director Modify current LanSafe SNMP proxy agent to support PW IBM Director Snap-In. --------------------------------------------- 2.0 Bugs Fixed/Issues Resolved in Version 4.17.3a --------------------------------------------- 2.1 Unable to install LanSafe on SuSE 7.2 or 8.0 Init directories in SuSE 7.2 and 8.0 changed from /sbin/init.d/ to /etc/init.d SOLUTION: Set init directories var of install.sh to /etc/init.d/ for SuSE 7.2 or 8.0 2.2 LanSafe daemon on SuSE7.2 or 8.0 not run automatically after reboot/shutdown During installation the 'automatic restart' option was selected. However, after reboot or shutdown it is necessary to start the daemon from the ls3 install directory with "./ls3 &" on SuSE 7.2 or 8.0 SOLUTION: On SuSE 7.2 or later, default runlevel is 5 (full multiusers with network and xdm) in /etc/inittab. But max runlevel for current LanSafe auto start is only 3. Modify install.sh to increase ls3 auto start runlevel to 5, in /etc/inittab file. 2.3 Host IP not resolved with SuSE7.2 or 8.0 Host IP on machines where Power Monitor installed could not be resolved by LanSafe, causing connection related problems between PMs SOLUTION: Recompile LanSafe on newer build environment RedHat 7.2 2.4 UPS on battery alert is not honoring wink time on Linux UPS on battery alert message displayed during wink time. SOLUTION: set a delay on "UPS on battery" alert. Delay value equals wink time. 2.5 Unable to install LanSafe tar file on RedHat 8.0 Tar installation of LanSafe halts, because new OS has no "(un)compress" utilities to expand files during installation. SOLUTION: uncompressed all installed files before packaging to tar file. 2.6 Console is read-only after correct password entered on Linux Correct password not recognized to enable access to settable features in Console window SOLUTION: replaced Console built on RedHat 7.2 by Console built on Turbo Linux 1.2 2.7 Warning alert interferes with comm lost alert in Unix Power Monitor window "Can not contact PM Deamon" warning message interferes with PM window alert when comm lost occurs. This gives impression that communication with UPS is on and off intermittenly SOLUTION: don't display the warning during comm lost --------------------------------------------- 3.0 Known Issues and Workarounds in Version 4.17.3a --------------------------------------------- 3.1 UPS Group list rebuild may require restart of Console The list of computers associated as a UPS Group may not be fully populated when the Console is first run. If members are missing from the UPS Group, restart the Console. 3.2 UPS Group communication failures cause intermittent loss of communication between Controller and Members The Controller becomes very busy during UPS communication failures, making the reestablishment of communication with the UPS its highest priority task. Because of this, it is possible that intermittent messages will be generated by a member indicating their temporary loss of connection to the controller. This is because the members verify their connection to the controller every 30 seconds. If this occurs while the controller is too busy to acknowledge the members message, the member will announce the loss of connection. COnsequences are no more dire than the loss of the UPS communications with the Controller. This is the serious issue, and the Controller is "right" to make it a top priority to reestablish this connection as quickly as possible. While in this state, all members would not be able to be aware of any UPS status changes anyway, so the fact that the have a temporary loss of connection to the Console does not make this situation any worse. ******************************************************* RELEASE NOTES FOR THE PREVIOUS VERSION ******************************************************* ================================================== RELEASE NOTES for Version 4.17.2a ================================================== These release notes cover changes made to LanSafe III since the release notes for version 4.17.1a for LanSafe III were published. --------------------------------------------- 1.0 New Features and Enhancements in Version 4.17.2a --------------------------------------------- --------------------------------------------- 2.0 Bugs Fixed/Issues Resolved in Version 4.17.2a --------------------------------------------- 2.1 Netware 6 not working with XCP-protocol UPSs LanSafe on Netware 6 in use with XCP-protocol based UPSs is now working properly. In previous versions, the Netware 6 AIOCOMX NLM would become unloaded unexpectedly in this situation. --------------------------------------------- 3.0 Known Issues and Workarounds in Version 4.17.2a --------------------------------------------- 3.1 Netware Group Controller may not shutdown during Low Battery AC Failures if server not rebooted after install The Controller will not shutdown after the Low Battery and Shut down in 1 min message is displayed. The computer seems to freeze up and never shut down the system. This has happened with Netware 6 and 5.0 as the controller. The UPS does not shut down until the battery is completely out of power. All previous settings are ignored. 3.2 Low Battery causes unexpected delays in shutdown for Netware Standalone When performing a low battery test, on various Netware systems (4.11, 5.0, & 6), the system shut down gracefully. The problem occurs with last three messages to the Netware 6 Logger screen/PM were: "13:27:55 Low battery" "13:27:55 OHIO will shut down in 1 min" "13:31:04 OHIO is now shutting down" "13:31:05 OHIO will shut down in 1 min." Then the OS began to shut down. According to the time stamps, the OS starts to shut down 2 minutes later than expected. This may be a major problem if the UPS only provides 2 minutes of runtime which is the current guaranteed runtime after the low battery message. 3.3 OS does not shutdown for Netware during Low Battery if OS is not rebooted after install (recommended installation requirement) OS does not shutdown after the low battery and 1 min to shutdown message appears. LanSafe stays frozen in that state until the battery runs out of back-up power and crashes the system when load segment shuts off. This only occurs if LanSafe is installed on Netware, manually started (load ls3ip, ls3ipx, ls3agent), and without reboot, a low battery scenario is executed. ------------------------------------------------------------ FailSafe III, LanSafe III, SurfSafe, and OnliNet are registered trademarks of Powerware Corporation. Windows 95, Windows 98, Windows NT, and Windows 2000 are trademarks of Microsoft Corporation. NetWare is a trademark of Novell Corporation. OS/2, AIX, and Netfinity are trademarks of IBM Corporation. HP-UX is a trademark of Hewlett Packard. Solaris is a trademark of Sun Micro Systems. SCO OpenServer and UnixWare are trademarks of Santa Cruz Operation. Tru64 is a trademark of Compaq.