Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Monitor Hyper-V and an interface via SNMP/WMI

Monitor Hyper-V and an interface via SNMP/WMI

Table of contents

Overview

This article discusses how to monitor Hyper-V and an interface using SNMP/WMI. 

Environment

  • All SAM versions
  • All NPM versions

Detail

If you have NPM installed and are monitoring an interface via SNMP, switching to WMI to monitor Hyper-V will cause the interface's historical data to be lost. You can either monitor Hyper-V via WMI or an interface via SNMP, not both.

Most Hyper-V hosts have more than one network interface.

  • Add an alternate interface IP as an SNMP node in Orion for the purpose of monitoring the Hyper-V hosts Network interface errors, discards, utilization, and so on.
    or
  • Another alternative is to create a simple template for monitoring network interface statistics using the Browse for Component Monitor wizard under Settings > SAM Settings.
Last modified

Tags

Classifications

Public