Difference between revisions of "Uninterruptable Power Supply"

From SME Server
Jump to navigationJump to search
m (add language bar)
(Many changes, basic content the same, mostly formating and English. Some one else will have to do the German. B-))
Line 1: Line 1:
 
{{Languages}}
 
{{Languages}}
 
===Nut UPS – Uninterruptable Power Supply===
 
 
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)=
 +
Most USB connected UPS's will work with the default settings. If using a USB connection just enable nut as follows:
  
====Default Configuration====
 
Most '''USB''' UPS devices will work with the default settings. If using a USB device just enable nut as follows.
 
 
  config setprop nut status enabled
 
  config setprop nut status enabled
 
  signal-event post-upgrade
 
  signal-event post-upgrade
 
  signal-event reboot
 
  signal-event reboot
If your USB UPS does not work properly OR you have a ''serial device'' then follow the optional instructions below.
 
  
===Optional Configuration Options===
+
If your USB UPS does not work properly OR you have a '''serial device''' then follow the Configuration Options below.
 +
 
 +
=Configuration Options=
 +
 
 +
Not all UPS's are supported by USB or the newhidups driver, refer to:  http://www.networkupstools.org/compat/stable.html to find the configuration details for your model of UPS.
  
Not all UPS's are supported by USB or the newhidups driver, refer to the link below. <br />
+
For example Model bcmxcp_usb is for some Powerware units connected via USB or Model genericups for other Powerware units that only work on serial.
eg. config setprop nut Model bcmxcp_usb is for some Powerware units on USB. <br />
 
Or config setprop nut Model genericups is for other Powerware units that only work on serial. <br />
 
  
Find your Model here http://www.networkupstools.org/compat/stable.html <br />
+
==Serial Connection==
Note: "Type" is only used if your model is genericups <br />
 
Caution: ALWAYS use the cable supplied with the UPS.  Standard serial cables won't work with a serial UPS and have even been known to cause damage to the UPS.
 
  
 +
'''Caution:''' ALWAYS use the serial cable supplied with the UPS.  Standard serial cables won't work with a serial UPS and have been known to cause damage to the UPS.
  
These are basic '''example''' settings.  Replace the properties with the appropriate settings for your UPS.
+
The following are basic '''example''' settings.  Replace the properties with the appropriate settings for your UPS:
  config setprop nut Model apcsmart
+
  config setprop nut Model genericups
 
  config setprop nut Device /dev/ttyS0
 
  config setprop nut Device /dev/ttyS0
 
  config setprop nut Type 7
 
  config setprop nut Type 7
 
  config setprop nut status enabled  
 
  config setprop nut status enabled  
  
check
+
Note: "Type" is only used if your model is Model genericups.
 +
 
 +
Check:
 
  config show nut
 
  config show nut
  
apply changes and restart server
+
Apply changes and restart server:
  signal-event post-upgrade ; signal-event reboot  
+
  signal-event post-upgrade
 +
signal-event reboot  
  
