Xymon Mailing List Archive search

UDP Ports

5 messages in this thread

list Tony Barrett · Thu, 3 May 2007 16:45:13 +0100 ·
Is there any way I can monitor UDP ports within bb-services? Hobbit
seems to assume all ports are TCP, and I'd like to run a port test
against our DHCP servers here to make sure they're responding ok.
 
Thanks
 

-- 
Roke Manor Research Ltd, Romsey,
Hampshire, SO51 0ZN, United Kingdom

A Siemens company
Registered in England & Wales at:
Siemens House, Oldbury, Bracknell
Berks RG12 8FZ. Number 267550
Visit our user-edfde8a08ce8@xymon.invalid
The information contained in this e-mail and any attachments is
proprietary to Roke Manor Research Ltd and must not be passed to any
third party without permission. This communication is for information
only and shall not create or change any contractual relationship.

Please consider the environment before printing this email
list Henrik Størner · Thu, 3 May 2007 17:49:38 +0200 ·
quoted from Tony Barrett
On Thu, May 03, 2007 at 04:45:13PM +0100, Barrett, Tony wrote:
Is there any way I can monitor UDP ports within bb-services? Hobbit
seems to assume all ports are TCP, and I'd like to run a port test
against our DHCP servers here to make sure they're responding ok.
Hobbit doesn't have support for UDP protocols built in, since these 
use mostly binary data - SNMP, DNS, DHCP, NFS and NTP are probably the 
most commonly used UDP-based protocols, and they all carry date in a
binary format, unlike the popular TCP-based protocols.

And unlike TCP, the UDP-based protocols do not have a generic
"handshake" that you can use to check if the service is running.

My best suggestion is to use the tool called "dhcping" to check your 
DHCP servers. It requires some special setup on the DHCP server side,
but once you have it working then creating a custom test script to
run it and report the status to Hobbit should be very simple.


Regards,
Henrik
list Massimo Morsiani · Thu, 3 May 2007 18:09:29 +0200 ·
Hi,

take a look at http://www.trantor.org/theshire/doku.php/monitors:dhcp.
It's a custom script based on dhcping.


Regards.

Massimo Morsiani
Information Technology Dept.
Gilbarco S.p.a.
via de' Cattani, 220/G
50145 Firenze
tel:	+XX-XXX-XXXXX
fax:	+XX-XXX-XXXXXX
email:	user-32025d8bd22e@xymon.invalid
web:	http://www.gilbarco.it
quoted from Henrik Størner


-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] Sent: giovedì 3 maggio 2007 17.50
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] UDP Ports

On Thu, May 03, 2007 at 04:45:13PM +0100, Barrett, Tony wrote:
Is there any way I can monitor UDP ports within bb-services? Hobbit seems to assume all ports are TCP, and I'd like to run a port test against our DHCP servers here to make sure they're responding ok.
Hobbit doesn't have support for UDP protocols built in, since these use mostly binary data - SNMP, DNS, DHCP, NFS and NTP are probably the most commonly used UDP-based protocols, and they all carry date in a binary format, unlike the popular TCP-based protocols.

And unlike TCP, the UDP-based protocols do not have a generic "handshake" that you can use to check if the service is running.

My best suggestion is to use the tool called "dhcping" to check your DHCP servers. It requires some special setup on the DHCP server side, but once you have it working then creating a custom test script to run it and report the status to Hobbit should be very simple.


Regards,
Henrik


This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee.  Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law.  If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system.  If you have any questions about this e-mail please notify the sender immediately.
list Mike Arnold · Thu, 3 May 2007 16:06:15 -0700 (MST) ·
quoted from Massimo Morsiani
Morsiani, Massimo wrote:
Hi,

take a look at http://www.trantor.org/theshire/doku.php/monitors:dhcp.
It's a custom script based on dhcping.
Also see Hobbit Monitor Client DHCP Server Test here:
http://www.razorsedge.org/~mike/software/#hobbit

Allows the Hobbit client to test DHCP servers. Useful when the Hobbit
server is not on the correct network and DHCP_RELAYs cannot be installed.

-- 
-m

... so long as the people do not care to exercise their freedom, those
who wish to tyrranize will do so; for tyrants are active and ardent,
and will devote themselves in the name of any number of gods, religious
and otherwise, to put shackles upon sleeping men.
                -- Voltarine de Cleyre
list Tony Barrett · Fri, 4 May 2007 15:49:08 +0100 ·
quoted from Massimo Morsiani
Morsiani, Massimo wrote:
Hi,

take a look at http://www.trantor.org/theshire/doku.php/monitors:dhcp.
It's a custom script based on dhcping.


Regards.

Massimo Morsiani
Information Technology Dept.
Gilbarco S.p.a.
via de' Cattani, 220/G
50145 Firenze
tel:	+XX-XXX-XXXXX
fax:	+XX-XXX-XXXXXX
email:	user-32025d8bd22e@xymon.invalid
web:	http://www.gilbarco.it


-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: giovedì 3 maggio 2007 17.50
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] UDP Ports

On Thu, May 03, 2007 at 04:45:13PM +0100, Barrett, Tony wrote:
Is there any way I can monitor UDP ports within bb-services? Hobbit
seems to assume all ports are TCP, and I'd like to run a port test
against our DHCP servers here to make sure they're responding ok.
Hobbit doesn't have support for UDP protocols built in, since these
use mostly binary data - SNMP, DNS, DHCP, NFS and NTP are probably
the most commonly used UDP-based protocols, and they all carry date
in a binary format, unlike the popular TCP-based protocols.   

And unlike TCP, the UDP-based protocols do not have a generic
"handshake" that you can use to check if the service is running. 

My best suggestion is to use the tool called "dhcping" to check your
DHCP servers. It requires some special setup on the DHCP server side,
but once you have it working then creating a custom test script to
run it and report the status to Hobbit should be very simple.   


Regards,
Henrik


This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law.  If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system.  If you
have any questions about this e-mail please notify the sender
immediately.

 
Massimo, I found a couple of small problems with this script. First, it was developed on Solaris, and uses ptime to measure execution time. Linux doesn't have ptime, just 'time' and I'm not sure if it's giving the correct response for script post-processing. I get some strange output;

  DHCP query succeeded
 
no answer
Command exited with non-zero status 1
0.00user 0.00system 0:10.00elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+191minor)pagefaults 0swaps
 
Seconds: 0

Hobbit though, thinks the connection has been successful, even though the script returns status 1 (no answer), and shows the link as green.

Secondly, the script seems to have been developed with a single DHCP server in mind. We use split DHCP servers that each lease a different range in a global scope, which means I cannot test both DHCP servers from the same script.
quoted from Tony Barrett


-- 
Roke Manor Research Ltd, Romsey,
Hampshire, SO51 0ZN, United Kingdom

A Siemens company
Registered in England & Wales at:
Siemens House, Oldbury, Bracknell
Berks RG12 8FZ. Number 267550
Visit our user-edfde8a08ce8@xymon.invalid
The information contained in this e-mail and any attachments is
proprietary to Roke Manor Research Ltd and must not be passed to any
third party without permission. This communication is for information
only and shall not create or change any contractual relationship.

Please consider the environment before printing this email