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. Error whilst searching for Dlink devices (Hans Erasmus)
2. Re: Error whilst searching for Dlink devices (Oliver Gorwits)
3. Re: Error whilst searching for Dlink devices (Hans Erasmus)
--- Begin Message ---
Good day everyone.
First off, thanks for a brilliant, brilliant piece of software. This thing
is TRULY amazing.
First off, I have gone through quite a few posts and suggestions, and even
tried my hand at git and other things (which is the equivalent of creating
a nuclear bomb if you know me at all), to try and get our implementation of
Netdisco to discover D-link devices correctly and comprehensively. I have
downloaded a load of MIBS to try and add them to our netdisco-mibs
directory, and even tried the instructions found here
<https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs> which ended
disastrously.
In short, we have a combination of Juniper, Dlink and Ruijie devices in our
network. I have MIB files for the Ruijie as well, but I first wanted to get
the Dlink stuff going (we have roughly about 2500 D-link devices).
When I try to discover a D-link device, the following shows up in the
backend-log:
Cannot find module (DES-1210-28-AX): At line 1 in (none)
So to my newbie eyes it seems that when it queries a D-link device, it will
try to discover it with said MIB, which is wrong. In the web interface I
can see (under device), that it shows SNMP Class -> SNMP::Info, but for
Ruijie devices it shows SNMP Class -> SNMP::Info::Layer3
<https://metacpan.org/pod/SNMP%3A%3AInfo%3A%3ALayer3>
I have raised a ticket/issue/bug here
<https://github.com/netdisco/netdisco-mibs/issues/19>.
Is this purely a MIB issue, or is there something else to be done?
I am in no way shape or form a programmer. I am an Infrastructure Architect
with ZERO coding skills. So please, be gentle, and also don't assume I will
know what you mean.
Any help would be gladly appreciated!
Regards
Hans
--- End Message ---
--- Begin Message ---
Hi Hans,
Thanks for persevering with this! I hope that we can get this working...
I will explain first what the "SNMP Class" means, as it might shed some
light for you. If you look at the page below, there are many modules for
different vendors (we even have one for DLink!):
https://metacpan.org/release/SNMP-Info
Netdisco tries to assign the most specific class from that page to each
device. Failing a truly vendor-specific class, the device will get one
which maps to its reported capabilities (switch = Layer2, router =
Layer3).
So, your Ruijie is reporting it can route, so gets "SNMP::Info::Layer3".
Sadly your Dlink is reporting little or nothing, so gets the very basic
"SNMP::Info". I hope that makes sense.
What we need to do is nudge Netdisco to select the more appropriate
device class. Let's ask your devices to describe themselves:
~netdisco/bin/netdisco-do show -d 1.2.3.4 -DI -e layers
~netdisco/bin/netdisco-do show -d 1.2.3.4 -DI -e description
~netdisco/bin/netdisco-do show -d 1.2.3.4 -DI -e id
You can add the output of those three commands, for different devices
(DLink, Ruijie, etc) to the github issue you opened.
Many thanks!
regards,
oliver.
On 2017-08-03 18:22, Hans Erasmus wrote:
Good day everyone.
First off, thanks for a brilliant, brilliant piece of software. This
thing is TRULY amazing.
First off, I have gone through quite a few posts and suggestions, and
even tried my hand at git and other things (which is the equivalent of
creating a nuclear bomb if you know me at all), to try and get our
implementation of Netdisco to discover D-link devices correctly and
comprehensively. I have downloaded a load of MIBS to try and add
them to our netdisco-mibs directory, and even tried the
instructions found here [1] which ended disastrously.
In short, we have a combination of Juniper, Dlink and Ruijie devices
in our network. I have MIB files for the Ruijie as well, but I first
wanted to get the Dlink stuff going (we have roughly about 2500 D-link
devices).
When I try to discover a D-link device, the following shows up in the
backend-log:
Cannot find module (DES-1210-28-AX): At line 1 in (none)
So to my newbie eyes it seems that when it queries a D-link device, it
will try to discover it with said MIB, which is wrong. In the web
interface I can see (under device), that it shows SNMP Class ->
SNMP::Info, but for Ruijie devices it shows SNMP Class
-> SNMP::Info::Layer3 [2]
I have raised a ticket/issue/bug here [3].
Is this purely a MIB issue, or is there something else to be done?
I am in no way shape or form a programmer. I am an Infrastructure
Architect with ZERO coding skills. So please, be gentle, and also
don't assume I will know what you mean.
Any help would be gladly appreciated!
Regards
Hans
Links:
------
[1] https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs
[2] https://metacpan.org/pod/SNMP%3A%3AInfo%3A%3ALayer3
[3] https://github.com/netdisco/netdisco-mibs/issues/19
------------------------------------------------------------------------------
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 ---
Hi Oliver
Thanks for the speedy reply, as well as the detail. I do understand what
you have explained. Attached to mentioned Issue in github I have attached
the output of the commands you have asked for. It is quite late at night in
South Africa, so I was only able to get the responses formulated based on
two of the models we currently have in use (both being deployed as
routers), but I have a funny feeling if we are able to fix just one, a lot
more of them will just "magically" work. The issue seems to be quite
generic, therefore I think the solution will as well.
Tomorrow when I am back at the office, I will try and get the responses for
at least 2 or 3 more of the devices we are using (1 type will be a router
and the other switches) and also attach those. Then whomever will be
looking at that issue, will at least be able to have a SNMP response to
correlate to MIB files as found in the ZIP file I have uploaded.
I am truly sorry that I am not personally capable of doing the verification
of the mibs myself, and submitting them back to the community. Maybe
sometime in the future I can rope in the help of someone much more skilled
than me, who is willing to spend an hour or so explaining to me how I need
to fix my system in order to do the MIB checks, and submitting them back to
the community. This software is solving a lot of my problems, and curing
quite a few headaches, so I am more than willing to give back to the
community if I can at all.
Thanks again to anyone involved in Netdisco, from the little I have seen so
far, this is truly doing an amazing job!
Have a nice day!
Hans
On Thu, 3 Aug 2017 at 22:22 Oliver Gorwits <[email protected]> wrote:
> Hi Hans,
>
> Thanks for persevering with this! I hope that we can get this working...
>
> I will explain first what the "SNMP Class" means, as it might shed some
> light for you. If you look at the page below, there are many modules for
> different vendors (we even have one for DLink!):
>
> https://metacpan.org/release/SNMP-Info
>
> Netdisco tries to assign the most specific class from that page to each
> device. Failing a truly vendor-specific class, the device will get one
> which maps to its reported capabilities (switch = Layer2, router =
> Layer3).
>
> So, your Ruijie is reporting it can route, so gets "SNMP::Info::Layer3".
> Sadly your Dlink is reporting little or nothing, so gets the very basic
> "SNMP::Info". I hope that makes sense.
>
> What we need to do is nudge Netdisco to select the more appropriate
> device class. Let's ask your devices to describe themselves:
>
> ~netdisco/bin/netdisco-do show -d 1.2.3.4 -DI -e layers
> ~netdisco/bin/netdisco-do show -d 1.2.3.4 -DI -e description
> ~netdisco/bin/netdisco-do show -d 1.2.3.4 -DI -e id
>
> You can add the output of those three commands, for different devices
> (DLink, Ruijie, etc) to the github issue you opened.
>
> Many thanks!
>
> regards,
> oliver.
>
> On 2017-08-03 18:22, Hans Erasmus wrote:
> > Good day everyone.
> >
> > First off, thanks for a brilliant, brilliant piece of software. This
> > thing is TRULY amazing.
> >
> > First off, I have gone through quite a few posts and suggestions, and
> > even tried my hand at git and other things (which is the equivalent of
> > creating a nuclear bomb if you know me at all), to try and get our
> > implementation of Netdisco to discover D-link devices correctly and
> > comprehensively. I have downloaded a load of MIBS to try and add
> > them to our netdisco-mibs directory, and even tried the
> > instructions found here [1] which ended disastrously.
> >
> > In short, we have a combination of Juniper, Dlink and Ruijie devices
> > in our network. I have MIB files for the Ruijie as well, but I first
> > wanted to get the Dlink stuff going (we have roughly about 2500 D-link
> > devices).
> >
> > When I try to discover a D-link device, the following shows up in the
> > backend-log:
> >
> > Cannot find module (DES-1210-28-AX): At line 1 in (none)
> >
> > So to my newbie eyes it seems that when it queries a D-link device, it
> > will try to discover it with said MIB, which is wrong. In the web
> > interface I can see (under device), that it shows SNMP Class ->
> > SNMP::Info, but for Ruijie devices it shows SNMP Class
> > -> SNMP::Info::Layer3 [2]
> >
> > I have raised a ticket/issue/bug here [3].
> >
> > Is this purely a MIB issue, or is there something else to be done?
> >
> > I am in no way shape or form a programmer. I am an Infrastructure
> > Architect with ZERO coding skills. So please, be gentle, and also
> > don't assume I will know what you mean.
> >
> > Any help would be gladly appreciated!
> >
> > Regards
> > Hans
> >
> > Links:
> > ------
> > [1] https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs
> > [2] https://metacpan.org/pod/SNMP%3A%3AInfo%3A%3ALayer3
> > [3] https://github.com/netdisco/netdisco-mibs/issues/19
> >
> >
> ------------------------------------------------------------------------------
> > 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
