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: Netdisco2 sometimes misses connected hosts data & SSH
      Collector (Muris)
   2. Re: [EXTERNAL] Re: NetDisco 2 Web front end not working
      (Edward Vopata)
--- Begin Message ---
Hi Oliver, I will get those details for you as soon as I get a chance to work 
through it.

On 30/6/17, 6:43 pm, "Oliver Gorwits" <[email protected]> wrote:

    Hi Muris
    
    On 2017-06-24 19:34, Muris wrote:
    > Here is my exact problem as I have spent 2 days analysing it, as it
    > took me ages to figure out whats happening with the large amount of
    > devices, lets say I have this setup at the moment:
    
    If you can reliably reproduce the problem with Switch1 and CoreSwitch1, 
    then please would you email me the output of the following commands:
    
    ~netdisco/bin/netdisco-do discover -DI -d Switch1
    ~netdisco/bin/netdisco-do macsuck -DI -d Switch1
    ~netdisco/bin/netdisco-do discover -DI -d CoreSwitch1
    ~netdisco/bin/netdisco-do macsuck -DI -d CoreSwitch1
    ~netdisco/bin/netdisco-do discover -DI -d Switch1
    ~netdisco/bin/netdisco-do macsuck -DI -d Switch1
    
    ...so that is, the same order you describe below, in steps (1), (2), 
    (3).
    
    My feeling is that the arpnip/sshcollector side of things is not 
    relevant to this case. Those two processes update ARP entries, but ARP 
    data lives in a separate table (node_ip) and does not refer directly to 
    switch ports. It is the discover and macsuck processes that control 
    Netdisco's understanding of "uplink" and nodes on ports.
    
    I advise you stop the backend daemon (netdisco-backend) during the test, 
    so you don't have interference. For info, the code where Netdisco checks 
    "uplink" status and assigns nodes to ports (or skips them), is roughly 
    here:
    
https://github.com/netdisco/netdisco/blob/master/lib/App/Netdisco/Core/Macsuck.pm#L359
    
    You can email me at the CPAN address used on this mail list. If you're 
    unsure, or want to check anything, join the #netdisco IRC channel on 
    Freenode.
    
    regards,
    oliver.
    
    
    > Switch1
    > CoreSwitch1
    > 
    > Between switches its setup as L2 with port channels.
    > 
    > Now for example..
    > 
    > 1)When I run a arpnip/macsuck on Switch1, everything appears fine.
    > 2)When it comes along to run a macsuck/arpnip on CoreSwitch1, the
    > arpnip/macsuck info disappears off the ports from Switch1, but instead
    > shows up on the portchannel on CoreSwitch1 that links to switch1 with
    > all the hosts from Switch1.
    > 3)Then when the next arpnip/macsuck is done on Switch1, all the data
    > appears on Switch1 ports and disappears off the CoreSwitch1 port
    > channel. Its almost like one moment its on one switch, next moment its
    > on the next, keeps swapping backwards and to when each arpnip/mac suck
    > is probed.
    > So all mac/arp comes on the port channel on core switch, then
    > released, on, then released , depending when each probe is done.
    > Switch1 shows data on and off on each probe.
    > 
    > If all the data is appearing correctly on Switch1 on all the ports,
    > how can I prevent the uplink on CoreSwitch1 show all the arp/mac when
    > its polled. Ive been trying for hours looking through the
    > documentation how to prevent this occurring, but didn’t find anything.
    > 
    > Its almost like I need something to specify its an uplink, don’t add
    > any macs/arps on this port..or I could be just missing something else
    > im not seeing.
    > 
    > Thanks Muris
    > 
    > 
    > On 24/6/17, 6:57 pm, "Oliver Gorwits" <[email protected]> wrote:
    > 
    >     Hi Muris
    > 
    >     Please can you describe in a little more detail what's missing from 
    > the
    >     web interface - is it the MAC addresses of nodes on the ports, or 
    > the IP
    >     addresses of those nodes, or the neighbor relations to other 
    > devices?
    >     Each of these is gathered by a different process.
    > 
    >     You could try slowing down the pollers by setting sleep_time:
    > 
    >     workers:
    >        tasks: 'AUTO * 4'
    >        sleep_time: 2
    > 
    >     This makes each worker pause a little after it polls (the default 
    > is one
    >     second). If your problem is UDP overload on your server then it 
    > might
    >     help.
    > 
    >     regards,
    >     oliver.
    > 
    >     On 2017-06-23 11:37, Muris wrote:
    >     > Hi All,
    >     >
    >     > I would like to say thanks to the person who came up with the SSH
    >     > Collector for Nexus/ASA devices its really awesome and working 
    > well.
    >     > Can it also connect via telnet ?
    >     >
    >     > I have come up with a problem, as i have around 3000 devices, for 
    > some
    >     > reason the macksuck and arp, on the automatic arpnips/walks dont 
    > fully
    >     > populate the data for a switch, when i go into the switch some 
    > ports
    >     > show up but blanks next to them on connected devices..
    >     >
    >     > However, if i manually force a discover/arpnip/macwalk through 
    > the
    >     > webinterface the data populates straight away.
    >     >
    >     > Is there any reason for this? How can it completely do it 
    > automated
    >     > without me refreshing a device manually? (Well the 
    > netdisco-backend
    >     > should be doing it but some reason some data dissapears when
    >     > displayed)
    >     >
    >     > I was thinking the SSH Collector of arps maybe could be 
    > conflicting
    >     > with netdisco arps to populate data...not sure..but at the moment
    >     > needing the ssh collector due to mpls and nexus with vrfs etc.
    >     >
    >     > To cater for this many devices, i have 8 CPUs set on a Xeon 
    > machine
    >     > with 16gb ram, and running the backend worker on AUTO * 4 in
    >     > deployment config.
    >     >
    >     > Postgresql is optimised with pgtune, and running latest netdisco
    >     > version released 22/06/17
    >     >
    >     > Any troubleshooting/recommendations would be appreciated :)
    >     >
    >     > Thankyou, Muris
    >     >
    >     >
    >     >
    > 
