Filter
Top Products
your UPS model and cable type, and the serial port that you have attached
the UPS to. People have used both /dev/ttya and /dev/ttyb with no
problems. You should be sure that logins are disabled on the port you are
going to use, otherwise you will not be able to communicate with the UPS.
If you are not sure that logins are disabled for the port, run the ’admintool’
program as root, and disable the port. The ’admintool’ program is a
GUI administration program, and required that you are running CDE,
OpenWindows, or another XWindows program such as KDE.
Solaris probes the serial ports during boot, and during this process, it toggles
some handshaking lines used by dumb UPSes. As a result, particularly for
simple signalling “dumb” UPSes it seems to kick it into a mode that makes
the UPS think it’s either in a calibration run, or some self-test mode. Since
at this point we are really not communicating with the UPS, it’s pretty
hard to tell what happened. But it’s easy to prevent this, and you should.
Disconnect the UPS, and boot the system. When you get to a login prompt,
log in as root. Type the following command:
eeprom com1-noprobe=true
or
eeprom com2-noprobe=true
depending on which com port your UPS is attached to. Then sync and
shutdown the system normally, reattach the UPS, and reboot. This should
solve the problem. However, we have some reports that recent versions of
Solaris (7 & 8) appear to have removed this eeprom option and there seems
to be no way to suppress the serial port probing during boot.
At this point, you should have a complete installation. The daemon will
load automatically at the next boot. Watch for any error messages during
boot, and check the event logs in /etc/apcupsd. If everything looks OK,
you can try testing the package by removing power from the UPS. NOTE! if
you have a voltage-signalling UPS, please run the first power tests with your
computer plugged into the wall rather than into the UPS. This is because
dumb serial-port UPSes have a tendency to power off if your configuration
or cable are not correct.
As a user, your input is very helpful in solving problems with the package,
and providing suggestions and future directions for the development of the
47