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
networking is considerably different from the old method described at the
beginning of this chapter. In the old code, there is a lot of configuration on
both the master and slave side, and the master polls or sends info to the
slave. Using the net driver is much simpler. However, you should carefully
check that the NIS slave does a proper shutdown. In the master/slave code,
the master ensures the best it can that the slave is shutdown or notified
before it shuts down itself. On the other hand, using the net driver, the
NIS server knows nothing about the NIS slaves that may be listening and
thus takes no special precautions to ensure that the NIS slaves receive the
shutdown signal. Since the NIS slave reads the master’s data once per second
there should be no shutdown problems, and our experience confirms this.
This question can only be answered by carefully testing the shutdown.
In this NIS server/slave mode, the NIS server is a standard stand alone con-
figuration except that it must have NETSERVER on in the configuration
file and have an NISPORT nnn defined. Thus any apcupsd running in
this mode then becomes the NIS server.
The NIS slave then uses the net driver to connect to the server’s NIS output.
In this mode, the NIS slave decides how often to poll the server for the
NIS information. The NIS slave’s conf file has UPSTYPE net, which
will invoke the “network” driver. By setting this machine’s DEVICE to be
server-ip:server-NIS-port it will automatically connect to the NIS server
and use the server’s signals to shutdown the computer. In the example net
slave configuration file below, the slave uses the NIS information provided
by the computer tibs on port 3551.
## apcupsd.conf v1.1 ##
UPSCABLE ether
UPSTYPE net
# Specify the server name:port where NIS is running
DEVICE tibs:3551
LOCKFILE /var/lock
BATTERYLEVEL 5
MINUTES 3
TIMEOUT 0
ANNOY 300
ANNOYDELAY 60
NOLOGON disable
EVENTSFILE /etc/apcupsd/apcupsd.events
UPSCLASS standalone
UPSMODE disable
#
# Use this to control the poll time.
# the default is 60 or 1 minute
#
NETTIME 30
107










