Details
Minor Description
I just recently deployed an Observium server to monitor the network. So far it has been great and no issues adding devices. I have a few Ruggedcom switches some with up to date FW and one that needs a FW update. On the older FW v5.5 the device are discovered and added as a generic device. With v5.7 Observium gives a false positive of a Wowza Streaming engine after what appears to be a re-detect.
o Re-Detect OS matched (wowza-engine: Wowza Streaming Engine):
I'm pretty new at this so hopefully someone can point me in the right direction on how to resolve the issue. Attached are both 5.5 and 5.7 discovery debugs.
Attachments
Activity
Seems this device is shit...
Oid three 1.3.6.1.4.1 required for vendor private entities.
Try more vendor specific Oids (but exacly with all options):
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.15004 > myagent-ent.snmpwalk
|
if this still get timeout, try same with bulk option:
snmpbulkwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.15004 > myagent-bulk.snmpwalk
|
The first command worked and is attached. Second timed out. A regular walk on that OID "snmpwalk -v2c -c <community> <host> .1.3.6.1.4.1" starts walking but eventually times out. Attached the output.
Based on your response, make snmpdump as this oids:
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.2.1 > myagent.snmpwalk
|
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
|
This is a new (unsupported) hardware, for improve detect and discovery need snmpdump.
Or you can provide snmp access to test device, for this write me in Discord channel @landy
Started dump '/tmp/<host>.snmpwalk' for device <host> from Oid: .
WARNING. THIS MAY TAKE A WHILE, PLEASE BE PATIENT WHILE IT RUNNING...
Check snmpdump running by cmd: wc -l /tmp/<host>.snmpwalk
Timeout: No Response from udp:<host>:161
Snmpdump not completed or exit by timeout.
<user>@observium:/opt/observium$
This works.... snmpwalk -v2c -c <community> <host> .1.3.6.1.2.1
you can make snmpdump by new script:
./scripts/snmpdump.php -h <device>
|
where <device> is device_id or hostname of device as stored in observium db.
"snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk"
couldn't get this syntax to work but a regular walk pulls the info from the device
"snmpwalk -v2c -c <community> <hostname>
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.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf 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.
Thanks so much for your help.