“High Availability Information” Missing in List Resources for FortiGate Nodes in SolarWinds Platform

1/21/2026 8:19 PM

1/21/2026 8:19 PM

When setting up FortiGate HA monitoring as described in the NPM documentation

Monitor FortiGate firewalls, you should see a “High Availability Information” option in List Resources for FortiGate nodes.

 

Typical scenario:

• The FortiGate cluster is configured in Active‑Passive or Active‑Active mode.
• The FortiGate node is added and monitored in SolarWinds using valid SNMP credentials.
• However, “High Availability Information” is not present in List Resources and cannot be selected.

 

Behind the scenes, FortiGate HA monitoring in the SolarWinds Platform depends on a FortiGate HA discovery step that queries specific HA SNMP OIDs. If this step does not run, fails, or decides that the device is not in HA, the platform will not create or expose the High Availability Information resource for that node.

Network Performance Monitor

1. SolarWinds Platform version does not support FortiGate HA

• FortiGate High Availability monitoring is supported starting with SolarWinds Platform / NPM 2025.4.
• In earlier versions (for example, 2025.1 or 2025.2), FortiGate HA is not fully supported, and “High Availability Information” will not appear in List Resources for FortiGate nodes by design.

2. FortiGate is not detected as HA‑capable

Even if you configured HA on the firewall, the SNMP view might not reflect an HA setup:

• The device reports itself as standalone or in a non‑HA mode through the HA SNMP OID:
• fgHaSystemMode — 1.3.6.1.4.1.12356.101.13.1.1.0 (Standalone = 1)
• High Availability monitoring is only enabled when the device is in Active‑Passive or Active‑Active mode. If it reports standalone, the platform treats HA as not applicable and does not create the HA resource.

3. SNMP access to FortiGate HA OIDs fails

General SNMP polling may succeed, but HA‑specific OIDs can still fail due to:

• ACLs or firewall rules blocking access to the HA MIB branches.
• Timeouts or partial SNMP responses when walking the HA OIDs.
• SNMP configuration differences between general OIDs and HA OIDs.

If the SolarWinds Platform cannot reliably query the HA OID trees, it will not enable the High Availability Information resource.

Relevant HA OID branches:

• 1.3.6.1.4.1.12356.101.13.1 – HA system information (mode, group ID, override, auto‑sync, schedule, group name, etc.)
• 1.3.6.1.4.1.12356.101.13.2.1 – HA member statistics table

4. Unsupported FortiOS version

• FortiGate HA monitoring requires FortiOS 6.4.0 or later.
• Older FortiOS versions may not fully expose the required HA OIDs, or may implement them in a way that does not meet the current HA monitoring logic. In such cases, the platform cannot reliably detect HA and will not show the HA resource.

5. Discovery or List Resources not re‑run after HA changes

• The FortiGate node might have been added before HA was configured on the device.
• After enabling or changing HA on the FortiGate, Discovery or List Resources was not re‑run, so the platform never re‑evaluated the HA state.
• Until a new discovery/List Resources pass is completed successfully, High Availability Information will not be added.

Work through the steps below to restore or enable High Availability Information for FortiGate nodes.

1. Verify SolarWinds Platform version

If you are on any version earlier than 2025.4, upgrade to 2025.4 or later to enable FortiGate HA support.

Note: Without 2025.4+, the High Availability Information option for FortiGate devices will not be available in List Resources.

 

2. Confirm the node is a FortiGate firewall

Ensure the node is discovered and classified as a FortiGate device:

• The node should be monitored via SNMP.
• The device’s SysObjectID should be in the FortiGate enterprise tree, typically:
  1.3.6.1.4.1.12356.101.*

If the node is detected as a generic device or something other than FortiGate, correct the monitoring configuration (for example, fix SNMP credentials or polling method) and then re‑run List Resources.

 

3. Confirm FortiGate HA configuration

On the FortiGate side:

• Verify that the firewall is configured in Active‑Passive or Active‑Active HA mode.

On the SNMP side:

• Check the HA mode OID:
  fgHaSystemMode (OID 1.3.6.1.4.1.12356.101.13.1.1.0) must not return 1 (Standalone).

 

For High Availability Information to be enabled:

• fgHaSystemMode must not indicate standalone mode.
• If it reports standalone, the SolarWinds Platform will treat HA as not applicable and will not show the HA resource.

 

4. Confirm HA SNMP OID access

From the polling engine (or an equivalent system with SNMP access), verify that the FortiGate responds to the HA SNMP OIDs:

• 1.3.6.1.4.1.12356.101.13.1 – HA system information
• 1.3.6.1.4.1.12356.101.13.2.1 – HA member statistics

If these OIDs time out, return errors, or do not return the expected data, correct any SNMP ACLs, credentials, or firewall rules on the FortiGate, then retest.

 

5. List Resources

After confirming:

• Platform version is 2025.4+
• Node is identified as FortiGate
• HA is properly configured on the device and available via SNMP

Do the following:

1. Go to the FortiGate Node Details page.
2. In the Management widget, click List Resources.
3. Let the List Resources scan complete.
4. If the environment meets all requirements above, the “High Availability Information” option should now appear; ensure it is selected, then submit the changes.

 

When to contact SolarWinds Support

If all of the following are true:

• You are running SolarWinds Platform / NPM 2025.4 or later.
• The FortiGate is confirmed to be in Active‑Passive or Active‑Active HA mode.
• The device responds correctly to the HA SNMP OIDs listed above.
• You have re‑run List Resources / Discovery, and “High Availability Information” is still missing.

Then gather the following and open a case with SolarWinds Support:

• SolarWinds diagnostics from the polling engine monitoring the FortiGate node.
• SNMP walk output covering:
• 1.3.6.1.4.1.12356.101.13.1
• 1.3.6.1.4.1.12356.101.13.2.1
• Screenshots of:
• The FortiGate’s HA configuration/status.
• The node’s List Resources page (showing that HA is missing).