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


SNMP Cisco System Health - No data since startup

Votes:

0

Your Vote:

Up

Down

Hello,

We have several different new Cisco devices and every new SNMP Cisco System Health sensors that have been defined are greyed out with "No data since startup" error. The devices are on different probes, I also restarted the probes and it still doesn't work. All the other sensors (few hundreds) are working fine.

Please advise. Regards, Yaron Eidelman

cisco-switch snmp-sensor system-health

Created on Jan 25, 2016 6:30:10 PM by  YEidelman (0) 2

Last change on Mar 13, 2018 10:53:19 AM by  Luciano Lingnau [Paessler Support]



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

We had a customer contact us via a support ticket about a similar issue.

In this particular case, the monitored device did not provide all the OID's required by the sensor. And this results in the error. We'd recommend anyone encountering this issue to first of all update the device's firmware to the latest version and then deleting and re-creating the sensor.

Background: For temperatures, we need three distinct OID's:

  • 1.3.6.1.4.1.9.9.13.1.3.1.2.index Temperature Descr
  • 1.3.6.1.4.1.9.9.13.1.3.1.6.index Temperature State
  • 1.3.6.1.4.1.9.9.13.1.3.1.3.index Temperature Value

With this particular case/customer, the Temperature Value readings were missing, which caused the sensor to fail.. Don't hesitate to contact us if you encounter a similar issue so that we can confirm the precise cause.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Apr 20, 2018 12:01:31 PM by  Luciano Lingnau [Paessler Support]



4 Replies

Votes:

0

Your Vote:

Up

Down

Hello Yaron,

Please download our SNMP Tester, start it on the affected Probe and configure it to target the device in question.

Copy and paste these lines into a text document, save it as "scan_script.txt" for example:

--------
Cisco Systemhealth
--------
----
CPU
----
walk=1.3.6.1.4.1.9.9.109.1.1.1.1
----
Memory
----
walk=1.3.6.1.4.1.9.9.221.1.1.1.1
walk=1.3.6.1.4.1.9.9.48.1.1.1
----
Voltage
----
walk=1.3.6.1.4.1.9.9.13.1.2
----
Temperature
----
walk=1.3.6.1.4.1.9.9.13.1.3.1
----
Fans
----
walk=1.3.6.1.4.1.9.9.13.1.4.1.3
----
Power Supplys
----
walk=1.3.6.1.4.1.9.9.13.1.5.1.3
----
Other
----
walk=1.3.6.1.4.1.9.9.91.1.1.1
----
Other Limits
----
walk=1.3.6.1.4.1.9.9.91.1.2.1
----
Other Names
----
walk=1.3.6.1.2.1.47.1.1.1.1.7
----

Use option Scan Script in SNMP-Tester to load the saved scan_script.txt and start the scan. Save the result and send it to support@paessler.com. Please use the same subject as here (SNMP Cisco System...) and place a link of your KB-post in the email.

Thank you & Kind regards.

Created on Jan 27, 2016 1:53:14 PM by  Erhard Mikulik [Paessler Support]

Last change on Jan 27, 2016 1:53:34 PM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello, Ive sent the logs to paessler support. Thank you. Yaron Eidelman

Created on Jan 31, 2016 10:01:28 AM by  YEidelman (0) 2



Votes:

0

Your Vote:

Up

Down

Logs received, get back to you shortly.

Kind regards.

Created on Feb 1, 2016 9:00:56 AM by  Erhard Mikulik [Paessler Support]



Accepted Answer

Votes:

0

Your Vote:

Up

Down

We had a customer contact us via a support ticket about a similar issue.

In this particular case, the monitored device did not provide all the OID's required by the sensor. And this results in the error. We'd recommend anyone encountering this issue to first of all update the device's firmware to the latest version and then deleting and re-creating the sensor.

Background: For temperatures, we need three distinct OID's:

  • 1.3.6.1.4.1.9.9.13.1.3.1.2.index Temperature Descr
  • 1.3.6.1.4.1.9.9.13.1.3.1.6.index Temperature State
  • 1.3.6.1.4.1.9.9.13.1.3.1.3.index Temperature Value

With this particular case/customer, the Temperature Value readings were missing, which caused the sensor to fail.. Don't hesitate to contact us if you encounter a similar issue so that we can confirm the precise cause.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Apr 20, 2018 12:01:31 PM by  Luciano Lingnau [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.