Show output for:
$ snmpget -v2c -c <community> -Ot <device> HOST-RESOURCES-MIB::hrSystemUptime.0
$ snmpget -v2c -c <community> -Ot <device> SNMP-FRAMEWORK-MIB::snmpEngineTime.0
Michael wrote:
That would be the uptime of the SNMP engine/daemon of the device.
They usually match on most sane devices. 500+ days, your miles may vary...
Michael
On 29 Jun 2017, at 7:36 pm, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote:
Dear all,
Runnig an SRX5600 cluster with version 12.3X48-D20.4. I noticed that displayed system uptime value doesn’t match :
<image001.png>
via CLI :
node0:
Current time: 2017-06-29 11:18:08 CEST System booted: 2016-01-09 23:20:47 CET (76w4d 10:57 ago) Protocols started: 2016-01-10 03:58:57 CET (76w4d 06:19 ago) 11:18AM up 536 days, 10:57, 2 users, load averages: 0.59, 0.34, 0.30
node1:
Current time: 2017-06-29 11:18:08 CEST System booted: 2016-01-09 23:20:47 CET (76w4d 10:57 ago) 11:18AM up 536 days, 10:57, 0 users, load averages: 0.00, 0.00, 0.00
I tried re-discovering the device, no changes. This is on latest stable release 8580. I tried to run a debug, this is what I get :
CMD[[0;33m/usr/bin/snmpget -v2c -c *** -Pu -OQUst -m SNMPv2-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'fw01-par01':'161' sysObjectID.0 sysUpTime.0[0m] [0m CMD EXITCODE[[0;32m0[0m] CMD RUNTIME[[0;32m0.0063s[0m][0m STDOUT[ sysObjectID.0 = enterprises.2636.1.1.1.2.28 sysUpTime.0 = 338397151 ][0m SNMP STATUS[[0;32mTRUE[0m][0m
Anyone noticed this ?
Best regards.
Youssef BENGELLOUN - ZAHR - Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr <image713928.PNG> Web : prodware.fr
<imagedece58.JPG> <image6916e1.JPG> <imaged404a4.JPG> <image975500.JPG> <image408de1.JPG> <image199c7c.JPG>
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium