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: Netdisco 2 - port name problem (Jeroen van Ingen)
2. Netdisco doesn?t use new snmp settings, tries to connect with
old settings (Sebastian R?sch)
3. suggest_guest (Stuart Kendrick)
4. Re: [Ext] Netdisco doesn?t use new snmp settings, tries to
connect with old settings (Jim Glassford)
--- Begin Message ---
Hi Edward,
While I understand and, to some level, share your opinion that "if the
[snmp] query fails or times-out, then it should fail <PERIOD> and NOT
write bad data to the database", I don't see (yet) how that could be
implemented in Netdisco within reasonable amount of time.
The thing is: Netdisco and SNMP::Info do their best to collect as much
data as possible. It depends on the device what is returned and what
not. A timeout on a specific SNMP operation doesn't necessarily mean
that there's an error condition and the collected data from the device
is "bad". If a device doesn't return interface names, descriptions,
module info or whatever, we won't store it; if it does on the next poll,
it's saved.
If you have an idea how exactly we should deal with such unreliable
responses without breaking anything for existing deployments, please do
let us know. Patches are always welcome.
In the mean time, I'm afraid that I don't have any more insights... both
ND1 and ND2 behave the same wrt SNMP timeouts; both have similar config
options regarding SNMP version, SNMP timeouts and whether or not to use
bulkwalk... and the data going into Netdisco is usually the same quality
as what you'd get by using snmpwalk/snmpbulkwalk and storing the
returned data.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 04/22/2016 05:09 PM, Edward Vopata wrote:
Yes. ND1 and ND2 are on separate host, separate databases.
The SNMP versions are fairly consistent between the list of hosts.
Primarily SNMP version 2, some version 1.
The timeout values are probably different between ND1 and ND2.
I've tired adjusting the timeout values, but I haven't had much success.
ND1:
snmptimeout = 1000000
ND2:
## Timeout = -t 20 ??
snmptimeout: 20000000
snmpretries: 3
snmpver: 2
Bulkwalk:
snmpbulkwalk -v2c -t 1 -c {comm} {host} .1
-- Timeout
snmpbulkwalk -v2c -t 2 -c {comm} {host} .1
-- Completes
snmpbulkwalk -v2c -t 10 -c {comm} {host} .1
-- Completes
But what really bothers me is that, if the query fails or times-out,
then it should fail <PERIOD>
and NOT write write bad data to the database.
--- End Message ---
--- Begin Message ---
Hi all,
I´m running netdisco v2.033003. For some of the devices I changed the snmp
version to v3. Now netdisco still remembers, that it already connected
successfully to the devices with v2.
Exactly the same problem as here:
https://sourceforge.net/p/netdisco/mailman/message/31821783/
How can I force netdisco to use the new settings from my deployment file?
Best Regards
Sebastian
--- End Message ---
--- Begin Message ---
I was imagining that adding the following to ~/environments/deployment.yml
# Enable this to display a banner suggesting to log in with a guest account.
# The username and password of this account must both be "guest".
suggest_guest: true
would add text to the login screen, something like "Guest access is available
by entering username 'guest' and password 'guest'"
I still see:
Welcome to Netdisco
Netdisco is an Open Source management tool designed for network administrators
Is there another step I would take to add suggestive text to the login screen?
App::Netdisco 2.033006
--sk
--- End Message ---
--- Begin Message ---
Hi Sebastian,
I am sure there are better ways but I comment out the non V3 community
strings, do a discover of the device/devices from the CLI. Will see
timeouts on the discover for last used community strings until disco
tries V3, then it remembers the V3 afterwards. Then I will un-comment
out the community strings afterwards.
best!
jim
On 5/3/2016 6:37 AM, Sebastian Rösch wrote:
Hi all,
I´m running netdisco v2.033003. For some of the devices I changed the
snmp version to v3. Now netdisco still remembers, that it already
connected successfully to the devices with v2.
Exactly the same problem as here:
https://sourceforge.net/p/netdisco/mailman/message/31821783/
How can I force netdisco to use the new settings from my deployment file?
Best Regards
Sebastian
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
