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


Can I Monitor my HP ProCurve Switch Health?

Votes:

0

Your Vote:

Up

Down

I'd like to monitor the health of my HP ProCurve switches, but there is no dedicated sensor. Additionally, SNMP CPU and Memory don't work on the appliance. Any workaround?

custom-lookup health hp-procurve snmp snmp-custom-sensor

Created on Mar 28, 2017 1:10:02 PM by  Stephan Linke [Paessler Support]



10 Replies

Accepted Answer

Votes:

3

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 16 or later

Introduction

This works with the SNMP Custom Advanced Sensor, which allows you to query specific device OIDs within one sensor. In combination with the Lookups, this will give you the metrics you're looking for, nicely formatted.


The finished sensor, monitoring the Health of your ProCurve Switch

Installation

Remarks
  • SNMP Sensors need to work in general on your appliance. Check out our SNMP Guide if you need to set this up first.
  • You installed the Lookups at the end
Setup
  1. Create a new SNMP Custom Advanced Sensor on the device
  2. Configure the channels like in the below table:
NameOIDValue TypeUnit / Lookup
CPU Load1.3.6.1.4.1.11.2.14.11.5.1.9.6.1.0GaugeCPU
Free Memory1.3.6.1.4.1.11.2.14.11.5.1.1.2.1.1.1.6.1GaugeBytes Memory
Fan State1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.1Gaugeprtg.customlookup.hp.procurve
Primary Power Supply State1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.2Gaugeprtg.customlookup.hp.procurve
Secondary Power Supply State1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.3Gaugeprtg.customlookup.hp.procurve
Temperature State1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.4Gaugeprtg.customlookup.hp.procurve
Average Temperature1.3.6.1.4.1.11.2.14.11.1.2.8.1.1.9.0GaugeTemperature


You're done! Apply some limits to the CPU Load / Memory channel. It should look something like in the screenshot.

OID List

Parameter NameDescription
1.3.6.1.4.1.11.2.14.11.5.1.9.6.1.0The current CPU load in percent (integer)
1.3.6.1.4.1.11.2.14.11.5.1.1.2.1.1.1.6.1Free Memory in bytes
1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.1Current Fan State
1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.2Primary Power Supply State
1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.3Secondary Power Supply State
1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.4Current Temperature State
1.3.6.1.4.1.11.2.14.11.1.2.8.1.1.9.0The average system temperature

State Table

StateDescription
1Invalid Value
3Bad
3Warning
4Good
5Not Present

Lookup

<?xml version="1.0" encoding="UTF-8"?>
  <ValueLookup id="prtg.customlookups.hp.procurve" desiredValue="4" undefinedState="None" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PaeValueLookup.xsd">
    <Lookups>
      <SingleInt state="None" value="1">
        No valid value returned.
      </SingleInt>
      <SingleInt state="Error" value="2">
        Bad
      </SingleInt>
      <SingleInt state="Warning" value="3">
        Warning
      </SingleInt>
      <SingleInt state="Ok" value="4">
        Good
      </SingleInt>
      <SingleInt state="None" value="5">
        Not Present
      </SingleInt>
    </Lookups>
  </ValueLookup>

Created on Mar 28, 2017 1:37:36 PM by  Stephan Linke [Paessler Support]

Last change on Apr 6, 2017 8:03:33 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hallo,

ich habe gestern versucht, diesen Sensor zu konfigurieren, doch leider bekomme ich keine Werte abgefragt...Sensor bleibt rot.

Kann mich hier jemand unterstützen?

Mit freundlichen Grüßen

Nico_K

Created on Aug 29, 2017 9:35:27 AM by  Nico_K (0) 1



Votes:

0

Your Vote:

Up

Down

Hi Nico,

Welchen Fehler erhalten Sie denn genau?


Mit freundlichen Grüßen,
Stephan Linke, Tech Support Team

Created on Aug 29, 2017 10:31:03 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hallo Herr Linke,

Die Fehlermeldung lautet: No such instance (snmp-Fehler #223)

Created on Aug 30, 2017 2:02:55 PM by  Nico_K (0) 1



Votes:

0

Your Vote:

Up

Down

Dann wäre jetzt interessant, welche OID hier nicht existiert. Bitte mal mit dem SNMP-Tester einen Walk auf das Gerät laufen lassen, und zwar auf die OID 1.3.6.1.4.1.11.2.14.11

Dann einfach das Log hier posten :)


Mit freundlichen Grüßen,
Stephan Linke, Tech Support Team

Created on Aug 30, 2017 6:53:15 PM by  Stephan Linke [Paessler Support]

Last change on Aug 30, 2017 6:53:57 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hallo Herr Linke,

