Learn how to do the APC UPS initial IP address configuration on the network. APC UPS - IP address.
![]()
Welcome to LinuxQuestions.org, a friendly and active Linux Community.You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Today!Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.Are you new to LinuxQuestions.org?
Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,.Having a problem logging in? Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on GuideThis guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.
They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.to receive this Complete Guide absolutely free. Code: UPSNAME smartupsUPSCABLE smart (note that putting in the actual cable number doesn't work - unrecognized cable)UPSTYPE apcsmartDEVICE /dev/ttyS0 (this is just a guess, I've tried S1 as well)LOCKFILE /var/lockONBATTERYDELAY 6BATTERYLEVEL 5MINUTES 3TIMEOUT 0ANNOY 300ANNOYDELAY 60NOLOGON disableKILLDELAY 0NISIP 127.0.0.1NISPORT 3551EVENTSFILE /var/log/apcupsd.eventsEVENTSFILEMAX 10UPSCLASS standaloneUPSMODE disableSTATTIME 0STATFILE /var/log/apcupsd.statusLOGSTATS offDATATIME 0But there is a problem because when I run apcupsd I get a fatal error. Yes, I've read the apcupsd manual and googled extensively, but I can't seem to get the apcupsd to recognise my cable. I was hoping someone else had experienced the issue and managed to solve it, or at least understood the inner workings of the apcupsd program better than I and would know what options I could try to get it working.ETA: I don't even know how to tell WHICH serial port the apcupsd thinks the UPS is plugged into, since using either /dev/ttyS0 and /dev/ttyS1 (and setserial output) produce identical results. When I try to communicate with either port using Minicom, nothing happens. Hi Michael,You're correct; it turns out my model of new APC UPS does in fact use a Microlink protocol, which my old server and old apcupsd cannot communicate.
Mystery solved as to WHY I can't get them to talk, now the question as to how I can fix it.This very interesting thread: indicates that after 3 years APC agreed it was unwise to alienate all its non-Microsoft users, and created a second protocol (MODBUS) which they shared with apcupsd developers. Apparently there is a new version of apcupsd that uses the new protocol. This is likely why the notice came off their homepage?Is there a way to tell if my UPS supports MODBUS and how I can get the new apcupsd installed on my old Linux (might not be compatible?). Code: UPSNAME APCUPSUPSCABLE 940-0625AUPSTYPE modbusDEVICE /dev/ttyS1LOCKFILE /var/lockSCRIPTDIR /etc/apcupsdPWRFAILDIR /etc/apcupsdNOLOGINDIR /etcONBATTERYDELAY 6BATTERYLEVEL 5MINUTES 3TIMEOUT 0ANNOY 300ANNOYDELAY 60NOLOGON disableKILLDELAY 0NETSERVER onNISIP 0.0.0.0NISPORT 3551EVENTSFILE /var/log/apcupsd.eventsEVENTSFILEMAX 10UPSCLASS standaloneUPSMODE disableSTATTIME 0STATFILE /var/log/apcupsd.statusLOGSTATS offDATATIME 0I checked in /var/log/apcupsd.events and saw the following:'Communications with UPS lost' (repeated about every 4-6 minutes)'apcserver: cannot bind port 3551.
![]()
ERR=Address already in use' (every hour. I used netstat to verify that nothing is using 3551)Again, I'm not sure how to tell which serial port it even thinks it's connected to. When I run apcupsd, nothing happens, but it doesn't seem to actually run either. Thanks for any help.
![]()
Sorry - I edited my previous post to include the information from apcupsd.events, but now that I refresh the page, the edits are gone!Anyway - I do in fact see apcupsd running in ps. I restarted it a few times for good measure./var/log/apcupsd.events reports'Communications with UPS lost.' (every few minutes)'apcserver: Cannot bind port 3551. ERR=Address already in use' (once an hour. I verified with netstat that nothing is running on 3551).I have physically gone into the server room and plugged the UPS into the other serial port on the server - didn't help. Hi sniff,Sadly, no. This server is.
If something is plugged into a USB port I am not guaranteed that it will boot up successfully after a power outage. (Backups are done over the network now.) My last few (pre-MODBUS) APC UPSes all connected via serial cable and when I bought this one I made sure it had serial too.Now, if you could get your Smart-UPS connected via serial, I would be very interested in how you did itMichaelk, yep, I have tried those settings from the manual.
I thought it would work better with my actual cable listed but alas, nothing seems to work. As of today I still get 'Communications with UPS lost' every 10 minutes in my apcupsd.events file.
Issue:Serial Terminal Connection Parameters for all NetBotz AppliancesProduct Line:NetBotzEnvironment:Versions as described belowterminal emulationCause:Terminal emulation (ie. Hyper-Terminal) configuration for communications with NetBotz appliances.Resolution:Terminal emulation is often used for initial IP configuration on NetBotz appliances.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |