Send Netdot-devel mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."


Today's Topics:

   1. Exporter/Nagios.pm doesn't export services attached       to ip
      addresses (Karl Putland)
   2. [Netdot - Bug #1722] Illegal division by zero with        /31 IPv4
      subnets ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Mon, 4 Feb 2013 10:46:01 -0700
From: Karl Putland <[email protected]>
Subject: [Netdot-devel] Exporter/Nagios.pm doesn't export services
        attached        to ip addresses
To: netdot-devel <[email protected]>
Message-ID:
        <ca+exwswwicgq+3g2zl7x4wwzmr2hsf9nowuln_+qxiarn-o...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Scenario....

I want to monitor the far end of an interface with PING.
The interface will always be up/up so SNMP monitoring won't work
I created a fake device to house "psedo interfaces" that /32 ipblock
entries are attached to. This should group the checks under the placeholder
device.

Problem is that exporter only selects service where service is attached to
snmp_target ip address on the device.

What I would like to see is services selected by device -> interface -> ip
-> ipservice

Thanks,

--Karl

Karl Putland
Senior VoIP Engineer

*SimpleSignal*
3600 S Yosemite, Suite 150
Denver, CO 80237
One Number Rings All My Phones: 303-242-8608

SimpleSignal.com <http://www.simplesignal.com/> |
Blog<http://www.simplesignal.com/blog>
 | Facebook <http://www.facebook.com/SimpleSignal?ref=ts> |
Twitter<http://twitter.com/simplesignal>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-devel/attachments/20130204/d2444b86/attachment-0001.html
 

------------------------------

Message: 2
Date: Mon, 4 Feb 2013 11:47:33 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1722] Illegal division by zero
        with    /31 IPv4 subnets
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1722 has been updated by Anton Berezin.


The problem description hints to an outdated version of NetAddr::IP.

>From NetAddr::IP documentation:

<pre>
       "->num()"
           As of version 4.42 of NetAddr::IP and version 1.27 of
           NetAddr::IP::Lite a /31 and /127 with return a net num value of 2
           instead of 0 (zero) for point-to-point networks.
</pre>

So I think that the originator should upgrade NetAddr::IP on his system.
----------------------------------------
Bug #1722: Illegal division by zero with /31 IPv4 subnets
https://osl.uoregon.edu/redmine/issues/1722#change-3033

Author: Matej Vadnjal
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: 


If I try to define a /31 IPv4 prefix of type Subnet in Management -> Address 
Space I get the following error:

@
error:  Illegal division by zero at 
/usr/local/netdot/htdocs/management/subnet.mhtml line 161.
context:        
...     
157:     $cols = 16;
158:    }
159:    
160:    my $num = ($mask == 31)? $net->num() : $net->num()+1;
161:    for( my $i=0; $i<($num/$cols); $i++ ) {
162:     my @row = ();
163:    
164:     for( my $j=0; $j<$cols; $j++ ) {
165:     my $ip_addr = $net->addr;
...     
code stack:      /usr/local/netdot/htdocs/management/subnet.mhtml:161
/usr/local/netdot/htdocs/management/ip.html:1732
/usr/local/netdot/htdocs/management/autohandler:81
/usr/share/perl5/HTML/Mason/Request.pm:936
/usr/local/netdot/htdocs/masondata/obj/991023240/management/autohandler.obj:21
/usr/local/netdot/htdocs/autohandler:76
@

The subnet is created in the database, but cannot be displayed. The exact same 
error appears if I select a /31 subnet already defined in netdot.

/31 Subnets discovered by SNMP on routers are added to netdot fine. But again 
cannot be "clicked on".

/31 Containers and Reserved work fine.

This is in version 1.0.4. I have a feeling this problem was not present in 
1.0.1, but I'm not a 100% sure.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


------------------------------

_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel


End of Netdot-devel Digest, Vol 71, Issue 2
*******************************************

Reply via email to