headers
Ronny Trommer | 2 Feb 2008 15:51
Picon

Re: [opennms-devel] Categories and other groupings


Only a user-reflection about categories and groups ;)

we using OpenNMS in very complex networks as isp. If you have a network with
many changes and many ip-subnets, then it is a good way to put functions to
categories, instead of XML-files with IP-based rules.
In that case maintaining is not very easy. One device must be in more than 3 or
4 groups.

I think you can use categories at the moment in two ways.

First grouping your devices for stuff like:
  - surveillance
  - dashboard
  - First-Page on WEBUI
  - SLA-calculations, reporting
  - All other grouping-stuff like geographic, topology, organisation

Second grouping for NMS-functionalities like:
  - notification
  - data-collections (different timeresolutions 60 sec., 300 sec etc.)
  - thresholding
  - polling
    - Default-Polling-Packages
    - Deviceclass-specific Polling-Packages
    - SLA-Polling-Packages
    - ?? and why not capabilityscans, but this is a another question ;)

A possible way i think, is to "tag" your categories to show some other persons,
which category is used for which function (?? meta-categories ;)??). I don't
(Continue reading)

Permalink | Reply | 0 comments |
headers
DJ Gregor | 4 Feb 2008 05:04
Favicon

[opennms-devel] Please test KSC reports in trunk revision 8334 or later

I just did some major rework of KSC reports, especially editing of
reports, as of trunk revision 8334, and I would appreciate as many eyes
as possible testing this, since it seems to be a popular feature.

In particular, each report is now referenced by a persistent ID that
doesn't change across edits (particularly new report addition, see bug
#2216).  Also, I fixed the long-standing problem of multiple people not
being able to edit KSC reports at the same time by moving editing state
into a new object, KscReportEditor, that is stored in the user's session
on the server.  A single user still can't edit multiple reports at the
same time with multiple windows of the same browser, however.

The commit message is below for those who are interested.


        Thanks,
       - djg

On Sun, 03 Feb 2008 19:57:56 -0800, djgregor <at> users.sourceforge.net said:
> Revision: 8334
>           http://opennms.svn.sourceforge.net/opennms/?rev=8334&view=rev
> Author:   djgregor
> Date:     2008-02-03 19:57:56 -0800 (Sun, 03 Feb 2008)
> 
> Log Message:
> -----------
> - Fix for bug#2216 -- KSC Report list is reordered every time a new
> report is added.
> - A unique ID is assigned to each KSC report, is persisted across edits,
> and is used instead of the report's index in the KSC configuration file
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rabie Van der Merwe | 4 Feb 2008 12:43
Picon

[opennms-devel] Bug#: 2235

Hi,

Just a thought, but it might not be a bad idea to extent on this a
little 
and trigger a rescan of a node if it picks up that the sysuptime has
reset, 
that way if anything moved because of a reboot we would catch it?
(think cisco :) )

Regards
Rabie

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
Permalink | Reply | 6 comments |
headers
Mike M | 4 Feb 2008 13:36
Picon

Re: [opennms-devel] Bug#: 2235

On Feb 4, 2008 6:43 AM, Rabie Van der Merwe <rvdmerwe <at> mhg.co.za> wrote:
> Hi,
>
> Just a thought, but it might not be a bad idea to extent on this a
> little
> and trigger a rescan of a node if it picks up that the sysuptime has
> reset,
> that way if anything moved because of a reboot we would catch it?
> (think cisco :) )

I think this would be cool, especially since we occasionally see nodes
kernel panic and reboot faster than OpenNMS can catch them.  My only
concern is that sysuptime is not exactly reliable, especially for
high-uptime Linux machines which have the jiffies rollover problem
after 497 days.

Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
(Continue reading)

Permalink | Reply | 5 comments |
headers
Jeff Gehlbach | 4 Feb 2008 15:20
Favicon

Re: [opennms-devel] Bug#: 2235


On Feb 4, 2008, at 7:36 AM, Mike M wrote:
> I think this would be cool, especially since we occasionally see nodes
> kernel panic and reboot faster than OpenNMS can catch them.  My only
> concern is that sysuptime is not exactly reliable, especially for
> high-uptime Linux machines which have the jiffies rollover problem
> after 497 days.

Alejandro Galue wrote a sysUpTime tracker at Dev-Jam 2007 that does  
exactly what Rabie suggested.  I believe he checked it in to trunk  
during bug day this past weekend.

sysUpTime sucks for a number of reasons, but we can't count on having  
hrSystemUptime everywhere, and it's the best indicator we've got of a  
device or agent having been restarted that's not configured to send  
coldStart traps.  I think most people would be willing to accept an  
extra rescan every sixteen months in exchange for not missing an index  
shift.

-jeff
Permalink | Reply | 0 comments |
headers
Rabie Van der Merwe | 4 Feb 2008 16:50
Picon

Re: [opennms-devel] Bug#: 2235

Mmm I have seen the uptime issue on some older boxes here ...
On a side note I run a threshold check on sysUptime to catch any system
restarts that falls between the 5 min ping checks :)

Rabie

