Description
This article describes how to monitor the CPU and memory status of each VDOM on the FortiGate.
Scope
FortiGate (all versions), SNMP
Solution
First, ensure that the FORTINET-CORE and FORTINET-FORTIGATE SNMP Management Information Base (MIB) files have been downloaded and installed to the SNMP Manager that will be querying the FortiGate. These MIBs may either be downloaded from the FortiGate itself under System -> SNMP in the Global VDOM or they can be downloaded from the Fortinet Support Site in the firmware download section. For more information on these MIBs, refer to the following documentation links:
With the above in mind, the SNMP Object Identifiers (OIDs) used to measure VDOM-specific CPU and memory usage are as follows:
fgVdEntCpuUsage - .1.3.6.1.4.1.12356.101.3.2.1.1.5.x
fgVdEntMemUsage - .1.3.6.1.4.1.12356.101.3.2.1.1.6.x
Where the 'x' is the snmp-index number for that specific vdom.
The above entries are part of a larger SNMP table called fgVdTable (.1.3.6.1.4.1.12356.101.3.2.1), and this includes fgVdEntName (.1.3.6.1.4.1.12356.101.3.2.1.1.2.x), which can be useful for mapping snmp-index numbers to named VDOMs. Alternatively, these snmp-index values can be found under the config system vdom-property section of the Global VDOM:
FortiGate # config global
FortiGate # show system vdom-property
config system vdom-property
edit "root"
set description "property limits for vdom root"
set snmp-index 1
next
edit "NGFW"
set description "property limits for vdom NGFW"
set snmp-index 2
next
edit "Test"
set description "property limits for vdom Test"
set snmp-index 3
next
end
As an example, the following screenshot shows the CPU and memory status of the root VDOM on the FortiGate:
Likewise, this screenshot shows the CPU and memory status of the NGFW VDOM on the same FortiGate:
Finally, the following screenshot shows the corresponding output from a MIB browser application that performed SNMP Get-Bulk requests for the fgVdTable entries (including fgVdEntCpuUsage and fgVdEntMemUsage):
