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: problem with IP report for a particular subnet
      (Oliver Gorwits)
--- Begin Message ---
Hi Brian

For IP Inventory or anything related to IP addresses really, Netdisco uses
the arpnip job (not the macsuck one you mentioned). Have you tried running
that against the firewalls?

Usually the arpnip is run against the default router/gateway for the
network (which may be the firewall). If you think something is wonky, try
running with debug at the command line to see any error:

~netdisco/bin/netdisco-do arpnip -d x.x.x.x -D

You can also add --force to that, which skips some sanity checks and
sometimes allows difficult devices to work with netdisco.

regards
Oliver.

On Fri, 25 Jul 2025 at 21:32, Cuttler, Brian R (HEALTH) via netdisco-users <
[email protected]> wrote:

> Netdisco user community,
>
>
>
> I modified our FW, enabled SNMP for the FW’s IP allowing access to
> Netdisco’s IP address.
> # netdisco-do macwalk is now successful when -d is the interface of either
> subnet, or the IP of the active or inactive FW.
>
>
> We also updated the database, revision was out of date, that problem is
> now also corrected.
> (As reported by the netdisco-do macwalk command).
>
> However the IP Inventory for the two subnets has not been updated.
> I’d thought running netdisco-do and running data gathering from the Admin
> tab would have done so, but something else must still be incorrectly setup.
>
>
>
> Thanks for any advice you can give,
>
>
>
> Brian
>
>
>
>
>
> *From:* Cuttler, Brian R (HEALTH) via netdisco-users <
> [email protected]>
> *Sent:* Thursday, July 24, 2025 4:45 PM
> *To:* [email protected]
> *Cc:* Hefner, Joseph (HEALTH) <[email protected]>
> *Subject:* [Netdisco] problem with IP report for a particular subnet
>
>
>
> *ATTENTION: This email came from an external source. Do not open
> attachments or click on links from unknown senders or unexpected emails.*
>
>
>
> We are running NetDisco on a Ubuntu 22.04.4 LTS (Jammy Jellyfish)
>
>
>
> Works great, have used it for years, love it.
>
> But I have one subnet that I can’t get an IP inventory on. It worked in
> the past and I’m not sure when it stopped working.
> I have current information for the router IPs for the subnet (primary and
> secondary IP addresses), and I have a few hosts with historical
> information, that is records 8+ years old but nothing else is displayed,
> neither current nor old.
>
> I’m unclear on when I stopped being able to scan/update the subnet, a /24
> network. Other networks on the same switches are reporting as expected,
> that is other /24 networks, different vlans on the same switches.
> And I’m not having issues with other networks/vlans at my other campuses.
>
> I am seeing SNMP to the devices in the IP range as returning zero
> bytes/zero packets, but the traffic is allowed.
> We did make several changes over time, the switches were all replaced (but
> they were replaced on all campuses), newer models, same vendor. Interface
> for the /24 is on the FW rather than a router or aggregation stack, but
> that is also true of another IP range on the FW, though they differ in that
> the one that is failing is local to the FW, on-campus, and the one that
> isn’t working is remote, via tunnel to the remote site.
>
>
>
> How is this information collected?
>
>
>
> Doing a little more comparison I’m seeing a second parallel issue, I
> wonder if this isn’t somehow FW related but I’ve no idea how/why.
> ICMP port unreachable when discovering a node I can ping.
>
> I have no issues when I “discover” the switches themselves, so I’m not at
> all certain that discovering the IP range by discovering the /24 network is
> an issue.
>
> Confused and clearly in need of a pointer.
> Your help is appreciated.
>
>
>
> Thank you,
>
> Brian
>
>
>
> Brian Cuttler, System and Network Administration
>
> Wadsworth Center, NYS Department of Health
>
> Albany, NY 12201 POB 509
>
> [email protected]
>
> 518 486-1697
>
>
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>

--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to