Fortinet black logo

Administration Guide

Fortinet MIBs

Fortinet MIBs

The FortiProxy SNMP agent supports Fortinet proprietary MIBs, as well as standard RFC 1213 and RFC 2665 MIBs. RFC support includes support for the parts of RFC 2665 (Ethernet-like MIB) and the parts of RFC 1213 (MIB II) that apply to FortiProxy unit configuration.

There are two MIB files for FortiProxy units; both files are required for proper SNMP data collection:

  • The Fortinet MIB: contains traps, fields, and information that is common to all Fortinet products.
  • The FortiProxy MIB: contains traps, fields, and information that is specific to FortiProxy units.

The Fortinet and FortiProxy MIB files are available for download on the Fortinet Customer Support site. Each Fortinet product has its own MIB—if you use other Fortinet products, you need to download their MIB files as well.

The Fortinet MIB and FortiProxy MIB, along with the two RFC MIBs, are listed in the table in this section.

To download the MIB files, go to System > SNMP and select a MIB link in the SNMP section. See SNMP.

Your SNMP manager may already include standard and private MIBs in a compiled database that is ready to use. You must add the Fortinet proprietary MIB to this database to have access to the Fortinet-specific information.

MIB files are updated for each version of FortiProxy. When upgrading the firmware, ensure that you update the Fortinet FortiProxy MIB file compiled in your SNMP manager as well.
MIB file name Description
FORTINET-CORE-MIB.mib The Fortinet MIB includes all system configuration information and trap information that is common to all Fortinet products. Your SNMP manager requires this information to monitor FortiProxy unit configuration settings and receive traps from the FortiProxy SNMP agent.
FORTINET-FORTIPROXY-MIB.mib The FortiProxy MIB includes all system configuration information and trap information that is specific to FortiProxy units. Your SNMP manager requires this information to monitor FortiProxy configuration settings and receive traps from the FortiProxy SNMP agent. FortiManager systems require this MIB to monitor FortiProxy units.

SNMP get command syntax

Normally, to get configuration and status information for a FortiProxy unit, an SNMP manager would use an SNMP get command to get the information in a MIB field. The SNMP get command syntax would be similar to:

snmpget -v2c -c <community_name> <address_ipv4> {<OID> | <MIB_field>}

    where:

  • <community_name> refers to the SNMP community name added to the FortiProxy configuration. You can add more than one community name to a FortiProxy SNMP configuration. The most commonly used community name is public. For security reasons, Fortinet recommends that neither public nor private be used for SNMP community names.
  • <address_ipv4> is the IP address of the FortiProxy interface that the SNMP manager connects to
  • {<OID> | <MIB_field>} is the object identifier for the MIB field or the MIB field name itself.

For example, to query the firmware version running on the FortiProxy unit, the following command could be issued:

snmpget -v2c -c public 10.10.10.1 1.3.6.1.4.1.12356.109.4.1.1.0

In this example, the community name is public, the IP address of the interface configured for SNMP management access is 10.10.10.1. The firmware version is queried using the MIB field fchSysVersion, the OID for which is 1.3.6.1.4.1.12356.109.4.1.1.0.

The value returned is a string with a value of v2.0,build0225,130213.

Fortinet MIBs

The FortiProxy SNMP agent supports Fortinet proprietary MIBs, as well as standard RFC 1213 and RFC 2665 MIBs. RFC support includes support for the parts of RFC 2665 (Ethernet-like MIB) and the parts of RFC 1213 (MIB II) that apply to FortiProxy unit configuration.

There are two MIB files for FortiProxy units; both files are required for proper SNMP data collection:

  • The Fortinet MIB: contains traps, fields, and information that is common to all Fortinet products.
  • The FortiProxy MIB: contains traps, fields, and information that is specific to FortiProxy units.

The Fortinet and FortiProxy MIB files are available for download on the Fortinet Customer Support site. Each Fortinet product has its own MIB—if you use other Fortinet products, you need to download their MIB files as well.

The Fortinet MIB and FortiProxy MIB, along with the two RFC MIBs, are listed in the table in this section.

To download the MIB files, go to System > SNMP and select a MIB link in the SNMP section. See SNMP.

Your SNMP manager may already include standard and private MIBs in a compiled database that is ready to use. You must add the Fortinet proprietary MIB to this database to have access to the Fortinet-specific information.

MIB files are updated for each version of FortiProxy. When upgrading the firmware, ensure that you update the Fortinet FortiProxy MIB file compiled in your SNMP manager as well.
MIB file name Description
FORTINET-CORE-MIB.mib The Fortinet MIB includes all system configuration information and trap information that is common to all Fortinet products. Your SNMP manager requires this information to monitor FortiProxy unit configuration settings and receive traps from the FortiProxy SNMP agent.
FORTINET-FORTIPROXY-MIB.mib The FortiProxy MIB includes all system configuration information and trap information that is specific to FortiProxy units. Your SNMP manager requires this information to monitor FortiProxy configuration settings and receive traps from the FortiProxy SNMP agent. FortiManager systems require this MIB to monitor FortiProxy units.

SNMP get command syntax

Normally, to get configuration and status information for a FortiProxy unit, an SNMP manager would use an SNMP get command to get the information in a MIB field. The SNMP get command syntax would be similar to:

snmpget -v2c -c <community_name> <address_ipv4> {<OID> | <MIB_field>}

    where:

  • <community_name> refers to the SNMP community name added to the FortiProxy configuration. You can add more than one community name to a FortiProxy SNMP configuration. The most commonly used community name is public. For security reasons, Fortinet recommends that neither public nor private be used for SNMP community names.
  • <address_ipv4> is the IP address of the FortiProxy interface that the SNMP manager connects to
  • {<OID> | <MIB_field>} is the object identifier for the MIB field or the MIB field name itself.

For example, to query the firmware version running on the FortiProxy unit, the following command could be issued:

snmpget -v2c -c public 10.10.10.1 1.3.6.1.4.1.12356.109.4.1.1.0

In this example, the community name is public, the IP address of the interface configured for SNMP management access is 10.10.10.1. The firmware version is queried using the MIB field fchSysVersion, the OID for which is 1.3.6.1.4.1.12356.109.4.1.1.0.

The value returned is a string with a value of v2.0,build0225,130213.