FORTINET-CORE-MIB

Monitored by Observium
        MIB module for Fortinet network devices.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Device identity
Explore Observium network monitoring
Source file
FORTINET-CORE-MIB
Last revised
Identity
fortinet
Base OID
1.3.6.1.4.1.12356
Imported Objects
IF-MIB ifIndex
INET-ADDRESS-MIB InetAddress InetAddressPrefixLength InetAddressType
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-MIB sysName
SNMPv2-SMI enterprises Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DisplayString TEXTUAL-CONVENTION (no object page)
Net-SNMP examples using the fortinet MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'FORTINET-CORE-MIB' -M '/opt/observium/mibs/fortinet:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FORTINET-CORE-MIB::fortinet'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'FORTINET-CORE-MIB' -M '/opt/observium/mibs/fortinet:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FORTINET-CORE-MIB::fortinet'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (21)
1 directly used by Observium
.1.3.6.1.4.1.12356
.1.3.6.1.4.1.12356.100
.1.3.6.1.4.1.12356.100.1
.1.3.6.1.4.1.12356.100.1.1
fnSysSerial OBS ✓
.1.3.6.1.4.1.12356.100.1.1.1
.1.3.6.1.4.1.12356.100.1.2
.1.3.6.1.4.1.12356.100.1.2.1
.1.3.6.1.4.1.12356.100.1.2.100
.1.3.6.1.4.1.12356.100.1.2.100.1
.1.3.6.1.4.1.12356.100.1.2.100.2
.1.3.6.1.4.1.12356.100.1.2.100.2.1
Integer32
.1.3.6.1.4.1.12356.100.1.2.100.2.1.1
.1.3.6.1.4.1.12356.100.1.2.100.2.1.2
.1.3.6.1.4.1.12356.100.1.2.100.2.1.3
.1.3.6.1.4.1.12356.100.1.2.100.2.1.4
.1.3.6.1.4.1.12356.100.1.2.100.2.1.5
.1.3.6.1.4.1.12356.100.1.3
.1.3.6.1.4.1.12356.100.1.3.0
.1.3.6.1.4.1.12356.100.1.3.1
.1.3.6.1.4.1.12356.100.1.3.1.1
.1.3.6.1.4.1.12356.100.10
Dependencies (7) 6 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. IANAifType-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMPv2-MIBrfc
  6. IF-MIBrfc
  7. INET-ADDRESS-MIBrfc
  8. FORTINET-CORE-MIBfortinetselected
Type Definitions (4)
Enumeration
disabled(1)
enabled(2)
Integer32 range: 0..2147483647
Enumeration
english(1)
simplifiedChinese(2)
japanese(3)
korean(4)
spanish(5)
traditionalChinese(6)
french(7)
portuguese(8)
undefined(255)
Enumeration
ip(0)
icmp(1)
igmp(2)
ipip(4)
tcp(6)
egp(8)
pup(12)
udp(17)
idp(22)
ipv6(41)
rsvp(46)
gre(47)
esp(50)
ah(51)
ospf(89)
pim(103)
comp(108)
raw(255)
Conformance Groups (5)
Objects relating to the physical device.
.1.3.6.1.4.1.12356.100.10.1
Objects relating the management of a device.
.1.3.6.1.4.1.12356.100.10.2
Administration access control objects.
.1.3.6.1.4.1.12356.100.10.3
Event notifications
.1.3.6.1.4.1.12356.100.10.4
Object identifiers used in notifications
.1.3.6.1.4.1.12356.100.10.5
Compliance Statements (1)

OID .1.3.6.1.4.1.12356.100.10.100
The compliance statement for the application MIB.
Required groups
optional fnSystemComplianceGroup This group is mandatory for all Fortinet network appliances
supporting this MIB.
optional fnMgmtComplianceGroup This group is optional for devices that do not support common
management interface options such as multiple languages.
optional fnAdminComplianceGroup This group should be accessible on any device supporting
administrator authentication.
optional fnTrapsComplianceGroup Traps are optional. Not all models support all traps. Consult
product literature to see which traps are supported.
optional fnNotifObjectsComplianceGroup Object identifiers used in notifications. Objects are required
if their containing trap is implemented.
Notifications / Traps (13)
NameOIDDescription
.1.3.6.1.4.1.12356.100.1.3.0.101
Indicates that the CPU usage has exceeded the configured threshold.
.1.3.6.1.4.1.12356.100.1.3.0.102
Indicates memory usage has exceeded the configured threshold.
.1.3.6.1.4.1.12356.100.1.3.0.103
Log disk usage has exceeded the configured threshold. Only available
on devices with log disks.
.1.3.6.1.4.1.12356.100.1.3.0.104
A temperature sensor on the device has exceeded its threshold.
Not all devices have thermal sensors. See manual for specifications.
.1.3.6.1.4.1.12356.100.1.3.0.105
Power levels have fluctuated outside of normal levels. Not all devices
have voltage monitoring instrumentation. See manual for specifications.
.1.3.6.1.4.1.12356.100.1.3.0.106
Power supply failure detected. Not available on all models. Available
on some devices which support redundant power supplies. See manual
for specifications.
.1.3.6.1.4.1.12356.100.1.3.0.107
An AMC interface entered bypass mode. Available on models with an AMC
expansion slot. Used with the ASM-CX4 and ASM-FX2 cards.
.1.3.6.1.4.1.12356.100.1.3.0.108
A fan failure has been detected. Not all devices have fan sensors.
See manual for specifications.
.1.3.6.1.4.1.12356.100.1.3.0.109
Interface entered bypass mode. Available on models with bypass ports.
.1.3.6.1.4.1.12356.100.1.3.0.110
Interface exited bypass mode. Available on models with bypass ports.
.1.3.6.1.4.1.12356.100.1.3.0.111
BIOS security level has been change.
.1.3.6.1.4.1.12356.100.1.3.0.201
Indicates that the IP address of the specified interface has been changed.
.1.3.6.1.4.1.12356.100.1.3.0.999
Trap sent for diagnostic purposes by an administrator.