Details
-
Help
-
Resolution: Not A Bug
-
Minor
-
None
-
Professional Edition
-
None
Description
Does the observium currently support these Juniper MIBS?
Input OID:
1.3.6.1.2.1.31.1.1.1.6
Output OID:
1.3.6.1.2.1.31.1.1.1.10
How do I view this in the Observium?
Attachments
Activity
Issue Type | Original: Task [ 3 ] | New: Help [ 10200 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Issue Type | Original: Improvement [ 4 ] | New: Task [ 3 ] |
Resolution | New: Not A Bug [ 6 ] | |
Status | Original: Pending Response [ 10000 ] | New: Resolved [ 5 ] |
Comment |
[ Please make and attach additional information about the device: * full snmp dump from device: {noformat} snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk {noformat} _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: {noformat} ./discovery.php -d -h <device> ./poller.php -d -h <device> {noformat} * additionally attach device and/or vendor specific MIB files {color:#505F79}_Note, this comment is added automatically._{color} ] |
Status | Original: Open [ 1 ] | New: Pending Response [ 10000 ] |
This is not a Juniper MIBs, but common HC counters in IF-MIB.
(IF-MIB::ifHCInOctets, IF-MIB::ifHCOutOctets).
We already support this counters for any device (if it exist on device snmp walk).