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. Re: Resolve Names for Devices Discovered? (Brian Candler)
2. Re: IPv6 only devices (Brian Candler)
3. Re: Resolve Names for Devices Discovered? (Brian Candler)
4. Re: Resolve Names for Devices Discovered? (Carlos Vicente)
5. Re: Resolve Names for Devices Discovered? (Chip Pleasants)
----------------------------------------------------------------------
Message: 1
Date: Tue, 18 Nov 2014 20:38:54 +0000
From: Brian Candler <[email protected]>
Subject: Re: [Netdot-users] Resolve Names for Devices Discovered?
To: Chip Pleasants <[email protected]>,
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 18/11/2014 14:07, Chip Pleasants wrote:
> Is there an option to resolve names for devices discovered within subnet?
Do you mean use reverse DNS to find the name? I think that should
already happen: see 'sub assign_name' in lib/Netdot/Model/Device.pm
In the opposite direction, mapping the device (or the device's name) to
its management IP address, things are a bit clearer:
# Preference order of methods used for determining a device's main IP
# and name (devices with many IP addresses like routers).
#
# sysname - Resolve sysname. Notice this can cause undesired
# results if sysnames are not unique (i.e. with
# redundant firewalls)
# router_id - the value of ospfRouterId
# highest_ip - Highest-numbered IP address in the device
# lowest_loopback - Lowest-numbered Loopback Interface with an IP
# snmp_target - Pick address that was used to discover device
#
DEVICE_NAMING_METHOD_ORDER => [ 'snmp_target', 'sysname', 'highest_ip',
'lowest_loopback' ],
However there is more than a little black magic in all of this,
especially if you are planning to use Netdot to generate your DNS
zonefiles, given that both forward and reverse DNS are used in part of
the device discovery process.
------------------------------
Message: 2
Date: Tue, 18 Nov 2014 20:42:31 +0000
From: Brian Candler <[email protected]>
Subject: Re: [Netdot-users] IPv6 only devices
To: Rod James Bio <[email protected]>, "[email protected]"
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 18/11/2014 10:29, Rod James Bio wrote:
> I've read online that this is because of the underlying net-snmp
> package (please correct me if I am wrong). Anyway is there a
> work-around into this?
I haven't tried it, but I did just come across this code in
lib/Netdot/Model/Device.pm:
if ( defined $ip ){
if ( Ipblock->matches_v4($ip) && Ipblock->validate($ip) ){
$logger->debug(sub{"Device::_get_main_ip: Chose $ip
using naming method: $method" });
return $ip ;
}else{
$logger->debug(sub{"Device::_get_main_ip: $ip not
valid. Ignoring"});
# Keep trying
undef($ip);
}
This suggests to me that Netdot itself will only accept an IPv4 address
for management purposes.
------------------------------
Message: 3
Date: Wed, 19 Nov 2014 08:08:35 +0000
From: Brian Candler <[email protected]>
Subject: Re: [Netdot-users] Resolve Names for Devices Discovered?
To: Chip Pleasants <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
[Please remember to include the list in your reply]
On 19/11/2014 00:07, Chip Pleasants wrote:
> Yes I guess I should of been more clear. It would be awesome if once
> Netdot finds say a windows server in the server vlan in it would to a
> reverse lookup against the DNS server entry in the resolv.conf. I am
> not snmp polling the windows server it just finds it from looking at
> the switches mac/arp table. Like the ones in purple(Discovered)
So I believe it *should* be doing this. If you want to debug it, add
some print statements into sub assign_name in lib/Netdot/Model/Device.pm
to see why it's not making use of the reverse DNS.
Regards,
Brian.
------------------------------
Message: 4
Date: Wed, 19 Nov 2014 10:35:34 -0500
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Resolve Names for Devices Discovered?
To: Brian Candler <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Hi Brian,
On Nov 19, 2014, at 3:08 AM, Brian Candler <[email protected]> wrote:
> [Please remember to include the list in your reply]
>
> On 19/11/2014 00:07, Chip Pleasants wrote:
>> Yes I guess I should of been more clear. It would be awesome if once
>> Netdot finds say a windows server in the server vlan in it would to a
>> reverse lookup against the DNS server entry in the resolv.conf. I am
>> not snmp polling the windows server it just finds it from looking at
>> the switches mac/arp table. Like the ones in purple(Discovered)
> So I believe it *should* be doing this. If you want to debug it, add
> some print statements into sub assign_name in lib/Netdot/Model/Device.pm
> to see why it's not making use of the reverse DNS.
>
Device::assign_name() only applies to discovered ?devices?, not ?Ipblocks?.
Netdot does not try to look up the DNS name of a discovered IP (e.g. from ARP).
This would be tricky because Netdot can be used as the source of DNS
information, so assigning names to IP addresses based on the state of DNS at
polling time could be problematic.
cv
------------------------------
Message: 5
Date: Wed, 19 Nov 2014 10:49:20 -0500
From: Chip Pleasants <[email protected]>
Subject: Re: [Netdot-users] Resolve Names for Devices Discovered?
To: Carlos Vicente <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID:
<CAJq5ATrnOviO_EFiUU=nCngi=mrzwtace2u+u3mdah68k4l...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Carlos,
If I configure bind as a secondary server and doing zone transfer for the
reverse zone populate the discovered hosts?
-Chip
On Wed, Nov 19, 2014 at 10:35 AM, Carlos Vicente <[email protected]>
wrote:
> Hi Brian,
>
> On Nov 19, 2014, at 3:08 AM, Brian Candler <[email protected]> wrote:
>
> > [Please remember to include the list in your reply]
> >
> > On 19/11/2014 00:07, Chip Pleasants wrote:
> >> Yes I guess I should of been more clear. It would be awesome if once
> >> Netdot finds say a windows server in the server vlan in it would to a
> >> reverse lookup against the DNS server entry in the resolv.conf. I am
> >> not snmp polling the windows server it just finds it from looking at
> >> the switches mac/arp table. Like the ones in purple(Discovered)
> > So I believe it *should* be doing this. If you want to debug it, add
> > some print statements into sub assign_name in lib/Netdot/Model/Device.pm
> > to see why it's not making use of the reverse DNS.
> >
>
>
> Device::assign_name() only applies to discovered ?devices?, not
> ?Ipblocks?. Netdot does not try to look up the DNS name of a discovered IP
> (e.g. from ARP).
>
> This would be tricky because Netdot can be used as the source of DNS
> information, so assigning names to IP addresses based on the state of DNS
> at polling time could be problematic.
>
> cv
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20141119/32efd7e3/attachment-0001.html
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 72, Issue 6
*******************************************
