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. Listing ports with connected nodes never finishes (Andy Ruhl)
2. Re: Listing ports with connected nodes never finishes
(Oliver Gorwits)
3. Re: NetDisco - ssh-collector issues with Palo Alto
(Oliver Gorwits)
4. Re: NetDisco - ssh-collector issues with Palo Alto (Caines, Max)
5. Re: Listing ports with connected nodes never finishes (Andy Ruhl)
--- Begin Message ---
I searched a bit and didn't find anything, hopefully this is a known issue.
On my larger switches (Cisco 6509, Juniper EX8208), if I click on the
"Ports" tab and I have connected devices and connected nodes checked,
the list never populates. I've let it sit for hours.
On a smaller 1U switch, I get a list back not that quickly, but it
eventually populates.
Where do I start troubleshooting?
Things I've done:
Use pgtune to tune the postgresql database
Delete and re-discover the device
vacuum the database
None of these have worked.
Andy
--- End Message ---
--- Begin Message ---
Hi Andy
On large switches with many ports and many VLANs, the current Netdisco
SQL query is definitely slow (and even broken in your case) as it tries
to retrieve so much data in one go from the database.
We could do with someone with good SQL chops taking a look at that -
maybe some correlated subqueries or common table expressions need
adding. Also we don't do paging in the UI so it gets all results and
sends them to the client in one go.
You could take a look at the number of rows in your device_port and
device_port_vlan tables to see if they look "about right" or if
something's gone wrong. Perhaps all 4095 VLANs have appeared on every
port (and could be filtered with discover_no_vlan), or something
similarly odd.
Filtering some of the stored data via config might work, but is not
ideal. Other than that, not a lot I can suggest, sorry. This is not seen
(or reported) enough for us to understand the root cause, as yet.
regards,
oliver.
On 2017-05-05 18:39, Andy Ruhl wrote:
I searched a bit and didn't find anything, hopefully this is a known
issue.
On my larger switches (Cisco 6509, Juniper EX8208), if I click on the
"Ports" tab and I have connected devices and connected nodes checked,
the list never populates. I've let it sit for hours.
On a smaller 1U switch, I get a list back not that quickly, but it
eventually populates.
Where do I start troubleshooting?
Things I've done:
Use pgtune to tune the postgresql database
Delete and re-discover the device
vacuum the database
None of these have worked.
Andy
------------------------------------------------------------------------------
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 ---
On 2017-05-04 10:20, Caines, Max wrote:
Given that ssh-collector is working on my Palo Alto, would it help if
I turned debugging on on it? I notice that there's also a commented
-out debug flag in the code for Net::OpenSSH. I could uncomment that
as well?
Sorry Max, I have no idea - I don't use the sshcollector myself and
didn't write any of the platform modules!
regards,
oliver.
Regards
Max
-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: 03 May 2017 15:05
To: Christian Ramseyer <[email protected]>; Daniel Bird
<[email protected]>; [email protected];
[email protected]
Subject: Re: [Netdisco] NetDisco - ssh-collector issues with Palo Alto
Hi all
This is not directly helpful in this case, but if anyone has the time
to
try connecting using Net::Appliance::Session (or Net::CLI::Interact) I
would appreciate the feedback.
NAS doesn't have a Palo Alto phrasebook but one of the others might
work. I am considering making a NAS-based collector for Netdisco to
take
away some of the pain exprienced in this thread.
regards,
oliver.
On 2017-05-03 14:03, Christian Ramseyer wrote:
Hi guys
After Jonathan's message, I was checking our network for a device to
try
this, but unfortunately we seem to only own every networking product
except Palo Alto :)
But I looked at it again now, the regex to capture the stuff still
seems
fine with the output both of you sent, so it either is the prompt
matching that fails or the split on the newline (which is fixed to
Windows-style \r\n).
So one simple thing to try would be to change
lib/App/Netdisco/SSHCollector/Platform/PaloAlto.pm line 52 to this:
for (split(/\R/, $before)){
This would work with most weird things any common system might
consider
a line break.
If this doesn't work, I'm afraid I can't help more and we need to find
someone that has such a device and also can fiddle around with the
code
a bit.
Christian
On 30.04.17 13:26, Daniel Bird wrote:
Hi Christian,
It appears I have the same issue, so just a follow up with some more
info.
[netdisco2@netmanage ~]$ ~/bin/netdisco-sshcollector -DQ
[12105] 2017-04-30 11:03:28 debug paloalto-host 12105 arpnip()
[12105] 2017-04-30 11:03:29 warn WARNING: no entries received from
<paloalto-host>
Can't use string ("1") as an ARRAY ref while "strict refs" in use at
/home/netdisco2/bin/netdisco-sshcollector line 114, <$__ANONIO__>
line
3.
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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 ---
Ok. Well, the only time I've seen the error message that's been reported in
this thread is when I had the wrong password for the account on the Palo Alto
and the "show arp all" command failed as a result, producing no entries. My
guess is that the problem is along those lines. I would try logging into the
firewall using the configured username and password and giving that command. If
it fails, it should be apparent why. If not, I would tend to give up!
Regards
Max
Sent from my iPhone
> On 6 May 2017, at 17:04, Oliver Gorwits <[email protected]> wrote:
>
>
>> On 2017-05-04 10:20, Caines, Max wrote:
>> Given that ssh-collector is working on my Palo Alto, would it help if
>> I turned debugging on on it? I notice that there's also a commented
>> -out debug flag in the code for Net::OpenSSH. I could uncomment that
>> as well?
>
> Sorry Max, I have no idea - I don't use the sshcollector myself and
> didn't write any of the platform modules!
>
> regards,
> oliver.
>
>> Regards
>>
>> Max
>>
>> -----Original Message-----
>> From: Oliver Gorwits [mailto:[email protected]]
>> Sent: 03 May 2017 15:05
>> To: Christian Ramseyer <[email protected]>; Daniel Bird
>> <[email protected]>; [email protected];
>> [email protected]
>> Subject: Re: [Netdisco] NetDisco - ssh-collector issues with Palo Alto
>>
>> Hi all
>>
>> This is not directly helpful in this case, but if anyone has the time
>> to
>> try connecting using Net::Appliance::Session (or Net::CLI::Interact) I
>> would appreciate the feedback.
>>
>> NAS doesn't have a Palo Alto phrasebook but one of the others might
>> work. I am considering making a NAS-based collector for Netdisco to
>> take
>> away some of the pain exprienced in this thread.
>>
>> regards,
>> oliver.
>>
>>> On 2017-05-03 14:03, Christian Ramseyer wrote:
>>> Hi guys
>>>
>>> After Jonathan's message, I was checking our network for a device to
>>> try
>>> this, but unfortunately we seem to only own every networking product
>>> except Palo Alto :)
>>>
>>> But I looked at it again now, the regex to capture the stuff still
>>> seems
>>> fine with the output both of you sent, so it either is the prompt
>>> matching that fails or the split on the newline (which is fixed to
>>> Windows-style \r\n).
>>>
>>> So one simple thing to try would be to change
>>> lib/App/Netdisco/SSHCollector/Platform/PaloAlto.pm line 52 to this:
>>>
>>> for (split(/\R/, $before)){
>>>
>>> This would work with most weird things any common system might
>>> consider
>>> a line break.
>>>
>>> If this doesn't work, I'm afraid I can't help more and we need to find
>>> someone that has such a device and also can fiddle around with the
>>> code
>>> a bit.
>>>
>>> Christian
>>>
>>>
>>>> On 30.04.17 13:26, Daniel Bird wrote:
>>>> Hi Christian,
>>>>
>>>> It appears I have the same issue, so just a follow up with some more
>>>> info.
>>>>
>>>> [netdisco2@netmanage ~]$ ~/bin/netdisco-sshcollector -DQ
>>>> [12105] 2017-04-30 11:03:28 debug paloalto-host 12105 arpnip()
>>>> [12105] 2017-04-30 11:03:29 warn WARNING: no entries received from
>>>> <paloalto-host>
>>>> Can't use string ("1") as an ARRAY ref while "strict refs" in use at
>>>> /home/netdisco2/bin/netdisco-sshcollector line 114, <$__ANONIO__>
>>>> line
>>>> 3.
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>
>> ------------------------------------------------------------------------------
>> 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 ---
Ok. This used to work, so it could be that there is some extra data in
those tables you mentioned.
I will delete a large device and see if the tables clean up properly
as well, to the extent that I know how it works.
I'll work on it on Monday hopefully.
Andy
On Sat, May 6, 2017 at 9:00 AM, Oliver Gorwits <[email protected]> wrote:
> Hi Andy
>
> On large switches with many ports and many VLANs, the current Netdisco
> SQL query is definitely slow (and even broken in your case) as it tries
> to retrieve so much data in one go from the database.
>
> We could do with someone with good SQL chops taking a look at that -
> maybe some correlated subqueries or common table expressions need
> adding. Also we don't do paging in the UI so it gets all results and
> sends them to the client in one go.
>
> You could take a look at the number of rows in your device_port and
> device_port_vlan tables to see if they look "about right" or if
> something's gone wrong. Perhaps all 4095 VLANs have appeared on every
> port (and could be filtered with discover_no_vlan), or something
> similarly odd.
>
> Filtering some of the stored data via config might work, but is not
> ideal. Other than that, not a lot I can suggest, sorry. This is not seen
> (or reported) enough for us to understand the root cause, as yet.
>
> regards,
> oliver.
>
> On 2017-05-05 18:39, Andy Ruhl wrote:
>> I searched a bit and didn't find anything, hopefully this is a known
>> issue.
>>
>> On my larger switches (Cisco 6509, Juniper EX8208), if I click on the
>> "Ports" tab and I have connected devices and connected nodes checked,
>> the list never populates. I've let it sit for hours.
>>
>> On a smaller 1U switch, I get a list back not that quickly, but it
>> eventually populates.
>>
>> Where do I start troubleshooting?
>>
>> Things I've done:
>>
>> Use pgtune to tune the postgresql database
>>
>> Delete and re-discover the device
>>
>> vacuum the database
>>
>> None of these have worked.
>>
>> Andy
>>
>> ------------------------------------------------------------------------------
>> 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 ---
------------------------------------------------------------------------------
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
