Issues modeling Fortinet devices
search cancel

Issues modeling Fortinet devices

book

Article ID: 127083

calendar_today

Updated On:

Products

Spectrum

Issue/Introduction

Issues modeling Fort Manager at oid 1.3.6.1.4.1.12356.103.1.10004 and a Fort Analyzer at oid 1.3.6.1.4.1.12356.103.3.10005.

Some issues seen:

The Interfaces tab does not populate
The Performance tab is not available
Not all ip addresses are associated with the model

Environment

Release:
Component: SPCAEM

Cause


INTERFACES TAB:

This looks to be an issue with the mib on the device. For example, in the interfaces mib, when trying to query the interfaces mib using MIB Tools, we get the following error: 

"Query from interfaces failed. Unable to send SNMP Request." 

The reason for the error is following entries in the interfaces mib on the device: 

1.3.6.1.2.1.2.2.1.23.1 , NULL , NULL 
1.3.6.1.2.1.2.2.1.23.2 , NULL , NULL 
1.3.6.1.2.1.2.2.1.23.3 , NULL , NULL 
1.3.6.1.2.1.2.2.1.23.4 , NULL , NULL 
1.3.6.1.2.1.2.2.1.23.5 , NULL , NULL 
1.3.6.1.2.1.2.2.1.23.6 , NULL , NULL 
1.3.6.1.2.1.2.2.1.23.7 , NULL , NULL 
1.3.6.1.2.1.2.2.1.23.8 , NULL , NULL 

As per RFC1213-MIB, the IF table with reference to '1.3.6.1.2.1.2.2.1.23' OID does NOT exist. Please refer to the below RFC mibs. 
http://www.oidview.com/mibs/0/RFC1213-MIB.html 
http://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?module=RFC1213-MIB&fournisseur=ietf 

If we remove these entries from the walk file and recreate the simulation without these entries, there are no issues. 

There are several other places in the mib where we are seeing similar issues of mib oids that do not exist in the RFC and mib definitions according to the published mibs.


PERFORMANCE TAB: 

The NRM_CPUUtil and NRM_MEMUtil attributes may not be pointing to the correct OID. 

NRM_CPUUtilAttr needs to be set to 0x5b10088 - fgSysCpuUsage

NRM_MEMUtilAttr needs to be set to 0x5b10089 - fgSysMemUsage

Set these attributes and then Reconfigure the model - right-click > Reconfiguration > Reconfigure Model



Resolution

This is an issue that needs to be addressed at the vendor.