Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

FortiGate 100E Monitoring

Hi all. First ever post!

So, we upgraded our edge firewalls from FortiGate 200Bs and 300Cs to 100Es in order to support the 5.4.x code, but once we upgraded and rediscovered our firewalls, not all the interfaces are showing up in the discovery process. I started poking around custom poller creation and noticed that the 100E is not in the MIB database. My question is this: Is there a way for me to append the MIB file (that I verified has 100E stuff in it) to the MIBs.cfg file in NPM? Or, is there a way for us to send the MIB file to SolarWinds so they can publish a new MIBs.cfg file?

Thanks!

Find more posts tagged with

fortigate

mib

fortinet

Accepted answers

alec_j123

I finally got an engineer who had a 100e-series firewall in their lab. It turns out that when we moved our configs from old firewall to new, the interface SNMP indexes got messed up, which is why only random ports were being returned by NPM. Only random SNMP indexes were correct. For example, "port1" is supposed to have "set snmp-index 27", but in our config is was 15 or something like that. When changing the SNMP index numbers to what the engineer provided worked in his lab, NPM was able to see and poll interface information properly.

All comments

TerryHarding

Raise a Support Call requesting inclusion of the MIB with SolarWinds and attach the MIB file. They will update the cfg file and let you know when it is available.

alec_j123

Thanks! I've opened a case with them and am waiting on a reply.

tinmann0715

...And then post here so the rest of us can benefit from your efforts. :-) And you will be showered with Thwack points as your reward.

sja

I will say that solarwinds doesn't have to do with all that

solarwinds use ONLY rfc1213 to get that information

Your HW vendor is probably missing some standard features...

What object IDs (OIDs) does NPM poll for interface information - SolarWinds Worldwide, LLC. Help and Support

No Interface Bandwidth Utilization Data available (Data is not available)

alec_j123

Do you think this is the issue even though when I list the resources some, but not all interfaces are shown? vs

Like I said, all of our other, older FortiGate devices poll just fine, but the new ones don't.

sja

no I didn't expect to see the stat. Check box.

i think that could help

should tell you what the box support

Use the Poller Checker tool - SolarWinds Worldwide, LLC. Help and Support

alec_j123

Just an update for everyone:

I'm stuck between a battle of finger pointing between SolarWinds and FortiNet support. SolarWinds says that FortiNet doesn't seem to be using standard OIDs (which I'm siding with at this point) and FortiNet is hinting that the SolarWinds MIB database isn't good and I should be using a different poller that allows me to use their MIBs directly to monitor our devices.

alec_j123

Also, when I updated our 600Ds to 5.4.4, polling returned everything I expected to see.

alec_j123

rana468

Hi,

But how to change the SNMP index number? I am also getting the same problem as most of our fortigate devices have been upgraded to latest firmware 5.4 with 100E and 100D model.

alec_j123

You must CLI in to the FortiGates.

config system interface

edit "port1"

set snmp-index #

edit "port2"

set snmp-index #

...etc and so on...

end

What I did is assign them all to really high numbers first to avoid the FortiGate saying the SNMP index number was already used, then reassigned them back to what FortiNet support told me they should be which is posted below. I trimmed out some of the configs they sent, but all the indexes should be there.

config system interface

edit "dmz"

set snmp-index 1

edit "mgmt"

set snmp-index 2

edit "wan1"

set snmp-index 3

edit "wan2"

set snmp-index 4

edit "ha1"

set snmp-index 5

edit "ha2"

set snmp-index 6

edit "npu0_vlink0"

set vdom "root"

set status down

set type physical

set snmp-index 7

edit "npu0_vlink1"

set vdom "root"

set status down

set type physical

set snmp-index 8

edit "modem"

set vdom "root"

set mode pppoe

set type physical

set snmp-index 9

edit "ssl.root"

set vdom "root"

set type tunnel

set alias "SSL VPN interface"

set snmp-index 10

edit "port16"

set vdom "root"

set type physical

set snmp-index 12

edit "port15"

set vdom "root"

set type physical

set snmp-index 13

edit "port14"

set vdom "root"

set type physical

set snmp-index 14

edit "port13"

set vdom "root"

set type physical

set snmp-index 15

edit "port12"

set vdom "root"

set type physical

set snmp-index 16

edit "port11"

set vdom "root"

set type physical

set snmp-index 17

edit "port10"

set vdom "root"

set type physical

set snmp-index 18

edit "port9"

set vdom "root"

set type physical

set snmp-index 19

edit "port8"

set vdom "root"

set type physical

set snmp-index 20

edit "port7"

set vdom "root"

set type physical

set snmp-index 21

edit "port6"

set vdom "root"

set type physical

set snmp-index 22

edit "port5"

set vdom "root"

set type physical

set snmp-index 23

edit "port4"

set vdom "root"

set type physical

set snmp-index 24

edit "port3"

set vdom "root"

set type physical

set snmp-index 25

edit "port2"

set vdom "root"

set type physical

set snmp-index 26

edit "port1"

set vdom "root"

set type physical

set snmp-index 27

end

surfertom

You can also do the following:

config sys int

edit <int name>

set snmp-index 0

This will cause the device to re-pick a new index #. It worked like a charm for me when I had the same problem of all interfaces not showing.