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: Auto start Netdisco on Centos 7 ? (Nikolaos Milas)
2. Re: Auto start Netdisco on Centos 7 ? (Andy Ruhl)
3. Re: Auto start Netdisco on Centos 7 ? (o...@leferguson.com)
4. Re: Auto start Netdisco on Centos 7 ? (Oliver Gorwits)
5. Re: Tools to connect the disconnected (Oliver Gorwits)
6. Re: Tools to connect the disconnected (o...@leferguson.com)
7. Re: Tools to connect the disconnected (Oliver Gorwits)
--- Begin Message ---
On 8/10/2015 3:24 πμ, Peter Grasso wrote:
Thanks for the heads up - I generated the scripts, copied them to
/usr/bin, did a chmod +x on them and then wrote a couple of .service
scripts in /etc/systemd/system to call them. (I called them
ndweb.service and nddaemon.service)
If you can share the scripts, it may help other people looking for a
solution.
Best regards,
Nick
--- End Message ---
--- Begin Message ---
I've been told this is bad form, but I like it anyway. I just start it
with a cron job like this:
[netdisco@box ~]$ crontab -l
#Added by Andy to start netdisco at boot time
@reboot ~/bin/netdisco-web start && ~/bin/netdisco-daemon start
With systemd you get a lot more resiliency and logging, it's probably
a better way.
Andy
--- End Message ---
--- Begin Message ---
I'm on Ubuntu 15.04, which now uses system also, but I simply used the scripts
generated by netdisco, moved to init.d as netdisco-daemon, added execute, and
ran update-rc.d. The scrips on the current netdisco have the appropriate
commented headers to generate the right steps, and at least so far it seems to
work correctly on reboots, etc. It even seems to change to the proper account
not root (though I have not dug deeply to see if there are any security issues).
It all just seemed to work. I started to change to a system format, but since
it worked OOTB I just used it.
Not sure if that's relevant to centos or not, but FWIW.
Linwood
-----Original Message-----
From: Andy Ruhl [mailto:acr...@gmail.com]
Sent: Thursday, October 08, 2015 10:27 AM
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Auto start Netdisco on Centos 7 ?
I've been told this is bad form, but I like it anyway. I just start it with a
cron job like this:
[netdisco@box ~]$ crontab -l
#Added by Andy to start netdisco at boot time
@reboot ~/bin/netdisco-web start && ~/bin/netdisco-daemon start
With systemd you get a lot more resiliency and logging, it's probably a better
way.
Andy
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Many thanks to all who have contributed on this thread!
Netdisco uses an upstream module to create the init scripts, so if we
can get examples of systemd service scripts then I'd be happy to help
submit a patch.
https://metacpan.org/pod/Daemon::Control
regards,
oliver.
On 2015-10-08 07:56, Nikolaos Milas wrote:
On 8/10/2015 3:24 πμ, Peter Grasso wrote:
Thanks for the heads up - I generated the scripts, copied them to
/usr/bin, did a chmod +x on them and then wrote a couple of .service
scripts in /etc/systemd/system to call them. (I called them
ndweb.service and nddaemon.service)
If you can share the scripts, it may help other people looking for a
solution.
Best regards,
Nick
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Linwood,
On 2015-10-05 17:02, o...@leferguson.com wrote:
First, thanks for a great tool.
Many thanks :)
ASA's don't do CDP or LLDP (right?), and so there's no CORRECT way to
have it link them to a connected device.
Just for my understanding, do you mean the connected devices at the
remote site, or you want to show the ASA connected to your head office
or another site (with the Internet as a cloud)?
Has anyone written scripts to pull together this type of information
and enter manual topology connections? With several dozen small sites
with ASA's I hate doing it all by hand (and yet it may be just a bit
too little to try to write code).
If there a documented way to import this? Can you just push it in
with
SQL? (perhaps while shut down)?
There is a script which works with a text file in the older topology
file format, which you could generate from info in the database, I
guess:
https://metacpan.org/pod/distribution/App-Netdisco/bin/nd-import-topology
Note that the docs in that page are wrong for the path to the script.
It's probably something like:
~netdisco/perl5/bin/nd-import-topology
regards,
oliver.
--- End Message ---
--- Begin Message ---
> Just for my understanding, do you mean the connected devices at the remote
> site, or
>you want to show the ASA connected to your head office or another site (with
>the Internet as a cloud)?
It's a good question, and I am probably too new to adopting this to know for
sure, as I do not want to distort the true layer 2 aspect too far. But I'm
putting this at two client-of-client sites now, neither of which have any real
network documentation (nor are they likely to maintain such themselves if they
had it). There's a very definite urge to "show how everything is connected as
best you can" pushing me to try to force disconnected devices together even
though that's not exactly what this tool is for.
That file format and tool look like an easy way to import; a bit less obvious
is how to change (for example if someone deleted a tunnel). Is everything
related just in the topology table? Could I just truncate the table and
re-import to update (i.e. for example if I had something scanning Cisco config
files for tunnels and wanted to represent them this way)? I.e. is it safe to
manually manipulate the topology table as a way of dynamically updating this
from an external script?
-----Original Message-----
From: Oliver Gorwits [mailto:oli...@cpan.org]
Sent: Friday, October 09, 2015 6:44 AM
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Tools to connect the disconnected
Hi Linwood,
On 2015-10-05 17:02, o...@leferguson.com wrote:
> First, thanks for a great tool.
Many thanks :)
> ASA's don't do CDP or LLDP (right?), and so there's no CORRECT way to
> have it link them to a connected device.
Just for my understanding, do you mean the connected devices at the remote
site, or you want to show the ASA connected to your head office or another site
(with the Internet as a cloud)?
> Has anyone written scripts to pull together this type of information
> and enter manual topology connections? With several dozen small sites
> with ASA's I hate doing it all by hand (and yet it may be just a bit
> too little to try to write code).
>
> If there a documented way to import this? Can you just push it in with
> SQL? (perhaps while shut down)?
There is a script which works with a text file in the older topology file
format, which you could generate from info in the database, I
guess:
https://metacpan.org/pod/distribution/App-Netdisco/bin/nd-import-topology
Note that the docs in that page are wrong for the path to the script.
It's probably something like:
~netdisco/perl5/bin/nd-import-topology
regards,
oliver.
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
> On 9 Oct 2015, at 15:23, "o...@leferguson.com" <o...@leferguson.com> wrote:
>
> That file format and tool look like an easy way to import; a bit less
> obvious is how to change (for example if someone deleted a tunnel). Is
> everything related just in the topology table?
You'll find the web interface to this data under the Admin menu -> Manual
Topology. That should be good enough for minor amendments.
Regards
Oliver.
> Could I just truncate the table and re-import to update (i.e. for example if
> I had something scanning Cisco config files for tunnels and wanted to
> represent them this way)? I.e. is it safe to manually manipulate the
> topology table as a way of dynamically updating this from an external script?
>
>
>
> -----Original Message-----
> From: Oliver Gorwits [mailto:oli...@cpan.org]
> Sent: Friday, October 09, 2015 6:44 AM
> To: netdisco-users@lists.sourceforge.net
> Subject: Re: [Netdisco] Tools to connect the disconnected
>
> Hi Linwood,
>
>> On 2015-10-05 17:02, o...@leferguson.com wrote:
>> First, thanks for a great tool.
>
> Many thanks :)
>
>> ASA's don't do CDP or LLDP (right?), and so there's no CORRECT way to
>> have it link them to a connected device.
>
> Just for my understanding, do you mean the connected devices at the remote
> site, or you want to show the ASA connected to your head office or another
> site (with the Internet as a cloud)?
>
>> Has anyone written scripts to pull together this type of information
>> and enter manual topology connections? With several dozen small sites
>> with ASA's I hate doing it all by hand (and yet it may be just a bit
>> too little to try to write code).
>>
>> If there a documented way to import this? Can you just push it in with
>> SQL? (perhaps while shut down)?
>
> There is a script which works with a text file in the older topology file
> format, which you could generate from info in the database, I
> guess:
>
> https://metacpan.org/pod/distribution/App-Netdisco/bin/nd-import-topology
>
> Note that the docs in that page are wrong for the path to the script.
> It's probably something like:
>
> ~netdisco/perl5/bin/nd-import-topology
>
> regards,
> oliver.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
