Monitoring a HP-UX system

[Palle L Jensen]

Hey List,

 

I was wondering if anyone would know if it is possible to monitor a few
things on a HP-UX system without installing anything on the server? We are
unable to install anything, plugins, apps etc on the server, it's a
production server. Below is a description of the general requirements.

 

The general requirements:

- Cannot install anything on the system - it's a validated production
system.

- It runs a SSH server daemon that we'd like to monitor.

- What I'd like to see is some way to have it connect to the specified port,
read the banner and then just abort the connection. The purpose of this is
that perhaps the Nagios system could read the banner response it gets, and
if it is not what it's expected, or fails to receive a banner/login prompt,
send an alert.

 

I know that monitoring the ping is workable, but how about anything else,
see above. Any help is much appreciated.

 

Thanks,

PJ

 

Nagios box running:  openSUSE 10.3 / Nagios v3.0.1. / Nagios Webinterface
3.0.1. / Nagios Nuvola 1.0.3. / Nagios Plugins 1.4.11. / Nagios Plugins
Extra 1.4.11. / Nagios Grapher 1.6.1-rc5. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090428/9f50dbb8/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null