Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
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
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. problem with IP report for a particular subnet
(Cuttler, Brian R (HEALTH))
--- Begin Message ---
We are running NetDisco on a Ubuntu 22.04.4 LTS (Jammy Jellyfish)
[cid:image001.png@01DBFCAF.6AA75870]
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?
[cid:image002.png@01DBFCBA.4BA32020]
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
brian.cutt...@health.ny.gov<mailto:brian.cutt...@health.ny.gov>
518 486-1697
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
