3 answers
- 210
Mike,
I believe we have found and fixed this problem, it is with missing OID entries in nmis_mibs.oid, and we have some very recently updated Fortinet models. Drop me an email and I will send the details.
Regards
Keith
Add your comment... - 210
Just to update, Keith reached out to me and provided some fixed oid output and Fortinet model to deal with the Fortigate device. It's now polling fine, just had to manually add interfaces to poll as it didn't add all the up/up interfaces oddly.
So good news if using Fortinet/Fortigate devices, this should probably make its way into the next release. Now for the rest of the Forti-things...
Thanks Keith!
Add your comment... - 10-1
For anyone looking for a fix to Fortinet now, add the following lines to your /usr/local/nmis8/mibs/nmis_mibs.oid
"fgVdNumber" "1.3.6.1.4.1.12356.101.3.1.1"
"fgVdMaxVdoms" "1.3.6.1.4.1.12356.101.3.1.2"
"fgVdEnabled" "1.3.6.1.4.1.12356.101.3.1.3"The new models are available if anyone is in a hurry.
Add your comment...
Hi, using a nmis combo vm to test features with a Fortinet appliance, and getting some unexpected behavior. The device is a fortigate 7060, and it is confusing nmis' snmp poller when it returns an oid in response to the query for the object identifier.
21:40:51 getNodeInfo,sysObjectId=1.3.6.1.4.1.12356.101.1.70001, sysObjectName=enterprises.12356.101.1.70001
21:40:51 getNodeInfo,sysDescr=FORTIGATE7060E
21:40:51 getNodeInfo,node model=Fortinet-FG set by node config
21:40:51 getNodeInfo,Finished with exit=0 nodedown=false snmpdown= wmidown=
21:40:51 runReach,Starting node FORTIGATE7060E, type=router
21:40:53 doCollect,Starting collect, node FORTIGATE7060E
21:40:53 doCollect,node=FORTIGATE7060E role=core type=router
21:40:53 doCollect,vendor=Fortinet, Inc. model=Fortinet-FG interfaces=71
21:40:53 runPing,INFO (FORTIGATE7060E) PING min/avg/max = /35.30/ ms loss=0%
21:40:53 runPing,Finished with exit=1, nodedown=false nodestatus=
21:40:53 updateNodeInfo,Starting Update Node Info, node FORTIGATE7060E
21:40:53 updateNodeInfo,Finished with exit=0
21:40:53 doCollect,Error: updateNodeInfo for FORTIGATE7060E failed: error=loadInfo failed for FORTIGATE7060E: , snmp_error=Expected OBJECT IDENTIFIER in dotted notation, wmi_error=
21:40:53 runServices,Starting Services stats, node=FORTIGATE7060E, nodeType=router
21:40:53 runServices,Service port22 on FORTIGATE7060E (interval "5m") last ran at 16-Sep-2017 21:40:06, skipping this time.
21:40:53 runServices,Finished
Is there a good way to simply ignore this? Fortinet seems to be trying to be crafty, but just confusing the snmp engine. It seems more in the snmp bits than the nmis.pl that is rejecting that.
That oid is referenced to the fortigate mib if you wanted to recurse it as:
fgt7000E OBJECT IDENTIFIER ::= { fgModel 70001 }
This is with nmis 8.6.1G just downloaded today.
Thanks in advance!