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

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-users
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-users digest..."


Today's Topics:

   1. Netdot 1.0-git CNAME issue (Vincent Magnin)
   2. Re: Netdot 1.0-git CNAME issue (Vincent Magnin)
   3. Broken MIB Object ipAdEntIfIndex (Vincent Magnin)
   4. Re: Broken MIB Object ipAdEntIfIndex (Vincent Magnin)
   5. Re: Broken MIB Object ipAdEntIfIndex (Carlos Vicente)


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

Message: 1
Date: Wed, 12 Sep 2012 10:12:29 +0200
From: Vincent Magnin <[email protected]>
Subject: [Netdot-users] Netdot 1.0-git CNAME issue
To: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
        format="flowed"

Hi All,

I'm testing latest netdot-1.0 (from branch netdot-1.0 on  
https://github.com/cvicente/Netdot.git), and, I've observed a strange  
issue when I add a CNAME to a host entry:


A random DNS Record appears after I've added the alias:
- Two DNS records are shown on my screen:
-- The expected host record (updated as expected)
-- A random DNS record
-- Order may vary.


Did someone else experienced the same?

PS: I've upgrade my database from 0.9.10 to 1.0. Maybe related (broken  
dependencies)?


Regards,


Vincent




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

Message: 2
Date: Wed, 12 Sep 2012 10:52:48 +0200
From: Vincent Magnin <[email protected]>
Subject: Re: [Netdot-users] Netdot 1.0-git CNAME issue
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
        format="flowed"

I've turned on DEBUG mode on htdocs/management/host.html. The  
following debug is shown:

> %ARGS is
>
> $VAR1 = 'page';
> $VAR2 = 'HOSTS';
> $VAR3 = 'submit';
> $VAR4 = 'save';
> $VAR5 = 'showheader';
> $VAR6 = 1;
> $VAR7 = 'RR__NEW__zone';
> $VAR8 = '2';
> $VAR9 = 'rr';
> $VAR10 = '58790';
> $VAR11 = 'RR__NEW__type';
> $VAR12 = 'CNAME';
> $VAR13 = 'RR__NEW__ttl';
> $VAR14 = '';
> $VAR15 = 'RR__NEW__name';
> $VAR16 = '53454642342';
> $VAR17 = 'RR__NEW__cname';
> $VAR18 = '6572346723.unil.ch';
> $VAR19 = 'id';
> $VAR20 = '58790';
>
>
> form_to_db returned:
>
> $VAR1 = 'RR';
> $VAR2 = {
>           'id' => {
>                     '772' => {
>                               'action' => 'INSERTED'
>                              }
>                   }
>         };


The random second DNS Record displayed is less random now:

- It's the RR element 772

But, this id is the one of the RRCNAME created.

Regards,

Vincent



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

Message: 3
Date: Wed, 12 Sep 2012 16:15:07 +0200
From: Vincent Magnin <[email protected]>
Subject: [Netdot-users] Broken MIB Object ipAdEntIfIndex
To: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
        format="flowed"

Hi,

I've some device which gives "unknown" index for SNMP object  
ipAdEntIfIndex (perl SNMP::Info->ip_index).

"unknown" means that these index do not exist in ifTable.

So, after each time I run ./updatedevice.pl, theses interface are  
deleted and re-created on Netdot 1.0.


Is it possible that Netdot ignores such values (ie. do not add an  
interface for undefined ifIndex)?


Regards,


Vincent



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

Message: 4
Date: Wed, 12 Sep 2012 16:31:23 +0200
From: Vincent Magnin <[email protected]>
Subject: Re: [Netdot-users] Broken MIB Object ipAdEntIfIndex
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
        format="flowed"

Re,

> Is it possible that Netdot ignores such values (ie. do not add an
> interface for undefined ifIndex)?

This small patch seems to solve my issue:

diff --git a/lib/Netdot/Model/Device.pm b/lib/Netdot/Model/Device.pm
index 0cf2933..bbd298f 100644
--- a/lib/Netdot/Model/Device.pm
+++ b/lib/Netdot/Model/Device.pm
@@ -1063,6 +1063,7 @@ sub get_snmp_info {
      # IPv4 addresses and masks
      #
      while ( my($ip,$iid) = each %{ $hashes{'ip_index'} } ){
+       next unless (defined $dev{interface}{$iid});
         next if &_check_if_status_down(\%dev, $iid);
         next if Ipblock->is_loopback($ip);
         next if ( $ip eq '0.0.0.0' || $ip eq '255.255.255.255' );



Regards,

Vincent



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

Message: 5
Date: Wed, 12 Sep 2012 11:11:24 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Broken MIB Object ipAdEntIfIndex
To: Vincent Magnin <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

Thank you Vincent.

The patch has now been added (for IPv6 too).


On 9/12/12 10:31 AM, Vincent Magnin wrote:
> Re,
> 
>> Is it possible that Netdot ignores such values (ie. do not add an
>> interface for undefined ifIndex)?
> 
> This small patch seems to solve my issue:
> 
> diff --git a/lib/Netdot/Model/Device.pm b/lib/Netdot/Model/Device.pm
> index 0cf2933..bbd298f 100644
> --- a/lib/Netdot/Model/Device.pm
> +++ b/lib/Netdot/Model/Device.pm
> @@ -1063,6 +1063,7 @@ sub get_snmp_info {
>       # IPv4 addresses and masks
>       #
>       while ( my($ip,$iid) = each %{ $hashes{'ip_index'} } ){
> +       next unless (defined $dev{interface}{$iid});
>          next if &_check_if_status_down(\%dev, $iid);
>          next if Ipblock->is_loopback($ip);
>          next if ( $ip eq '0.0.0.0' || $ip eq '255.255.255.255' );
> 
> 
> 
> Regards,
> 
> Vincent
> 
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
> 


-- 
cv


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

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


End of Netdot-users Digest, Vol 46, Issue 10
********************************************

Reply via email to