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: Backend stopping, errors (Oliver Gorwits)
2. Re: NetDisco Not Recognizing IOS upgrade (Oliver Gorwits)
--- Begin Message ---
Many thanks :-)
On 2018-04-08 00:20, [email protected] wrote:
I really do not know that it was causing it, it was just among the
last things in the log (that and the missing MIB).
I will (per your subsequent note) collect more info next time.
Thank you.
Linwood
-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Saturday, April 7, 2018 7:14 PM
To: [email protected]
Subject: Re: [Netdisco] Backend stopping, errors
Hi Linwood,
Many thanks for the reports. I've put in a small fix to the next
release for the MAC address error you saw.
However I cannot see why this would stop the whole backend from
processing. The way the backend is written, each job is a worker
subprocess which quits and is respawned fresh, so even the error you
saw will just make one job die and then a new worker is started.
regards,
oliver.
On 2018-04-06 20:17, [email protected] wrote:
Running 2.39.17, snmp 3.52, db 51, perl 5.22.1, on Ubuntu 16.04.6.
A couple times now at unpredictable times I have had the backend stop
processing, though the service is running.
I don't see starts and stops in the log so I'm struggling a bit to
know what errors correspond to the actual issues, but I see thousands
of these:
Use of uninitialized value $args{"mac"} in pattern match (m//) at
/home/netdisco/perl5/lib/perl5/NetAddr/MAC.pm line 128, <__ANONIO__>
line 1.
Use of uninitialized value $node in sprintf at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 74,
<__ANONIO__> line 1.
M
And also quite a few though less of these (below), which may be
related to DLINK? And I have some DLINK's.
Not sure if either of these relate to it stopping. It stops rarely,
running days between, so leaving debug on the whole time is not an
attractive option due to log size. Any simple way to tell what's
happening absent something definitive in the log?
By the way the symptom is that jobs just stay queued, and do not
process, and do not receive errors. A service restart runs them all
almost instantly.
Linwood
Cannot find module (AGENT-GENERAL-MIB): At line 1 in (none)
MIB search path:
/home/netdisco/netdisco-mibs/3com:/home/netdisco/netdisco-mibs/adtran:/home/netdisco/netdisco-mibs/aerohive:/home/netdisco/netdisco-mibs/alcatel:/home/netdisco/netdisco-mibs/allied:/home/netdisco/netdisco-mibs/apc:/home/netdisco/netdisco-mibs/arista:/home/netdisco/netdisco-mibs/aruba:/home/netdisco/netdisco-mibs/asante:/home/netdisco/netdisco-mibs/avaya:/home/netdisco/netdisco-mibs/bluecoat:/home/netdisco/netdisco-mibs/bluesocket:/home/netdisco/netdisco-mibs/brother:/home/netdisco/netdisco-mibs/cabletron:/home/netdisco/netdisco-mibs/checkpoint:/home/netdisco/netdisco-mibs/cisco:/home/netdisco/netdisco-mibs/ciscosb:/home/netdisco/netdisco-mibs/citrix:/home/netdisco/netdisco-mibs/colubris:/home/netdisco/netdisco-mibs/cyclades:/home/netdisco/netdisco-mibs/d-link:/home/netdisco/netdisco-mibs/dell:/home/netdisco/netdisco-mibs/enterasys:/home/netdisco/netdisco-mibs/EXTRAS:/home/netdisco/netdisco-mibs/extreme:/home/netdisco/netdisco-mibs/extricom:/home/netdisco/netdisco-mibs/f5:/home/netdis
co/netdisco-mibs/force10:/home/netdisco/netdisco-mibs/fortinet:/home/netdisco/netdisco-mibs/foundry:/home/netdisco/netdisco-mibs/gigamon:/home/netdisco/netdisco-mibs/h3c:/home/netdisco/netdisco-mibs/hp:/home/netdisco/netdisco-mibs/huawei:/home/netdisco/netdisco-mibs/ibm:/home/netdisco/netdisco-mibs/juniper:/home/netdisco/netdisco-mibs/lancom:/home/netdisco/netdisco-mibs/lantronix:/home/netdisco/netdisco-mibs/liebert:/home/netdisco/netdisco-mibs/mediant:/home/netdisco/netdisco-mibs/meraki:/home/netdisco/netdisco-mibs/meru:/home/netdisco/netdisco-mibs/mikrotik:/home/netdisco/netdisco-mibs/moser-baer:/home/netdisco/netdisco-mibs/motorola:/home/netdisco/netdisco-mibs/net-snmp:/home/netdisco/netdisco-mibs/netapp:/home/netdisco/netdisco-mibs/netgear:/home/netdisco/netdisco-mibs/netscreen:/home/netdisco/netdisco-mibs/nexans:/home/netdisco/netdisco-mibs/nortel:/home/netdisco/netdisco-mibs/northerndesign:/home/netdisco/netdisco-mibs/opengear:/home/netdisco/netdisco-mibs/packetfront:/home/netd
isco/netdisco-mibs/paloalto:/home/netdisco/netdisco-mibs/pica8:/home/netdisco/netdisco-mibs/rad:/home/netdisco/netdisco-mibs/rfc:/home/netdisco/netdisco-mibs/riverbed:/home/netdisco/netdisco-mibs/ruckus:/home/netdisco/netdisco-mibs/schleifenbauer:/home/netdisco/netdisco-mibs/sentry:/home/netdisco/netdisco-mibs/sixnet:/home/netdisco/netdisco-mibs/sonicwall:/home/netdisco/netdisco-mibs/tplink:/home/netdisco/netdisco-mibs/trapeze:/home/netdisco/netdisco-mibs/vmware:/home/netdisco/netdisco-mibs/xirrus
----------------------------------------------------------------------
-------- 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://sourceforge.net/p/netdisco/mailman/netdisco-users/
------------------------------------------------------------------------------
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://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Jason
On 2018-03-29 15:47, Jason Garrett wrote:
Is it necessary to delete and re-discover devices after an IOS
upgrade, or should Netdisco recognize that automatically?
Indeed, Netdisco should pick up the OS change during discover (daily)
automatically.
When you upgraded, did the SNMP community change? If there are two valid
SNMP community strings for a device (with different view acls), Netdisco
can get stuck on the wrong one and then the only fix is to delete the
device. That's the only situation I can think of when Netdisco would
fail to gather some data from a device.
If it happens again, please run "netdisco-do discover -d 1.2.3.4 -DI"
from the command line and send me the output.
Many thanks,
regards,
oliver.
I have upgraded the IOS on a couple of Cisco 3560-X switches. The
following day I checked, and NETDISCO still showed them with the old
IOS version. I tried to run a discover process on them and waited yet
another day, but it still showed the old version. I went ahead and
deleted the switch and then re-discovered it and it now shows the
correct version.
Is it necessary to delete and re-discover devices after an IOS
upgrade, or should Netdisco recognize that automatically?
Thanks!
Jason Garrett
Diocese of Lincoln Schools
Education Technology: (402) 473-0600
Email: [email protected]
------------------------------------------------------------------------------
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://sourceforge.net/p/netdisco/mailman/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
