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
Please note, there are reports that you must use UPSTYPE smartups on
the slave even if the master is using UPSTYPE dumb. This is apparently
some bug in the new dumb driver.
In this configuration, the shutdown will be initiated by the master. It is also
possible to specify BATTERYLEVEL, MINUTES, and TIMEOUT configu-
ration directives in the Slave machine that will cause the slave to shutdown
before the master. This can often be useful if the slave is less important
than the master and you wish to reduce battery power consumption so that
the master can remain up longer during a power outage.
Variation on the Master/Slave Configuration
It is also possible to have a Master/Slave configuration where the Slave is
powered by a different UPS (or any other power source), but is nevertheless
controlled (i.e. shutdown) by the master. The setup would be identical
to the Master/Slave configuration files shown above. The only difference is
where the slave actually receives its power. In effect, apcupsd does not know
or care where the power really comes from.
A Sample NIS Slave Configuration Using the Net Driver
As opposed to the old master/slave mode demonstrated above, you can
turn any computer into an NIS slave by configuring with the NIS network
driver turned on --enable-net. The difference is that the NIS server has
no explicit knowledge of the slaves. The NIS server makes its information
available via the net (NIS), and the NIS slaves read it. When the NIS server
is going to shutdown, it makes the information available to any NIS slave
that polls it, but the NIS server does not explicitly call each NIS slave as is
the case in the Master/Slave networking described several sections above.
Running in this configuration, you can use any computer with apcupsd
running the Network Information Server (NIS) as the server. The NIS slave
simply uses the NIS information to decide when to shutdown. This is a
much simpler mode than the older master/slave code mentioned above.
The main apcupsd (NIS server) is connected to the UPS and has NIS turned
on, but the configuration is a simple standalone as in the section A Sim-
ple Configuration for a SmartUPS. It doesn’t matter how the UPS is
connected to the computer (serial, USB, ...).
For the NIS slave computer, you will have a configuration that looks some-
56










