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. NetDisco Statistics question (Deshong, Kenneth)
2. Re: NetDisco Statistics question (Simon Hobson)
3. Re: NetDisco Statistics question (Oliver Gorwits)
4. Problem after upgrading to 2.029002 - Jobs not running
(Tobias Gerlach)
5. Re: Problem after upgrading to 2.029002 - Jobs not running
(Oliver Gorwits)
6. Re: Problem after upgrading to 2.029002 - Jobs not running
(Tobias Gerlach)
--- Begin Message ---
Oliver,
I was wanting to provide my boss with some cools stats but looking at the front
page of my NetDisco I'm a little confused by this. How can there only be
11,558 IP's but 27,974 nodes. I thought NetDisco considered a node to be
something that was attached to a switchport.
Statistics for this installation
582 devices with 29,365 interfaces using 1,328 IPs (device= Switch)
1,977 layer 2 links between devices
27,974 nodes in 39,986 entries
11,558 IPs in 31,229 entries
Statistics took 0 seconds to process.
Ken DeShong
Network Engineer
USF Health Information Systems
Desk: 813-396-9472
Fax: 813-974-5198
Amazing Things Happen When You Connect the Unconnected
-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Monday, August 04, 2014 12:41 PM
To: [email protected]
Subject: Re: [Netdisco] Web Front End - Netdisco2
Hi Ken,
On 2014-08-04 14:59, Deshong, Kenneth wrote:
> I'm not sure how I did this but I've locked myself out of the web
> front end. I can log into the server fine so how would I reset the
> usernamepassword to log back onto the website as an admin. I've
> looked
> online at the guides but I don't understand how to correct this.
There's currently no way in the supplied toolset to do this, so you
need to go to the database.
Connect to PostgreSQL ("psql -U netdisco netdisco") then run:
=> DELETE FROM users WHERE admin;
Then run ~/bin/netdisco-deploy. It will offer to create a new admin
user for you.
Hope this helps,
regards,
oliver.
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
"Deshong, Kenneth" <[email protected]> wrote:
> 11,558 IPs in 31,229 entries
I suspect that a lot of devices don't have IPs in the database. This will
happen if the MAC-IP mapping isn't in the ARP cache of a device at a point when
it's macsucked. L2 switches don't provide the information anyway (unless they
are specifically equipped and configured to snoop the traffic), only L3 devices
provide it.
So if you don't macsuck your routers, or the IP isn't in the cache when you do,
then it'll be missing from the table.
I also wonder what happens in a dynamic network (eg with a high turnover of
guests on a public WiFi) where IPs get reused. There could be several devices
associated with one IP - hence more devices than IPs.
--- End Message ---
--- Begin Message ---
Good answer Simon, thanks :)
On 2014-08-08 22:15, Simon Hobson wrote:
I also wonder what happens in a dynamic network (eg with a high
turnover of guests on a public WiFi) where IPs get reused. There
could
be several devices associated with one IP - hence more devices than
IPs.
Yes, it ends up looking like this:
346,694 nodes in 802,096 entries
140,473 IPs in 2,602,034 entries
There are other reasons too... if a MAC (node) is on more than one VLAN
it could have multiple entries and IPs. Also the expiry policy affects
how large these tables get. The above example has many wireless entries,
and a very long time before archived entry expiry (for CERT trace
reasons).
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hello,
after upgrading to ND2 2.029002 I notice that jobs aren't executed any longer.
My new "housekeeping" entries looks as follows:
schedule:
discoverall:
when:
min: 00
hour: 20
wday: 'mon,wed'
arpwalk:
when:
min: 00
hour: "00,04,08,12,16,20"
wday: "mon-sun"
macwalk:
when:
min: 00
hour: "02,06,10,14,18,22"
wday: "mon-sun"
The only thing I changed was renaming "housekeeping" to "schedule".
Seems that the word changed with this version.
Through the WebGUI the jobs are queued and stay the hole time in that
status not being executed.
Polling devices with netdisco-do from cli is working fine.
My pg_hba.conf looks as follows:
...
# TYPE DATABASE USER ADDRESS METHOD
local all postgres peer
local netdisco netdisco trust
local all all md5
host all all 127.0.0.1/32 md5
host all all ::1/128 md5
host all all 0.0.0.0/0 md5
# netdisco2 installation
host netdisco netdisco 127.0.0.1/32 md5
...
Any ideas?
Thanks a lot in advance.
Tobias
--- End Message ---
--- Begin Message ---
Hi Tobias,
Please could you start the daemon in the foreground and see if that
shows up a problem?
~/bin/netdisco-daemon stop
~/bin/netdisco-daemon-fg start
You can also set "log: debug" in the configuration file to get more
output, if nothing shows up.
regards,
oliver.
On 2014-08-11 10:07, Tobias Gerlach wrote:
Hello,
after upgrading to ND2 2.029002 I notice that jobs aren't executed
any longer.
My new "housekeeping" entries looks as follows:
schedule:
discoverall:
when:
min: 00
hour: 20
wday: 'mon,wed'
arpwalk:
when:
min: 00
hour: "00,04,08,12,16,20"
wday: "mon-sun"
macwalk:
when:
min: 00
hour: "02,06,10,14,18,22"
wday: "mon-sun"
The only thing I changed was renaming "housekeeping" to "schedule".
Seems that the word changed with this version.
Through the WebGUI the jobs are queued and stay the hole time in that
status not being executed.
Polling devices with netdisco-do from cli is working fine.
My pg_hba.conf looks as follows:
...
# TYPE DATABASE USER ADDRESS
METHOD
local all postgres peer
local netdisco netdisco trust
local all all md5
host all all 127.0.0.1/32 md5
host all all ::1/128 md5
host all all 0.0.0.0/0 md5
# netdisco2 installation
host netdisco netdisco 127.0.0.1/32 md5
...
Any ideas?
Thanks a lot in advance.
Tobias
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
When I restart the daemon I see an error in the netdisco-daemon.log file:
netdisco@server:~> tail -f logs/netdisco-daemon.log
[10121] 2014-08-11 11:40:38 warn App::Netdisco 2.029002 backend
The schema daemon is not configured at
/usr/local/netdisco/perl5/lib/perl5/Dancer/Plugin/DBIC.pm line 29.
Compilation failed in require at (eval 141) line 1.
Dancer is up to date. (1.3126)
Dancer::Plugin::DBIC is up to date. (0.2100)
2014-08-11 11:07 GMT+02:00 Tobias Gerlach <[email protected]>:
> Hello,
>
> after upgrading to ND2 2.029002 I notice that jobs aren't executed any longer.
> My new "housekeeping" entries looks as follows:
>
> schedule:
> discoverall:
> when:
> min: 00
> hour: 20
> wday: 'mon,wed'
> arpwalk:
> when:
> min: 00
> hour: "00,04,08,12,16,20"
> wday: "mon-sun"
> macwalk:
> when:
> min: 00
> hour: "02,06,10,14,18,22"
> wday: "mon-sun"
>
> The only thing I changed was renaming "housekeeping" to "schedule".
> Seems that the word changed with this version.
> Through the WebGUI the jobs are queued and stay the hole time in that
> status not being executed.
> Polling devices with netdisco-do from cli is working fine.
>
> My pg_hba.conf looks as follows:
> ...
> # TYPE DATABASE USER ADDRESS METHOD
> local all postgres peer
> local netdisco netdisco trust
> local all all md5
> host all all 127.0.0.1/32 md5
> host all all ::1/128 md5
> host all all 0.0.0.0/0 md5
> # netdisco2 installation
> host netdisco netdisco 127.0.0.1/32 md5
> ...
>
> Any ideas?
>
> Thanks a lot in advance.
>
> Tobias
--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
