monitor successful but host still down

[gandalf]

port 33439!? That's not the port i told it to monitor!?

This behaviour is so bizzare!

That's one port to be found in lib/ping.php as a constant value. But when testing for TCP/23, that one should be taken instead
Reinhard

[crashergs]

That happened to me today, device showed as down in the monitor plugin. We went into the switch and determined that the community was blank, which was weird because it was graphing this whole time until today, we repopulated the community name and started graphing again. although sounds too simple, I would check that if you haven't done so already.

[jrdalrymple]

In the end, both result in the POWERWARE not responding, so my statement earlier about the .0.1 being 'nonexistent' is premature. That is, it may or may not exist on the POWERWARE UPS...all I know is when asked by either application, it does not reply, where every other devices we have replies fine with the .0.1 request.

Could use some more advice. My development background here is weak, but I'm trying!

Sincere appreciation on this. I'm excited to be getting into the details of this problem!

I've written a quick and dirty fix for the Eaton Powerware problem.
The problem is that for some reason these devices don't reply to getnexts. If you do a get on the oid instead it replies and the host then appears up. To complicate matters it doesn't seem to like to reply to pings either.

My fix was to query the sysDescr.0 OID and look for the string "ConnectUPS". If it finds it then it does a get on that OID instead of getnext on .1.

If you want the exact code feel free to ask and I'll send a diff or whatever. Also, this is on 0.8.7b