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: Is it possible to add the server with snmp agent enabled
to netmap/topology automaticaly? (Oliver Gorwits)
2. Re: Not all links/connection is present on netmap/topology
between devices (Oliver Gorwits)
3. Moving Netdisco 2 to another machine/OS (Andy Ruhl)
4. Re: Moving Netdisco 2 to another machine/OS (Oliver Gorwits)
5. Re: Moving Netdisco 2 to another machine/OS (Andy Ruhl)
6. Re: Moving Netdisco 2 to another machine/OS (Oliver Gorwits)
7. HTTPS Support / Netbios Filter Priority (Florian Schnelle)
8. Re: HTTPS Support / Netbios Filter Priority (Oliver Gorwits)
9. Re: Netdisco 2 equivalent of netdisco -n -D <dotted quad>
(Dan Augustine)
--- Begin Message ---
Hi Alexander,
On 2015-02-06 08:22, Alexander R wrote:
With discovered link to switch
I you have a server running SNMP you can treat it like a "device" in
Netdisco, and run a discover against it (via web or CLI).
The server will only be discovered automatically if it's running a
neighbor protocol such as LLDP and the local switch is reporting the
server as a neighbor.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi Alexander,
On 2015-02-06 09:08, Alexander R wrote:
how to configure ND2 to display all of the discovered
links/connection
between devices?
This is not configurable at the moment (although you can submit a
feature request, and/or patch). We found that if all links are
displayed, the image can be very difficult to interpret. It would be
nice to have a way to toggle this, of course.
However the static graph generation (output to PNG, etc) will show all
links, I believe. For this you'll need to install some additional
software, make the configuration in deployment.yml, and then you can use
"netdisco-do graph":
https://metacpan.org/pod/App::Netdisco::Util::Graph
https://metacpan.org/source/OLIVER/App-Netdisco-2.031004/share/config.yml#L224
https://metacpan.org/pod/distribution/App-Netdisco/bin/netdisco-do#graph
regards,
oliver.
--- End Message ---
--- Begin Message ---
Just in case someone wants to know, it's pretty simple to move Netdisco 2
to another machine.
I have to move mine soon for some uninteresting reasons, so I tested it.
Follow all of the steps from this page:
https://metacpan.org/pod/App::Netdisco
Stop before this step (don't do this step):
~/bin/netdisco-deploy
At this point, you will restore the database from your first machine using
a combination of pg_dump redirected to a file on the old one, then psql
--file= on the new one. I can elaborate if necessary.
Then continue with the Startup heading.
(Don't forget to set up/turn off your firewall, set netdisco to start at
reboot, etc, all the stuff you are doing now.)
Nice!
Andy
--- End Message ---
--- Begin Message ---
Thanks Andy, really good to know it's so straightforward :)
You might still want to run netdisco-deploy, to download the MIBs to
your new system.
Also, in case the version of Netdisco installed isn't the same as the
earlier one, you should use netdisco-deploy to reapply the schema
(idempotent).
regards,
oliver.
On 2015-02-06 20:41, Andy Ruhl wrote:
Just in case someone wants to know, it's pretty simple to move
Netdisco 2 to another machine.
I have to move mine soon for some uninteresting reasons, so I tested
it.
Follow all of the steps from this page:
https://metacpan.org/pod/App::Netdisco [1]
Stop before this step (don't do this step):
~/bin/netdisco-deploy
At this point, you will restore the database from your first machine
using a combination of pg_dump redirected to a file on the old one,
then psql --file= on the new one. I can elaborate if necessary.
Then continue with the Startup heading.
(Don't forget to set up/turn off your firewall, set netdisco to start
at reboot, etc, all the stuff you are doing now.)
Nice!
Andy
Links:
------
[1] https://metacpan.org/pod/App::Netdisco
--- End Message ---
--- Begin Message ---
On Fri, Feb 6, 2015 at 2:06 PM, Oliver Gorwits <[email protected]> wrote:
>
> Thanks Andy, really good to know it's so straightforward :)
>
> You might still want to run netdisco-deploy, to download the MIBs to
> your new system.
>
> Also, in case the version of Netdisco installed isn't the same as the
> earlier one, you should use netdisco-deploy to reapply the schema
> (idempotent).
>
Oops!
Sorry, totally forgot that netdisco-deploy does more than just apply the
schema...
So maybe the right thing to do would be:
1. Run deploy
2. Drop the database
3. Create the database (because pg_dump of a single database doesn't create
the database unless you use -C during pg_dump)
4. Restore the database
5. Re-run deploy to fix the schema?
What do you think?
Andy
--- End Message ---
--- Begin Message ---
On 2015-02-06 21:11, Andy Ruhl wrote:
Sorry, totally forgot that netdisco-deploy does more than just apply
the schema...
So maybe the right thing to do would be:
1. Run deploy
2. Drop the database
3. Create the database (because pg_dump of a single database doesn't
create the database unless you use -C during pg_dump)
4. Restore the database
5. Re-run deploy to fix the schema?
What do you think?
I would do:
1. Create and restore the database
2. Run the full installation following all steps in the docs (including
saying "yes" to all questions in netdisco-deploy)
I hope that makes sense. This is basically the same as the upgrade path
from Netdisco 1.x (i.e. pre-existing database of any schema version).
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi everyone,
first of all - GREAT PROJECT.
Is there any plan to implement HTTPS natively? Or will we be bound to use a
reverse proxy?
Another question is:
If I filter for NODES and nodes have a NETBIOS name as well as a DNS name. Is
it true that the NETBIOS name is prefered over the DNS name? Is it posible to
somehow disable NETBIOS collection?
Thanks and regards,
Florian
--- End Message ---
--- Begin Message ---
Hi Florian,
On 2015-02-11 09:44, Florian Schnelle wrote:
first of all - GREAT PROJECT.
Thanks :)
Is there any plan to implement HTTPS natively? Or will we be bound to
use a reverse proxy?
The web server in Netdisco comes from another project, and they have
only experimental support for SSL, so far. However because of the
requirement to specify certificate and key, and also listen on a
privileged port, I have a preference to let another tool (Apache, Nginx,
etc) take care of the job :-).
If you really want to try, you could look at the manual page for the
web server component, and the three SSL options (probably also the
option to change the port number to 443):
https://metacpan.org/pod/starman
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Deployment.pod#SSL-Support
Another question is:
If I filter for NODES and nodes have a NETBIOS name as well as a DNS
name. Is it true that the NETBIOS name is prefered over the DNS name?
Is it posible to somehow disable NETBIOS collection?
NetBIOS collection is enabled in the default schedule, but you can
disable it. Comment out (or remove) the following two lines from your
deployment.yml file:
nbtwalk:
when: '0 8,13,21 * * *'
Yes, the default search includes NetBIOS names as well as node DNS - I
don't think there's a way to change this, sorry. However you could log a
feature request here, if you wish:
https://sourceforge.net/p/netdisco/nd2-features/
regards,
oliver.
--- End Message ---
--- Begin Message ---
I had a chance to try out the "renumber" feature today in my lab. This will
save me a ton of time in our switch renumbering project.
Oliver, Thank you for implementing this. It's very handy!
Regards,
Dan
On Wed, Feb 4, 2015 at 5:55 AM, Oliver Gorwits <[email protected]> wrote:
> On 2015-02-02 19:58, Sckolnick, Gary wrote:
> > I'm going to add my two cents, too. Moving from ND1 to ND2, we
> > really miss being able to delete devices from the CLI. Please
> > consider this a feature request. Thank you!
>
> Gary and Dan, I've just committed the CLI delete feature to the code
> repo. It'll be in the next release.
>
> Many thanks for using Netdisco :)
>
> regards,
> oliver.
>
> p.s. working on device rename, now, as I know that's also requested.
> It's trickier, tho.
>
>
> >
> > Best regards,
> > ________________________
> > Gary Sckolnick
> > Network Engineer
> > Information Services
> > [email protected]
> > The University of Vermont Medical Center
> > UVMHealth.org/MedCenter
> > ________________________________
> > From: Dan Augustine [[email protected]]
> > Sent: Monday, February 02, 2015 13:22
> > To: Oliver Gorwits
> > Cc: [email protected]
> > Subject: Re: [Netdisco] Netdisco 2 equivalent of netdisco -n -D
> > <dotted quad>
> >
> > Hi Oliver,
> >
> > It would be great to have a way to delete from the CLI.
> >
> > I'm expected to have to delete a bunch of switches and routers when
> > their management IP changes in the coming months.
> >
> > Is there a way for Netdisco to learn the new IP address? The best
> > method I found so far was to delete-and-archive, then re-discover.
> >
> > Is there a better way?
> >
> > Regards,
> > Dan
> >
> >
> > This message and any attachments may contain information that is
> > confidential, privileged and/or protected from disclosure under state
> > and federal laws. If you received this message in error or through
> > inappropriate means, please reply to this message to notify the
> > Sender
> > that the message was received by you in error, and then permanently
> > delete this message from all storage media, without forwarding or
> > retaining a copy.
> >
> >
> >
> ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming. The Go Parallel Website,
> > sponsored by Intel and developed in partnership with Slashdot Media,
> > is your
> > hub for all things parallel software development, from weekly thought
> > leadership blogs to news, videos, case studies, tutorials and more.
> > Take a
> > look and join the conversation now.
> > http://goparallel.sourceforge.net/
> > _______________________________________________
> > Netdisco mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
