I have exactly same problem with Eaton UPS Companion 1.03 and Eaton Ellipse ECO. "Communication with the Device has Failed" all the time. %uFEFFAlso when i open Eaton UPS Companion%uFEFF it crash most of the time.
Is there any fix?
I have exactly same problem with Eaton UPS Companion 1.03 and Eaton Ellipse ECO. "Communication with the Device has Failed" all the time. %uFEFFAlso when i open Eaton UPS Companion%uFEFF it crash most of the time.
Is there any fix?
Have anyone found fix yet? I have same problem with 5110 devices... Latest IPP and the communication is lost many times each day. Most of them restores after two minutes... some will be on error for all day. I can't believe this is not getting fixed ASAP. It is 2015 already... In future I think we will buy APC UPS-es instead. this is unacceptable...
In hopes of best resolving this issue for all Spiceheads contributing to this post and still having difficulty, please reach out to me directly. My e-mail is JeffreyCKennedy@eaton.com. I will follow up accordingly with each of you and provide a plan of action to resolve these issues for you. Thank you for your patience to this point.
something worked out for me after few years of dealing with this problem (of course, not constantly): I've just changed a (access) password in a way that it does not contain exclamation mark (that's: !)... maybe it's an issue with (some) special characters?
Regards,
Josip
I would think so too. But I tried creating the rule and leave it on for half an hour. The connection were fine during that time. Then I removed the rule again, and the server lost connection after about 2 min. I then reapplied the rule, and the connection came on immediately.
It does seem a little strange, why I would be able to connect to the UPS when all ports ought to be closed.
Okay, then again it wouldn't be the first time I witness strange behavior in this field! I'll try your firewall fix, although mine would be the host firewall since both devices are on the same subnet. What did your rule consist of? TCP, UDP port numbers to permit?
I know what you're saying :-)
I've created two rules:
UDP port 4679 and 4680
TCP port 4679 and 4680 + 5000 and 5001.
That seemed to do the trick.
Thanks! I'll implement today and post my results. :-)
Well, no such luck... in fact, the server already had "Eaton" firewall rules allowing this IPP traffic.
Eaton, please advise when this will be fixed or we will have to select another UPS vendor! Thanks
Hi,
I'm having a similar issue - I'm losing connectivity to the ESXi server(s), and notice if I remove the Connector, then re-add it, that communication comes back. I'm running IPM 1.42 using the CentOS 5.5 appliance downloaded from Eaton.
I'm also seeing as soon as I reboot the IPM server, connectivity to the ESXi servers is gone again.
Pierre and Bruce,tcp179 wrote:
Well, no such luck... in fact, the server already had "Eaton" firewall rules allowing this IPP traffic.
Eaton, please advise when this will be fixed or we will have to select another UPS vendor! Thanks
When do you plan to release the IPM virtual appliance 1.42 ? I'm trying to keep 1.40 working with a Eaton 9130 1500 UPS and lost many hours to try to solve communications problems. Adding "Shutdown module" causing communication errors with the appliance and restarting the Eaton-IPM service or rebooting the appliance is causing communication errors with ESXi 5.5....
Thanks David! I have contacted Jim in the communications software dept. He was extremely helpful and we have resolved the issue.
IPP with the legacy cards (CONNECTUPS-X, etc.) doesn't require a login and password. IPP with the newer cards such as NETWORK-MS, etc. do!
So, in your IPP configuration on the computer/server, select the "Settings", "Shutdown" section, then edit the "Power Source", and in the "Access Parameters" section, enter the login and password that you configured for the NETWORK-MS card.
Communications errors fixed!
My UPS is Powerware 9130 1500 with a Network Management minislot 100036826 card, firmware upgraded to HF release. I'm trying to use the IPM 1.40 vApp on vmware 5.5, the IPM 1.42 windows version, the IPP 1.42 windows version, the IPP 1.10 windows version (on my CD). I have the same "communication lost" problem with my power source. After entering the pwd into Settings-Shutdown-Configuration section, the communication still working for about 1 minute. To get connected again I must remove the power source node and add it again....it works for about 1 min. again (in the 1.10 version, but in 1.40 and 1.42 it's not as simple to keep connected again.)
I don't think it's a network problem. I do not have any problem with the web interface. I also tested snmp v1 connection with Paessler SNMP tester and do not have problems to retrieve data every...
I have same problems! How I resolve it?
Hi, I have the same problem running ipp 1.42 build 109 on ubuntu 10.04 and windows xp. I have the UPS conected to an ESXi Server via USB and then I atached the USB to virtual machine with linux 10.04. Sometimes the comunication failure lasts 2 minutes but sometimes it lasts hours. I don't know how to fix the problem if anybody can help me I would be very grateful!
Experiencing the same thing!
One Eaton 5P UPP.
IPM installed on Domain Controller, IPP installed on SQL and Terminal running on same VMware. Also installed IPM-1.43 on the same VMware.
Is this normal? Thinking about all the issues with the Eaton UPS?
Hi all, with the deadline to install the server with a trustable shutdown solution I forgot the Eaton IPM software and use an open source solution (NUT for Network UPS Tools). I have only one physical server using one UPS with a network management card. Maybe it can be difficult to make it run with many servers or UPS.
Also,I used the Eaton virtual appliance to install NUT Server on it (eliminate the need to install and configure a new linux server) its a return on investment after all the hours I passed to try to make Eaton IPM work !
If you are interrested you can follow this manual, it was very usefull but it is in French:
http://rene.margar.fr/2012/05/client-nut-pour-esxi-5-0/
I followed it to install onto vmware 5.5.
Hi. I've a lot of small UPSs like 5115 750i connected through USB and installed version IPP 1.42. The communication is lost many times each day.