FortiWeb CPU and Memory Monitoring in the SolarWinds Platform

7/20/2026 5:05 PM

7/20/2026 5:26 PM

Environment

• SolarWinds Network Performance Monitor (NPM)

• Fortinet FortiWeb appliances (physical or virtual)

• SysObjectID tree: 1.3.6.1.4.1.12356.107.x

• SNMP version: SNMPv2c or SNMPv3

Symptoms

• CPU and memory values for FortiWeb nodes show as null or are not populated in the SolarWinds web console

• All CPU and memory pollers show as light red (not supported) in the SolarWinds Poller Checker Tool with Error Code 0

• The Poller Checker Tool color results for FortiWeb nodes:

  • N.Cpu.SNMP.Fortigate — light red (not supported)

  • N.Memory.SNMP.Fortigate — light red (not supported)

  • N.Cpu.SNMP.HrProcessorLoad — light red (not supported)

  • N.Memory.SNMP.HrStorage — light red (not supported)

  • All other built-in CPU and memory pollers — light red (not supported)

Network Performance Monitor

This is expected behavior and is not a SolarWinds Platform issue or a polling configuration error.

FortiWeb appliances use the Fortinet FortiWeb enterprise MIB tree (SysObjectID 1.3.6.1.4.1.12356.107.x). This is a completely separate product line and MIB tree from FortiGate (SysObjectID 1.3.6.1.4.1.12356.101.x). SolarWinds built-in CPU and memory pollers — including N.Cpu.SNMP.Fortigate, N.Memory.SNMP.Fortigate, N.Cpu.SNMP.HrProcessorLoad, and N.Memory.SNMP.HrStorage — do not target the FortiWeb MIB tree. SolarWinds does not natively support CPU and memory monitoring for FortiWeb appliances.

CPU and memory monitoring for FortiWeb devices can be achieved by creating custom Universal Device Pollers (UnDP) targeting the FortiWeb-specific SNMP OIDs.

No downtime or service restart is required for any step below.

Step 1 — Obtain FortiWeb SNMP OIDs

Obtain the FortiWeb-specific SNMP OIDs for CPU and memory from Fortinet's official documentation or community resources. The OIDs required are specific to the FortiWeb MIB and differ from the FortiGate MIB.

Disclaimer: The following Fortinet community resource is provided as a reference only. This is third-party content not owned, maintained, or supported by SolarWinds. Your organization should internally review and assess to what extent, if any, information from this source will be incorporated into your environment. You elect to use third-party content at your own risk.

• Fortinet Community — FortiWeb SNMP OIDs for monitoring system basic information: https://community.fortinet.com/fortiweb-40/technical-tip-fortiweb-snmp-oid-for-monitoring-system-basic-information-196351

For the FortiWeb MIB file, contact Fortinet support or download from the Fortinet support portal. Consult your Fortinet representative for the correct MIB version for your FortiWeb firmware.

Step 2 — Verify SNMP Connectivity to the FortiWeb Device

Before creating custom pollers, confirm that the FortiWeb device is responding to SNMP queries from the SolarWinds polling engine. Run the SolarWinds SnmpWalk tool from the polling engine server against the FortiWeb device IP, targeting the FortiWeb enterprise OID tree:

• Tool location (verify the actual path from your environment): C:\Program Files (x86)\SolarWinds\Orion\SnmpWalk.exe

• Target OID tree: 1.3.6.1.4.1.12356.107 (FortiWeb enterprise MIB root)

If the OID tree returns values, proceed to Step 3. If no response is returned, verify SNMP credentials, community string, and firewall rules allowing UDP port 161 from the polling engine to the FortiWeb device.

Note: On polling engines with Windows FIPS mode enforced, the SolarWinds SnmpWalk GUI will return Error #31224 (Crypto Error) when SHA (SHA-1) is selected as the Authentication Algorithm. SHA-1 is not FIPS 140-2 compliant. In this case, use the Poller Checker Tool instead — it uses the Orion polling engine's own SNMP stack and is not affected by Windows FIPS restrictions.

Step 3 — Create Custom Universal Device Pollers (UnDP)

Using the OIDs obtained in Step 1, create custom UnDP pollers for CPU and memory:

• Navigate to Settings > All Settings > Universal Device Pollers

• Click New Universal Device Poller

• Enter the FortiWeb CPU OID obtained from Fortinet documentation

• Set the SNMP Get Type to GET for scalar OIDs

• Set the Data Type to Rate or Gauge as appropriate for the OID

• Save and repeat for the memory OID

For full UnDP creation steps, refer to the SolarWinds documentation:

• https://documentation.solarwinds.com/en/success_center/npm/content/npm-creating-universal-device-pollers.htm

Step 4 — Assign the UnDP Pollers to FortiWeb Nodes

• Navigate to the FortiWeb node's detail page in the SolarWinds web console

• Click Edit Node

• Under Universal Device Pollers, assign the CPU and memory pollers created in Step 3

• Save and click Poll Now

• Wait one full poll cycle and confirm CPU and memory values are populating

Step 5 — Display the Polled Data

Add the following resources to the FortiWeb node detail page to display the polled data:

• Universal Device Poller Status — displays current polled values

• Tabular Universal Device Poller — displays polled values in a tabular format

Additional Notes

• FortiWeb appliances (SysObjectID 1.3.6.1.4.1.12356.107.x) are a separate Fortinet product line from FortiGate (SysObjectID 1.3.6.1.4.1.12356.101.x). Pollers designed for FortiGate are not compatible with FortiWeb and will show as light red (not supported) in the Poller Checker Tool — this is expected

• UnDP pollers are tied to the polling engine on which they are created. If the FortiWeb nodes are polled by an Additional Polling Engine (APE), the UnDP pollers must be created on that APE

• A community-contributed FortiWeb VM UnDP package is available on THWACK Content Exchange. Review the OIDs included against your FortiWeb firmware version before deploying

• THWACK Content Exchange — FortiWeb VM UnDP: https://thwack.solarwinds.com

Please note that Thwack is a community space where users may post any content as a suggestion or recommendations to you for your internal use. The information set forth herein may come from third-party websites or customers. SolarWinds is not liable for any downtime or any issue that may occur if you perform the following suggestions on the link provided. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.