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

Additional Fortinet MIBS

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery

    Description

      Could you please add the two MIBS attached to the Fortinet directory? 

       

      Attachments

        Issue Links

          duplicates

          Add New Device / OS - User wants to add support for currently unsupported device or OS. OBS-4018 Add MIB for FortiAP

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Progress

          Activity

            [OBS-4434] Additional Fortinet MIBS
            landy Mike Stupalov made changes -
            Link New: This issue duplicates OBS-4018 [ OBS-4018 ]
            landy Mike Stupalov made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Pending Response [ 10000 ] New: Resolved [ 5 ]
            landy Mike Stupalov added a comment -

            MIBs added in r12581.

            But if you want improve support for devices with MIBs, you should create snmpdump from device(s) as Bot requested.

            landy Mike Stupalov added a comment - MIBs added in r12581. But if you want improve support for devices with MIBs, you should create snmpdump from device(s) as Bot requested.
            bot Observium Bot made changes -
            Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
            khamilton@exegy.com Kent Hamilton created issue -
            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.

            People

              landy Mike Stupalov
              khamilton@exegy.com Kent Hamilton
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: