Table of Contents 1.0 Operating System Requirements 2.0 Installing the PowerChute Business Edition Agent 3.0 Starting the PowerChute Business Edition Agent 4.0 Stopping the PowerChute Business Edition Agent 5.0 Uninstalling the PowerChute Business Edition Agent 6.0 Using the Linux Sample Shell Script 7.0 Known Issues with PowerChute Business Edition Agent 1.0 Operating System Requirements - The PowerChute Business Edition Agent is compatible with Red Hat Linux Professional 7.3, 8.0, 9.0; 7.3J, 8.0J, 9.0J Red Hat Linux AS 2.1, 3.0; 2.1J, 3.0J Red Hat Linux ES 2.1, 3.0; 2.1J, 3.0J Red Hat Linux WS 3.0; 3.0J Turbolinux® Server 8.0; 8.0J; 10.0; 10.0J SuSE Linux Professional 8.2, 9.0, 9.1 (not supported in Japan) Miracle Linux 2.1J, 3.0J (only in Japan) Novell® NetWare® 6.0, 6.5 (not supported in Japan) Solaris 8, 9; 8J, 9J - The PowerChute Business Edition Agent installs and requires Sun Microsystems' JVM 1.4.2_06. 2.0 Installing the PowerChute Business Edition Agent ========================================================= NOTE: Your Linux download only includes the Agent component of the three PowerChute Business Edition software components. The other two components only run on Windows; all three are described below. 1. PowerChute Business Edition Agent: Provides UPS status monitoring and, in the event of an extended power outage, system shutdown capabilities for your UPS-protected computers. The Agent must be installed on each computer that is directly attached to one of the supported UPS systems. 2. PowerChute Business Edition Server: Used to configure and monitor the Agents. The PowerChute Server gathers information from the PowerChute Agents and provides centralized event tracking, event notification, and a single point of contact for the PowerChute Console. The Server software must be installed on one of your supported Windows networked computers. 3. PowerChute Business Edition Console: Connects to the PowerChute Business Edition Server to provide the user interface for managing and configuring your UPS-protected systems. The Console can be installed on any supported Windows workstation, desktop, or laptop (running a supported operating system). ======================================================== Launch the PowerChute Business Edition for Linux installer by entering the absolute path to the pbe_agent_redhat_jvm.bin file. This file can be found in the Linux directory on the CD-ROM. For example, if the CD-ROM is mounted to /mnt/cdrom, you would enter the following at the shell prompt... /mnt/cdrom/Linux/pbe_agent_linux_jvm.bin An RPM package of the PowerChute Business Edition Agent for Linux is also available. This is also found in the Linux directory on the CD-ROM. Install the package using the -i (install) option. For example, if the CD-ROM is mounted to /mnt/cdrom, you would enter the following at the shell prompt... rpm -i /mnt/cdrom/Linux/pbeagent-xxx.i386.rpm ...where xxx is the version of the product. This installs PowerChute Business Edition to the default directory, /opt/APC/PowerchuteBusinessEdition/Agent. If PowerChute Business Edition Agent 7.0.1 or later was installed from an RPM, you may upgrade by using the -U option. This rpm also supports the --prefix option to allow you to specify the destination directory. For example, rpm -i /mnt/cdrom/Linux/pbeagent-xxx.i386.rpm --prefix /PCBE_Agent ...would install the PowerChute Business Edition Agent to the /PCBE_Agent directory. Once the RPM has been installed, you MUST configure the Agent for login information and the UPS type. This is handled by running the "config.sh" script located within the PowerChute Business Edition installation directory. NOTE: This script should only be run immediately after installing the RPM. Subsequent configuration changes must be done through the PowerChute Business Edition console. This utility allows you to create an account name and password, and to configure the UPS by entering the communication type and communication port. The utility asks various questions including whether you are using simple or smart signaling. If you have a 940-0020B, then you use simple signaling; if you have a 940-0024B, 940-0095A, or 940-009 then you use smart signaling. (Smart signaling gives you more information such as battery voltage and battery runtime remaining and a log recording power-related data over a time period. It also enables you to define power parameters such as high-transfer voltage and sensitivity.) After completing the configuration, you can start the PowerChute Business Edition Agent. 3.0 Starting the PowerChute Business Edition Agent After the installation process is completed, the PowerChute Business Edition Agent begins running automatically. The Agent runs automatically each time the operating system is started. To manually start the PowerChute Business Edition Agent after it has been deliberately stopped, you can enter the following command at the shell prompt from anywhere in the file system ... /etc/init.d/PBEAgent start 4.0 Stopping the PowerChute Business Edition Agent To stop the PowerChute Business Edition Agent when it is running, you can enter the following command from anywhere in the file system ... /etc/init.d/PBEAgent stop 5.0 Uninstalling the PowerChute Business Edition Agent To uninstall the PowerChute Business Edition Agent if you used the .bin executable, enter the absolute path to the uninstallPowerChuteBusinessEditionAgent script that is located in the directory where the Agent has been installed. For example, if the Agent is installed to /opt/APC/PowerChuteBusinessEdition/Agent directory, enter the following command at the shell prompt to uninstall the PowerChute Business Edition Agent ... /opt/APC/PowerChuteBusinessEdition/Agent/uninstallPowerChuteBusinessEditionAgent If you used the rpm to install the PowerChute Business Edition Agent, use the -e (erase) rpm option to uninstall PowerChute Business Edition. For example: rpm -e pbeagent 6.0 Using the Linux Sample Shell Script The "default.sh" file has basic information on running a command file on Linux. It is included in the installation at /Agent/cmdfiles/ Here is the complete text of the "default.sh" file: ========================================================= # # This command file is here for demonstration purposes only # # In order for PowerChute Business Edition to recognize additional # command files they must be placed in the directory where # this file currently resides. # # This file is not required for the correct operation of # PowerChute Business Edition. # # Note: Before running any kind of scripts in Linux, be sure to # include a #!/bin/(type of script) at the very top of your script file. # # For example: # If you use shell script, then use #!/bin/sh # If you use Bourne shell script, then use #!/bin/sh # If you use Bourne Again shell script, then use #!/bin/bash # If you use C shell script, then use #!/bin/csh # # If this does not work please contact your system administrator. ========================================================= The Console online help, included with PowerChute Business Edition for Windows platforms, contains background information on setting up command files through the Shutdown Sequence dialog box. 7.0 Known Issues 7.1 Issue: The product does not perform properly with an APC Back-UPS or an APC UPS using Simple Signaling. Solution: PowerChute Business Edition requires the 940-0020B cable for UPS communications using Simple Signaling. If you were using the 940-0023A cable with a previous PowerChute product, you must replace it with the 940-0020B cable when you use PowerChute Business Edition. 7.2 Issue: PowerChute Business Edition does not install on a system which is using the SJIS locale. Solution: The SJIS locale is not supported by PowerChute Business Edition. The only Japanese locale supported by PowerChute is eucJ. 7.3 Issue: SNMP Communication cannot be configured. Solution: SNMP communication is not available on PowerChute Business Edition Agent for Linux. 7.4 Issue: PowerChute Business Edition Agents running on Linux may not be able to send broadcast messages to Windows systems. If you are using Japanese-language systems, messages sent from Linux to Windows may not be readable. Solution: These problems are the result of incompatibilities between Windows and Linux, and cannot be resolved through PowerChute. 7.5 Issue: When the PowerChute Business Edition daemon is stopped, the "Monitoring Stopped" event is not recorded in the PowerChute Business Edition event log. Solution: This is a known issue which will be corrected in a future release of PowerChute. 7.6 Issue: During the PowerChute Business Edition Agent install using the graphical .bin install file on a RedHat 7.3 Japanese system, dialog boxes display incorrect characters and text. Solution: Install the PowerChute Business Edition Agent using the RPM file 7.7 Issue: When the --prefix option is used to install the RPM on RedHat 8.x, the PowerChute Business Edition Agent does not install to the directory specified. Solution: There is a known issue with RPM version 4.1x which ships with RedHat 8.0 where the --prefix option does not operate correctly. If this version of RPM is installed, the PowerChute Business Edition Agent will install to the default directory, /opt/APC/PowerChuteBusinessEdition/Agent, regardless of the directory specified. 7.8 Issue: When the --prefix option is used to install the RPM on Turbolinux 8.x, the /opt/APC/PowerChuteBusinessEdition/Agent directory is still created. Solution: This is an issue that will not affect the performance of PowerChute. This empty folder is removed upon uninstallation of the PowerChute Business Edition Agent. 7.9 Issue: During the boot process, the server momentarily pauses and displays messages similar to one of the following: modprobe: modprobe: can't locate module char-major-4 Solution: This is an issue that will not affect the performance of PowerChute. 7.10 Issue: PowerChute Business Edition Agent installer generates the following error on some Linux systems: Exception in main class "JExpressLoader" Solution: The package compat-libstdc++-7.3-2.96.118.i386.rpm is required on the system prior to installing the PowerChute Business Edition Agent. 7.11 Issue: RPM uninstall reports "error: cannot remove /opt/APC/PowerChuteBusinessEditionAgent directory not empty". Solution: This is a cosmetic issue that does not affect the performance of Powerchute. The directory is properly removed during the uninstall. 7.12 Issue: JVM files remain on cancelling out of a Solaris or Linux installation Solution: Manually remove all the installed files when you cancel out of an installation on these operating systems. 7.13 Issue: Old JVM files remain after upgrading to this version of PowerChute Business Edition (PCBE) Solution: If no other program is using these JVM files, manually remove the contents of all folder(s) except the 1.4.2_06 folder created by this version of PCBE. 7.14 Issue: Japanese characters appear garbled when installing on Turbolinux 10 Solution: Perform the following steps to fix this problem: 1) Change locale setting to English(en_US) at the time you run the installer. 2) After completing the install, restore Japanese locale(ja_JP.eucJP) and stop the PCBE agent service. #cd /opt/APC/PowerChuteBusinessEdition/Agent/bin #./startup stop 3) Add the following line to the second line of the two files /etc/rc.d/init.d/PBEAgent /opt/APC/PowerChuteBusinessEdition/Agent/bin/startup add below the second line which is after #!/bin/sh export LC_ALL=ja_JP 4) Restart PCBE agent #cd /opt/APC/PowerChuteBusinessEdition/Agent/bin #./startup start