<body leftmargin="0" marginwidth="0" topmargin="0" marginheight="0" offset="0" bgcolor='#FFFFFF' ><!-- This is a notification from the Help Desk. -->
<STYLE>
a { color:#FF6600;}
</STYLE>
<table width="550" cellpadding="20" cellspacing="0" bgcolor="#FFFFFF">
<tr>
<td bgcolor="#FFFFFF" valign="top" style="font-size:12px;color:#000000;font-family:trebuchet ms;">
<p style="font-weight:bold"></p>
<i style="color:#555555; font-size:11px">On Nov 12, 2013 @ 05:32 pm, smokeping-users-request@lists.oetiker.ch wrote:</i>
<p>Send smokeping-users mailing list submissions to<br />        smokeping-users@lists.oetiker.ch<br /><br />To subscribe or unsubscribe via the World Wide Web, visit<br />        https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users<br />or, via email, send a message with subject or body 'help' to<br />        smokeping-users-request@lists.oetiker.ch<br /><br />You can reach the person managing the list at<br />        smokeping-users-owner@lists.oetiker.ch<br /><br />When replying, please edit your Subject line so it is more specific<br />than "Re: Contents of smokeping-users digest..."<br /><br /><br />Today's Topics:<br /><br /> 1. Re: Network Latency of DHCP clients (Paul Mansfield)<br /> 2. Re: Network Latency of DHCP clients (Dan O'Neill)<br /> 3. RedHat install newbie issues. (Indian Maiden)<br /> 4. Re: RedHat install newbie issues. (Paul Mansfield)<br /> 5. (no subject) (Dharmapriya Thusitha)<br /> 6. Re: (no subject) (Paul Mansfield)<br /> 7. Re: (no subject) (Pa
ul Mansfield)<br /><br /><br />----------------------------------------------------------------------<br /><br />Message: 1<br />Date: Mon, 1 Jul 2013 10:25:05 +0100<br />From: Paul Mansfield <paul.mansfield+smokeping@grapeshot.co.uk><br />Subject: Re: [smokeping-users] Network Latency of DHCP clients<br />To: smokeping-users@lists.oetiker.ch<br />Message-ID:<br />        <CAHYeK0cmLr7cb+-+jEC1PewNJdHQjz3vyW_dK4p7N5jd-DDv3w@mail.gmail.com><br />Content-Type: text/plain; charset=ISO-8859-1<br /><br />On 1 July 2013 10:20, puneet bhardwaj <puneetbhrdwj02@gmail.com> wrote:<br />> Yes I want to measure network latency between my smokeping monitoring<br />> server and all clients who have been allocated a DHCP address and also the<br /><br />I would suggest using cacti and monitor switch ports instead.<br /><br /><br /><br />------------------------------<br /><br />Message: 2<br />Date: Mon, 1 Jul 2013 06:07:10 -0700<br />From: "Dan O'Neill" <dano@
northpb.com><br />Subject: Re: [smokeping-users] Network Latency of DHCP clients<br />To: Paul Mansfield <paul.mansfield+smokeping@grapeshot.co.uk><br />Cc: "smokeping-users@lists.oetiker.ch"<br />        <smokeping-users@lists.oetiker.ch><br />Message-ID:<br />        <CACCnszEgMZkuPqJTz_-aMP0Bzw9h9RPEVwCDYqNLNM33kYVTDw@mail.gmail.com><br />Content-Type: text/plain; charset="iso-8859-1"<br /><br />On Mon, Jul 1, 2013 at 2:25 AM, Paul Mansfield <<br />paul.mansfield+smokeping@grapeshot.co.uk> wrote:<br /><br />> On 1 July 2013 10:20, puneet bhardwaj <puneetbhrdwj02@gmail.com> wrote:<br />> > Yes I want to measure network latency between my smokeping monitoring<br />> > server and all clients who have been allocated a DHCP address and also<br />> the<br />><br />> I would suggest using cacti and monitor switch ports instead.<br />><br />><br />While it is certainly possible to measure latency to your client
s, DHCP<br />allocated addresses add some behaviors that are somewhat incompatible with<br />long-term measurements. DHCP hands out addresses on request. These<br />addresses have a lease lifetime and the device that requested the address<br />will be required to renew prior to the expiration of the lease. There is no<br />guarantee that the device will always receive the same IP address, although<br />it is very likely. Further problems arise when devices with an allocated<br />address leave the network - a cell phone on WiFi, for example, will travel<br />away from the network and therefore the address is no longer active or may<br />be reassigned to a different device. This will generate graphs with holes,<br />spikes and all kinds of noisy information.<br /><br />Assuming you're going to continue down this path, you'll need to find the<br />dhcpd.leases file on your DHCP server. In a Linux installation, the file is<br />normally located at /var/lib/dhcp3/dhcpd.leases. Yo
u'll then need to write<br />a script to read this file, extract IP addresses, generate a set of<br />Smokeping targets in your smokeping configuration file and finally reload<br />Smokeping. You may also want to remove targets from leases that are no<br />longer active, or not...<br /><br />Bandwidth measurement is not a strength of Smokeping. As mentioned by Paul<br />Mansfield, you will want to use a different solution that can read SNMP<br />information from your managed switch to retrieve the number of packets<br />being sent and received.<br /><br />Best,<br /><br />Dan<br />-------------- next part --------------<br />An HTML attachment was scrubbed...<br />URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130701/e613ae9b/attachment-0001.htm <br /><br />------------------------------<br /><br />Message: 3<br />Date: Wed, 3 Jul 2013 09:21:41 -0700<br />From: Indian Maiden <theindianmaiden@gmail.com><br />Subject: [smokeping-users] RedHat instal
l newbie issues.<br />To: smokeping-users@lists.oetiker.ch<br />Message-ID:<br />        <CAKJ0_nt3dEjoXXoAE2S_EEO4v9y2ov16dL+rfQ0xwo5nHzdOXg@mail.gmail.com><br />Content-Type: text/plain; charset="iso-8859-1"<br /><br />I have had to manually compile rrdtood but do not know how to resolve this<br />error:<br /><br />checking checking for perl module 'LWP'... Ok ** Aborting Configure<br />******************************<br /><br />If you know where perl can find the missing modules, set the PERL5LIB<br />environment variable accordingly. FIRST though, make sure that 'perl'<br />starts the perl binary you want to use for SmokePing. Now you can install<br />local copies of the missing modules by running<br />./setup/build-perl-modules.sh /opt/smokeping/thirdparty The RRDs perl<br />module is part of RRDtool. Either use the rrdtool package provided by your<br />OS or install rrdtool from source. If you install from source, the RRDs<br />module is located PREFIX/lib/perl
<br /><br />Hopefully it is easy!<br />-------------- next part --------------<br />An HTML attachment was scrubbed...<br />URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130703/659939dc/attachment-0001.htm <br /><br />------------------------------<br /><br />Message: 4<br />Date: Wed, 3 Jul 2013 17:43:43 +0100<br />From: Paul Mansfield <paul.mansfield+smokeping@grapeshot.co.uk><br />Subject: Re: [smokeping-users] RedHat install newbie issues.<br />To: smokeping-users@lists.oetiker.ch<br />Message-ID:<br />        <CAHYeK0eoEsTigTHgajOSNZU3mAORzb6eK9kYm0bpJUh6fuOVQg@mail.gmail.com><br />Content-Type: text/plain; charset=ISO-8859-1<br /><br />is this for Centos6? these are the depends I put in when I packaged it...<br /><br />bc, fping, libidn, make, perl-CGI, perl-Config-Grammar,<br />perl-Test-Simple, perl-YAML, popt, rrdtool-perl, tcptraceroute<br /><br /><br />I had to use cpanspec for the perl-Config-Grammar package.<br /><br /><br />On 3 July
2013 17:21, Indian Maiden <theindianmaiden@gmail.com> wrote:<br />> I have had to manually compile rrdtood but do not know how to resolve this<br />> error:<br />><br />> checking checking for perl module 'LWP'... Ok ** Aborting Configure<br />> ******************************<br />><br />> If you know where perl can find the missing modules, set the PERL5LIB<br />> environment variable accordingly. FIRST though, make sure that 'perl' starts<br />> the perl binary you want to use for SmokePing. Now you can install local<br />> copies of the missing modules by running ./setup/build-perl-modules.sh<br />> /opt/smokeping/thirdparty The RRDs perl module is part of RRDtool. Either<br />> use the rrdtool package provided by your OS or install rrdtool from source.<br />> If you install from source, the RRDs module is located PREFIX/lib/perl<br />><br />> Hopefully it is easy!<br />><br />> ____________________________________
___________<br />> smokeping-users mailing list<br />> smokeping-users@lists.oetiker.ch<br />> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users<br />><br /><br /><br /><br />------------------------------<br /><br />Message: 5<br />Date: Mon, 8 Jul 2013 14:30:42 +0530<br />From: Dharmapriya Thusitha <thusitha555@gmail.com><br />Subject: [smokeping-users] (no subject)<br />To: smokeping-users@lists.oetiker.ch<br />Message-ID:<br />        <CAJh6EL6PZMNdU_yF-dXm0nu6umTrY4t5ds3Fugf0yPU5Vmd3Ww@mail.gmail.com><br />Content-Type: text/plain; charset="iso-8859-1"<br /><br />hi,<br />In smokeping ,it uses ++/[-_0-9a-zA-Z]+/ types of device names.so i cant<br />add ip address as the device name .it gives an error." ERROR:<br />/etc/smokeping/devices/xx.xx.xx.xx, line 1: unknown section<br />'"xx.xx.xx.xx.and i have 5000 agents to monitor. because of this<br />problem ,it is very hard<br />to change the names of those devices.give me an so
lution<br />-------------- next part --------------<br />An HTML attachment was scrubbed...<br />URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130708/44583e38/attachment-0001.htm <br /><br />------------------------------<br /><br />Message: 6<br />Date: Mon, 8 Jul 2013 10:10:29 +0100<br />From: Paul Mansfield <paul.mansfield+smokeping@grapeshot.co.uk><br />Subject: Re: [smokeping-users] (no subject)<br />To: smokeping-users@lists.oetiker.ch<br />Message-ID:<br />        <CAHYeK0fA1m6UwwvfGELW8OkOqO2-a0p=cGVTtdikMxUfjmJ4yQ@mail.gmail.com><br />Content-Type: text/plain; charset=ISO-8859-1<br /><br />On 8 July 2013 10:00, Dharmapriya Thusitha <thusitha555@gmail.com> wrote:<br />> and i have 5000 agents to monitor. because of this problem ,it is very hard<br />> to change the names of those devices.give me an solution<br /><br />I'd recommend programmatically generating something you can add to<br />/etc/hosts file or DNS, as well as gene
rating the smokeping<br />configuration.<br /><br />If you have that many hosts you must be using some sort of automated<br />deployment and monitoring already so you can get the list of IPs from<br />that.<br /><br /><br /><br />------------------------------<br /><br />Message: 7<br />Date: Mon, 8 Jul 2013 11:27:30 +0100<br />From: Paul Mansfield <paul.mansfield+smokeping@grapeshot.co.uk><br />Subject: Re: [smokeping-users] (no subject)<br />To: smokeping-users@lists.oetiker.ch<br />Message-ID:<br />        <CAHYeK0f+pa9jpeapnwiFeQd3gqr+YtktQCaacd8yNJvq6rMmxA@mail.gmail.com><br />Content-Type: text/plain; charset=ISO-8859-1<br /><br />Simply emailing me directly with your original question, without<br />having considered my reply, is neither polite nor likely to yield<br />results. In your original demand for a solution, I presume you have<br />invoked the service contract you paid for to get minions to spring<br />into action?<br /><br />http://www.catb.org/esr/faqs/
smart-questions.html#before<br /><br /><br />On 8 July 2013 10:20, Dharmapriya Thusitha <thusitha555@gmail.com> wrote:<br />> hi,<br />> In smokeping ,it uses ++/[-_0-9a-zA-Z]+/ types of device names.so i cant add<br />> ip address as the device name .it gives an error." ERROR:<br />> /etc/smokeping/devices/xx.xx.xx.xx, line 1: unknown section '"xx.xx.xx.xx.<br />> and i have 5000 agents to monitor. because of this problem ,it is very hard<br />> to change the names of those devices.give me an solution<br />><br />><br />> On Mon, Jul 8, 2013 at 2:40 PM, Paul Mansfield<br />> <paul.mansfield+smokeping@grapeshot.co.uk> wrote:<br />>><br />>> On 8 July 2013 10:00, Dharmapriya Thusitha <thusitha555@gmail.com> wrote:<br />>> > and i have 5000 agents to monitor. because of this problem ,it is very<br />>> > hard<br />>> > to change the names of those devices.give me an solution<br />&
gt;><br />>> I'd recommend programmatically generating something you can add to<br />>> /etc/hosts file or DNS, as well as generating the smokeping<br />>> configuration.<br />>><br />>> If you have that many hosts you must be using some sort of automated<br />>> deployment and monitoring already so you can get the list of IPs from<br />>> that.<br />>><br />>> _______________________________________________<br />>> smokeping-users mailing list<br />>> smokeping-users@lists.oetiker.ch<br />>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users<br />><br />><br /><br /><br /><br />------------------------------<br /><br />_______________________________________________<br />smokeping-users mailing list<br />smokeping-users@lists.oetiker.ch<br />https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users<br /><br /><br />End of smokeping-users Digest, Vol 77, Issue 2<br />*********************
*************************</p>
<br/>
<hr/>
This is an automated response. Your issue has been noted. We'll be in touch soon.<br/>
<br/>
Please reply to this email or visit the URL below with any additional details.<br/>
<br/>
<a href="http://florin-pc/portal/view-help-request/32">http://florin-pc/portal/view-help-request/32</a><br/>
</td>
</tr>
</table>
</body>