Network UPS Tools User Manual
Network UPS Tools User Manual
Network UPS Tools User Manual
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Network</strong> <strong>UPS</strong> <strong>Tools</strong> <strong>User</strong> <strong>Manual</strong> 21 / 84<br />
6.2 Basic configuration<br />
This chapter describe the base configuration to establish communication with the device.<br />
This will be sufficient for PDU. But for <strong>UPS</strong> and SCD, you will also need to configure automatic shutdowns for low battery<br />
events.<br />
6.2.1 Driver configuration<br />
Create one section per <strong>UPS</strong> in /usr/local/ups/etc/ups.conf<br />
To find out which driver to use, check the Hardware Compatibility List, or data/driver.list.<br />
Once you have picked a driver, create a section for your <strong>UPS</strong> in ups.conf. You must supply values for "driver" and "port".<br />
Some drivers may require other flags or settings. The "desc" value is optional, but is recommended to provide a better description<br />
of what your <strong>UPS</strong> is supporting.<br />
A typical device without any extra settings looks like this:<br />
[mydevice]<br />
driver = mydriver<br />
port = /dev/ttyS1<br />
desc = "Workstation"<br />
Note<br />
USB drivers (usbhid-ups, bcmxcp_usb, tripplite_usb, blazer_usb and richcomm_usb) are special cases and ignore the port<br />
value. You must still set this value, but it does not matter what you set it to; a common and good practice is to set port to auto,<br />
but you can put whatever you like. If you only own one UBS <strong>UPS</strong>, the driver will find it automatically. If you own more than one,<br />
refer to the driver’s manual page for more information on matching a specific device.<br />
References: ups.conf(5), nutupsdrv(8), bcmxcp_usb(8), blazer(8), richcomm_usb(8), tripplite_usb(8), usbhid-ups(8)<br />
6.2.2 Starting the driver(s)<br />
Start the driver(s) for your hardware:<br />
/usr/local/ups/sbin/upsdrvctl start<br />
Make sure the driver doesn’t report any errors. It should show a few details about the hardware and then enter the background.<br />
You should get back to the command prompt a few seconds later. For reference, a successful start of the usbhid-ups driver<br />
looks like this:<br />
# /usr/local/ups/sbin/upsdrvctl start<br />
<strong>Network</strong> <strong>UPS</strong> <strong>Tools</strong> - Generic HID driver 0.34 (2.4.1)<br />
USB communication driver 0.31<br />
Using subdriver: MGE HID 1.12<br />
Detected EATON - Ellipse MAX 1100 [ADKK22008]
Change language