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: netdisco2 Scheduler not working (Oliver Gorwits)
2. report - ip inventory issue (Cuttler, Brian R (HEALTH))
3. Re: report - ip inventory issue (Hans Erasmus)
4. snmpV3 (Palermo Jansen)
--- Begin Message ---
Super, glad to hear :)
Oliver.
> On 19 Oct 2017, at 20:32, Chuck Sanderson <[email protected]> wrote:
>
> Thanks for the response, That was it a formatting, this is working for me
> now.
>
> -Chuck
>
> -----Original Message-----
> From: Oliver Gorwits [mailto:[email protected]]
> Sent: Thursday, October 19, 2017 10:30 AM
> To: [email protected]
> Subject: Re: [Netdisco] netdisco2 Scheduler not working
>
> Hi Chuck
>
>> On 2017-10-18 22:21, Chuck Sanderson wrote:
>> I have yet to get the scheduler working, everything else seems
>> functional. Any ideas?
>
> From the way your config appeared in the email, it could be that you have an
> indenting error in the file - this is a common cause of problems with YAML.
> Perhaps copy the config here and send the link:
> https://nopaste.xyz/
>
> In any case, what do you mean by the netdisco-backend "stalls" ?
>
> You should be able to run ~netdisco/bin/netdisco-backend-fg at the command
> line and see what happens. You can increase logging by adding
> "log: debug" to the config file as well.
>
> regards,
> oliver.
>
>
>>
>> BUILT USING OPEN SOURCE
>>
>> SOFTWARE
>>
>> VERSION
>>
>> APP::NETDISCO [1]
>>
>> 2.36.9
>>
>> SNMP::INFO [2]
>>
>> 3.37
>>
>> DB SCHEMA [3]
>>
>> 44
>>
>> POSTGRESQL [4]
>>
>> 9.5.8
>>
>> PERL [5]
>>
>> 5.22.1
>>
>> Here's what is in the deployment.yml, when I uncomment out the workers
>> part the netdisco-backend stalls and the netdisco-web will not start,
>> comment it back and it starts but auto scheduler/poller does not work
>>
>> # this is the schedule for automatically keeping netdisco up-to-date
>>
>> # ``````````````````````````````````````````````````````````````````
>>
>> schedule:
>>
>> discoverall:
>>
>> when: '5 7 * * *'
>>
>> macwalk:
>>
>> when:
>>
>> min: 20
>>
>> arpwalk:
>>
>> when:
>>
>> min: 50
>>
>> nbtwalk:
>>
>> when: '0 8,13,21 * * *'
>>
>> expire:
>>
>> when: '20 23 * * *'
>>
>> workers:
>>
>> pollers: 10
>>
>> tasks: 'AUTO * 2'
>>
>> sleep_time: 1
>>
>> min_runtime: 0
>>
>> max_deferrals: 10
>>
>> retry_after: '7 days'
>>
>> Thanks in advance..
>>
>> Chuck Sanderson
>> JELD-WEN Technology Services - LAN/WAN Integration Mgr
>>
>> JELD-WEN, inc.
>> Corporate Business Technology
>> [email protected]
>>
>> RELIABILITY _for_ REAL LIFEÄ
>>
>>
>>
>> Links:
>> ------
>> [1] http://netdisco.org/
>> [2] https://github.com/netdisco/snmp-info
>> [3] https://metacpan.org/module/netdisco-db-deploy
>> [4] http://www.postgresql.org/
>> [5] http://www.perl.org/
>>
>> ----------------------------------------------------------------------
>> -------- 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://lists.sourceforge.net/lists/listinfo/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://lists.sourceforge.net/lists/listinfo/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://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hello netdisco users.
I start with an apology, now that am writing you I realize I don't know exactly
what version I'm running, doesn't seem to be a button or file to tell me that,
though I am running netdisco2 rather than netdisco.
Platform is FreeBSD 9.3.
Netdisco is terrific, could hardly go a day with out, however now that I'm
moving the last of my buildings to dynamic DNS I wanted to pull an ip inventory
for the network in use there. This is the smallest building and supports only a
/23 network and I manage only 3 switches there, else I'd have probably noted
the issue sooner.
Issue is that what I ask for a report "ip inventory" and specify the network
10.57.56.0/23 I get zero results back, despite being able to see addresses in
that range when I examine the individual switches.
I'd thought I needed to modify the ~/environment/deployment.yml file, but
process of elimination makes me second guess myself on that.
Specifically, the file contains 10.57.56.0/24 in the discovery_only section,
and those nodes do not show up.
I have other network ranges that are similarly mistakes, a /24 when there
should be a /21, but all found. And I have other ranges that are not listed at
all that display correctly.
So, I'm thinking I either don't know what I'm doing in the deployment.yml file
(likely) or perhaps I have a serious problem (seems unlikely).
Removing and re-discovering one of the switches involved did not seem to make
any difference.
Thanks in advance for your help.
Brian Cuttler
Wadsworth Center
Albany, NY
--- End Message ---
--- Begin Message ---
This might seem like a silly question, but what are the IP's of the routers
containing the ARP tables for said subnet? If your router has an IP address
of 10.57.57.254 for instance, which is within the /23 but falls outside the
scope of the /24, it will not be discovered. It might also be that one of
the other segments carries a /24 route in stead of a /23 route, and this
was discovered by Netdisco previously, and because the 2 overlap, it is
being ignored? I am not sure, I just throwing out ideas here.
Regards
Hans
On Tue, 24 Oct 2017 at 22:31 Cuttler, Brian R (HEALTH) <
[email protected]> wrote:
> Hello netdisco users.
>
> I start with an apology, now that am writing you I realize I don't know
> exactly what version I'm running, doesn't seem to be a button or file to
> tell me that, though I am running netdisco2 rather than netdisco.
>
> Platform is FreeBSD 9.3.
>
> Netdisco is terrific, could hardly go a day with out, however now that I'm
> moving the last of my buildings to dynamic DNS I wanted to pull an ip
> inventory for the network in use there. This is the smallest building and
> supports only a /23 network and I manage only 3 switches there, else I'd
> have probably noted the issue sooner.
>
> Issue is that what I ask for a report "ip inventory" and specify the
> network 10.57.56.0/23 I get zero results back, despite being able to see
> addresses in that range when I examine the individual switches.
>
> I'd thought I needed to modify the ~/environment/deployment.yml file, but
> process of elimination makes me second guess myself on that.
> Specifically, the file contains 10.57.56.0/24 in the discovery_only
> section, and those nodes do not show up.
> I have other network ranges that are similarly mistakes, a /24 when there
> should be a /21, but all found. And I have other ranges that are not listed
> at all that display correctly.
>
> So, I'm thinking I either don't know what I'm doing in the deployment.yml
> file (likely) or perhaps I have a serious problem (seems unlikely).
>
> Removing and re-discovering one of the switches involved did not seem to
> make any difference.
>
> Thanks in advance for your help.
>
> Brian Cuttler
> Wadsworth Center
> Albany, NY
>
>
>
> ------------------------------------------------------------------------------
> 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://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
--- Begin Message ---
Hi,
I`m using Netdisco 2.0 with great satisfaction for several years now. Its a
real stable tool and it give you lots of information as a network Engineer.
Over the years security is gaining popularity. And most company switch to a
saver network. As-well the company where i work for.
The security advisory board had decided to switch to SNMPv3. This is no
problem, and i adjust the configuration of Netdisco.
This was a year ago.
Now they came with something new. All switches, routers, firewalls should have
there own SNMPv3 credentials.
I was thinking how to implement it in the Netdisco, But i do not have an answer
yet. Does any one have the same problem or may has a solution?
Greetings
Palermo
--- 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
