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: IBM BNT device version number problem (Andy Ruhl)
2. Re: Error During Update (Oliver Gorwits)
3. Re: IBM BNT device version number problem (Jeroen van Ingen)
4. Re: IBM BNT device version number problem (Andy Ruhl)
5. Discovery on Meraki MX60 (Glenn Newman)
--- Begin Message ---
On Mon, May 18, 2015 at 6:57 AM, Jeroen van Ingen <
[email protected]> wrote:
> It depends. Are the models similar enough to share most of the vendor
> specific code or are they so different (eg completely different
> operating system or acquired / OEM'ed from different companies) that
> each model or group of models should be put in a separate device class?
>
> For example: depending on the model, an HP switch is classified as
> SNMP::Info::Layer2::HP4000 (old ProCurve models with only menu driven
> interface), SNMP::Info::Layer2::HP (more current ProCurve models that
> also have a CLI and differ in SNMP support), SNMP::Info::Layer2::HPVC
> for VirtualConnect interconnects in blade chassis and
> SNMP::Info::Layer3::H3C for HP switches running Comware operating system.
>
> Without any information about the (dis)similarities between the
> platforms and without seeing the MIB contents it's hard to advise or
> assist you.
>
> Can you provide a bit more background / info on the various models and
> can you upload the MIBs that you'd need in a Sourceforge ticket for
> netdisco-mibs ?
>
>
Pretty sure that they should be similar. They software releases for them
are usually numbered very similarly, and from a configuration standpoint
they work the same.
Andy
--- End Message ---
--- Begin Message ---
On 2015-05-18 11:02, Bavo Seesink wrote:
When i change the directory where netdisco 2.0 is installed.
and update from there the install works.
I have an install script to install netdisco 2.0 and it is not
installed with root access.
It is not really a problem now i know. :-)
Good to hear, many thanks.
regards,
oliver.
--- End Message ---
--- Begin Message ---
It depends. Are the models similar enough to share most of the vendor
specific code or are they so different (eg completely different
operating system or acquired / OEM'ed from different companies) that
each model or group of models should be put in a separate device class?
Without any information about the (dis)similarities between the
platforms and without seeing the MIB contents it's hard to advise or
assist you.
Can you provide a bit more background / info on the various models and
can you upload the MIBs that you'd need in a Sourceforge ticket for
netdisco-mibs ?
Pretty sure that they should be similar. They software releases for them
are usually numbered very similarly, and from a configuration standpoint
they work the same.
OK, I can try updating the IBMGbTor class for you so it loads the
additional MIBs and tries a second object to determine software version,
if the object we currently use isn't implemented.
Can you upload the relevant MIBs in a new ticket in
https://sourceforge.net/p/netdisco/nd-mibs/ ?
And do you know which object(s) in these MIBs should be used to
determine the software version on the other switch models?
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
--- End Message ---
--- Begin Message ---
On Tue, May 19, 2015 at 4:50 AM, Jeroen van Ingen <
[email protected]> wrote:
> OK, I can try updating the IBMGbTor class for you so it loads the
> additional MIBs and tries a second object to determine software version,
> if the object we currently use isn't implemented.
>
> Can you upload the relevant MIBs in a new ticket in
> https://sourceforge.net/p/netdisco/nd-mibs/ ?
>
> And do you know which object(s) in these MIBs should be used to
> determine the software version on the other switch models?
>
> I uploaded the MIB files. Unfortunately I don't know a lot about SNMP so I
don't know which object the device that is working (8124), but based on
what I know about these devices I would guess it's the same.
I can test whatever you come up with. Otherwise I will have to put some
time into figuring out how the MIB is used.
Andy
--- End Message ---
--- Begin Message ---
I am not able to do discovery on a Meraki MX60. Is there another way to add
it? Is there a way to tell it to use the Meraki MIB when discovering it? I
downloaded the MIB, created a "Meraki" directory under
/home/netdisco/netdisco-mibs. I modified snmp.conf in that directory and
modified the path to reflect that. I copied that to /home/netdisco/.snmp/.
Here is the command and a tcpdump of the result:
~/bin/netdisco-do -D discover -d 10.49.236.254
07:09:41.084672 IP 10.52.1.20.51672 > 10.49.236.254.161: C=public
GetRequest(28) .1.3.6.1.2.1.1.3.0
07:09:41.193572 IP 10.49.236.254.161 > 10.52.1.20.51672: C=public
GetResponse(28) .1.3.6.1.2.1.1.3.0=[noSuchObject]
07:09:41.194423 IP 10.52.1.20.59586 > 10.49.236.254.161: C=public
GetRequest(28) .1.3.6.1.2.1.1.3.0
07:09:41.300253 IP 10.49.236.254.161 > 10.52.1.20.59586: C=public
GetResponse(28) noSuchName@1 .1.3.6.1.2.1.1.3.0=
07:09:41.300799 IP 10.52.1.20.51992 > 10.49.236.254.161: GetRequest(28)
.1.3.6.1.2.1.1.3.0
07:09:44.303924 IP 10.52.1.20.51992 > 10.49.236.254.161: GetRequest(28)
.1.3.6.1.2.1.1.3.0
07:09:47.307028 IP 10.52.1.20.5992 > 10.49.236.254.161: GetRequest(28)
.1.3.6.1.2.1.1.3.0
Also ran this command and showing the tail of the results:
./snmpwalkmib -c public -d 10.49.236.254 -w meraki
MIB search path:
/home/netdisco/netdisco-mibs/rfc:/home/netdisco/netdisco-mibs/net-snmp:/home/netdisco/netdisco-mibs/cisco:/home/netdisco/netdisco-mibs/3com:/home/netdisco/netdisco-mibs/aerohive:/home/netdisco/netdisco-mibs/alcatel:/home/netdisco/netdisco-mibs/allied:/home/netdisco/netdisco-mibs/apc:/home/netdisco/netdisco-mibs/arista:/home/netdisco/netdisco-mibs/aruba:/home/netdisco/netdisco-mibs/asante:/home/netdisco/netdisco-mibs/avaya:/home/netdisco/netdisco-mibs/bluecoat:/home/netdisco/netdisco-mibs/bluesocket:/home/netdisco/netdisco-mibs/cabletron:/home/netdisco/netdisco-mibs/checkpoint:/home/netdisco/netdisco-mibs/citrix:/home/netdisco/netdisco-mibs/colubris:/home/netdisco/netdisco-mibs/cyclades:/home/netdisco/netdisco-mibs/d-link:/home/netdisco/netdisco-mibs/dell:/home/netdisco/netdisco-mibs/enterasys:/home/netdisco/netdisco-mibs/extreme:/home/netdisco/netdisco-mibs/extricom:/home/netdisco/netdisco-mibs/f5:/home/netdisco/netdisco-mibs/force10:/home/netdisco/netdisco-mibs/fortinet:/home/netdisco/netdisco-mibs/foundry:/home/netdisco/netdisco-mibs/h3c:/home/netdisco/netdisco-mibs/hp:/home/netdisco/netdisco-mibs/huawei:/home/netdisco/netdisco-mibs/ibm:/home/netdisco/netdisco-mibs/juniper:/home/netdisco/netdisco-mibs/lantronix:/home/netdisco/netdisco-mibs/meraki:/home/netdisco/netdisco-mibs/mikrotik:/home/netdisco/netdisco-mibs/netapp:/home/netdisco/netdisco-mibs/netgear:/home/netdisco/netdisco-mibs/netscreen:/home/netdisco/netdisco-mibs/nortel:/home/netdisco/netdisco-mibs/packetfront:/home/netdisco/netdisco-mibs/paloalto:/home/netdisco/netdisco-mibs/pica8:/home/netdisco/netdisco-mibs/rad:/home/netdisco/netdisco-mibs/riverbed:/home/netdisco/netdisco-mibs/ruckus:/home/netdisco/netdisco-mibs/sonicwall:/home/netdisco/netdisco-mibs/trapeze:/home/netdisco/netdisco-mibs/xirrus
Cannot find module (meraki): At line 1 in (none)
--- End Message ---
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users