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. systemd script (was: Re: Netdisco2 systemd CentOS 7 or    other
      OS HowTo) (Oliver Gorwits)
   2. Re: systemd script (was: Re: Netdisco2 systemd CentOS 7   or
      other OS HowTo) (Stuart Kendrick)
   3. Netdisco v2 discovery help (Screaming Trees)
   4. Re: Issue with H3C/HP 5130 Switches (Muris)
--- Begin Message ---

Thanks Aurelien! I will see if I can somehow incorporate this into the docs.

Another user was recently asking about systemd scripts (Stuart Kendrick I believe) so this may be immediately useful to some. I've changed the subject to help the search.

regards,
oliver.

On 2016-06-08 13:53, Aurelien Guerson wrote:
To help everybody

---------------------------

netdisco2 was installed under /opt/netdisco

netdisco user from /etc/passwd :
netdisco:x:1000:1000::/opt/netdisco:/bin/bash

For security reasons : in "/etc/ssh/sshd_config" you need this line
"DenyUsers netdisco"

---------------------------

touch /etc/systemd/system/netdiscoweb.service

vim /etc/systemd/system/netdiscoweb.service

---------------------------

[Unit]
Description=Netdisco Web Service
After=network.target

[Service]
Type=forking
User=netdisco
Group=netdisco
ExecStart=/opt/netdisco/perl5/bin/netdisco-web start
ExecStop=/opt/netdisco/perl5/bin/netdisco-web stop
Restart=on-abort

[Install]
WantedBy=multi-user.target

---------------------------

touch /etc/systemd/system/netdiscodaemon.service

vim /etc/systemd/system/netdiscodaemon.service

---------------------------

[Unit]
Description=Netdisco Daemon Service
After=network.target netdiscoweb.service
Requires=netdiscoweb.service

[Service]
Type=forking
User=netdisco
Group=netdisco
ExecStart=/opt/netdisco/perl5/bin/netdisco-daemon start
ExecStop=/opt/netdisco/perl5/bin/netdisco-daemon stop
Restart=on-abort

[Install]
WantedBy=multi-user.target

---------------------------

chmod 644 /etc/systemd/system/netdiscoweb.service

chmod 644 /etc/systemd/system/netdiscodaemon.service

chown root:root /etc/systemd/system/netdiscoweb.service

chown root:root /etc/systemd/system/netdiscodaemon.service

systemctl enable netdiscoweb.service

systemctl enable netdiscodaemon.service

systemctl start netdiscoweb.service

systemctl start netdiscodaemon.service

---------------------------

Think to use "systemctl daemon-reload" if systemd scripts were already
created

---------------------------

Regards,

aguerson

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e

_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users



--- End Message ---
--- Begin Message ---
Ahhh, "Type=forking" ... that's what I was missing.  Thank you Aurelien

FWIW:  here are my versions of the /etc/system/system files.  Oliver, you may 
want to tweak the names of the files, and their Description lines, to better 
fit into your naming nomenclature.

cat /etc/system/system/netdisco-daemon.service
[Unit]
Description=Netdisco Device Management Back-End
AssertFileIsExecutable=/home/netdisco/bin/netdisco-daemon
After=syslog.target network-online.target

[Service]
Type=forking
ExecStart=/home/netdisco/bin/netdisco-daemon start
ExecStop=/home/netdisco/bin/netdisco-daemon stop
Restart=on-failure
RestartSec=60
User=netdisco

[Install]
WantedBy=multi-user.target


cat /etc/system/system/netdisco-daemon.service
[Unit]
Description=Netdisco Device Management Front-End
AssertFileIsExecutable=/home/netdisco/bin/netdisco-web
After=syslog.target network-online.target

[Service]
Type=forking
ExecStart=/home/netdisco/bin/netdisco-web start
ExecStop=/home/netdisco/bin/netdisco-web stop
Restart=on-failure
RestartSec=60
User=netdisco

[Install]
WantedBy=multi-user.target


--sk

-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]] 
Sent: Wednesday, June 08, 2016 6:32 AM
To: [email protected]
Subject: [Netdisco] systemd script (was: Re: Netdisco2 systemd CentOS 7 or 
other OS HowTo)


Thanks Aurelien! I will see if I can somehow incorporate this into the docs.

Another user was recently asking about systemd scripts (Stuart Kendrick I 
believe) so this may be immediately useful to some. I've changed the subject to 
help the search.

regards,
oliver.

