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 - Feature #1717] Name management when fetching arp
cache with CLI ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Thu, 7 Mar 2013 08:34:59 -0800
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1717] Name management when
fetching arp cache with CLI
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1717 has been updated by Nicolas Leseignoux.
File name.patch added
Hello,
Here's a quick patch file for using "show names" before using a reverse lookup.
Hopes this will helps understanding the problem.
Thanks for developping netdot :)
----------------------------------------
Feature #1717: Name management when fetching arp cache with CLI
https://osl.uoregon.edu/redmine/issues/1717#change-3046
Author: Nicolas Leseignoux
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
Hi,
I noticed that somes hosts were not added to the arp cache when fetching arp
cache from my Cisco ASA 5510 with CLI. When running update_devices.pl manually
I noticed that the script could not resolve some objects because these objects
were not fqdn. I searched inside the CiscoFW.pm file and found that effectively
the script was trying to call the "Netdot->dns->resolve_name" function and if
it fails there is an "cannot resolve ..." error.
Objects can also be defined statically with the "name" ios command, and names
can be fetched with the "show names" command.
Since names can also be defined locally and fetched from cli, should not the
name resolution process be based first on the local definition of names and if
it fails on dns resolution ?
I've written a quick patch for this but would like your views on this subject
before submitting it...
--
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 72, Issue 3
*******************************************
