APC SU1400XLT User Manual download pdf (Page 66)

SNMP Trap Catching

apcupsd-3.11.14 introduces support for SNMP trap catching. Previous versions polled the UPS status

once per minute, leading to significant delays before UPS state changes were recognized. With SNMP

trap handling, apcupsd monitors the SNMP trap port and will re-poll the UPS whenever a trap is received.

This happens, for example, when the UPS switches on or off battery.

In order for this feature to work, you must configure your UPS to deliver traps to the server running

apcupsd. This is generally done by connecting to your SNMP card via a web browser or telnet connection.

You will need to enter your server's IP address as a trap receiver and make sure trap delivery is enabled.

Trap catching can lead to problems if you are already running another SNMP trap daemon on your server.

Only one daemon can listen to the trap port, so whichever one is started first will succeed and the others

will fail. Apcupsd will fall back to polling behavior if it is unable to open the trap port. You can also forcibly

disable trap catching by appending _NOTRAP to your vendor string in the apcupsd.conf DEVICE

directive.

Known Problems

Currently (as of 3.10.0) the code to power off the UPS needs special configuration. The killpower

command for SNMP UPSes can not be issued during shutdown as typically at some time during shutdown

operations the network stack is stopped. To overcome this problem it is needed to modify the

/etc/rc.d/apcupsd system control script to tell apcupsd to issue the power down command (killpower) to

the UPS immediately before apcupsd initiates the system shutdown. For this reason it is paramount to set

your UPS grace time to a value greater than 120 seconds to allow for clean shutdown operations before

the UPS removes the power from its plugs. To enable correct shutdown operation during powerdown do

the following:

• Connect to your Web/SNMP card using your favorite web browser, go to the UPS configuration

menu and change the "Shutdown Delay" parameter to 180 seconds or more, depending on how

much time your system shutdown requires to umount all the filesystems.

• Option 1 (non-windows) Edit the server halt script. Relocate the ups_kill_power() function higher in

the shutdown sequence, primarily before the command to bring down the ethernet service. This is

the preferred method for shutting down the UPS. The UPS will power down after the prescribed

"Shut Down Delay" time (in seconds) has elapsed.

• Option 2 Change /etc/rc.d/apcupsd script adding the --kill-on-powerfail to the apcupsd

invocation. This method is not preferred because the UPS is commanded to power down without

delay. This creates the potential for UPS powering down before the server calling for UPS power

down completes its shutdown. However, in the case of Microsoft Windows OS, this is the only

method available for powering down the UPS.

• Restart your apcupsd

With this setup your UPS operations should be safe.

apcupsd System Logging

The apcupsd philosophy is that all logging should be done through the syslog facility (see: 'man

syslog') This is now implemented with the exceptions that STATUS logging, for compatibility with prior

versions is still done to a file, and EVENTS logging can be directed to a temporary file so that it can be

reported by the network information server.

Logging Types

apcupsd splits its logging into four separate types called:

1. DEBUG

2. DATA

3. STATUS

1 2 ... 61 62 63 64 65 66 67 68 69 70 71 ... 114 115

Comments to this Manuals

No comments

APC SU1400XLT User Manual Page 66

Comments to this Manuals