alternatively
+
Alternatively, with NUT not running or a server reboot:
 
  expand-template /etc/sysconfig/ups
 
  expand-template /etc/sysconfig/ups
 
  expand-template /etc/ups/*
 
  expand-template /etc/ups/*
 
  /etc/rc7.d/S38nut start
 
  /etc/rc7.d/S38nut start
  
confirm server is communicating with UPS
+
Confirm server is communicating with UPS:
 
  upsc UPS@localhost
 
  upsc UPS@localhost
  
Emails are sent to admin whenever a UPS event occurs
+
For serial connected APC Smart UPS's there is a step by step How To: [http://wiki.contribs.org/APC_Serial_UPS APC_Serial_UPS]. This also shows how to configure the udev system instead of using a direct reference to the serial port.
  
====Configuring as a slave====
+
Whenever a UPS event occurs Emails are sent to the admin account.
where 192.168.33.11 is your UPS master, the computer that will communicate with the UPS
 
The hostname of the server may also work.  
 
  
set configuration values
+
==Configuring as a slave==
 +
Set configuration values:
 
  config setprop nut SlaveUPS UPS@192.168.33.11
 
  config setprop nut SlaveUPS UPS@192.168.33.11
 
  config setprop nut Master no
 
  config setprop nut Master no
  
apply changes and restart server
+
Where 192.168.33.11 is your UPS master, that is the computer that is in direct communication with the UPS. The hostname of that computer may also work.
signal-event post-upgrade ; signal-event reboot
 
  
confirm server is communicating with master
+
Apply changes and restart server:
 +
signal-event post-upgrade
 +
signal-event reboot
 +
 
 +
Confirm server is communicating with master:
 
  upsc UPS@192.168.33.11
 
  upsc UPS@192.168.33.11
  
====Conecting multiple UPS's====
+
==Conecting multiple UPS's==
to be added
+
To be added http://bugs.contribs.org/show_bug.cgi?id=629
http://bugs.contribs.org/show_bug.cgi?id=629
 
  
 
+
=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.
  
For information on configuration parameters
+
For information on configuration parameters:
 
  man ups.conf
 
  man ups.conf
 
  man upsd.conf
 
  man upsd.conf
Line 77: Line 78:
 
  man upssched.conf
 
  man upssched.conf
  
For general information  
+
For general information:
 
  man upsd
 
  man upsd
 
  man nutupsdrv
 
  man nutupsdrv
 
 
 
  
 
<noinclude>[[Category:Howto]]</noinclude>
 
<noinclude>[[Category:Howto]]</noinclude>

Revision as of 12:31, 5 May 2008


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/

Default Configuration (USB)

Most USB connected UPS's will work with the default settings. If using a USB connection just enable nut as follows:

config setprop nut status enabled
signal-event post-upgrade
signal-event reboot

If your USB UPS does not work properly OR you have a serial device then follow the Configuration Options below.

Configuration Options

Not all UPS's are supported by USB or the newhidups driver, refer to: http://www.networkupstools.org/compat/stable.html to find the configuration details for your model of UPS.

For example Model bcmxcp_usb is for some Powerware units connected via USB or Model genericups for other Powerware units that only work on serial.

Serial Connection

Caution: ALWAYS use the serial cable supplied with the UPS. Standard serial cables won't work with a serial UPS and have been known to cause damage to the UPS.

The following are basic example settings. Replace the properties with the appropriate settings for your UPS:

config setprop nut Model genericups 
config setprop nut Device /dev/ttyS0
config setprop nut Type 7
config setprop nut status enabled 

Note: "Type" is only used if your model is Model genericups.

Check:

config show nut

Apply changes and restart server:

signal-event post-upgrade
signal-event reboot 

Alternatively, with NUT not running or a server reboot:

expand-template /etc/sysconfig/ups
expand-template /etc/ups/*
/etc/rc7.d/S38nut start

Confirm server is communicating with UPS:

upsc UPS@localhost

For serial connected APC Smart UPS's there is a step by step How To: APC_Serial_UPS. This also shows how to configure the udev system instead of using a direct reference to the serial port.

Whenever a UPS event occurs Emails are sent to the admin account.

Configuring as a slave

Set configuration values:

config setprop nut SlaveUPS UPS@192.168.33.11
config setprop nut Master no

Where 192.168.33.11 is your UPS master, that is the computer that is in direct communication with the UPS. The hostname of that computer may also work.

Apply changes and restart server:

signal-event post-upgrade
signal-event reboot 

Confirm server is communicating with master:

upsc UPS@192.168.33.11

Conecting multiple UPS's

To be added http://bugs.contribs.org/show_bug.cgi?id=629

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.

For information on configuration parameters:

man ups.conf
man upsd.conf
man upsd.users
man upsmon.conf
man upssched.conf

For general information:

man upsd
man nutupsdrv