Recent changes to nd-mibs

#12 MIB update for Fortigate

Jeroen van Ingen — Thu, 05 Jan 2017 16:54:42 -0000

status: accepted --> closed

#12 MIB update for Fortigate

Jeroen van Ingen — Thu, 05 Jan 2017 16:54:15 -0000

status: open --> accepted
assigned_to: Jeroen van Ingen

#11 MIB support for Opengear

Jeroen van Ingen — Thu, 05 Jan 2017 16:31:56 -0000

status: open --> closed
assigned_to: Jeroen van Ingen

MIB update for Fortigate

falz — Tue, 27 Dec 2016 14:26:27 -0000

Updated MIB file for newer fortigate prodocuts. Current version in code was dated 201307260000Z, this version is dated 201606170000Z.

I was able to drop in as replacement, restart services, and it correctly identified a newer device (1000D aka Model.10005)

MIB update for Fortigate

falz — Tue, 27 Dec 2016 14:26:27 -0000

Ticket 12 has been modified: MIB update for Fortigate
Edited By: Jeroen van Ingen (jeroenvi)
Status updated: u'open' => u'accepted'
Owner updated: None => u'jeroenvi'

MIB update for Fortigate

falz — Tue, 27 Dec 2016 14:26:27 -0000

Ticket 12 has been modified: MIB update for Fortigate
Edited By: Jeroen van Ingen (jeroenvi)
Status updated: u'accepted' => u'closed'

MIB support for Opengear

falz — Tue, 27 Dec 2016 14:19:58 -0000

Requesting to add support for Opengear MIBS.

Vendor OID is enterprises.25049.1.81

I believe the two MIBS below are what would be required:

OG-PRODUCTS-MIB / OG-PRODUCTS-MIB.mib
OG-SMI-MIB / OG-SMI-MIB.mib
http://ftp.opengear.com/download/snmp/mibs/OG-SMI-MIB.mib
http://ftp.opengear.com/download/snmp/mibs/OG-PRODUCTS-MIB.mib

I could not find any docs or samples of how to properly add MIBs, if they existed or would exist I could go through this and add as a patch instead of a request.

MIB support for Opengear

falz — Tue, 27 Dec 2016 14:19:58 -0000

Ticket 11 has been modified: MIB support for Opengear
Edited By: Jeroen van Ingen (jeroenvi)
Status updated: u'open' => u'closed'
Owner updated: None => u'jeroenvi'

#3 Motorola / Symbol MIB's

Jeroen van Ingen — Mon, 12 Sep 2016 08:53:59 -0000

The WING-MIB in the supplied tarball results in a lot of object relocations, so it's not a backwards compatible change: it would break a lot of translations for other Motorola/Symbol products. I don't know the product ranges, so can't say whether it depends on model or on software version.

Lee: is this still important for you to get working? If so, can you give more context about the product ranges that use these MIBs, what software they run, etc?

#9 Please add MIB files for CheckPoint

Max Kosmach — Mon, 12 Sep 2016 08:29:40 -0000

Thank You Jeroen!
Will ty to upgrade our CP (snmp support in VSX 77.10 is strange) later and add support for CP and CP VSX to netdisco.