Skip to main content
realmark
New Member
December 5, 2023
Question

SNMP OID for transciever DDM/DOM features (namely RX dBm)

  • December 5, 2023
  • 8 replies
  • 3482 views

The MIBs for FortiOS core, Fortigate, and Fortiswitch (where I really care) seem to lack any OIDs for transceiver diagnostic data. Namely RX strength. We do this sort of monitoring with all our non-Forti networks, typically with LibreNMS. I checked the OID mappings that Aruba/Cisco/Mikrotik tend to use, found no similar spot in an SNMPWALK of a fs-1048e, fs-148f, fs-108f, or FG-201F.

 

Obviously the switches have the data, as the below command would show.

 

 get switch modules status port49
____________________________________________________________
Port(port49)
temperature      40.539062 C
voltage          3.300300 volts
alarm_flags      0x0040
warning_flags    0x0040
laser_bias       35.442001 mAmps
tx_power         -2.726214 dBm
rx_power         -18.124792 dBm
options          0x000F ( TX_DISABLE TX_FAULT RX_LOSS TX_POWER_LEVEL1 )
options_status   0x0008 ( TX_POWER_LEVEL1 )

 Anybody know if it's possible to poll the transceivers for health metrics via SNMP? 

8 replies

ebilcari
Staff
Staff
December 6, 2023

This is a fair request but it seems like this OID doesn't exist yet. I would suggest to contact your local Fortinet representative to file a NFR (new feature request) since this would be very helpful to keep an eye on monitoring the fibers health.

For the moment there is support through API for FSW transceivers managed by FGT that you can try if your monitoring system supports API:
GET /switch-controller/managed-switch/tx-rx

 

Parameters:

mkey * Filter: FortiSwitch ID.
port * Name of the port.

 

Response:

tx-power
rx-power

 

Emirjon
Tozz
Visitor III
January 12, 2024

I was looking for DOM/DMI information in SNMP as well. IMHO it's quite bizarre this isn't implemented

networkers
New Member
January 19, 2026

Is it already available nowadays?

Tozz
Visitor III
January 19, 2026

No. Transceiver monitoring is somewhat implemented in SNMP now, but as expected from Fortinet the implementation is completely broken.

 

The OIDs are entirely random and you cannot identify which OID belongs to which SFP ports (other than guessing based on port number)

 

I've reported a bug for this issue, which was accepted, but not yet resolved.

 

realmark
realmarkAuthor
New Member
January 19, 2026

Thank you, I'd seen SNMP updates in release notes but hadn't taken the time to crawl the MIB again.

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.