Details

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

    Description

      Fuji Xerox Apoes C8180 has a slightly different sysObjectID on their new MFC's ** 

      sysDescr    | FUJIFILM Apeos C8180; System 23.5.15, ESS 1.3.3, IOT 47.5.0, HCF 12.0.0, Finisher C 2.8.0, ADF 1.40.0, Panel 1.1.4, IPS Accelerator 21.9.0, Boot 1.0.155, Contents 5.1.32, Plugin 5.1.32, Booklet  0.35.0, Stapler  1.1.0                                                                                                                                                    
      sysObjectID | .1.3.6.1.4.1.297.1.11.93.2.1.2.5.4

      Attachments

        Activity

          [OBS-4593] New Fuji Xerox MFC

          Improved in r12960.

          landy Mike Stupalov added a comment - Improved in r12960.
          psemp Paul Semple added a comment - - edited

          To test, I added a new sysObjectID ".1.3.6.1.4.1.297.1.11.93.2."  to "fuji-xerox-printer" in os.inc.php and re-ran discovery and the MFC now displays fine.

          psemp Paul Semple added a comment - - edited To test, I added a new sysObjectID ".1.3.6.1.4.1.297.1.11.93.2."  to "fuji-xerox-printer" in os.inc.php and re-ran discovery and the MFC now displays fine.

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            psemp Paul Semple
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: