APC SU1400XLT User Manual Page 34

  • Download
  • Add to my manuals
  • Print
  • Page
    / 115
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 33
server decides to shutdown and the time it no longer responds. Your slave must poll during this interval.
Any client run using the Net driver will shutdown when its own timers expire or when the NIS server shuts
down, whichever occurs first. This means that if you want the slave to shutdown before the server, you
need only set BATTERYLEVEL, MINUTES or TIMEOUT on the client for a faster shutdown than the values
defined on the NIS server. This can often be useful if the slave is less important than the master and you
wish to reduce battery power consumption so that the master can remain up longer during a power
outage.
NIS clients work principally by reading the STATFLAG record that is sent by the NIS server (present in the
output of apcaccess). The low 16 bits are the standard APC status flag, and the upper 16 bits represent
the internal state of apcupsd, so the slave can see when the power fails and know when to shutdown.
It would be possible to have a client also work as a server, but that would increase the delay of
information getting from the UPS to the secondary client.
Differences between NIS Client/Server and the old (now removed) Master/Slave modes
The difference between the NIS mode and the removed master/slave mode is that the NIS server has no
explicit knowledge of the slaves. The NIS server makes its information available via the net (NIS), and the
NIS slaves read it. When the NIS server is going to shutdown, it makes the information available to any
NIS slave that polls it, but the NIS server does not explicitly call each NIS slave as is the case in the
Master/Slave networking described several sections above.
Think of the difference as push (Master/Slave) vs. pull (NIS-based). In the case of M/S, the master makes
all the shutdown decisions and notifies the slaves when they are to shut down or when some other
interesting event happens. The slaves just do whatever the master says, whenever the master says to. On
the other hand, with the NIS-based network config you basically "publish" the UPS status from one server
and then your clients view that status and make their own decisions.
PowerChute Network Shutdown Driver (PCNET)
As of 3.14, Apcupsd supports the PowerChute Network Shutdown protocol. This is an alternative to
SNMP for use with APC's AP9617 family of network smartslot modules. Note that the older AP9606
modules do not support PCNET.
To enable PCNET support, configure with the --enable-pcnet flag. This is typically enabled by
default.
The required apcupsd.conf settings are straightforward:
## apcupsd.conf v1.1 ##
UPSCABLE ether
UPSTYPE pcnet
LOCKFILE /var/lock
DEVICE ipaddr:user:passphrase
UPSCLASS standalone
UPSMODE disable
The DEVICE setting specifies the IP address of the UPS as well as the username and authentication
passphrase to use. Note that the username and passphrase are not the Web/SNMP login credentials.
They are separate settings. The default username on a new card is "apc" and the default passphrase is
"admin user phrase". To change the passphrase, log in to the Web UI and go to the UPS tab, then to
PowerChute -> Configuration. (This assumes firmware v3.3.1. Other versions may place the setting
elsewhere.) The password must be a minimum of 15 characters long. The web UI will silently ignore
shorter passwords and does not give an error message. There is no apparent way to change the
username.
Note that you may leave DEVICE blank and Apcupsd will accept information from any PCNET UPS on
the network, however it will be very insecure since an attacker could easily send packets crafted to
cause your server to shut down. Using the ipaddr, user, and passphrase will prevent this
Page view 33
1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 114 115

Comments to this Manuals

No comments