-----Original Message-----
From: opennms-devel-bounces <at> lists.sourceforge.net
[mailto:opennms-devel-bounces <at> lists.sourceforge.net] On Behalf Of Mike M
Sent: 04 February 2008 14:37 PM
To: OpenNMS Code Development and Bugs
Subject: Re: [opennms-devel] Bug#: 2235

On Feb 4, 2008 6:43 AM, Rabie Van der Merwe <rvdmerwe <at> mhg.co.za> wrote:
> Hi,
>
> Just a thought, but it might not be a bad idea to extent on this a
> little
> and trigger a rescan of a node if it picks up that the sysuptime has
> reset,
> that way if anything moved because of a reboot we would catch it?
> (think cisco :) )

I think this would be cool, especially since we occasionally see nodes
kernel panic and reboot faster than OpenNMS can catch them.  My only
concern is that sysuptime is not exactly reliable, especially for
high-uptime Linux machines which have the jiffies rollover problem
after 497 days.

Mike
(Continue reading)

Permalink | Reply | 3 comments |
headers
Benjamin Reed | 4 Feb 2008 17:03
Favicon
Gravatar

[opennms-devel] Time for a 1.3.10 release?


What is everyone's thought on releasing 1.3.10?

We'd like to have a new release ready for SCALE so that we can have CDs
and such ready, and IMHO I don't think any of the remaining 1.3.10 bugs
are showstoppers.

~  http://bugzilla.opennms.org/showdependencytree.cgi?id=2108

Thoughts?

--
Benjamin Reed
The OpenNMS Group
http://www.opennms.org/
Permalink | Reply | 0 comments |
headers
ayresw | 4 Feb 2008 19:37
Picon

[opennms-devel] [Fwd: [opennms-cvs] SF.net SVN: opennms: [8326] opennms/trunk/opennms-services/src/main/java/ org/opennms/netmgt/dhcpd/Dhcpd.java]

This mod (rev 8326) breaks DHCP! I tested this by backing it out of my
system and verifying that the problem went away. Here are the errors
from poller.log:

2008-02-04 09:12:04,999 DEBUG [PollerScheduler-30 Pool-fiber26] Poller:
Poller.ctor: opening socket connection with DHCP client daemon on port
5818
2008-02-04 09:12:05,001 ERROR [PollerScheduler-30 Pool-fiber26] Poller:
IO Exception during socket connection establishment with DHCP client
daemon.
java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:366)
        at java.net.Socket.<init>(Socket.java:208)
        at org.opennms.netmgt.dhcpd.Poller.<init>(Poller.java:238)
        at org.opennms.netmgt.dhcpd.Poller.isServer(Poller.java:401)
        at org.opennms.netmgt.dhcpd.Dhcpd.isServer(Dhcpd.java:388)
        at
org.opennms.netmgt.poller.monitors.DhcpMonitor.poll(DhcpMonitor.java:130)
        at
org.opennms.netmgt.poller.pollables.LatencyStoringServiceMonitorAdaptor.poll(LatencyStoringServiceMonitorAdaptor.java:90)
        at
org.opennms.netmgt.poller.pollables.PollableServiceConfig.poll(PollableServiceConfig.java:100)
(Continue reading)

Permalink | Reply | 7 comments |
headers
Rabie Van der Merwe | 4 Feb 2008 20:29
Picon

Re: [opennms-devel] Bug#: 2235

Hi,

I see bug 2235 is fixed, just a note, nothing big, there is a typo in
the debug output attached to the bug:

"Ignoring value because of sysUpTime chaned"
Should read:
"Ignoring value because of sysUpTime changed" :)

Regards
Rabie

-----Original Message-----
From: opennms-devel-bounces <at> lists.sourceforge.net
[mailto:opennms-devel-bounces <at> lists.sourceforge.net] On Behalf Of Rabie
Van der Merwe
Sent: 04 February 2008 17:50 PM
To: OpenNMS Code Development and Bugs
Subject: Re: [opennms-devel] Bug#: 2235

Mmm I have seen the uptime issue on some older boxes here ...
On a side note I run a threshold check on sysUptime to catch any system
restarts that falls between the 5 min ping checks :)

Rabie

-----Original Message-----
From: opennms-devel-bounces <at> lists.sourceforge.net
[mailto:opennms-devel-bounces <at> lists.sourceforge.net] On Behalf Of Mike M
Sent: 04 February 2008 14:37 PM
(Continue reading)

Permalink | Reply | 2 comments |
headers
Alejandro Galue | 4 Feb 2008 20:39
Picon

Re: [opennms-devel] Bug#: 2235


Hello,

Thanks for catch it.

It fixed on rev 8336

Alejandro.

On Feb 4, 2008, at 2:59 PM, Rabie Van der Merwe wrote:

> Hi,
>
> I see bug 2235 is fixed, just a note, nothing big, there is a typo in
> the debug output attached to the bug:
>
> "Ignoring value because of sysUpTime chaned"
> Should read:
> "Ignoring value because of sysUpTime changed" :)
>
> Regards
> Rabie
>
>
> -----Original Message-----
> From: opennms-devel-bounces <at> lists.sourceforge.net
> [mailto:opennms-devel-bounces <at> lists.sourceforge.net] On Behalf Of  
> Rabie
> Van der Merwe
> Sent: 04 February 2008 17:50 PM
(Continue reading)

Permalink | Reply | 1 comment |

Gmane