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
the Data (see DATA Logging) section of this manual for additional
details.
FACILITY<log-facility> The facility directive can be used to change
the system logging class or facility. The default is DAEMON. This
parameter can be useful if you wish to direct the apcupsd system
logging information to other than your system default files. See the
Logging section of this manual for additional details.
Configuration Directives for Sharing a UPS
The following directives apply to the master/slave networking mode of
apcupsd where multiple machines can be powered by the same UPS. One
machine, the master, will have a serial port connection to the UPS, and
the other machines, the slaves, will obtain their information via the network
from the master.
Note, as of version 3.10.x, the old master/slave code is by default turned
off in the configuration. You must explicitly enable it by including a
--enable-master-slave option on your ./configure command before
building the source.
In addition to the old master/slave code, there is now a new network driver
enabled with --enable-net (default disabled) that can be used to control a
slave from any version of apcupsd running NIS. This is a much more flexible
system of controlling slaves because a slave machine that also has NIS turned
on can thus act as a master for another slave with --enable-net turned
on. With this mode turned on, the slave obtains the address of the master
from the DEVICE directive, which takes the form hostname[:port] as a
consequence, none of the directives apply for this form of networking. In
addition, for this mode to work, you must specify UPSTYPE net so that
the proper driver is loaded.
The remainder of this section presents directives that apply to the old mas-
ter/slave code that must be enabled by the enable-master-slave configu-
ration option.
UPSCLASS <class of operation> [ standalone — shareslave — share-
master ] and [ netslave — netmaster ] are valid types. [ standalone —
netslave — netmaster ] are tested classes. [ shareslave — sharemaster
] classes are being tested.
The default is standalone and should be used for all machines pow-
ered by the UPS and having a serial port connection to the UPS, but
170