On 2016-06-08 13:53, Aurelien Guerson wrote:
> To help everybody
> 
> ---------------------------
> 
> netdisco2 was installed under /opt/netdisco
> 
> netdisco user from /etc/passwd :
> netdisco:x:1000:1000::/opt/netdisco:/bin/bash
> 
> For security reasons : in "/etc/ssh/sshd_config" you need this line 
> "DenyUsers netdisco"
> 
> ---------------------------
> 
> touch /etc/systemd/system/netdiscoweb.service
> 
> vim /etc/systemd/system/netdiscoweb.service
> 
> ---------------------------
> 
> [Unit]
> Description=Netdisco Web Service
> After=network.target
> 
> [Service]
> Type=forking
> User=netdisco
> Group=netdisco
> ExecStart=/opt/netdisco/perl5/bin/netdisco-web start 
> ExecStop=/opt/netdisco/perl5/bin/netdisco-web stop Restart=on-abort
> 
> [Install]
> WantedBy=multi-user.target
> 
> ---------------------------
> 
> touch /etc/systemd/system/netdiscodaemon.service
> 
> vim /etc/systemd/system/netdiscodaemon.service
> 
> ---------------------------
> 
> [Unit]
> Description=Netdisco Daemon Service
> After=network.target netdiscoweb.service Requires=netdiscoweb.service
> 
> [Service]
> Type=forking
> User=netdisco
> Group=netdisco
> ExecStart=/opt/netdisco/perl5/bin/netdisco-daemon start 
> ExecStop=/opt/netdisco/perl5/bin/netdisco-daemon stop Restart=on-abort
> 
> [Install]
> WantedBy=multi-user.target
> 
> ---------------------------
> 
> chmod 644 /etc/systemd/system/netdiscoweb.service
> 
> chmod 644 /etc/systemd/system/netdiscodaemon.service
> 
> chown root:root /etc/systemd/system/netdiscoweb.service
> 
> chown root:root /etc/systemd/system/netdiscodaemon.service
> 
> systemctl enable netdiscoweb.service
> 
> systemctl enable netdiscodaemon.service
> 
> systemctl start netdiscoweb.service
> 
> systemctl start netdiscodaemon.service
> 
> ---------------------------
> 
> Think to use "systemctl daemon-reload" if systemd scripts were already 
> created
> 
> ---------------------------
> 
> Regards,
> 
> aguerson
> 
> ----------------------------------------------------------------------
> -------- What NetFlow Analyzer can do for you? Monitors network 
> bandwidth and traffic patterns at an interface-level. Reveals which 
> users, apps, and protocols are consuming the most bandwidth. Provides 
> multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make 
> informed decisions using capacity planning reports.
> https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> 
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic 
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning 
reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users



--- End Message ---
--- Begin Message ---
Hi all:)  I installed the latest version of netdisco a couple of days ago, 
everything went fine during the installation (at least i believe so). My work 
network consists of about 1500 cisco routers and switches. But when i run the 
discover all command i get about 250 results. It seems like the cdp discover 
doesn't work very well. Even if i use discover on a core router the cdp doesn't 
move very deep into the network. Any ideas hiw to fix this?  An idea to fix 
this would be to run a discovery command using a seed file with a list of the 
routers but since i am new to Linux i have nit idea how to write such script. :(
Thanks in advance :) 
Aris
                                          

--- End Message ---
--- Begin Message ---
Thanks for that Oliver that has helped really well :)

What about the ME3600 getting a invalid IID when it recognises a HP5130 on
a port? as per previously what i wrote.

Also I noticed PoE outputs of ports are not showing on the 5130, im
guessing something has to be tweaked on the backend for this to show on the
HP/H3c ?

Thanks in advance.

On Thu, Jun 2, 2016 at 12:37 PM, Muris <[email protected]> wrote:

> Hi Jeroen, thanks again for your help.
>
> Increasing the timeout didnt help with the bulkwalk. The HP 5130s when
> they are stacked simply dont like it, and they seem to prefer the the other
> method GETNEXT.
>
> The issue is the network is 2500+ devices, turning of bulkwalk on specific
> ones would be administrative nightmare specifying hostnames or IPs.
> Is it possible to use the vendor model name instead in the config file to
> use for GETNEXT only? For example the 5130 are listed under vendor name as
> hp513024GSFP4SFPPlusEI and hp513048GPoEPlus4SFPPlus370WEI . If its possible
> to use vendor model name, can you let me know how i would include the
> parameter in the config file? This way when it sees this model it only does
> a GETNEXT, but the rest use bulkwalk. This is for netdisco v1.
>
> And with the ME3600, yes when i do a discover and do a debug on it, it
> lists "port for IID" not resolved. Not a macsuck or arpnip, but a discover
> command on it. I think its getting some kind of invalid IID recognising the
> 5130 on those ports.
>
> On the 5130 yes the uplinks get marked as blocking marked in blue. Like I
> have 2 uplinks, in a port channel going to the ME3600. PortChannel on the
> HP they call it BridgeAggregation. The individual uplinks are marked as
> blue, but the Bridge Aggregation is normal colour. BridgeAggregation doesnt
> show the remote connected port channel, its just blank. However the
> individual interfaces the 2 uplinks show the remote Cisco correctly and
> ports, highlighted in blue however.
>
> Thanks again for your work contributing to this magnificent tool.
>
>
>
> On Mon, May 23, 2016 at 8:11 PM, Muris <[email protected]> wrote:
>
>> Thanks Jeroen, I will try that.
>> What i actually managed to do is set bulk_walk off to true, to use the
>> GETNEXT process to pull the data out instead of BULKWALK. This worked.. and
>> I was able to pull data out, i think because went slower to pull out the
>> data..
>>
>> Do you recommend using BULKWALK instead and increasing the snmp timeout
>> Value?
>>
>> Also on another note, these 5130s in stack mode, are connected to Cisco
>> ME3600 distribution switches, everything between them has LLDP enabled, but
>> on netdisco it cant get a mapping correctly from the Cisco.
>>
>> When i discover the Cisco ME3600, i get these errors
>> Port for IID:2 not resolved.
>> Port for IID:26 not resolved.
>> Port for IID:25 not resolved.
>> And these are the ports where i have the H3C/Comware switches on.
>>
>> Is there a issue with Cisco ME3600 mapping to H3C/Comware switches via
>> LLDP? Does something need to be tweaked to get it working and map it
>> correctly.
>>
>> When i look at the 5130, it is able to accurately get the interfaces from
>> the Cisco via LLDP , however it marks the ports in blue color, which is
>> blocking. But really it shouldnt be in blue as they are not blocking ports.
>>
>> Thanks again for your assistance.
>>
>
>

--- End Message ---
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to