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

Fortigate NPU on CPU-Graph and NPU Session Count

Details

    • Improvement
    • Resolution: Incomplete
    • Major
    • None
    • Enterprise Edition
    • OS, Poller
    • None

    Description

      I had a long conversation with Fortinet about the npu processor.
      The used attribute 'fgProcessorUsage', showed in the CPU graph, isn't a usal processor usage. It is an average session count on the npu. But at the moment there is no support for this value, instead of this we should use fgNPUSessionCount per NPU.

      So you need to remove the fgProcessorUsage from the "Processor Graph" and bring the fgNPUSessionCount into the "Session Graph".

      Attachments

        Activity

          [OBS-4070] Fortigate NPU on CPU-Graph and NPU Session Count
          landy Mike Stupalov added a comment -

          Not really understand, what you mean..

          fgNPUSessionCount OBJECT-TYPE
          		 
              DESCRIPTION
          		 
                  "Number of active sessions in the NPU"
          		 
              ::= { fgNPUEntry 3 }

          For CPU usage we use correct Oids (as written in FortiGate docs).

          landy Mike Stupalov added a comment - Not really understand, what you mean.. fgNPUSessionCount OBJECT-TYPE DESCRIPTION "Number of active sessions in the NPU" ::= { fgNPUEntry 3 } For CPU usage we use correct Oids (as written in FortiGate docs).
          itz Jens Brückner added a comment -

          Sorry, it is not Major.

          itz Jens Brückner added a comment - Sorry, it is not Major.
          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
            itz Jens Brückner
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: