# Fortinet MIB's

**URL:** https://discuss.elastic.co/t/fortinet-mibs/79092
**Category:** Logstash
**Created:** [March 17, 2017, 8:09pm UTC](https://discuss.elastic.co/t/fortinet-mibs/79092 "2017-03-17T20:09:11Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![sweath](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@sweath](https://discuss.elastic.co/u/sweath)
#### Post date: [March 17, 2017, 8:09pm UTC](https://discuss.elastic.co/t/fortinet-mibs/79092/1 "2017-03-17T20:09:11Z")

</div>

One of the steps to get snmptraps for Logstash running is importing MIB's from certain devices in your network. I'm running into an issue when trying to use the import.rb script on my FORTIGATE-FORTINET-MIB.mib file. The error that continually gets thrown is:

smidump: module `mibs//FORTINET-FORTIGATE-MIB.mib' contains errors, expect flawed output  
\*\*\* No nodes defined in: mibs//FORTINET-FORTIGATE-MIB.mib \*\*\*

There is another thread, [MIB OID Translation](https://discuss.elastic.co/t/mib-oid-translation/29710), that the user suggests he finally go it to work after solving some issues with "dependencies". I've ran smidump on the FORTIGATE-FORTINET-MIB.mib file using the -l5 switch and there is a list of errors such as:

mibs/FORTINET-FORTIGATE-MIB.mib:15: failed to locate MIB module `FORTINET-CORE-MIB' mibs/FORTINET-FORTIGATE-MIB.mib:119: unknown object identifier label`fortinet'  
mibs/FORTINET-FORTIGATE-MIB.mib:487: type `FnBoolState' of node`fgVdEnabled' does not resolve to a known base type  
mibs/FORTINET-FORTIGATE-MIB.mib:514: warning: index element `fgVdEntIndex' of row`fgVdEntry' should be not-accessible in SMIv2 MIB  
mibs/FORTINET-FORTIGATE-MIB.mib:903: type `FnIndex' of node`fgHwSensorEntIndex' does not resolve to a known base type  
mibs/FORTINET-FORTIGATE-MIB.mib:887: illegal base type `FnIndex' in index element`fgHwSensorEntIndex' of row fgHwSensorEntry  
mibs/FORTINET-FORTIGATE-MIB.mib:980: type `FnIndex' of node`fgProcessorEntIndex' does not resolve to a known base type  
mibs/FORTINET-FORTIGATE-MIB.mib:958: illegal base type `FnIndex' in index element`fgProcessorEntIndex' of row fgProcessorEntry  
mibs/FORTINET-FORTIGATE-MIB.mib:1019: type `FnIndex' of node`fgProcessorContainedIn' does not resolve to a known base type  
mibs/FORTINET-FORTIGATE-MIB.mib:1281: type `FnIndex' of node`fgProcModIndex' does not resolve to a known base type  
mibs/FORTINET-FORTIGATE-MIB.mib:1259: illegal base type `FnIndex' in index element`fgProcModIndex' of row fgProcessorModuleEntry  
mibs/FORTINET-FORTIGATE-MIB.mib:1558: type `FnIndex' of node`fgUsbportEntIndex' does not resolve to a known base type  
mibs/FORTINET-FORTIGATE-MIB.mib:1536: illegal base type `FnIndex' in index element`fgUsbportEntIndex' of row fgUsbportEntry....

The FORTINET-CORE-MIB.mib file is in the same directory, but no where does the import.rb script allow for passing another file, which I'm not even sure if that is what the error is wanting. I don't feel like I'm this incompetent but setting this "simple" log server up has made me feel as such. Can someone please assist in simply converting these Fortigate mib files, or perhaps is there a repository of existing yamls for specific vendors? Thank you.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 14, 2017, 8:09pm UTC](https://discuss.elastic.co/t/fortinet-mibs/79092/2 "2017-04-14T20:09:25Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
