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. [Netdot - Bug #1752] (New) Netdot can't collect FWT       on some
      H3C/HP devices ([email protected])
   2. [Netdot - Bug #1752] (Closed) Netdot can't collect        FWT on
      some H3C/HP devices ([email protected])
   3. enhancement: doc status on interface detail page, red when
      removed (Karl Putland)
   4. [Netdot - Bug #1751] (Resolved) Netdot sets SNMP  community to
      SNMPv3 username when discovering via SNMPv3 ([email protected])
   5. [Netdot - Bug #1749] (Resolved) Reports -> IP ->  Unused
      Subnets - System error ([email protected])
   6. [Netdot - Bug #1745] (Resolved) ipv6 addresses on interfaces
      on nexus 7K not working ([email protected])
   7. [Netdot - Bug #1744] (Resolved) Nagios - Cannot   monitor a
      service unless the IP address is the snmp_target address
      ([email protected])
   8. [Netdot - Feature #1739] Utilization of DHCP pools
      ([email protected])
   9. [Netdot - Bug #1740] (Resolved) Not possible to give      an
      existing ipv4 host an ipv6 address via user_management    (and vice
      versa) ([email protected])
  10. [Netdot - Feature #1739] (Closed) Utilization of  DHCP pools
      ([email protected])


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

Message: 1
Date: Tue, 23 Apr 2013 00:44:33 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1752] (New) Netdot can't
        collect FWT     on some H3C/HP devices
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1752 has been reported by Blakkheim GW.

----------------------------------------
Bug #1752: Netdot can't collect FWT on some H3C/HP devices
https://osl.uoregon.edu/redmine/issues/1752

Author: Blakkheim GW
Status: New
Priority: Normal
Assignee: 
Category: AddressTracking
Target version: 1.0.4
Resolution: 


Hi,

I have a problem on some of our switches models (H3C S5800, HP A3600...). On 
these equipments, the MIB table dot1dTpFdbTable isn't present anymore. HP/H3C 
recommends to use the dot1qTpFdbTable instead to retrieve MAC addresses.

Is this possible to add this to Netdot ?

Regards.


-- 
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


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

Message: 2
Date: Tue, 23 Apr 2013 06:36:58 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1752] (Closed) Netdot can't
        collect FWT on some H3C/HP devices
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1752 has been updated by Carlos Vicente.

Status changed from New to Closed
Assignee set to Carlos Vicente
Resolution set to wontfix

Blakkheim GW wrote:
> Hi,
> 
> I have a problem on some of our switches models (H3C S5800, HP A3600...). On 
> these equipments, the MIB table dot1dTpFdbTable isn't present anymore. HP/H3C 
> recommends to use the dot1qTpFdbTable instead to retrieve MAC addresses.
> 
> Is this possible to add this to Netdot ?
> 
> Regards.


That kind of change needs to happen in the SNMP::Info project. 

https://sourceforge.net/projects/snmp-info/

cv
----------------------------------------
Bug #1752: Netdot can't collect FWT on some H3C/HP devices
https://osl.uoregon.edu/redmine/issues/1752#change-3055

Author: Blakkheim GW
Status: Closed
Priority: Normal
Assignee: Carlos Vicente
Category: AddressTracking
Target version: 1.0.4
Resolution: wontfix


Hi,

I have a problem on some of our switches models (H3C S5800, HP A3600...). On 
these equipments, the MIB table dot1dTpFdbTable isn't present anymore. HP/H3C 
recommends to use the dot1qTpFdbTable instead to retrieve MAC addresses.

Is this possible to add this to Netdot ?

Regards.


-- 
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


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

Message: 3
Date: Tue, 23 Apr 2013 10:03:32 -0600
From: Karl Putland <[email protected]>
Subject: [Netdot-devel] enhancement: doc status on interface detail
        page,   red when removed
To: netdot-devel <[email protected]>
Message-ID:
        <ca+exwsypwnw3ykxdtxay8tps8tyngm5axswkwpvcok00etp...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On the interface details page, please change the td.bg to red if doc_status
== removed.
This would be consistent with the display of the interface list.

--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/20130423/72076074/attachment-0001.html
 

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

Message: 4
Date: Tue, 23 Apr 2013 11:07:42 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1751] (Resolved) Netdot sets
        SNMP    community to SNMPv3 username when discovering via SNMPv3
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1751 has been updated by Carlos Vicente.

Status changed from New to Resolved
Resolution set to fixed


----------------------------------------
Bug #1751: Netdot sets SNMP community to SNMPv3 username when discovering via 
SNMPv3
https://osl.uoregon.edu/redmine/issues/1751#change-3056

Author: Carlos Vicente
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 1.0.5
Resolution: fixed


This breaks SNMPv2 operations.


-- 
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


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

Message: 5
Date: Tue, 23 Apr 2013 11:12:57 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1749] (Resolved) Reports -> IP
        ->      Unused Subnets - System error
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1749 has been updated by Carlos Vicente.

Category set to IPManagement
Status changed from New to Resolved
Assignee set to Carlos Vicente
Target version changed from 1.0.4 to 1.0.5
Resolution set to fixed

Thank you!
----------------------------------------
Bug #1749: Reports -> IP -> Unused Subnets - System error
https://osl.uoregon.edu/redmine/issues/1749#change-3057

Author: Vadym Kalsin
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: IPManagement
Target version: 1.0.5
Resolution: fixed


When running Report - IP - Unused Subnets (or Unused Subnets (v4) got the error:
<pre>
error:  Can't locate object method "_netaddr" via package "Ipblock" at 
/usr/local/netdot/lib/Netdot/Model/Ipblock.pm line 549.
context:                ...     
545:     my ($self, $address, $prefix) = @_;
546:     my ($netaddr, $version);
547:     if ( ref($self) ){
548:     # Called as object method
549:     $netaddr = $self->_netaddr;
550:     $version = $self->version;
551:     }else{
552:     # Called as class method
553:     $self->throw_fatal("Missing required arguments when called as class 
method: address")
...     

code stack:      /usr/local/netdot/lib/Netdot/Model/Ipblock.pm:549
 /usr/local/netdot/lib/Netdot/Model/Ipblock.pm:407
 /usr/local/netdot/htdocs/reports/unused_subnets.html:21
 /usr/local/netdot/htdocs/reports/ip_reports.html:51
 /usr/local/netdot/htdocs/reports/autohandler:132
 /usr/share/perl5/HTML/Mason/Request.pm:936
 /usr/local/netdot/htdocs/masondata/obj/991023240/reports/autohandler.obj:21
 /usr/local/netdot/htdocs/autohandler:76
</pre>


-- 
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


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

Message: 6
Date: Tue, 23 Apr 2013 11:33:02 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1745] (Resolved) ipv6 addresses
        on      interfaces on nexus 7K not working
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1745 has been updated by Carlos Vicente.

Category set to DeviceManagement
Status changed from New to Resolved
Assignee set to Carlos Vicente
Target version set to 1.0.5
Resolution set to fixed

Thank you
----------------------------------------
Bug #1745: ipv6 addresses on interfaces on nexus 7K not working
https://osl.uoregon.edu/redmine/issues/1745#change-3058

Author: Wim Vandersmissen
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 1.0.5
Resolution: fixed


ipv6 addresses on vlan interfaces on nexus 7K weren't showing up
Seems like nexus is giving other values back on OID 1.3.6.1.2.1.4.34.1.5 
(ipAddressType)
The current code uses the wrong field for the ifIndex identifier. It also seems 
that for nexus the ifIndex id is always greater than 150000000

The following code works for me and fixes the issue.
<pre>
--- Device.pm     2012-12-05 17:35:01.000000000 +0100
+++ Device.pm   2013-03-27 14:56:26.000000000 +0100
@@ -1133,10 +1133,15 @@
        if ( $key =~ /^.+\.((?:\d+\.){15}\d+)$/o ) {
            $addr = $self->_octet_string_to_v6($1);
        }
-       if ( $val =~ /^(\d+)\.\d+\.\d+\.([\d\.]+)\.(\d+)$/o ) {
+       if ( $val =~ /^(\d+)\.(\d+)\.\d+\.([\d\.]+)\.(\d+)$/o ) {
            # ifIndex, type, size, prefix length
-           $iid = $1; $len = $3;
-           $pfx = $self->_octet_string_to_v6($2);
+           if ( ($1 == 1)  && ($2 > 150000000)) {
+                $iid=$2;
+            } else {
+                $iid=$1;
+            }
+           $len = $4;
+           $pfx = $self->_octet_string_to_v6($3);
        }
        if ( $iid && $addr && $pfx && $len ){
            next unless (defined $dev{interface}{$iid});
</pre>


-- 
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


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

Message: 7
Date: Tue, 23 Apr 2013 11:33:56 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1744] (Resolved) Nagios -
        Cannot  monitor a service unless the IP address is the snmp_target
        address
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1744 has been updated by Carlos Vicente.

Status changed from New to Resolved
Resolution set to fixed

Added a "monitored" field in the Ipblock table and rewrote a chunk of the 
Netdot exporter.
----------------------------------------
Bug #1744: Nagios - Cannot monitor a service unless the IP address is the 
snmp_target address
https://osl.uoregon.edu/redmine/issues/1744#change-3059

Author: Carlos Vicente
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: DeviceManagement
Target version: 1.0.5
Resolution: fixed


This was a bad assumption when the code was written. A server can bind specific 
services to specific IP addresses other than the one used for SNMP discovery.


-- 
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


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

Message: 8
Date: Tue, 23 Apr 2013 11:34:45 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1739] Utilization of DHCP
        pools
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1739 has been updated by Carlos Vicente.

Resolution set to wontfix


----------------------------------------
Feature #1739: Utilization of DHCP pools
https://osl.uoregon.edu/redmine/issues/1739#change-3060

Author: Vadym Kalsin
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: wontfix


I'm examing network documentation tool - Netdot, and I want to graph DHCP 
utilization. 

In the Feature #1645 Carlos Vicente wrote:

> ... What we do at the University is to graph the utilization of DHCP pools 
> using SNMP. This process polls the DHCP servers every 5 minutes and 
> determines more exactly how many addresses are used in the pool. This 
> requires some special scripts and configurations, which I'd be glad to share 
> outside this ticket.

Could you share this scripts and configurations?


-- 
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


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

Message: 9
Date: Tue, 23 Apr 2013 11:57:56 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1740] (Resolved) Not possible
        to give an existing ipv4 host an ipv6 address via user_management       
(and
        vice versa)
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1740 has been updated by Carlos Vicente.

Category set to DNS
Status changed from New to Resolved
Assignee set to Carlos Vicente
Target version set to 1.0.5
Resolution set to fixed

Patch applied with some modifications. Thank you!
----------------------------------------
Bug #1740: Not possible to give an existing ipv4 host an ipv6 address via 
user_management (and vice versa)
https://osl.uoregon.edu/redmine/issues/1740#change-3061

Author: Wim Vandersmissen
Status: Resolved
Priority: Normal
Assignee: Carlos Vicente
Category: DNS
Target version: 1.0.5
Resolution: fixed


When there already exists a hostname in a zone with an IPv4 address (e.g. 
host.mydomain.com IN A 1.2.3.4) it's not possible to add an ipv6 address with 
the same hostname (e.g. host.domain.com IN AAAA 2001:db8::1) via the delegated 
user_management interface (as admin it's possible)
(and vice versa, adding an ipv4 address to a hostname which already has an ipv6 
address)

Simple patch below fixes this for me
<pre>
--- Model/RR.pm 2012-12-05 17:35:01.000000000 +0100
+++ Model/RR.pm 2013-03-20 00:18:35.000000000 +0100
@@ -518,7 +518,26 @@
        unless $zone;

     if ( my $h = RR->search(name=>$argv{name}, zone=>$zone)->first ){
-       $class->throw_user($h->get_label." is already taken");
+       my $arecords=$h->a_records;
+       my $records=$arecords->{_data};
+       my $v4version=0;
+       my $v6version=0;
+       #print Dumper(@records);
+       foreach my $record (@{$records}) {
+               my @ipblocks=Ipblock->search(id=>$record->{ipblock});
+               foreach my $ipblock (@ipblocks) {
+                       if ($ipblock->version == 4) {
+                               $v4version=1;
+                       }
+                       if ($ipblock->version == 6) {
+                               $v6version=1;
+                       }
+               }
+       }
+
+       if ($v4version && $v6version) {
+               $class->throw_user($h->get_label." is already taken");
+       }
     }

</pre>


-- 
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


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

Message: 10
Date: Tue, 23 Apr 2013 11:58:19 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1739] (Closed) Utilization
        of      DHCP pools
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #1739 has been updated by Carlos Vicente.

Status changed from New to Closed


----------------------------------------
Feature #1739: Utilization of DHCP pools
https://osl.uoregon.edu/redmine/issues/1739#change-3062

Author: Vadym Kalsin
Status: Closed
Priority: Normal
Assignee: 
Category: 
Target version: 
Resolution: wontfix


I'm examing network documentation tool - Netdot, and I want to graph DHCP 
utilization. 

In the Feature #1645 Carlos Vicente wrote:

> ... What we do at the University is to graph the utilization of DHCP pools 
> using SNMP. This process polls the DHCP servers every 5 minutes and 
> determines more exactly how many addresses are used in the pool. This 
> requires some special scripts and configurations, which I'd be glad to share 
> outside this ticket.

Could you share this scripts and configurations?


-- 
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 73, Issue 8
*******************************************

Reply via email to