Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3032

Add support for FortiSwitch

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • None

    Description

      Hi there, it would be great to get additional support for our Fortinet FortiSwitches.  At the moment we only get very basic port and vlan information with no system or environmental data.  I have attached the FortiSwitch MIBs.

      Attachments

        1. FORTINET-CORE-MIB.mib
          14 kB
          Matthew McDougall
        2. FORTINET-FORTISWITCH-MIB.mib
          5 kB
          Matthew McDougall

        Activity

          [OBS-3032] Add support for FortiSwitch
          landy Mike Stupalov added a comment -

          Improved in r9939.

          landy Mike Stupalov added a comment - Improved in r9939.
          landy Mike Stupalov added a comment -

          And some field which you rewritten to "**REDACTED**" need to correctly detect.
          To not save this information here, send the file to my mail (mike@observium.org).

          landy Mike Stupalov added a comment - And some field which you rewritten to "** REDACTED **" need to correctly detect. To not save this information here, send the file to my mail ( mike@observium.org ).
          landy Mike Stupalov added a comment -

          Hi caacorg, thanks.
          But we want snmpwalk with exactly such options: --hexOutputLength=0 -ObentxU as I written previously. And for extended device support more interesting is vendor oid tree .1.3.6.1.4.1.

          In walk which you attached I do not see additional information (which we do not yet support).

          landy Mike Stupalov added a comment - Hi caacorg , thanks. But we want snmpwalk with exactly such options: --hexOutputLength=0 -ObentxU as I written previously. And for extended device support more interesting is vendor oid tree .1.3.6.1.4.1 . In walk which you attached I do not see additional information (which we do not yet support).
          caacorg Matthew McDougall added a comment -

          Hi Mike, thanks for your assistance. Snmpwalk results attached.

          caacorg Matthew McDougall added a comment - Hi Mike, thanks for your assistance. Snmpwalk results attached.
          landy Mike Stupalov added a comment -

          caacorg ?

          landy Mike Stupalov added a comment - caacorg ?
          landy Mike Stupalov added a comment -

          Hrm, in fact, we already support such devices.
          Maybe something is not correctly detected or something has changed in the new firmware.

          Please give SNMP access to device (access can send privately by mail mike@observium.org),
          or if access not possible, please do full snmp walk from device:

          snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
          		 
          snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

          myagent.snmpwalk you can also send to this mail or attach to the issue here.

          landy Mike Stupalov added a comment - Hrm, in fact, we already support such devices. Maybe something is not correctly detected or something has changed in the new firmware. Please give SNMP access to device (access can send privately by mail mike@observium.org), or if access not possible, please do full snmp walk from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk myagent.snmpwalk you can also send to this mail or attach to the issue here.

          People

            landy Mike Stupalov
            caacorg Matthew McDougall
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: