689
edits
Changes
From SME Server
Jump to navigationJump to searchUninterruptable Power Supply (view source)
Revision as of 11:54, 18 January 2010
, 11:54, 18 January 2010Corrected headings for inclusion in Technical Manual
{{Languages}}
{{Languages}}
==Introduction==
==Uninterruptable Power Supply==
{{Level|Advanced}}
{{Level|Advanced}}
===Introduction===
The primary goal of the Network UPS Tools (NUT) project is to provide reliable monitoring of UPS hardware and ensure safe shutdowns of the systems which are connected.
The primary goal of the Network UPS Tools (NUT) project is to provide reliable monitoring of UPS hardware and ensure safe shutdowns of the systems which are connected.
The default configuration of NUT, will keep your connected systems operational until a critical battery state is reached (ie battery is nearing exhaustion) and then power down your server/equipment in a controlled fashion. See http://www.networkupstools.org/
The default configuration of NUT, will keep your connected systems operational until a critical battery state is reached (ie battery is nearing exhaustion) and then power down your server/equipment in a controlled fashion. See http://www.networkupstools.org/
==Default Configuration (USB)==
===Default Configuration (USB)===
The default configuration in SME Server for 'NUT' is set by the configuration database properties
The default configuration in SME Server for 'NUT' is set by the configuration database properties
Model = usbhid-ups
Model = usbhid-ups
If your USB UPS does not work properly OR you have a '''serial device''' then follow the Configuration Options below as required.
If your USB UPS does not work properly OR you have a '''serial device''' then follow the Configuration Options below as required.
==Configuration Options==
===Configuration Options===
Not all UPS's are supported by USB or the usbhid-ups driver. However NUT supports many UPS's and can be configured under SME Server easily.
Not all UPS's are supported by USB or the usbhid-ups driver. However NUT supports many UPS's and can be configured under SME Server easily.
===Serial Connection===
====Serial Connection====
<ol></li><li>Find the configuration details for your model of UPS. Refer to: http://www.networkupstools.org/compat/stable.html and make note of the driver name and upstype number (if any) in the third column.
<ol></li><li>Find the configuration details for your model of UPS. Refer to: http://www.networkupstools.org/compat/stable.html and make note of the driver name and upstype number (if any) in the third column.
</li></ol>
</li></ol>
===Configuring as a slave===
====Configuring as a slave====
Set configuration values:
Set configuration values:
config setprop nut SlaveUPS UPS@192.168.33.11
config setprop nut SlaveUPS UPS@192.168.33.11
upsc UPS@192.168.33.11
upsc UPS@192.168.33.11
===Conecting multiple UPS's===
====Conecting multiple UPS's====
To be added http://bugs.contribs.org/show_bug.cgi?id=629
To be added http://bugs.contribs.org/show_bug.cgi?id=629
==UPS Variables and Commands==
===UPS Variables and Commands===
In some cases you may wish to modify variables on the actual UPS such as the Low Charge/LOWBATTERY setting. This requires the use of the '''upsrw''' command and UPS administrative privileges.
In some cases you may wish to modify variables on the actual UPS such as the Low Charge/LOWBATTERY setting. This requires the use of the '''upsrw''' command and UPS administrative privileges.
{{Warning box|In general, the UPS data should be left protected and changes to it or issuing of commands well thought out. If you wish to make data changes or issue commands then the administrative privileges can be enabled as below and should then be disabled.}}
{{Warning box|In general, the UPS data should be left protected and changes to it or issuing of commands well thought out. If you wish to make data changes or issue commands then the administrative privileges can be enabled as below and should then be disabled.}}
===UPS Administrative Privileges===
====UPS Administrative Privileges====
In order to be able to use '''upsrw''' and '''upscmd''' it is necessary to have a suitable additional user defined in the '''upsd.users''' configuration file.
In order to be able to use '''upsrw''' and '''upscmd''' it is necessary to have a suitable additional user defined in the '''upsd.users''' configuration file.
}}
}}
===Setting UPS Variables===
====Setting UPS Variables====
In order to set UPS variables it is necessary to have enabled a user with administrative privileges as above first.
In order to set UPS variables it is necessary to have enabled a user with administrative privileges as above first.
- Upsrw examples: [http://opensource.mgeups.com/howto.htm MGE UPS Howto]
- Upsrw examples: [http://opensource.mgeups.com/howto.htm MGE UPS Howto]
===Issuing UPS Commands===
====Issuing UPS Commands====
In order to issue UPS commands it is necessary to have enabled a user with administrative privileges as above first.
In order to issue UPS commands it is necessary to have enabled a user with administrative privileges as above first.
Issuing commands could shutdown your server unexpectedly!}}
Issuing commands could shutdown your server unexpectedly!}}
==Scheduling Events - Shutdown Time Delay==
===Scheduling Events - Shutdown Time Delay===
By default NUT will issue a shutdown command as soon as it receives a low battery event from the UPS. There may be instances and installation configurations that require a shutdown sooner, or other events with timed or schedules outcomes. See the '''man''' pages etc for further info and example situations.
By default NUT will issue a shutdown command as soon as it receives a low battery event from the UPS. There may be instances and installation configurations that require a shutdown sooner, or other events with timed or schedules outcomes. See the '''man''' pages etc for further info and example situations.
signal-event reboot
signal-event reboot
==Aditional Information==
===Aditional Information===
There are template fragments in /etc/e-smith/templates/etc/ups that control the config files located in /etc/ups. The default settings should be OK for most situations.
There are template fragments in /etc/e-smith/templates/etc/ups that control the config files located in /etc/ups. The default settings should be OK for most situations.
