You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(9) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(1) |
Feb
(2) |
Mar
(14) |
Apr
(15) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(17) |
Dec
(10) |
2006 |
Jan
(35) |
Feb
(27) |
Mar
(13) |
Apr
(61) |
May
(17) |
Jun
(2) |
Jul
(9) |
Aug
(7) |
Sep
(3) |
Oct
(6) |
Nov
(15) |
Dec
(3) |
2007 |
Jan
(6) |
Feb
(8) |
Mar
(1) |
Apr
(3) |
May
(9) |
Jun
(22) |
Jul
(11) |
Aug
(9) |
Sep
(6) |
Oct
(11) |
Nov
(9) |
Dec
(17) |
2008 |
Jan
(7) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(2) |
Jul
(10) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(2) |
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
(29) |
Jul
(32) |
Aug
(9) |
Sep
|
Oct
(31) |
Nov
(6) |
Dec
(5) |
2010 |
Jan
(12) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
(14) |
Jun
(4) |
Jul
|
Aug
(26) |
Sep
(3) |
Oct
(7) |
Nov
(14) |
Dec
(1) |
2011 |
Jan
(17) |
Feb
(6) |
Mar
(4) |
Apr
(4) |
May
(6) |
Jun
(11) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
(4) |
Nov
(3) |
Dec
(2) |
2012 |
Jan
(17) |
Feb
(5) |
Mar
(4) |
Apr
(4) |
May
(9) |
Jun
(6) |
Jul
(6) |
Aug
(6) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(6) |
2013 |
Jan
(8) |
Feb
(3) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
(5) |
Apr
(2) |
May
(7) |
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(4) |
Oct
(2) |
Nov
(5) |
Dec
|
2016 |
Jan
|
Feb
(4) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(1) |
2017 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Oliver G. <ol...@cp...> - 2017-02-27 16:39:39
|
Hi all, The tickets for Netdisco and SNMP::Info (and netdisco-mibs) are now migrated to Github: https://github.com/netdisco/netdisco/issues https://github.com/netdisco/snmp-info/issues https://github.com/netdisco/netdisco-mibs/issues The ticket numbers are not the same and the original requestor emails have not been migrated for the sake of privacy, but the original sf.net tickets are linked, and all requestors will have got an email about the migration. Many thanks! Oliver. On 2016-12-11 21:38, Oliver Gorwits wrote: > Hi all, > > From time to time we discuss the hosting of the projects (Netdisco and > SNMP-Info). I believe there are some good reasons for considering a > move > from Sourceforge to Github: > > * Better user interface for admins and users > * More well-known workflow > * Better uptime > * Github Pages for a homepage > > In particular I'll pick out that the fork and merge request process in > Sourceforge is clunky and presents quite a hurdle to new or drive-by > users. Personally speaking, the outages at Sourceforge hosting have > been > a real pain, and the git repo is slow. > > The only feature that sf.net uniquely has is the mail lists, so they > will remain. > > Right now I'm planning my activities for the upcoming holidays and I > would be happy to migrate Netdisco and SNMP-Info to Github, leaving the > mail list(s) at sf.net and updating up web links and documentation. > > Please let me know by 24 Dec if you're aware of any show-stopper to the > move, or if you think it's a really bad idea for any reason. We > recently > discussed this on the IRC channel #netdisco and there were no > objections > from the several devs present. > > Feel free to reply to this email or drop by #netdisco if you have > questions, and thank you for your attention! > > regards, > Oliver Gorwits. > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/xeonphi > _______________________________________________ > Netdisco mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netdisco-users |
From: Oliver G. <ol...@cp...> - 2017-01-15 17:41:25
|
On 2017-01-13 20:57, Mark Boolootian wrote: > The logic for port control under NDv1 included an > automatically generated email whenever a port > was enabled or disabled. As part of the NDv1 > parity, I think it would be quite useful if this feature > was added to NDv2. added: https://github.com/netdisco/netdisco/issues/290 Many thanks, oliver. > happy day, > booloo > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > _______________________________________________ > netdisco-devel mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netdisco-devel |
From: Mark B. <bo...@uc...> - 2017-01-13 20:57:29
|
The logic for port control under NDv1 included an automatically generated email whenever a port was enabled or disabled. As part of the NDv1 parity, I think it would be quite useful if this feature was added to NDv2. happy day, booloo |
From: Sanjeev G. <sa...@dc...> - 2017-01-05 19:33:55
|
On Thu, Jan 5, 2017 at 3:40 AM, Oliver Gorwits <ol...@cp...> wrote: > > > ssh://USE...@gi.../p/netdisco/netdisco-ng > gi...@gi...:netdisco/netdisco.git I have update Openhub with the new code location for netdisco, and the update job is running. -- Sanjeev Gupta +65 98551208 http://sg.linkedin.com/in/ghane |
From: Oliver G. <ol...@cp...> - 2017-01-05 19:23:20
|
On 2017-01-05 19:08, Sanjeev Gupta wrote: > On Thu, Jan 5, 2017 at 3:40 AM, Oliver Gorwits <ol...@cp...> > wrote: > >> ssh://USE...@gi.../p/netdisco/netdisco-ng [1] >> gi...@gi...:netdisco/netdisco.git > > I have update Openhub with the new code location for netdisco, and the > update job is running. Thank you! regards, oliver. > -- > Sanjeev Gupta > +65 98551208 http://sg.linkedin.com/in/ghane [2] > > > Links: > ------ > [1] http://USE...@gi.../p/netdisco/netdisco-ng > [2] http://sg.linkedin.com/in/ghane |
From: Oliver G. <ol...@cp...> - 2017-01-04 19:40:08
|
Hi all, First, a very happy [Gregorian calendar] new year to you, and thanks for continuing to use our software! Following agreement in the dev team, the new home for Netdisco and SNMP-Info is: https://github.com/netdisco Please update your git repository URLs as in the example below: $ git remote -v origin ssh://USE...@gi.../p/snmp-info/code (fetch) origin ssh://USE...@gi.../p/snmp-info/code (push) $ git remote set-url origin gi...@gi...:netdisco/snmp-info.git The full list of from/to URL changes (pay close attention!): ssh://USE...@gi.../p/snmp-info/code gi...@gi...:netdisco/snmp-info.git ssh://USE...@gi.../p/netdisco/mibs gi...@gi...:netdisco/netdisco-mibs.git ssh://USE...@gi.../p/netdisco/misc gi...@gi...:netdisco/netdisco-misc.git ssh://USE...@gi.../p/netdisco/code gi...@gi...:netdisco/netdisco-legacy.git ssh://USE...@gi.../p/netdisco/netdisco-ng gi...@gi...:netdisco/netdisco.git See this page if you get stuck with the URL or authenticating: https://help.github.com/articles/which-remote-url-should-i-use/ I am going to have a look at migrating the tickets, but it may be lossy in metadata (ticket requestor) so, we'll see. Going forward we would like the GitHub issues to be used to report bugs and request features, although of course these mail lists are always preferred for initial contact and discussion (and will remain at SourceForge). Any questions, please let me know on or off list, regards, oliver. |
From: Oliver G. <ol...@cp...> - 2016-12-11 21:38:34
|
Hi all, From time to time we discuss the hosting of the projects (Netdisco and SNMP-Info). I believe there are some good reasons for considering a move from Sourceforge to Github: * Better user interface for admins and users * More well-known workflow * Better uptime * Github Pages for a homepage In particular I'll pick out that the fork and merge request process in Sourceforge is clunky and presents quite a hurdle to new or drive-by users. Personally speaking, the outages at Sourceforge hosting have been a real pain, and the git repo is slow. The only feature that sf.net uniquely has is the mail lists, so they will remain. Right now I'm planning my activities for the upcoming holidays and I would be happy to migrate Netdisco and SNMP-Info to Github, leaving the mail list(s) at sf.net and updating up web links and documentation. Please let me know by 24 Dec if you're aware of any show-stopper to the move, or if you think it's a really bad idea for any reason. We recently discussed this on the IRC channel #netdisco and there were no objections from the several devs present. Feel free to reply to this email or drop by #netdisco if you have questions, and thank you for your attention! regards, Oliver Gorwits. |
From: Oliver G. <ol...@cp...> - 2016-10-01 17:27:23
|
Hi Max, On 2016-02-15 22:41, Max Kosmach wrote: > Patch below adds Check Point VSX support to sshcollector Many thanks! I have applied the patch and it will be in the next release of Netdisco. My apologies for taking so long to reply to this email. regards, oliver. > Please review and apply if it's ok. > > From 84d9c89e599c9cdea7371a627268e8b988c7f196 Mon Sep 17 00:00:00 2001 > From: Max Kosmach <be...@us...> > Date: Tue, 16 Feb 2016 00:55:22 +0300 > Subject: Add Check Point VSX support > > --- > .../App/Netdisco/SSHCollector/Platform/CPVSX.pm | 142 > +++++++++++++++++++++ > 1 file changed, 142 insertions(+) > create mode 100644 > Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm > > diff --git a/Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm > b/Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm > new file mode 100644 > index 0000000..983beff > --- /dev/null > +++ b/Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm > @@ -0,0 +1,142 @@ > +package App::Netdisco::SSHCollector::Platform::CPVSX; > + > +=head1 NAME > + > +App::Netdisco::SSHCollector::Platform::CPVSX > + > +=head1 DESCRIPTION > + > +Collect ARP entries from Check Point VSX > + > +This collector uses "C<arp>" as the command for the arp utility on > your > +system. Clish "C<show arp>" dows not work correctly in versions prior > to R77.30. > +Config example: > + > + sshcollector: > + - ip: '192.0.2.1' > + user: oliver > + password: letmein > + expert_password: letmein2 > + platform: CPVSX > + > +=cut > + > +use strict; > +use warnings; > + > +use Dancer ':script'; > +use Expect; > +use Moo; > + > +=head1 PUBLIC METHODS > + > +=over 4 > + > +=item B<arpnip($host, $ssh)> > + > +Retrieve ARP entries from device. C<$host> is the hostname or IP > address > +of the device. C<$ssh> is a Net::OpenSSH connection to the device. > + > +Returns a list of hashrefs in the format C<< { mac => MACADDR, ip => > IPADDR } >>. > + > +=back > + > +=cut > + > +sub arpnip { > + my ($self, $hostlabel, $ssh, $args) = @_; > + > + my @arpentries = (); > + > + debug "$hostlabel $$ arpnip()"; > + > + my ($pty, $pid) = $ssh->open2pty or die "unable to run remote > command"; > + my $expect = Expect->init($pty); > + > + my ($pos, $error, $match, $before, $after); > + my $prompt; > + > + $prompt = qr/>/; > + ($pos, $error, $match, $before, $after) = $expect->expect(10, > -re, $prompt); > + > + # TODO: check CP os/version via "cpstat os" and VSX status via > "show vsx" > +# $expect->send("show vsx\n"); > +# ($pos, $error, $match, $before, $after) = $expect->expect(10, > -re, $prompt); > +# debug "$hostlabel $$ show vsx: $before"; > + > + # Enumerate virtual systems > + # Virtual systems list > + # VS ID VS NAME > + # 0 0 > + # 1 BACKUP-VSX_xxxxxx_Context > + # ... > + > + $expect->send("show virtual-system all\n"); > + ($pos, $error, $match, $before, $after) = $expect->expect(10, > -re, $prompt); > + > + my @vsxentries = (); > + my @lines = split(m/\n/, $before); > + > + my $linereg = qr/(\d+)\s+([A-Za-z0-9_-]+)/; > + foreach my $line (@lines) { > + if ($line =~ $linereg) { > + my ($vsid, $vsname) = ($1, $2); > + push @vsxentries, { vsid => $vsid, vsname=> $vsname }; > + debug "$hostlabel $$ $vsid, $vsname"; > + } > + } > + > + # TODO: > + # Expert mode should be used only for pre-R77.30 versions > + # For R77.30 and later we can use: > + # set virtual-system $vsid > + # show arp dynamic all > + > + $expect->send("expert\n"); > + > + $prompt = qr/Enter expert password:/; > + ($pos, $error, $match, $before, $after) = $expect->expect(10, > -re, $prompt); > + > + $expect->send( $args->{expert_password} ."\n" ); > + > + $prompt = qr/#/; > + ($pos, $error, $match, $before, $after) = $expect->expect(10, > -re, $prompt); > + > + foreach (@vsxentries) { > + my $vsid = $_->{vsid}; > + debug "$hostlabel $$ arpnip VSID: $vsid"; > + > + $expect->send("vsenv $vsid\n"); > + ($pos, $error, $match, $before, $after) = $expect->expect(10, > -re, $prompt); > + > + $expect->send("arp -n | tail -n +2\n"); > + ($pos, $error, $match, $before, $after) = $expect->expect(10, > -re, $prompt); > + > + @lines = split(m/\n/, $before); > + > + # 192.168.1.1 ether 00:b6:aa:f5:bb:6e C eth1 > + $linereg = qr/([0-9\.]+)\s+ether\s+([a-fA-F0-9:]+)/; > + > + foreach my $line (@lines) { > + if ($line =~ $linereg) { > + my ($ip, $mac) = ($1, $2); > + push @arpentries, { mac => $mac, ip => $ip }; > + debug "$hostlabel $$ arpnip VSID: $vsid IP: $ip MAC: $mac"; > + } > + } > + > + } > + > + $expect->send("exit\n"); > + > + $prompt = qr/>/; > + ($pos, $error, $match, $before, $after) = $expect->expect(5, -re, > $prompt); > + > + $expect->send("exit\n"); > + > + $expect->soft_close(); > + > + return @arpentries; > +} > + > +1; > -- > 2.7.0 > > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > netdisco-devel mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netdisco-devel |
From: Oliver G. <ol...@cp...> - 2016-10-01 17:22:24
|
Hi Steven, On 2016-02-26 19:21, Steven Xu wrote: > I found and patched a problem when you have 5.5 million node_ip > entries, deleting devices can possibly take 10 minutes or more. Trying > to delete the device twice can cause netdisco to lock up the database. > > I fixed this by limiting the subquery "find all mac addresses in node > ip which don't have corresponding entries in the node table" with the > first subquery ("select all mac addresses for the device being > deleted"). Apologies for taking ages to reply to this. I have applied your patch for the next release of Netdisco - it looks good. I'm grateful for you finding this and reporting it with a fix! Many thanks indeed, Oliver. > You can find the patch attached. I'm new to open source software, so > if there are issues, please inform me. > > Steven > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > > _______________________________________________ > netdisco-devel mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netdisco-devel |
From: Steven Xu <st...@yo...> - 2016-04-29 21:01:52
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">Hi all,<br><br>York University has customized Netdisco to keep track of cable assets, connecting physical cable topology with virtual information that switches and routers know about. This allows Netdisco users to search up the physical location of a node (for example, a workstation) by what building and room they are in. Additionally, if the wall cover that the user is connected to is labelled, Netdisco users are able to look for what switch is connected on the other side.<br><br>It's similar in functionality to NetDot, but uses the new features of Netdisco V2.<br><br>It's on github (https://github.com/latagore/netdisco) but currently isn't easy to deploy from scratch. Raw (and very dirty) database schema changes over the years (at York) can be found in lib/App/Netdisco/DB/schema_versions/port_info.sql, and various couplings may need to be removed in order to integrate with existing Netdisco installations (some that come to mind are lib/App/NetdiscoX/Web/Auth/Provider/YorkLDAP.pm which does LDAP authentication for York University).<br><br>While I can't promise that I'll be able to make these customizations work with Netdisco out of the box, hopefully the source for the following features will be useful to someone:<br>- Significantly improved performance for viewing ports on a device<br>- Searching for switch/router ports connected to a cable plate mounted on a wall<br>- Listing all of the switch ports that terminate in a given room (like a lab or office)<br>- Cable edit functionality through the web interface<br><br>Steven<br><div></div></font> |
From: Steven Xu <st...@yo...> - 2016-04-11 13:43:08
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">Hi Jeroen,<br><br>Sorry for the late reply.<br><br>The reason it seemed significant is because we graph the CPU loads, and there are spikes that exactly correspond with the scheduled times for Netdisco discovery and other tools that make SNMP requests. As you said, it may not be as a big of a deal, considering the low priority of SNMP work. I don't believe we experience significant problems with SNMP polling.<br><br>Thanks for the detailed reply!<br>Steven<br><br><br><font color="#990099">-----Jeroen van Ingen <j.v...@ut...> wrote: -----</font><div style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;">To: <net...@li...><br>From: Jeroen van Ingen <j.v...@ut...><br>Date: 02/08/2016 04:12AM<br>Subject: Re: [netdisco-devel] Reduce SNMP query rate<br><br><div><font face="Courier New,Courier,monospace" size="2">Hi Steven,<br><br>As far as I know, no efforts have been made to purposely slow down <br>Netdisco or SNMP::Info ;-)<br><br>Yes, device CPU load may increase significantly when a device is polled <br>for information, especially when large tables are polled (eg during <br>arpnip on a device that routs between many large subnets, or macsuck on <br>switches carrying several VLANs with thousands of MAC addresses).<br><br>We've never had any issues that we could relate to CPU load caused by <br>SNMP polling, that's why I never really considered trying to lower the <br>SNMP request rate (in the code) or delaying SNMP traffic (eg using 'tc' <br>on the server).<br><br>We see the high loads mostly on our Cisco Cat6k boxes; they are fine <br>with it, since the IOS scheduler puts the SNMP tasks at the lowest <br>priority, so virtually all other tasks performed by the CPU will get <br>their share before SNMP is allowed its cycles.<br><br>IMHO the biggest downside to our approach is that monitoring the box for <br>high CPU load doesn't say that much, you'd need the full process list <br>with load per process to determine whether the box is really overloaded. <br>That's a relatively expensive operation to perform in itself, so we just <br>use another metric: we use the CPU time spent in interrupt context to <br>monitor whether a box is overloaded. If one of our Cat6k's spends more <br>than 30% of its CPU time in interrupt context, there's a traffic <br>condition that's probably causing issues and that's something we want to <br>investigate.<br><br><br>Do your devices actually have issues with performing their normal <br>routing & switching tasks, in times when SNMP polling is using a <br>significant amount of CPU cycles? Or is the load in general worrying you?<br><br><br>Regards,<br><br>Jeroen van Ingen<br>ICT Service Centre<br>University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands<br><br><br>On 02/04/2016 07:54 PM, Steven Xu wrote:<br>> Hi,<br>><br>> We've noticed that when Netdisco makes SNMP requests, the CPU load<br>> increases significantly on some devices. Has anyone explored the option<br>> of including delays between SNMP requests or otherwise reducing the load?<br>><br>> Steven<br><br><br>------------------------------------------------------------------------------<br>Site24x7 APM Insight: Get Deep Visibility into Application Performance<br>APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month<br>Monitor end-to-end web transactions and take corrective actions now<br>Troubleshoot faster and improve end-user experience. Signup Now!<br><a href="http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140">http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140</a><br>_______________________________________________<br>netdisco-devel mailing list<br>net...@li...<br><a href="https://lists.sourceforge.net/lists/listinfo/netdisco-devel">https://lists.sourceforge.net/lists/listinfo/netdisco-devel</a><br></font></div></div></div><div></div></font> |
From: Steven Xu <st...@yo...> - 2016-02-26 19:21:16
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">Hi, <br><br>I found and patched a problem when you have 5.5 million node_ip entries, deleting devices can possibly take 10 minutes or more. Trying to delete the device twice can cause netdisco to lock up the database.<br><br>I fixed this by limiting the subquery "find all mac addresses in node ip which don't have corresponding entries in the node table" with the first subquery ("select all mac addresses for the device being deleted").<br><br>You can find the patch attached. I'm new to open source software, so if there are issues, please inform me.<br><br>Steven<br><div></div></font> |
From: Max K. <be...@us...> - 2016-02-15 23:00:44
|
Hi Patch below adds Check Point VSX support to sshcollector Please review and apply if it's ok. From 84d9c89e599c9cdea7371a627268e8b988c7f196 Mon Sep 17 00:00:00 2001 From: Max Kosmach <be...@us...> Date: Tue, 16 Feb 2016 00:55:22 +0300 Subject: Add Check Point VSX support --- .../App/Netdisco/SSHCollector/Platform/CPVSX.pm | 142 +++++++++++++++++++++ 1 file changed, 142 insertions(+) create mode 100644 Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm diff --git a/Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm b/Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm new file mode 100644 index 0000000..983beff --- /dev/null +++ b/Netdisco/lib/App/Netdisco/SSHCollector/Platform/CPVSX.pm @@ -0,0 +1,142 @@ +package App::Netdisco::SSHCollector::Platform::CPVSX; + +=head1 NAME + +App::Netdisco::SSHCollector::Platform::CPVSX + +=head1 DESCRIPTION + +Collect ARP entries from Check Point VSX + +This collector uses "C<arp>" as the command for the arp utility on your +system. Clish "C<show arp>" dows not work correctly in versions prior to R77.30. +Config example: + + sshcollector: + - ip: '192.0.2.1' + user: oliver + password: letmein + expert_password: letmein2 + platform: CPVSX + +=cut + +use strict; +use warnings; + +use Dancer ':script'; +use Expect; +use Moo; + +=head1 PUBLIC METHODS + +=over 4 + +=item B<arpnip($host, $ssh)> + +Retrieve ARP entries from device. C<$host> is the hostname or IP address +of the device. C<$ssh> is a Net::OpenSSH connection to the device. + +Returns a list of hashrefs in the format C<< { mac => MACADDR, ip => IPADDR } >>. + +=back + +=cut + +sub arpnip { + my ($self, $hostlabel, $ssh, $args) = @_; + + my @arpentries = (); + + debug "$hostlabel $$ arpnip()"; + + my ($pty, $pid) = $ssh->open2pty or die "unable to run remote command"; + my $expect = Expect->init($pty); + + my ($pos, $error, $match, $before, $after); + my $prompt; + + $prompt = qr/>/; + ($pos, $error, $match, $before, $after) = $expect->expect(10, -re, $prompt); + + # TODO: check CP os/version via "cpstat os" and VSX status via "show vsx" +# $expect->send("show vsx\n"); +# ($pos, $error, $match, $before, $after) = $expect->expect(10, -re, $prompt); +# debug "$hostlabel $$ show vsx: $before"; + + # Enumerate virtual systems + # Virtual systems list + # VS ID VS NAME + # 0 0 + # 1 BACKUP-VSX_xxxxxx_Context + # ... + + $expect->send("show virtual-system all\n"); + ($pos, $error, $match, $before, $after) = $expect->expect(10, -re, $prompt); + + my @vsxentries = (); + my @lines = split(m/\n/, $before); + + my $linereg = qr/(\d+)\s+([A-Za-z0-9_-]+)/; + foreach my $line (@lines) { + if ($line =~ $linereg) { + my ($vsid, $vsname) = ($1, $2); + push @vsxentries, { vsid => $vsid, vsname=> $vsname }; + debug "$hostlabel $$ $vsid, $vsname"; + } + } + + # TODO: + # Expert mode should be used only for pre-R77.30 versions + # For R77.30 and later we can use: + # set virtual-system $vsid + # show arp dynamic all + + $expect->send("expert\n"); + + $prompt = qr/Enter expert password:/; + ($pos, $error, $match, $before, $after) = $expect->expect(10, -re, $prompt); + + $expect->send( $args->{expert_password} ."\n" ); + + $prompt = qr/#/; + ($pos, $error, $match, $before, $after) = $expect->expect(10, -re, $prompt); + + foreach (@vsxentries) { + my $vsid = $_->{vsid}; + debug "$hostlabel $$ arpnip VSID: $vsid"; + + $expect->send("vsenv $vsid\n"); + ($pos, $error, $match, $before, $after) = $expect->expect(10, -re, $prompt); + + $expect->send("arp -n | tail -n +2\n"); + ($pos, $error, $match, $before, $after) = $expect->expect(10, -re, $prompt); + + @lines = split(m/\n/, $before); + + # 192.168.1.1 ether 00:b6:aa:f5:bb:6e C eth1 + $linereg = qr/([0-9\.]+)\s+ether\s+([a-fA-F0-9:]+)/; + + foreach my $line (@lines) { + if ($line =~ $linereg) { + my ($ip, $mac) = ($1, $2); + push @arpentries, { mac => $mac, ip => $ip }; + debug "$hostlabel $$ arpnip VSID: $vsid IP: $ip MAC: $mac"; + } + } + + } + + $expect->send("exit\n"); + + $prompt = qr/>/; + ($pos, $error, $match, $before, $after) = $expect->expect(5, -re, $prompt); + + $expect->send("exit\n"); + + $expect->soft_close(); + + return @arpentries; +} + +1; -- 2.7.0 |
From: Jeroen v. I. <j.v...@ut...> - 2016-02-08 09:12:47
|
Hi Steven, As far as I know, no efforts have been made to purposely slow down Netdisco or SNMP::Info ;-) Yes, device CPU load may increase significantly when a device is polled for information, especially when large tables are polled (eg during arpnip on a device that routs between many large subnets, or macsuck on switches carrying several VLANs with thousands of MAC addresses). We've never had any issues that we could relate to CPU load caused by SNMP polling, that's why I never really considered trying to lower the SNMP request rate (in the code) or delaying SNMP traffic (eg using 'tc' on the server). We see the high loads mostly on our Cisco Cat6k boxes; they are fine with it, since the IOS scheduler puts the SNMP tasks at the lowest priority, so virtually all other tasks performed by the CPU will get their share before SNMP is allowed its cycles. IMHO the biggest downside to our approach is that monitoring the box for high CPU load doesn't say that much, you'd need the full process list with load per process to determine whether the box is really overloaded. That's a relatively expensive operation to perform in itself, so we just use another metric: we use the CPU time spent in interrupt context to monitor whether a box is overloaded. If one of our Cat6k's spends more than 30% of its CPU time in interrupt context, there's a traffic condition that's probably causing issues and that's something we want to investigate. Do your devices actually have issues with performing their normal routing & switching tasks, in times when SNMP polling is using a significant amount of CPU cycles? Or is the load in general worrying you? Regards, Jeroen van Ingen ICT Service Centre University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands On 02/04/2016 07:54 PM, Steven Xu wrote: > Hi, > > We've noticed that when Netdisco makes SNMP requests, the CPU load > increases significantly on some devices. Has anyone explored the option > of including delays between SNMP requests or otherwise reducing the load? > > Steven |
From: Steven Xu <st...@yo...> - 2016-02-04 18:54:23
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">Hi,<br><br>We've noticed that when Netdisco makes SNMP requests, the CPU load increases significantly on some devices. Has anyone explored the option of including delays between SNMP requests or otherwise reducing the load? <br><br>Steven<br><div></div></font> |
From: Oliver G. <ol...@cp...> - 2015-11-16 21:42:16
|
On 2015-10-27 18:38, Steven Xu wrote: > Below is a fix for the issue reported in the email thread > "[Netdisco] > snmpretries setting not working?" Could someone review and commit the > following code? Many thanks indeed Steven! This is included in release 2.033004 on its way to CPAN, now. Sorry for not replying to the personal email, I was just busy. regards, oliver. > I originally sent this email to Oliver Gorwits, but it might be more > appropriate to send to this mailing list instead. I am new to > submitting changes to open-source development. > > Steven > > >From e76c15dc2d3094cfbf8d2e3ce274ca407aa51f8f Mon Sep 17 00:00:00 > 2001 > From: Steven Xu <st...@yo...> > Date: Tue, 27 Oct 2015 14:26:53 -0400 > Subject: [PATCH] Allow snmpretries to be set to 0 > > --- > Netdisco/lib/App/Netdisco/Util/SNMP.pm | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/Netdisco/lib/App/Netdisco/Util/SNMP.pm > b/Netdisco/lib/App/Netdisco/Util/SNMP.pm > index 754a00e..9561191 100644 > --- a/Netdisco/lib/App/Netdisco/Util/SNMP.pm > +++ b/Netdisco/lib/App/Netdisco/Util/SNMP.pm > @@ -66,7 +66,9 @@ sub _snmp_connect_generic { > my %snmp_args = ( > AutoSpecify => 0, > DestHost => $device->ip, > - Retries => (setting('snmpretries') || 2), > + # 0 is falsy. Using || with snmpretries equal to 0 will set > retries > to 2. > + # check if the setting is 0. If not, use the default value of 2. > + Retries => (setting('snmpretries') || setting('snmpretries') == 0 > ? > 0 : 2), > Timeout => (setting('snmptimeout') || 1000000), > NonIncreasing => (setting('nonincreasing') || 0), > BulkWalk => ((defined setting('bulkwalk_off') && > setting('bulkwalk_off')) > -- > 1.9.1 |
From: Steven Xu <st...@yo...> - 2015-11-16 20:22:33
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> To be fair, it really should have an explicit configuration option.<br> <br>Steven<br><br><font color="#990099">-----Christian Ramseyer <rc...@ne...> wrote: -----</font> <div style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;"> To: Steven Xu <st...@yo...><br>From: Christian Ramseyer <rc...@ne...><br> Date: 11/16/2015 07:15AM<br>Cc: net...@li...<br> Subject: Re: [netdisco-devel] Configurable postgres port<br><br><div><font size="2" face="Courier New,Courier,monospace"> On 12/11/15 16:38, Steven Xu wrote:<br>> Hi Christian,<br>> <br>> According to the Deployment documentation, you can pick a port as<br> > follows:<br>> <a href="http://search.cpan.org/~oliver/App-Netdisco-2.029008/lib/App/Netdisco/Manual/Deployment.pod#Connect_to_PostgreSQL_database_on_non-standard_port"> http://search.cpan.org/~oliver/App-Netdisco-2.029008/lib/App/Netdisco/Manual/Deployment.pod#Connect_to_PostgreSQL_database_on_non-standard_port</a> <br>> <br><br>Thanks Steven, looks like I stopped RTFMing too early after not finding<br> a port option in the App:Netdisco POD.<br><br><br>Christian<br></font></div> </div></div><div></div></font> |
From: Christian R. <rc...@ne...> - 2015-11-16 12:10:53
|
On 12/11/15 16:38, Steven Xu wrote: > Hi Christian, > > According to the Deployment documentation, you can pick a port as > follows: > http://search.cpan.org/~oliver/App-Netdisco-2.029008/lib/App/Netdisco/Manual/Deployment.pod#Connect_to_PostgreSQL_database_on_non-standard_port > Thanks Steven, looks like I stopped RTFMing too early after not finding a port option in the App:Netdisco POD. Christian |
From: Steven Xu <st...@yo...> - 2015-11-12 15:38:35
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> Hi Christian,<br><br>According to the Deployment documentation, you can pick a port as follows: <a target="_blank" href="http://search.cpan.org/~oliver/App-Netdisco-2.029008/lib/App/Netdisco/Manual/Deployment.pod#Connect_to_PostgreSQL_database_on_non-standard_port" title="http://search.cpan.org/~oliver/App-Netdisco-2.029008/lib/App/Netdisco/Manual/Deployment.pod#Connect_to_PostgreSQL_database_on_non-standard_port"> http://search.cpan.org/~oliver/App-Netdisco-2.029008/lib/App/Netdisco/Manual/Deployment.pod#Connect_to_PostgreSQL_database_on_non-standard_port</a> <br><br>However, having a documented configuration option would be much nicer than described in the link.<br> <br>Steven<br><br><font color="#990099">-----Christian Ramseyer <rc...@ne...> wrote: -----</font> <div style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;"> To: net...@li...<br>From: Christian Ramseyer <rc...@ne...><br> Date: 11/10/2015 07:00PM<br>Subject: [netdisco-devel] Configurable postgres port<br> <br><div><font size="2" face="Courier New,Courier,monospace">Hello list<br> <br>I tried to use Netdisco with a non-default Postgres port and noticed<br> that there seemed to be no way to communicate this fact via deployment.yml.<br> <br>Attached is a quick attempt at a patch.<br><br>Cheers<br>Christian<br> <br></font></div><div><font size="2" face="Courier New,Courier,monospace"> ------------------------------------------------------------------------------<br> </font></div><div><font size="2" face="Courier New,Courier,monospace">_______________________________________________<br> netdisco-devel mailing list<br>net...@li...<br> <a href="https://lists.sourceforge.net/lists/listinfo/netdisco-devel">https://lists.sourceforge.net/lists/listinfo/netdisco-devel</a> <br></font></div></div><br><br>[attachment "configurable_port.patch" removed by Steven Xu/fs/YorkU]</div> <div></div></font> |
From: Christian R. <rc...@ne...> - 2015-11-10 22:10:41
|
Hello list I tried to use Netdisco with a non-default Postgres port and noticed that there seemed to be no way to communicate this fact via deployment.yml. Attached is a quick attempt at a patch. Cheers Christian |
From: Steven Xu <st...@yo...> - 2015-10-27 18:39:18
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> Hi all,<br></font><br><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> <font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> Below is a fix for the issue reported in the email thread "[Netdisco] snmpretries setting not working?" Could someone review and commit the following code?<br><br></font> I originally sent this email to Oliver Gorwits, but it might be more appropriate to send to this mailing list instead. I am new to submitting changes to open-source development. <br> <br>Steven<br><br><font face="Default Monospace,Courier New,Courier,monospace"> >From e76c15dc2d3094cfbf8d2e3ce274ca407aa51f8f Mon Sep 17 00:00:00 2001<br> From: Steven Xu <st...@yo...><br>Date: Tue, 27 Oct 2015 14:26:53 -0400<br> Subject: [PATCH] Allow snmpretries to be set to 0<br><br>---<br> Netdisco/lib/App/Netdisco/Util/SNMP.pm | 4 +++-<br> 1 file changed, 3 insertions(+), 1 deletion(-)<br><br>diff --git a/Netdisco/lib/App/Netdisco/Util/SNMP.pm b/Netdisco/lib/App/Netdisco/Util/SNMP.pm<br> index 754a00e..9561191 100644<br>--- a/Netdisco/lib/App/Netdisco/Util/SNMP.pm<br> +++ b/Netdisco/lib/App/Netdisco/Util/SNMP.pm<br>@@ -66,7 +66,9 @@ sub _snmp_connect_generic {<br> my %snmp_args = (<br> AutoSpecify => 0,<br> DestHost => $device->ip,<br>- Retries => (setting('snmpretries') || 2),<br> + # 0 is falsy. Using || with snmpretries equal to 0 will set retries to 2.<br> + # check if the setting is 0. If not, use the default value of 2.<br> + Retries => (setting('snmpretries') || setting('snmpretries') == 0 ? 0 : 2),<br> Timeout => (setting('snmptimeout') || 1000000),<br> NonIncreasing => (setting('nonincreasing') || 0),<br> BulkWalk => ((defined setting('bulkwalk_off') && setting('bulkwalk_off'))<br> --<br>1.9.1</font></font><div></div></font> |
From: Oliver G. <ol...@cp...> - 2015-10-04 19:09:29
|
Hi Mark, On 2015-09-17 23:36, Mark Boolootian wrote: > I'd like to still be able to expire nodes for the switches in > resnet, but in order to do that without collateral damage > (i.e. removing a node that isn't in a resnet VLAN), I would > like to be able to restrict node removal to a specific VLAN. > > Any chance that feature is worthy of implementation? Awkward, only because the netdisco-do command doesn't have any spare command line parameters I can lazily repurpose ;-) I did consider allowing -p to specify port or vlan, but of course there *could* be numeric port names so it's not easy to tell. Any other suggestions are welcome. oliver. |
From: Mark B. <bo...@uc...> - 2015-09-18 22:42:23
|
Hi Steven, > From what I understand, expiring nodes is essentially deleting the node > entries from the Netdisco database (maybe someone can confirm this for me). I believe that is correct. > Writing a SQL query to remove these nodes manually may be an acceptable > workaround for you. Yes, we could definitely do this, but my thinking was that adding a flag to 'netdisco-do expirenodes' specifying VLAN might be a generally useful feature to have. cheers, mark |
From: Steven Xu <st...@yo...> - 2015-09-18 18:50:28
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"> >From what I understand, expiring nodes is essentially deleting the node entries from the Netdisco database (maybe someone can confirm this for me). Writing a SQL query to remove these nodes manually may be an acceptable workaround for you.<br> <br>Steven<br><br><font color="#990099">-----Mark Boolootian <bo...@uc...> wrote: -----</font> <div style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;"> To: net...@li...<br>From: Mark Boolootian <bo...@uc...><br> Date: 09/17/2015 07:20PM<br>Subject: [netdisco-devel] expirenodes by VLAN<br> <br><div><font face="Courier New,Courier,monospace" size="2">We go through the exercise of expiring nodes on all the<br> switches in our residential network each summer, just<br>ahead of the new crop of students showing up (no value<br> in keeping last year's data around).<br><br>This past year, we replaced all our resnet switches, and<br> began 802.1q tagging to the new switches so that we can<br>provide more than just resnet subnets on each switch.<br> <br>I'd like to still be able to expire nodes for the switches in<br>resnet, but in order to do that without collateral damage<br> (i.e. removing a node that isn't in a resnet VLAN), I would<br>like to be able to restrict node removal to a specific VLAN.<br> <br>Any chance that feature is worthy of implementation?<br><br>mark<br> <br>------------------------------------------------------------------------------<br> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!<br>Get real-time metrics from all of your servers, apps and tools<br> in one place.<br>SourceForge users - Click here to start your Free Trial of Datadog now!<br> <a href="http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140"> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140</a> <br>_______________________________________________<br>netdisco-devel mailing list<br> net...@li...<br><a href="https://lists.sourceforge.net/lists/listinfo/netdisco-devel"> https://lists.sourceforge.net/lists/listinfo/netdisco-devel</a><br></font> </div></div></div><div></div></font> |
From: Mark B. <bo...@uc...> - 2015-09-17 22:56:04
|
>> o a note/comment field (which we use to show affiliation) >> o created/last seen timestamps > > These fields are already in the database so I've exposed them in the > web interface and this will be in the next release. > > Note that the last seen stamp is only updated on login, and this is a > session-length cookie. > >> If easy, it would also be useful if it were possible to >> CSV export the user management page similar to the >> functionality provided on device pages. > > Yep, I've enabled this as well. This is awesome. Thank you Oliver! cheers, mark |