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: ND2 strange node behaviour (Eric Miller)
2. Error while loading /home/netdisco/perl5/bin/netdisco-web-fg
(Manfred Mayer IT)
3. Re: Auto start ND2 daemons (Nikolaos Milas)
4. Re: Auto start ND2 daemons (Oliver Gorwits)
5. Re: ND2 LLDP discovery on Juniper EX series switches
(Jeroen van Ingen)
6. date/time on ND2 logs? (Joseph Bernard)
7. Re: date/time on ND2 logs? (Oliver Gorwits)
--- Begin Message ---
It is simply a matter of how often a device is communicating on the
network.
When the ageing timer drops to 15 seconds upon receipt of a TCN, the MAC
will disappear if the device does not send a frame within the 15 second
window. The end device must send a frame to populate the forwarding
table, if the switch doesn't have a device's MAC within its forwarding
table it acts like a hub and forwards the frame out all of the other
ports, so communications still work just not efficiently.
On 2014-06-01 13:40, Nikolaos Milas wrote:
On 1/6/2014 1:20 μμ, Nikolaos Milas wrote:
When I changed it to trunk, everything started running
smoothly in this network branch (I re-enabled STP on csw-astr0).
Yet, I still wonder why, when the TCN flooding situation was happening,
the "MAC disappearing" issue seemed to occur only with particular
dynamic MAC addresses and not with all (or more) of them...
Could you, Eric (you seem most knowledgeable on the subject), or anyone
else, attempt an explanation, please?
Thanks,
Nick
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi there,
I try to install Netdisco2 on a Ubuntu 12.04 machine. I have already configured
user and database, now I'm trying to start the web-frontend.
As I want to run Netdisco on the same machine as OMD (omdistro.org), port 5000
is already occupied. So a "bin/netdisco-web start" results in "Can't connect to
TCP port 5000".
According to the installation instructions
(https://metacpan.org/pod/App::Netdisco::Manual::Deployment) I tried to use
another port by starting with "bin/netdisco-web start --port=8080", but then I
get this error message in the logfile: "Error while loading
/home/netdisco/perl5/bin/netdisco-web-fg: Paths need to start with / at
/home/netdisco/perl5/lib/perl5/Plack/Builder.pm line 108"
Can someone help me, how can I solve this? Is there additional config needed
for apache, I'm not very firm with webservers.
Thanks
Mana
________________________________
Rapunzel Naturkost GmbH, Rapunzelstra?e 1, D-87764 Legau
Registergericht Memmingen HRB 14736 | Sitz der Gesellschaft: Legau
Ust Id Nr. DE 129088402
Gesch?ftsf?hrer: Joseph Wilhelm | Margit Epple | Andreas Wenning
Telefon: +49 (0)8330 / 529 - 0
--- End Message ---
--- Begin Message ---
On 7/3/2014 12:40 μμ, Nikolaos Milas wrote:
...
Would you find it an acceptable practice to add in /etc/rc.local (I'm on
CentOS 6.5):
sudo -u netdisco /home/netdisco/bin/netdisco-web start
sudo -u netdisco /home/netdisco/bin/netdisco-daemon start
...?
On 8/3/2014 5:03 μμ, Oliver Gorwits wrote: ...
...
For now, your rc.local solution is probably best. It also would allow
you to relocate the installation away from /home/netdisco if required
for any reason (by setting NETDISCO_HOME environment variable).
I would like to note that the above solution did not work (on CentOS 6.5
x86_64 running as a VM), for reasons I have not identified (at least yet).
Adding the above commands in /etc/rc.local will NOT start ND2
automatically upon reboot, whereas running these commands manually (as
root) works.
If there are any suggestions or an auto start feature has been added to
ND2 latest version (e.g. by using a custom-built start script for use in
init.d), please let me know.
Thanks,
Nick
--- End Message ---
--- Begin Message ---
Hi Nick,
I believe the version on CPAN will now create the init script for you:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Deployment.pod#Init-and-Run-Control-Scripts
Obviously this is run as root, but it drops privilege to the netdisco
user on startup automatically.
regards,
oliver.
On 2014-06-02 11:00, Nikolaos Milas wrote:
On 7/3/2014 12:40 μμ, Nikolaos Milas wrote:
...
Would you find it an acceptable practice to add in /etc/rc.local
(I'm on
CentOS 6.5):
sudo -u netdisco /home/netdisco/bin/netdisco-web start
sudo -u netdisco /home/netdisco/bin/netdisco-daemon start
...?
On 8/3/2014 5:03 μμ, Oliver Gorwits wrote: ...
...
For now, your rc.local solution is probably best. It also would
allow
you to relocate the installation away from /home/netdisco if
required
for any reason (by setting NETDISCO_HOME environment variable).
I would like to note that the above solution did not work (on CentOS
6.5
x86_64 running as a VM), for reasons I have not identified (at least
yet).
Adding the above commands in /etc/rc.local will NOT start ND2
automatically upon reboot, whereas running these commands manually
(as
root) works.
If there are any suggestions or an auto start feature has been added
to
ND2 latest version (e.g. by using a custom-built start script for use
in
init.d), please let me know.
Thanks,
Nick
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
That's odd... can you re-run the discover with debugging enabled and
provide the output? Perhaps that gives some clue as to what goes wrong.
The Layer3::Juniper class includes LLDP support, so SNMP::Info should be
able to provide Netdisco with neighbor information...
Shamelessly copied from an earlier list post by Oliver:
netdisco@server:~> INFO_TRACE=1 netdisco-do discover -D -d <switch>
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 05/30/2014 05:44 PM, Cody Wood wrote:
I have just installed ND2 and it is up and running and discovering my
cisco switches fine. It can see the neighbors of each cisco switch via
CDP. However, when I discover a Juniper switch it outputs “neigh -
CDP/LLDP not enabled!” and lists no neighbors in the web interface.
I’ve gone to the switches and confirmed that LLDP is enabled and working
correctly. From my netdisco box, I can snmpwalk to an ex series switch
and OID 1.0.8802.1.1.2.1 does show its neighbors. What am I missing?
Thanks,
*Cody Wood*
/Systems Administrator, Network Operations///
Southeastern Oklahoma State University
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Is there a way to have the messages in the log files (netdisco-web.log,
netdisco-daemon.log) to have a date/time stamp on them?
Thanks,
Joseph B.
--- End Message ---
--- Begin Message ---
Hi Joseph,
On 2014-06-02 15:54, Joseph Bernard wrote:
Is there a way to have the messages in the log files
(netdisco-web.log, netdisco-daemon.log) to have a date/time stamp on
them?
Yes, you can configure the logger_format setting in your deployment.yml
file.
The instructions are here:
https://metacpan.org/pod/Dancer::Logger::Abstract#logger_format
In fact I'll probably change it in the next release to be:
logger_format: '[%P] %U %L %m'
regards,
oliver.
--- End Message ---
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
