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

Discovery of Fortiauthenticator does not use FORTINET-FORTIAUTHENTICATOR-MIB

Details

    • Bug
    • Resolution: Unresolved
    • Trivial
    • None
    • Professional Edition
    • Discovery

    Description

      Hi!

      We have adding a Fortiauthenticator in observium but during the discovering and poller steps the use of the FORTINET-FORTIAUTHENTICATOR-MIB mib is not done.
      Only FORTINET-CORE-MIB is used.
      In the MIB global list on Observium we don't see FORTIAUTHENTICATOR-MIB but all others FORTI* appear.

      In attachment some informations.
      Can you help us please.

      Attachments

        1. discovery_sfhvfac01.txt
          131 kB
        2. ls_dir_sfhvfac01.txt
          0.4 kB
        3. myagent.discovery
          135 kB
        4. myagent.poller
          150 kB
        5. myagent.snmpwalk
          522 kB
        6. observium_forti_authenticator_01.png
          observium_forti_authenticator_01.png
          197 kB
        7. observium_forti_authenticator_02.png
          observium_forti_authenticator_02.png
          7 kB
        8. observium_forti_authenticator_03.png
          observium_forti_authenticator_03.png
          91 kB
        9. poller_sfhvfac01.txt
          149 kB

        Activity

          [OBS-4017] Discovery of Fortiauthenticator does not use FORTINET-FORTIAUTHENTICATOR-MIB
          Philippe Schweizer added a comment -

          Hi,

          sorry for the delay, the requested files (myagent.snmpwalk for snmp dump,  myagent.discovery and myagent.poller) are now created and attached.

          Just to understand,  "In device MIBs page listed only supported MIB", but we have found this page : https://mibs.observium.org/mib/FORTINET-FORTIAUTHENTICATOR-MIB/

          and the MIB file is present :

          PROD:[---@sfhvmon01 fortinet]# pwd
          /opt/observium/mibs/fortinet
          PROD:[---@sfhvmon01 fortinet]# ll
          total 676
          rw-rr- 1 root root  15162 Oct 13 09:12 FORTINET-CORE-MIB
          rw-rr- 1 root root 108061 Oct 13 09:12 FORTINET-FORTIADC-MIB
          rw-rr- 1 root root  14767 Mar  1  2018 FORTINET-FORTIANALYZER-MIB
          rw-rr- 1 root root  14305 Oct 13 09:12 FORTINET-FORTIAUTHENTICATOR-MIB
          rw-rr- 1 root root 401653 Jan 19 09:02 FORTINET-FORTIGATE-MIB
          rw-rr- 1 root root  20595 Oct 13 09:12 FORTINET-FORTIMAIL-MIB
          rw-rr- 1 root root  42080 Oct 13 09:12 FORTINET-FORTIMANAGER-FORTIANALYZER-MIB
          rw-rr- 1 root root   2565 Mar  1  2018 FORTINET-FORTIMANAGER-MIB
          rw-rr- 1 root root   6096 Jul 15  2019 FORTINET-FORTISWITCH-MIB
          rw-rr- 1 root root  23567 Jan  4  2021 FORTINET-FORTIWEB-MIB
          rw-rr- 1 root root  20134 Mar  1  2018 FORTINET-MIB-280

           

          So it does not mean that this MIB file is supported?

          Best regards.

           

           

          Philippe Schweizer added a comment - Hi, sorry for the delay, the requested files (myagent.snmpwalk for snmp dump,  myagent.discovery and myagent.poller) are now created and attached. Just to understand,  "In device MIBs page listed only supported MIB", but we have found this page : https://mibs.observium.org/mib/FORTINET-FORTIAUTHENTICATOR-MIB/ and the MIB file is present : PROD: [---@sfhvmon01 fortinet] # pwd /opt/observium/mibs/fortinet PROD: [---@sfhvmon01 fortinet] # ll total 676 rw-r r - 1 root root  15162 Oct 13 09:12 FORTINET-CORE-MIB rw-r r - 1 root root 108061 Oct 13 09:12 FORTINET-FORTIADC-MIB rw-r r - 1 root root  14767 Mar  1  2018 FORTINET-FORTIANALYZER-MIB rw-r r - 1 root root  14305 Oct 13 09:12 FORTINET-FORTIAUTHENTICATOR-MIB rw-r r - 1 root root 401653 Jan 19 09:02 FORTINET-FORTIGATE-MIB rw-r r - 1 root root  20595 Oct 13 09:12 FORTINET-FORTIMAIL-MIB rw-r r - 1 root root  42080 Oct 13 09:12 FORTINET-FORTIMANAGER-FORTIANALYZER-MIB rw-r r - 1 root root   2565 Mar  1  2018 FORTINET-FORTIMANAGER-MIB rw-r r - 1 root root   6096 Jul 15  2019 FORTINET-FORTISWITCH-MIB rw-r r - 1 root root  23567 Jan  4  2021 FORTINET-FORTIWEB-MIB rw-r r - 1 root root  20134 Mar  1  2018 FORTINET-MIB-280   So it does not mean that this MIB file is supported? Best regards.    
          Philippe Schweizer made changes -
          Attachment New: myagent.poller [ 19611 ]
          Philippe Schweizer made changes -
          Attachment New: myagent.discovery [ 19610 ]
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          Philippe Schweizer made changes -
          Attachment New: myagent.snmpwalk [ 19609 ]
          landy Mike Stupalov added a comment -

          In device MIBs page listed only supported MIB.

          For improve device/mib support need create and attach snmpdump as Bot requested.

          landy Mike Stupalov added a comment - In device MIBs page listed only supported MIB. For improve device/mib support need create and attach snmpdump as Bot requested.
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

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

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.
          Philippe Schweizer created issue -

          People

            landy Mike Stupalov
            Philippe Schweizer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: