Router inventory is not working

Mike Stupalov added a comment - 2024/04/24 09:08 AM This is JunOS EVO and it's support common ENTITY-MIB inventory. I switched discovery inventory to this mib. Device report incorrect `entPhysicalContainedIn` oid value, ie for this PICs. ENTITY-MIB::entPhysicalIndex.25 = INTEGER: 25 ENTITY-MIB::entPhysicalDescr.25 = STRING: PIC: 8X400GE-MR + 4X100GE-MR @ 0/2/* ENTITY-MIB::entPhysicalVendorType.25 = OID: JUNIPER-CHASSIS-DEFINES-MIB::jnxProductLinePTX1000136mr.0 ENTITY-MIB::entPhysicalContainedIn.25 = INTEGER: 2 ENTITY-MIB::entPhysicalClass.25 = INTEGER: 0 ENTITY-MIB::entPhysicalParentRelPos.25 = INTEGER: 2 ENTITY-MIB::entPhysicalName.25 = STRING: ENTITY-MIB::entPhysicalHardwareRev.25 = STRING: 255.09 ENTITY-MIB::entPhysicalFirmwareRev.25 = STRING: Default ENTITY-MIB::entPhysicalSoftwareRev.25 = STRING: 23.2R1.15-EVO ENTITY-MIB::entPhysicalSerialNum.25 = STRING: BUILTIN ENTITY-MIB::entPhysicalMfgName.25 = STRING: Juniper Networks ENTITY-MIB::entPhysicalModelName.25 = STRING: Default ENTITY-MIB::entPhysicalAlias.25 = STRING: Default ENTITY-MIB::entPhysicalAssetID.25 = STRING: Default ENTITY-MIB::entPhysicalIsFRU.25 = INTEGER: true(1) entity with index 2 not exist in table.

Eduardo Schoedler added a comment - 2024/04/23 08:10 PM - edited Mike, This box has 3 PICs. I see PIC 0/0/x and 0/1/x but PIC 0/2/x is not showing. It's present and have transceivers on it. Thanks.

Mike Stupalov added a comment - 2024/04/23 07:24 PM Should be fixed in r13521.

Eduardo Schoedler added a comment - 2024/04/23 03:42 PM Sent e-mail again, please confirm receipt.

Mike Stupalov added a comment - 2024/04/23 10:39 AM Hi Eduardo, I received your email, but this snmpdump not usable for virtual environment. You should use all snmpwalk options as Bot written! Alternatively you can create snmpdump by our script: ./scripts/snmpdump.php -h <device> Make snmpdump for specific device (exist in db) to file <hostname>.snmpwalk

Mike Stupalov added a comment - 2024/04/19 08:58 AM In Discord DM (link in bot comment) to @landy or mail mike@observium.org

Eduardo Schoedler added a comment - 2024/04/18 10:42 PM MIB is .1.3.6.1.2.1.47.1.1.1.1

Eduardo Schoedler added a comment - 2024/04/18 10:40 PM How can I post a snmpwalk with subtle information? Can I send you directly, by email perhaps?

Observium Bot added a comment - 2024/04/18 10:38 PM 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.