Monitoring HP ProCurve switches natively with SCOM 2012: an utter disappointment

11 May

SCOM 2012 has greatly enhanced monitoring capabilities for network devices such as routers and switches. Adding network devices using SNMP works like a charm and is quite simple. However, some consideration is required how much information you can get out of these devices.

Microsoft has provided a list of network devices it supports which is available at the following location:

The Excel sheet provides filtering mechanisms to display the devices from one or more manufacturers. The devices listed provide extended monitoring capabilities in SCOM 2012. They will be labeled as ‘CERTIFIED’ in SCOM which is great.

HP ProCurve switches are nowhere to be found in this list, monitoring on these devices is very limited, actually only PING statistics and availability status can be retrieved from these switches. These switches will be labeled as ‘GENERIC’.

From a SCOM 2012 point of view, this is quite a disappointment. Extra Management Packs and labour are required to get some decent monitoring information from HP ProCurve switches…


8 responses to “Monitoring HP ProCurve switches natively with SCOM 2012: an utter disappointment

  1. Hayden

    19/06/2012 at 04:24

    I’ve yet to find a way to import x-snmp which did a reasonable job of monitoring these switches in 2007 R2 into Ops Manager 2012 as these devices are now counted as legacy network devices…

  2. humphric

    26/06/2012 at 16:46


    I wanted to ask if you have had any luck in your HP Procurve switch monitoring? I’m also trying to some various things monitored related to the switches and I’m quite new to the whole thing and was looking for help/advice.


  3. mwesterink

    26/06/2012 at 21:55

    At the moment I need to investigate when I get the opportunity again.
    I tried xSNMP as well but that got me really nowhere.
    For the customer, the basic monitoring was enough for them, but I can imagine others want more information from these devices…

    Update 17-08-2012: recently I learned the devices used were HP ProCurve 2610-48 which are ‘pretty dumb’ switches (I’m not networking specialist so my knowledge about these devices is limited). Results might be different for different models but will still be recognised as Generic devices

  4. Hayden

    22/02/2013 at 00:07

    A colleague of mine came up with this;
    The trick is to make some changes to a couple of the discovery configuration files which are located here:

    C:\Program Files\System Center 2012\Operations Manager\Server\NetworkMonitoring\conf\discovery

    The files that are of most use are:

    Change DisplayNameFormat = “AUTOASSIGNED” to DisplayNameFormat = “MIBIISYSNAME” – This will discover the hostname of the device.

    This file allows you to discover your own devices and mark them as certified. By marking them as certified and seeting the Vendor and Model parameters it appears to enable the features that certified devices have as far as actively monitoring ports and connections between devices etc.

    Below is an example of the one I’ve used with our HP J9477a Pro Curve Switches:
    # HP ProCurve J9477A Switch
    . {
    TYPE = Switch
    MODEL = J9477A
    CONT = Generic-Bridge
    VLAN = Dot1q
    HEALTH = HPProCurveJ4Series
    Environment = HPProCurveJ4SeriesEnvMon:DeviceID
    Interface-Fault = MIB2
    Interface-Performance = MIB2
    Port-Fault = MIB2
    Port-Performance = MIB2
    Port-Ethernet-Performance = dot3_Ethernet

    You will need the OID as it is reported in SCOM for the device. For our ProCurves it was .

    Hope that helps.

  5. Post

    09/09/2014 at 11:00

    Dear Hayden,

    Could you give me some more information about changing the conf file?

    I added the ProCurve entry but the switch is still marked as generic. (i’ve changed the OID)

  6. Chuck

    27/07/2015 at 13:54

    I’m trying to figure out why my HP Procurve switches are showing up as Not Monitored. Your blog seems to indicate that this is normal for this model of switch however they do appear as CERTIFIED so I’m guessing that SCOM does support them now. If that is true then why are they still showing a not monitored?

  7. juzlas

    19/10/2015 at 15:30

    I try to change that conf file, but nothing to change, i have two different procurve (HP) switch, try to change conf file, but nothing to change.. and of course i have HP V1810-48G switch, i mast to create this switch performance, but i cant, because i can monitored just 2 ports (interfaces). i thing that problem will be in certified. any ideas?

    • mwesterink

      21/10/2015 at 21:50

      Hi juzlas,

      Even though a switch is certified you depend on the information the device releases to OpsMgr. Even to this day, it looks like HP devices are still very limited in releasing any device information. I believe there’s not much we can do about it at this time.

      Hope this helps…


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Steve Thompson [MVP]

The automation specialist

Boudewijn Plomp

Cloud and related stuff...

Anything about IT

by Alex Verboon

Deployment Made Simple

Modern Workplace

Azure, Hybrid Identity & Enterprise Mobility + Security

Daan Weda

This site is all about System Center and PowerShell

IT And Management by Abheek

Microsoft certified Trainer -Abheek

Heading To The Clouds

by Marthijn van Rheenen

%d bloggers like this: