Descritpion
This article describes that to monitor performance of the IT unit, one of the most popular method is to use Simple Network Management Protocol (SNMP).
Some users prefer not to get all the information available on SNMP.
On these type of cases it is necessary to go through the Management Information Base (MIBs file) to get all different Object Identifiers (OIDs).
If there is a specific OIDs, only that part of the status of the unit will appear instead of all SNMP walkthrough.
Scope
- This article will show the typical OIDs to monitor and how to get all the possible OIDs.
- To get OIDs is a must to be familiar of how SNMP and MIBs works.
- Firmware 6.4.6 MIB database of FortiManager/FortiAnalyzer is used.
- Use the correct firmware version, if OIDs provided here does not work, it is necessary to verify the correct ID downloading MIB database of the firmware version.
Solution
1) Log-in the Support portal https://support.fortinet.com/.
2) On the Customer Service Support page, select:
Download -> Firmware Images, then select Product -> FortiManager (Or Fortianalyzer) and then select 'Download' tab.
3) Select the appropriate FortiManager/FortiAnalyzer Version directory (6.2, 6.4, 7.0, 7.2, ...).
4) Select the MIB file and download the applicable files using the https link (version 6.4.6, as example): FORTINET-FORTIMANAGER-FORTIANALYZER-MIB-build2363.mib.
These OIDs are the most typical used, normally they do not change from version to version, however if it does not work refer to scope of this article.
fmSysCpuUsage <----- Current CPU usage (percentage).
.1.3.6.1.4.1.12356.103.2.1.1
fmSysMemUsed <---- Current memory used (KB).
.1.3.6.1.4.1.12356.103.2.1.2
fmSysMemCapacity <---- Total physical and swap memory installed (KB).
.1.3.6.1.4.1.12356.103.2.1.3
fmSysDiskUsage <---- Current hard disk usage (MB).
.1.3.6.1.4.1.12356.103.2.1.4
fmSysDiskCapacity <---- Total hard disk capacity (MB).
.1.3.6.1.4.1.12356.103.2.1.5
fnSysSerial <---- Unit serial number
.1.3.6.1.4.1.12356.100.1.1.1
fmSysVersion <---- Firmware version of the unit.
.1.3.6.1.4.1.12356.103.2.1.7
To get all OIDs available.
It is possible to use FortiManager/FortiAnalyzer CLI, 'Wireshark' and 'iReasoning MIB Browser' (as example) to get details of communication and OIDs (notice that sniffing on port 161 and compare the result with equivalent commands on FortiManager/FortiAmaylzer is an advance verification, not all basic/intermediate users may achieve this purpose).
To troubleshoot SNMP.
Get the PCAP file sniffing SNMP Protocol (it is possible to open it with Wireshark) and then verify what is the communication. Get in mind the following on SNMP protocol.
*get-request is SNMP server is trying to get all OIDs available in SNMP.
*get-response is FortiManager/FortiAnalyzer answering to the general request of SNMP (not using specific OIDs).
fmSysMemUsed <----- Current memory used (KB).
fmSysCpuUsage <----- Current CPU usage (percentage).
fmSysMemCapacity <----- Total physical and swap memory installed (KB).
fmSysDiskUsage <----- Current hard disk usage (MB).
fmSysDiskCapacity <----- Total hard disk capacity (MB).
fmSysVersion <----- Firmware version of the unit.
fnSysSerial <----- Unit serial number.
Related article.
Technical Tip : How to configure and test snmpv3 config on fmg/faz
