New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


DISMAN-EVENT-MIB::sysUpTimeInstance = No such object (SNMP error # 222)

Votes:

0

Your Vote:

Up

Down

Guys,

Are there any plans to support SNMP Traffic sensor for devices without sysUpTime OID (1.3.6.1.2.1.1.3.0) counter?

I do realize, the counter is mandatory and not having is device software flaw.

The workaround with creating separate in and out counters and combining them into aggregated sensor is not feasible if you need to monitor more than a handful ports...

Could you tune default behavior of SNMP Traffic sensor a bit to take it easier, if sysUpTime OID is missing, please? The was a similar discussion here: KB: Help monitoring meraki network

snmp sysuptime sysuptimeinstance

Created on Feb 5, 2015 9:38:55 PM by  OlPRTG (0) 1

Last change on Dec 29, 2015 6:49:36 AM by  Luciano Lingnau [Paessler Support]



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello,

as you already mention, devices with no OID for system uptime are not RFC compatible. We use the system uptime to ensure correct monitoring; it helps us to detect when a device was last reset. This is necessary for the correct interpretation of the counter values, and for the functionality to automatically update the port names after a device reset, for example.

For this reason we cannot support devices that do not return an uptime value.

Created on Feb 9, 2015 10:26:28 AM by  Daniel Zobel [Paessler Support]

Last change on Feb 9, 2015 10:28:08 AM by  Daniel Zobel [Paessler Support]



3 Replies

Votes:

0

Your Vote:

Up

Down

Hi,
Thank you for your feedback. Please allow me to forward this to our development team. I will get back to you as soon as I know more.
Best regards

Created on Feb 6, 2015 1:54:30 PM by  Konstantin Wolff [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Sounds good! Let me know if you need any additional info (like logs)

Created on Feb 6, 2015 6:51:50 PM by  OlPRTG (0) 1



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello,

as you already mention, devices with no OID for system uptime are not RFC compatible. We use the system uptime to ensure correct monitoring; it helps us to detect when a device was last reset. This is necessary for the correct interpretation of the counter values, and for the functionality to automatically update the port names after a device reset, for example.

For this reason we cannot support devices that do not return an uptime value.

Created on Feb 9, 2015 10:26:28 AM by  Daniel Zobel [Paessler Support]

Last change on Feb 9, 2015 10:28:08 AM by  Daniel Zobel [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.