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. Installation Instructions (Diego Andrade)
2. Re: Installation Instructions (Oliver Gorwits)
3. Re: [Netdisco2] Problem with SNMP polling order (Oliver Gorwits)
4. Re: [Netdisco2] Problem with SNMP polling order (Oliver Gorwits)
5. Re: [Netdisco2] Problem with SNMP polling order (Tobias Gerlach)
6. Netdisco 2 Device Delete (Pavel Skovajsa)
--- Begin Message ---
Good Evening,
I'm trying to make a test of Netdisco in the company I work. I read some
instructions on how to install for diferent Distributions of Linux.
Unfortunnately I don't have know how in BSD. The far I can go is make the Web
Interface to work in the Ubuntu 13.10 but It seems the system itself does not
work.
I don't really na expert in anything and everything I do I seek for the online
documentation. In the case of Netdisco I found little hard to find the right
instructions to follow.
Does anyone can help me sending me directions on this? What would be a good
process to make it work in the Ubuntu or Debian distro?
Thank you.
Diego Andrade.
--- End Message ---
--- Begin Message ---
Hi Diego,
On 2014-01-03 15:09, Diego Andrade wrote:
I'm trying to make a test of Netdisco in the company I work. I read
some instructions on how to install for diferent Distributions of
Linux. Unfortunnately I don't have know how in BSD. The far I can go
is make the Web Interface to work in the Ubuntu 13.10 but It seems
the
system itself does not work.
It sounds like you might need to enable the cron jobs so that Netdisco
will poll your network.
You can start the process manually by running a discover against the
router on your network:
http://www.netdisco.org/readme.html#command_line_commands
netdisco -d x.x.x.x
Don't forget to set SNMP community strings in your configuration file.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi Tobias,
Thanks for using Netdisco 2 :)
On 2014-01-03 11:18, Tobias Gerlach wrote:
In future we have to deploy on all devices v3 instead of v2.
But here is the big problem, when I change the SNMP version from v2
to
v3, than ND will not try to reach the device with the v3 credentials.
Here is an example:
First, you should be able to leave snmpver unset. This option is only
useful to prevent Netdisco from ever trying SNMP v3. I guess a better
name would be "max_snmpver". The default for snmpver in Netdisco is "3"
(yes, sorry, the docs are wrong).
I think I see why version 3 might be skipped. Netdisco remembers the
last successful SNMP version used for a device, and then sets snmpver to
this when reconnecting. When you reconfigure a device from v2 to 3,
Netdisco remembers that v2 worked, and never tries v3! I've opened a bug
report for this so that it's fixed in the next release.
In the meantime I'll follow up on this email when a dev release is out
with the bug fix, so that you can install an update immediately. Sorry
about that.
regards,
oliver.
netdisco@server:~> ~/bin/netdisco-do -D discover -d 1.2.3.4
[1925] info @0.000014> discover: started at Fri Jan 3 11:54:46 2014
[1925] debug @0.284574> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @4.772507> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @8.778624> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string2
[1925] debug @12.793444> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string3
[1925] debug @16.807209> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string1
[1925] debug @20.942497> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string1
[1925] debug @24.948641> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string2
[1925] debug @28.963591> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info, comm: string3
[1925] debug @32.977029> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @36.994538> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string1
[1925] debug @41.000445> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string2
[1925] debug @45.015187> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info::Layer2::Baystack, comm: string3
[1925] debug @49.028760> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string1
[1925] debug @53.043990> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string1
[1925] debug @57.048070> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string2
[1925] debug @61.062583> [1.2.3.4] try_connect with ver: 1, class:
SNMP::Info, comm: string3
[1925] info @65.078802> discover: finished at Fri Jan 3 11:55:51
2014
[1925] info @65.078992> discover: status error: discover failed:
could not SNMP connect to 1.2.3.4/32
netdisco@server:~>
The opposite way, deactivate v3 and activate v2 on the switch, works
fine:
netdisco@server:~> ~/bin/netdisco-do -D discover -d 1.2.3.4
[2307] info @0.000015> discover: started at Fri Jan 3 12:09:49 2014
[2307] debug @0.278486> [1.2.3.4] try_connect with ver: 3, class:
SNMP::Info::Layer2::Baystack, comm: v3user:v3username
[2307] debug @0.827602> [1.2.3.4] try_connect with ver: 3, class:
SNMP::Info, comm: v3user:v3username
[2307] debug @1.024884> [1.2.3.4] try_connect with ver: 2, class:
SNMP::Info::Layer2::Baystack, comm: string1
[2307] debug @1.350217> [1.2.3.4] device - aliased as 1.2.3.4
[2307] debug @1.350614> resolving 1 aliases with max 250 outstanding
requests
[2307] debug @1.526184> [1.2.3.4] device - removed 1 aliases
[2307] debug @1.531474> [1.2.3.4] device - added 1 new aliases
...
Am I wrong with my deployment.yml config?
Thanks in advance for any ideas!
Regards
Tobias
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most
IT
organizations don't have a clear picture of how application
performance
affects their revenue. With AppDynamics, you get 100% visibility into
your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
On 2014-01-06 10:08, Oliver Gorwits wrote:
In the meantime I'll follow up on this email when a dev release is
out
with the bug fix, so that you can install an update immediately.
Sorry
about that.
A fix has been applied and a dev release pushed to CPAN. To install:
# upgrade Netdisco
~/bin/localenv cpanm install
http://cpan.metacpan.org/authors/id/O/OL/OLIVER/App-Netdisco-2.020003_003.tar.gz
# apply database schema updates
~/bin/netdisco-deploy
# restart web service
~/bin/netdisco-web restart
# restart job daemon (if you use it)
~/bin/netdisco-daemon restart
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hello Oliver,
thanks for your quick support! I could test the dev release today and
the fix works perfect!
Regards Tobias
2014/1/3 Tobias Gerlach <[email protected]>:
> Hello,
>
> I recently updated from Netdisco 1.3.2 to Netdisco 2.020002 without
> any problems so far.
> We have SNMPv3 and SNMPv2 devices as well in our network, in summary
> about ~3000.
>
> My deployment.yml looks as follows (only the SNMP relevant part):
>
> snmpver: 3
> community: []
> community_rw: []
> snmp_auth:
> -
> tag: v2cemea
> community: string1
> -
> tag: v2camerica
> community: string2
> -
> tag: v2capa
> community: string3
> -
> tag: v3global
> user: v3username
> auth:
> pass: secret
> proto: MD5
> priv:
> pass: secret
> proto: AES
>
> Discovering of a new device works fine. Doesn't matter what SNMP
> version is configured. ND starts with v3, then tries v2 community
> strings and at least again for v1.
> In future we have to deploy on all devices v3 instead of v2.
> But here is the big problem, when I change the SNMP version from v2 to
> v3, than ND will not try to reach the device with the v3 credentials.
> Here is an example:
>
> netdisco@server:~> ~/bin/netdisco-do -D discover -d 1.2.3.4
> [1925] info @0.000014> discover: started at Fri Jan 3 11:54:46 2014
> [1925] debug @0.284574> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info::Layer2::Baystack, comm: string1
> [1925] debug @4.772507> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info::Layer2::Baystack, comm: string1
> [1925] debug @8.778624> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info::Layer2::Baystack, comm: string2
> [1925] debug @12.793444> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info::Layer2::Baystack, comm: string3
> [1925] debug @16.807209> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info, comm: string1
> [1925] debug @20.942497> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info, comm: string1
> [1925] debug @24.948641> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info, comm: string2
> [1925] debug @28.963591> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info, comm: string3
> [1925] debug @32.977029> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info::Layer2::Baystack, comm: string1
> [1925] debug @36.994538> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info::Layer2::Baystack, comm: string1
> [1925] debug @41.000445> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info::Layer2::Baystack, comm: string2
> [1925] debug @45.015187> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info::Layer2::Baystack, comm: string3
> [1925] debug @49.028760> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info, comm: string1
> [1925] debug @53.043990> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info, comm: string1
> [1925] debug @57.048070> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info, comm: string2
> [1925] debug @61.062583> [1.2.3.4] try_connect with ver: 1, class:
> SNMP::Info, comm: string3
> [1925] info @65.078802> discover: finished at Fri Jan 3 11:55:51 2014
> [1925] info @65.078992> discover: status error: discover failed:
> could not SNMP connect to 1.2.3.4/32
> netdisco@server:~>
>
> The opposite way, deactivate v3 and activate v2 on the switch, works fine:
>
> netdisco@server:~> ~/bin/netdisco-do -D discover -d 1.2.3.4
> [2307] info @0.000015> discover: started at Fri Jan 3 12:09:49 2014
> [2307] debug @0.278486> [1.2.3.4] try_connect with ver: 3, class:
> SNMP::Info::Layer2::Baystack, comm: v3user:v3username
> [2307] debug @0.827602> [1.2.3.4] try_connect with ver: 3, class:
> SNMP::Info, comm: v3user:v3username
> [2307] debug @1.024884> [1.2.3.4] try_connect with ver: 2, class:
> SNMP::Info::Layer2::Baystack, comm: string1
> [2307] debug @1.350217> [1.2.3.4] device - aliased as 1.2.3.4
> [2307] debug @1.350614> resolving 1 aliases with max 250 outstanding requests
> [2307] debug @1.526184> [1.2.3.4] device - removed 1 aliases
> [2307] debug @1.531474> [1.2.3.4] device - added 1 new aliases
> ...
>
> Am I wrong with my deployment.yml config?
>
> Thanks in advance for any ideas!
>
> Regards
> Tobias
--- End Message ---
--- Begin Message ---
Hello,
is there a way on how to delete devices and their nodes from Netdisco using
the command line. I checked the netdisco-do actions, and it seems like
there is no delete function.
In the www frontend there is a red Delete button, but I do not really want
to delete 1000 devices by hand.
Regards,
Pavel Skovajsa
--- End Message ---
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
