Snmpwalk & the Fortinet MIB files ...

[NorthsideCC]

Hi, I' ve recently been configuring our monitoring system (Opsview) to poll our new Fortigate 100D' s via snmp and I' ve noticed something strange with the MIB files provided from Fortinet. Basically, I' m expecting that the Fortinet MIB files, when loaded into the right place on my server (/usr/share/snmp/mibs), will essentially aid in a more readable output from an snmpwalk command. A good explanation of what I' m trying to achieve can be found here. Now before I get dismissed to the Opsview forums, when I simply run a snmpwalk command I get the generic sort of output you' d expect if there wasn' t a MIB file loaded, eg.:

SNMPv2-SMI::enterprises.12356.101.4.1.3.0 = Gauge32: 0

Whereas, I' d expect to be getting:

FORTINET-FORTIGATE-MIB::fgSysCpuUsage.0 = Gauge32: 0

I' ve loaded both the Core & Fortigate MIB files into place. If I give snmpwalk both an OID & the Fortigate MIB it gives me back the kind of output I' d expect, but that defeats the point for me; it' s telling essentially what I already know. Any thoughts? Thanks.

[emnoc]

Those two are the same oids.What I would do is to snmpwalk using numerical output for both of them and compare and or snmptranslate the fortigateone. snmpwalk -c public x.x.x.x -On SNMPv2-SMI::enterprises.12356.101.4.1 Since I lost my fortigate-support password ( can' t find my mib.txt file ), I would have done the later for you :) .1.3.6.1.4.1.12356.101.4.1.3

[NorthsideCC]

Yes, I know they' re the same OIDs. The point is an snmpwalk should be showing the latter output, not the generic numerical version. Normally, with SNMP, you load your MIB files so that you can get a human-friendly output, rather than numerical OIDs. The Fortigate MIBs aren' t working. I' ve been able to achieve this easily with MIB files from other vendors.