anbei das Log:

Paessler SNMP Tester 5.2.3 Computername: XXX Interface: XXX
04.09.2017 14:10:58 (7 ms) : Device: 10.X.X.X
04.09.2017 14:10:58 (10 ms) : SNMP V2c
04.09.2017 14:10:58 (14 ms) : Custom OID 1.3.6.1.4.1.11.2.14.11
04.09.2017 14:10:58 (21 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
04.09.2017 14:10:58 (24 ms) : -------
04.09.2017 14:10:58 (27 ms) : Value: No such object (SNMP error # 222)
04.09.2017 14:10:58 (31 ms) : Done

Scheinbar kennt der Switch die OID nicht..

Created on Sep 4, 2017 12:13:59 PM by  Nico_K (0) 1

Last change on Sep 5, 2017 7:31:18 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Könnten Sie das Ganze bitte nochmals testen, aber mit "Walk" statt "Custom OID" ausgewählt?


Mit freundlichen Grüßen,
Stephan Linke, Tech Support Team

Created on Sep 5, 2017 7:32:08 AM by  Stephan Linke [Paessler Support]

Last change on Sep 5, 2017 7:32:31 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Korrekt, die OIDs gibt es auf dem Gerät nicht. Gibt es hier evtl. ein Firmware Update? Ansonsten mal beim HP-Support fragen, ob es evtl. alternative OIDs für dieses Gerät gibt. Falls nicht, sollten auf der Dokumentations-CD oder im Download-Bereich von HP MIB-Dateien verfügbar sein.

Diese können Sie mit unserem MIB Importer in PRTG importieren und mithilfe des SNMP Library Sensor in PRTG einbinden.


Kind regards,
Stephan Linke, Tech Support Team

Created on Sep 6, 2017 9:55:08 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I have tried creating this so that PRTG may monitor the health of my HP ProCurve 2610 switches but I have been unsuccessful in getting this to work.

I am using PRTG 18.4.47.1962+

Here is what I've done so far:

1) Used the Paessler SNMP Tester 5.2.3 to test various OIDs on one of my Procurve 2610 switches. I defined the IP address, SNMP V2c, the community string, and selected a Custom OID value of "1.3.6.1.4.1.11.2.14.11.5.1.9.6.1.0" for CPU utilization. These are the results I received:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: HWCPRTG Interface: (172.20.2.106)
2/28/2019 4:03:27 PM (14 ms) : Device: 10.21.50.4
2/28/2019 4:03:27 PM (19 ms) : SNMP V2c
2/28/2019 4:03:27 PM (25 ms) : Custom OID 1.3.6.1.4.1.11.2.14.11.5.1.9.6.1.0
2/28/2019 4:03:27 PM (103 ms) : SNMP Datatype: ASN_INTEGER
2/28/2019 4:03:27 PM (109 ms) : -------
2/28/2019 4:03:27 PM (114 ms) : Value: 3
2/28/2019 4:03:27 PM (124 ms) : Done

I then tried the rest of the OIDs listed above and saw values returned on all but the very last one, but this is the least of my concerns.

2) Copied the contents of the Lookup box above and pasted it into the lookups\custom folder on my server. I named the file prtg.customlookups.hp.procurve.ovl ((At a later point I made a copy of the file named prtg.customlookups.hp.procurve.xsd because the .xsd look similar. This was just an attempt at getting it work.))

3) Created a SNMP Custom Advanced sensor and input the following info:

Sensor Channel #1 Name:         CPU Load
Sensor Channel #1 OID:      1.3.6.1.4.1.11.2.14.11.5.1.9.6.1.0
Sensor Channel #1 Unit:        CPU
Sensor Channel #2 Name:     Free Memory
Sensor Channel #2 OID:        1.3.6.1.4.1.11.2.14.11.5.1.1.2.1.1.1.6.1
Sensor Channel #2 Unit:        Bytes Memory
Sensor Channel #3 Name:      Fan State
Sensor Channel #3 OID:        1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.1
Sensor Channel #3 Unit:        prtg.customlookup.hp.procurve
etc. etc.

I realize I am configuring something wrong but I'm not sure what it is.

Created on Feb 28, 2019 10:13:56 PM by  arigsby (10) 1

Last change on Mar 1, 2019 5:27:51 AM by  Sven Roggenhofer [Paessler Technical Support]



Votes:

1

Your Vote:

Up

Down

I figured out my problem. I had misspelled it as prtg.customlookup.hp.procurve when the XML code said prtg.customlookups.hp.procurve. It works well. This has been a great help. Thank you.

Created on Mar 1, 2019 5:08:33 PM by  arigsby (10) 1



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.