limitation when monitoring uptime with snmp

[Carracido]

Hello Community.

I have an inquiry with which maybe you can help me. This is the situation:

In order to know the uptime I´m using the OID 1.3.6.1.2.1.25.1.1.0 to get the value of object hrSystemUptime. This is a counter of 32 bits and considering it´s counting in hundreds of seconds, the maximum uptime without overflow is: 2^32 = 4294967296 (hundreds of seconds) -> 497 days.

So if the device is not rebooted before 497 days the uptime value won´t be correct by using snmp.

Do you know any way (snmp or other means) to bypass this limitation and to get the correct uptime regardless the value??

Thanks in advance,

Marcos.

[kiwi]

Hi @Carracido,

I'm not sure if there's a workaround for that ... or if the latest MIB might be 64 bit aware.  Maybe someone else can answer that question or it might be worthwile to reach out to support to answer your question.

That said, it would mean that you don't do any firmware upgrades for 497 days ... I'm not convinced that would be a good idea either 🙂

Cheers !

-Kiwi.

[BPry]

@Carracido,

Not aware of any workaround and unless I don't  believe the latest MIB is 64 bit aware at all. However as @kiwi already mentioned that would mean that this device has ran for well over a year without any updates; that wouldn't be a great thing to run across. 

[Remo]

---

@BPry wrote:

@Carracido,

that wouldn't be a great thing to run across. 

---

Specially not for a security appliance ...

[Remo]

@Carracido

Did you try the API to get the value?