Details

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

    Description

      Hello

      New Juniper PTX10001-36MR-K seem to be misidentified as generic devices.

      Attaching more info below to add proper support on it.

      Thank you

      Attachments

        Issue Links

          Activity

            [OBS-5028] add Juniper PTX10001-36MR-K

            It works ok now. thank you

            nuno Nuno Vieira added a comment - It works ok now. thank you

            I answered to you in mail about why your device still not detected. (Seems as firmware issue or device configuration trouble).

            But I improved detect for your recent snmpdump and should be fixed in r14023.

            landy Mike Stupalov added a comment - I answered to you in mail about why your device still not detected. (Seems as firmware issue or device configuration trouble). But I improved detect for your recent snmpdump and should be fixed in r14023.

            Hi Mike.

            I am affraid it didnt resolved.

            I have upgraded to rolling r14021, and reran the discovery and pooler, but it still appears as generic.

            I have performed the snmpwalk but its way to large to post here.

            I am sending the details via email to Mike.

            Thank you.

            nuno Nuno Vieira added a comment - Hi Mike. I am affraid it didnt resolved. I have upgraded to rolling r14021, and reran the discovery and pooler, but it still appears as generic. I have performed the snmpwalk but its way to large to post here. I am sending the details via email to Mike. Thank you.

            Your snmpwalk is incomplete.
            But it is sufficient to identify the issue (firmware issue).

            Improved detect in r14020 (rolling updates).

            landy Mike Stupalov added a comment - Your snmpwalk is incomplete. But it is sufficient to identify the issue (firmware issue). Improved detect in r14020 (rolling updates).

            snmpwalk attached.

            nuno Nuno Vieira added a comment - snmpwalk attached.

            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
              nuno Nuno Vieira
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: