DOCSLIB.ORG

Apcupsd User's Manual Apcupsd User's Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Apcupsd User's Manual Apcupsd User's Manual apcupsd User's Manual apcupsd User's Manual Revision History Revision 2.0 20 Sept 2003 esr First XML−DocBook version. Table of Contents Release Notes New Features in in 3.10.6 New Features in 3.10.5 New Features in 3.10.4 How To Use This Manual I. Basic User's Guide 1. Planning Your Installation Quick Start for Beginners Supported Operating Systems, UPSes and Cables Choosing a Configuration Type Checking Out Your USB Subsystem 2. Building and Installing apcupsd Installation from Binary Packages Red Hat Linux Microsoft Windows Installation from Source Verifying a Source Installation Configure Options Recommended Options for most Systems Compilers and Options Operating System Specifics Alpha Debian FreeBSD HPUX NetBSD OpenBSD Red Hat Systems Slackware SuSE Sun Solaris Unknown System Windows Systems with CYGWIN Installed 3. After Installation Checking Your Configuration File Arranging for Reboot on Power−Up Making Sure apcupsd Is Running 4. Testing apcupsd Process−Status Test Logging Test apcaccess Test apcupsd User's Manual 1 apcupsd User's Manual Communications Test Simulated Power Fail Test System Shutdown Test Full Power Down Test Shutdown Sequence apctest 5. Troubleshooting Your Installation Known Problems with USB UPSes Reconnection does not clean up the lockfile Power Off (killpower) of UPS Does Not Work apcupsd Cannot Reconnect After a Reboot 6. Monitoring and Tuning your UPS apcaccess apcaccess status apcaccess eprom hid−ups and USB Specific Information apcupsd Network Monitoring (CGI) Programs Setting up and Testing the CGI Programs multimon.cgi upsstats.cgi ./upsstats.cgi upsfstatus.cgi Working Example Client Test Program A Tip from Carl Erhorn for Sun Systems Credits Security Issues Configuring Your EEPROM apcupsd No Longer Configures EEPROM Using apctest to Configure Your EEPROM 7. Maintaining Your UPS What Various People Have to Say about Batteries Where Carl Suggests You Get Batteries 8. Frequently−Asked Questions 9. Apcupsd Bugs II. Advanced topics 10. Customizing Event Handling apccontrol Command Line Options 11. Master/Slave Configurations Configuration Directives Master/Slave Problems Master/Slave Shutdown Master/Slave Networking using NIS and the NET Driver Network Problems with Master/Slave Configurations Error Messages from a Master Configuration Error Messages from a Slave Configuration Master/Slave Connection Not Working 12. Controlling Multiple UPSes on one Machine Configuration The First Copy of apcupsd The Second Copy of apcupsd apcupsd User's Manual 2 apcupsd User's Manual Important Steps after Installation of the Second Copy 13. Support for SNMP UPSes Connecting an SNMP UPS Building and Installing apcupsd SNMP Specific Information Known Problems 14. Alternate Ways To Run The Network Information Server Running the server as a child of apcupsd Running apcnisd from INETD Running apcnisd Standalome 15. apcupsd System Logging Logging Types Implementation Details Developer's Notes III. Legacy Installation: Windows 16. The Windows Version of apcupsd Installation Installation Directory Testing Upgrading Post Installation Problem Areas Utility Functions Disclaimer Email Notification of Events Killpower under Windows Power Down During Shutdown Command Line Options Specific to the Windows Version Building the Win32 Version from the Source IV. Legacy Installation: Serial−Line UPSes 17. Overview of Serial−Interface UPSes 18. Connecting a Serial−Line UPS to a USB Port 19. 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 The Back−UPS Office 500 signals Analyses of APC Cables 940−0020B Cable Wiring 940−0020C Cable Wiring 940−0023A Cable Wiring 940−0095A Cable Wiring 940−0095B Cable Wiring 940−0119A Cable Wiring BackOffice ES BackUPS ES and CS in Serial mode with Cable 940−0128A Win32 Implementation Restrictions for Simple UPSes Internal Apcupsd Actions for Simple Cables apcupsd User's Manual 3 apcupsd User's Manual RS232 Wiring and Signal Conventions Pin Assignment for the Serial Port (RS−232C), 25−pin and 9−pin, Female End Ioctl to RS232 Correspondence 20. Testing Serial−Line UPSes Establishing Serial Port Connection Using apctest on Serial−Line UPSses Expected apctest Signals for a UPS Expected apctest Signals for a BackUPS Pro 21. Troubleshooting Serial Line communications Determining Which Voltage−Signaling Cable You Have Once you have established serial communications Bizarre Intermittent Behavior 22. Recalibrating the UPS Runtime Status Logging On Serial−Line UPSes 23. DATA Logging V. Technical Reference 24. Configuration Directive Reference General Configuration Directives Configuration Directives Used by the Network Information Server Configuration Directives used during Power Failures Configuration Directives used to Control System Logging Configuration Directives for Sharing a UPS Configuration Directives Used to Set the UPS EPROM 25. Configuration Examples A Simple Configuration for a SmartUPS A Simple USB Configuration A Simple Master Configuration A Simple Slave Configuration Variation on the Master/Slave Configuration A Sample Slave Configuration Using the Net Driver 26. apcupsd Status Logging Status report format Status Report Example Status Report Fields Logging the STATUS Information 27. The Shutown Sequence and its Discontents Shutdown Sequence Shutdown Problems Master/Slave Shutdown Startup Windows Considerations 28. APC's smart protocol Description RS−232 differences Diagram for cable hackers The Smart Protocol Dip switch info Status bits Alert messages Register 1 Register 2 apcupsd User's Manual 4 apcupsd User's Manual Register 3 Interpretation of the Old Firmware Revision Interpretation of the New Firmware Revision EEPROM Values Programming the UPS EEPROM Acknowledgements A. Credits Contributors Disclaimer: NO WARRANTY List of Figures 1.1. Configuration types. Release Notes Table of Contents New Features in in 3.10.6 New Features in 3.10.5 New Features in 3.10.4 This release contains a good number of cleanups and bug fixes to prior 3.10.x versions, and is intended to be the official release. See the ChangeLog below for more details. New Features in in 3.10.6 This release contains a good number of cleanups and bug fixes to prior 3.10.x versions, and is intended to be the official release. See the ChangeLog below for more details. Change Log − Lots of updates to the document. − Fixed a slave crash in master/slave mode. It was a missing setup_device, and was diagnosed and reported by Christian Schacht −− many thanks. − Made non−existent header files non−fatal and added #ifdef around sys/socket.h so it will compile on IRIX. − Add Scott's latest apcupsd.conf with the hid−ups program code (actually I had done this some time ago ...). − Start a ReleaseNotes file − Fixed a typo error (mine) that prevented Scott from building rpms. Strange, it worked for me???? − More DESTDIR cleanup for building non−root rpms. − Add DESTDIR everywhere so we can build rpms non−root − Additional documentation − Add Scott's new apcupsd.spec − On Hilary Jones suggestion, I fixed the ./configure message that is printed when no libgd is found to direct the user to the main source. − Add Sergey Vlasov's kernel patch to the examples directory, and it replaces the previous patch. This patch now solves the killpower problem on Linux USB. <apcupsd−source>/examples/linux−2.4.20−alt−apc_usb_ups.patch Release Notes 5 apcupsd User's Manual notes are in: linux−usb−patch−email.txt − Add TTY mode to apctest to communicated directly with UPS. − Apply patch to linux−usb.c in killpower supplied by Sergey Vlasov (thanks!). − Eliminate pow() function in linux−usb.c so that −lm is not needed. − Add automatic detection of socklen_t − I received a kernel patch from Sergey Vlasov that fixes the killpower problem on CS UPSes. apcupsd can now shutdown these devices! I've removed some debug code that was in the killpower routine and is not needed or used. I have put the kernel patch in: <apcupsd−source>/examples/linux−2.4.20−alt−hidups.patch − When the Win32 version starts as a service, delete the NOLOGIN and PWRFAIL files to prevent later confusion. Thanks to Allen Crawford for pointing this out. − Modify all Win32 program so that only windowed programs (apcupsd, popup) have the −mwindows flags. The others do not. − Tweak apctest.c a bit −− add EEPROM programming (still a bit kludgy), but at least it can be done. − Lots of clean ups for Cygwin stuff. Events now work, and exit. − Clean up a few undefined symbols in building with everything on. − Eliminate pid and serial port lock file on Win32 systems. − Modify init script to use daemon so that STDIN/OUT, ... are detached from the terminal and pointed to the log file. This prevents remotely logged in users who start apcupsd from being unable to log out. − Made some mindor modifications to configure.in and aclocal.m4 to make consistent use of double quotes in test statements in response to problems with make install reported by Andrew Surratt. − Thanks to Richard Schwaninger for finding and submitting a patch to the tcp−wrappers code that prevented it from working because of an invalid name. Fixed. − Thanks to Andrew Reid for pointing out that the child reaping code should be clearing the pid slot if a −1 is returned. The pid table was filling up on his system due to killed children. Fixed − A bug report against the Mandrake version of apcupsd indicates that apcupsd is not releasing /dev/console. I've moved the close() of STDIN so that it is always executed to prevent this possibility. − Implement very crude first cut of EEPROM programming in apctest. Set battery date, set UPS name, and print EEPROM values should work. New Features in 3.10.5 This release is primarily version 3.10.4 but including a fix that closes a root exploit of slave machines. In addition, it makes the −−enable−master−slave ./configure option work and has a few updates to the Mandrake release.
Load more

Recommended publications
  • Power Monitoring Using the Raspberry Pi
    2013 ASCUE Proceedings Power monitoring using the Raspberry Pi Robin M Snyder RobinSnyder.com [email protected] http://www.robinsnyder.com Abstract The Raspberry Pi is a credit card size low powered compute board with Ethernet connection, HDMI video output, audio, full Linux operating system run from an SD card, and more, all for $45. With ca- bles, SD card, etc., the cost is about $70. Originally designed to help teach computer science principles to low income children and students, the Pi has taken on a life of its own, with many online resources and projects that cover most everything one would want to do with a small low monetary cost and low battery power computer. This paper/session will present the Raspberry Pi and provide ideas of what it can do and how one can get started using it. The author has used Pi's for Internet data acquisi- tion/monitoring, cluster processing using more than one Pi, email notifications, and power monitoring. The particular focus example will be on UPS power monitoring and status using off the shelf Open Source software. The main software for the purpose of power monitoring is NUT, Network UPS Tools, whose goal is "to provide support for Power Devices, such as Uninterruptible Power Supplies, Power Distribution Units and Solar Controllers." Some background in the theory and practice of electrical power, surge protection, uninterruptible powers supplies, etc., will be provided. Introduction The Raspberry Pi is a credit card size low powered compute board with Ethernet connection, HDMI video output, audio, full Linux operating system run from an SD card, and more, all for $45.
    [Show full text]
  • Eaton UPS Software Intelligent Power Manager Manual
    www.eaton.com Eaton Intelligent Power® Manager – User’s Guide / AL - v1.30 Page 1/125 www.eaton.com Table of Contents 1 Introduction .................................................................................................................... 8 2 Installation ...................................................................................................................... 9 2.1 Installation Prerequisites ................................................................................................................... 9 ® 2.1.1 On the System Hosting « Intelligent Power Manager » ............................................................... 9 2.1.2 On the System that Displays Web-based Graphical User Interface.............................................. 9 2.2 Quick Start & Installation .................................................................................................................. 10 2.3 Installation Result .............................................................................................................................. 14 2.4 Uninstalling the Product ................................................................................................................... 14 2.5 Upgrading the Product ...................................................................................................................... 14 2.6 Installation / Uninstallation from command line ............................................................................. 15 3 Configuration ................................................................................................................
    [Show full text]
  • LBT PROJECT 2 X 8,4M OPTICAL TELESCOPE UPS and Thermal Monitor Client System Configuration
    LBT PROJECT 2x8,4m TELESCOPE Doc.No. : 228s010 Issue : b Date : 10-May-2012 LBT PROJECT 2 X 8,4m OPTICAL TELESCOPE UPS and Thermal Monitor Client System Configuration LBT PROJECT Doc.No : 228s010 Issue : b Page 2 UPS Client System Configuration Date : 10-May-12 Signature Date Prepared Dan Cox 31-Oct-11 Reviewed Norm Cushing 05-Jan-12 Approved Joar Brynnel 05-Jan-12 LBT PROJECT Doc.No : 228s010 Issue : b Page 3 UPS Client System Configuration Date : 10-May-12 1. Revision History Issue Date Changes Responsible a 31-Oct-11 First draft Dan Cox b 10-May-12 References to “red button” replaced with Dan Cox “yellow button”; section added for testing shutdown applications. LBT PROJECT Doc.No : 228s010 Issue : b Page 4 UPS Client System Configuration Date : 10-May-12 2. Table Of Contents 1.Revision History...............................................................................................................3 2.Table Of Contents.............................................................................................................4 4.List Of Abbreviations........................................................................................................5 5.About this document.........................................................................................................6 1.1. Purpose......................................................................................................................6 1.2. Reference Documents...............................................................................................6
    [Show full text]
  • Fedora 7 Release Notes
    Fedora 7 Release Notes Fedora Documentation Project Copyright © 2007 Red Hat, Inc. and Others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. All other trademarks are the property of their respective owners. Abstract 1. Welcome to Fedora ................................................................................................................ 3 2. Release Highlights .................................................................................................................. 4 2.1. Fedora Tour ................................................................................................................. 4 2.2.
    [Show full text]
  • Owner's Manual
    Owner’s Manual Console Server Management Switch Models: B096-016 / B096-032 / B096-048 Console Server with PowerAlert Model: B092-016 Console Server Models: B095-004-1E / B095-003-1E-M / B094-008-2E-M-F / B094-008-2E-V PROTECT YOUR INVESTMENT! Register your product for quicker service and ultimate peace of mind. You could also win an ISOBAR6ULTRA surge protector—a $50 value! www.tripplite.com/warranty 1111 W. 35th Street, Chicago, IL 60609 USA • www.tripplite.com/support Copyright © 2014 Tripp Lite. All rights reserved. All trademarks are the property of their respective owners. 1 FCC Information, Class A This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. The user must use shielded cables and connectors with this equipment.
    [Show full text]
  • Enhanced Console Server
    Enhanced Console Server ECS0016 FCC Compliance Statement This equipment has been tested and found to comply with the limits for a Class B digital de- vice, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: • Reorient or relocate the receiving antenna. • Increase the separation between the equipment and receiver. • Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. • Consult the dealer or an experienced radio/TV technician for help. Use of Trademarks, Registered Trademarks, and other Protected Names and Symbols This manual may make reference to trademarks, registered trademarks, and other protected names and/or symbols of third-party companies not related in any way to StarTech.com. Where they occur these references are for illustrative purposes only and do not represent an endorse- ment of a product or service by StarTech.com, or an endorsement of the product(s) to which this manual applies by the third-party company in question. Regardless of any direct acknowl- edgement elsewhere in the body of this document, StarTech.com hereby acknowledges that all trademarks, registered trademarks, service marks, and other protected names and/or symbols contained in this manual and related documents are the property of their respective holders.
    [Show full text]
  • Cisco Unified Communications Manager XML Developers Guide, Release 9.0(1) Copyright © 2006–2012 Cisco Systems, Inc
    Cisco Unified Communications Manager XML Developers Guide Release 9.0(1) Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number: OL-27400-01 NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Opengear CLI and Scripting Reference.Pdf
    CLI and Scripting Reference ACM7000 Remote Site Gateway ACM7000-L Resilience Gateway IM7200 Infrastructure Manager CM7100 Console Servers Version 2.0 2019-07-23 1 Table of Contents Safety Please take care to follow the safety precautions below when installing and operating the console server: - Do not remove the metal covers. There are no operator serviceable components inside. Opening or removing the cover may expose you to dangerous voltage which may cause fire or electric shock. Refer all service to Opengear qualified personnel. - To avoid electric shock the power cord protective grounding conductor must be connected through to ground. - Always pull on the plug, not the cable, when disconnecting the power cord from the socket. Do not connect or disconnect the console server during an electrical storm. Use a surge suppressor or UPS to protect the equipment from transients. FCC Warning Statement This device complies with Part 15 of the FCC rules. Operation of this device is subject to the following conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference that may cause undesired operation. Proper back-up systems and necessary safety devices should be utilized to protect against injury, death or property damage due to system failure. Such protection is the responsibility of the user. This console server device is not approved for use as a life-support or medical system. Any changes or modifications made to this console server device without the explicit approval or consent of Opengear will void Opengear of any liability or responsibility of injury or loss caused by any malfunction.
    [Show full text]
  • APC Tracker APC UPS Software for Mac OS X / Xserve
    APC Tracker APC UPS Software for Mac OS X / Xserve Connecting to a USB APC Tracker is the intelligent software for connecting to equipped UPS uninterruptible power supplies (UPS) for the Mac platform. Along with the standard protection a UPS provides USB HID standard compliant UPS devices from against power-failures and fluctuations, an active UPS different vendors are compatible with APC device monitoring system is useful and necessary to enable Tracker. This includes the APC Back-UPS and a proper server shut down in the event of a long-term Smart-UPS series models that are equipped with power-outage. A monitoring system is also necessary to a USB connector. diagnose the problem and to receive an automatic notification in the event of a failure. equinux APC Tracker provides Connecting to an APC UPS optimal support for market leading APCTM UPS systems over the network for the Mac platform. APC Tracker is able to connect to the UPS in the Restarting your server after a cold following ways: • Downtime prevention: shutdown can consume a lot of time due to file system APC SNMP Card checks, data base consistency checks, etc. APC Tracker All APC models that have a smart slot can be gives you the time to properly shut down your server in equipped with an APC Network Management the event of a longer power failure and thus prevents Card. This card supplies an ethernet jack to problems restarting the system. connect it to the local network. In regular time periods and in failure situations, the card sends • Easy to use: APC Tracker runs faceless in the status messages to the connected servers.
    [Show full text]
  • Packager Guide
    NUT Packager and Integrators Guide i NUT Packager and Integrators Guide NUT Packager and Integrators Guide ii REVISION HISTORY NUMBER DATE DESCRIPTION NAME 2.7.4 2016-03-09 Current release of Network UPS Tools (NUT). 2.6.0 2011-01-14 First release of AsciiDoc documentation for Network UPS Tools (NUT). NUT Packager and Integrators Guide iii Contents 1 Introduction 1 2 Packagers involved 2 3 Possible use cases 3 4 Optimised packaging proposal 3 4.1 Overview of the package tree.............................................3 4.2 Detailed view of the package tree...........................................4 4.2.1 nut......................................................4 4.2.2 libupsclient1.................................................4 4.2.3 libupsclient1-dev...............................................5 4.2.4 nut-cgi....................................................5 4.2.5 nut-powerman-pdu..............................................5 4.2.6 nut-snmp...................................................5 4.2.7 nut-xml....................................................5 4.2.8 nut-clients...................................................6 4.2.9 python-pynut.................................................6 4.2.10 python-nut-gui................................................6 4.2.11 nut-doc....................................................6 NUT Packager and Integrators Guide iv Abstract The aim of this document is to describe the best way to package the Network UPS Tools, and the best practices across the various packaging implementation of NUT. So as to these can be spread on all supported platforms as a standard, and as a foundation block to build upon. NUT Packager and Integrators Guide 1 / 7 Warning this is a Work In Progress document. 1 Introduction Packaging is a final aim for software. It eases and completes the software integration into an OS, and allows users to have an easy software installation and support out of the box.
    [Show full text]
  • NUT - Network UPS Tools NUT - Network UPS Tools
    2021/09/26 07:37 1/7 NUT - Network UPS Tools NUT - Network UPS Tools This guide explains how to install NUT on a client / server architecture with several clients accessing the UPS. NUT Server Installation 1. Installing the nut package, should add the nut user and group. If it doesn’t, you have to add those manually. sudo apt-get install nut 2. Make the USB-Device accessible by NUT lsusb output: Bus 001 Device 002: ID 051d:0003 American Power Conversion UPS 3. Create new udev rule sudo vim /etc/udev/rules.d/90-nut-ups.rules ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="051d", ATTR{idProduct}=="0003", MODE="0660", GROUP="nut" 4. Activate udevadm control --reload-rules udevadm trigger ups.conf [ups] driver = usbhid-ups port = auto pollonly desc = "ups" The label in the square brackets can be anything. It identifies the UPS to upsd and upsmon. Find your UPS model on the NUT hardware compatibility list and substitute the corresponding driver for usbhid- ups above. If your UPS isn’t listed, find similar ones. They probably use the same driver. If you have a USB-based UPS, you can leave the port as auto; it’s ignored. Note: if you are connecting a Synology NAS to your NUT setup, then the label in square brackets must be named ups. Bernard's Wiki - https://wiki.condrau.com/ 2021/09/26 07:37 2/7 NUT - Network UPS Tools Make sure that nut properly detects the UPS: # upsdrvctl start You should see something like the following: Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) Using subdriver: APC HID 0.92 Now, we need to configure upsd and upsmon.
    [Show full text]
  • Apc Ups User Guide
    Apc Ups User Guide Torrance remains tutti after Bartlet liquidates midnight or aggresses any teffs. Frustrate Martino always frills his crosshatch if Dimitrios is impassioned or titivated comprehensively. Unabridged and unsymmetrical Seymour roughen so far-forth that Wolfram pocket his lascar. After having problems as two common in some parameters configuration parameter insures that under those elements of user guide ups apc ups is on the ups systems as they will switch would make it is If your critical electronics from apc ups to. Elevated temperature reduces longevity. When replacing batteries, use the same number and type ofsealed lead acid batteries as were originally contained in your UPS. Also, the information that is inserted in your halt script varies from system to system. This is the first year they show these products at the SPS. HDMI Streamer Pvi Vecaster Pro. All the standard apcupsd options can be used on the Windows version. So easy, even a baby could do it! Depending on the setting of your BIOS, it may prevent your computer from restarting when the power returns. Endpoint detection and response uses AI to help protect against nearly every type of attack aimed at endpoints in real time and can even roll back infected. We appreciate your patience and understanding. Yesterday we had a major snowstorm. Actual runtime may vary depending on the operating environment of the UPS, the power factors of the protected equipment and the condition of the UPS batteries. Designed with predictive failure notification a line-interactive APC UPS conducts. Conference scheduling, setting up the profile and address book.
    [Show full text]