------------------------------------------------------------------------------
    >     > Check out the vibrant tech community on one of the world's most
    >     > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    >     >
    >     > _______________________________________________
    >     > Netdisco mailing list
    >     > [email protected]
    >     > https://lists.sourceforge.net/lists/listinfo/netdisco-users
    > 
    > 
    > 
    > 
    > 
    > 
    > 
------------------------------------------------------------------------------
    > Check out the vibrant tech community on one of the world's most
    > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    > _______________________________________________
    > Netdisco mailing list
    > [email protected]
    > https://lists.sourceforge.net/lists/listinfo/netdisco-users
    
    
    





--- End Message ---
--- Begin Message ---

No. I did not get anything about accepting connection.

Attached is the results for the command.

Also, I am attaching a sanitized copy of my config file.

-- Ed

On 07/05/17 17:10, Oliver Gorwits wrote:
Hi Edward

What happens when you stop the processes and then run:

DBIC_TRACE=1 ~netdisco/bin/localenv plackup bin/netdisco-web-fg

(ignore the Twiggy error!)

Does it say "accepting connections..." ?

regards,
oliver.

On 2017-07-05 22:41, Edward Vopata via netdisco-users wrote:
The Web front end on my NetDisco 2 has stopped working:

NetDisco information
-----------------------------
OS            : Ubuntu 16.04.2 LTS
Perl          : v5.22.1
App::NetDisco : 2.036005
DB Schema     : 44
SNMP::Info    : 3.36
Apache        : 2.4.18
Net-SNMP      : 5.7.3
PostgreSQL    : 9.5.7
 I have restarted the netdisco-backend and the netdisco-web processes.
 However, the netdisco-web process doesn't look right.

     netdisco  4202     1  0 16:27 ?        00:00:00
netdisco-backend
     netdisco  4203  4202  0 16:27 ?        00:00:00
[perl] <defunct>
     netdisco  4359     1  0 16:33 ?        00:00:00
perl /opt/NetDisco/netdisco/bin/netdisco-web start
     netdisco  4360  4359  0 16:33 ?        00:00:00
[starman] <defunct>

 And 'netstat -tan' is NOT showing port 5000.

 Please advise.

 Ed Vopata


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

% echo $NETDISCO_HOME
/opt/NetDisco/netdisco

% echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/NetDisco/netdisco/bin:/opt/NetDisco/tools/sbin


% DBIC_TRACE=1 localenv netdisco-web-fg 
[24541] 2017-07-06 13:07:46  warn App::Netdisco 2.036005 web
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Inventory
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::PortVLANMismatch
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::PortAdminDown
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::PortBlocking
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::PortMultiNodes
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::PortSsid
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::PortUtilization
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::ApChannelDist
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::ApClients
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::ApRadioChannelPower
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::HalfDuplex
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::DeviceAddrNoDNS
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::DeviceByLocation
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::InventoryByModelByOS
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::DeviceDnsMismatch
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::DevicePoeStatus
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::DuplexMismatch
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::IpInventory
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::ModuleInventory
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::Netbios
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::NodeMultiIPs
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::NodeVendor
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::NodesDiscovered
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::SsidInventory
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::VlanInventory
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::SubnetUtilization
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Report::PortLog
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::JobQueue
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::Topology
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::PollerPerformance
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::PseudoDevice
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::SlowDevices
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::UndiscoveredNeighbors
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::OrphanedDevices
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::DuplicateDevices
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::TimedOutDevices
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::UserLog
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::AdminTask::Users
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Search::Device
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Search::Node
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Search::VLAN
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Search::Port
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Device::Details
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Device::Ports
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Device::Modules
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Device::Neighbors
[24541] 2017-07-06 13:07:47 debug loading Netdisco plugin 
App::Netdisco::Web::Plugin::Device::Addresses
SELECT me.version, me.installed 
  FROM dbix_class_schema_versions me 
WHERE 1 = 0
SELECT me.version 
  FROM dbix_class_schema_versions me 
ORDER BY installed DESC 
  LIMIT '1'
SELECT me.id, me.creation, me.a_session 
  FROM sessions me 
WHERE me.id = 'dancer_session_cookie_key'

Attachment: deployment.yml
Description: application/yaml


--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to