Send netdisco-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-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 netdisco-users digest..."
Today's Topics:
1. Re: report - ip inventory issue (Hans Erasmus)
2. Re: report - ip inventory issue (Cuttler, Brian R (HEALTH))
--- Begin Message ---
Hi Brian
IMHO I would rather query the ARP table of the router. Some hosts (like
standard windows machines) do not necessarily ping back if their firewall
is enabled, so in my experience I usually get the ARP table from the router
(on which the gateway of your segment is announced), as this will hold
entries for devices that have been discovered within the time frame of ARP
expiry. This has both its advantages and disadvantages. Advantage: it does
not care if the Windows machine FW is enabled, it will be discovered due to
communications between end device and router. Disadvantage: Once the ARP
entry has expired, you do not have accurate data with regards to IP's used
on that segment. Now the last point is debatable, and many admins and
engineers differ when it comes to "accuracy of data".
In my experience I have relied on the router's ARP tables as the source of
most info, from which netdisco can then run auto-discovery. Depending on
the type of routers and switches you use, you will be able to get end
device type (based on MAC OUI) and all sorts of other data, just by
querying your router.
Again, just my 2 cents.
Regards
Hans
On Wed, 25 Oct 2017 at 15:34 Cuttler, Brian R (HEALTH) <
[email protected]> wrote:
> Good morning Hans,
>
>
>
> The switches that host the end points are in the 10.56.69.0 range, the
> site router is as well.
>
> The end point switches are being discovered and display switch interface
> information that includes IPs in the range what I am trying to get an IP
> Report on. I’m thought once the interface information was included in the
> rancid database there would be enough there to generate a report on the IP
> range.
>
>
>
> If I have the switches, don’t I have the data? Do I also need to discover
> the site’s router?
>
>
>
> thank you,
>
> Brian
>
>
>
>
>
>
>
>
>
> *ATTENTION: This email came from an external source. Do not open
> attachments or click on links from unknown senders or unexpected emails.*
>
> This might seem like a silly question, but what are the IP's of the
> routers containing the ARP tables for said subnet? If your router has an IP
> address of 10.57.57.254 for instance, which is within the /23 but falls
> outside the scope of the /24, it will not be discovered. It might also be
> that one of the other segments carries a /24 route in stead of a /23 route,
> and this was discovered by Netdisco previously, and because the 2 overlap,
> it is being ignored? I am not sure, I just throwing out ideas here.
>
>
>
> Regards
>
> Hans
>
>
>
> On Tue, 24 Oct 2017 at 22:31 Cuttler, Brian R (HEALTH) <
> [email protected]> wrote:
>
> Hello netdisco users.
>
> I start with an apology, now that am writing you I realize I don't know
> exactly what version I'm running, doesn't seem to be a button or file to
> tell me that, though I am running netdisco2 rather than netdisco.
>
> Platform is FreeBSD 9.3.
>
> Netdisco is terrific, could hardly go a day with out, however now that I'm
> moving the last of my buildings to dynamic DNS I wanted to pull an ip
> inventory for the network in use there. This is the smallest building and
> supports only a /23 network and I manage only 3 switches there, else I'd
> have probably noted the issue sooner.
>
> Issue is that what I ask for a report "ip inventory" and specify the
> network 10.57.56.0/23 I get zero results back, despite being able to see
> addresses in that range when I examine the individual switches.
>
> I'd thought I needed to modify the ~/environment/deployment.yml file, but
> process of elimination makes me second guess myself on that.
> Specifically, the file contains 10.57.56.0/24 in the discovery_only
> section, and those nodes do not show up.
> I have other network ranges that are similarly mistakes, a /24 when there
> should be a /21, but all found. And I have other ranges that are not listed
> at all that display correctly.
>
> So, I'm thinking I either don't know what I'm doing in the deployment.yml
> file (likely) or perhaps I have a serious problem (seems unlikely).
>
> Removing and re-discovering one of the switches involved did not seem to
> make any difference.
>
> Thanks in advance for your help.
>
> Brian Cuttler
> Wadsworth Center
> Albany, NY
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
>
--- End Message ---
--- Begin Message ---
Reviewed with my manager. The switches are in the discover_only range, that is
the end point switches but not the site router.
I have been corrected in that discover_only is not for end use IP range
discovery, which in retrospect makes sense.
Why if the switch is being learned don’t the end point devices not show up in
IP inventory report as it does else where in my network?
thank you,
Brian
From: Cuttler, Brian R (HEALTH) [mailto:[email protected]]
Sent: Wednesday, October 25, 2017 9:35 AM
To: Hans Erasmus <[email protected]>
Cc: [email protected]
Subject: Re: [Netdisco] report - ip inventory issue
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
Good morning Hans,
The switches that host the end points are in the 10.56.69.0 range, the site
router is as well.
The end point switches are being discovered and display switch interface
information that includes IPs in the range what I am trying to get an IP Report
on. I’m thought once the interface information was included in the rancid
database there would be enough there to generate a report on the IP range.
If I have the switches, don’t I have the data? Do I also need to discover the
site’s router?
thank you,
Brian
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown senders or unexpected emails.
This might seem like a silly question, but what are the IP's of the routers
containing the ARP tables for said subnet? If your router has an IP address of
10.57.57.254 for instance, which is within the /23 but falls outside the scope
of the /24, it will not be discovered. It might also be that one of the other
segments carries a /24 route in stead of a /23 route, and this was discovered
by Netdisco previously, and because the 2 overlap, it is being ignored? I am
not sure, I just throwing out ideas here.
Regards
Hans
On Tue, 24 Oct 2017 at 22:31 Cuttler, Brian R (HEALTH)
<[email protected]<mailto:[email protected]>> wrote:
Hello netdisco users.
I start with an apology, now that am writing you I realize I don't know exactly
what version I'm running, doesn't seem to be a button or file to tell me that,
though I am running netdisco2 rather than netdisco.
Platform is FreeBSD 9.3.
Netdisco is terrific, could hardly go a day with out, however now that I'm
moving the last of my buildings to dynamic DNS I wanted to pull an ip inventory
for the network in use there. This is the smallest building and supports only a
/23 network and I manage only 3 switches there, else I'd have probably noted
the issue sooner.
Issue is that what I ask for a report "ip inventory" and specify the network
10.57.56.0/23<http://10.57.56.0/23> I get zero results back, despite being able
to see addresses in that range when I examine the individual switches.
I'd thought I needed to modify the ~/environment/deployment.yml file, but
process of elimination makes me second guess myself on that.
Specifically, the file contains 10.57.56.0/24<http://10.57.56.0/24> in the
discovery_only section, and those nodes do not show up.
I have other network ranges that are similarly mistakes, a /24 when there
should be a /21, but all found. And I have other ranges that are not listed at
all that display correctly.
So, I'm thinking I either don't know what I'm doing in the deployment.yml file
(likely) or perhaps I have a serious problem (seems unlikely).
Removing and re-discovering one of the switches involved did not seem to make
any difference.
Thanks in advance for your help.
Brian Cuttler
Wadsworth Center
Albany, NY
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
