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 2: discover error (Robert Kerr)
2. mkindex without result ([email protected])
3. Re: mkindex without result (Eric Miller)
4. mkindex without result ([email protected])
5. Re: Netdisco 1.3.2 Neighbor discovery (Simon De Matos)
--- Begin Message ---
On 08/11/13 04:34, Eric Miller wrote:
> On 2013-11-07 02:35, Huber, Peter wrote:
>> It seems to work perfectly. I can discover our extreme switches as it
>> was with netdisco version 1.3.x
> Thanks, this has been committed for inclusion in the next release of
> SNMP::Info.
Since this change I notice that netdisco 1 no longer includes the native
VLAN in the VLAN membership column? Is this intended behaviour?
Looking at HP devices I still see the native VLAN in the VLAN membership
column.
--
Robert Kerr
--- End Message ---
--- Begin Message ---
I just installed netdisco 1.3.2 on a debian wheezy and it is working fine.
Now I'm trying to add some mibs following the instructions in
../mibs/README. After running mkindex the mib_index.txt only contains the
line 'MIB Index' and nothing more.
So I tried the snmptranslate command from the promt and got the following
answers:
snmptranslate -M./hirschmann sysName
MIB search path: ./hirschmann
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
.
.
.
Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)
Cannot find module (SNMPv2-TM): At line 0 in (none)
Cannot find module (NET-SNMP-VACM-MIB): At line 0 in (none)
sysName: Unknown Object Identifier (Sub-id not found: (top) -> sysName)
It doesn't matter which of the mib directories I try: it's always the same
answer, always the same modules that cannot be found.
Are there any ideas?
greetings
Mathias
ArcelorMittal Bremen GmbH
Vorsitzender des Aufsichtsrates: Hedwig Vergote
Vorstand der GmbH: Dr. Dietmar Ringel, Vorsitzender, Rudolf Egbert, Jörn
Pufpaff, Peter Scherrer
Sitz der Gesellschaft: Bremen
Amtsgericht Bremen, HRB 15474 HB
--- End Message ---
--- Begin Message ---
You should be able to just add the new mib directory to your
netdisco.conf and depending upon what you're using them for snmp.conf as
well to have them recognized.
The mib_index.txt file is used by some utilities (walk_all) in the
netdisco-mibs distribution, but shouldn't be required for netdisco.
What version of net-snmp is installed? It appears that there has been a
change in the way net-snmp generates .index files which is what the
snmptranslate command is doing in the mkindex script. See
http://www.mail-archive.com/[email protected]/msg29058.html for a discussion.
Eric
On 2013-11-19 08:05, [email protected] wrote:
I just installed netdisco 1.3.2 on a debian wheezy and it is working
fine.
Now I'm trying to add some mibs following the instructions in
../mibs/README. After running mkindex the mib_index.txt only contains
the line 'MIB Index' and nothing more.
So I tried the snmptranslate command from the promt and got the
following answers:
snmptranslate -M./hirschmann sysName
MIB search path: ./hirschmann
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
.
.
.
Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none)
Cannot find module (SNMPv2-TM): At line 0 in (none)
Cannot find module (NET-SNMP-VACM-MIB): At line 0 in (none)
sysName: Unknown Object Identifier (Sub-id not found: (top) ->
sysName)
It doesn't matter which of the mib directories I try: it's always the
same answer, always the same modules that cannot be found.
Are there any ideas?
greetings
Mathias
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
You are right. There is a change in the way the .index is generated. I
found the file in /usr/share/snmp/mibs.
Now I try to get any further.
Thanks so far
Mathias
You should be able to just add the new mib directory to your
netdisco.conf and depending upon what you're using them for snmp.conf as
well to have them recognized.
The mib_index.txt file is used by some utilities (walk_all) in the
netdisco-mibs distribution, but shouldn't be required for netdisco.
What version of net-snmp is installed? It appears that there has been a
change in the way net-snmp generates .index files which is what the
snmptranslate command is doing in the mkindex script. See
http://www.mail-archive.com/[email protected]/msg29058.html
for a discussion.
Eric
ArcelorMittal Bremen GmbH
Vorsitzender des Aufsichtsrates: Hedwig Vergote
Vorstand der GmbH: Dr. Dietmar Ringel, Vorsitzender, Rudolf Egbert, Jörn
Pufpaff, Peter Scherrer
Sitz der Gesellschaft: Bremen
Amtsgericht Bremen, HRB 15474 HB
--- End Message ---
--- Begin Message ---
Hello again,
Sorry for this late answer, I've been very busy and couldn't work on Netdisco.
After checking everything again I founded a mistake I made (apologies
from the newbie). In the end, the right Info.PM has been patched
except for one of the modification:
my %l3sysoidmap = (
25506 => 'SNMP::Info::Layer3::3Com',
);
This wasn't added because it already exists and is named "25506 =>
'SNMP::Info::Layer3::H3C',"
Now everything works fine.
Thanks for everything !
Simon
Jethro R Binks <[email protected]> a écrit :
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.
------------------------------------------------------------------------------
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
--
Simon De Matos
----------------------------------
Service Infrastructures
Direction du Système d'Information
Pôle Ressources
----------------------------------
Université de Limoges
123, avenue Albert Thomas
87060 Limoges cedex
05.55.45.75.71
--- End Message ---
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
