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: remote collector (Ricardo Stella)
2. Re: remote collector (Christian Ramseyer)
--- Begin Message ---
Thanks - I'm having some issues however.
Figuring I don't need the postgres server, I did not install that RPM. I
then opened up the 5432 port in the main netdisco db server, changed the
psql-hba file to allow remote access, and verified connectivity using the
psql client. I then configured the deployment.xml and added the host/port
entry for the DB.
Finally on the remote collector, I tried running netdisco-deploy except I
said No to deploy database schema. But it gets stuck after "download and
update OUI data". I also tried doing it by passing ./oui.txt as a
parameter (like for non-internet access installations).
Should I do a full install including the postgres DB, then change
deployment.xml and shut down that local DB? Or am I missing something?
TIA.
On Sat, Apr 10, 2021 at 4:55 AM Christian Ramseyer <[email protected]>
wrote:
>
>
> On 09.04.21 22:56, Ricardo Stella wrote:
> >
> > We had a site that was directly connected to us in the past that now it
> > has become a semi separate network and we no longer can directly see
> > it's devices. I found a thread where Oliver says you could run a remote
> > "netdisco-backend" and have it report to the main DB and web front end.
> >
> > If so, would the process be just do a full install but then have
> > netdisco-backend point to the main system? How would this be done? Am I
> > missing a Wiki entry here?
>
> Hi Ricardo
>
> Yes that is pretty much it, just install a second Netdisco but change
> the database: settings in it to point to the "main" database. Use
> devices_no/devices_only to distribute your networks between the two.
>
> There is a short bit about it in the wiki here:
>
>
> https://github.com/netdisco/netdisco/wiki/Install-Tips#run-multiple-poller-daemons
>
>
> Cheers
> Christian
>
--
°(((=((===°°°(((================================================
--- End Message ---
--- Begin Message ---
Hi Ricardo
Yes unfortunately we don't have a full description of the installation
of a second poller, and as you notice there are some potential questions
and variants how to do it.
On 13.04.21 06:54, Ricardo Stella wrote:
> Thanks - I'm having some issues however.
>
> Figuring I don't need the postgres server, I did not install that RPM.
> I then opened up the 5432 port in the main netdisco db server, changed
> the psql-hba file to allow remote access, and verified connectivity
> using the psql client. I then configured the deployment.xml and added
> the host/port entry for the DB.
That's spot on, the postgres server is not needed, just enough Postgres
packages to successfully connect to the main server. Sounds like that is
working for you.
>
> Finally on the remote collector, I tried running netdisco-deploy except
> I said No to deploy database schema. But it gets stuck after "download
> and update OUI data". I also tried doing it by passing ./oui.txt as a
> parameter (like for non-internet access installations).
I'm not sure why this happens, but the OUI step just copies the file
into the database, so there is no need to do that a second time and you
can just skip it.
However I think the mibs should be updated locally and kept in sync with
the main server. So the "download mibs" step is the only thing that
should succeed. Or if it doesn't, just copy the mibhome directory
(https://github.com/netdisco/netdisco/wiki/Configuration#mibhome) from
the main server.
BTW whether you do the update of the db schema also shouldn't matter,
the remote poller would just see that it's already up-to-date and not
change anything.
So once you're past the mibs step your remote netdisco should be good
to go.
To test it, the easiest way would be to discover a device from your
remote network on the command line, e.g.
netdisco-do -D discover -d 192.168.3.99
You should see errors regarding db connection etc. straight away in you
terminal, an afterwards you should be able to find the device in your
main Netdisco.
Let us know if you encounter more issues, then we can maybe also put
them in the Wiki as a guide for future readers.
Cheers
Christian
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
