User's Manual UPS control system
Table Of Contents
- Apcupsd User's Manual
- Release Notes
- How To Use This Manual
- Basic User's Guide
- Planning Your Installation
- Building and Installing apcupsd
- After Installation
- Configuration Examples
- Testing Apcupsd
- Troubleshooting Your Installation
- Monitoring and Tuning your UPS
- Maintaining Your UPS
- Frequently-Asked Questions
- Apcupsd Bugs
- Advanced topics
- Customizing Event Handling
- Master/Slave Configurations
- Controlling Multiple UPSes on one Machine
- Support for SNMP UPSes
- Alternate Ways To Run The Network Information Server
- apcupsd System Logging
- Installation: Windows
- Windows Version of apcupsd
- Installation: Serial-Line UPSes
- Overview of Serial-Interface UPSes
- Connecting a Serial-Line UPS to a USB Port
- Connecting a APC USB UPS to either a PC USB or Serial Port
- Cables
- Smart-Custom Cable for SmartUPSes
- Smart Signalling Cable for BackUPS CS Models
- Voltage-Signalling Cable for "dumb" UPSes
- Other APC Cables that apcupsd Supports
- Voltage Signalling Features Supported by Apcupsd for Various Cables
- Voltage Signalling
- Back-UPS Office 500 signals
- Analyses of APC Cables
- Win32 Implementation Restrictions for Simple UPSes
- Internal Apcupsd Actions for Simple Cables
- RS232 Wiring and Signal Conventions
- Pin Assignment for the Serial Port (RS-232C), 25-pin and 9-pin, Female End
- Ioctl to RS232 Correspondence
- Testing Serial-Line UPSes
- Troubleshooting Serial Line communications
- Recalibrating the UPS Runtime
- DATA Logging
- Technical Reference
- Configuration Directive Reference
- apcupsd Status Logging
- Shutown Sequence and its Discontents
- APC smart protocol
- Apcupsd --- RPM Packaging FAQ
- Credits
- Kernel Config
Next you must edit the hosts file /etc/apcupsd/hosts.conf and at the end,
add the name of the hosts you want to monitor and a label string for them.
Kern Sibbald uses multimon.conf unmodified from what is on the source
distribution. However, he has modified the hosts.conf file to contain the
following three lines:
MONITOR matou "Server"
MONITOR polymatou "Backup server"
MONITOR deuter "Disk server"
matou, polymatou, and deuter are the network names of the three machines
currently running apcupsd. Please note that the network names may either
be IP addresses or fully qualified domain names. The network name (or
IP address) may optionally be followed by :<port>, where the port is the
NIS port address you wish to use. This is useful if you are running multiple
copies of apcupsd on the same system or if you are running in a mixed vendor
environment where the NIS port assignments differ. An example could be
the following:
MONITOR matou "Server"
MONITOR polymatou "Backup server"
MONITOR deuter "Disk server"
MONITOR polymatou:7001 "APC USB UPS"
where the USB copy of apcupsd has been configured to use port
7001 (with --with-nis-port=7001 on the ./configure or by modifying
apcupsd.conf). Note, the default NIS port is 3551 on most platforms.
To test multimon.cgi, you can execute it as non-root directly from the source
cgi build directory. To do so, enter at a shell prompt:
./multimon.cgi
If everything is set up correctly, it will print a bunch of HTML with the
values of the machines that you have put in the hosts.conf file. It should
look something like the following (note, only a small portion of the output
is reproduced here):
77










