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. Re: Netdisco doesn?t use new snmp settings, tries to connect
with old settings (Sebastian R?sch)
2. Re: Netdisco doesn?t use new snmp settings, tries to connect
with old settings (Oliver Gorwits)
3. netdisco systemd service units (Stuart Kendrick)
4. Clustering or replication of Netdisco v2 servers?
(Lavin, Michael (ITS))
--- Begin Message ---
Hello Oliver,
indeed, it is working.... I didn´t remember, that I used the force_snmpv2
option for some networks.....
Thanks!
-----Ursprüngliche Nachricht-----
Von: Oliver Gorwits [mailto:oli...@cpan.org]
Gesendet: Dienstag, 3. Mai 2016 17:50
An: netdisco-users@lists.sourceforge.net
Betreff: Re: [Netdisco] Netdisco doesn´t use new snmp settings, tries to
connect with old settings
Hi Sebastian,
On 2016-05-03 11:37, Sebastian Rösch wrote:
> 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.
>
> How can I force netdisco to use the new settings from my deployment
> file?
Jim has already replied with the workaround.
However I thought that we already patched this issue in commit
c615ba4df2848ff4be5cdb30585fe7017f80d85d from the thread you mentioned.
Netdisco should try the known community settings, then when they fail it will
try all possible configurations from SNMP version 3 down to 1 (in that order).
This means your new SNMPv3 configuration should be found and used. Please let
me know if you think this isn't the case, as we may have a regression.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Super, thanks for letting me know :)
On 2016-05-06 07:53, Sebastian Rösch wrote:
Hello Oliver,
indeed, it is working.... I didn´t remember, that I used the
force_snmpv2 option for some networks.....
Thanks!
-----Ursprüngliche Nachricht-----
Von: Oliver Gorwits [mailto:oli...@cpan.org]
Gesendet: Dienstag, 3. Mai 2016 17:50
An: netdisco-users@lists.sourceforge.net
Betreff: Re: [Netdisco] Netdisco doesn´t use new snmp settings, tries
to connect with old settings
Hi Sebastian,
On 2016-05-03 11:37, Sebastian Rösch wrote:
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.
How can I force netdisco to use the new settings from my deployment
file?
Jim has already replied with the workaround.
However I thought that we already patched this issue in commit
c615ba4df2848ff4be5cdb30585fe7017f80d85d from the thread you
mentioned.
Netdisco should try the known community settings, then when they fail
it will try all possible configurations from SNMP version 3 down to 1
(in that order). This means your new SNMPv3 configuration should be
found and used. Please let me know if you think this isn't the case,
as we may have a regression.
regards,
oliver.
------------------------------------------------------------------------------
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
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Is anyone willing to share their netdisco systemd files?
Here's mine:
[guru# cat /etc/system/system/netdisco-web.service
[Unit]
Description=Netdisco Device Management Application
AssertFileIsExecutable=/home/netdisco/bin/netdisco-web
After=syslog.target network-online.target
[Service]
Type=simple
Environment=PATH=/opt/local/bin
ExecStart=/home/netdisco/bin/netdisco-web start
ExecStop=/home/netdisco/bin/netdisco-web stop
User=netdisco
[Install]
WantedBy=multi-user.target
guru#
Regrettably, it doesn't work. I see the following in syslog:
May 11 10:44:40 guru netdisco-web: config watcher: watching
/home/netdisco/environments for updates.
May 11 10:44:40 guru netdisco-web: config watcher: sending TERM to the server
(pid:14791)...
May 11 10:44:41 guru netdisco-web: Netdisco Web
#033[32m[Stopped]#033[0m
Starting by hand works just fine:
guru> /home/netdisco/bin/netdisco-web start
Netdisco Web [Started]
config watcher: watching /home/netdisco/environments for updates.
guru>
guru> which perl
/opt/local/bin/perl
guru>
--sk
--- End Message ---
--- Begin Message ---
I work for a large organization. They have a large network. They are taking
over the networks of some smaller organizations and trying to integrate them
into our network. During the process some networks are only partially connected
to our main network. Firewalls, routing rules and overlapping NAT IP ranges
stop our Netdisco server from collecting information from these remote networks.
Some of our monitoring tools allow us to have more than one server acting as a
collector of information. We can then log onto one website and access the
information gathered by the various collectors.
Some of these collectors are placed in these unconnected networks. This allows
us to monitor these other partially consolidated networks.
Is it possible to do something similar with Netdisco? Can an instance of
Netdisco at one location send its data to an instance of Netdisco at another
location? I have heard that Postgres can replicate or sync two databases to
some extent. Is there a way to use this feature to sync different Netdisco
servers in different locations if they can communicate with each other?
Just curious really. Unless it is very simple, by the time I could implement
it, the networks would probably be consolidated.
Thanks for all the hard work. It is a great product.
--- End Message ---
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
