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: Netdisco 1.3.2 Neighbor discovery (Jethro R Binks)
2. Netdisco 2 - another minor bug (ldap) (Daniel Tuecks)
3. Re: Netdisco 2 - small bugs when running with a custom path
(Eric Miller)
4. Re: Netdisco 2 - another minor bug (ldap) (Eric Miller)
5. Re: Netdisco 1.3.2 Neighbor discovery (Eric Miller)
6. Re: Netdisco 1.3.2 Neighbor discovery (Jethro R Binks)
--- Begin Message ---
Ooo I don't know what they mean, but I suspect something has changed in recent
netdisco/snmp::info; unfortunately my installation is quite old. I probably
have later stuff but it may not help with this; Jeroen was separately working
on HP/H3C support and we'd had some talk about how to integrate but not pursued
it much since.
If one of the other devs recognises the symptoms and can tell me what the issue
might be I can try and find time to take a quick look, otherwise I'm unlikely
to be able to get to this imminently.
Jethro (on mobile)
> On 12 Nov 2013, at 16:25, Simon De Matos <[email protected]> wrote:
>
> Hello,
>
> I just installed Netdisco on a Debian Wheezy and I'm currently having
> an error with the neighbor discovery.
>
> We're using Cisco, HP and 3Com switches, so I followed jrbinks'
> documentation to make Netdisco work properly with 3Com products
> (patching Info.pm, getting the missing 3Com mibs) but when trying a
> network discovery from one of the 3Com switches I get this:
>
> [3Com-4800G-switch] Fetching Neighbor Information
> SNMP::Info::_validate_autoload_method(hasLLDP) Unable to resolve method.
> SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
> SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve method.
> SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
> SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
> SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve method.
> SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
> [3Com-4800g-switch] ! CDP not Enabled.
> Network Discovery complete.
>
>
> The discovery works fine with the other brands. I'm not familiar with
> CPAN/SNMP::Info/Netdisco and my searches weren't really successful ...
>
> Hoping someone here knows what could cause these errors (or what I'm
> missing) because I'm currently running out of ideas.
>
>
> Best regards,
>
> Simon De Matos
> ----------------------------------
> Service Infrastructures
> Direction du Système d'Information
> Pôle Ressources
> ----------------------------------
> Université de Limoges
> 123, avenue Albert Thomas
> 87060 Limoges cedex
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi again,
I've found another netdisco 2 bug: Login via LDAP is not possible because
of a typo in DBIC.pm (see attached Patch). Also i think it would be nice,
if we could configure the ldap filter. Right now, it's set to '($filter)'
where $filter is the username. This might not be sufficient in some cases.
At our site, my filter looks like "sAMAccountName=$filter". As a
workaround, I hardcoded it but I fear it will be overwritten by the next
update...
regards,
Daniel
diff -crB netdisco-netdisco-ng-f1de543acf1d3f5fa4aeef6f704cae8a9010ec86/Netdisco/lib/App/Netdisco/Web/Auth/Provider/DBIC.pm netdisco-netdisco-ng-dtuecks/Netdisco/lib/App/Netdisco/Web/Auth/Provider/DBIC.pm
*** netdisco-netdisco-ng-f1de543acf1d3f5fa4aeef6f704cae8a9010ec86/Netdisco/lib/App/Netdisco/Web/Auth/Provider/DBIC.pm 2013-11-09 00:50:50.000000000 +0100
--- netdisco-netdisco-ng-dtuecks/Netdisco/lib/App/Netdisco/Web/Auth/Provider/DBIC.pm 2013-11-12 20:53:06.089552476 +0100
***************
*** 133,139 ****
return undef unless defined($filter);
return undef if (defined $attrs and ref [] ne ref $attrs);
! foreach my $server (@{$conf->{server}}) {
my $opts = $conf->{opts} || {};
my $ldap = Net::LDAP->new($server, %$opts) or next;
my $msg = undef;
--- 133,139 ----
return undef unless defined($filter);
return undef if (defined $attrs and ref [] ne ref $attrs);
! foreach my $server (@{$conf->{servers}}) {
my $opts = $conf->{opts} || {};
my $ldap = Net::LDAP->new($server, %$opts) or next;
my $msg = undef;
--- End Message ---
--- Begin Message ---
Thanks for the patches, these have been committed for inclusion in the
next release.
On 2013-11-12 11:51, Daniel Tuecks wrote:
Hi all,
I've found two small bugs when deploying netdisco2 to a custom path
(path: /netdisco2).
The first one occurs, when you log into the new netdisco installation.
Right after the login process, one gets redirected to '/inventory'
instead of '/netdisco2/inventory'.
The second bug affects .csv export. This is basically the the same
error as the one above: The generated download link is '/ajax/....'
(should be '/netdisco2/ajax/...').
I've attached patches to fix these bugs. Hope this is of any help for
you.
regards
Daniel
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models.
Explore
techniques for threading, error checking, porting, and tuning. Get the
most
from the latest Intel processors and coprocessors. See abstracts and
register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
This patch has been committed for inclusion in the next release.
Can you provide the code you hardcoded? I'm having difficulty
understanding without seeing the example, I was thinking that you could
just modify user_string in the config file.
Thanks,
Eric
On 2013-11-12 15:00, Daniel Tuecks wrote:
Hi again,
I've found another netdisco 2 bug: Login via LDAP is not possible
because of a typo in DBIC.pm (see attached Patch). Also i think it
would be nice, if we could configure the ldap filter. Right now, it's
set to '($filter)' where $filter is the username. This might not be
sufficient in some cases. At our site, my filter looks like
"sAMAccountName=$filter". As a workaround, I hardcoded it but I fear
it will be overwritten by the next update...
regards,
Daniel
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP
server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and
Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
On 2013-11-12 11:25, Simon De Matos wrote:
Hello,
I just installed Netdisco on a Debian Wheezy and I'm currently having
an error with the neighbor discovery.
We're using Cisco, HP and 3Com switches, so I followed jrbinks'
documentation to make Netdisco work properly with 3Com products
(patching Info.pm, getting the missing 3Com mibs) but when trying a
network discovery from one of the 3Com switches I get this:
[3Com-4800G-switch] Fetching Neighbor Information
SNMP::Info::_validate_autoload_method(hasLLDP) Unable to resolve
method.
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve
method.
SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve
method.
SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
[3Com-4800g-switch] ! CDP not Enabled.
Network Discovery complete.
The discovery works fine with the other brands. I'm not familiar with
CPAN/SNMP::Info/Netdisco and my searches weren't really successful ...
Hoping someone here knows what could cause these errors (or what I'm
missing) because I'm currently running out of ideas.
These are simply debug messages indicating that device class code
doesn't provide the methods needed to get topology information, they do
not indicate an error. Topology was re-factored in SNMP::Info version
3.0 the patch may be missing the methods needed for support.
On another note, some support for 3Com devices is included in recent
SNMP::Info devices through the Layer3::H3C class. For that class to
work it may require the branding of the device to be changed. Please
check the product configuration guide for details of the BRAND command
and the MIB STYLE command.
Thanks,
Eric
--- End Message ---
--- Begin Message ---
On Thu, 14 Nov 2013, Eric Miller wrote:
> On 2013-11-12 11:25, Simon De Matos wrote:
>
> > We're using Cisco, HP and 3Com switches, so I followed jrbinks'
> > documentation to make Netdisco work properly with 3Com products
> > (patching Info.pm, getting the missing 3Com mibs) but when trying a
> > network discovery from one of the 3Com switches I get this:
> >
> > [3Com-4800G-switch] Fetching Neighbor Information
> > SNMP::Info::_validate_autoload_method(hasLLDP) Unable to resolve
> > method.
> > SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
> > SNMP::Info::_validate_autoload_method(hasSONMP) Unable to resolve
> > method.
> > SNMP::Info::_validate_autoload_method(hasFDP) Unable to resolve method.
> > SNMP::Info::_validate_autoload_method(hasEDP) Unable to resolve method.
> > SNMP::Info::_validate_autoload_method(hasAMAP) Unable to resolve
> > method.
> > SNMP::Info::_validate_autoload_method(hasCDP) Unable to resolve method.
> > [3Com-4800g-switch] ! CDP not Enabled.
> > Network Discovery complete.
> >
> > The discovery works fine with the other brands. I'm not familiar with
> > CPAN/SNMP::Info/Netdisco and my searches weren't really successful ...
> >
> > Hoping someone here knows what could cause these errors (or what I'm
> > missing) because I'm currently running out of ideas.
>
> These are simply debug messages indicating that device class code
> doesn't provide the methods needed to get topology information, they do
> not indicate an error. Topology was re-factored in SNMP::Info version
> 3.0 the patch may be missing the methods needed for support.
>
> On another note, some support for 3Com devices is included in recent
> SNMP::Info devices through the Layer3::H3C class. For that class to
> work it may require the branding of the device to be changed. Please
> check the product configuration guide for details of the BRAND command
> and the MIB STYLE command.
I'll add a bit more context around this.
I originally wrote the the 3Com classes to support original SuperStack kit
from back in the day, then expanded it to support Comware 3 devices like
the E5500 which came out the H3C joint venture. Later again it grew more
to support Comware 5 devices like 4800G, A5500 and so on. Then HP bought
3Com over, renumbered the product lines, and it all got very difficult ...
(the A5500 is different from the E5500).
Subsequently, Jeroen worked on an H3C class for his HP A5500 (which is
exactly the same as the 4800G in fact).
SNMP::Info works by trying to match a device it is talking to with a
class. Primarily, it uses the manufacturer Oid, but can also use other
heuristics such as sysDescr if it needs to modify that decision.
In this case, you have several manufacturer Oids involved (3com on older
kit, h3c for some, hp for some newer), where for a given Oid you might
have kit that reacts in totally different ways, and which could also vary
based on the code version you are running.
So, it is likely to get proper selection between 3Com-oldSuperstack,
3Com-comware3, h3c-comware3, h3c-comware5, and hp-comware5 (and going
forward comware7), there will likely need to be a number of considerations
in order for SNMP::Info to correctly select the right class for the
device.
Now as Eric alludes, there is a "mib-style" command. In fact until this
conversation, and with Eric and Jeroen separately, I had never noticed
this command, so I've never used it. Its effects may well depend on the
version of code you are running. More investigation needed!
There's some similar info here:
http://www.h3c.com/portal/Products___Solutions/Technology/System_Management/Configuration_Example/200912/656452_57_0.htm#_Toc247357228
Moving forward, Jeroen and I had vaguely decided that perhaps the thing to
do was make old classic Superstack products fall within my 3Com.pm class,
and have Comware 5 stuff be represented in Jeroen's H3C class, and take
things forward from there. We might have to issue advice to use the
mib-style command if it will make development easier.
For you Simon, check your SNMP::Info install has Jeroen's H3C classes, and
then I'd suggest you need to hack SNMP::Info (Info.pm) to ensure it
selects that for the 4800G, and then see what you get, sorry not able to
tell you precisely just now, but maybe something like:
$objtype = 'SNMP::Info::Layer3::H3C'
if ( $desc =~ /^4800G/ );
would be good enough at least to test it out.
Jethro.
. . . . . . . . . . . . . . . . . . . . . . . . .
Jethro R Binks, Network Manager,
Information Services Directorate, University Of Strathclyde, Glasgow, UK
The University of Strathclyde is a charitable body, registered in
Scotland, number SC015263.
--- End Message ---
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
